Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index d488b9f59f19221874863a4d6762643ec5f495ff..14c5a7bebd1c15aac928081a1c60408114c03387 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -7,665 +7,706 @@
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
        <item>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
        <item>

-               <title>«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig integritet»</title>
-               <link>http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html</guid>
-                <pubDate>Tue, 27 Jun 2017 17:50:00 +0200</pubDate>
-               <description>&lt;p&gt;Jeg kom over teksten
-«&lt;a href=&quot;https://freedom-to-tinker.com/2017/06/21/killing-car-privacy-by-federal-mandate/&quot;&gt;Killing
-car privacy by federal mandate&lt;/a&gt;» av Leonid Reyzin på Freedom to
-Tinker i dag, og det gleder meg å se en god gjennomgang om hvorfor det
-er et urimelig inngrep i privatsfæren å la alle biler kringkaste sin
-posisjon og bevegelse via radio.  Det omtalte forslaget basert på
-Dedicated Short Range Communication (DSRC) kalles Basic Safety Message
-(BSM) i USA og Cooperative Awareness Message (CAM) i Europa, og det
-norske Vegvesenet er en av de som ser ut til å kunne tenke seg å
-pålegge alle biler å fjerne nok en bit av innbyggernes privatsfære.
-Anbefaler alle å lese det som står der.
-
-&lt;p&gt;Mens jeg tittet litt på DSRC på biler i Norge kom jeg over et sitat
-jeg synes er illustrativt for hvordan det offentlige Norge håndterer
-problemstillinger rundt innbyggernes privatsfære i SINTEF-rapporten
-«&lt;a href=&quot;https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933&quot;&gt;Informasjonssikkerhet
-i AutoPASS-brikker&lt;/a&gt;» av Trond Foss:&lt;/p&gt;
+               <title>Retten til kontant betaling er en rettighet som må brukes for å beholdes</title>
+               <link>http://people.skolelinux.org/pere/blog/Retten_til_kontant_betaling_er_en_rettighet_som_m__brukes_for___beholdes.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Retten_til_kontant_betaling_er_en_rettighet_som_m__brukes_for___beholdes.html</guid>
+                <pubDate>Tue, 11 Dec 2018 10:00:00 +0100</pubDate>
+               <description>&lt;p&gt;&lt;a href=&quot;https://www.fn.no/Om-FN/Avtaler/Menneskerettigheter/FNs-verdenserklaering-om-menneskerettigheter&quot;&gt;FNs
+menneskerettighetserklæring&lt;/a&gt; artikkel 13 første punkt lyder som
+følger:&lt;/p&gt;

 
 &lt;p&gt;&lt;blockquote&gt;
 
 &lt;p&gt;&lt;blockquote&gt;

-«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig
-  integritet.»
+Enhver har rett til å bevege seg fritt og til fritt å velge
+oppholdssted innenfor en stats grenser.

 &lt;/blockquote&gt;&lt;/p&gt;
 
 &lt;/blockquote&gt;&lt;/p&gt;
 

-&lt;p&gt;Så enkelt kan det tydeligvis gjøres når en vurderer
-informasjonssikkerheten.  Det holder vel at folkene på toppen kan si
-at «Personvernet er ivaretatt», som jo er den populære intetsigende
-frasen som gjør at mange tror enkeltindividers integritet tas vare på.
-Sitatet fikk meg til å undres på hvor ofte samme tilnærming, å bare se
-bort fra behovet for personlig itegritet, blir valgt når en velger å
-legge til rette for nok et inngrep i privatsfæren til personer i
-Norge.  Det er jo sjelden det får reaksjoner.  Historien om
-reaksjonene på Helse Sør-Østs tjenesteutsetting er jo sørgelig nok et
-unntak og toppen av isfjellet, desverre.  Tror jeg fortsatt takker nei
-til både AutoPASS og holder meg så langt unna det norske helsevesenet
-som jeg kan, inntil de har demonstrert og dokumentert at de verdsetter
-individets privatsfære og personlige integritet høyere enn kortsiktig
-gevist og samfunnsnytte.&lt;/p&gt;
+&lt;p&gt;Det er altså en menneskerett å kunne bevege seg fritt i landet.
+For å bevege seg fritt i landet, så må en kunne bevege seg uten å bli
+sporet.  Det vil i dagens samfunn innebære å bevege seg uten å legge
+igjen digitale spor og uten å være radiomerket.  Hvis en vet at ens
+bevegelser, hvor en befinner seg når, og hvem som befinner seg i
+nærheten, blir samlet inn og gjort tilgjengelig for fremmede, det være
+seg myndighetene eller private organisasjoner, så kan en ikke lenger
+bevege seg fritt.  Dette gjør at det er en forutsetning for å ha glede
+av retten til å bevege seg fritt i landet at en motstår fristelsen til
+å legge igjen digitale spor når en betaler for seg.  Rettigheter som
+ikke blir brukt, blit fjernet.  Den eneste måten i dag å unngå å legge
+igjen digitale spor når en betaler for seg, er å betale med kontanter,
+samt takke nei til å legge igjen navn og adresse (slik f.eks. Elkjøp
+ber om &amp;mdash; jeg sier de kan legge inn «anonym anonym» når
+datasystemet deres trenger et navn).  Personlig anbefaler jeg å
+konsekvent bruke kontant betaling når man beveger seg rundt, for å
+bidra til forsvaret av menneskerettighetene i Norge.  Kanskje noe også
+for deg?  Merk at det ikke er tilstrekkelig for å unngå sporing å
+betale med kontanter, men det er et lite steg i riktig retning.&lt;/p&gt;
+
+&lt;p&gt;Det er flere andre argumenter i tillegg til
+menneskerettighetsargumentet for å bruke kontanter.  I går hadde
+Dagbladet en utmerket kommentar av sin journalist John Olav Egeland om
+hvilket
+&lt;a href=&quot;https://www.dagbladet.no/kultur/kontantlost-diktatur/70543434&quot;&gt;kontantløst
+diktatur&lt;/a&gt; som venter oss hvis mange nok slutter å insistere på å
+betale med kontanter.  Jeg anbefaler deg å lese den.&lt;/p&gt;
+
+&lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
+det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
+til min adresse
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
+Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Updated sales number for my Free Culture paper editions</title>
-               <link>http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html</guid>
-                <pubDate>Mon, 12 Jun 2017 11:40:00 +0200</pubDate>
-               <description>&lt;p&gt;It is pleasing to see that the work we put down in publishing new
-editions of the classic &lt;a href=&quot;http://www.free-culture.cc/&quot;&gt;Free
-Culture book&lt;/a&gt; by the founder of the Creative Commons movement,
-Lawrence Lessig, is still being appreciated.  I had a look at the
-latest sales numbers for the paper edition today.  Not too impressive,
-but happy to see some buyers still exist.  All the revenue from the
-books is sent to the &lt;a href=&quot;https://creativecommons.org/&quot;&gt;Creative
-Commons Corporation&lt;/a&gt;, and they receive the largest cut if you buy
-directly from Lulu.  Most books are sold via Amazon, with Ingram
-second and only a small fraction directly from Lulu.  The ebook
-edition is available for free from
-&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;Github&lt;/a&gt;.&lt;/p&gt;
-
-&lt;table border=&quot;0&quot;&gt;
-&lt;tr&gt;&lt;th rowspan=&quot;2&quot; valign=&quot;bottom&quot;&gt;Title / language&lt;/th&gt;&lt;th colspan=&quot;3&quot;&gt;Quantity&lt;/th&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;th&gt;2016 jan-jun&lt;/th&gt;&lt;th&gt;2016 jul-dec&lt;/th&gt;&lt;th&gt;2017 jan-may&lt;/th&gt;&lt;/tr&gt;
-
-&lt;tr&gt;
-  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;Culture Libre / French&lt;/a&gt;&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;6&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;15&lt;/td&gt;
-&lt;/tr&gt;
-
-&lt;tr&gt;
-  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Fri kultur / Norwegian&lt;/a&gt;&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;1&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
-&lt;/tr&gt;
-
-&lt;tr&gt;
-  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;Free Culture / English&lt;/a&gt;&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;14&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;27&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;16&lt;/td&gt;
-&lt;/tr&gt;
-
-&lt;tr&gt;
-  &lt;td&gt;Total&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;24&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;34&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;31&lt;/td&gt;
-&lt;/tr&gt;
-
-&lt;/table&gt;
-
-&lt;p&gt;A bit sad to see the low sales number on the Norwegian edition, and
-a bit surprising the English edition still selling so well.&lt;/p&gt;
-
-&lt;p&gt;If you would like to translate and publish the book in your native
-language, I would be happy to help make it happen.  Please get in
-touch.&lt;/p&gt;
+               <title>Why is your site not using Content Security Policy / CSP?</title>
+               <link>http://people.skolelinux.org/pere/blog/Why_is_your_site_not_using_Content_Security_Policy___CSP_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_is_your_site_not_using_Content_Security_Policy___CSP_.html</guid>
+                <pubDate>Sun, 9 Dec 2018 15:00:00 +0100</pubDate>
+               <description>&lt;p&gt;Yesterday, I had the pleasure of watching on Frikanalen the OWASP
+talk by Scott Helme titled
+&quot;&lt;a href=&quot;https://frikanalen.no/video/626080/&quot;&gt;What We’ve Learned From
+Billions of Security Reports&lt;/a&gt;&quot;.  I had not heard of the
+&lt;a href=&quot;https://en.wikipedia.org/wiki/Content_Security_Policy&quot;&gt;Content
+Security Policy standard&lt;/a&gt; nor its ability to &quot;call home&quot; when a
+browser detect a policy breach (I do not follow web page design
+development much these days), and found the talk very illuminating.&lt;/p&gt;
+
+&lt;p&gt;The mechanism allow a web site owner to use HTTP headers to tell
+visitors web browser which sources (internal and external) are allowed to
+be used on the web site.  Thus it become possible to enforce a &quot;only
+local content&quot; policy despite web designers urge to fetch programs
+from random sites on the Internet, like the one
+&lt;a href=&quot;https://securityaffairs.co/wordpress/68966/hacking/browsealoud-plugin-hack.html&quot;&gt;enabling
+the attack&lt;/a&gt; reported by Scott Helme earlier this year.&lt;/p&gt;
+
+&lt;p&gt;Using CSP seem like an obvious thing for a site admin to implement
+to take some control over the information leak that occur when
+external sources are used to render web pages, it is a mystery more
+sites are not using CSP?  It is being
+&lt;a href=&quot;https://www.w3.org/TR/CSP/&quot;&gt;standardized under W3C&lt;/a&gt; these
+days, and is supposed by most web browsers&lt;/p&gt;
+
+&lt;p&gt;I managed to find &lt;a href=&quot;https://github.com/mozilla/django-csp&quot;&gt;a
+Django middleware for implementing CSP&lt;/a&gt; and was happy to discover
+it was already in Debian.  I plan to use it to add CSP support to the
+Frikanalen web site soon.&lt;/p&gt;
+
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Release 0.1.1 of free software archive system Nikita announced</title>
-               <link>http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</guid>
-                <pubDate>Sat, 10 Jun 2017 00:40:00 +0200</pubDate>
-               <description>&lt;p&gt;I am very happy to report that the
-&lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;Nikita Noark 5
-core project&lt;/a&gt; tagged its second release today.  The free software
-solution is an implementation of the Norwegian archive standard Noark
-5 used by government offices in Norway.  These were the changes in
-version 0.1.1 since version 0.1.0 (from NEWS.md):
-
-&lt;ul&gt;
-
- &lt;li&gt;Continued work on the angularjs GUI, including document upload.&lt;/li&gt;
- &lt;li&gt;Implemented correspondencepartPerson, correspondencepartUnit and
-   correspondencepartInternal&lt;/li&gt;
- &lt;li&gt;Applied for coverity coverage and started submitting code on
-   regualr basis.&lt;/li&gt;
- &lt;li&gt;Started fixing bugs reported by coverity&lt;/li&gt;
- &lt;li&gt;Corrected and completed HATEOAS links to make sure entire API is
-   available via URLs in _links.&lt;/li&gt;
- &lt;li&gt;Corrected all relation URLs to use trailing slash.&lt;/li&gt;
- &lt;li&gt;Add initial support for storing data in ElasticSearch.&lt;/li&gt;
- &lt;li&gt;Now able to receive and store uploaded files in the archive.&lt;/li&gt;
- &lt;li&gt;Changed JSON output for object lists to have relations in _links.&lt;/li&gt;
- &lt;li&gt;Improve JSON output for empty object lists.&lt;/li&gt;
- &lt;li&gt;Now uses correct MIME type application/vnd.noark5-v4+json.&lt;/li&gt;
- &lt;li&gt;Added support for docker container images.&lt;/li&gt;
- &lt;li&gt;Added simple API browser implemented in JavaScript/Angular.&lt;/li&gt;
- &lt;li&gt;Started on archive client implemented in JavaScript/Angular.&lt;/li&gt;
- &lt;li&gt;Started on prototype to show the public mail journal.&lt;/li&gt;
- &lt;li&gt;Improved performance by disabling Sprint FileWatcher.&lt;/li&gt;
- &lt;li&gt;Added support for &#39;arkivskaper&#39;, &#39;saksmappe&#39; and &#39;journalpost&#39;.&lt;/li&gt;
- &lt;li&gt;Added support for some metadata codelists.&lt;/li&gt;
- &lt;li&gt;Added support for Cross-origin resource sharing (CORS).&lt;/li&gt;
- &lt;li&gt;Changed login method from Basic Auth to JSON Web Token (RFC 7519)
-   style.&lt;/li&gt;
- &lt;li&gt;Added support for GET-ing ny-* URLs.&lt;/li&gt;
- &lt;li&gt;Added support for modifying entities using PUT and eTag.&lt;/li&gt;
- &lt;li&gt;Added support for returning XML output on request.&lt;/li&gt;
- &lt;li&gt;Removed support for English field and class names, limiting ourself
-   to the official names.&lt;/li&gt;
- &lt;li&gt;...&lt;/li&gt;
- 
-&lt;/ul&gt;
-
-&lt;p&gt;If this sound interesting to you, please contact us on IRC (#nikita
-on irc.freenode.net) or email
-(&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
-mailing list).&lt;/p&gt;
+               <title>New and improved Frikanalen Kodi addon version 0.0.3</title>
+               <link>http://people.skolelinux.org/pere/blog/New_and_improved_Frikanalen_Kodi_addon_version_0_0_3.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_and_improved_Frikanalen_Kodi_addon_version_0_0_3.html</guid>
+                <pubDate>Thu, 8 Nov 2018 10:30:00 +0100</pubDate>
+               <description>&lt;p&gt;If you read my blog regularly, you probably know I am involved in
+running and developing the &lt;a href=&quot;https://frikanalen.no/&quot;&gt;Norwegian
+TV channel Frikanalen&lt;/a&gt;.  It is an open channel, allowing everyone
+in Norway to publish videos on a TV channel with national coverage.
+You can think of it as Youtube for national television.
+In addition to distribution on RiksTV and Uninett, Frikanalen is also
+available as a Kodi addon.  The last few days I have updated the code
+to add more features.  A
+&lt;a href=&quot;https://kodi.tv/addon/plugins-video-add-ons/frikanalen-nett-tv&quot;&gt;new
+and improved version 0.0.3 Frikanalen addon&lt;/a&gt; was just made
+available via the Kodi repositories.  This new version include a
+option to browse videos by category, as well as free text search
+in the video archive.  It will now also show the video duration in the
+video lists, which were missing earlier.  A new and experimental
+link to the HD video stream currently being worked on is provided, for
+those that want to see what the &lt;a href=&quot;https://casparcg.com/&quot;&gt;CasparCG&lt;/a&gt;
+output look like.  The alternative is the SD video stream, generated
+using MLT.  CasparCG is controlled by our
+&lt;a href=&quot;https://github.com/Frikanalen/mltplayout/&quot;&gt;mltplayout
+server&lt;/a&gt; which instead of talking to mlt is giving PLAY instructions
+to the CasparCG server when it is time to start a new program.&lt;/p&gt;
+
+&lt;p&gt;By now, you are probably wondering what kind of content is being
+played on the channel.  These days, it is filled with technical
+presentations like those from &lt;a href=&quot;https://www.nuug.no/&quot;&gt;NUUG&lt;/a&gt;,
+&lt;a href=&quot;https://www.debconf.org/&quot;&gt;Debconf&lt;/a&gt;, Makercon, and TED,
+but there are also some periods with
+&lt;a href=&quot;https://www.empo.no/&quot;&gt;EMPT TV&lt;/a&gt; and
+&lt;a href=&quot;https://www.p7.no/&quot;&gt;P7&lt;/a&gt;.
+
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Idea for storing trusted timestamps in a Noark 5 archive</title>
-               <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</guid>
-                <pubDate>Wed, 7 Jun 2017 21:40:00 +0200</pubDate>
-               <description>&lt;p&gt;&lt;em&gt;This is a copy of
-&lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html&quot;&gt;an
-email I posted to the nikita-noark mailing list&lt;/a&gt;.  Please follow up
-there if you would like to discuss this topic.  The background is that
-we are making a free software archive system based on the Norwegian
-&lt;a href=&quot;https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden&quot;&gt;Noark
-5 standard&lt;/a&gt; for government archives.&lt;/em&gt;&lt;/p&gt;
-
-&lt;p&gt;I&#39;ve been wondering a bit lately how trusted timestamps could be
-stored in Noark 5.
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Trusted_timestamping&quot;&gt;Trusted
-timestamps&lt;/a&gt; can be used to verify that some information
-(document/file/checksum/metadata) have not been changed since a
-specific time in the past.  This is useful to verify the integrity of
-the documents in the archive.&lt;/p&gt;
-
-&lt;p&gt;Then it occured to me, perhaps the trusted timestamps could be
-stored as dokument variants (ie dokumentobjekt referered to from
-dokumentbeskrivelse) with the filename set to the hash it is
-stamping?&lt;/p&gt;
-
-&lt;p&gt;Given a &quot;dokumentbeskrivelse&quot; with an associated &quot;dokumentobjekt&quot;,
-a new dokumentobjekt is associated with &quot;dokumentbeskrivelse&quot; with the
-same attributes as the stamped dokumentobjekt except these
-attributes:&lt;/p&gt;
-
-&lt;ul&gt;
-
-&lt;li&gt;format -&gt; &quot;RFC3161&quot;
-&lt;li&gt;mimeType -&gt; &quot;application/timestamp-reply&quot;
-&lt;li&gt;formatDetaljer -&gt; &quot;&amp;lt;source URL for timestamp service&amp;gt;&quot;
-&lt;li&gt;filenavn -&gt; &quot;&amp;lt;sjekksum&amp;gt;.tsr&quot;
-
-&lt;/ul&gt;
-
-&lt;p&gt;This assume a service following
-&lt;a href=&quot;https://tools.ietf.org/html/rfc3161&quot;&gt;IETF RFC 3161&lt;/a&gt; is
-used, which specifiy the given MIME type for replies and the .tsr file
-ending for the content of such trusted timestamp.  As far as I can
-tell from the Noark 5 specifications, it is OK to have several
-variants/renderings of a dokument attached to a given
-dokumentbeskrivelse objekt.  It might be stretching it a bit to make
-some of these variants represent crypto-signatures useful for
-verifying the document integrity instead of representing the dokument
-itself.&lt;/p&gt;
-
-&lt;p&gt;Using the source of the service in formatDetaljer allow several
-timestamping services to be used.  This is useful to spread the risk
-of key compromise over several organisations.  It would only be a
-problem to trust the timestamps if all of the organisations are
-compromised.&lt;/p&gt;
-
-&lt;p&gt;The following oneliner on Linux can be used to generate the tsr
-file.  $input is the path to the file to checksum, and $sha256 is the
-SHA-256 checksum of the file (ie the &quot;&lt;sjekksum&gt;.tsr&quot; value mentioned
-above).&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
-openssl ts -query -data &quot;$inputfile&quot; -cert -sha256 -no_nonce \
-  | curl -s -H &quot;Content-Type: application/timestamp-query&quot; \
-      --data-binary &quot;@-&quot; http://zeitstempel.dfn.de &gt; $sha256.tsr
-&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;To verify the timestamp, you first need to download the public key
-of the trusted timestamp service, for example using this command:&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
-wget -O ca-cert.txt \
-  https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
-&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;Note, the public key should be stored alongside the timestamps in
-the archive to make sure it is also available 100 years from now.  It
-is probably a good idea to standardise how and were to store such
-public keys, to make it easier to find for those trying to verify
-documents 100 or 1000 years from now. :)&lt;/p&gt;
-
-&lt;p&gt;The verification itself is a simple openssl command:&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
-openssl ts -verify -data $inputfile -in $sha256.tsr \
-  -CAfile ca-cert.txt -text
-&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;Is there any reason this approach would not work?  Is it somehow against
-the Noark 5 specification?&lt;/p&gt;
+               <title>Time for an official MIME type for patches?</title>
+               <link>http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
+                <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
+               <description>&lt;p&gt;As part of my involvement in
+&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
+archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
+emails into a test instance of the archive to see how well this would
+go.  I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
+notmuch email database&lt;/a&gt;, all public emails sent to me via
+@lists.debian.org, giving me a set of around 216 000 emails to import.
+In the process, I had a look at the various attachments included in
+these emails, to figure out what to do with attachments, and noticed
+that one of the most common attachment formats do not have
+&lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
+official MIME type&lt;/a&gt; registered with IANA/IETF.  The output from
+diff, ie the input for patch, is on the top 10 list of formats
+included in these emails.  At the moment people seem to use either
+text/x-patch or text/x-diff, but neither is officially registered.  It
+would be better if one official MIME type were registered and used
+everywhere.&lt;/p&gt;
+
+&lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
+up the topic on
+&lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
+media-types mailing list&lt;/a&gt;.  If you are interested in discussion
+which MIME type to use as the official for patch files, or involved in
+making software using a MIME type for patches, perhaps you would like
+to join the discussion?&lt;/p&gt;
+
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Når nynorskoversettelsen svikter til eksamen...</title>
-               <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
-                <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
-               <description>&lt;p&gt;&lt;a href=&quot;http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html&quot;&gt;Aftenposten
-melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
-menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
-like.  Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
-på om den fri oversetterløsningen
-&lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
-jobb enn Utdanningsdirektoratet.  Det kan se slik ut.&lt;/p&gt;
-
-&lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
-
-&lt;blockquote&gt;
-&lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
-rolle og muligheter til å håndtere internasjonale utfordringer, som
-for eksempel flykningekrisen.&lt;/p&gt;
-
-&lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
-på temaet:&lt;/p&gt;
-&lt;ol&gt;
-&lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
-&lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
-&lt;/ol&gt;
-
-&lt;/blockquote&gt;
-
-&lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
-
-&lt;blockquote&gt;
-&lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
-andre aktørar og høve til å handtera internasjonale utfordringar, som
-til dømes *flykningekrisen.&lt;/p&gt;
-
-&lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
-temaet:&lt;/p&gt;
-
-&lt;ol&gt;
-&lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
-&lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
-&lt;/ol&gt;
-
-&lt;/blockquote&gt;
-
-&lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
-ekstra språksjekk.  Men ingen ord er forsvunnet, slik det var i
-oppgaven elevene fikk presentert på eksamen.  Jeg mistenker dog at
-&quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
-&quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
-det er kanskje flisespikking.  Det understreker vel bare at det alltid
-trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
+               <title>Measuring the speaker frequency response using the AUDMES free software GUI - nice free software</title>
+               <link>http://people.skolelinux.org/pere/blog/Measuring_the_speaker_frequency_response_using_the_AUDMES_free_software_GUI___nice_free_software.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Measuring_the_speaker_frequency_response_using_the_AUDMES_free_software_GUI___nice_free_software.html</guid>
+                <pubDate>Mon, 22 Oct 2018 08:40:00 +0200</pubDate>
+               <description>&lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2018-10-22-audmes-measure-speakers.png&quot; align=&quot;right&quot; width=&quot;40%&quot;/&gt;&lt;/p&gt;
+
+&lt;p&gt;My current home stereo is a patchwork of various pieces I got on
+flee markeds over the years.  It is amazing what kind of equipment
+show up there.  I&#39;ve been wondering for a while if it was possible to
+measure how well this equipment is working together, and decided to
+see how far I could get using free software.  After trawling the web I
+came across an article from DIY Audio and Video on
+&lt;a href=&quot;https://www.diyaudioandvideo.com/Tutorial/SpeakerResponseTesting/&quot;&gt;Speaker
+Testing and Analysis&lt;/a&gt; describing how to test speakers, and it listing
+several software options, among them
+&lt;a href=&quot;https://sourceforge.net/projects/audmes/&quot;&gt;AUDio MEasurement
+System (AUDMES)&lt;/a&gt;.  It is the only free software system I could find
+focusing on measuring speakers and audio frequency response.  In the
+process I also found an interesting article from NOVO on
+&lt;a href=&quot;http://novo.press/understanding-speaker-specifications-and-frequency-response/&quot;&gt;Understanding
+Speaker Specifications and Frequency Response&lt;/a&gt; and an article from
+ecoustics on
+&lt;a href=&quot;https://www.ecoustics.com/articles/understanding-speaker-frequency-response/&quot;&gt;Understanding
+Speaker Frequency Response&lt;/a&gt;, with a lot of information on what to
+look for and how to interpret the graphs.  Armed with this knowledge,
+I set out to measure the state of my speakers.&lt;/p&gt;
+
+&lt;p&gt;The first hurdle was that AUDMES hadn&#39;t seen a commit for 10 years
+and did not build with current compilers and libraries.  I got in
+touch with its author, who no longer was spending time on the program
+but gave me write access to the subversion repository on Sourceforge.
+The end result is that now the code build on Linux and is capable of
+saving and loading the collected frequency response data in CSV
+format.  The application is quite nice and flexible, and I was able to
+select the input and output audio interfaces independently.  This made
+it possible to use a USB mixer as the input source, while sending
+output via my laptop headphone connection.  I lacked the hardware and
+cabling to figure out a different way to get independent cabling to
+speakers and microphone.&lt;/p&gt;
+
+&lt;p&gt;Using this setup I could see how a large range of high frequencies
+apparently were not making it out of my speakers.  The picture show
+the frequency response measurement of one of the speakers.  Note the
+frequency lines seem to be slightly misaligned, compared to the CSV
+output from the program.  I can not hear several of these are high
+frequencies, according to measurement from
+&lt;a href=&quot;http://freehearingtestsoftware.com&quot;&gt;Free Hearing Test
+Software&lt;/a&gt;, an freeware system to measure your hearing (still
+looking for a free software alternative), so I do not know if they are
+coming out out the speakers.  I thus do not quite know how to figure
+out if the missing frequencies is a problem with the microphone, the
+amplifier or the speakers, but I managed to rule out the audio card in my
+PC by measuring my Bose noise canceling headset using its own
+microphone.  This setup was able to see the high frequency tones, so
+the problem with my stereo had to be in the amplifier or speakers.&lt;/p&gt;
+
+&lt;p&gt;Anyway, to try to role out one factor I ended up picking up a new
+set of speakers at a flee marked, and these work a lot better than the
+old speakers, so I guess the microphone and amplifier is OK.  If you
+need to measure your own speakers, check out AUDMES.  If more people
+get involved, perhaps the project could become good enough to
+&lt;a href=&quot;https://bugs.debian.org/910876&quot;&gt;include in Debian&lt;/a&gt;?  And if
+you know of some other free software to measure speakers and amplifier
+performance, please let me know.  I am aware of the freeware option
+&lt;a href=&quot;https://www.roomeqwizard.com/&quot;&gt;REW&lt;/a&gt;, but I want something
+that can be developed also when the vendor looses interest.&lt;/p&gt;
+
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Epost inn som arkivformat i Riksarkivarens forskrift?</title>
-               <link>http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html</guid>
-                <pubDate>Thu, 27 Apr 2017 11:30:00 +0200</pubDate>
-               <description>&lt;p&gt;I disse dager, med frist 1. mai, har Riksarkivaren ute en høring på
-sin forskrift.  Som en kan se er det ikke mye tid igjen før fristen
-som går ut på søndag.  Denne forskriften er det som lister opp hvilke
-formater det er greit å arkivere i
-&lt;a href=&quot;http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5&quot;&gt;Noark
-5-løsninger&lt;/a&gt; i Norge.&lt;/p&gt;
-
-&lt;p&gt;Jeg fant høringsdokumentene hos
-&lt;a href=&quot;https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing&quot;&gt;Norsk
-Arkivråd&lt;/a&gt; etter å ha blitt tipset på epostlisten til
-&lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;fri
-programvareprosjektet Nikita Noark5-Core&lt;/a&gt;, som lager et Noark 5
-Tjenestegresesnitt.  Jeg er involvert i Nikita-prosjektet og takket
-være min interesse for tjenestegrensesnittsprosjektet har jeg lest en
-god del Noark 5-relaterte dokumenter, og til min overraskelse oppdaget
-at standard epost ikke er på listen over godkjente formater som kan
-arkiveres.  Høringen med frist søndag er en glimrende mulighet til å
-forsøke å gjøre noe med det.  Jeg holder på med
-&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex&quot;&gt;egen
-høringsuttalelse&lt;/a&gt;, og lurer på om andre er interessert i å støtte
-forslaget om å tillate arkivering av epost som epost i arkivet.&lt;/p&gt;
-
-&lt;p&gt;Er du igang med å skrive egen høringsuttalelse allerede?  I så fall
-kan du jo vurdere å ta med en formulering om epost-lagring. Jeg tror
-ikke det trengs så mye.  Her et kort forslag til tekst:&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;
-
-  &lt;p&gt;Viser til høring sendt ut 2017-02-17 (Riksarkivarens referanse
-  2016/9840 HELHJO), og tillater oss å sende inn noen innspill om
-  revisjon av Forskrift om utfyllende tekniske og arkivfaglige
-  bestemmelser om behandling av offentlige arkiver (Riksarkivarens
-  forskrift).&lt;/p&gt;
+               <title>Web browser integration of VLC with Bittorrent support</title>
+               <link>http://people.skolelinux.org/pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html</guid>
+                <pubDate>Sun, 21 Oct 2018 09:50:00 +0200</pubDate>
+               <description>&lt;p&gt;Bittorrent is as far as I know, currently the most efficient way to
+distribute content on the Internet.  It is used all by all sorts of
+content providers, from national TV stations like
+&lt;a href=&quot;https://www.nrk.no/&quot;&gt;NRK&lt;/a&gt;, Linux distributors like
+&lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; and
+&lt;a href=&quot;https://www.ubuntu.com/&quot;&gt;Ubuntu&lt;/a&gt;, and of course the
+&lt;a href=&quot;https://archive.org/&quot;&gt;Internet archive&lt;/A&gt;.
+
+&lt;p&gt;Almost a month ago
+&lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;a new
+package adding Bittorrent support to VLC&lt;/a&gt; became available in
+Debian testing and unstable.  To test it, simply install it like
+this:&lt;/p&gt;
+
+&lt;p&gt;&lt;pre&gt;
+apt install vlc-plugin-bittorrent
+&lt;/pre&gt;&lt;/p&gt;
+
+&lt;p&gt;Since the plugin was made available for the first time in Debian,
+several improvements have been made to it.  In version 2.2-4, now
+available in both testing and unstable, a desktop file is provided to
+teach browsers to start VLC when the user click on torrent files or
+magnet links.  The last part is thanks to me finally understanding
+what the strange x-scheme-handler style MIME types in desktop files
+are used for.  By adding x-scheme-handler/magnet to the MimeType entry
+in the desktop file, at least the browsers Firefox and Chromium will
+suggest to start VLC when selecting a magnet URI on a web page.  The
+end result is that now, with the plugin installed in Buster and Sid,
+one can visit any
+&lt;a href=&quot;https://archive.org/details/CopyingIsNotTheft1080p&quot;&gt;Internet
+Archive page with movies&lt;/a&gt; using a web browser and click on the
+torrent link to start streaming the movie.&lt;/p&gt;
+
+&lt;p&gt;Note, there is still some misfeatures in the plugin.  One is the
+fact that it will hang and
+&lt;a href=&quot;https://github.com/johang/vlc-bittorrent/issues/13&quot;&gt;block VLC
+from exiting until the torrent streaming starts&lt;/a&gt;.  Another is the
+fact that it
+&lt;a href=&quot;https://github.com/johang/vlc-bittorrent/issues/9&quot;&gt;will pick
+and play a random file in a multi file torrent&lt;/a&gt;.  This is not
+always the video file you want.  Combined with the first it can be a
+bit hard to get the video streaming going.  But when it work, it seem
+to do a good job.&lt;/p&gt;
+
+&lt;p&gt;For the Debian packaging, I would love to find a good way to test
+if the plugin work with VLC using autopkgtest.  I tried, but do not
+know enough of the inner workings of VLC to get it working.  For now
+the autopkgtest script is only checking if the .so file was
+successfully loaded by VLC.  If you have any suggestions, please
+submit a patch to the Debian bug tracking system.&lt;/p&gt;
+
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+</description>
+       </item>
+       
+       <item>
+               <title>Release 0.2 of free software archive system Nikita announced</title>
+               <link>http://people.skolelinux.org/pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html</guid>
+                <pubDate>Thu, 18 Oct 2018 14:40:00 +0200</pubDate>
+               <description>&lt;p&gt;This morning, the new release of the
+&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;Nikita
+Noark 5 core project&lt;/a&gt; was
+&lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2018-October/000406.html&quot;&gt;announced
+on the project mailing list&lt;/a&gt;.  The free software solution is an
+implementation of the Norwegian archive standard Noark 5 used by
+government offices in Norway.  These were the changes in version 0.2
+since version 0.1.1 (from NEWS.md):

 
 

-  &lt;p&gt;Svært mye av vår kommuikasjon foregår i dag på e-post.  Vi
-  foreslår derfor at Internett-e-post, slik det er beskrevet i IETF
-  RFC 5322,
-  &lt;a href=&quot;https://tools.ietf.org/html/rfc5322&quot;&gt;https://tools.ietf.org/html/rfc5322&lt;/a&gt;. bør
-  inn som godkjent dokumentformat.  Vi foreslår at forskriftens
-  oversikt over godkjente dokumentformater ved innlevering i § 5-16
-  endres til å ta med Internett-e-post.&lt;/p&gt;
+&lt;ul&gt;
+  &lt;li&gt;Fix typos in REL names&lt;/li&gt;
+  &lt;li&gt;Tidy up error message reporting&lt;/li&gt;
+  &lt;li&gt;Fix issue where we used Integer.valueOf(), not Integer.getInteger()&lt;/li&gt;
+  &lt;li&gt;Change some String handling to StringBuffer&lt;/li&gt;
+  &lt;li&gt;Fix error reporting&lt;/li&gt;
+  &lt;li&gt;Code tidy-up&lt;/li&gt;
+  &lt;li&gt;Fix issue using static non-synchronized SimpleDateFormat to avoid 
+      race conditions&lt;/li&gt;
+  &lt;li&gt;Fix problem where deserialisers were treating integers as strings&lt;/li&gt;
+  &lt;li&gt;Update methods to make them null-safe&lt;/li&gt;
+  &lt;li&gt;Fix many issues reported by coverity&lt;/li&gt;
+  &lt;li&gt;Improve equals(), compareTo() and hash() in domain model&lt;/li&gt;
+  &lt;li&gt;Improvements to the domain model for metadata classes&lt;/li&gt;
+  &lt;li&gt;Fix CORS issues when downloading document&lt;/li&gt;
+  &lt;li&gt;Implementation of case-handling with registryEntry and document upload&lt;/li&gt;
+  &lt;li&gt;Better support in Javascript for OPTIONS&lt;/li&gt;
+  &lt;li&gt;Adding concept description of mail integration&lt;/li&gt;
+  &lt;li&gt;Improve setting of default values for GET on ny-journalpost&lt;/li&gt;
+  &lt;li&gt;Better handling of required values during deserialisation &lt;/li&gt;
+  &lt;li&gt;Changed tilknyttetDato (M620) from date to dateTime&lt;/li&gt;
+  &lt;li&gt;Corrected some opprettetDato (M600) (de)serialisation errors.&lt;/li&gt;
+  &lt;li&gt;Improve parse error reporting.&lt;/li&gt;
+  &lt;li&gt;Started on OData search and filtering.&lt;/li&gt;
+  &lt;li&gt;Added Contributor Covenant Code of Conduct to project.&lt;/li&gt;
+  &lt;li&gt;Moved repository and project from Github to Gitlab.&lt;/li&gt;
+  &lt;li&gt;Restructured repository, moved code into src/ and web/.&lt;/li&gt;
+  &lt;li&gt;Updated code to use Spring Boot version 2.&lt;/li&gt;
+  &lt;li&gt;Added support for OAuth2 authentication.&lt;/li&gt;
+  &lt;li&gt;Fixed several bugs discovered by Coverity.&lt;/li&gt;
+  &lt;li&gt;Corrected handling of date/datetime fields.&lt;/li&gt;
+  &lt;li&gt;Improved error reporting when rejecting during deserializatoin.&lt;/li&gt;
+  &lt;li&gt;Adjusted default values provided for ny-arkivdel, ny-mappe,
+   ny-saksmappe, ny-journalpost and ny-dokumentbeskrivelse.&lt;/li&gt;
+  &lt;li&gt;Several fixes for korrespondansepart*.&lt;/li&gt;
+  &lt;li&gt;Updated web GUI:
+     &lt;ul&gt;
+       &lt;li&gt;Now handle both file upload and download.&lt;/li&gt;
+       &lt;li&gt;Uses new OAuth2 authentication for login.&lt;/li&gt;
+       &lt;li&gt;Forms now fetches default values from API using GET.&lt;/li&gt;
+       &lt;li&gt;Added RFC 822 (email), TIFF and JPEG to list of possible file formats.&lt;/li&gt;
+     &lt;/ul&gt;&lt;/li&gt;
+&lt;/ul&gt;

 
 

-&lt;/blockquote&gt;&lt;/p&gt;
+&lt;p&gt;The changes and improvements are extensive.  Running diffstat on
+the changes between git tab 0.1.1 and 0.2 show 1098 files changed,
+108666 insertions(+), 54066 deletions(-).&lt;/p&gt;

 
 

-&lt;p&gt;Som del av arbeidet med tjenestegrensesnitt har vi testet hvordan
-epost kan lagres i en Noark 5-struktur, og holder på å skrive et
-forslag om hvordan dette kan gjøres som vil bli sendt over til
-arkivverket så snart det er ferdig.  De som er interesserte kan
-&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md&quot;&gt;følge
-fremdriften på web&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;If free and open standardized archiving API sound interesting to
+you, please contact us on IRC
+(&lt;a href=&quot;irc://irc.freenode.net/%23nikita&quot;&gt;#nikita on
+irc.freenode.net&lt;/a&gt;) or email
+(&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
+mailing list&lt;/a&gt;).&lt;/p&gt;

 
 

-&lt;p&gt;Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev
-  &lt;a href=&quot;https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml&quot;&gt;sendt
-  inn av foreningen NUUG&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Offentlig elektronisk postjournal blokkerer tilgang for utvalgte webklienter</title>
-               <link>http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html</guid>
-                <pubDate>Thu, 20 Apr 2017 13:00:00 +0200</pubDate>
-               <description>&lt;p&gt;Jeg oppdaget i dag at &lt;a href=&quot;https://www.oep.no/&quot;&gt;nettstedet som
-publiserer offentlige postjournaler fra statlige etater&lt;/a&gt;, OEP, har
-begynt å blokkerer enkelte typer webklienter fra å få tilgang.  Vet
-ikke hvor mange det gjelder, men det gjelder i hvert fall libwww-perl
-og curl.  For å teste selv, kjør følgende:&lt;/p&gt;
-
-&lt;blockquote&gt;&lt;pre&gt;
-% curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2&gt;&amp;1 |grep &#39;&lt; HTTP&#39;
-&lt; HTTP/1.1 404 Not Found
-% curl -v -s --header &#39;User-Agent:Opera/12.0&#39; https://www.oep.no/pub/report.xhtml?reportId=3 2&gt;&amp;1 |grep &#39;&lt; HTTP&#39;
-&lt; HTTP/1.1 200 OK
-%
-&lt;/pre&gt;&lt;/blockquote&gt;
-
-&lt;p&gt;Her kan en se at tjenesten gir «404 Not Found» for curl i
-standardoppsettet, mens den gir «200 OK» hvis curl hevder å være Opera
-versjon 12.0.  Offentlig elektronisk postjournal startet blokkeringen
-2017-03-02.&lt;/p&gt;
-
-&lt;p&gt;Blokkeringen vil gjøre det litt vanskeligere å maskinelt hente
-informasjon fra oep.no.  Kan blokkeringen være gjort for å hindre
-automatisert innsamling av informasjon fra OEP, slik Pressens
-Offentlighetsutvalg gjorde for å dokumentere hvordan departementene
-hindrer innsyn i
-&lt;a href=&quot;http://presse.no/dette-mener-np/undergraver-offentlighetsloven/&quot;&gt;rapporten
-«Slik hindrer departementer innsyn» som ble publiserte i januar
-2017&lt;/a&gt;.  Det virker usannsynlig, da det jo er trivielt å bytte
-User-Agent til noe nytt.&lt;/p&gt;
-
-&lt;p&gt;Finnes det juridisk grunnlag for det offentlige å diskriminere
-webklienter slik det gjøres her?  Der tilgang gis eller ikke alt etter
-hva klienten sier at den heter?  Da OEP eies av DIFI og driftes av
-Basefarm, finnes det kanskje noen dokumenter sendt mellom disse to
-aktørene man kan be om innsyn i for å forstå hva som har skjedd.  Men
-&lt;a href=&quot;https://www.oep.no/search/result.html?period=dateRange&amp;fromDate=01.01.2016&amp;toDate=01.04.2017&amp;dateType=documentDate&amp;caseDescription=&amp;descType=both&amp;caseNumber=&amp;documentNumber=&amp;sender=basefarm&amp;senderType=both&amp;documentType=all&amp;legalAuthority=&amp;archiveCode=&amp;list2=196&amp;searchType=advanced&amp;Search=Search+in+records&quot;&gt;postjournalen
-til DIFI viser kun to dokumenter&lt;/a&gt; det siste året mellom DIFI og
-Basefarm.
-&lt;a href=&quot;https://www.mimesbronn.no/request/blokkering_av_tilgang_til_oep_fo&quot;&gt;Mimes brønn neste&lt;/a&gt;,
-tenker jeg.&lt;/p&gt;
+               <title>Fetching trusted timestamps using the rfc3161ng python module</title>
+               <link>http://people.skolelinux.org/pere/blog/Fetching_trusted_timestamps_using_the_rfc3161ng_python_module.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fetching_trusted_timestamps_using_the_rfc3161ng_python_module.html</guid>
+                <pubDate>Mon, 8 Oct 2018 12:30:00 +0200</pubDate>
+               <description>&lt;p&gt;I have  earlier covered the basics of trusted timestamping using the
+&#39;openssl ts&#39; client.  See blog post for
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Public_Trusted_Timestamping_services_for_everyone.html&quot;&gt;2014&lt;/a&gt;,
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/syslog_trusted_timestamp___chain_of_trusted_timestamps_for_your_syslog.html&quot;&gt;2016&lt;/a&gt;
+and
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html&quot;&gt;2017&lt;/a&gt;
+for those stories.  But some times I want to integrate the timestamping
+in other code, and recently I needed to integrate it into Python.
+After searching a bit, I found
+&lt;a href=&quot;https://dev.entrouvert.org/projects/python-rfc3161&quot;&gt;the
+rfc3161 library&lt;/a&gt; which seemed like a good fit, but I soon
+discovered it only worked for python version 2, and I needed something
+that work with python version 3.  Luckily I next came across
+&lt;a href=&quot;https://github.com/trbs/rfc3161ng/&quot;&gt;the rfc3161ng library&lt;/a&gt;,
+a fork of the original rfc3161 library.  Not only is it working with
+python 3, it have fixed a few of the bugs in the original library, and
+it has an active maintainer.  I decided to wrap it up and make it
+&lt;a href=&quot;https://tracker.debian.org/pkg/python-rfc3161ng&quot;&gt;available in
+Debian&lt;/a&gt;, and a few days ago it entered Debian unstable and testing.&lt;/p&gt;
+
+&lt;p&gt;Using the library is fairly straight forward.  The only slightly
+problematic step is to fetch the required certificates to verify the
+timestamp.  For some services it is straight forward, while for others
+I have not yet figured out how to do it.  Here is a small standalone
+code example based on of the integration tests in the library code:&lt;/p&gt;
+
+&lt;pre&gt;
+#!/usr/bin/python3
+
+&quot;&quot;&quot;
+
+Python 3 script demonstrating how to use the rfc3161ng module to
+get trusted timestamps.
+
+The license of this code is the same as the license of the rfc3161ng
+library, ie MIT/BSD.
+
+&quot;&quot;&quot;
+
+import os
+import pyasn1.codec.der
+import rfc3161ng
+import subprocess
+import tempfile
+import urllib.request
+
+def store(f, data):
+    f.write(data)
+    f.flush()
+    f.seek(0)
+
+def fetch(url, f=None):
+    response = urllib.request.urlopen(url)
+    data = response.read()
+    if f:
+        store(f, data)
+    return data
+
+def main():
+    with tempfile.NamedTemporaryFile() as cert_f,\
+        tempfile.NamedTemporaryFile() as ca_f,\
+        tempfile.NamedTemporaryFile() as msg_f,\
+        tempfile.NamedTemporaryFile() as tsr_f:
+
+        # First fetch certificates used by service
+        certificate_data = fetch(&#39;https://freetsa.org/files/tsa.crt&#39;, cert_f)
+        ca_data_data = fetch(&#39;https://freetsa.org/files/cacert.pem&#39;, ca_f)
+
+        # Then timestamp the message
+        timestamper = \
+            rfc3161ng.RemoteTimestamper(&#39;http://freetsa.org/tsr&#39;,
+                                        certificate=certificate_data)
+        data = b&quot;Python forever!\n&quot;
+        tsr = timestamper(data=data, return_tsr=True)
+
+        # Finally, convert message and response to something &#39;openssl ts&#39; can verify
+        store(msg_f, data)
+        store(tsr_f, pyasn1.codec.der.encoder.encode(tsr))
+        args = [&quot;openssl&quot;, &quot;ts&quot;, &quot;-verify&quot;,
+                &quot;-data&quot;, msg_f.name,
+               &quot;-in&quot;, tsr_f.name,
+               &quot;-CAfile&quot;, ca_f.name,
+                &quot;-untrusted&quot;, cert_f.name]
+        subprocess.check_call(args)
+
+if &#39;__main__&#39; == __name__:
+   main()
+&lt;/pre&gt;
+
+&lt;p&gt;The code fetches the required certificates, store them as temporary
+files, timestamp a simple message, store the message and timestamp to
+disk and ask &#39;openssl ts&#39; to verify the timestamp.  A timestamp is
+around 1.5 kiB in size, and should be fairly easy to store for future
+use.&lt;/p&gt;
+
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Free software archive system Nikita now able to store documents</title>
-               <link>http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html</guid>
-                <pubDate>Sun, 19 Mar 2017 08:00:00 +0100</pubDate>
-               <description>&lt;p&gt;The &lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;Nikita
-Noark 5 core project&lt;/a&gt; is implementing the Norwegian standard for
-keeping an electronic archive of government documents.
-&lt;a href=&quot;http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version&quot;&gt;The
-Noark 5 standard&lt;/a&gt; document the requirement for data systems used by
-the archives in the Norwegian government, and the Noark 5 web interface
-specification document a REST web service for storing, searching and
-retrieving documents and metadata in such archive.  I&#39;ve been involved
-in the project since a few weeks before Christmas, when the Norwegian
-Unix User Group
-&lt;a href=&quot;https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml&quot;&gt;announced
-it supported the project&lt;/a&gt;.  I believe this is an important project,
-and hope it can make it possible for the government archives in the
-future to use free software to keep the archives we citizens depend
-on.  But as I do not hold such archive myself, personally my first use
-case is to store and analyse public mail journal metadata published
-from the government.  I find it useful to have a clear use case in
-mind when developing, to make sure the system scratches one of my
-itches.&lt;/p&gt;
-
-&lt;p&gt;If you would like to help make sure there is a free software
-alternatives for the archives, please join our IRC channel
-(&lt;a href=&quot;irc://irc.freenode.net/%23nikita&quot;&quot;&gt;#nikita on
-irc.freenode.net&lt;/a&gt;) and
-&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;the
-project mailing list&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;When I got involved, the web service could store metadata about
-documents.  But a few weeks ago, a new milestone was reached when it
-became possible to store full text documents too.  Yesterday, I
-completed an implementation of a command line tool
-&lt;tt&gt;archive-pdf&lt;/tt&gt; to upload a PDF file to the archive using this
-API.  The tool is very simple at the moment, and find existing
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Fonds&quot;&gt;fonds&lt;/a&gt;, series and
-files while asking the user to select which one to use if more than
-one exist.  Once a file is identified, the PDF is associated with the
-file and uploaded, using the title extracted from the PDF itself.  The
-process is fairly similar to visiting the archive, opening a cabinet,
-locating a file and storing a piece of paper in the archive.  Here is
-a test run directly after populating the database with test data using
-our API tester:&lt;/p&gt;
+               <title>Automatic Google Drive sync using grive in Debian</title>
+               <link>http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
+                <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
+               <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian.  To try to
+rescue the remains, I helped set up automatic sync with Google Drive.
+I did not find any sensible Debian package handling this
+automatically, so I rebuild the grive2 source from
+&lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
+task and added a autostart desktop entry and a small shell script to
+run in the background while the user is logged in to do the sync.
+Here is a sketch of the setup for future reference.&lt;/p&gt;
+
+&lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
+ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user.  Next, I
+created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
+to start the sync when the user log in:&lt;/p&gt;

 
 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 
 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;

-~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
-using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
-using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
-
- 0 - Title of the test case file created 2017-03-18T23:49:32.103446
- 1 - Title of the test file created 2017-03-18T23:49:32.103446
-Select which mappe you want (or search term): 0
-Uploading mangelmelding/mangler.pdf
-  PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
-  File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
-~/src//noark5-tester$
+[Desktop Entry]
+Name=Google drive autosync
+Type=Application
+Exec=/home/user/bin/grive-sync

 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 
 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 

-&lt;p&gt;You can see here how the fonds (arkiv) and serie (arkivdel) only had
-one option, while the user need to choose which file (mappe) to use
-among the two created by the API tester.  The &lt;tt&gt;archive-pdf&lt;/tt&gt;
-tool can be found in the git repository for the API tester.&lt;/p&gt;
-
-&lt;p&gt;In the project, I have been mostly working on
-&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester&quot;&gt;the API
-tester&lt;/a&gt; so far, while getting to know the code base.  The API
-tester currently use
-&lt;a href=&quot;https://en.wikipedia.org/wiki/HATEOAS&quot;&gt;the HATEOAS links&lt;/a&gt;
-to traverse the entire exposed service API and verify that the exposed
-operations and objects match the specification, as well as trying to
-create objects holding metadata and uploading a simple XML file to
-store.  The tester has proved very useful for finding flaws in our
-implementation, as well as flaws in the reference site and the
-specification.&lt;/p&gt;
-
-&lt;p&gt;The test document I uploaded is a summary of all the specification
-defects we have collected so far while implementing the web service.
-There are several unclear and conflicting parts of the specification,
-and we have
-&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding&quot;&gt;started
-writing down&lt;/a&gt; the questions we get from implementing it.  We use a
-format inspired by how &lt;a href=&quot;http://www.opengroup.org/austin/&quot;&gt;The
-Austin Group&lt;/a&gt; collect defect reports for the POSIX standard with
-&lt;a href=&quot;http://www.opengroup.org/austin/mantis.html&quot;&gt;their
-instructions for the MANTIS defect tracker system&lt;/a&gt;, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a &lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/mangelmelding/sendt/2017-03-15-mangel-prosess.md&quot;&gt;request for a procedure for submitting defect reports&lt;/a&gt; :).
-
-&lt;p&gt;The Nikita project is implemented using Java and Spring, and is
-fairly easy to get up and running using Docker containers for those
-that want to test the current code base.  The API tester is
-implemented in Python.&lt;/p&gt;
+&lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
+~/googledrive/ with the files in Google Drive.&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+#!/bin/sh
+set -e
+cd ~/
+cleanup() {
+    if [ &quot;$syncpid&quot; ] ; then
+        kill $syncpid
+    fi
+}
+trap cleanup EXIT INT QUIT
+/usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
+syncpdi=$!
+while true; do
+    if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
+        echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
+        exit 1
+    fi
+    if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
+        /usr/lib/grive/grive-sync.sh sync googledrive
+    fi
+    sleep 300
+done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Feel free to use the setup if you want.  It can be assumed to be
+GNU GPL v2 licensed (or any later version, at your leisure), but I
+doubt this code is possible to claim copyright on.&lt;/p&gt;
+
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Detecting NFS hangs on Linux without hanging yourself...</title>
-               <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
-                <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
-               <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
-computers at the time, I often needed a way to detect if the machine
-was experiencing NFS hang.  If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
-file or directory affected by the hang, the process (and possibly the
-shell) will hang too.  So you want to be able to detect this without
-risking the detection process getting stuck too.  It has not been
-obvious how to do this.  When the hang has lasted a while, it is
-possible to find messages like these in dmesg:&lt;/p&gt;
+               <title>Valutakrambod - A python and bitcoin love story</title>
+               <link>http://people.skolelinux.org/pere/blog/Valutakrambod___A_python_and_bitcoin_love_story.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Valutakrambod___A_python_and_bitcoin_love_story.html</guid>
+                <pubDate>Sat, 29 Sep 2018 22:20:00 +0200</pubDate>
+               <description>&lt;p&gt;It would come as no surprise to anyone that I am interested in
+bitcoins and virtual currencies.  I&#39;ve been keeping an eye on virtual
+currencies for many years, and it is part of the reason a few months
+ago, I started writing a python library for collecting currency
+exchange rates and trade on virtual currency exchanges.  I decided to
+name the end result valutakrambod, which perhaps can be translated to
+small currency shop.&lt;/p&gt;
+
+&lt;p&gt;The library uses the tornado python library to handle HTTP and
+websocket connections, and provide a asynchronous system for
+connecting to and tracking several services.  The code is available
+from
+&lt;a href=&quot;http://github.com/petterreinholdtsen/valutakrambod&quot;&gt;github&lt;/a&gt;.&lt;/p&gt;
+
+&lt;/p&gt;There are two example clients of the library.  One is very simple and
+list every updated buy/sell price received from the various services.
+This code is started by running bin/btc-rates and call the client code
+in valutakrambod/client.py.  The simple client look like this:&lt;/p&gt;

 
 

-&lt;p&gt;&lt;blockquote&gt;
-nfs: server nfsserver not responding, still trying
-&lt;br&gt;nfs: server nfsserver OK
-&lt;/blockquote&gt;&lt;/p&gt;
-  
-&lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
-be sure looking in dmesg is going to work.  If there are lots of other
-messages in dmesg the lines might have rotated out of site before they
-are noticed.&lt;/p&gt;
-
-&lt;p&gt;While reading through the nfs client implementation in linux kernel
-code, I came across some statistics that seem to give a way to detect
-it.  The om_timeouts sunrpc value in the kernel will increase every
-time the above log entry is inserted into dmesg.  And after digging a
-bit further, I discovered that this value show up in
-/proc/self/mountstats on Linux.&lt;/p&gt;
-
-&lt;p&gt;The mountstats content seem to be shared between files using the
-same file system context, so it is enough to check one of the
-mountstats files to get the state of the mount point for the machine.
-I assume this will not show lazy umounted NFS points, nor NFS mount
-points in a different process context (ie with a different filesystem
-view), but that does not worry me.&lt;/p&gt;
-
-&lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+import functools
+import tornado.ioloop
+import valutakrambod
+class SimpleClient(object):
+    def __init__(self):
+        self.services = []
+        self.streams = []
+        pass
+    def newdata(self, service, pair, changed):
+        print(&quot;%-15s %s-%s: %8.3f %8.3f&quot; % (
+            service.servicename(),
+            pair[0],
+            pair[1],
+            service.rates[pair][&#39;ask&#39;],
+            service.rates[pair][&#39;bid&#39;])
+        )
+    async def refresh(self, service):
+        await service.fetchRates(service.wantedpairs)
+    def run(self):
+        self.ioloop = tornado.ioloop.IOLoop.current()
+        self.services = valutakrambod.service.knownServices()
+        for e in self.services:
+            service = e()
+            service.subscribe(self.newdata)
+            stream = service.websocket()
+            if stream:
+                self.streams.append(stream)
+            else:
+                # Fetch information from non-streaming services immediately
+                self.ioloop.call_later(len(self.services),
+                                       functools.partial(self.refresh, service))
+                # as well as regularly
+                service.periodicUpdate(60)
+        for stream in self.streams:
+            stream.connect()
+        try:
+            self.ioloop.start()
+        except KeyboardInterrupt:
+            print(&quot;Interrupted by keyboard, closing all connections.&quot;)
+            pass
+        for stream in self.streams:
+            stream.close()
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;The library client loops over all known &quot;public&quot; services,
+initialises it, subscribes to any updates from the service, checks and
+activates websocket streaming if the service provide it, and if no
+streaming is supported, fetches information from the service and sets
+up a periodic update every 60 seconds.  The output from this client
+can look like this:&lt;/p&gt;

 
 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 
 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;

-[...]
-device /dev/mapper/Debian-var mounted on /var with fstype ext3
-device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
-        opts:   rw,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,soft,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.240.3.145,mountvers=3,mountport=4048,mountproto=udp,local_lock=all
-        age:    7863311
-        caps:   caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
-        sec:    flavor=1,pseudoflavor=1
-        events: 61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0 
-        bytes:  166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809 
-        RPC iostats version: 1.0  p/v: 100003/3 (nfs)
-        xprt:   tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
-        per-op statistics
-                NULL: 0 0 0 0 0 0 0 0
-             GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
-             SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
-              LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
-              ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
-            READLINK: 125 125 0 20472 18620 0 1112 1118
-                READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
-               WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
-              CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
-               MKDIR: 3680 3680 0 773980 993920 26 23990 24245
-             SYMLINK: 903 903 0 233428 245488 6 5865 5917
-               MKNOD: 80 80 0 20148 21760 0 299 304
-              REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
-               RMDIR: 3367 3367 0 645112 484848 22 5782 6002
-              RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
-                LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
-             READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
-         READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
-              FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
-              FSINFO: 2 2 0 232 328 0 1 1
-            PATHCONF: 1 1 0 116 140 0 0 0
-              COMMIT: 0 0 0 0 0 0 0 0
-
-device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
-[...]
+Bl3p            BTC-EUR: 5687.110 5653.690
+Bl3p            BTC-EUR: 5687.110 5653.690
+Bl3p            BTC-EUR: 5687.110 5653.690
+Hitbtc          BTC-USD: 6594.560 6593.690
+Hitbtc          BTC-USD: 6594.560 6593.690
+Bl3p            BTC-EUR: 5687.110 5653.690
+Hitbtc          BTC-USD: 6594.570 6593.690
+Bitstamp        EUR-USD:    1.159    1.154
+Hitbtc          BTC-USD: 6594.570 6593.690
+Hitbtc          BTC-USD: 6594.580 6593.690
+Hitbtc          BTC-USD: 6594.580 6593.690
+Hitbtc          BTC-USD: 6594.580 6593.690
+Bl3p            BTC-EUR: 5687.110 5653.690
+Paymium         BTC-EUR: 5680.000 5620.240

 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 
 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 

-&lt;p&gt;The key number to look at is the third number in the per-op list.
-It is the number of NFS timeouts experiences per file system
-operation.  Here 22 write timeouts and 5 access timeouts.  If these
-numbers are increasing, I believe the machine is experiencing NFS
-hang.  Unfortunately the timeout value do not start to increase right
-away.  The NFS operations need to time out first, and this can take a
-while.  The exact timeout value depend on the setup.  For example the
-defaults for TCP and UDP mount points are quite different, and the
-timeout value is affected by the soft, hard, timeo and retrans NFS
-mount options.&lt;/p&gt;
-
-&lt;p&gt;The only way I have been able to get working on Debian and RedHat
-Enterprise Linux for getting the timeout count is to peek in /proc/.
-But according to
-&lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
-10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
-command can be used to get these timeout values.  But this do not work
-on Linux, as far as I can tell.  I
-&lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
-but have not seen any replies yet.&lt;/p&gt;
-
-&lt;p&gt;Is there a better way to figure out if a Linux NFS client is
-experiencing NFS hangs?  Is there a way to detect which processes are
-affected?  Is there a way to get the NFS mount going quickly once the
-network problem causing the NFS hang has been cleared?  I would very
-much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
-</description>
-       </item>
-       
-       <item>
-               <title>How does it feel to be wiretapped, when you should be doing the wiretapping...</title>
-               <link>http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html</guid>
-                <pubDate>Wed, 8 Mar 2017 11:50:00 +0100</pubDate>
-               <description>&lt;p&gt;So the new president in the United States of America claim to be
-surprised to discover that he was wiretapped during the election
-before he was elected president.  He even claim this must be illegal.
-Well, doh, if it is one thing the confirmations from Snowden
-documented, it is that the entire population in USA is wiretapped, one
-way or another.  Of course the president candidates were wiretapped,
-alongside the senators, judges and the rest of the people in USA.&lt;/p&gt;
-
-&lt;p&gt;Next, the Federal Bureau of Investigation ask the Department of
-Justice to go public rejecting the claims that Donald Trump was
-wiretapped illegally.  I fail to see the relevance, given that I am
-sure the surveillance industry in USA believe they have all the legal
-backing they need to conduct mass surveillance on the entire
-world.&lt;/p&gt;
-
-&lt;p&gt;There is even the director of the FBI stating that he never saw an
-order requesting wiretapping of Donald Trump.  That is not very
-surprising, given how the FISA court work, with all its activity being
-secret.  Perhaps he only heard about it?&lt;/p&gt;
-
-&lt;p&gt;What I find most sad in this story is how Norwegian journalists
-present it.  In a news reports the other day in the radio from the
-Norwegian National broadcasting Company (NRK), I heard the journalist
-claim that &#39;the FBI denies any wiretapping&#39;, while the reality is that
-&#39;the FBI denies any illegal wiretapping&#39;.  There is a fundamental and
-important difference, and it make me sad that the journalists are
-unable to grasp it.&lt;/p&gt;
-
-&lt;p&gt;&lt;strong&gt;Update 2017-03-13:&lt;/strong&gt; Look like
-&lt;a href=&quot;https://theintercept.com/2017/03/13/rand-paul-is-right-nsa-routinely-monitors-americans-communications-without-warrants/&quot;&gt;The
-Intercept report that US Senator Rand Paul confirm what I state above&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;The exchange order book is tracked in addition to the best buy/sell
+price, for those that need to know the details.&lt;/p&gt;
+
+&lt;p&gt;The other example client is focusing on providing a curses view
+with updated buy/sell prices as soon as they are received from the
+services.  This code is located in bin/btc-rates-curses and activated
+by using the &#39;-c&#39; argument.  Without the argument the &quot;curses&quot; output
+is printed without using curses, which is useful for debugging.  The
+curses view look like this:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+           Name Pair   Bid         Ask         Spr    Ftcd    Age
+ BitcoinsNorway BTCEUR   5591.8400   5711.0800   2.1%   16    nan     60
+       Bitfinex BTCEUR   5671.0000   5671.2000   0.0%   16     22     59
+        Bitmynt BTCEUR   5580.8000   5807.5200   3.9%   16     41     60
+         Bitpay BTCEUR   5663.2700         nan   nan%   15    nan     60
+       Bitstamp BTCEUR   5664.8400   5676.5300   0.2%    0      1      1
+           Bl3p BTCEUR   5653.6900   5684.9400   0.5%    0    nan     19
+       Coinbase BTCEUR   5600.8200   5714.9000   2.0%   15    nan    nan
+         Kraken BTCEUR   5670.1000   5670.2000   0.0%   14     17     60
+        Paymium BTCEUR   5620.0600   5680.0000   1.1%    1   7515    nan
+ BitcoinsNorway BTCNOK  52898.9700  54034.6100   2.1%   16    nan     60
+        Bitmynt BTCNOK  52960.3200  54031.1900   2.0%   16     41     60
+         Bitpay BTCNOK  53477.7833         nan   nan%   16    nan     60
+       Coinbase BTCNOK  52990.3500  54063.0600   2.0%   15    nan    nan
+        MiraiEx BTCNOK  52856.5300  54100.6000   2.3%   16    nan    nan
+ BitcoinsNorway BTCUSD   6495.5300   6631.5400   2.1%   16    nan     60
+       Bitfinex BTCUSD   6590.6000   6590.7000   0.0%   16     23     57
+         Bitpay BTCUSD   6564.1300         nan   nan%   15    nan     60
+       Bitstamp BTCUSD   6561.1400   6565.6200   0.1%    0      2      1
+       Coinbase BTCUSD   6504.0600   6635.9700   2.0%   14    nan    117
+         Gemini BTCUSD   6567.1300   6573.0700   0.1%   16     89    nan
+         Hitbtc+BTCUSD   6592.6200   6594.2100   0.0%    0      0      0
+         Kraken BTCUSD   6565.2000   6570.9000   0.1%   15     17     58
+  Exchangerates EURNOK      9.4665      9.4665   0.0%   16 107789    nan
+     Norgesbank EURNOK      9.4665      9.4665   0.0%   16 107789    nan
+       Bitstamp EURUSD      1.1537      1.1593   0.5%    4      5      1
+  Exchangerates EURUSD      1.1576      1.1576   0.0%   16 107789    nan
+ BitcoinsNorway LTCEUR      1.0000     49.0000  98.0%   16    nan    nan
+ BitcoinsNorway LTCNOK    492.4800    503.7500   2.2%   16    nan     60
+ BitcoinsNorway LTCUSD      1.0221     49.0000  97.9%   15    nan    nan
+     Norgesbank USDNOK      8.1777      8.1777   0.0%   16 107789    nan
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;The code for this client is too complex for a simple blog post, so
+you will have to check out the git repository to figure out how it
+work.  What I can tell is how the three last numbers on each line
+should be interpreted.  The first is how many seconds ago information
+was received from the service.  The second is how long ago, according
+to the service, the provided information was updated.  The last is an
+estimate on how often the buy/sell values change.&lt;/p&gt;
+
+&lt;p&gt;If you find this library useful, or would like to improve it, I
+would love to hear from you.  Note that for some of the services I&#39;ve
+implemented a trading API.  It might be the topic of a future blog
+post.&lt;/p&gt;
+
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;

 </description>
        </item>
        
 </description>
        </item>