X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/e07c5ac9e1cf465a1f075e6e8118eda1b779a167..f8d3af1589dece3d5ee766752359559f7a52bcc0:/blog/index.rss diff --git a/blog/index.rss b/blog/index.rss index c2f0d0552e..1d9e0d03bc 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -6,6 +6,441 @@ http://people.skolelinux.org/pere/blog/ + + H, Ap, Frp og Venstre går for DNA-innsamling av hele befolkingen + http://people.skolelinux.org/pere/blog/H__Ap__Frp_og_Venstre_g_r_for_DNA_innsamling_av_hele_befolkingen.html + http://people.skolelinux.org/pere/blog/H__Ap__Frp_og_Venstre_g_r_for_DNA_innsamling_av_hele_befolkingen.html + Wed, 14 Mar 2018 14:15:00 +0100 + <p>I går kom det nok et argument for å holde seg unna det norske +helsevesenet. Da annonserte et stortingsflertall bestående av Høyre, +Arbeiderpartiet, Fremskrittspartiet og Venstre, at de går inn for å +samle inn og lagre DNA fra hele befolkningen i Norge til evig tid. +Endringen gjelder innsamlede blodprøver fra nyfødte i Norge. Det vil +dermed ta litt tid før en har hele befolkningen, men det er dit vi +havner gitt nok tid. I dag er det nesten hundre prosent oppslutning +om undersøkelsen som gjøres like etter fødselen, på bakgrunn av +blodprøven det er snakk om å lagre, for å oppdage endel medfødte +sykdommer. Blodprøven lagres i dag i inntil seks år. +<a href="https://www.stortinget.no/no/Saker-og-publikasjoner/Publikasjoner/Innstillinger/Stortinget/2017-2018/inns-201718-182l/?all=true">Stortingets +flertallsinnstilling</a> er at tidsbegresningen skal fjernes, og mener +at tidsubegrenset lagring ikke vil påvirke oppslutningen om +undersøkelsen.</p> + +<p>Datatilsynet har ikke akkurat applaudert forslaget:</p> + +<p><blockquote> + + <p>«Datatilsynet mener forslaget ikke i tilstrekkelig grad + synliggjør hvilke etiske og personvernmessige utfordringer som må + diskuteres før en etablerer en nasjonal biobank med blodprøver fra + hele befolkningen.»</p> + +</blockquote></p> + +<p>Det er flere historier om hvordan innsamlet biologisk materiale har +blitt brukt til andre formål enn de ble innsamlet til, og historien om +<a href="https://www.aftenposten.no/norge/i/Ql0WR/Na-ma-Folkehelsa-slette-uskyldiges-DNA-info">folkehelseinstituttets +lagring på vegne av politiet (Kripos) av innsamlet biologisk materiale +og DNA-informasjon i strid med loven</a> viser at en ikke kan være +trygg på at lover og intensjoner beskytter de som blir berørt mot +misbruk av slik privat og personlig informasjon.</p> + +<p>Det er verdt å merke seg at det kan forskes på de innsamlede +blodprøvene uten samtykke fra den det gjelder (eller foreldre når det +gjelder barn), etter en lovendring for en stund tilbake, med mindre +det er sendt inn skjema der en reserverer seg mot forskning uten +samtykke. Skjemaet er tilgjengelig fra +<a href="https://www.fhi.no/arkiv/publikasjoner/for-pasienter-skjema-for-reservasjo/">folkehelseinstituttets +websider</a>, og jeg anbefaler, uavhengig av denne saken, varmt alle å +sende inn skjemaet for å dokumentere hvor mange som ikke synes det er +greit å fjerne krav om samtykke.</p> + +<p>I tillegg bør en kreve destruering av alt biologisk materiale som +er samlet inn om en selv, for å redusere eventuelle negative +konsekvener i fremtiden når materialet kommer på avveie eller blir +brukt uten samtykke, men det er så vidt jeg vet ikke noe system for +dette i dag.</p> + + + + + First rough draft Norwegian and Spanish edition of the book Made with Creative Commons + http://people.skolelinux.org/pere/blog/First_rough_draft_Norwegian_and_Spanish_edition_of_the_book_Made_with_Creative_Commons.html + http://people.skolelinux.org/pere/blog/First_rough_draft_Norwegian_and_Spanish_edition_of_the_book_Made_with_Creative_Commons.html + Tue, 13 Mar 2018 13:00:00 +0100 + <p>I am working on publishing yet another book related to Creative +Commons. This time it is a book filled with interviews and histories +from those around the globe making a living using Creative +Commons.</p> + +<p>Yesterday, after many months of hard work by several volunteer +translators, the first draft of a Norwegian Bokmål edition of the book +<a href="https://madewith.cc">Made with Creative Commons from 2017</a> +was complete. The Spanish translation is also complete, while the +Dutch, Polish, German and Ukraine edition need a lot of work. Get in +touch if you want to help make those happen, or would like to +translate into your mother tongue.</p> + +<p>The whole book project started when +<a href="http://gwolf.org/node/4102">Gunnar Wolf announced</a> that he +was going to make a Spanish edition of the book. I noticed, and +offered some input on how to make a book, based on my experience with +translating the +<a href="https://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Free +Culture</a> and +<a href="https://debian-handbook.info/get/#norwegian">The Debian +Administrator's Handbook</a> books to Norwegian Bokmål. To make a +long story short, we ended up working on a Bokmål edition, and now the +first rough translation is complete, thanks to the hard work of +Ole-Erik Yrvin, Ingrid Yrvin, Allan Nordhøy and myself. The first +proof reading is almost done, and only the second and third proof +reading remains. We will also need to translate the 14 figures and +create a book cover. Once it is done we will publish the book on +paper, as well as in PDF, ePub and possibly Mobi formats.</p> + +<p>The book itself originates as a manuscript on Google Docs, is +downloaded as ODT from there and converted to Markdown using pandoc. +The Markdown is modified by a script before is converted to DocBook +using pandoc. The DocBook is modified again using a script before it +is used to create a Gettext POT file for translators. The translated +PO file is then combined with the earlier mentioned DocBook file to +create a translated DocBook file, which finally is given to dblatex to +create the final PDF. The end result is a set of editions of the +manuscript, one English and one for each of the translations.</p> + +<p>The translation is conducted using +<a href="https://hosted.weblate.org/projects/madewithcc/translation/">the +Weblate web based translation system</a>. Please have a look there +and get in touch if you would like to help out with proof +reading. :)</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> + + + + + Debian used in the subway info screens in Oslo, Norway + http://people.skolelinux.org/pere/blog/Debian_used_in_the_subway_info_screens_in_Oslo__Norway.html + http://people.skolelinux.org/pere/blog/Debian_used_in_the_subway_info_screens_in_Oslo__Norway.html + Fri, 2 Mar 2018 13:10:00 +0100 + <p>Today I was pleasantly surprised to discover my operating system of +choice, Debian, was used in the info screens on the subway stations. +While passing Nydalen subway station in Oslo, Norway, I discovered the +info screen booting with some text scrolling. I was not quick enough +with my camera to be able to record a video of the scrolling boot +screen, but I did get a photo from when the boot got stuck with a +corrupt file system: + +<p align="center"><a href="http://people.skolelinux.org/pere/blog/images/2018-03-02-ruter-debian-lenny.jpeg"><img align="center" width="40%" src="http://people.skolelinux.org/pere/blog/images/2018-03-02-ruter-debian-lenny.jpeg" alt="[photo of subway info screen]"></a></p> + +<p>While I am happy to see Debian used more places, some details of the +content on the screen worries me.</p> + +<p>The image show the version booting is 'Debian GNU/Linux lenny/sid', +indicating that this is based on code taken from Debian Unstable/Sid +after Debian Etch (version 4) was released 2007-04-08 and before +Debian Lenny (version 5) was released 2009-02-14. Since Lenny Debian +has released version 6 (Squeeze) 2011-02-06, 7 (Wheezy) 2013-05-04, 8 +(Jessie) 2015-04-25 and 9 (Stretch) 2017-06-15, according to +<a href="https://en.wikipedia.org/wiki/Debian_version_history">a Debian +version history on Wikpedia</a>. This mean the system is running +around 10 year old code, with no security fixes from the vendor for +many years.</p> + +<p>This is not the first time I discover the Oslo subway company, +Ruter, running outdated software. In 2012, +<a href="http://people.skolelinux.org/pere/blog/Er_billettautomatene_til_kollektivtrafikken_i_Oslo_uten_sikkerhetsoppdateringer_.html">I +discovered the ticket vending machines were running Windows 2000</a>, +and this was +<a href="http://people.skolelinux.org/pere/blog/Fortsatt_ingen_sikkerhetsoppdateringer_for_billettautomatene_til_kollektivtrafikken_i_Oslo_.html">still +the case in 2016</a>. Given the response from the responsible people +in 2016, I would assume the machines are still running unpatched +Windows 2000. Thus, an unpatched Debian setup come as no surprise.</p> + +<p>The photo is made available under the license terms +<a href="http://creativecommons.org/licenses/by/4.0/">Creative Commons +4.0 Attribution International (CC BY 4.0)</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> + + + + + The SysVinit upstream project just migrated to git + http://people.skolelinux.org/pere/blog/The_SysVinit_upstream_project_just_migrated_to_git.html + http://people.skolelinux.org/pere/blog/The_SysVinit_upstream_project_just_migrated_to_git.html + Sun, 18 Feb 2018 09:20:00 +0100 + <p>Surprising as it might sound, there are still computers using the +traditional Sys V init system, and there probably will be until +systemd start working on Hurd and FreeBSD. +<a href="https://savannah.nongnu.org/projects/sysvinit">The upstream +project still exist</a>, though, and up until today, the upstream +source was available from Savannah via subversion. I am happy to +report that this just changed.</p> + +<p>The upstream source is now in Git, and consist of three +repositories:</p> + +<ul> + +<li><a href="http://git.savannah.nongnu.org/cgit/sysvinit.git">sysvinit</a></li> +<li><a href="http://git.savannah.nongnu.org/cgit/sysvinit/insserv.git">insserv</a></li> +<li><a href="http://git.savannah.nongnu.org/cgit/sysvinit/startpar.git">startpar</a></li> + +</ul> + +<p>I do not really spend much time on the project these days, and I +has mostly retired, but found it best to migrate the source to a good +version control system to help those willing to move it forward.</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> + + + + + Using VLC to stream bittorrent sources + http://people.skolelinux.org/pere/blog/Using_VLC_to_stream_bittorrent_sources.html + http://people.skolelinux.org/pere/blog/Using_VLC_to_stream_bittorrent_sources.html + Wed, 14 Feb 2018 08:00:00 +0100 + <p>A few days ago, a new major version of +<a href="https://www.videolan.org/">VLC</a> was announced, and I +decided to check out if it now supported streaming over +<a href="http://bittorrent.org/">bittorrent</a> and +<a href="https://webtorrent.io">webtorrent</a>. Bittorrent is one of +the most efficient ways to distribute large files on the Internet, and +Webtorrent is a variant of Bittorrent using +<a href="https://webrtc.org">WebRTC</a> as its transport channel, +allowing web pages to stream and share files using the same technique. +The network protocols are similar but not identical, so a client +supporting one of them can not talk to a client supporting the other. +I was a bit surprised with what I discovered when I started to look. +Looking at +<a href="https://www.videolan.org/vlc/releases/3.0.0.html">the release +notes</a> did not help answering this question, so I started searching +the web. I found several news articles from 2013, most of them +tracing the news from Torrentfreak +("<a href=https://torrentfreak.com/open-source-giant-vlc-mulls-bittorrent-support-130211/">Open +Source Giant VLC Mulls BitTorrent Streaming Support</a>"), about a +initiative to pay someone to create a VLC patch for bittorrent +support. To figure out what happend with this initiative, I headed +over to the #videolan IRC channel and asked if there were some bug or +feature request tickets tracking such feature. I got an answer from +lead developer Jean-Babtiste Kempf, telling me that there was a patch +but neither he nor anyone else knew where it was. So I searched a bit +more, and came across an independent +<a href="https://github.com/johang/vlc-bittorrent">VLC plugin to add +bittorrent support</a>, created by Johan Gunnarsson in 2016/2017. +Again according to Jean-Babtiste, this is not the patch he was talking +about.</p> + +<p>Anyway, to test the plugin, I made a working Debian package from +the git repository, with some modifications. After installing this +package, I could stream videos from +<a href="https://www.archive.org/">The Internet Archive</a> using VLC +commands like this:</p> + +<p><blockquote><pre> +vlc https://archive.org/download/LoveNest/LoveNest_archive.torrent +</pre></blockquote></p> + +<p>The plugin is supposed to handle magnet links too, but since The +Internet Archive do not have magnet links and I did not want to spend +time tracking down another source, I have not tested it. It can take +quite a while before the video start playing without any indication of +what is going on from VLC. It took 10-20 seconds when I measured it. +Some times the plugin seem unable to find the correct video file to +play, and show the metadata XML file name in the VLC status line. I +have no idea why.</p> + +<p>I have created a <a href="https://bugs.debian.org/890360">request for +a new package in Debian (RFP)</a> and +<a href="https://github.com/johang/vlc-bittorrent/issues/1">asked if +the upstream author is willing to help make this happen</a>. Now we +wait to see what come out of this. I do not want to maintain a +package that is not maintained upstream, nor do I really have time to +maintain more packages myself, so I might leave it at this. But I +really hope someone step up to do the packaging, and hope upstream is +still maintaining the source. If you want to help, please update the +RFP request or the upstream issue.</p> + +<p>I have not found any traces of webtorrent support for VLC.</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> + + + + + Version 3.1 of Cura, the 3D print slicer, is now in Debian + http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html + http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html + Tue, 13 Feb 2018 06:20:00 +0100 + <p>A new version of the +<a href="https://tracker.debian.org/pkg/cura">3D printer slicer +software Cura</a>, version 3.1.0, is now available in Debian Testing +(aka Buster) and Debian Unstable (aka Sid). I hope you find it +useful. It was uploaded the last few days, and the last update will +enter testing tomorrow. See the +<a href="https://ultimaker.com/en/products/cura-software/release-notes">release +notes</a> for the list of bug fixes and new features. Version 3.2 +was announced 6 days ago. We will try to get it into Debian as +well.</p> + +<p>More information related to 3D printing is available on the +<a href="https://wiki.debian.org/3DPrinting">3D printing</a> and +<a href="https://wiki.debian.org/3D-printer">3D printer</a> wiki pages +in Debian.</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> + + + + + Overvåkning i Kina vs. Norge + http://people.skolelinux.org/pere/blog/Overv_kning_i_Kina_vs__Norge.html + http://people.skolelinux.org/pere/blog/Overv_kning_i_Kina_vs__Norge.html + Mon, 12 Feb 2018 09:40:00 +0100 + <p>Jeg lar meg fascinere av en artikkel +<a href="https://www.dagbladet.no/kultur/terroristene-star-pa-dora/69436116">i +Dagbladet om Kinas håndtering av Xinjiang</a>, spesielt følgende +utsnitt:</p> + +<p><blockquote> + +<p>«I den sørvestlige byen Kashgar nærmere grensa til +Sentral-Asia meldes det nå at 120.000 uigurer er internert i såkalte +omskoleringsleirer. Samtidig er det innført et omfattende +helsesjekk-program med innsamling og lagring av DNA-prøver fra +absolutt alle innbyggerne. De mest avanserte overvåkingsmetodene +testes ut her. Programmer for å gjenkjenne ansikter og stemmer er på +plass i regionen. Der har de lokale myndighetene begynt å installere +GPS-systemer i alle kjøretøy og egne sporingsapper i +mobiltelefoner.</p> + +<p>Politimetodene griper så dypt inn i folks dagligliv at motstanden +mot Beijing-regimet øker.»</p> + +</blockquote></p> + +<p>Beskrivelsen avviker jo desverre ikke så veldig mye fra tilstanden +her i Norge.</p> + +<table> +<tr> +<th>Dataregistrering</th> +<th>Kina</th> +<th>Norge</th> + +<tr> +<td>Innsamling og lagring av DNA-prøver fra befolkningen</td> +<td>Ja</td> +<td>Delvis, planlagt for alle nyfødte.</td> +</tr> + +<tr> +<td>Ansiktsgjenkjenning</td> +<td>Ja</td> +<td>Ja</td> +</tr> + +<tr> +<td>Stemmegjenkjenning</td> +<td>Ja</td> +<td>Nei</td> +</tr> + +<tr> +<td>Posisjons-sporing av mobiltelefoner</td> +<td>Ja</td> +<td>Ja</td> +</tr> + +<tr> +<td>Posisjons-sporing av biler</td> +<td>Ja</td> +<td>Ja</td> +</tr> + +</table> + +<p>I Norge har jo situasjonen rundt Folkehelseinstituttets lagring av +DNA-informasjon på vegne av politiet, der de nektet å slette +informasjon politiet ikke hadde lov til å ta vare på, gjort det klart +at DNA tar vare på ganske lenge. I tillegg finnes det utallige +biobanker som lagres til evig tid, og det er planer om å innføre +<a href="https://www.aftenposten.no/norge/i/75E9/4-av-10-mener-staten-bor-lagre-DNA-profiler-pa-alle-nyfodte">evig +lagring av DNA-materiale fra alle spebarn som fødes</a> (med mulighet +for å be om sletting).</p> + +<p>I Norge er det system på plass for ansiktsgjenkjenning, som +<a href="https://www.nrk.no/norge/kun-gardermoen-har-teknologi-for-ansiktsgjenkjenning-i-norge-1.12719461">en +NRK-artikkel fra 2015</a> forteller er aktiv på Gardermoen, samt +<a href="https://www.dagbladet.no/nyheter/inntil-27-000-bor-i-norge-under-falsk-id/60500781">brukes +til å analysere bilder innsamlet av myndighetene</a>. Brukes det også +flere plasser? Det er tett med overvåkningskamera kontrollert av +politi og andre myndigheter i for eksempel Oslo sentrum.</p> + +<p>Jeg er ikke kjent med at Norge har noe system for identifisering av +personer ved hjelp av stemmegjenkjenning.</p> + +<p>Posisjons-sporing av mobiltelefoner er ruinemessig tilgjengelig for +blant annet politi, NAV og Finanstilsynet, i tråd med krav i +telefonselskapenes konsesjon. I tillegg rapporterer smarttelefoner +sin posisjon til utviklerne av utallige mobil-apper, der myndigheter +og andre kan hente ut informasjon ved behov. Det er intet behov for +noen egen app for dette.</p> + +<p>Posisjons-sporing av biler er rutinemessig tilgjengelig via et tett +nett av målepunkter på veiene (automatiske bomstasjoner, +køfribrikke-registrering, automatiske fartsmålere og andre veikamera). +Det er i tillegg vedtatt at alle nye biler skal selges med utstyr for +GPS-sporing (eCall).</p> + +<p>Det er jammen godt vi lever i et liberalt demokrati, og ikke en +overvåkningsstat, eller?</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> + + + + + How hard can æ, ø and å be? + http://people.skolelinux.org/pere/blog/How_hard_can______and___be_.html + http://people.skolelinux.org/pere/blog/How_hard_can______and___be_.html + Sun, 11 Feb 2018 17:10:00 +0100 + <img src="http://people.skolelinux.org/pere/blog/images/2018-02-11-peppes-unicode.jpeg" align="right"/> + +<p>We write 2018, and it is 30 years since Unicode was introduced. +Most of us in Norway have come to expect the use of our alphabet to +just work with any computer system. But it is apparently beyond reach +of the computers printing recites at a restaurant. Recently I visited +a Peppes pizza resturant, and noticed a few details on the recite. +Notice how 'ø' and 'å' are replaced with strange symbols in +'Servitør', 'Å BETALE', 'Beløp pr. gjest', 'Takk for besøket.' and 'Vi +gleder oss til å se deg igjen'.</p> + +<p>I would say that this state is passed sad and over in embarrassing.</p> + +<p>I removed personal and private information to be nice.</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> + + + Legal to share more than 11,000 movies listed on IMDB? http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_11_000_movies_listed_on_IMDB_.html @@ -479,770 +914,5 @@ illegally.</p> - - Cura, the nice 3D print slicer, is now in Debian Unstable - http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html - http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html - Sun, 17 Dec 2017 07:00:00 +0100 - <p>After several months of working and waiting, I am happy to report -that the nice and user friendly 3D printer slicer software Cura just -entered Debian Unstable. It consist of five packages, -<a href="https://tracker.debian.org/pkg/cura">cura</a>, -<a href="https://tracker.debian.org/pkg/cura-engine">cura-engine</a>, -<a href="https://tracker.debian.org/pkg/libarcus">libarcus</a>, -<a href="https://tracker.debian.org/pkg/fdm-materials">fdm-materials</a>, -<a href="https://tracker.debian.org/pkg/libsavitar">libsavitar</a> and -<a href="https://tracker.debian.org/pkg/uranium">uranium</a>. The last -two, uranium and cura, entered Unstable yesterday. This should make -it easier for Debian users to print on at least the Ultimaker class of -3D printers. My nearest 3D printer is an Ultimaker 2+, so it will -make life easier for at least me. :)</p> - -<p>The work to make this happen was done by Gregor Riepl, and I was -happy to assist him in sponsoring the packages. With the introduction -of Cura, Debian is up to three 3D printer slicers at your service, -Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D -printer, give it a go. :)</p> - -<p>The 3D printer software is maintained by the 3D printer Debian -team, flocking together on the -<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general">3dprinter-general</a> -mailing list and the -<a href="irc://irc.debian.org/#debian-3dprinting">#debian-3dprinting</a> -IRC channel.</p> - -<p>The next step for Cura in Debian is to update the cura package to -version 3.0.3 and then update the entire set of packages to version -3.1.0 which showed up the last few days.</p> - - - - - Idea for finding all public domain movies in the USA - http://people.skolelinux.org/pere/blog/Idea_for_finding_all_public_domain_movies_in_the_USA.html - http://people.skolelinux.org/pere/blog/Idea_for_finding_all_public_domain_movies_in_the_USA.html - Wed, 13 Dec 2017 10:15:00 +0100 - <p>While looking at -<a href="http://onlinebooks.library.upenn.edu/cce/">the scanned copies -for the copyright renewal entries for movies published in the USA</a>, -an idea occurred to me. The number of renewals are so few per year, it -should be fairly quick to transcribe them all and add references to -the corresponding IMDB title ID. This would give the (presumably) -complete list of movies published 28 years earlier that did _not_ -enter the public domain for the transcribed year. By fetching the -list of USA movies published 28 years earlier and subtract the movies -with renewals, we should be left with movies registered in IMDB that -are now in the public domain. For the year 1955 (which is the one I -have looked at the most), the total number of pages to transcribe is -21. For the 28 years from 1950 to 1978, it should be in the range -500-600 pages. It is just a few days of work, and spread among a -small group of people it should be doable in a few weeks of spare -time.</p> - -<p>A typical copyright renewal entry look like this (the first one -listed for 1955):</p> - -<p><blockquote> - ADAM AND EVIL, a photoplay in seven reels by Metro-Goldwyn-Mayer - Distribution Corp. (c) 17Aug27; L24293. Loew's Incorporated (PWH); - 10Jun55; R151558. -</blockquote></p> - -<p>The movie title as well as registration and renewal dates are easy -enough to locate by a program (split on first comma and look for -DDmmmYY). The rest of the text is not required to find the movie in -IMDB, but is useful to confirm the correct movie is found. I am not -quite sure what the L and R numbers mean, but suspect they are -reference numbers into the archive of the US Copyright Office.</p> - -<p>Tracking down the equivalent IMDB title ID is probably going to be -a manual task, but given the year it is fairly easy to search for the -movie title using for example -<a href="http://www.imdb.com/find?q=adam+and+evil+1927&s=all">http://www.imdb.com/find?q=adam+and+evil+1927&s=all</a>. -Using this search, I find that the equivalent IMDB title ID for the -first renewal entry from 1955 is -<a href="http://www.imdb.com/title/tt0017588/">http://www.imdb.com/title/tt0017588/</a>.</p> - -<p>I suspect the best way to do this would be to make a specialised -web service to make it easy for contributors to transcribe and track -down IMDB title IDs. In the web service, once a entry is transcribed, -the title and year could be extracted from the text, a search in IMDB -conducted for the user to pick the equivalent IMDB title ID right -away. By spreading out the work among volunteers, it would also be -possible to make at least two persons transcribe the same entries to -be able to discover any typos introduced. But I will need help to -make this happen, as I lack the spare time to do all of this on my -own. If you would like to help, please get in touch. Perhaps you can -draft a web service for crowd sourcing the task?</p> - -<p>Note, Project Gutenberg already have some -<a href="http://www.gutenberg.org/ebooks/search/?query=copyright+office+renewals">transcribed -copies of the US Copyright Office renewal protocols</a>, but I have -not been able to find any film renewals there, so I suspect they only -have copies of renewal for written works. I have not been able to find -any transcribed versions of movie renewals so far. Perhaps they exist -somewhere?</p> - -<p>I would love to figure out methods for finding all the public -domain works in other countries too, but it is a lot harder. At least -for Norway and Great Britain, such work involve tracking down the -people involved in making the movie and figuring out when they died. -It is hard enough to figure out who was part of making a movie, but I -do not know how to automate such procedure without a registry of every -person involved in making movies and their death year.</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> - - - - - Is the short movie «Empty Socks» from 1927 in the public domain or not? - http://people.skolelinux.org/pere/blog/Is_the_short_movie__Empty_Socks__from_1927_in_the_public_domain_or_not_.html - http://people.skolelinux.org/pere/blog/Is_the_short_movie__Empty_Socks__from_1927_in_the_public_domain_or_not_.html - Tue, 5 Dec 2017 12:30:00 +0100 - <p>Three years ago, a presumed lost animation film, -<a href="https://en.wikipedia.org/wiki/Empty_Socks">Empty Socks from -1927</a>, was discovered in the Norwegian National Library. At the -time it was discovered, it was generally assumed to be copyrighted by -The Walt Disney Company, and I blogged about -<a href="http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html">my -reasoning to conclude</a> that it would would enter the Norwegian -equivalent of the public domain in 2053, based on my understanding of -Norwegian Copyright Law. But a few days ago, I came across -<a href="http://www.toonzone.net/forums/threads/exposed-disneys-repurchase-of-oswald-the-rabbit-a-sham.4792291/">a -blog post claiming the movie was already in the public domain</a>, at -least in USA. The reasoning is as follows: The film was released in -November or Desember 1927 (sources disagree), and presumably -registered its copyright that year. At that time, right holders of -movies registered by the copyright office received government -protection for there work for 28 years. After 28 years, the copyright -had to be renewed if the wanted the government to protect it further. -The blog post I found claim such renewal did not happen for this -movie, and thus it entered the public domain in 1956. Yet someone -claim the copyright was renewed and the movie is still copyright -protected. Can anyone help me to figure out which claim is correct? -I have not been able to find Empty Socks in Catalog of copyright -entries. Ser.3 pt.12-13 v.9-12 1955-1958 Motion Pictures -<a href="http://onlinebooks.library.upenn.edu/cce/1955r.html#film">available -from the University of Pennsylvania</a>, neither in -<a href="https://babel.hathitrust.org/cgi/pt?id=mdp.39015084451130;page=root;view=image;size=100;seq=83;num=45">page -45 for the first half of 1955</a>, nor in -<a href="https://babel.hathitrust.org/cgi/pt?id=mdp.39015084451130;page=root;view=image;size=100;seq=175;num=119">page -119 for the second half of 1955</a>. It is of course possible that -the renewal entry was left out of the printed catalog by mistake. Is -there some way to rule out this possibility? Please help, and update -the wikipedia page with your findings. - -<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> - - - - - Metadata proposal for movies on the Internet Archive - http://people.skolelinux.org/pere/blog/Metadata_proposal_for_movies_on_the_Internet_Archive.html - http://people.skolelinux.org/pere/blog/Metadata_proposal_for_movies_on_the_Internet_Archive.html - Tue, 28 Nov 2017 12:00:00 +0100 - <p>It would be easier to locate the movie you want to watch in -<a href="https://www.archive.org/">the Internet Archive</a>, if the -metadata about each movie was more complete and accurate. In the -archiving community, a well known saying state that good metadata is a -love letter to the future. The metadata in the Internet Archive could -use a face lift for the future to love us back. Here is a proposal -for a small improvement that would make the metadata more useful -today. I've been unable to find any document describing the various -standard fields available when uploading videos to the archive, so -this proposal is based on my best quess and searching through several -of the existing movies.</p> - -<p>I have a few use cases in mind. First of all, I would like to be -able to count the number of distinct movies in the Internet Archive, -without duplicates. I would further like to identify the IMDB title -ID of the movies in the Internet Archive, to be able to look up a IMDB -title ID and know if I can fetch the video from there and share it -with my friends.</p> - -<p>Second, I would like the Butter data provider for The Internet -archive -(<a href="https://github.com/butterproviders/butter-provider-archive">available -from github</a>), to list as many of the good movies as possible. The -plugin currently do a search in the archive with the following -parameters:</p> - -<p><pre> -collection:moviesandfilms -AND NOT collection:movie_trailers -AND -mediatype:collection -AND format:"Archive BitTorrent" -AND year -</pre></p> - -<p>Most of the cool movies that fail to show up in Butter do so -because the 'year' field is missing. The 'year' field is populated by -the year part from the 'date' field, and should be when the movie was -released (date or year). Two such examples are -<a href="https://archive.org/details/SidneyOlcottsBen-hur1905">Ben Hur -from 1905</a> and -<a href="https://archive.org/details/Caminandes2GranDillama">Caminandes -2: Gran Dillama from 2013</a>, where the year metadata field is -missing.</p> - -So, my proposal is simply, for every movie in The Internet Archive -where an IMDB title ID exist, please fill in these metadata fields -(note, they can be updated also long after the video was uploaded, but -as far as I can tell, only by the uploader): - -<dl> - -<dt>mediatype</dt> -<dd>Should be 'movie' for movies.</dd> - -<dt>collection</dt> -<dd>Should contain 'moviesandfilms'.</dd> - -<dt>title</dt> -<dd>The title of the movie, without the publication year.</dd> - -<dt>date</dt> -<dd>The data or year the movie was released. This make the movie show -up in Butter, as well as make it possible to know the age of the -movie and is useful to figure out copyright status.</dd> - -<dt>director</dt> -<dd>The director of the movie. This make it easier to know if the -correct movie is found in movie databases.</dd> - -<dt>publisher</dt> -<dd>The production company making the movie. Also useful for -identifying the correct movie.</dd> - -<dt>links</dt> - -<dd>Add a link to the IMDB title page, for example like this: &lt;a -href="http://www.imdb.com/title/tt0028496/"&gt;Movie in -IMDB&lt;/a&gt;. This make it easier to find duplicates and allow for -counting of number of unique movies in the Archive. Other external -references, like to TMDB, could be added like this too.</dd> - -</dl> - -<p>I did consider proposing a Custom field for the IMDB title ID (for -example 'imdb_title_url', 'imdb_code' or simply 'imdb', but suspect it -will be easier to simply place it in the links free text field.</p> - -<p>I created -<a href="https://github.com/petterreinholdtsen/public-domain-free-imdb">a -list of IMDB title IDs for several thousand movies in the Internet -Archive</a>, but I also got a list of several thousand movies without -such IMDB title ID (and quite a few duplicates). It would be great if -this data set could be integrated into the Internet Archive metadata -to be available for everyone in the future, but with the current -policy of leaving metadata editing to the uploaders, it will take a -while before this happen. If you have uploaded movies into the -Internet Archive, you can help. Please consider following my proposal -above for your movies, to ensure that movie is properly -counted. :)</p> - -<p>The list is mostly generated using wikidata, which based on -Wikipedia articles make it possible to link between IMDB and movies in -the Internet Archive. But there are lots of movies without a -Wikipedia article, and some movies where only a collection page exist -(like for <a href="https://en.wikipedia.org/wiki/Caminandes">the -Caminandes example above</a>, where there are three movies but only -one Wikidata entry).</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> - - - - - Legal to share more than 3000 movies listed on IMDB? - http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html - http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html - Sat, 18 Nov 2017 21:20:00 +0100 - <p>A month ago, I blogged about my work to -<a href="http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html">automatically -check the copyright status of IMDB entries</a>, and try to count the -number of movies listed in IMDB that is legal to distribute on the -Internet. I have continued to look for good data sources, and -identified a few more. The code used to extract information from -various data sources is available in -<a href="https://github.com/petterreinholdtsen/public-domain-free-imdb">a -git repository</a>, currently available from github.</p> - -<p>So far I have identified 3186 unique IMDB title IDs. To gain -better understanding of the structure of the data set, I created a -histogram of the year associated with each movie (typically release -year). It is interesting to notice where the peaks and dips in the -graph are located. I wonder why they are placed there. I suspect -World War II caused the dip around 1940, but what caused the peak -around 2010?</p> - -<p align="center"><img src="http://people.skolelinux.org/pere/blog/images/2017-11-18-verk-i-det-fri-filmer.png" /></p> - -<p>I've so far identified ten sources for IMDB title IDs for movies in -the public domain or with a free license. This is the statistics -reported when running 'make stats' in the git repository:</p> - -<pre> - 249 entries ( 6 unique) with and 288 without IMDB title ID in free-movies-archive-org-butter.json - 2301 entries ( 540 unique) with and 0 without IMDB title ID in free-movies-archive-org-wikidata.json - 830 entries ( 29 unique) with and 0 without IMDB title ID in free-movies-icheckmovies-archive-mochard.json - 2109 entries ( 377 unique) with and 0 without IMDB title ID in free-movies-imdb-pd.json - 291 entries ( 122 unique) with and 0 without IMDB title ID in free-movies-letterboxd-pd.json - 144 entries ( 135 unique) with and 0 without IMDB title ID in free-movies-manual.json - 350 entries ( 1 unique) with and 801 without IMDB title ID in free-movies-publicdomainmovies.json - 4 entries ( 0 unique) with and 124 without IMDB title ID in free-movies-publicdomainreview.json - 698 entries ( 119 unique) with and 118 without IMDB title ID in free-movies-publicdomaintorrents.json - 8 entries ( 8 unique) with and 196 without IMDB title ID in free-movies-vodo.json - 3186 unique IMDB title IDs in total -</pre> - -<p>The entries without IMDB title ID are candidates to increase the -data set, but might equally well be duplicates of entries already -listed with IMDB title ID in one of the other sources, or represent -movies that lack a IMDB title ID. I've seen examples of all these -situations when peeking at the entries without IMDB title ID. Based -on these data sources, the lower bound for movies listed in IMDB that -are legal to distribute on the Internet is between 3186 and 4713. - -<p>It would be great for improving the accuracy of this measurement, -if the various sources added IMDB title ID to their metadata. I have -tried to reach the people behind the various sources to ask if they -are interested in doing this, without any replies so far. Perhaps you -can help me get in touch with the people behind VODO, Public Domain -Torrents, Public Domain Movies and Public Domain Review to try to -convince them to add more metadata to their movie entries?</p> - -<p>Another way you could help is by adding pages to Wikipedia about -movies that are legal to distribute on the Internet. If such page -exist and include a link to both IMDB and The Internet Archive, the -script used to generate free-movies-archive-org-wikidata.json should -pick up the mapping as soon as wikidata is updates.</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> - - - - - Some notes on fault tolerant storage systems - http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html - http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html - Wed, 1 Nov 2017 15:35:00 +0100 - <p>If you care about how fault tolerant your storage is, you might -find these articles and papers interesting. They have formed how I -think of when designing a storage system.</p> - -<ul> - -<li>USENIX :login; <a -href="https://www.usenix.org/publications/login/summer2017/ganesan">Redundancy -Does Not Imply Fault Tolerance. Analysis of Distributed Storage -Reactions to Single Errors and Corruptions</a> by Aishwarya Ganesan, -Ramnatthan Alagappan, Andrea C. Arpaci-Dusseau, and Remzi -H. Arpaci-Dusseau</li> - -<li>ZDNet -<a href="http://www.zdnet.com/article/why-raid-5-stops-working-in-2009/">Why -RAID 5 stops working in 2009</a> by Robin Harris</li> - -<li>ZDNet -<a href="http://www.zdnet.com/article/why-raid-6-stops-working-in-2019/">Why -RAID 6 stops working in 2019</a> by Robin Harris</li> - -<li>USENIX FAST'07 -<a href="http://research.google.com/archive/disk_failures.pdf">Failure -Trends in a Large Disk Drive Population</a> by Eduardo Pinheiro, -Wolf-Dietrich Weber and Luiz André Barroso</li> - -<li>USENIX ;login: <a -href="https://www.usenix.org/system/files/login/articles/hughes12-04.pdf">Data -Integrity. Finding Truth in a World of Guesses and Lies</a> by Doug -Hughes</li> - -<li>USENIX FAST'08 -<a href="https://www.usenix.org/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/">An -Analysis of Data Corruption in the Storage Stack</a> by -L. N. Bairavasundaram, G. R. Goodson, B. Schroeder, A. C. -Arpaci-Dusseau, and R. H. Arpaci-Dusseau</li> - -<li>USENIX FAST'07 <a -href="https://www.usenix.org/legacy/events/fast07/tech/schroeder/schroeder_html/">Disk -failures in the real world: what does an MTTF of 1,000,000 hours mean -to you?</a> by B. Schroeder and G. A. Gibson.</li> - -<li>USENIX ;login: <a -href="https://www.usenix.org/events/fast08/tech/full_papers/jiang/jiang_html/">Are -Disks the Dominant Contributor for Storage Failures? A Comprehensive -Study of Storage Subsystem Failure Characteristics</a> by Weihang -Jiang, Chongfeng Hu, Yuanyuan Zhou, and Arkady Kanevsky</li> - -<li>SIGMETRICS 2007 -<a href="http://research.cs.wisc.edu/adsl/Publications/latent-sigmetrics07.pdf">An -analysis of latent sector errors in disk drives</a> by -L. N. Bairavasundaram, G. R. Goodson, S. Pasupathy, and J. Schindler</li> - -</ul> - -<p>Several of these research papers are based on data collected from -hundred thousands or millions of disk, and their findings are eye -opening. The short story is simply do not implicitly trust RAID or -redundant storage systems. Details matter. And unfortunately there -are few options on Linux addressing all the identified issues. Both -ZFS and Btrfs are doing a fairly good job, but have legal and -practical issues on their own. I wonder how cluster file systems like -Ceph do in this regard. After all, there is an old saying, you know -you have a distributed system when the crash of a computer you have -never heard of stops you from getting any work done. The same holds -true if fault tolerance do not work.</p> - -<p>Just remember, in the end, it do not matter how redundant, or how -fault tolerant your storage is, if you do not continuously monitor its -status to detect and replace failed disks.</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> - - - - - Web services for writing academic LaTeX papers as a team - http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html - http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html - Tue, 31 Oct 2017 21:00:00 +0100 - <p>I was surprised today to learn that a friend in academia did not -know there are easily available web services available for writing -LaTeX documents as a team. I thought it was common knowledge, but to -make sure at least my readers are aware of it, I would like to mention -these useful services for writing LaTeX documents. Some of them even -provide a WYSIWYG editor to ease writing even further.</p> - -<p>There are two commercial services available, -<a href="https://sharelatex.com">ShareLaTeX</a> and -<a href="https://overleaf.com">Overleaf</a>. They are very easy to -use. Just start a new document, select which publisher to write for -(ie which LaTeX style to use), and start writing. Note, these two -have announced their intention to join forces, so soon it will only be -one joint service. I've used both for different documents, and they -work just fine. While -<a href="https://github.com/sharelatex/sharelatex">ShareLaTeX is free -software</a>, while the latter is not. According to <a -href="https://www.overleaf.com/help/17-is-overleaf-open-source">a -announcement from Overleaf</a>, they plan to keep the ShareLaTeX code -base maintained as free software.</p> - -But these two are not the only alternatives. -<a href="https://app.fiduswriter.org/">Fidus Writer</a> is another free -software solution with <a href="https://github.com/fiduswriter">the -source available on github</a>. I have not used it myself. Several -others can be found on the nice -<a href="https://alternativeto.net/software/sharelatex/">alterntiveTo -web service</a>. - -<p>If you like Google Docs or Etherpad, but would like to write -documents in LaTeX, you should check out these services. You can even -host your own, if you want to. :)</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> - - - - - Locating IMDB IDs of movies in the Internet Archive using Wikidata - http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html - http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html - Wed, 25 Oct 2017 12:20:00 +0200 - <p>Recently, I needed to automatically check the copyright status of a -set of <a href="http://www.imdb.com/">The Internet Movie database -(IMDB)</a> entries, to figure out which one of the movies they refer -to can be freely distributed on the Internet. This proved to be -harder than it sounds. IMDB for sure list movies without any -copyright protection, where the copyright protection has expired or -where the movie is lisenced using a permissive license like one from -Creative Commons. These are mixed with copyright protected movies, -and there seem to be no way to separate these classes of movies using -the information in IMDB.</p> - -<p>First I tried to look up entries manually in IMDB, -<a href="https://www.wikipedia.org/">Wikipedia</a> and -<a href="https://www.archive.org/">The Internet Archive</a>, to get a -feel how to do this. It is hard to know for sure using these sources, -but it should be possible to be reasonable confident a movie is "out -of copyright" with a few hours work per movie. As I needed to check -almost 20,000 entries, this approach was not sustainable. I simply -can not work around the clock for about 6 years to check this data -set.</p> - -<p>I asked the people behind The Internet Archive if they could -introduce a new metadata field in their metadata XML for IMDB ID, but -was told that they leave it completely to the uploaders to update the -metadata. Some of the metadata entries had IMDB links in the -description, but I found no way to download all metadata files in bulk -to locate those ones and put that approach aside.</p> - -<p>In the process I noticed several Wikipedia articles about movies -had links to both IMDB and The Internet Archive, and it occured to me -that I could use the Wikipedia RDF data set to locate entries with -both, to at least get a lower bound on the number of movies on The -Internet Archive with a IMDB ID. This is useful based on the -assumption that movies distributed by The Internet Archive can be -legally distributed on the Internet. With some help from the RDF -community (thank you DanC), I was able to come up with this query to -pass to <a href="https://query.wikidata.org/">the SPARQL interface on -Wikidata</a>: - -<p><pre> -SELECT ?work ?imdb ?ia ?when ?label -WHERE -{ - ?work wdt:P31/wdt:P279* wd:Q11424. - ?work wdt:P345 ?imdb. - ?work wdt:P724 ?ia. - OPTIONAL { - ?work wdt:P577 ?when. - ?work rdfs:label ?label. - FILTER(LANG(?label) = "en"). - } -} -</pre></p> - -<p>If I understand the query right, for every film entry anywhere in -Wikpedia, it will return the IMDB ID and The Internet Archive ID, and -when the movie was released and its English title, if either or both -of the latter two are available. At the moment the result set contain -2338 entries. Of course, it depend on volunteers including both -correct IMDB and The Internet Archive IDs in the wikipedia articles -for the movie. It should be noted that the result will include -duplicates if the movie have entries in several languages. There are -some bogus entries, either because The Internet Archive ID contain a -typo or because the movie is not available from The Internet Archive. -I did not verify the IMDB IDs, as I am unsure how to do that -automatically.</p> - -<p>I wrote a small python script to extract the data set from Wikidata -and check if the XML metadata for the movie is available from The -Internet Archive, and after around 1.5 hour it produced a list of 2097 -free movies and their IMDB ID. In total, 171 entries in Wikidata lack -the refered Internet Archive entry. I assume the 70 "disappearing" -entries (ie 2338-2097-171) are duplicate entries.</p> - -<p>This is not too bad, given that The Internet Archive report to -contain <a href="https://archive.org/details/feature_films">5331 -feature films</a> at the moment, but it also mean more than 3000 -movies are missing on Wikipedia or are missing the pair of references -on Wikipedia.</p> - -<p>I was curious about the distribution by release year, and made a -little graph to show how the amount of free movies is spread over the -years:<p> - -<p><img src="http://people.skolelinux.org/pere/blog/images/2017-10-25-verk-i-det-fri-filmer.png"></p> - -<p>I expect the relative distribution of the remaining 3000 movies to -be similar.</p> - -<p>If you want to help, and want to ensure Wikipedia can be used to -cross reference The Internet Archive and The Internet Movie Database, -please make sure entries like this are listed under the "External -links" heading on the Wikipedia article for the movie:</p> - -<p><pre> -* {{Internet Archive film|id=FightingLady}} -* {{IMDb title|id=0036823|title=The Fighting Lady}} -</pre></p> - -<p>Please verify the links on the final page, to make sure you did not -introduce a typo.</p> - -<p>Here is the complete list, if you want to correct the 171 -identified Wikipedia entries with broken links to The Internet -Archive: <a href="http://www.wikidata.org/entity/Q1140317">Q1140317</a>, -<a href="http://www.wikidata.org/entity/Q458656">Q458656</a>, -<a href="http://www.wikidata.org/entity/Q458656">Q458656</a>, -<a href="http://www.wikidata.org/entity/Q470560">Q470560</a>, -<a href="http://www.wikidata.org/entity/Q743340">Q743340</a>, -<a href="http://www.wikidata.org/entity/Q822580">Q822580</a>, -<a href="http://www.wikidata.org/entity/Q480696">Q480696</a>, -<a href="http://www.wikidata.org/entity/Q128761">Q128761</a>, -<a href="http://www.wikidata.org/entity/Q1307059">Q1307059</a>, -<a href="http://www.wikidata.org/entity/Q1335091">Q1335091</a>, -<a href="http://www.wikidata.org/entity/Q1537166">Q1537166</a>, -<a href="http://www.wikidata.org/entity/Q1438334">Q1438334</a>, -<a href="http://www.wikidata.org/entity/Q1479751">Q1479751</a>, -<a href="http://www.wikidata.org/entity/Q1497200">Q1497200</a>, -<a href="http://www.wikidata.org/entity/Q1498122">Q1498122</a>, -<a href="http://www.wikidata.org/entity/Q865973">Q865973</a>, -<a href="http://www.wikidata.org/entity/Q834269">Q834269</a>, -<a href="http://www.wikidata.org/entity/Q841781">Q841781</a>, -<a href="http://www.wikidata.org/entity/Q841781">Q841781</a>, -<a href="http://www.wikidata.org/entity/Q1548193">Q1548193</a>, -<a href="http://www.wikidata.org/entity/Q499031">Q499031</a>, -<a href="http://www.wikidata.org/entity/Q1564769">Q1564769</a>, -<a href="http://www.wikidata.org/entity/Q1585239">Q1585239</a>, -<a href="http://www.wikidata.org/entity/Q1585569">Q1585569</a>, -<a href="http://www.wikidata.org/entity/Q1624236">Q1624236</a>, -<a href="http://www.wikidata.org/entity/Q4796595">Q4796595</a>, -<a href="http://www.wikidata.org/entity/Q4853469">Q4853469</a>, -<a href="http://www.wikidata.org/entity/Q4873046">Q4873046</a>, -<a href="http://www.wikidata.org/entity/Q915016">Q915016</a>, -<a href="http://www.wikidata.org/entity/Q4660396">Q4660396</a>, -<a href="http://www.wikidata.org/entity/Q4677708">Q4677708</a>, -<a href="http://www.wikidata.org/entity/Q4738449">Q4738449</a>, -<a href="http://www.wikidata.org/entity/Q4756096">Q4756096</a>, -<a href="http://www.wikidata.org/entity/Q4766785">Q4766785</a>, -<a href="http://www.wikidata.org/entity/Q880357">Q880357</a>, -<a href="http://www.wikidata.org/entity/Q882066">Q882066</a>, -<a href="http://www.wikidata.org/entity/Q882066">Q882066</a>, -<a href="http://www.wikidata.org/entity/Q204191">Q204191</a>, -<a href="http://www.wikidata.org/entity/Q204191">Q204191</a>, -<a href="http://www.wikidata.org/entity/Q1194170">Q1194170</a>, -<a href="http://www.wikidata.org/entity/Q940014">Q940014</a>, -<a href="http://www.wikidata.org/entity/Q946863">Q946863</a>, -<a href="http://www.wikidata.org/entity/Q172837">Q172837</a>, -<a href="http://www.wikidata.org/entity/Q573077">Q573077</a>, -<a href="http://www.wikidata.org/entity/Q1219005">Q1219005</a>, -<a href="http://www.wikidata.org/entity/Q1219599">Q1219599</a>, -<a href="http://www.wikidata.org/entity/Q1643798">Q1643798</a>, -<a href="http://www.wikidata.org/entity/Q1656352">Q1656352</a>, -<a href="http://www.wikidata.org/entity/Q1659549">Q1659549</a>, -<a href="http://www.wikidata.org/entity/Q1660007">Q1660007</a>, -<a href="http://www.wikidata.org/entity/Q1698154">Q1698154</a>, -<a href="http://www.wikidata.org/entity/Q1737980">Q1737980</a>, -<a href="http://www.wikidata.org/entity/Q1877284">Q1877284</a>, -<a href="http://www.wikidata.org/entity/Q1199354">Q1199354</a>, -<a href="http://www.wikidata.org/entity/Q1199354">Q1199354</a>, -<a href="http://www.wikidata.org/entity/Q1199451">Q1199451</a>, -<a href="http://www.wikidata.org/entity/Q1211871">Q1211871</a>, -<a href="http://www.wikidata.org/entity/Q1212179">Q1212179</a>, -<a href="http://www.wikidata.org/entity/Q1238382">Q1238382</a>, -<a href="http://www.wikidata.org/entity/Q4906454">Q4906454</a>, -<a href="http://www.wikidata.org/entity/Q320219">Q320219</a>, -<a href="http://www.wikidata.org/entity/Q1148649">Q1148649</a>, -<a href="http://www.wikidata.org/entity/Q645094">Q645094</a>, -<a href="http://www.wikidata.org/entity/Q5050350">Q5050350</a>, -<a href="http://www.wikidata.org/entity/Q5166548">Q5166548</a>, -<a href="http://www.wikidata.org/entity/Q2677926">Q2677926</a>, -<a href="http://www.wikidata.org/entity/Q2698139">Q2698139</a>, -<a href="http://www.wikidata.org/entity/Q2707305">Q2707305</a>, -<a href="http://www.wikidata.org/entity/Q2740725">Q2740725</a>, -<a href="http://www.wikidata.org/entity/Q2024780">Q2024780</a>, -<a href="http://www.wikidata.org/entity/Q2117418">Q2117418</a>, -<a href="http://www.wikidata.org/entity/Q2138984">Q2138984</a>, -<a href="http://www.wikidata.org/entity/Q1127992">Q1127992</a>, -<a href="http://www.wikidata.org/entity/Q1058087">Q1058087</a>, -<a href="http://www.wikidata.org/entity/Q1070484">Q1070484</a>, -<a href="http://www.wikidata.org/entity/Q1080080">Q1080080</a>, -<a href="http://www.wikidata.org/entity/Q1090813">Q1090813</a>, -<a href="http://www.wikidata.org/entity/Q1251918">Q1251918</a>, -<a href="http://www.wikidata.org/entity/Q1254110">Q1254110</a>, -<a href="http://www.wikidata.org/entity/Q1257070">Q1257070</a>, -<a href="http://www.wikidata.org/entity/Q1257079">Q1257079</a>, -<a href="http://www.wikidata.org/entity/Q1197410">Q1197410</a>, -<a href="http://www.wikidata.org/entity/Q1198423">Q1198423</a>, -<a href="http://www.wikidata.org/entity/Q706951">Q706951</a>, -<a href="http://www.wikidata.org/entity/Q723239">Q723239</a>, -<a href="http://www.wikidata.org/entity/Q2079261">Q2079261</a>, -<a href="http://www.wikidata.org/entity/Q1171364">Q1171364</a>, -<a href="http://www.wikidata.org/entity/Q617858">Q617858</a>, -<a href="http://www.wikidata.org/entity/Q5166611">Q5166611</a>, -<a href="http://www.wikidata.org/entity/Q5166611">Q5166611</a>, -<a href="http://www.wikidata.org/entity/Q324513">Q324513</a>, -<a href="http://www.wikidata.org/entity/Q374172">Q374172</a>, -<a href="http://www.wikidata.org/entity/Q7533269">Q7533269</a>, -<a href="http://www.wikidata.org/entity/Q970386">Q970386</a>, -<a href="http://www.wikidata.org/entity/Q976849">Q976849</a>, -<a href="http://www.wikidata.org/entity/Q7458614">Q7458614</a>, -<a href="http://www.wikidata.org/entity/Q5347416">Q5347416</a>, -<a href="http://www.wikidata.org/entity/Q5460005">Q5460005</a>, -<a href="http://www.wikidata.org/entity/Q5463392">Q5463392</a>, -<a href="http://www.wikidata.org/entity/Q3038555">Q3038555</a>, -<a href="http://www.wikidata.org/entity/Q5288458">Q5288458</a>, -<a href="http://www.wikidata.org/entity/Q2346516">Q2346516</a>, -<a href="http://www.wikidata.org/entity/Q5183645">Q5183645</a>, -<a href="http://www.wikidata.org/entity/Q5185497">Q5185497</a>, -<a href="http://www.wikidata.org/entity/Q5216127">Q5216127</a>, -<a href="http://www.wikidata.org/entity/Q5223127">Q5223127</a>, -<a href="http://www.wikidata.org/entity/Q5261159">Q5261159</a>, -<a href="http://www.wikidata.org/entity/Q1300759">Q1300759</a>, -<a href="http://www.wikidata.org/entity/Q5521241">Q5521241</a>, -<a href="http://www.wikidata.org/entity/Q7733434">Q7733434</a>, -<a href="http://www.wikidata.org/entity/Q7736264">Q7736264</a>, -<a href="http://www.wikidata.org/entity/Q7737032">Q7737032</a>, -<a href="http://www.wikidata.org/entity/Q7882671">Q7882671</a>, -<a href="http://www.wikidata.org/entity/Q7719427">Q7719427</a>, -<a href="http://www.wikidata.org/entity/Q7719444">Q7719444</a>, -<a href="http://www.wikidata.org/entity/Q7722575">Q7722575</a>, -<a href="http://www.wikidata.org/entity/Q2629763">Q2629763</a>, -<a href="http://www.wikidata.org/entity/Q2640346">Q2640346</a>, -<a href="http://www.wikidata.org/entity/Q2649671">Q2649671</a>, -<a href="http://www.wikidata.org/entity/Q7703851">Q7703851</a>, -<a href="http://www.wikidata.org/entity/Q7747041">Q7747041</a>, -<a href="http://www.wikidata.org/entity/Q6544949">Q6544949</a>, -<a href="http://www.wikidata.org/entity/Q6672759">Q6672759</a>, -<a href="http://www.wikidata.org/entity/Q2445896">Q2445896</a>, -<a href="http://www.wikidata.org/entity/Q12124891">Q12124891</a>, -<a href="http://www.wikidata.org/entity/Q3127044">Q3127044</a>, -<a href="http://www.wikidata.org/entity/Q2511262">Q2511262</a>, -<a href="http://www.wikidata.org/entity/Q2517672">Q2517672</a>, -<a href="http://www.wikidata.org/entity/Q2543165">Q2543165</a>, -<a href="http://www.wikidata.org/entity/Q426628">Q426628</a>, -<a href="http://www.wikidata.org/entity/Q426628">Q426628</a>, -<a href="http://www.wikidata.org/entity/Q12126890">Q12126890</a>, -<a href="http://www.wikidata.org/entity/Q13359969">Q13359969</a>, -<a href="http://www.wikidata.org/entity/Q13359969">Q13359969</a>, -<a href="http://www.wikidata.org/entity/Q2294295">Q2294295</a>, -<a href="http://www.wikidata.org/entity/Q2294295">Q2294295</a>, -<a href="http://www.wikidata.org/entity/Q2559509">Q2559509</a>, -<a href="http://www.wikidata.org/entity/Q2559912">Q2559912</a>, -<a href="http://www.wikidata.org/entity/Q7760469">Q7760469</a>, -<a href="http://www.wikidata.org/entity/Q6703974">Q6703974</a>, -<a href="http://www.wikidata.org/entity/Q4744">Q4744</a>, -<a href="http://www.wikidata.org/entity/Q7766962">Q7766962</a>, -<a href="http://www.wikidata.org/entity/Q7768516">Q7768516</a>, -<a href="http://www.wikidata.org/entity/Q7769205">Q7769205</a>, -<a href="http://www.wikidata.org/entity/Q7769988">Q7769988</a>, -<a href="http://www.wikidata.org/entity/Q2946945">Q2946945</a>, -<a href="http://www.wikidata.org/entity/Q3212086">Q3212086</a>, -<a href="http://www.wikidata.org/entity/Q3212086">Q3212086</a>, -<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, -<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, -<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, -<a href="http://www.wikidata.org/entity/Q6909175">Q6909175</a>, -<a href="http://www.wikidata.org/entity/Q7405709">Q7405709</a>, -<a href="http://www.wikidata.org/entity/Q7416149">Q7416149</a>, -<a href="http://www.wikidata.org/entity/Q7239952">Q7239952</a>, -<a href="http://www.wikidata.org/entity/Q7317332">Q7317332</a>, -<a href="http://www.wikidata.org/entity/Q7783674">Q7783674</a>, -<a href="http://www.wikidata.org/entity/Q7783704">Q7783704</a>, -<a href="http://www.wikidata.org/entity/Q7857590">Q7857590</a>, -<a href="http://www.wikidata.org/entity/Q3372526">Q3372526</a>, -<a href="http://www.wikidata.org/entity/Q3372642">Q3372642</a>, -<a href="http://www.wikidata.org/entity/Q3372816">Q3372816</a>, -<a href="http://www.wikidata.org/entity/Q3372909">Q3372909</a>, -<a href="http://www.wikidata.org/entity/Q7959649">Q7959649</a>, -<a href="http://www.wikidata.org/entity/Q7977485">Q7977485</a>, -<a href="http://www.wikidata.org/entity/Q7992684">Q7992684</a>, -<a href="http://www.wikidata.org/entity/Q3817966">Q3817966</a>, -<a href="http://www.wikidata.org/entity/Q3821852">Q3821852</a>, -<a href="http://www.wikidata.org/entity/Q3420907">Q3420907</a>, -<a href="http://www.wikidata.org/entity/Q3429733">Q3429733</a>, -<a href="http://www.wikidata.org/entity/Q774474">Q774474</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> - - -