New post on the municipality map.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index aa7fe2eccbbd9181cf26b2734a8f31f69a8e0689..770eae38cbc1784222dc81e78937a8bf5929108e 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -7,229 +7,252 @@
                 <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>When terms and policy turn users away</title>
-               <link>http://people.skolelinux.org/pere/blog/When_terms_and_policy_turn_users_away.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/When_terms_and_policy_turn_users_away.html</guid>
-                <pubDate>Sat, 7 Dec 2019 21:15:00 +0100</pubDate>
-               <description>&lt;p&gt;When asked to accept terms of use and privacy policies that state
-it will to remove rights I otherwise had or accept unreasonable terms
-undermining my privacy, I choose away the service.  I simply do not
-have the conscience to accept terms I have no indention of upholding.
-But how are the system and service providers to know how many people
-they scared away?  Normally I just quietly walk away.  But today, I
-tried a new approach.  I sent the following email (removing the
-specifics, as I am not out to take the specific service in question)
-to the service provider I decided to not use, to at least give them
-one data point on how many users are unhappy with their terms:&lt;/p&gt;
+               <title>Nikita version 0.6 released - free software archive API server</title>
+               <link>http://people.skolelinux.org/pere/blog/Nikita_version_0_6_released___free_software_archive_API_server.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nikita_version_0_6_released___free_software_archive_API_server.html</guid>
+                <pubDate>Thu, 10 Jun 2021 17:10:00 +0200</pubDate>
+               <description>&lt;p&gt;I am very pleased to be able to share with you
+&lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2021-June/000576.html&quot;&gt;the
+announcement of a new version of the archiving system Nikita&lt;/a&gt;
+published by its lead developer Thomas Sødring:&lt;/p&gt;

 
 

-&lt;blockquote&gt;
-From: Petter Reinholdtsen
-&lt;br&gt;Subject: When terms of use turn users away
-&lt;br&gt;To: [contact@some.site]
-&lt;br&gt;Date: Sat, 07 Dec 2019 16:30:56 +0100
-
-&lt;p&gt;Dear [Site Owner],&lt;/p&gt;
-
-&lt;p&gt;I was eager to test the system, as it seemed like a fun and
-interesting application of [some] technology, but after reading the
-terms of use and privacy policy on &amp;lt;URL:
-https://www.[some.site]/terms-of-use &amp;gt; and &amp;lt;URL:
-https://www.[some.site]/privacy-policy &amp;gt; I want you to know that I
-decided to turn away.  There were several provisions in the terms and
-policy turning me off, but the final term that convinced me was being
-asked to sign away my right to reverse engineer.&lt;/p&gt;
-
-&lt;p&gt;-- 
-&lt;br&gt;Happy hacking
-&lt;br&gt;Petter Reinholdtsen&lt;/p&gt;
-&lt;/blockquote&gt;
+&lt;p&gt;&lt;blockquote&gt;

 
 

-&lt;p&gt;I do not expect much to come out of it, but sharing it here in case
-others want to give something similar a try too.  If companies
-discover their terms scare away enough people, perhaps they will be
-improved...&lt;/p&gt;
-</description>
-       </item>
-       
-       <item>
-               <title>What would it cost to store all 2018 phone calls in Norway?</title>
-               <link>http://people.skolelinux.org/pere/blog/What_would_it_cost_to_store_all_2018_phone_calls_in_Norway_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_would_it_cost_to_store_all_2018_phone_calls_in_Norway_.html</guid>
-                <pubDate>Mon, 25 Nov 2019 20:15:00 +0100</pubDate>
-               <description>&lt;p&gt;Four years ago, I did a back of the envelope calculation on
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_would_it_cost_to_store_all_phone_calls_in_Norway_.html&quot;&gt;how
-much it would cost to store audio recordings of all the phone calls in
-Norway&lt;/a&gt;, and came up with NOK 2.1 million / EUR 250 000 for the
-year 2013.  It is time to repeat the calculation using updated
-numbers.  The calculation is based on how much data storage is needed
-for each minute of audio, how many minutes all the calls in Norway
-sums up to, multiplied by the cost of data storage.&lt;/p&gt;
-
-&lt;p&gt;The number of phone call minutes for 2018 was fetched from
-&lt;a href=&quot;https://ekomstatistikken.nkom.no/&quot;&gt;the NKOM statistics
-site&lt;/a&gt;, and for 2018, land line calls are listed as 434 238 000
-minutes, while mobile phone calls are listed with 7 542 006 000
-minutes.  The total number of minutes is thus 7 976 244 000.  For
-simplicity, I decided to ignore any advantages in audio compression the
-last four years, and continue to assume 60 Kbytes/min as the last
-time.&lt;/p&gt;
-
-&lt;p&gt;Storage prices still varies a lot, but as last time, I decide to
-take a reasonable big and cheap hard drive, and double its price to
-include the surrounding costs into account.  A 10 TB disk cost less
-than 4500 NOK / 450 EUR these days, and doubling it give 9000 NOK per
-10 TB.&lt;/p&gt;
-
-&lt;p&gt;So, with the parameters in place, lets update the old table
-estimating cost for calls in a given year:&lt;/p&gt;
-
-&lt;table border=&quot;1&quot;&gt;
-&lt;tr&gt;&lt;th&gt;Year&lt;/th&gt;&lt;th&gt;Call minutes&lt;/th&gt;&lt;th&gt;Size&lt;/th&gt;&lt;th&gt;Price in NOK / EUR&lt;/th&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;2005&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;24 000 000 000&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;1.3 PiB&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;1 170 000 / 117 000&lt;/td&gt;&lt;/tr&gt;
-
-&lt;tr&gt;&lt;td&gt;2012&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;18 000 000 000&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;1.0 PiB&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;900 000 / 90 000&lt;/td&gt;&lt;/tr&gt;
-
-&lt;tr&gt;&lt;td&gt;2013&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;17 000 000 000&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;950 TiB&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;855 000 / 85 500&lt;/td&gt;&lt;/tr&gt;
-
-&lt;tr&gt;&lt;td&gt;2018&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;7 976 244 000&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;445 TiB&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;401 100 / 40 110&lt;/td&gt;&lt;/tr&gt;
-&lt;/table&gt;
-
-&lt;p&gt;Both the cost of storage and the number of phone call minutes have
-dropped since the last time, bringing the cost down to a level where I
-guess even small organizations can afford to store the audio recording
-from every phone call taken in a year in Norway.  Of course, this is
-just the cost of buying the storage equipment.  Maintenance, need to
-be included as well, but the volume of a single year is about a single
-rack of hard drives, so it is not much more than I could fit in my own
-home.  Wonder how much the electricity bill would raise if I had that
-kind of storage?  I doubt it would be more than a few tens of thousand
-NOK per year.&lt;/p&gt;
+&lt;p&gt;It is with great pleasure that we can announce a new release of
+nikita.  Version 0.6
+(&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&lt;/a&gt;). This
+release makes new record keeping functionality available. This really
+is a maturity release. Both in terms of functionality but also code.
+Considerable effort has gone into refactoring the codebase and
+simplifying the code. Notable changes for this release include:&lt;/p&gt;
+
+&lt;ul&gt;
+
+  &lt;li&gt;Significantly improved OData parsing&lt;/li&gt;
+  &lt;li&gt;Support for business specific metadata and national identifiers&lt;/li&gt;
+  &lt;li&gt;Continued implementation of domain model and endpoints&lt;/li&gt;
+  &lt;li&gt;Improved testing&lt;/li&gt;
+  &lt;li&gt;Ability to export and import from arkivstruktur.xml&lt;/li&gt;
+
+&lt;/ul&gt;
+
+&lt;p&gt;We are currently in the process of reaching an agreement with an
+archive institution to publish their picture archive using nikita with
+business specific metadata and we hope that we can share this with you
+soon. This is an interesting project as it allows the organisation to
+bring an older picture archive back to life while using the original
+metadata values stored as business specific metadata. Combined with
+OData means the scope and use of the archive is significantly
+increased and will showcase both the flexibility and power of
+Noark.&lt;/p&gt;
+
+&lt;p&gt;I really think we are approaching a version 1.0 of nikita, even
+though there is still a lot of work to be done. The notable work at
+the moment is to implement access-control and full text indexing of
+documents.&lt;/p&gt;
+
+&lt;p&gt;My sincere thanks to everyone who has contributed to this
+release!&lt;/p&gt;
+
+&lt;p&gt;- Thomas&lt;/p&gt;
+
+&lt;p&gt;&lt;strong&gt;Release 0.6 2021-06-10 (d1ba5fc7e8bad0cfdce45ac20354b19d10ebbc7b)&lt;/strong&gt;&lt;/p&gt;
+
+&lt;ul&gt;
+
+  &lt;li&gt;Refactor metadata entity search&lt;/li&gt;
+  &lt;li&gt;Remove redundant security configuration&lt;/li&gt;
+  &lt;li&gt;Make OpenAPI documentation work&lt;/li&gt;
+  &lt;li&gt;Change database structure / inheritance model to a more sensible approach&lt;/li&gt;
+  &lt;li&gt;Make it possible to move entities around the fonds structure&lt;/li&gt;
+  &lt;li&gt;Implemented a number of missing endpoints&lt;/li&gt;
+  &lt;li&gt;Make sure yml files are in sync&lt;/li&gt;
+  &lt;li&gt;Implemented/finalised storing and use of
+  &lt;ul&gt;
+       &lt;li&gt;Business Specific Metadata&lt;/li&gt;
+       &lt;li&gt;Norwegian National Identifiers&lt;/li&gt;
+       &lt;li&gt;Cross Reference&lt;/li&gt;
+       &lt;li&gt;Keyword&lt;/li&gt;
+       &lt;li&gt;StorageLocation&lt;/li&gt;
+       &lt;li&gt;Author&lt;/li&gt;
+       &lt;li&gt;Screening for relevant objects&lt;/li&gt;
+       &lt;li&gt;ChangeLog&lt;/li&gt;
+       &lt;li&gt;EventLog&lt;/li&gt;
+  &lt;/ul&gt;&lt;/li&gt;
+  &lt;li&gt;Make generation of updated docker image part of successful CI pipeline&lt;/li&gt;
+  &lt;li&gt;Implement pagination for all list requests
+  &lt;ul&gt;
+       &lt;li&gt;Refactor code to support lists&lt;/li&gt;
+       &lt;li&gt;Refactor code for readability&lt;/li&gt;
+       &lt;li&gt;Standardise the controller/service code&lt;/li&gt;
+  &lt;/ul&gt;&lt;/li&gt;
+  &lt;li&gt;Finalise File-&gt;CaseFile expansion and Record-&gt;registryEntry/recordNote 
+expansion&lt;/li&gt;
+  &lt;li&gt;Improved Continuous Integration (CI) approach via gitlab&lt;/li&gt;
+  &lt;li&gt;Changed conversion approach to generate tagged PDF documents&lt;/li&gt;
+  &lt;li&gt;Updated dependencies
+  &lt;ul&gt;
+       &lt;li&gt;For security reasons&lt;/li&gt;
+       &lt;li&gt;Brought codebase to spring-boot version 2.5.0&lt;/li&gt;
+       &lt;li&gt;Remove import of necessary dependencies&lt;/li&gt;
+       &lt;li&gt;Remove non-used metrics classes&lt;/li&gt;
+  &lt;/ul&gt;&lt;/li&gt;
+  &lt;li&gt;Added new analysis to CI including&lt;/li&gt;
+  &lt;li&gt;Implemented storing of Keyword&lt;/li&gt;
+  &lt;li&gt;Implemented storing of Screening and ScreeningMetadata&lt;/li&gt;
+  &lt;li&gt;Improved OData support
+  &lt;ul&gt;
+       &lt;li&gt;Better support for inheritance in queries where applicable&lt;/li&gt;
+       &lt;li&gt;Brought in more OData tests&lt;/li&gt;
+       &lt;li&gt;Improved OData/hibernate understanding of queries&lt;/li&gt;
+       &lt;li&gt;Implement $count, $orderby&lt;/li&gt;
+       &lt;li&gt;Finalise $top and $skip&lt;/li&gt;
+       &lt;li&gt;Make sure &amp; is used between query parameters&lt;/li&gt;
+  &lt;/ul&gt;&lt;/li&gt;
+  &lt;li&gt;Improved Testing in codebase
+  &lt;ul&gt;
+       &lt;li&gt;A new approach for integration tests to make test more readable&lt;/li&gt;
+       &lt;li&gt;Introduce tests in parallel with code development for TDD approach&lt;/li&gt;
+       &lt;li&gt;Remove test that required particular access to storage&lt;/li&gt;
+  &lt;/ul&gt;&lt;/li&gt;
+  &lt;li&gt;Implement case-handling process from received email to case-handler
+  &lt;ul&gt;
+       &lt;li&gt;Develop required GUI elements (digital postroom from email)&lt;/li&gt;
+       &lt;li&gt;Introduced leader, quality control and postroom roles&lt;/li&gt;
+  &lt;/ul&gt;&lt;/li&gt;
+  &lt;li&gt;Make PUT requests return 200 OK not 201 CREATED&lt;/li&gt;
+  &lt;li&gt;Make DELETE requests return 204 NO CONTENT not 200 OK&lt;/li&gt;
+  &lt;li&gt;Replaced &#39;oppdatert*&#39; with &#39;endret*&#39; everywhere to match latest spec&lt;/li&gt;
+  &lt;li&gt;Upgrade Gitlab CI to use python &gt; 3 for CI scripts&lt;/li&gt;
+  &lt;li&gt;Bug fixes
+  &lt;ul&gt;
+       &lt;li&gt;Fix missing ALLOW&lt;/li&gt;
+       &lt;li&gt;Fix reading of objects from jar file during start-up&lt;/li&gt;
+       &lt;li&gt;Reduce the number of warnings in the codebase&lt;/li&gt;
+       &lt;li&gt;Fix delete problems&lt;/li&gt;
+       &lt;li&gt;Make better use of cascade for &quot;leaf&quot; objects&lt;/li&gt;
+       &lt;li&gt;Add missing annotations where relevant&lt;/li&gt;
+       &lt;li&gt;Remove the use of ETAG for delete&lt;/li&gt;
+       &lt;li&gt;Fix missing/wrong/broken rels discovered by runtest&lt;/li&gt;
+       &lt;li&gt;Drop unofficial convertFil (konverterFil) end point&lt;/li&gt;
+       &lt;li&gt;Fix regex problem for dateTime&lt;/li&gt;
+       &lt;li&gt;Fix multiple static analysis issues discovered by coverity&lt;/li&gt;
+       &lt;li&gt;Fix proxy problem when looking for object class names&lt;/li&gt;
+       &lt;li&gt;Add many missing translated Norwegian to English (internal) 
+attribute/entity names&lt;/li&gt;
+       &lt;li&gt;Change UUID generation approach to allow code also set a value&lt;/li&gt;
+       &lt;li&gt;Fix problem with Part/PartParson&lt;/li&gt;
+       &lt;li&gt;Fix problem with empty OData search results&lt;/li&gt;
+       &lt;li&gt;Fix metadata entity domain problem&lt;/li&gt;
+  &lt;/ul&gt;&lt;/li&gt;
+  &lt;li&gt;General Improvements
+  &lt;ul&gt;
+       &lt;li&gt;Makes future refactoring easier as coupling is reduced&lt;/li&gt;
+       &lt;li&gt;Allow some constant variables to be set from property file&lt;/li&gt;
+       &lt;li&gt;Refactor code to make reflection work better across codebase&lt;/li&gt;
+       &lt;li&gt;Reduce the number of @Service layer classes used in @Controller 
+classes&lt;/li&gt;
+       &lt;li&gt;Be more consistent on naming of similar variable types&lt;/li&gt;
+       &lt;li&gt;Start printing rels/href if they are applicable&lt;/li&gt;
+       &lt;li&gt;Cleaner / standardised approach to deleting objects&lt;/li&gt;
+       &lt;li&gt;Avoid concatenation when using StringBuilder&lt;/li&gt;
+       &lt;li&gt;Consolidate code to avoid duplication&lt;/li&gt;
+       &lt;li&gt;Tidy formatting for a more consistent reading style across 
+similar class files&lt;/li&gt;
+       &lt;li&gt;Make throw a log.error message not an log.info message&lt;/li&gt;
+       &lt;li&gt;Make throw print the log value rather than printing in multiple 
+places&lt;/li&gt;
+       &lt;li&gt;Add some missing pronom codes&lt;/li&gt;
+       &lt;li&gt;Fix time formatting issue in Gitlab CI&lt;/li&gt;
+       &lt;li&gt;Remove stale / unused code&lt;/li&gt;
+       &lt;li&gt;Use only UUID datatype rather than combination String/UUID for systemID&lt;/li&gt;
+       &lt;li&gt;Mark variables final and @NotNull where relevant to indicate 
+intention&lt;/li&gt;
+  &lt;/ul&gt;&lt;/li&gt;
+  &lt;li&gt;Change Date values to DateTime to maintain compliance with Noark 5 
+standard&lt;/li&gt;
+  &lt;li&gt;Domain model improvements using Hypersistence Optimizer
+  &lt;ul&gt;
+       &lt;li&gt;Move @Transactional from class to methods to avoid borrowing the JDBC Connection unnecessarily&lt;/li&gt;
+       &lt;li&gt;Fix OneToOne performance issues&lt;/li&gt;
+       &lt;li&gt;Fix ManyToMany performance issues&lt;/li&gt;
+       &lt;li&gt;Add missing bidirectional synchronization support&lt;/li&gt;
+       &lt;li&gt;Fix ManyToMany performance issue&lt;/li&gt;
+  &lt;/ul&gt;&lt;/li&gt;
+  &lt;li&gt;Make List&lt;&gt; and Set&lt;&gt; use final-keyword to avoid potential problems 
+during update operations&lt;/li&gt;
+  &lt;li&gt;Changed internal URLs, replaced &quot;hateoas-api&quot; with &quot;api&quot;.&lt;/li&gt;
+  &lt;li&gt;Implemented storing of Precedence.&lt;/li&gt;
+  &lt;li&gt;Corrected handling of screening.&lt;/li&gt;
+  &lt;li&gt;Corrected _links collection returned for list of mixed entity types 
+to match the specific entity.&lt;/li&gt;
+  &lt;li&gt;Improved several internal structures.&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;/blockquote&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.oftc.net/%23nikita&quot;&gt;#nikita on
+irc.oftc.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;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>Norwegian movies that might be legal to share on the Internet</title>
-               <link>http://people.skolelinux.org/pere/blog/Norwegian_movies_that_might_be_legal_to_share_on_the_Internet.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_movies_that_might_be_legal_to_share_on_the_Internet.html</guid>
-                <pubDate>Sun, 1 Sep 2019 11:10:00 +0200</pubDate>
-               <description>&lt;p&gt;While working on identifying and counting movies that can be
-legally shared on the Internet, I also looked at the Norwegian movies
-listed in IMDb.  So far I have identified 54 candidates published
-before 1940 that might no longer be protected by norwegian copyright
-law.  Of these, only 29 are available at least in part from the
-Norwegian National Library.  It can be assumed that the remaining 25
-movies are lost.  It seem most useful to identify the copyright status
-of movies that are not lost.  To verify that the movie is really no
-longer protected, one need to verify the list of copyright holders and
-figure out if and when they died.  I&#39;ve been able to identify some of
-them, but for some it is hard to figure out when they died.&lt;/p&gt;
-
-&lt;/p&gt;This is the list of 29 movies both available from the library and
-possibly no longer protected by copyright law.  The year range
-(1909-1979 on the first line) is year of publication and last year
-with copyright protection.&lt;/p&gt;
-
-&lt;pre&gt;
-1909-1979 ( 70 year) NSB Bergensbanen 1909 - http://www.imdb.com/title/tt0347601/
-1910-1980 ( 70 year) Bjørnstjerne Bjørnsons likfærd - http://www.imdb.com/title/tt9299304/
-1910-1980 ( 70 year) Bjørnstjerne Bjørnsons begravelse - http://www.imdb.com/title/tt9299300/
-1912-1998 ( 86 year) Roald Amundsens Sydpolsferd (1910-1912) - http://www.imdb.com/title/tt9237500/
-1913-2006 ( 93 year) Roald Amundsen på sydpolen - http://www.imdb.com/title/tt0347886/
-1917-1987 ( 70 year) Fanden i nøtten - http://www.imdb.com/title/tt0346964/
-1919-2018 ( 99 year) Historien om en gut - http://www.imdb.com/title/tt0010259/
-1920-1990 ( 70 year) Kaksen på Øverland - http://www.imdb.com/title/tt0011361/
-1923-1993 ( 70 year) Norge - en skildring i 6 akter - http://www.imdb.com/title/tt0014319/
-1925-1997 ( 72 year) Roald Amundsen - Ellsworths flyveekspedition 1925 - http://www.imdb.com/title/tt0016295/
-1925-1995 ( 70 year) En verdensreise, eller Da knold og tott vaskede negrene hvite med 13 sæpen - http://www.imdb.com/title/tt1018948/
-1926-1996 ( 70 year) Luftskibet &#39;Norge&#39;s flugt over polhavet - http://www.imdb.com/title/tt0017090/
-1926-1996 ( 70 year) Med &#39;Maud&#39; over Polhavet - http://www.imdb.com/title/tt0017129/
-1927-1997 ( 70 year) Den store sultan - http://www.imdb.com/title/tt1017997/
-1928-1998 ( 70 year) Noahs ark - http://www.imdb.com/title/tt1018917/
-1928-1998 ( 70 year) Skjæbnen - http://www.imdb.com/title/tt1002652/
-1928-1998 ( 70 year) Chefens cigarett - http://www.imdb.com/title/tt1019896/
-1929-1999 ( 70 year) Se Norge - http://www.imdb.com/title/tt0020378/
-1929-1999 ( 70 year) Fra Chr. Michelsen til Kronprins Olav og Prinsesse Martha - http://www.imdb.com/title/tt0019899/
-1930-2000 ( 70 year) Mot ukjent land - http://www.imdb.com/title/tt0021158/
-1930-2000 ( 70 year) Det er natt - http://www.imdb.com/title/tt1017904/
-1930-2000 ( 70 year) Over Besseggen på motorcykel - http://www.imdb.com/title/tt0347721/
-1931-2001 ( 70 year) Glimt fra New York og den Norske koloni - http://www.imdb.com/title/tt0021913/
-1932-2007 ( 75 year) En glad gutt - http://www.imdb.com/title/tt0022946/
-1934-2004 ( 70 year) Den lystige radio-trio - http://www.imdb.com/title/tt1002628/
-1935-2005 ( 70 year) Kronprinsparets reise i Nord Norge - http://www.imdb.com/title/tt0268411/
-1935-2005 ( 70 year) Stormangrep - http://www.imdb.com/title/tt1017998/
-1936-2006 ( 70 year) En fargesymfoni i blått - http://www.imdb.com/title/tt1002762/
-1939-2009 ( 70 year) Til Vesterheimen - http://www.imdb.com/title/tt0032036/
-&lt;/pre&gt;
-
-To be sure which one of these can be legally shared on the Internet,
-in addition to verifying the right holders list is complete, one need
-to verify the death year of these persons:
-
-&lt;pre&gt;
-Bjørnstjerne Bjørnson (dead 1910) - http://www.imdb.com/name/nm0085085/
-Gustav Adolf Olsen (missing death year) - http://www.imdb.com/name/nm0647652/
-Gustav Lund (missing death year) - http://www.imdb.com/name/nm0526168/
-John W. Brunius (dead 1937) - http://www.imdb.com/name/nm0116307/
-Ola Cornelius (missing death year) - http://www.imdb.com/name/nm1227236/
-Oskar Omdal (dead 1927) - http://www.imdb.com/name/nm3116241/
-Paul Berge (missing death year) - http://www.imdb.com/name/nm0074006/
-Peter Lykke-Seest (dead 1948) - http://www.imdb.com/name/nm0528064/
-Roald Amundsen (dead 1928) - https://www.imdb.com/name/nm0025468/
-Sverre Halvorsen (dead 1936) - http://www.imdb.com/name/nm1299757/
-Thomas W. Schwartz (missing death year) - http://www.imdb.com/name/nm2616250/
-&lt;/pre&gt;
-
-&lt;p&gt;Perhaps you can help me figuring death year of those missing it, or
-right holders if some are missing in IMDb?  It would be nice to have a
-definite list of Norwegian movies that are legal to share on the
-Internet.&lt;/p&gt;
-
-&lt;/p&gt;This is the list of 25 movies not available from the library and
-possibly no longer protected by copyright law:&lt;/p&gt;
-
-&lt;pre&gt;
-1907-2009 (102 year) Fiskerlivets farer - http://www.imdb.com/title/tt0121288/
-1912-2018 (106 year) Historien omen moder - http://www.imdb.com/title/tt0382852/
-1912-2002 ( 90 year) Anny - en gatepiges roman - http://www.imdb.com/title/tt0002026/
-1916-1986 ( 70 year) The Mother Who Paid - http://www.imdb.com/title/tt3619226/
-1917-2018 (101 year) En vinternat - http://www.imdb.com/title/tt0008740/
-1917-2018 (101 year) Unge hjerter - http://www.imdb.com/title/tt0008719/
-1917-2018 (101 year) De forældreløse - http://www.imdb.com/title/tt0007972/
-1918-2018 (100 year) Vor tids helte - http://www.imdb.com/title/tt0009769/
-1918-2018 (100 year) Lodsens datter - http://www.imdb.com/title/tt0009314/
-1919-2018 ( 99 year) Æresgjesten - http://www.imdb.com/title/tt0010939/
-1921-2006 ( 85 year) Det nye year? - http://www.imdb.com/title/tt0347686/
-1921-1991 ( 70 year) Under Polarkredsens himmel - http://www.imdb.com/title/tt0012789/
-1923-1993 ( 70 year) Nordenfor polarcirkelen - http://www.imdb.com/title/tt0014318/
-1925-1995 ( 70 year) Med &#39;Stavangerfjord&#39; til Nordkap - http://www.imdb.com/title/tt0016098/
-1926-1996 ( 70 year) Over Atlanterhavet og gjennem Amerika - http://www.imdb.com/title/tt0017241/
-1926-1996 ( 70 year) Hallo! Amerika! - http://www.imdb.com/title/tt0016945/
-1926-1996 ( 70 year) Tigeren Teodors triumf - http://www.imdb.com/title/tt1008052/
-1927-1997 ( 70 year) Rød sultan - http://www.imdb.com/title/tt1017979/
-1927-1997 ( 70 year) Søndagsfiskeren Flag - http://www.imdb.com/title/tt1018002/
-1930-2000 ( 70 year) Ro-ro til fiskeskjær - http://www.imdb.com/title/tt1017973/
-1933-2003 ( 70 year) I kongens klær - http://www.imdb.com/title/tt0024164/
-1934-2004 ( 70 year) Eventyret om de tre bukkene bruse - http://www.imdb.com/title/tt1007963/
-1934-2004 ( 70 year) Pål sine høner - http://www.imdb.com/title/tt1017966/
-1937-2007 ( 70 year) Et mesterverk - http://www.imdb.com/title/tt1019937/
-1938-2008 ( 70 year) En Harmony - http://www.imdb.com/title/tt1007975/
-&lt;/pre&gt;
-
-&lt;p&gt;Several of these movies completely lack right holder information in
-IMDb and elsewhere.  Without access to a copy of the movie, it is
-often impossible to get the list of people involved in making the
-movie, making it impossible to figure out the correct copyright
-status.&lt;/p&gt;
-
-&lt;p&gt;Not listed here are the movies still protected by copyright law.
-Their copyright terms varies from 79 to 144 years, according to the
-information I have available so far.  One of the non-lost movies might
-change status next year,
-&lt;a href=&quot;https://www.imdb.com/title/tt1008007/&quot;&gt;Mustads Mono from 1920&lt;/a&gt;.
-The next one might be
-&lt;a href=&quot;https://www.imdb.com/title/tt0347215/&quot;&gt;Hvor isbjørnen ferdes
-from 1935&lt;/a&gt; in 2024.&lt;/p&gt;
-
+               <title>VLC bittorrent plugin in Bullseye, saved by the bell?</title>
+               <link>http://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_in_Bullseye__saved_by_the_bell_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_in_Bullseye__saved_by_the_bell_.html</guid>
+                <pubDate>Sat, 1 May 2021 11:00:00 +0200</pubDate>
+               <description>&lt;p&gt;Yesterday morning I got a warning call from the Debian quality
+control system that
+&lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;the VLC
+bittorrent plugin&lt;/a&gt; was due to be removed because of a release
+critical bug in one of its dependencies.  As you might remember, this
+plugin make VLC able to stream videos directly from a bittorrent
+source using both torrent files and magnet links, similar to using a
+HTTP source.  I believe such protocol support is a vital feature in
+VLC, allowing efficient streaming from sources such at the almost 7
+million movies in &lt;a href=&quot;https://archive.org/&quot;&gt;the Internet
+Archive&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;The dependency was the unmaintained
+&lt;a href=&quot;https://tracker.debian.org/pkg/libtorrent-rasterbar&quot;&gt;libtorrent-rasterbar&lt;/a&gt;
+package, and &lt;a href=&quot;https://bugs.debian.org/987306&quot;&gt;the bug in
+question&lt;/a&gt; blocked its python library from working properly.  As I
+did not want Bullseye to release without bittorrent support in VLC, I
+set out to check out the status, and track down a fix for the problem.
+Luckily the issue had already been identified and fixed upstream,
+providing everything needed.  All I needed to do was to fetch the
+Debian git repository, extract and trim the patch from upstream and
+apply it to the Debian package for upload.&lt;/p&gt;
+
+&lt;p&gt;The fixed library was uploaded yesterday evening.  But that is not
+enough to get it into Bullseye, as Debian is currently in package
+freeze to prepare for a new next stable release.  Only non-critical
+packages with
+&lt;a href=&quot;https://wiki.debian.org/ContinuousIntegration/autopkgtest&quot;&gt;autopkgtest
+setup&lt;/a&gt; included, in other words able to validate automatically that
+the package is working, are allowed to migrate automatically into the
+next release at this stage.  And the unmaintained libtorrent-rasterbar
+lack such testing, and thus needed a manual override.  I am happy to
+report that such manual override was approved a few minutes ago, thus
+increasing significantly the chance of VLC bittorrent streaming being
+available out of the box also for Debian/Buster users.  A bit too
+close shave for my liking, as the Bullseye release is most likely just
+a few days away, and this  did feel like the package was saved by the
+bell.  I am so glad the warning email showed up in time for me to
+handle the issue, and a big thanks go to the Debian Release team for
+the quick feedback on
+&lt;a href=&quot;irc://irc.debian.org/%23debian-release&quot;&gt;#debian-release&lt;/a&gt;
+and their &lt;a href=&quot;https://bugs.debian.org/987865&quot;&gt;swift
+unblocking&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;
 &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;


@@ -237,69 +260,57 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
        </item>
        
        <item>

-               <title>Legal to share more than 16,000 movies listed on IMDB?</title>
-               <link>http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_16_000_movies_listed_on_IMDB_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_16_000_movies_listed_on_IMDB_.html</guid>
-                <pubDate>Sat, 10 Aug 2019 12:00:00 +0200</pubDate>
-               <description>&lt;p&gt;The recent announcement of from the New York Public Library on its
-results in
-&lt;a href=&quot;https://www.vice.com/en_us/article/kz4e3e/millions-of-books-are-secretly-in-the-public-domain-you-can-download-them-free&quot;&gt;identifying
-books published in the USA that are now in the public domain&lt;/a&gt;,
-inspired me to update the scripts I use to track down movies that are
-in the public domain.  This involved updating the script used to
-extract lists of movies believed to be in the public domain, to work
-with the latest version of the source web sites.  In particular the
-new edition of the &lt;a href=&quot;https://retrofilmvault.com/&quot;&gt;Retro Film
-Vault&lt;/a&gt; web site now seem to list all the films available from that
-distributor, bringing the films identified there to more than 12.000
-movies, and I was able to connect 46% of these to IMDB titles.&lt;/p&gt;
-
-&lt;p&gt;The new total is 16307 IMDB IDs (aka films) in the public domain or
-creative commons licensed, and unknown status for 31460 movies
-(possibly duplicates of the 16307).&lt;/p&gt;
-
-&lt;p&gt;The complete data set is available from
-&lt;a href=&quot;https://github.com/petterreinholdtsen/public-domain-free-imdb&quot;&gt;a
-public git repository&lt;/a&gt;, including the scripts used to create it.&lt;/p&gt;
-
-&lt;p&gt;Anyway, this is the summary of the 28 collected data sources so
-far:&lt;/p&gt;
-
-&lt;p&gt;&lt;pre&gt;
- 2361 entries (   50 unique) with and 22472 without IMDB title ID in free-movies-archive-org-search.json
- 2363 entries (  146 unique) with and     0 without IMDB title ID in free-movies-archive-org-wikidata.json
-  299 entries (   32 unique) with and    93 without IMDB title ID in free-movies-cinemovies.json
-   88 entries (   52 unique) with and    36 without IMDB title ID in free-movies-creative-commons.json
- 3190 entries ( 1532 unique) with and    13 without IMDB title ID in free-movies-fesfilm-xls.json
-  620 entries (   24 unique) with and   283 without IMDB title ID in free-movies-fesfilm.json
- 1080 entries (  165 unique) with and   651 without IMDB title ID in free-movies-filmchest-com.json
-  830 entries (   13 unique) with and     0 without IMDB title ID in free-movies-icheckmovies-archive-mochard.json
-   19 entries (   19 unique) with and     0 without IMDB title ID in free-movies-imdb-c-expired-gb.json
- 7410 entries ( 7101 unique) with and     0 without IMDB title ID in free-movies-imdb-c-expired-us.json
- 1205 entries (   41 unique) with and     0 without IMDB title ID in free-movies-imdb-pd.json
-  163 entries (   22 unique) with and    88 without IMDB title ID in free-movies-infodigi-pd.json
-  158 entries (  103 unique) with and     0 without IMDB title ID in free-movies-letterboxd-looney-tunes.json
-  113 entries (    4 unique) with and     0 without IMDB title ID in free-movies-letterboxd-pd.json
-  182 entries (   71 unique) with and     0 without IMDB title ID in free-movies-letterboxd-silent.json
-  248 entries (   85 unique) with and     0 without IMDB title ID in free-movies-manual.json
-  158 entries (    4 unique) with and    64 without IMDB title ID in free-movies-mubi.json
-   85 entries (    1 unique) with and    23 without IMDB title ID in free-movies-openflix.json
-  520 entries (   22 unique) with and   244 without IMDB title ID in free-movies-profilms-pd.json
-  343 entries (   14 unique) with and    10 without IMDB title ID in free-movies-publicdomainmovies-info.json
-  701 entries (   16 unique) with and   560 without IMDB title ID in free-movies-publicdomainmovies-net.json
-   74 entries (   13 unique) with and    60 without IMDB title ID in free-movies-publicdomainreview.json
-  698 entries (   16 unique) with and   118 without IMDB title ID in free-movies-publicdomaintorrents.json
- 5506 entries ( 2941 unique) with and  6585 without IMDB title ID in free-movies-retrofilmvault.json
-   16 entries (    0 unique) with and     0 without IMDB title ID in free-movies-thehillproductions.json
-  110 entries (    2 unique) with and    29 without IMDB title ID in free-movies-two-movies-net.json
-   73 entries (   20 unique) with and   131 without IMDB title ID in free-movies-vodo.json
-16307 unique IMDB title IDs in total, 12509 only in one list, 31460 without IMDB title ID
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;New this time is a list of all the identified IMDB titles, with
-title, year and running time, provided in free-complete.json.  this
-file also indiciate which source is used to conclude the video is free
-to distribute.&lt;/p&gt;
+               <title>Updated Valutakrambod, now also with information from NBX</title>
+               <link>http://people.skolelinux.org/pere/blog/Updated_Valutakrambod__now_also_with_information_from_NBX.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Updated_Valutakrambod__now_also_with_information_from_NBX.html</guid>
+                <pubDate>Sat, 27 Feb 2021 13:30:00 +0100</pubDate>
+               <description>&lt;p&gt;I have neglected the Valutakrambod library for a while, but decided
+this weekend to give it a face lift.  I fixed a few minor glitches in
+several of the service drivers, where the API had changed since I last
+looked at the code.  I also added support for fetching the order book
+from the newcomer Norwegian Bitcoin Exchange.&lt;/p&gt;
+
+&lt;p&gt;I also decided to migrate the project from github to gitlab in the
+process.  If you want a python library for talking to various currency
+exchanges, check out
+&lt;a href=&quot;https://gitlab.com/petterreinholdtsen/valutakrambod&quot;&gt;code for
+valutakrambod&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;This is what the output from &#39;&lt;tt&gt;bin/btc-rates-curses -c&lt;/tt&gt;&#39;
+looked like a few minutes ago:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+           Name Pair           Bid         Ask Spread Ftcd    Age   Freq
+       Bitfinex BTCEUR  39229.0000  39246.0000   0.0%   44     44    nan
+        Bitmynt BTCEUR  39071.0000  41048.9000   4.8%   43     74    nan
+         Bitpay BTCEUR  39326.7000         nan   nan%   39    nan    nan
+       Bitstamp BTCEUR  39398.7900  39417.3200   0.0%    0      0      1
+           Bl3p BTCEUR  39158.7800  39581.9000   1.1%    0    nan      3
+       Coinbase BTCEUR  39197.3100  39621.9300   1.1%   38    nan    nan
+         Kraken+BTCEUR  39432.9000  39433.0000   0.0%    0      0      0
+        Paymium BTCEUR  39437.2100  39499.9300   0.2%    0   2264    nan
+        Bitmynt BTCNOK 409750.9600 420516.8500   2.6%   43     74    nan
+         Bitpay BTCNOK 410332.4000         nan   nan%   39    nan    nan
+       Coinbase BTCNOK 408675.7300 412813.7900   1.0%   38    nan    nan
+        MiraiEx BTCNOK 412174.1800 418396.1500   1.5%   34    nan    nan
+            NBX BTCNOK 405835.9000 408921.4300   0.8%   33    nan    nan
+       Bitfinex BTCUSD  47341.0000  47355.0000   0.0%   44     53    nan
+         Bitpay BTCUSD  47388.5100         nan   nan%   39    nan    nan
+       Coinbase BTCUSD  47153.6500  47651.3700   1.0%   37    nan    nan
+         Gemini BTCUSD  47416.0900  47439.0500   0.0%   36    336    nan
+         Hitbtc BTCUSD  47429.9900  47386.7400  -0.1%    0      0      0
+         Kraken+BTCUSD  47401.7000  47401.8000   0.0%    0      0      0
+  Exchangerates EURNOK     10.4012     10.4012   0.0%   38  76236    nan
+     Norgesbank EURNOK     10.4012     10.4012   0.0%   31  76236    nan
+       Bitstamp EURUSD      1.2030      1.2045   0.1%    2      2      1
+  Exchangerates EURUSD      1.2121      1.2121   0.0%   38  76236    nan
+     Norgesbank USDNOK      8.5811      8.5811   0.0%   31  76236    nan
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Yes, I notice the negative spread on Hitbtc.  Either I fail to
+understand their Websocket API or they are sending bogus data.  I&#39;ve
+seen the same with Kraken, and suspect there is something wrong with
+the data they send.&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;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address


@@ -308,33 +319,115 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
        </item>
        
        <item>

-               <title>Oppdatert Noark 5 Tjenestegrenesnitt versjon 1.0 for Noark 5.5.0</title>
-               <link>http://people.skolelinux.org/pere/blog/Oppdatert_Noark_5_Tjenestegrenesnitt_versjon_1_0_for_Noark_5_5_0.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oppdatert_Noark_5_Tjenestegrenesnitt_versjon_1_0_for_Noark_5_5_0.html</guid>
-                <pubDate>Fri, 5 Jul 2019 17:20:00 +0200</pubDate>
-               <description>&lt;p&gt;Jeg er veldig glad for å kunne fortelle at i går ble ny versjon av
-&lt;a href=&quot;https://www.arkivverket.no/forvaltning-og-utvikling/noark-standarden/noark-5/tjenestegrensesnitt-noark5&quot;&gt;API-spesifikasjonen
-for Noark 5 Tjenestegrensesnitt&lt;/a&gt; gitt ut.  Det så lenge mørkt ut
-for sjansene for å få inn nødvendige korreksjoner i
-spesifikasjonsteksten innen rimelig tid, men takket være intens og god
-innsats fra Mona og Anne Sofie hos Arkivverket de siste ukene, så ble
-resultatet som ble gitt ut på USAs uavhengighetsdag mye bedre enn jeg
-fryktet.&lt;/p&gt;
-
-&lt;p&gt;Spesifikasjonen er
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/&quot;&gt;tilgjengelig
-som markdown-filer i Arkivverkets github-prosjekt for dette&lt;/a&gt;, og de
-aller fleste av forslagene til forbedringer fra oss som holder på med
-&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;Nikita-prosjektet&lt;/a&gt;
-kom med i denne nye og oppdaterte spesifikasjonsteksten.  Det er
-fortsatt mye som gjenstår før den er entydig, klar og sikrer samvirke
-på tvers av leverandører, men utgangspunktet er veldig mye bedre enn
-forrige versjon fra 2016.  Ta gjerne en titt.&lt;/p&gt;
-
-&lt;p&gt;Ellers må jeg jo si at det var hyggelig å se at min forrige
-bloggpost om tjenestegrensesnittet fikk en
-&lt;a href=&quot;https://beta.arkivverket.no/post/186020592045/noark-5-versjon-50-tjenestegrensesnitt-10&quot;&gt;lenke
-fra Arkivverket Beta&lt;/a&gt;.&lt;/p&gt;
+               <title>Boken «Hvordan knuse overvåkningskapitalismen» lanseres på norsk</title>
+               <link>http://people.skolelinux.org/pere/blog/Boken__Hvordan_knuse_overv_kningskapitalismen__lanseres_p__norsk.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Boken__Hvordan_knuse_overv_kningskapitalismen__lanseres_p__norsk.html</guid>
+                <pubDate>Tue, 26 Jan 2021 19:10:00 +0100</pubDate>
+               <description>&lt;p&gt;Etter intenst arbeid over mange måneder er endelig den norske
+utgaven av «Hvordan knuse overvåkningskapitalismen» av Cory Doctorow
+ferdig og klar til å glede millioner av lesere over hele verden.
+Følgende pressemelding ble nettopp sendt ut til norske redaksjoner:
+
+&lt;blockquote&gt;
+
+&lt;p&gt;&lt;strong&gt;Hva gjør stordata med oss, og hvordan gjør algoritmene
+«fake news» til realiter?&lt;/strong&gt;&lt;/p&gt;
+
+&lt;p&gt;Nå foreligger en viktig bok om temaet også på norsk. Boken klargjør
+og foreslår hvordan vi selv som enkeltpersoner, men også nasjonalt og
+internasjonalt kan bekjempe stordatakonsentrasjonene;
+«overvåkingskapitalismen».  Boken er «Hvordan knuse
+overvåkingskapitalismen» av dr. Cory Doctorow. Den engelske
+bokutgivelsen kom for noen dager siden og lanseres med et Webinar
+torsdag 2021-01-28. Doctorow besøkte Norge og NUUG i desember med sin
+presentasjon Monopoly, Not Mind Control: What&#39;s Really Happening With
+&quot;Surveillance Capitalism&quot;.&lt;/p&gt;
+
+&lt;p&gt;I funn etter funn, eksempel etter eksempel, gjennomgår og
+analyserer dr. Doctorow de utfordringer vi møter i større og større
+omfang. Ikke bare i USA, men også her hjemme.&lt;/p&gt;
+
+&lt;p&gt;Cory Doctorow er en britisk-kanadisk forfatter, journalist og
+aktivist, kjent for sine science fiction-romaner, for arbeidet for
+Creative Commons-bevegelsen, og for sine bidrag til reform av
+opphavsretten. Han er både æresdoktor og gjesteforeleser i
+datavitenskap ved Open University i UK, konsulent for Electronic
+Frontier Foundation, og godt kjent for innsiktsfullt å kommentere og
+skrive om digital utvikling.&lt;/p&gt;
+
+&lt;p&gt;Boken lanseres nå på norsk, både som ebok og på papir, oversatt av
+en dugnadsgjeng ledet av Petter Reinholdtsen.&lt;/p&gt;
+
+&lt;p&gt;Boken reiser noen helt grunnleggende og samfunnskritiske spørsmål:
+Hva fører det til når store deler av Internettet domineres av få store
+aktører og deres styringsverktøy og algoritmer?&lt;/p&gt;
+
+&lt;p&gt;Som individer bør vi være opptatt at grenser blir satt og håndhevet
+- grenser for overvåkning av individet, for utøvelse av kommersiell
+og politisk påvirkning, og for monopoldannelser i
+dataverdenen. Slik grensesetting styrker personvernet.&lt;/p&gt;
+
+&lt;p&gt;Konkurransetilsynet har ansvaret for at konkurranselovens § 11 skal
+forby «et dominerende foretak for utilbørlig å utnytte og misbruke
+sin dominerende stilling». Et tilsvarende forbud omfattes også av
+EØS-avtalens artikkel 54. Boken går i detalj om serien av
+innskrenkninger vi møter i valgfriheten, innskrenkninger som denne
+lovgivningen nettopp skal forhindre. Håndhevelse av en slik lovgivning
+er også til fordel for mindre næringsdrivende som uten dette får
+begrenset sine faktiske eller potensielle muligheter for vekst og
+etablering. «Slik atferd kan utgjøre et misbruk og kan ta ulike
+former», skriver Konkurransetilsynet.&lt;/p&gt;
+
+&lt;p&gt;Cory Doctorow går i sin bok lengre enn det med sine mange eksempler
+på forhold det burde vært grepet inn mot.&lt;/p&gt;
+
+&lt;p&gt;«Boken bør bidra til et sterkere engasjemen fra voktere av
+Inter­nettet nasjonalt og internasjonalt - EU medregnet» sier
+oversetter Ole-Erik Yrvin og fortsetter: «Vi har derfor
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2021-01-26-knus-overvaakningskapitalismen-helleland.pdf&quot;&gt;allerede
+tatt opp bokens forslag&lt;/a&gt; direkte med Distrikts- og
+digitaliseringsminister Linda Hofstad Helleland (H) og
+Konkurransetilsynet slik at de kan følges opp.»&lt;/p&gt;
+
+&lt;p&gt;«Også Norge bør innta en pådriverrolle i denne utviklingen», sier
+Petter Reinholdtsen. «Tiden er knapp, og tilsynsmyndighetene må få
+de verktøy og de ressurser de trenger for at vi her hjemme skal oppnå
+nødvendige resultater. Dette gjelder ikke bare vår egen generasjon;
+det gjelder alle generasjoner fremover», avslutter Petter
+Reinholdsen.&lt;/p&gt;
+
+&lt;p&gt;Kontaktinformasjon:&lt;/p&gt;
+
+&lt;ul&gt;
+
+&lt;li&gt;Ole-Erik Yrvin, oeyrvin (at) gmail.com, +47 46500450&lt;/li&gt;
+
+&lt;li&gt;Petter Reinholdtsen, pere (at) hungry.com&lt;/li&gt;
+
+&lt;/ul&gt;
+
+&lt;p&gt;Relevante lenker:&lt;p&gt;
+
+&lt;ul&gt;
+
+&lt;li&gt;«Hvordan knuse overvåkingskapitalismen» kan bestilles på papir,
+som ebok eller leses på nett via
+&lt;a href=&quot;http://www.hungry.com/~pere/publisher/&quot;&gt;http://www.hungry.com/~pere/publisher/&lt;/a&gt;.&lt;/li&gt;
+
+&lt;li&gt;Opptak av NUUG-møtet Monopoly, Not Mind Control: What&#39;s Really
+Happening With &quot;Surveillance Capitalism&quot; med Cory Doctorow,
+&lt;a href=&quot;https://www.nuug.no/aktiviteter/20201208-doctorow/&quot;&gt;https://www.nuug.no/aktiviteter/20201208-doctorow/&lt;/a&gt;.&lt;/li&gt;
+
+&lt;li&gt;Påmelding til webinar som lanserer den engelske utgaven kan gjøres
+via
+&lt;a href=&quot;https://craphound.com/category/destroy/&quot;&gt;https://craphound.com/category/destroy/&lt;/a&gt;.&lt;/li&gt;
+
+&lt;li&gt;Cory Doctorows nettsted er
+&lt;a href=&quot;https://craphound.com/&quot;&gt;https://craphound.com/&lt;/a&gt;.&lt;/li&gt;
+
+&lt;/ul&gt;
+
+&lt;/blockquote&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
 
 &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


@@ -345,39 +438,112 @@ Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
        </item>
        
        <item>
        </item>
        
        <item>

-               <title>Teach kids to protect their privacy - the EDRi way</title>
-               <link>http://people.skolelinux.org/pere/blog/Teach_kids_to_protect_their_privacy___the_EDRi_way.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teach_kids_to_protect_their_privacy___the_EDRi_way.html</guid>
-                <pubDate>Thu, 4 Jul 2019 19:10:00 +0200</pubDate>
-               <description>&lt;p&gt;Childs need to learn how to guard their privacy too.  To help them,
-&lt;a href=&quot;https://edri.org/&quot;&gt;European Digital Rights (EDRi)&lt;/a&gt; created
-a colorful booklet providing information on several privacy related topics,
-and tips on how to protect ones privacy in the digital age.&lt;/p&gt;
-
-&lt;p&gt;The 24 page booklet titled Digital Defenders is
-&lt;a href=&quot;https://edri.org/digital-defenders-help-kids-defend-their-privacy-around-europe&quot;&gt;available
-in several languages&lt;/a&gt;.  Thanks to the valuable contributions from
-members of &lt;a href=&quot;https://efn.no/&quot;&gt;the Electronic Foundation Norway
-(EFN)&lt;/a&gt; and others, it is also available in Norwegian Bokmål.
-If you would like to have it available in your language too,
-&lt;a href=&quot;https://hosted.weblate.org/projects/efn/privacy4kids/&quot;&gt;contribute
-via Weblate&lt;/a&gt; and get in touch.&lt;/p&gt;
-
-&lt;p&gt;But a funny, well written and good looking PDF do not have much
-impact, unless it is read by the right audience.  To increase the
-chance of kids reading it, I am currently assisting EFN in getting
-copies printed on paper to distribute on the street and in class
-rooms.  Print the booklet was made possible thanks to a small et of
-great sponsors.  Thank you very much to each and every one of them!  I
-hope to have the printed booklet ready to hand out on Tuesday, when
-&lt;a href=&quot;https://www.nuug.no/&gt;&quot;&gt;the Norwegian Unix Users Group&lt;/a&gt; is
-organizing &lt;a href=&quot;https://wiki.nuug.no/sommerfest2019&quot;&gt;its yearly
-barbecue for geeks and free software zealots in the Oslo area&lt;/a&gt;.  If
-you are nearby, feel free to come by and check out the party and the
-booklet.&lt;/p&gt;
-
-&lt;p&gt;If the booklet prove to be a success, it would be great to get
-more sponsoring and distribute it to every kid in the country. :)&lt;/p&gt;
+               <title>Latest Jami back in Debian Testing, and scriptable using dbus</title>
+               <link>http://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</guid>
+                <pubDate>Tue, 12 Jan 2021 17:00:00 +0100</pubDate>
+               <description>&lt;p&gt;After a lot of hard work by its maintainer Alexandre Viau and
+others, the decentralized communication platform
+&lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;
+(earlier known as Ring), managed to get
+&lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;its latest version&lt;/a&gt;
+into Debian Testing.  Several of its dependencies has caused build and
+propagation problems, which all seem to be solved now.&lt;/p&gt;
+
+&lt;p&gt;In addition to the fact that Jami is decentralized, similar to how
+bittorrent is decentralized, I first of all like how it is not
+connected to external IDs like phone numbers.  This allow me to set up
+computers to send me notifications using Jami without having to find
+get a phone number for each computer.  Automatic notification via Jami
+is also made trivial thanks to the provided client side API (as a DBus
+service).  Here is my bourne shell script demonstrating how to let any
+system send a message to any Jami address.  It will create a new
+identity before sending the message, if no Jami identity exist
+already:&lt;/p&gt;
+
+&lt;p&gt;&lt;pre&gt;
+#!/bin/sh
+#
+# Usage: $0 &lt;jami-address&gt; &lt;message&gt;
+#
+# Send &lt;message&gt; to &lt;jami-address&gt;, create local jami account if
+# missing.
+#
+# License: GPL v2 or later at your choice
+# Author: Petter Reinholdtsen
+
+
+if [ -z &quot;$HOME&quot; ] ; then
+    echo &quot;error: missing \$HOME, required for dbus to work&quot;
+    exit 1
+fi
+
+# First, get dbus running if not already running
+DBUSLAUNCH=/usr/bin/dbus-launch
+PIDFILE=/run/asterisk/dbus-session.pid
+if [ -e $PIDFILE ] ; then
+    . $PIDFILE
+    if ! kill -0 $DBUS_SESSION_BUS_PID 2&gt;/dev/null ; then
+        unset DBUS_SESSION_BUS_ADDRESS
+    fi
+fi
+if [ -z &quot;$DBUS_SESSION_BUS_ADDRESS&quot; ] &amp;&amp; [ -x &quot;$DBUSLAUNCH&quot; ]; then
+    DBUS_SESSION_BUS_ADDRESS=&quot;unix:path=$HOME/.dbus&quot;
+    dbus-daemon --session --address=&quot;$DBUS_SESSION_BUS_ADDRESS&quot; --nofork --nopidfile --syslog-only &lt; /dev/null &gt; /dev/null 2&gt;&amp;1 3&gt;&amp;1 &amp;
+    DBUS_SESSION_BUS_PID=$!
+    (
+        echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
+        echo DBUS_SESSION_BUS_ADDRESS=\&quot;&quot;$DBUS_SESSION_BUS_ADDRESS&quot;\&quot;
+        echo export DBUS_SESSION_BUS_ADDRESS
+    ) &gt; $PIDFILE
+    . $PIDFILE
+fi &amp;
+
+dringop() {
+    part=&quot;$1&quot;; shift
+    op=&quot;$1&quot;; shift
+    dbus-send --session \
+        --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
+}
+
+dringopreply() {
+    part=&quot;$1&quot;; shift
+    op=&quot;$1&quot;; shift
+    dbus-send --session --print-reply \
+        --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
+}
+
+firstaccount() {
+    dringopreply ConfigurationManager getAccountList | \
+      grep string | awk -F&#39;&quot;&#39; &#39;{print $2}&#39; | head -n 1
+}
+
+account=$(firstaccount)
+
+if [ -z &quot;$account&quot; ] ; then
+    echo &quot;Missing local account, trying to create it&quot;
+    dringop ConfigurationManager addAccount \
+      dict:string:string:&quot;Account.type&quot;,&quot;RING&quot;,&quot;Account.videoEnabled&quot;,&quot;false&quot;
+    account=$(firstaccount)
+    if [ -z &quot;$account&quot; ] ; then
+        echo &quot;unable to create local account&quot;
+        exit 1
+    fi
+fi
+
+# Not using dringopreply to ensure $2 can contain spaces
+dbus-send --print-reply --session \
+  --dest=cx.ring.Ring \
+  /cx/ring/Ring/ConfigurationManager \
+  cx.ring.Ring.ConfigurationManager.sendTextMessage \
+  string:&quot;$account&quot; string:&quot;$1&quot; \
+  dict:string:string:&quot;text/plain&quot;,&quot;$2&quot; 
+&lt;/pre&gt;&lt;/p&gt;
+
+&lt;p&gt;If you want to check it out yourself, visit the 
+&lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system project page&lt;/a&gt; to learn
+more, and install the latest Jami client from Debian Unstable or
+Testing.&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;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address


@@ -386,289 +552,137 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
        </item>
        
        <item>

-               <title>Nikita og Noark 5 tjenestegrensesnittet tilbyr ny måte å tenke arkivering</title>
-               <link>http://people.skolelinux.org/pere/blog/Nikita_og_Noark_5_tjenestegrensesnittet_tilbyr_ny_m_te___tenke_arkivering.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nikita_og_Noark_5_tjenestegrensesnittet_tilbyr_ny_m_te___tenke_arkivering.html</guid>
-                <pubDate>Fri, 21 Jun 2019 11:30:00 +0200</pubDate>
-               <description>&lt;p&gt;&lt;em&gt;av Thomas Sødring (OsloMet) og Petter Reinholdtsen (foreningen
-NUUG)&lt;/em&gt;&lt;/p&gt;
-
-&lt;p&gt;Nikita Noark 5-kjerne er et fri programvareprosjekt som tar i bruk
-Arkivverkets spesifikasjonen for Noark 5 Tjenestegrensesnitt og tilbyr
-et maskinlesbart grensesnitt (arkiv-API) til datasystemer som trenger å
-arkivere dokumenter og informasjon.  I tillegg tilbyr Nikita et
-nettleserbasert brukergrensesnitt for brukere av arkivet.  Dette
-brukergrensesnittet benytter det maskinlesbare grensesnittet.  Noark 5
-Tjenestegrensesnitt er en ny måte å tenke arkivering, med fokus på
-automatisering og maskinell behandling av arkivmateriale, i stedet for
-å fokusere på brukergrensesnitt.  En kan tenke på
-tjenestegrensesnittet som arkivet uten brukergrensesnitt, der flere
-aktører kan koble til ulike brukergrensesnitt, tilpasset ulike
-behov.&lt;/p&gt;
-
-&lt;p&gt;Historisk sett gjorde Noark standarden en veldig bra jobb med
-overgangen fra
-papir til digital saksbehandling, men det har kommet til kort på andre
-områder. Den teknologiske utviklingen har brakt oss ditt at vi kan og
-skal forvente langt mer fra en arkivkjerne enn før, men det offentlig
-er ofte konservativ når det gjelder nytenking. For lengst skulle
-begreper som samvirke mellom datasystemer, metadata, prosess og
-tjenestegrensesnitt (API) vært dominerende når systemer kjøpes
-inn. Dessverre er det slik at ikke alle ønsker samvirke mellom
-datasystemer velkommen, og det kan være trygt å kjøpe «svarte bokser»
-der du slipper å ta stilling til hvordan man skal få flere systemer
-til å virke sammen. Men IT-arkitektur er et begrep arkivfolk også
-begynner å ta inn over seg.&lt;/p&gt;
-
-&lt;p&gt;Slike systemer for å organisere metadata bør ha nettbaserte
-tjenestegrensesnitt der brukergrensesnitt er tydelig adskilt fra
-bakenforliggende system. Det finnes mange rapporter som snakker om å
-bryte ned siloer i forvaltningen og standardiserte tjenestegrensesnitt
-er det viktigste virkemiddel mot datasiloer og legger til rette for
-økt samvirke mellom systemer. Et standardisert tjenestegrensesnitt er
-et viktig middel for å få systemer til å samhandle da det sikrer at
-ulike produsenters systemer kan snakke sammen på tvers. Samfunnet
-fungerer ikke uten standardisering. Vi har alle samme strømstyrke og
-kontakter i veggene og kjører alle på høyre side av veien i Norge.  Det er i en slik
-sammenheng at prosjektet «Noark 5 Tjenestegrensesnitt» er veldig
-viktig. Hvis alle leverandører av arkivsystemer forholdt seg til et
-standardisert tjenestegrensesnitt kunne kostnadene for arkivering
-reduseres.  Tenk deg at du er en kommune som ønsker et fagsystem integrert
-med arkivløsningen din. I dag må fagsystemleverandøren vite og
-tilpasse seg den spesifikke versjonen og varianten av arkivløsningen
-du har. Hvis vi antar at alle leverandører av arkivkjerner har solgt
-inn enten SOAP eller REST-grensesnitt til kunder de siste 10 årene og
-det kommer endret versjon av grensesnittet innimellom, så gir det
-veldig mange forskjellige tjenestegrensesnitt en fagsystemleverandør
-må forholde seg til. Med 12 leverandører og kvartalsvise oppdateringer
-kan det potensielt bli 96 ulike varianter hvert eneste år.  Det sier
-seg selv at det blir dyrt. Men det blir faktisk verre. Hvis du senere
-ønsker å bytte ut arkivsystemet med et annet så er du avhengig å få
-alle integrasjonene dine laget på nytt. Dette kan gjøre at du velger å
-forbli hos en dårlig leverandør framfor å skaffe nytt system, fordi
-det blir for vanskelig og dyrt å bytte. Dermed etableres det «små»
-monopolsituasjoner som er vanskelig å bryte ut av. Dårlige valg i dag
-kan ha uante kostander på sikt. I Nikita-prosjektet har vi kun jobbet
-opp mot Noark 5 Tjenestegrensesnittet.  Det har tatt en god del
-ressurser å sette seg inn i spesifikasjonen og ta den i bruk, spesielt
-på grunn av uklarheter i spesifikasjonen. Hvis vi måtte gjøre det
-samme for alle versjoner og varianter av de forskjellige
-tjenestegrensesnittene ville det blitt veldig tidkrevende og
-kostbart.&lt;/p&gt;
-
-&lt;p&gt;For deg som arkivar er digitalisering og systemer som skal virke
-sammen en del av den nye hverdagen. Du har kanskje blitt skånet for
-det ved å kjøpe svarte bokser, men du risikerer at du gjør deg selv en
-bjørnetjeneste. Det kan oppleves som kjedelig å fortelle kolleger at
-du skal sette deg inn i et tjenestegrensesnitt, men dette er faktisk
-veldig spennende. Tjenestegrensesnittet er på en måte blitt levende og
-det er spesielt et begrep du bør merke deg: OData.  Å trekke inn deler
-av OData-standarden som en måte å filtrere entitetsøk i et arkivsystem
-var et nyttig trekk i prosjektet.  Følgende eksempel er en
-OData-spørring det går an å sende inn til en standardisert
-arkivkjerne:&lt;/p&gt;
+               <title>Boken «Made with Creative Commons» lanseres på norsk</title>
+               <link>http://people.skolelinux.org/pere/blog/Boken__Made_with_Creative_Commons__lanseres_p__norsk.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Boken__Made_with_Creative_Commons__lanseres_p__norsk.html</guid>
+                <pubDate>Sun, 15 Nov 2020 23:50:00 +0100</pubDate>
+               <description>&lt;p&gt;Endelig er den norske utgaven av «Made with Creative Commons»
+ferdig og publisert.  Følgende pressemelding ble nettopp sendt ut:

 
 

-&lt;p&gt;&lt;blockquote&gt;
-.../sakarkiv/journalpost?filter=contains(tittel, &#39;nabovarsel&#39;)
-&lt;/blockquote&gt;&lt;/p&gt;
+&lt;blockquote&gt;
+
+&lt;p&gt;&lt;strong&gt;Boken «Made with Creative Commons» lanseres på norsk&lt;/strong&gt;&lt;/p&gt;
+
+&lt;p&gt;«Gjort med Creative Commons» er en bok om gjenbruk, deling og den
+digitale allmenningen. Boken omhandler å bygge en forretningsmodell på
+åpne verdier, endringene i tankesett og filosofi, og fordelene og
+praksisen som kommer med å være «åpen».&lt;/p&gt;
+  
+&lt;p&gt;Forfatterne Paul Stacey og Sarah Hinchliff Pearson tar oss med inn
+i samtaler med 24 mennesker, prosjekter og organisasjoner som på ulike
+måter generere inntekter gjennom deling av sine verk. Som leser får
+man innsikt i hvordan alt fra forskere, forfattere, kunstnere og
+filmskapere tjener penger basert på åpne forretningsmodeller. En av
+referansestudiene i denne boken viser hvordan Blender Animation Studio
+lager vakre animasjonsfilmer som de publiserer under en fri lisens,
+basert på en plattform som er fri programvare.&lt;/p&gt;
+
+&lt;p&gt;Utover praktiske eksempler på forskjellige forretningsmodeller berører
+også boken forskjellen mellom tradisjonelle kommersielle virksomheter og
+de som tar utgangspunkt i den globale delingskulturen.&lt;/p&gt;
+
+&lt;p&gt;«Hvis du ønsker å lære mer om digital delingskultur og Creative Commons
+er dette en bok som både vil inspirere og gi grunnleggende innsikt» sier
+leder av Creative Commons Norge, Christer Solheim Gundersen. «De siste
+årene har denne globale bevegelsen sett en betydelig vekst med totalt
+over 1,6 milliarder verk med CC-lisens tilgjengelig på nett.»
+  
+Nå er den tilgjengelig på norsk takket være liten gruppe frivillige
+entusiaster ledet av Petter Reinholdtsen. «På vegne av Creative Commons
+Norge vil jeg takke hver enkelt bidragsyter. Dette prosjektet er i seg
+selv et inspirerende eksempel på at delingskulturen også har godt
+fotfeste her i Norge.», avslutter Gundersen.&lt;/p&gt;
+
+&lt;p&gt;Boken er selvsagt fritt tilgjengelig under en Creative Commons lisens,
+og kan også kjøpes som ebok og papirutgave på blant annet Lulu.com og
+Amazon.&lt;/p&gt;
+
+&lt;p&gt;&lt;strong&gt;Lenker og kontaktinformasjon&lt;/strong&gt;&lt;/p&gt;
+
+&lt;ul&gt;
+
+&lt;li&gt;Kontaktpunkt:
+&lt;br&gt;Ole-Erik Yrvin (oeyrvin@gmail.com) og
+&lt;br&gt;Christer Solheim Gundersen (christer@goopen.no), +47 9341 1360&lt;/li&gt;

 
 

-&lt;p&gt;Spørringen over vil hente en liste av alle dine journalposter der
-tittelen til journalposten inneholder ordet &#39;nabovarsel&#39;. Alle
-leverandører som implementerer tjenestegrensesnittet vil måtte tilby
-dette.  Det betyr at hvis du lærer dette språket for et system, vil det
-være gjeldende for alle. Dette er egentlig en ny måte å søke i
-arkivdatabasen på og vil være svært nyttig, for eksempel kan søk i
-tjenestegrensesnittet antagelig brukes til å hente ut offentlig
-postjournal. I arkivverden pleier vi å like teknologier som er
-menneskelesbart, da vet vi det er enkelt og nyttig! OData er også
-viktig fordi det kan bli en ny måte å svare innsynsforespørsler på i
-tråd med offentlighetsloven § 9, der retten til å kreve innsyn i
-sammenstilling fra databaser er nedfelt. I dag ser vi
-forvaltningsorganer som avviser slike krav fordi det «ikke kan gjøres
-med enkle framgangsmåter». Bruken av OData i tjenestegrensesnittet,
-sammen med maskinlesbar markeringsformater kan være et viktig bidrag
-til å åpne arkivene i tråd med prinsippene om en åpen og transparent
-forvaltning.&lt;/p&gt;
-
-&lt;p&gt;Standardisering er viktig fordi det &lt;em&gt;kan&lt;/em&gt; sikre samvirke.
-Men den effekten kommer kun hvis standardiseringen sikrer at alle
-forstår standarden på samme måte, dvs. at den er entydig og klar.  En
-god måte å sikre en entydig og klar spesifikasjon er ved å kreve at
-det finnes minst to ulike implementasjoner som følger spesifikasjonen
-og som kan snakke sammen, det vil si at de snakker samme språk, slik
-IETF krever for alle sine standarder, før spesifikasjonen anses å være
-ferdig. Tilbakemelding fra miljøet forteller at både leverandører og
-kunder har et avslappet forhold til Noark 5 Tjenestegrensesnitt og det
-er så langt kun Evry som har visst offentlig at de har en
-implementasjon av tjenestegrensesnittet.  Evry, HK Data og Fredrikstad
-kommune er igang med et pilotprosjekt på Noark 5
-Tjenestegrensesnitt. For å redusere kostnadene for samvirkende
-datasystemer betraktelig, er det veldig viktig at vi kommer i en
-situasjon der alle leverandører har sine egne implementasjoner av
-tjenestegrensesnittet, og at disse oppfører seg likt og i tråd med det
-som er beskrevet i spesifikasjonen.&lt;/p&gt;
-
-&lt;p&gt;Det er her fri programvare spiller en viktig rolle. Med en uklar
-standard blir det som en polsk riksdag, der ingenting fungerer. Nikita
-er en fri programvareimplementasjon av tjenestegrensesnitt og kan
-fungere som teknisk referanse slik at leverandører enklere kan se og
-forstå hvordan standarden skal tolkes. Vi har i Nikitaprosjektet
-erfart å ende opp med vidt forskjellige tolkninger når
-prosjektmedlemmene leser spesifikasjonsteksten, en effekt av en uklar
-spesifikasjon. Men Nikitaprosjektet har også utviklet et test-program
-som sjekker om et tjenestegrensesnitt er i samsvar med standarden, og
-prosjektet bruker det hele tiden for å sikre at endringer og
-forbedringer fungerer. Egenerklæringsskjemaenes dager kan være talte!
-Snart vil du selv kunne teste hver oppdatering av arkivsystemet med en
-uavhengig sjekk.&lt;/p&gt;
-
-&lt;p&gt;Fri programvare representerer en demokratisering av kunnskap der
-tolkning- og innlåsingsmakt flyttes fra leverandør til allmenheten.
-Med fri programvare har du en litt annerledes verdikjede, der selve
-produktet ikke holdes hemmelig for å tjene penger, slik en gjør med
-ufri programvare og skytjenester som ikke bruker fri programvare, men
-du kan tjene penger på andre deler av verdikjeden. Med fri programvare
-kan samfunnet betale for å videreutvikle nyttig
-fellesfunksjonalitet.&lt;/p&gt;
-
-&lt;p&gt;Nikita er en fri programvareimplementasjon av tjenestegrensesnittet og
-kan fungere som en referanseimplementasjon dersom det er ønskelig.
-Alle har lik tilgang til koden og det koster ingenting å ta den i bruk
-og utforske det. Nikitaprosjektet ønsker tjenestegrensesnittet
-velkommen og stiller veldig gjerne opp i diskusjoner om tolkning av
-tjenestegrensesnittet. Nikita er bygget på moderne
-programmeringsrammeverk og utviklet i full åpenhet. Men Nikita er ikke
-noe du kan kjøpe. Nikita er først og fremst et verktøy for forsking og
-utvikling laget for å fremme forskning på arkivfeltet.  Systemer som
-virker sammen har alltid vært hovedfokus og vil være det fremover.
-Det brukes som undervisningsverktøy der studentene ved OsloMet lærer
-om administrativt oppsett, saksbehandling, uttrekk og samvirkende
-datasystemer.  Det brukes også som forskningsobjekt der vi ser på
-import av dokumentsamlinger, bruk av blokkjede og andre nyskapende
-måter å tenke arkiv på. Det er dog helt greit om andre tar Nikita og
-pakker det for å selge det som produkt.  Forvaltningsorganer med
-sterke drift- og utviklingsmiljøer kan også se på Nikita og utforske
-hva som er mulig. Dette kan de gjøre uten å måtte betale for
-bruksrettigheter eller tilgang til konsulenter.  Men arkivering blir
-ikke gratis på grunn av Nikita.  Det trengs fortsatt folk med
-kompetanse og tid til å ta i bruk Nikita.&lt;/p&gt;
-
-&lt;p&gt;Nikita har nylig kommet med en ny utgave, den sjette i rekken.
-Systemet er ikke ferdig, mest på grunn av at API-spesifikasjonen for
-Noark 5 Tjenestegrensesnitt ikke er ferdig, men allerede i dag kan en
-bruke Nikita som arkiv.  Vi har laget eksempelsystem for å importere
-data fra deponi-XML og slik gjøre eksisterende arkivdata tilgjengelig
-via et API.  Vi har også laget en testklient som importerer epost inn
-i arkivet med vedlegg der epostenes trådinformasjon brukes til å legge
-eposttråder i samme arkivmappe, og en annen testklient som henter
-epost ut av en arkivmappe på mbox-format slik at en vanlig epostklient
-kan brukes til å lese igjennom og svare på epostene i en
-arkivmappe. De som vil ta en titt på Nikita kan besøke
-&lt;a href=&quot;https://nikita.oslomet.no&quot;&gt;https://nikita.oslomet.no&lt;/a&gt; og
-logge inn med brukernavn «admin@example.com» og passord «password».
-Dette gir tilgang til det forenklede brukergrensesnittet som brukes
-til undervisning.  De som heller vil ta en titt under panseret kan
-besøke
-&lt;a href=&quot;https://nikita.oslomet.no/browse.html&quot;&gt;https://nikita.oslomet.no/browse.html&lt;/a&gt;
-og der se hvordan API-et fungerer mer i detalj.  Innloggingsdetaljer
-her er det samme som for brukergrensesnittet.&lt;/p&gt;
-
-&lt;p&gt;Fremover er fokuset på forbedring av spesifikasjonen Noark 5
-Tjenestegrensesnitt. De som skrev tjenestegrensesnittet gjorde et
-interessant og framtidsrettet grep, de skilte sak fra arkiv.
-Tjenestegrensesnittet består av flere &quot;pakker&quot;, der noen er
-grunnleggende mens andre bygger på de grunnleggende pakkene. Pakkene
-som er beskrevet så langt heter «arkivstruktur», «sakarkiv»,
-«administrasjon», «loggogsporing» og «moeter» (dessverre
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/pull/120&quot;&gt;planlagt
-fjernet&lt;/a&gt; i første utgave).  Etter hvert håper vi å utforske
-prosses- og metadatabeskrivelser til flere fagområder og bidra til at
-tjenestegrensesnittet kan legge til flere pakker som «byggarkiv»,
-«barnevern», «personal», «barnehage», der arkivfaglig metadata- og
-dokumentasjonsbehov er kartlagt og standardisert.&lt;/p&gt;
-
-&lt;p&gt;Nikita utvikles av en liten prosjektgruppe, og vi er alltid
-interessert å bli flere. Hvis en åpen, fri og standardisert tilnærming
-til arkivering høres interessant ut, bli med oss på veien videre.  Vi
-er tilstede på IRC-kanalen #nikita hos FreeNode (tilgjengelig via
-nettleser på
-&lt;a href=&quot;https://webchat.freenode.net?channels=#nikita&quot;&gt;https://webchat.freenode.net?channels=#nikita&lt;/a&gt;),
-og har en e-postliste nikita-noark@nuug.no hos NUUG (tilgjengelig for
-påmelding og arkiv på
-&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;https://lists.nuug.no/mailman/listinfo/nikita-noark&lt;/a&gt;)
-der en kan følge med eller være med oss på den spennende veien videre.
-Spesifikasjonen for Noark 5 Tjenestegrensesnitt vedlikeholdes på
-github,
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/&quot;&gt;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/&lt;/a&gt;.&lt;/p&gt;
+&lt;li&gt;Bokens &lt;a href=&quot;https://madewith.cc/&quot;&gt;engelske nettside&lt;/a&gt;&lt;/li&gt;
+
+&lt;li&gt;Den &lt;a href=&quot;http://www.hungry.com/~pere/publisher/&quot;&gt;norske utgavens nettside&lt;/a&gt;&lt;/li&gt;
+
+&lt;li&gt;&lt;a href=&quot;https://www.lulu.com/en/us/shop/sarah-hinchliff-pearson-and-paul-stacey-and-bryan-mathers-and-ryan-merkley/gjort-med-creative-commons/paperback/product-m5jy75.html&quot;&gt;Papirutgaven fra Lulu&lt;/a&gt;&lt;/li&gt;
+
+&lt;li&gt;&lt;a href=&quot;https://www.lulu.com/en/us/shop/sarah-hinchliff-pearson-and-paul-stacey-and-bryan-mathers-and-ryan-merkley/gjort-med-creative-commons/ebook/product-zw2r4k.html&quot;&gt;Epub-utgaven fra lulu&lt;/a&gt;&lt;/li&gt;
+
+&lt;/ul&gt;
+
+&lt;/blockquote&gt;
+
+&lt;p&gt;Nå håper jeg bare den får mange lesere, og finner veien under mange
+juletrær.&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;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>
+               <title>Buster based Bokmål edition of Debian Administrator&#39;s Handbook</title>
+               <link>http://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
+                <pubDate>Tue, 20 Oct 2020 18:35:00 +0200</pubDate>
+               <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2020-10-20-debian-handbook-nb-testprint.jpeg&quot; width=&quot;60%&quot;/&gt;&lt;/p&gt;
+
+&lt;p&gt;I am happy to report that we finally made it!  Norwegian Bokmål
+became the first translation published on paper of the new Buster
+based edition of &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
+Administrator&#39;s Handbook&lt;/a&gt;&quot;.  The print proof reading copy arrived
+some days ago, and it looked good, so now the book is approved for
+general distribution.  This updated paperback edition &lt;a
+href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available from
+lulu.com&lt;/a&gt;.  The book is also available for download in electronic
+form as PDF, EPUB and Mobipocket, and can also be
+&lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;I am very happy to wrap up this Creative Common licensed project,
+which concludes several months of work by several volunteers. The
+number of Linux related books published in Norwegian are few, and I
+really hope this one will gain many readers, as it is packed with deep
+knowledge on Linux and the Debian ecosystem.  The book will be
+available for various Internet book stores like Amazon and Barnes &amp;
+Noble soon, but I recommend buying
+&quot;&lt;a href=&quot;https://www.lulu.com/en/us/shop/roland-mas-and-rapha%C3%ABl-hertzog/h%C3%A5ndbok-for-debian-administratoren/paperback/product-9j7qwq.html&quot;&gt;Håndbok
+for Debian-administratoren&lt;/a&gt;&quot; directly from the source at Lulu.
+
+&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>
 &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>Jami/Ring, finally functioning peer to peer communication client</title>
-               <link>http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
-                <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
-               <description>&lt;p&gt;Some years ago, in 2016, I
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html&quot;&gt;wrote
-for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
-It would provide messaging without any central server coordinating the
-system and without requiring all users to register a phone number or
-own a mobile phone.  Back then, I could not get it to work, and put it
-aside until it had seen more development.  A few days ago I decided to
-give it another try, and am happy to report that this time I am able
-to not only send and receive messages, but also place audio and video
-calls.  But only if UDP is not blocked into your network.&lt;/p&gt;
-
-&lt;p&gt;The Ring system changed name earlier this year to
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;.  I
-tried doing web search for &#39;ring&#39; when I discovered it for the first
-time, and can only applaud this change as it is impossible to find
-something called Ring among the noise of other uses of that word.  Now
-you can search for &#39;jami&#39; and this client and
-&lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
-least on duckduckgo.&lt;/p&gt;
-
-&lt;p&gt;Jami will by default encrypt messages as well as audio and video
-calls, and try to send them directly between the communicating parties
-if possible.  If this proves impossible (for example if both ends are
-behind NAT), it will use a central SIP TURN server maintained by the
-Jami project.  Jami can also be a normal SIP client.  If the SIP
-server is unencrypted, the audio and video calls will also be
-unencrypted.  This is as far as I know the only case where Jami will
-do anything without encryption.&lt;/p&gt;
-
-&lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
-Android, iOS, and Android TV.  It is included in Debian already.  Jami
-also work for those using F-Droid without any Google connections,
-while Signal do not.
-&lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
-protocol&lt;/a&gt; is described in the Ring project wiki.  The system uses a
-distributed hash table (DHT) system (similar to BitTorrent) running
-over UDP.  On one of the networks I use, I discovered Jami failed to
-work.  I tracked this down to the fact that incoming UDP packages
-going to ports 1-49999 were blocked, and the DHT would pick a random
-port and end up in the low range most of the time.  After talking to
-the developers, I solved this by enabling the dhtproxy in the
-settings, thus using TCP to talk to a central DHT proxy instead of
-
-peering directly with others.  I&#39;ve been told the developers are
-working on allowing DHT to use TCP to avoid this problem.  I also ran
-into a problem when trying to talk to the version of Ring included in
-Debian Stable (Stretch).  Apparently the protocol changed between
-beta2 and the current version, making these clients incompatible.
-Hopefully the protocol will not be made incompatible in the
-future.&lt;/p&gt;
-
-&lt;p&gt;It is worth noting that while looking at Jami and its features, I
-came across another communication platform I have not tested yet.  The
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
-and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;.  It might
-become the topic of a future blog post.&lt;/p&gt;
+               <title>Buster update of Norwegian Bokmål edition of Debian Administrator&#39;s Handbook almost done</title>
+               <link>http://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html</guid>
+                <pubDate>Fri, 11 Sep 2020 09:45:00 +0200</pubDate>
+               <description>&lt;p&gt;Thanks to the good work of several volunteers, the updated edition
+of the Norwegian translation for
+&quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
+Handbook&lt;/a&gt;&quot; is now almost completed.  After many months of proof
+reading, I consider the proof reading complete enough for us to move
+to the next step, and have asked for the print version to be prepared
+and sent of to the print on demand service lulu.com.  While it is
+still not to late if you find any incorrect translations on
+&lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
+hosted Weblate service&lt;/a&gt;, but it will be soon. :) You can check out
+&lt;a href=&quot; https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;the Buster
+edition on the web&lt;/a&gt; until the print edition is ready.&lt;/p&gt;
+
+&lt;p&gt;The book will be for sale on lulu.com and various web book stores,
+with links available from the web site for the book linked to above.
+I hope a lot of readers find it useful.&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;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address


@@ -677,116 +691,94 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
        </item>
        
        <item>

-               <title>More sales number for my Free Culture paper editions (2019-edition)</title>
-               <link>http://people.skolelinux.org/pere/blog/More_sales_number_for_my_Free_Culture_paper_editions__2019_edition_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_sales_number_for_my_Free_Culture_paper_editions__2019_edition_.html</guid>
-                <pubDate>Tue, 11 Jun 2019 16:05:00 +0200</pubDate>
-               <description>&lt;p&gt;The first book I published,
-&lt;a href=&quot;http://www.free-culture.cc/&quot;&gt;Free Culture by Lawrence
-Lessig&lt;/a&gt;, is still selling a few copies.  Not a lot, but enough to
-have contributed slightly over $500 to the &lt;a
-href=&quot;https://creativecommons.org/&quot;&gt;Creative Commons Corporation&lt;/a&gt;
-so far.  All the profit is sent there. Most books are still sold via
-Amazon (83 copies), with Ingram second (49) and Lulu (12) and Machette (7) as
-minor channels.  Bying directly from Lulu bring the largest cut to
-Creative Commons.  The English Edition sold 80 copies so far, the
-French 59 copies, and Norwegian only 8 copies.  Nothing impressive,
-but nice to see the work we put down is still being appreciated.  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;7&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-jun&lt;/th&gt;
-&lt;th&gt;2017 jul-dec&lt;/th&gt;
-&lt;th&gt;2018 jan-jun&lt;/th&gt;
-&lt;th&gt;2018 jul-dec&lt;/th&gt;
-&lt;th&gt;2019 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;19&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;11&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;6&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;7&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;td align=&quot;right&quot;&gt;0&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;0&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;td align=&quot;right&quot;&gt;9&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;3&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;35&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;20&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;10&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;13&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;10&lt;/td&gt;
-&lt;/tr&gt;
-
-&lt;/table&gt;
-
-&lt;p&gt;It is fun to see the French edition being more popular than the
-English one.&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>Working on updated Norwegian Bokmål edition of Debian Administrator&#39;s Handbook</title>
+               <link>http://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
+                <pubDate>Sat, 4 Jul 2020 23:55:00 +0200</pubDate>
+               <description>&lt;p&gt;Three years ago, the first Norwegian Bokmål edition of
+&quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
+Handbook&lt;/a&gt;&quot; was published.  This was based on Debian Jessie.  Now a
+new and updated version based on Buster is getting ready.  Work on the
+updated Norwegian Bokmål edition has been going on for a few months
+now, and yesterday, we reached the first mile stone, with 100% of the
+texts being translated.  A lot of proof reading remains, of course,
+but a major step towards a new edition has been taken.&lt;/p&gt;
+
+&lt;p&gt;The book is translated by volunteers, and we would love to get some
+help with the proof reading.  The translation uses
+&lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
+hosted Weblate service&lt;/a&gt;, and we welcome everyone to have a look and
+submit improvements and suggestions.  There is also a proof readers
+PDF available on request, get in touch if you want to help out that
+way.&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>Official MIME type &quot;text/vnd.sosi&quot; for SOSI map data</title>
-               <link>http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html</guid>
-                <pubDate>Tue, 4 Jun 2019 09:20:00 +0200</pubDate>
-               <description>&lt;p&gt;Just 15 days ago,
-&lt;ahref=&quot;http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html&quot;&gt;I
-mentioned&lt;/a&gt; my submission to IANA to register an official MIME type
-for the SOSI vector map format.  This morning, just an hour ago, I was
-notified that
-&lt;a href=&quot;https://www.iana.org/assignments/media-types/text/vnd.sosi&quot;&gt;the
-MIME type &quot;text/vnd.sosi&quot;&lt;/a&gt; is registered for this format.  In
-addition to this registration, my
-&lt;a href=&quot;https://github.com/file/file/blob/master/magic/Magdir/sosi&quot;&gt;file(1)
-patch for a pattern matching rule for SOSI files&lt;/a&gt; has been accepted
-into the official source of that program (pending a new release), and
-I&#39;ve been told by the team behind
-&lt;a href=&quot;https://www.nationalarchives.gov.uk/PRONOM/&quot;&gt;PRONOM&lt;/a&gt; that
-the SOSI format will be included in the next release of PRONOM, which
-they plan to release this summer around July.&lt;/p&gt;
-
-&lt;p&gt;I am very happy to see all of this fall into place, for use by
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/&quot;&gt;the
-Noark 5 Tjenestegrensesnitt&lt;/a&gt; implementations.&lt;/p&gt;
+               <title>Secure Socket API - a simple and powerful approach for TLS support in software</title>
+               <link>http://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</guid>
+                <pubDate>Sat, 6 Jun 2020 12:40:00 +0200</pubDate>
+               <description>&lt;p&gt;As a member of the &lt;a href=&quot;https://www.nuug.no/&quot;&gt;Norwegian Unix
+User Group&lt;/a&gt;, I have the pleasure of receiving the
+&lt;a href=&quot;https://www.usenix.org/&quot;&gt;USENIX&lt;/a&gt; magazine
+&lt;a href=&quot;https://www.usenix.org/publications/login/&quot;&gt;;login:&lt;/a&gt;
+several times a year.  I rarely have time to read all the articles,
+but try to at least skim through them all as there is a lot of nice
+knowledge passed on there.  I even carry the latest issue with me most
+of the time to try to get through all the articles when I have a few
+spare minutes.&lt;/p&gt;
+
+&lt;p&gt;The other day I came across a nice article titled
+&quot;&lt;a href=&quot;https://www.usenix.org/publications/login/winter2018/oneill&quot;&gt;The
+Secure Socket API: TLS as an Operating System Service&lt;/a&gt;&quot; with a
+marvellous idea I hope can make it all the way into the POSIX standard.
+The idea is as simple as it is powerful.  By introducing a new
+socket() option IPPROTO_TLS to use TLS, and a system wide service to
+handle setting up TLS connections, one both make it trivial to add TLS
+support to any program currently using the POSIX socket API, and gain
+system wide control over certificates, TLS versions and encryption
+systems used.  Instead of doing this:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;the program code would be doing this:&lt;p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;According to the ;login: article, converting a C program to use TLS
+would normally modify only 5-10 lines in the code, which is amazing
+when compared to using for example the OpenSSL API.&lt;/p&gt;
+
+&lt;p&gt;The project has set up the
+&lt;a href=&quot;https://securesocketapi.org/&quot;&gt;https://securesocketapi.org/&lt;/a&gt;
+web site to spread the idea, and the code for a kernel module and the
+associated system daemon is available from two github repositories:
+&lt;a href=&quot;https://github.com/markoneill/ssa&quot;&gt;ssa&lt;/a&gt; and
+&lt;a href=&quot;https://github.com/markoneill/ssa-daemon&quot;&gt;ssa-daemon&lt;/a&gt;.
+Unfortunately there is no explicit license information with the code,
+so its copyright status is unclear.  A
+&lt;a href=&quot;https://github.com/markoneill/ssa/issues/2&quot;&gt;request to solve
+this&lt;/a&gt; about it has been unsolved since 2018-08-17.&lt;/p&gt;
+
+&lt;p&gt;I love the idea of extending socket() to gain TLS support, and
+understand why it is an advantage to implement this as a kernel module
+and system wide service daemon, but can not help to think that it
+would be a lot easier to get projects to move to this way of setting
+up TLS if it was done with a user space approach where programs
+wanting to use this API approach could just link with a wrapper
+library.&lt;/p&gt;
+
+&lt;p&gt;I recommend you check out this simple and powerful approach to more
+secure network connections. :)&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;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address