<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/CasparCG_Server_for_TV_broadcast_playout_in_Debian.html">CasparCG Server for TV broadcast playout in Debian</a></div>
- <div class="date">15th January 2019</div>
- <div class="body"><p>The layered video playout server created by Sveriges Television,
-<a href="https://casparcg.com/">CasparCG Server</a>, entered Debian
-today. This completes many months of work to get the source ready to
-go into Debian. The first upload to the Debian NEW queue happened a
-month ago, but the work upstream to prepare it for Debian started more
-than two and a half month ago. So far
-<a href="https://tracker.debian.org/pkg/casparcg-server">the
-casparcg-server package</a> is only available for amd64, but I hope
-this can be improved. The package is in contrib because it depend on
-the <a href="https://tracker.debian.org/pkg/fdk-aac">non-free fdk-aac
-library</a>. The Debian package lack support for streaming web pages
-because Debian is missing CEF, Chromium Embedded Framework. CEF is
-wanted by several packages in Debian. But because the Chromium source
-is <a href="https://bugs.debian.org/893448">not available as a build
-dependency</a>, it is not yet possible to upload CEF to Debian. I
-hope this will change in the future.</p>
-
-<p>The reason I got involved is that
-<a href="https://frikanalen.no/">the Norwegian open channel
-Frikanalen</a> is starting to use CasparCG for our HD playout, and I
-would like to have all the free software tools we use to run the TV
-channel available as packages from the Debian project. The last
-remaining piece in the puzzle is Open Broadcast Encoder, but it depend
-on quite a lot of patched libraries which would have to be included in
-Debian first.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/When_terms_and_policy_turn_users_away.html">When terms and policy turn users away</a></div>
+ <div class="date"> 7th December 2019</div>
+ <div class="body"><p>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:</p>
+
+<blockquote>
+From: Petter Reinholdtsen
+<br>Subject: When terms of use turn users away
+<br>To: [contact@some.site]
+<br>Date: Sat, 07 Dec 2019 16:30:56 +0100
+
+<p>Dear [Site Owner],</p>
+
+<p>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 <URL:
+https://www.[some.site]/terms-of-use > and <URL:
+https://www.[some.site]/privacy-policy > 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.</p>
+
+<p>--
+<br>Happy hacking
+<br>Petter Reinholdtsen</p>
+</blockquote>
+
+<p>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...</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html">Learn to program with Minetest on Debian</a></div>
- <div class="date">15th December 2018</div>
- <div class="body"><p>A fun way to learn how to program
-<a href="https://www.python.org/">Python</a> is to follow the
-instructions in the book
-"<a href="https://nostarch.com/programwithminecraft">Learn to program
-with Minecraft</a>", which introduces programming in Python to people
-who like to play with Minecraft. The book uses a Python library to
-talk to a TCP/IP socket with an API accepting build instructions and
-providing information about the current players in a Minecraft world.
-The TCP/IP API was first created for the Minecraft implementation for
-Raspberry Pi, and has since been ported to some server versions of
-Minecraft. The book contain recipes for those using Windows, MacOSX
-and Raspian. But a little known fact is that you can follow the same
-recipes using the free software construction game
-<a href="https://minetest.net/">Minetest</a>.</p>
-
-<p>There is <a href="https://github.com/sprintingkiwi/pycraft_mod">a
-Minetest module implementing the same API</a>, making it possible to
-use the Python programs coded to talk to Minecraft with Minetest too.
-I
-<a href="https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html">uploaded
-this module</a> to Debian two weeks ago, and as soon as it clears the
-FTP masters NEW queue, learning to program Python with Minetest on
-Debian will be a simple 'apt install' away. The Debian package is
-maintained as part of the Debian Games team, and
-<a href="https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft">the
-packaging rules</a> are currently located under 'unfinished' on
-Salsa.</p>
-
-<p>You will most likely need to install several of the Minetest
-modules in Debian for the examples included with the library to work
-well, as there are several blocks used by the example scripts that are
-provided via modules in Minetest. Without the required blocks, a
-simple stone block is used instead. My initial testing with a analog
-clock did not get gold arms as instructed in the python library, but
-instead used stone arms.</p>
-
-<p>I tried to find a way to add the API to the desktop version of
-Minecraft, but were unable to find any working recipes. The
-<a href="https://www.epiphanydigest.com/tag/minecraft-python-api/">recipes</a>
-I <a href="https://github.com/kbsriram/mcpiapi">found</a> are only
-working with a standalone Minecraft server setup. Are there any
-options to use with the normal desktop version?</p>
-
-<p>As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/What_would_it_cost_to_store_all_2018_phone_calls_in_Norway_.html">What would it cost to store all 2018 phone calls in Norway?</a></div>
+ <div class="date">25th November 2019</div>
+ <div class="body"><p>Four years ago, I did a back of the envelope calculation on
+<a href="http://people.skolelinux.org/pere/blog/What_would_it_cost_to_store_all_phone_calls_in_Norway_.html">how
+much it would cost to store audio recordings of all the phone calls in
+Norway</a>, 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.</p>
+
+<p>The number of phone call minutes for 2018 was fetched from
+<a href="https://ekomstatistikken.nkom.no/">the NKOM statistics
+site</a>, 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.</p>
+
+<p>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.</p>
+
+<p>So, with the parameters in place, lets update the old table
+estimating cost for calls in a given year:</p>
+
+<table border="1">
+<tr><th>Year</th><th>Call minutes</th><th>Size</th><th>Price in NOK / EUR</th></tr>
+<tr><td>2005</td><td align="right">24 000 000 000</td><td align="right">1.3 PiB</td><td align="right">1 170 000 / 117 000</td></tr>
+
+<tr><td>2012</td><td align="right">18 000 000 000</td><td align="right">1.0 PiB</td><td align="right">900 000 / 90 000</td></tr>
+
+<tr><td>2013</td><td align="right">17 000 000 000</td><td align="right">950 TiB</td><td align="right">855 000 / 85 500</td></tr>
+
+<tr><td>2018</td><td align="right">7 976 244 000</td><td align="right">445 TiB</td><td align="right">401 100 / 40 110</td></tr>
+</table>
+
+<p>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.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Non_blocking_bittorrent_plugin_for_vlc.html">Non-blocking bittorrent plugin for vlc</a></div>
- <div class="date">12th December 2018</div>
- <div class="body"><p>A few hours ago, a new and improved version (2.4) of
-<a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">the VLC
-bittorrent plugin</a> was uploaded to Debian. This new version
-include a complete rewrite of the bittorrent related code, which seem
-to make the plugin non-blocking. This mean you can actually exit VLC
-even when the plugin seem to be unable to get the bittorrent streaming
-started. The new version also include support for filtering playlist
-by file extension using command line options, if you want to avoid
-processing audio, video or images. The package is currently in Debian
-unstable, but should be available in Debian testing in two days. To
-test it, simply install it like this:</p>
-
-<p><pre>
-apt install vlc-plugin-bittorrent
-</pre></p>
-
-<p>After it is installed, you can try to use it to play a file
-downloaded live via bittorrent like this:
-
-<p><pre>
-vlc https://archive.org/download/Glass_201703/Glass_201703_archive.torrent
-</pre></p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Norwegian_movies_that_might_be_legal_to_share_on_the_Internet.html">Norwegian movies that might be legal to share on the Internet</a></div>
+ <div class="date"> 1st September 2019</div>
+ <div class="body"><p>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've been able to identify some of
+them, but for some it is hard to figure out when they died.</p>
+
+</p>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.</p>
+
+<pre>
+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 'Norge's flugt over polhavet - http://www.imdb.com/title/tt0017090/
+1926-1996 ( 70 year) Med 'Maud' 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/
+</pre>
+
+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:
+
+<pre>
+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/
+</pre>
+
+<p>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.</p>
+
+</p>This is the list of 25 movies not available from the library and
+possibly no longer protected by copyright law:</p>
+
+<pre>
+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 'Stavangerfjord' 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/
+</pre>
+
+<p>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.</p>
+
+<p>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,
+<a href="https://www.imdb.com/title/tt1008007/">Mustads Mono from 1920</a>.
+The next one might be
+<a href="https://www.imdb.com/title/tt0347215/">Hvor isbjørnen ferdes
+from 1935</a> in 2024.</p>
<p>As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Retten_til_kontant_betaling_er_en_rettighet_som_m__brukes_for___beholdes.html">Retten til kontant betaling er en rettighet som må brukes for å beholdes</a></div>
- <div class="date">11th December 2018</div>
- <div class="body"><p><a href="https://www.fn.no/Om-FN/Avtaler/Menneskerettigheter/FNs-verdenserklaering-om-menneskerettigheter">FNs
-menneskerettighetserklæring</a> artikkel 13 første punkt lyder som
-følger:</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_16_000_movies_listed_on_IMDB_.html">Legal to share more than 16,000 movies listed on IMDB?</a></div>
+ <div class="date">10th August 2019</div>
+ <div class="body"><p>The recent announcement of from the New York Public Library on its
+results in
+<a href="https://www.vice.com/en_us/article/kz4e3e/millions-of-books-are-secretly-in-the-public-domain-you-can-download-them-free">identifying
+books published in the USA that are now in the public domain</a>,
+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 <a href="https://retrofilmvault.com/">Retro Film
+Vault</a> 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.</p>
+
+<p>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).</p>
+
+<p>The complete data set is available from
+<a href="https://github.com/petterreinholdtsen/public-domain-free-imdb">a
+public git repository</a>, including the scripts used to create it.</p>
+
+<p>Anyway, this is the summary of the 28 collected data sources so
+far:</p>
-<p><blockquote>
-Enhver har rett til å bevege seg fritt og til fritt å velge
-oppholdssted innenfor en stats grenser.
-</blockquote></p>
+<p><pre>
+ 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
+</pre></p>
-<p>Det er altså en menneskerett å kunne bevege seg fritt i landet.
-For å bevege seg fritt i landet, så må en kunne bevege seg uten å bli
-sporet. Det vil i dagens samfunn innebære å bevege seg uten å legge
-igjen digitale spor og uten å være radiomerket. Hvis en vet at ens
-bevegelser, hvor en befinner seg når, og hvem som befinner seg i
-nærheten, blir samlet inn og gjort tilgjengelig for fremmede, det være
-seg myndighetene eller private organisasjoner, så kan en ikke lenger
-bevege seg fritt. Dette gjør at det er en forutsetning for å ha glede
-av retten til å bevege seg fritt i landet at en motstår fristelsen til
-å legge igjen digitale spor når en betaler for seg. Rettigheter som
-ikke blir brukt, blir fjernet. Den eneste måten i dag å unngå å legge
-igjen digitale spor når en betaler for seg, er å betale med kontanter,
-samt takke nei til å legge igjen navn og adresse (slik f.eks. Elkjøp
-ber om — jeg sier de kan legge inn «anonym anonym» når
-datasystemet deres trenger et navn). Personlig anbefaler jeg å
-konsekvent bruke kontant betaling når man beveger seg rundt, for å
-bidra til forsvaret av menneskerettighetene i Norge. Kanskje noe også
-for deg? Merk at det ikke er tilstrekkelig for å unngå sporing å
-betale med kontanter, men det er et lite steg i riktig retning.</p>
-
-<p>Det er flere andre argumenter i tillegg til
-menneskerettighetsargumentet for å bruke kontanter. I går hadde
-Dagbladet en utmerket kommentar av sin journalist John Olav Egeland om
-hvilket
-<a href="https://www.dagbladet.no/kultur/kontantlost-diktatur/70543434">kontantløst
-diktatur</a> som venter oss hvis mange nok slutter å insistere på å
-betale med kontanter. Jeg anbefaler deg å lese den.</p>
+<p>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.</p>
-<p>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
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
-Merk, betaling med bitcoin er ikke anonymt. :)</p>
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Why_is_your_site_not_using_Content_Security_Policy___CSP_.html">Why is your site not using Content Security Policy / CSP?</a></div>
- <div class="date"> 9th December 2018</div>
- <div class="body"><p>Yesterday, I had the pleasure of watching on Frikanalen the OWASP
-talk by Scott Helme titled
-"<a href="https://frikanalen.no/video/626080/">What We’ve Learned From
-Billions of Security Reports</a>". I had not heard of the
-<a href="https://en.wikipedia.org/wiki/Content_Security_Policy">Content
-Security Policy standard</a> nor its ability to "call home" when a
-browser detect a policy breach (I do not follow web page design
-development much these days), and found the talk very illuminating.</p>
-
-<p>The mechanism allow a web site owner to use HTTP headers to tell
-visitors web browser which sources (internal and external) are allowed to
-be used on the web site. Thus it become possible to enforce a "only
-local content" policy despite web designers urge to fetch programs
-from random sites on the Internet, like the one
-<a href="https://securityaffairs.co/wordpress/68966/hacking/browsealoud-plugin-hack.html">enabling
-the attack</a> reported by Scott Helme earlier this year.</p>
-
-<p>Using CSP seem like an obvious thing for a site admin to implement
-to take some control over the information leak that occur when
-external sources are used to render web pages, it is a mystery more
-sites are not using CSP? It is being
-<a href="https://www.w3.org/TR/CSP/">standardized under W3C</a> these
-days, and is supposed by most web browsers</p>
-
-<p>I managed to find <a href="https://github.com/mozilla/django-csp">a
-Django middleware for implementing CSP</a> and was happy to discover
-it was already in Debian. I plan to use it to add CSP support to the
-Frikanalen web site soon.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Oppdatert_Noark_5_Tjenestegrenesnitt_versjon_1_0_for_Noark_5_5_0.html">Oppdatert Noark 5 Tjenestegrenesnitt versjon 1.0 for Noark 5.5.0</a></div>
+ <div class="date"> 5th July 2019</div>
+ <div class="body"><p>Jeg er veldig glad for å kunne fortelle at i går ble ny versjon av
+<a href="https://www.arkivverket.no/forvaltning-og-utvikling/noark-standarden/noark-5/tjenestegrensesnitt-noark5">API-spesifikasjonen
+for Noark 5 Tjenestegrensesnitt</a> 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.</p>
+
+<p>Spesifikasjonen er
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">tilgjengelig
+som markdown-filer i Arkivverkets github-prosjekt for dette</a>, og de
+aller fleste av forslagene til forbedringer fra oss som holder på med
+<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core">Nikita-prosjektet</a>
+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.</p>
+
+<p>Ellers må jeg jo si at det var hyggelig å se at min forrige
+bloggpost om tjenestegrensesnittet fikk en
+<a href="https://beta.arkivverket.no/post/186020592045/noark-5-versjon-50-tjenestegrensesnitt-10">lenke
+fra Arkivverket Beta</a>.</p>
-<p>As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+<p>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
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
+Merk, betaling med bitcoin er ikke anonymt. :)</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/New_and_improved_Frikanalen_Kodi_addon_version_0_0_3.html">New and improved Frikanalen Kodi addon version 0.0.3</a></div>
- <div class="date"> 8th November 2018</div>
- <div class="body"><p>If you read my blog regularly, you probably know I am involved in
-running and developing the <a href="https://frikanalen.no/">Norwegian
-TV channel Frikanalen</a>. It is an open channel, allowing everyone
-in Norway to publish videos on a TV channel with national coverage.
-You can think of it as Youtube for national television.
-In addition to distribution on RiksTV and Uninett, Frikanalen is also
-available as a Kodi addon. The last few days I have updated the code
-to add more features. A
-<a href="https://kodi.tv/addon/plugins-video-add-ons/frikanalen-nett-tv">new
-and improved version 0.0.3 Frikanalen addon</a> was just made
-available via the Kodi repositories. This new version include a
-option to browse videos by category, as well as free text search
-in the video archive. It will now also show the video duration in the
-video lists, which were missing earlier. A new and experimental
-link to the HD video stream currently being worked on is provided, for
-those that want to see what the <a href="https://casparcg.com/">CasparCG</a>
-output look like. The alternative is the SD video stream, generated
-using MLT. CasparCG is controlled by our
-<a href="https://github.com/Frikanalen/mltplayout/">mltplayout
-server</a> which instead of talking to mlt is giving PLAY instructions
-to the CasparCG server when it is time to start a new program.</p>
-
-<p>By now, you are probably wondering what kind of content is being
-played on the channel. These days, it is filled with technical
-presentations like those from <a href="https://www.nuug.no/">NUUG</a>,
-<a href="https://www.debconf.org/">Debconf</a>, Makercon, and TED,
-but there are also some periods with
-<a href="https://www.empo.no/">EMPT TV</a> and
-<a href="https://www.p7.no/">P7</a>.
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Teach_kids_to_protect_their_privacy___the_EDRi_way.html">Teach kids to protect their privacy - the EDRi way</a></div>
+ <div class="date"> 4th July 2019</div>
+ <div class="body"><p>Childs need to learn how to guard their privacy too. To help them,
+<a href="https://edri.org/">European Digital Rights (EDRi)</a> created
+a colorful booklet providing information on several privacy related topics,
+and tips on how to protect ones privacy in the digital age.</p>
+
+<p>The 24 page booklet titled Digital Defenders is
+<a href="https://edri.org/digital-defenders-help-kids-defend-their-privacy-around-europe">available
+in several languages</a>. Thanks to the valuable contributions from
+members of <a href="https://efn.no/">the Electronic Foundation Norway
+(EFN)</a> and others, it is also available in Norwegian Bokmål.
+If you would like to have it available in your language too,
+<a href="https://hosted.weblate.org/projects/efn/privacy4kids/">contribute
+via Weblate</a> and get in touch.</p>
+
+<p>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
+<a href="https://www.nuug.no/>">the Norwegian Unix Users Group</a> is
+organizing <a href="https://wiki.nuug.no/sommerfest2019">its yearly
+barbecue for geeks and free software zealots in the Oslo area</a>. If
+you are nearby, feel free to come by and check out the party and the
+booklet.</p>
+
+<p>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. :)</p>
<p>As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="http://people.skolelinux.org/pere/blog/tags/kodi">kodi</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html">Time for an official MIME type for patches?</a></div>
- <div class="date"> 1st November 2018</div>
- <div class="body"><p>As part of my involvement in
-<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core">the Nikita
-archive API project</a>, I've been importing a fairly large lump of
-emails into a test instance of the archive to see how well this would
-go. I picked a subset of <a href="https://notmuchmail.org/">my
-notmuch email database</a>, all public emails sent to me via
-@lists.debian.org, giving me a set of around 216 000 emails to import.
-In the process, I had a look at the various attachments included in
-these emails, to figure out what to do with attachments, and noticed
-that one of the most common attachment formats do not have
-<a href="https://www.iana.org/assignments/media-types/media-types.xhtml">an
-official MIME type</a> registered with IANA/IETF. The output from
-diff, ie the input for patch, is on the top 10 list of formats
-included in these emails. At the moment people seem to use either
-text/x-patch or text/x-diff, but neither is officially registered. It
-would be better if one official MIME type were registered and used
-everywhere.</p>
-
-<p>To try to get one official MIME type for these files, I've brought
-up the topic on
-<a href="https://www.ietf.org/mailman/listinfo/media-types">the
-media-types mailing list</a>. If you are interested in discussion
-which MIME type to use as the official for patch files, or involved in
-making software using a MIME type for patches, perhaps you would like
-to join the discussion?</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Nikita_og_Noark_5_tjenestegrensesnittet_tilbyr_ny_m_te___tenke_arkivering.html">Nikita og Noark 5 tjenestegrensesnittet tilbyr ny måte å tenke arkivering</a></div>
+ <div class="date">21st June 2019</div>
+ <div class="body"><p><em>av Thomas Sødring (OsloMet) og Petter Reinholdtsen (foreningen
+NUUG)</em></p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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:</p>
-<p>As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
+<p><blockquote>
+.../sakarkiv/journalpost?filter=contains(tittel, 'nabovarsel')
+</blockquote></p>
+
+<p>Spørringen over vil hente en liste av alle dine journalposter der
+tittelen til journalposten inneholder ordet 'nabovarsel'. 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.</p>
+
+<p>Standardisering er viktig fordi det <em>kan</em> 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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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
+<a href="https://nikita.oslomet.no">https://nikita.oslomet.no</a> 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
+<a href="https://nikita.oslomet.no/browse.html">https://nikita.oslomet.no/browse.html</a>
+og der se hvordan API-et fungerer mer i detalj. Innloggingsdetaljer
+her er det samme som for brukergrensesnittet.</p>
+
+<p>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 "pakker", 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
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/pull/120">planlagt
+fjernet</a> 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.</p>
+
+<p>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å
+<a href="https://webchat.freenode.net?channels=#nikita">https://webchat.freenode.net?channels=#nikita</a>),
+og har en e-postliste nikita-noark@nuug.no hos NUUG (tilgjengelig for
+påmelding og arkiv på
+<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">https://lists.nuug.no/mailman/listinfo/nikita-noark</a>)
+der en kan følge med eller være med oss på den spennende veien videre.
+Spesifikasjonen for Noark 5 Tjenestegrensesnitt vedlikeholdes på
+github,
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/</a>.</p>
+
+<p>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
<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/
debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/
noark5">noark5</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Measuring_the_speaker_frequency_response_using_the_AUDMES_free_software_GUI___nice_free_software.html">Measuring the speaker frequency response using the AUDMES free software GUI - nice free software</a></div>
- <div class="date">22nd October 2018</div>
- <div class="body"><p><img src="http://people.skolelinux.org/pere/blog/images/2018-10-22-audmes-measure-speakers.png" align="right" width="40%"/></p>
-
-<p>My current home stereo is a patchwork of various pieces I got on
-flee markeds over the years. It is amazing what kind of equipment
-show up there. I've been wondering for a while if it was possible to
-measure how well this equipment is working together, and decided to
-see how far I could get using free software. After trawling the web I
-came across an article from DIY Audio and Video on
-<a href="https://www.diyaudioandvideo.com/Tutorial/SpeakerResponseTesting/">Speaker
-Testing and Analysis</a> describing how to test speakers, and it listing
-several software options, among them
-<a href="https://sourceforge.net/projects/audmes/">AUDio MEasurement
-System (AUDMES)</a>. It is the only free software system I could find
-focusing on measuring speakers and audio frequency response. In the
-process I also found an interesting article from NOVO on
-<a href="http://novo.press/understanding-speaker-specifications-and-frequency-response/">Understanding
-Speaker Specifications and Frequency Response</a> and an article from
-ecoustics on
-<a href="https://www.ecoustics.com/articles/understanding-speaker-frequency-response/">Understanding
-Speaker Frequency Response</a>, with a lot of information on what to
-look for and how to interpret the graphs. Armed with this knowledge,
-I set out to measure the state of my speakers.</p>
-
-<p>The first hurdle was that AUDMES hadn't seen a commit for 10 years
-and did not build with current compilers and libraries. I got in
-touch with its author, who no longer was spending time on the program
-but gave me write access to the subversion repository on Sourceforge.
-The end result is that now the code build on Linux and is capable of
-saving and loading the collected frequency response data in CSV
-format. The application is quite nice and flexible, and I was able to
-select the input and output audio interfaces independently. This made
-it possible to use a USB mixer as the input source, while sending
-output via my laptop headphone connection. I lacked the hardware and
-cabling to figure out a different way to get independent cabling to
-speakers and microphone.</p>
-
-<p>Using this setup I could see how a large range of high frequencies
-apparently were not making it out of my speakers. The picture show
-the frequency response measurement of one of the speakers. Note the
-frequency lines seem to be slightly misaligned, compared to the CSV
-output from the program. I can not hear several of these are high
-frequencies, according to measurement from
-<a href="http://freehearingtestsoftware.com">Free Hearing Test
-Software</a>, an freeware system to measure your hearing (still
-looking for a free software alternative), so I do not know if they are
-coming out out the speakers. I thus do not quite know how to figure
-out if the missing frequencies is a problem with the microphone, the
-amplifier or the speakers, but I managed to rule out the audio card in my
-PC by measuring my Bose noise canceling headset using its own
-microphone. This setup was able to see the high frequency tones, so
-the problem with my stereo had to be in the amplifier or speakers.</p>
-
-<p>Anyway, to try to role out one factor I ended up picking up a new
-set of speakers at a flee marked, and these work a lot better than the
-old speakers, so I guess the microphone and amplifier is OK. If you
-need to measure your own speakers, check out AUDMES. If more people
-get involved, perhaps the project could become good enough to
-<a href="https://bugs.debian.org/910876">include in Debian</a>? And if
-you know of some other free software to measure speakers and amplifier
-performance, please let me know. I am aware of the freeware option
-<a href="https://www.roomeqwizard.com/">REW</a>, but I want something
-that can be developed also when the vendor looses interest.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html">Jami/Ring, finally functioning peer to peer communication client</a></div>
+ <div class="date">19th June 2019</div>
+ <div class="body"><p>Some years ago, in 2016, I
+<a href="http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html">wrote
+for the first time about</a> 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.</p>
+
+<p>The Ring system changed name earlier this year to
+<a href="https://en.wikipedia.org/wiki/Jami_(software)">Jami</a>. I
+tried doing web search for 'ring' 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 'jami' and this client and
+<a href="https://jami.net/">the Jami system</a> is the first hit at
+least on duckduckgo.</p>
+
+<p>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.</p>
+
+<p>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.
+<a href="https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol">The
+protocol</a> 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'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.</p>
+
+<p>It is worth noting that while looking at Jami and its features, I
+came across another communication platform I have not tested yet. The
+<a href="https://en.wikipedia.org/wiki/Tox_(protocol)">Tox protocol</a>
+and <a href="https://tox.chat/">family of Tox clients</a>. It might
+become the topic of a future blog post.</p>
<p>As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html">Web browser integration of VLC with Bittorrent support</a></div>
- <div class="date">21st October 2018</div>
- <div class="body"><p>Bittorrent is as far as I know, currently the most efficient way to
-distribute content on the Internet. It is used all by all sorts of
-content providers, from national TV stations like
-<a href="https://www.nrk.no/">NRK</a>, Linux distributors like
-<a href="https://www.debian.org/">Debian</a> and
-<a href="https://www.ubuntu.com/">Ubuntu</a>, and of course the
-<a href="https://archive.org/">Internet archive</A>.
-
-<p>Almost a month ago
-<a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">a new
-package adding Bittorrent support to VLC</a> became available in
-Debian testing and unstable. To test it, simply install it like
-this:</p>
-
-<p><pre>
-apt install vlc-plugin-bittorrent
-</pre></p>
-
-<p>Since the plugin was made available for the first time in Debian,
-several improvements have been made to it. In version 2.2-4, now
-available in both testing and unstable, a desktop file is provided to
-teach browsers to start VLC when the user click on torrent files or
-magnet links. The last part is thanks to me finally understanding
-what the strange x-scheme-handler style MIME types in desktop files
-are used for. By adding x-scheme-handler/magnet to the MimeType entry
-in the desktop file, at least the browsers Firefox and Chromium will
-suggest to start VLC when selecting a magnet URI on a web page. The
-end result is that now, with the plugin installed in Buster and Sid,
-one can visit any
-<a href="https://archive.org/details/CopyingIsNotTheft1080p">Internet
-Archive page with movies</a> using a web browser and click on the
-torrent link to start streaming the movie.</p>
-
-<p>Note, there is still some misfeatures in the plugin. One is the
-fact that it will hang and
-<a href="https://github.com/johang/vlc-bittorrent/issues/13">block VLC
-from exiting until the torrent streaming starts</a>. Another is the
-fact that it
-<a href="https://github.com/johang/vlc-bittorrent/issues/9">will pick
-and play a random file in a multi file torrent</a>. This is not
-always the video file you want. Combined with the first it can be a
-bit hard to get the video streaming going. But when it work, it seem
-to do a good job.</p>
-
-<p>For the Debian packaging, I would love to find a good way to test
-if the plugin work with VLC using autopkgtest. I tried, but do not
-know enough of the inner workings of VLC to get it working. For now
-the autopkgtest script is only checking if the .so file was
-successfully loaded by VLC. If you have any suggestions, please
-submit a patch to the Debian bug tracking system.</p>
-
-<p>As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/More_sales_number_for_my_Free_Culture_paper_editions__2019_edition_.html">More sales number for my Free Culture paper editions (2019-edition)</a></div>
+ <div class="date">11th June 2019</div>
+ <div class="body"><p>The first book I published,
+<a href="http://www.free-culture.cc/">Free Culture by Lawrence
+Lessig</a>, is still selling a few copies. Not a lot, but enough to
+have contributed slightly over $500 to the <a
+href="https://creativecommons.org/">Creative Commons Corporation</a>
+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
+<a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p>
+
+<table border="0">
+<tr><th rowspan="2" valign="bottom">Title / language</th>
+<th colspan="7">Quantity</th></tr>
+<tr>
+<th>2016 jan-jun</th>
+<th>2016 jul-dec</th>
+<th>2017 jan-jun</th>
+<th>2017 jul-dec</th>
+<th>2018 jan-jun</th>
+<th>2018 jul-dec</th>
+<th>2019 jan-may</th>
+</tr>
+
+<tr>
+ <td><a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">Culture Libre / French</a></td>
+ <td align="right">3</td>
+ <td align="right">6</td>
+ <td align="right">19</td>
+ <td align="right">11</td>
+ <td align="right">7</td>
+ <td align="right">6</td>
+ <td align="right">7</td>
+</tr>
+
+<tr>
+ <td><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Fri kultur / Norwegian</a></td>
+ <td align="right">7</td>
+ <td align="right">1</td>
+ <td align="right">0</td>
+ <td align="right">0</td>
+ <td align="right">0</td>
+ <td align="right">0</td>
+ <td align="right">0</td>
+</tr>
+
+<tr>
+ <td><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">Free Culture / English</a></td>
+ <td align="right">14</td>
+ <td align="right">27</td>
+ <td align="right">16</td>
+ <td align="right">9</td>
+ <td align="right">3</td>
+ <td align="right">7</td>
+ <td align="right">3</td>
+</tr>
+
+<tr>
+ <td>Total</td>
+ <td align="right">24</td>
+ <td align="right">34</td>
+ <td align="right">35</td>
+ <td align="right">20</td>
+ <td align="right">10</td>
+ <td align="right">13</td>
+ <td align="right">10</td>
+</tr>
+
+</table>
+
+<p>It is fun to see the French edition being more popular than the
+English one.</p>
+
+<p>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.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html">Release 0.2 of free software archive system Nikita announced</a></div>
- <div class="date">18th October 2018</div>
- <div class="body"><p>This morning, the new release of the
-<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita
-Noark 5 core project</a> was
-<a href="https://lists.nuug.no/pipermail/nikita-noark/2018-October/000406.html">announced
-on the project mailing list</a>. The free software solution is an
-implementation of the Norwegian archive standard Noark 5 used by
-government offices in Norway. These were the changes in version 0.2
-since version 0.1.1 (from NEWS.md):
-
-<ul>
- <li>Fix typos in REL names</li>
- <li>Tidy up error message reporting</li>
- <li>Fix issue where we used Integer.valueOf(), not Integer.getInteger()</li>
- <li>Change some String handling to StringBuffer</li>
- <li>Fix error reporting</li>
- <li>Code tidy-up</li>
- <li>Fix issue using static non-synchronized SimpleDateFormat to avoid
- race conditions</li>
- <li>Fix problem where deserialisers were treating integers as strings</li>
- <li>Update methods to make them null-safe</li>
- <li>Fix many issues reported by coverity</li>
- <li>Improve equals(), compareTo() and hash() in domain model</li>
- <li>Improvements to the domain model for metadata classes</li>
- <li>Fix CORS issues when downloading document</li>
- <li>Implementation of case-handling with registryEntry and document upload</li>
- <li>Better support in Javascript for OPTIONS</li>
- <li>Adding concept description of mail integration</li>
- <li>Improve setting of default values for GET on ny-journalpost</li>
- <li>Better handling of required values during deserialisation </li>
- <li>Changed tilknyttetDato (M620) from date to dateTime</li>
- <li>Corrected some opprettetDato (M600) (de)serialisation errors.</li>
- <li>Improve parse error reporting.</li>
- <li>Started on OData search and filtering.</li>
- <li>Added Contributor Covenant Code of Conduct to project.</li>
- <li>Moved repository and project from Github to Gitlab.</li>
- <li>Restructured repository, moved code into src/ and web/.</li>
- <li>Updated code to use Spring Boot version 2.</li>
- <li>Added support for OAuth2 authentication.</li>
- <li>Fixed several bugs discovered by Coverity.</li>
- <li>Corrected handling of date/datetime fields.</li>
- <li>Improved error reporting when rejecting during deserializatoin.</li>
- <li>Adjusted default values provided for ny-arkivdel, ny-mappe,
- ny-saksmappe, ny-journalpost and ny-dokumentbeskrivelse.</li>
- <li>Several fixes for korrespondansepart*.</li>
- <li>Updated web GUI:
- <ul>
- <li>Now handle both file upload and download.</li>
- <li>Uses new OAuth2 authentication for login.</li>
- <li>Forms now fetches default values from API using GET.</li>
- <li>Added RFC 822 (email), TIFF and JPEG to list of possible file formats.</li>
- </ul></li>
-</ul>
-
-<p>The changes and improvements are extensive. Running diffstat on
-the changes between git tab 0.1.1 and 0.2 show 1098 files changed,
-108666 insertions(+), 54066 deletions(-).</p>
-
-<p>If free and open standardized archiving API sound interesting to
-you, please contact us on IRC
-(<a href="irc://irc.freenode.net/%23nikita">#nikita on
-irc.freenode.net</a>) or email
-(<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
-mailing list</a>).</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html">Official MIME type "text/vnd.sosi" for SOSI map data</a></div>
+ <div class="date"> 4th June 2019</div>
+ <div class="body"><p>Just 15 days ago,
+<ahref="http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html">I
+mentioned</a> 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
+<a href="https://www.iana.org/assignments/media-types/text/vnd.sosi">the
+MIME type "text/vnd.sosi"</a> is registered for this format. In
+addition to this registration, my
+<a href="https://github.com/file/file/blob/master/magic/Magdir/sosi">file(1)
+patch for a pattern matching rule for SOSI files</a> has been accepted
+into the official source of that program (pending a new release), and
+I've been told by the team behind
+<a href="https://www.nationalarchives.gov.uk/PRONOM/">PRONOM</a> that
+the SOSI format will be included in the next release of PRONOM, which
+they plan to release this summer around July.</p>
+
+<p>I am very happy to see all of this fall into place, for use by
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">the
+Noark 5 Tjenestegrensesnitt</a> implementations.</p>
<p>As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/
nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/
kart">kart</a>, <a href="http://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
</div>
<li>2019
<ul>
-<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/01/">January (1)</a></li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/01/">January (4)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/02/">February (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/03/">March (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/05/">May (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/06/">June (5)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/07/">July (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/08/">August (1)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/09/">September (1)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/11/">November (1)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2019/12/">December (1)</a></li>
</ul></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (10)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/betalkontant">betalkontant (8)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (11)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (17)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (165)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (168)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (158)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (11)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (17)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (25)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (26)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (396)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (411)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (13)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (14)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (32)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (34)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (16)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (20)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (22)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/kodi">kodi (4)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (42)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (11)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (12)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/noark5">noark5 (17)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (300)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (307)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (191)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (196)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (34)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (37)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (72)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (75)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (108)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (111)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (2)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (10)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (12)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (6)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (7)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (55)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (56)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (58)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (66)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (6)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (12)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (55)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (57)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (4)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (9)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri (14)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri (17)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (72)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (73)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
projects / homepage.git / blobdiff