Add link to CasparCG too.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index ce50cbf3950ab37f8c24797ca6308ac360d2c423..cfcefdc156c1fd31a645adf2f430596b6da71039 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -7,513 +7,35 @@
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
        <item>
-               <title>Kommentarer til «Evaluation of (il)legality» for Popcorn Time</title>
-               <link>http://people.skolelinux.org/pere/blog/Kommentarer_til__Evaluation_of__il_legality__for_Popcorn_Time.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kommentarer_til__Evaluation_of__il_legality__for_Popcorn_Time.html</guid>
-                <pubDate>Wed, 20 Dec 2017 11:40:00 +0100</pubDate>
-               <description>&lt;p&gt;I går var jeg i Follo tingrett som sakkyndig vitne og presenterte
-  mine undersøkelser rundt
-  &lt;a href=&quot;https://github.com/petterreinholdtsen/public-domain-free-imdb&quot;&gt;telling
-    av filmverk i det fri&lt;/a&gt;, relatert til
-  &lt;a href=&quot;https://www.nuug.no/&quot;&gt;foreningen NUUG&lt;/a&gt;s involvering i
-  &lt;a href=&quot;https://www.nuug.no/news/tags/dns-domenebeslag/&quot;&gt;saken om
-  Økokrims beslag og senere inndragning av DNS-domenet
-  popcorn-time.no&lt;/a&gt;.  Jeg snakket om flere ting, men mest om min
-  vurdering av hvordan filmbransjen har målt hvor ulovlig Popcorn Time
-  er.  Filmbransjens måling er så vidt jeg kan se videreformidlet uten
-  endringer av norsk politi, og domstolene har lagt målingen til grunn
-  når de har vurdert Popcorn Time både i Norge og i utlandet (tallet
-  99% er referert også i utenlandske domsavgjørelser).&lt;/p&gt;
-
-&lt;p&gt;I forkant av mitt vitnemål skrev jeg et notat, mest til meg selv,
-  med de punktene jeg ønsket å få frem.  Her er en kopi av notatet jeg
-  skrev og ga til aktoratet.  Merkelig nok ville ikke dommerene ha
-  notatet, så hvis jeg forsto rettsprosessen riktig ble kun
-  histogram-grafen lagt inn i dokumentasjonen i saken.  Dommerne var
-  visst bare interessert i å forholde seg til det jeg sa i retten,
-  ikke det jeg hadde skrevet i forkant.  Uansett så antar jeg at flere
-  enn meg kan ha glede av teksten, og publiserer den derfor her.
-  Legger ved avskrift av dokument 09,13, som er det sentrale
-  dokumentet jeg kommenterer.&lt;/p&gt;
-
-&lt;p&gt;&lt;strong&gt;Kommentarer til «Evaluation of (il)legality» for Popcorn
-  Time&lt;/strong&gt;&lt;/p&gt;
-
-&lt;p&gt;&lt;strong&gt;Oppsummering&lt;/strong&gt;&lt;/p&gt;           
-
-&lt;p&gt;Målemetoden som Økokrim har lagt til grunn når de påstår at 99% av
-  filmene tilgjengelig fra Popcorn Time deles ulovlig har
-  svakheter.&lt;/p&gt;
-
-&lt;p&gt;De eller den som har vurdert hvorvidt filmer kan lovlig deles har
-  ikke lyktes med å identifisere filmer som kan deles lovlig og har
-  tilsynelatende antatt at kun veldig gamle filmer kan deles lovlig.
-  Økokrim legger til grunn at det bare finnes èn film, Charlie
-  Chaplin-filmen «The Circus» fra 1928, som kan deles fritt blant de
-  som ble observert tilgjengelig via ulike Popcorn Time-varianter.
-  Jeg finner tre flere blant de observerte filmene: «The Brain That
-  Wouldn&#39;t Die» fra 1962, «God’s Little Acre» fra 1958 og «She Wore a
-  Yellow Ribbon» fra 1949.  Det er godt mulig det finnes flere.  Det
-  finnes dermed minst fire ganger så mange filmer som lovlig kan deles
-  på Internett i datasettet Økokrim har lagt til grunn når det påstås
-  at mindre enn 1 % kan deles lovlig.&lt;/p&gt;
-
-&lt;p&gt;Dernest, utplukket som gjøres ved søk på tilfeldige ord hentet fra
-  ordlisten til Dale-Chall avviker fra årsfordelingen til de brukte
-  filmkatalogene som helhet, hvilket påvirker fordelingen mellom
-  filmer som kan lovlig deles og filmer som ikke kan lovlig deles.  I
-  tillegg gir valg av øvre del (de fem første) av søkeresultatene et
-  avvik fra riktig årsfordeling, hvilket påvirker fordelingen av verk
-  i det fri i søkeresultatet.&lt;/p&gt;
-
-&lt;p&gt;Det som måles er ikke (u)lovligheten knyttet til bruken av Popcorn
-  Time, men (u)lovligheten til innholdet i bittorrent-filmkataloger
-  som vedlikeholdes uavhengig av Popcorn Time.&lt;/p&gt;
-
-&lt;p&gt;Omtalte dokumenter: 09,12, &lt;a href=&quot;#dok-09-13&quot;&gt;09,13&lt;/a&gt;, 09,14,
-09,18, 09,19, 09,20.&lt;/p&gt;
-
-&lt;p&gt;&lt;strong&gt;Utfyllende kommentarer&lt;/strong&gt;&lt;/p&gt;
-
-&lt;p&gt;Økokrim har forklart domstolene at minst 99% av alt som er
-  tilgjengelig fra ulike Popcorn Time-varianter deles ulovlig på
-  Internet.  Jeg ble nysgjerrig på hvordan de er kommet frem til dette
-  tallet, og dette notatet er en samling kommentarer rundt målingen
-  Økokrim henviser til.  Litt av bakgrunnen for at jeg valgte å se på
-  saken er at jeg er interessert i å identifisere og telle hvor mange
-  kunstneriske verk som er falt i det fri eller av andre grunner kan
-  lovlig deles på Internett, og dermed var interessert i hvordan en
-  hadde funnet den ene prosenten som kanskje deles lovlig.&lt;/p&gt;
-
-&lt;p&gt;Andelen på 99% kommer fra et ukreditert og udatert notatet som tar
-  mål av seg å dokumentere en metode for å måle hvor (u)lovlig ulike
-  Popcorn Time-varianter er.&lt;/p&gt;
-
-&lt;p&gt;Raskt oppsummert, så forteller metodedokumentet at på grunn av at
-  det ikke er mulig å få tak i komplett liste over alle filmtitler
-  tilgjengelig via Popcorn Time, så lages noe som skal være et
-  representativt utvalg ved å velge 50 søkeord større enn tre tegn fra
-  ordlisten kjent som Dale-Chall.  For hvert søkeord gjøres et søk og
-  de første fem filmene i søkeresultatet samles inn inntil 100 unike
-  filmtitler er funnet.  Hvis 50 søkeord ikke var tilstrekkelig for å
-  nå 100 unike filmtitler ble flere filmer fra hvert søkeresultat lagt
-  til.  Hvis dette heller ikke var tilstrekkelig, så ble det hentet ut
-  og søkt på flere tilfeldig valgte søkeord inntil 100 unike
-  filmtitler var identifisert.&lt;/p&gt;
-
-&lt;p&gt;Deretter ble for hver av filmtitlene «vurdert hvorvidt det var
-  rimelig å forvente om at verket var vernet av copyright, ved å se på
-  om filmen var tilgjengelig i IMDB, samt se på regissør,
-  utgivelsesår, når det var utgitt for bestemte markedsområder samt
-  hvilke produksjons- og distribusjonsselskap som var registrert» (min
-  oversettelse).&lt;/p&gt;
-
-&lt;p&gt;Metoden er gjengitt både i de ukrediterte dokumentene 09,13 og
-  09,19, samt beskrevet fra side 47 i dokument 09,20, lysark datert
-  2017-02-01.  Sistnevnte er kreditert Geerart Bourlon fra Motion
-  Picture Association EMEA.  Metoden virker å ha flere svakheter som
-  gir resultatene en slagside.  Den starter med å slå fast at det ikke
-  er mulig å hente ut en komplett liste over alle filmtitler som er
-  tilgjengelig, og at dette er bakgrunnen for metodevalget.  Denne
-  forutsetningen er ikke i tråd med det som står i dokument 09,12, som
-  ikke heller har oppgitt forfatter og dato.  Dokument 09,12 forteller
-  hvordan hele kataloginnholdet ble lasted ned og talt opp.  Dokument
-  09,12 er muligens samme rapport som ble referert til i dom fra Oslo
-  Tingrett 2017-11-03
-  (&lt;a href=&quot;https://www.domstol.no/no/Enkelt-domstol/Oslo--tingrett/Nyheter/ma-sperre-for-popcorn-time/&quot;&gt;sak
-  17-093347TVI-OTIR/05&lt;/a&gt;) som rapport av 1. juni 2017 av Alexander
-  Kind Petersen, men jeg har ikke sammenlignet dokumentene ord for ord
-  for å kontrollere dette.&lt;/p&gt;
-
-&lt;p&gt;IMDB er en forkortelse for The Internet Movie Database, en
-  anerkjent kommersiell nettjeneste som brukes aktivt av både
-  filmbransjen og andre til å holde rede på hvilke spillefilmer (og
-  endel andre filmer) som finnes eller er under produksjon, og
-  informasjon om disse filmene.  Datakvaliteten er høy, med få feil og
-  få filmer som mangler.  IMDB viser ikke informasjon om
-  opphavsrettslig status for filmene på infosiden for hver film.  Som
-  del av IMDB-tjenesten finnes det lister med filmer laget av
-  frivillige som lister opp det som antas å være verk i det fri.&lt;/p&gt;
-  
-&lt;p&gt;Det finnes flere kilder som kan brukes til å finne filmer som er
-  allemannseie (public domain) eller har bruksvilkår som gjør det
-  lovlig for alleå dele dem på Internett.  Jeg har de siste ukene
-  forsøkt å samle og krysskoble disse listene for å forsøke å telle
-  antall filmer i det fri.  Ved å ta utgangspunkt i slike lister (og
-  publiserte filmer for Internett-arkivets del), har jeg så langt
-  klart å identifisere over 11 000 filmer, hovedsaklig spillefilmer.
-
-&lt;p&gt;De aller fleste oppføringene er hentet fra IMDB selv, basert på det
-  faktum at alle filmer laget i USA før 1923 er falt i det fri.
-  Tilsvarende tidsgrense for Storbritannia er 1912-07-01, men dette
-  utgjør bare veldig liten del av spillefilmene i IMDB (19 totalt).
-  En annen stor andel kommer fra Internett-arkivet, der jeg har
-  identifisert filmer med referanse til IMDB.  Internett-arkivet, som
-  holder til i USA, har som
-  &lt;a href=&quot;https://archive.org/about/terms.php&quot;&gt;policy å kun publisere
-  filmer som det er lovlig å distribuere&lt;/a&gt;.  Jeg har under arbeidet
-  kommet over flere filmer som har blitt fjernet fra
-  Internett-arkivet, hvilket gjør at jeg konkluderer med at folkene
-  som kontrollerer Internett-arkivet har et aktivt forhold til å kun
-  ha lovlig innhold der, selv om det i stor grad er drevet av
-  frivillige.  En annen stor liste med filmer kommer fra det
-  kommersielle selskapet Retro Film Vault, som selger allemannseide
-  filmer til TV- og filmbransjen, Jeg har også benyttet meg av lister
-  over filmer som hevdes å være allemannseie, det være seg Public
-  Domain Review, Public Domain Torrents og Public Domain Movies (.net
-  og .info), samt lister over filmer med Creative Commons-lisensiering
-  fra Wikipedia, VODO og The Hill Productions.  Jeg har gjort endel
-  stikkontroll ved å vurdere filmer som kun omtales på en liste.  Der
-  jeg har funnet feil som har gjort meg i tvil om vurderingen til de
-  som har laget listen har jeg forkastet listen fullstendig (gjelder
-  en liste fra IMDB).&lt;/p&gt;
-  
-&lt;p&gt;Ved å ta utgangspunkt i verk som kan antas å være lovlig delt på
-  Internett (fra blant annet Internett-arkivet, Public Domain
-  Torrents, Public Domain Reivew og Public Domain Movies), og knytte
-  dem til oppføringer i IMDB, så har jeg så langt klart å identifisere
-  over 11 000 filmer (hovedsaklig spillefilmer) det er grunn til å tro
-  kan lovlig distribueres av alle på Internett.  Som ekstra kilder er
-  det brukt lister over filmer som antas/påstås å være allemannseie.
-  Disse kildene kommer fra miljøer som jobber for å gjøre tilgjengelig
-  for almennheten alle verk som er falt i det fri eller har
-  bruksvilkår som tillater deling.
-
-&lt;p&gt;I tillegg til de over 11 000 filmene der tittel-ID i IMDB er
-  identifisert, har jeg funnet mer enn 20 000 oppføringer der jeg ennå
-  ikke har hatt kapasitet til å spore opp tittel-ID i IMDB.  Noen av
-  disse er nok duplikater av de IMDB-oppføringene som er identifisert
-  så langt, men neppe alle.  Retro Film Vault hevder å ha 44 000
-  filmverk i det fri i sin katalog, så det er mulig at det reelle
-  tallet er betydelig høyere enn de jeg har klart å identifisere så
-  langt.  Konklusjonen er at tallet 11 000 er nedre grense for hvor
-  mange filmer i IMDB som kan lovlig deles på Internett.  I følge &lt;a
-  href=&quot;http://www.imdb.com/stats&quot;&gt;statistikk fra IMDB&lt;/a&gt; er det 4.6
-  millioner titler registrert, hvorav 3 millioner er TV-serieepisoder.
-  Jeg har ikke funnet ut hvordan de fordeler seg per år.&lt;/p&gt;
-
-&lt;p&gt;Hvis en fordeler på år alle tittel-IDene i IMDB som hevdes å lovlig
-  kunne deles på Internett, får en følgende histogram:&lt;/p&gt;
-
-&lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;80%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-12-20-histogram-year.png&quot;&gt;&lt;/p&gt;
-
-&lt;p&gt;En kan i histogrammet se at effekten av manglende registrering
-  eller fornying av registrering er at mange filmer gitt ut i USA før
-  1978 er allemannseie i dag.  I tillegg kan en se at det finnes flere
-  filmer gitt ut de siste årene med bruksvilkår som tillater deling,
-  muligens på grunn av fremveksten av
-  &lt;a href=&quot;https://creativecommons.org/&quot;&gt;Creative
-  Commons&lt;/a&gt;-bevegelsen..&lt;/p&gt;
-  
-&lt;p&gt;For maskinell analyse av katalogene har jeg laget et lite program
-  som kobler seg til bittorrent-katalogene som brukes av ulike Popcorn
-  Time-varianter og laster ned komplett liste over filmer i
-  katalogene, noe som bekrefter at det er mulig å hente ned komplett
-  liste med alle filmtitler som er tilgjengelig.  Jeg har sett på fire
-  bittorrent-kataloger.  Den ene brukes av klienten tilgjengelig fra
-  www.popcorntime.sh og er navngitt &#39;sh&#39; i dette dokumentet.  Den
-  andre brukes i følge dokument 09,12 av klienten tilgjengelig fra
-  popcorntime.ag og popcorntime.sh og er navngitt &#39;yts&#39; i dette
-  dokumentet.  Den tredje brukes av websidene tilgjengelig fra
-  popcorntime-online.tv og er navngitt &#39;apidomain&#39; i dette dokumentet.
-  Den fjerde brukes av klienten tilgjenglig fra popcorn-time.to i
-  følge dokument 09,12, og er navngitt &#39;ukrfnlge&#39; i dette
-  dokumentet.&lt;/p&gt;
-
-&lt;p&gt;Metoden Økokrim legger til grunn skriver i sitt punkt fire at
-  skjønn er en egnet metode for å finne ut om en film kan lovlig deles
-  på Internett eller ikke, og sier at det ble «vurdert hvorvidt det
-  var rimelig å forvente om at verket var vernet av copyright».  For
-  det første er det ikke nok å slå fast om en film er «vernet av
-  copyright» for å vite om det er lovlig å dele den på Internett eller
-  ikke, da det finnes flere filmer med opphavsrettslige bruksvilkår
-  som tillater deling på Internett.  Eksempler på dette er Creative
-  Commons-lisensierte filmer som Citizenfour fra 2014 og Sintel fra
-  2010.  I tillegg til slike finnes det flere filmer som nå er
-  allemannseie (public domain) på grunn av manglende registrering
-  eller fornying av registrering selv om både regisør,
-  produksjonsselskap og distributør ønsker seg vern.  Eksempler på
-  dette er Plan 9 from Outer Space fra 1959 og Night of the Living
-  Dead fra 1968.  Alle filmer fra USA som var allemannseie før
-  1989-03-01 forble i det fri da Bern-konvensjonen, som tok effekt i
-  USA på det tidspunktet, ikke ble gitt tilbakevirkende kraft.  Hvis
-  det er noe
-  &lt;a href=&quot;http://www.latimes.com/local/lanow/la-me-ln-happy-birthday-song-lawsuit-decision-20150922-story.html&quot;&gt;historien
-  om sangen «Happy birthday»&lt;/a&gt; forteller oss, der betaling for bruk
-  har vært krevd inn i flere tiår selv om sangen ikke egentlig var
-  vernet av åndsverksloven, så er det at hvert enkelt verk må vurderes
-  nøye og i detalj før en kan slå fast om verket er allemannseie eller
-  ikke, det holder ikke å tro på selverklærte rettighetshavere.  Flere
-  eksempel på verk i det fri som feilklassifiseres som vernet er fra
-  dokument 09,18, som lister opp søkeresultater for klienten omtalt
-  som popcorntime.sh og i følge notatet kun inneholder en film (The
-  Circus fra 1928) som under tvil kan antas å være allemannseie.&lt;/p&gt;
-
-&lt;p&gt;Ved rask gjennomlesning av dokument 09,18, som inneholder
-  skjermbilder fra bruk av en Popcorn Time-variant, fant jeg omtalt
-  både filmen «The Brain That Wouldn&#39;t Die» fra 1962 som er
-  &lt;a href=&quot;https://archive.org/details/brain_that_wouldnt_die&quot;&gt;tilgjengelig
-  fra Internett-arkivet&lt;/a&gt; og som
-  &lt;a href=&quot;https://en.wikipedia.org/wiki/List_of_films_in_the_public_domain_in_the_United_States&quot;&gt;i
-    følge Wikipedia er allemannseie i USA&lt;/a&gt; da den ble gitt ut i
-  1962 uten &#39;copyright&#39;-merking, og filmen «God’s Little Acre» fra
-  1958 &lt;a href=&quot;https://en.wikipedia.org/wiki/God%27s_Little_Acre_%28film%29&quot;&gt;som
-    er lagt ut på Wikipedia&lt;/a&gt;, der det fortelles at
-  sort/hvit-utgaven er allemannseie.  Det fremgår ikke fra dokument
-  09,18 om filmen omtalt der er sort/hvit-utgaven.  Av
-  kapasitetsårsaker og på grunn av at filmoversikten i dokument 09,18
-  ikke er maskinlesbart har jeg ikke forsøkt å sjekke alle filmene som
-  listes opp der om mot liste med filmer som er antatt lovlig kan
-  distribueres på Internet.&lt;/p&gt;
-
-&lt;p&gt;Ved maskinell gjennomgang av listen med IMDB-referanser under
-  regnearkfanen &#39;Unique titles&#39; i dokument 09.14, fant jeg i tillegg
-  filmen «She Wore a Yellow Ribbon» fra 1949) som nok også er
-  feilklassifisert. Filmen «She Wore a Yellow Ribbon» er tilgjengelig
-  fra Internett-arkivet og markert som allemannseie der.  Det virker
-  dermed å være minst fire ganger så mange filmer som kan lovlig deles
-  på Internett enn det som er lagt til grunn når en påstår at minst
-  99% av innholdet er ulovlig.  Jeg ser ikke bort fra at nærmere
-  undersøkelser kan avdekke flere.  Poenget er uansett at metodens
-  punkt om «rimelig å forvente om at verket var vernet av copyright»
-  gjør metoden upålitelig.&lt;/p&gt;
-
-&lt;p&gt;Den omtalte målemetoden velger ut tilfeldige søketermer fra
-  ordlisten Dale-Chall.  Den ordlisten inneholder 3000 enkle engelske
-  som fjerdeklassinger i USA er forventet å forstå.  Det fremgår ikke
-  hvorfor akkurat denne ordlisten er valgt, og det er uklart for meg
-  om den er egnet til å få et representativt utvalg av filmer.  Mange
-  av ordene gir tomt søkeresultat.  Ved å simulerte tilsvarende søk
-  ser jeg store avvik fra fordelingen i katalogen for enkeltmålinger.
-  Dette antyder at enkeltmålinger av 100 filmer slik målemetoden
-  beskriver er gjort, ikke er velegnet til å finne andel ulovlig
-  innhold i bittorrent-katalogene.&lt;/p&gt;
-
-&lt;p&gt;En kan motvirke dette store avviket for enkeltmålinger ved å gjøre
-  mange søk og slå sammen resultatet.  Jeg har testet ved å
-  gjennomføre 100 enkeltmålinger (dvs. måling av (100x100=) 10 000
-  tilfeldig valgte filmer) som gir mindre, men fortsatt betydelig
-  avvik, i forhold til telling av filmer pr år i hele katalogen.&lt;/p&gt;
-  
-&lt;p&gt;Målemetoden henter ut de fem øverste i søkeresultatet.
-  Søkeresultatene er sortert på antall bittorrent-klienter registrert
-  som delere i katalogene, hvilket kan gi en slagside mot hvilke
-  filmer som er populære blant de som bruker bittorrent-katalogene,
-  uten at det forteller noe om hvilket innhold som er tilgjengelig
-  eller hvilket innhold som deles med Popcorn Time-klienter.  Jeg har
-  forsøkt å måle hvor stor en slik slagside eventuelt er ved å
-  sammenligne fordelingen hvis en tar de 5 nederste i søkeresultatet i
-  stedet.  Avviket for disse to metodene for endel kataloger er godt
-  synlig på histogramet.  Her er histogram over filmer funnet i den
-  komplette katalogen (grønn strek), og filmer funnet ved søk etter
-  ord i Dale-Chall.  Grafer merket &#39;top&#39; henter fra de 5 første i
-  søkeresultatet, mens de merket &#39;bottom&#39; henter fra de 5 siste.  En
-  kan her se at resultatene påvirkes betydelig av hvorvidt en ser på
-  de første eller de siste filmene i et søketreff.&lt;/p&gt;
-
-&lt;p align=&quot;center&quot;&gt;
-  &lt;img width=&quot;40%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-12-20-histogram-year-sh-top.png&quot;/&gt;
-  &lt;img width=&quot;40%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-12-20-histogram-year-sh-bottom.png&quot;/&gt;
-  &lt;br&gt;
-  &lt;img width=&quot;40%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-12-20-histogram-year-yts-top.png&quot;/&gt;
-  &lt;img width=&quot;40%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-12-20-histogram-year-yts-bottom.png&quot;/&gt;
-  &lt;br&gt;
-  &lt;img width=&quot;40%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-12-20-histogram-year-ukrfnlge-top.png&quot;/&gt;
-  &lt;img width=&quot;40%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-12-20-histogram-year-ukrfnlge-bottom.png&quot;/&gt;
-  &lt;br&gt;
-  &lt;img width=&quot;40%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-12-20-histogram-year-apidomain-top.png&quot;/&gt;
-  &lt;img width=&quot;40%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-12-20-histogram-year-apidomain-bottom.png&quot;/&gt;
-&lt;/p&gt;
-  
-&lt;p&gt;Det er verdt å bemerke at de omtalte bittorrent-katalogene ikke er
-  laget for bruk med Popcorn Time.  Eksempelvis tilhører katalogen
-  YTS, som brukes av klientet som ble lastes ned fra popcorntime.sh,
-  et selvstendig fildelings-relatert nettsted YTS.AG med et separat
-  brukermiljø.  Målemetoden foreslått av Økokrim måler dermed ikke
-  (u)lovligheten rundt bruken av Popcorn Time, men (u)lovligheten til
-  innholdet i disse katalogene.&lt;/p&gt;
-
-&lt;hr&gt;
-
-&lt;p id=&quot;dok-09-13&quot;&gt;Metoden fra Økokrims dokument 09,13 i straffesaken
-om DNS-beslag.&lt;/p&gt;
-
-&lt;p&gt;&lt;strong&gt;1. Evaluation of (il)legality&lt;/strong&gt;&lt;/p&gt;
-
-&lt;p&gt;&lt;strong&gt;1.1. Methodology&lt;/strong&gt;
-     
-&lt;p&gt;Due to its technical configuration, Popcorn Time applications don&#39;t
-allow to make a full list of all titles made available. In order to
-evaluate the level of illegal operation of PCT, the following
-methodology was applied:&lt;/p&gt;
-
-&lt;ol&gt;
-
- &lt;li&gt;A random selection of 50 keywords, greater than 3 letters, was
-    made from the Dale-Chall list that contains 3000 simple English
-    words1. The selection was made by using a Random Number
-    Generator2.&lt;/li&gt;
-         
- &lt;li&gt;For each keyword, starting with the first randomly selected
-    keyword, a search query was conducted in the movie section of the
-    respective Popcorn Time application. For each keyword, the first
-    five results were added to the title list until the number of 100
-    unique titles was reached (duplicates were removed).&lt;/li&gt;
-         
- &lt;li&gt;For one fork, .CH, insufficient titles were generated via this
-    approach to reach 100 titles. This was solved by adding any
-    additional query results above five for each of the 50 keywords.
-    Since this still was not enough, another 42 random keywords were
-    selected to finally reach 100 titles.&lt;/li&gt;
-         
- &lt;li&gt;It was verified whether or not there is a reasonable expectation
-    that the work is copyrighted by checking if they are available on
-    IMDb, also verifying the director, the year when the title was
-    released, the release date for a certain market, the production
-    company/ies of the title and the distribution company/ies.&lt;/li&gt;
-
-&lt;/ol&gt;
-
-&lt;p&gt;&lt;strong&gt;1.2. Results&lt;/strong&gt;&lt;/p&gt;
-     
-&lt;p&gt;Between 6 and 9 June 2016, four forks of Popcorn Time were
-investigated: popcorn-time.to, popcorntime.ag, popcorntime.sh and
-popcorntime.ch. An excel sheet with the results is included in
-Appendix 1. Screenshots were secured in separate Appendixes for each
-respective fork, see Appendix 2-5.&lt;/p&gt;
-
-&lt;p&gt;For each fork, out of 100, de-duplicated titles it was possible to
-retrieve data according to the parameters set out above that indicate
-that the title is commercially available. Per fork, there was 1 title
-that presumably falls within the public domain, i.e. the 1928 movie
-&quot;The Circus&quot; by and with Charles Chaplin.&lt;/p&gt;
-
-&lt;p&gt;Based on the above it is reasonable to assume that 99% of the movie
-content of each fork is copyright protected and is made available
-illegally.&lt;/p&gt;
-
-&lt;p&gt;This exercise was not repeated for TV series, but considering that
-besides production companies and distribution companies also
-broadcasters may have relevant rights, it is reasonable to assume that
-at least a similar level of infringement will be established.&lt;/p&gt;
-
-&lt;p&gt;Based on the above it is reasonable to assume that 99% of all the
-content of each fork is copyright protected and are made available
-illegally.&lt;/p&gt;
-</description>
-       </item>
-       
-       <item>
-               <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
-               <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
-                <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
-               <description>&lt;p&gt;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,
-&lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
-&lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
-&lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
-&lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
-&lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
-&lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;.  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. :)&lt;/p&gt;
-
-&lt;p&gt;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. :)&lt;/p&gt;
-
-&lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
-team, flocking together on the
-&lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
-mailing list and the
-&lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
-IRC channel.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-</description>
-       </item>
-       
-       <item>
-               <title>Idea for finding all public domain movies in the USA</title>
-               <link>http://people.skolelinux.org/pere/blog/Idea_for_finding_all_public_domain_movies_in_the_USA.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_finding_all_public_domain_movies_in_the_USA.html</guid>
-                <pubDate>Wed, 13 Dec 2017 10:15:00 +0100</pubDate>
-               <description>&lt;p&gt;While looking at
-&lt;a href=&quot;http://onlinebooks.library.upenn.edu/cce/&quot;&gt;the scanned copies
-for the copyright renewal entries for movies published in the USA&lt;/a&gt;,
-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.&lt;/p&gt;
-
-&lt;p&gt;A typical copyright renewal entry look like this (the first one
-listed for 1955):&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;
-  ADAM AND EVIL, a photoplay in seven reels by Metro-Goldwyn-Mayer
-  Distribution Corp. (c) 17Aug27; L24293. Loew&#39;s Incorporated (PWH);
-  10Jun55; R151558.
-&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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
-&lt;a href=&quot;http://www.imdb.com/find?q=adam+and+evil+1927&amp;s=all&quot;&gt;http://www.imdb.com/find?q=adam+and+evil+1927&amp;s=all&lt;/a&gt;.
-Using this search, I find that the equivalent IMDB title ID for the
-first renewal entry from 1955 is
-&lt;a href=&quot;http://www.imdb.com/title/tt0017588/&quot;&gt;http://www.imdb.com/title/tt0017588/&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;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?&lt;/p&gt;
-
-&lt;p&gt;Note, Project Gutenberg already have some
-&lt;a href=&quot;http://www.gutenberg.org/ebooks/search/?query=copyright+office+renewals&quot;&gt;transcribed
-copies of the US Copyright Office renewal protocols&lt;/a&gt;, 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?&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
+               <title>Time for an official MIME type for patches?</title>
+               <link>http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
+                <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
+               <description>&lt;p&gt;As part of my involvement in
+&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
+archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
+emails into a test instance of the archive to see how well this would
+go.  I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
+notmuch email database&lt;/a&gt;, all public emails sent to me via
+@lists.debian.org, giving me a set of around 216 000 emails to import.
+In the process, I had a look at the various attachments included in
+these emails, to figure out what to do with attachments, and noticed
+that one of the most common attachment formats do not have
+&lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
+official MIME type&lt;/a&gt; registered with IANA/IETF.  The output from
+diff, ie the input for patch, is on the top 10 list of formats
+included in these emails.  At the moment people seem to use either
+text/x-patch or text/x-diff, but neither is officially registered.  It
+would be better if one official MIME type were registered and used
+everywhere.&lt;/p&gt;
+
+&lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
+up the topic on
+&lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
+media-types mailing list&lt;/a&gt;.  If you are interested in discussion
+which MIME type to use as the official for patch files, or involved in
+making software using a MIME type for patches, perhaps you would like
+to join the discussion?&lt;/p&gt;
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
@@ -522,42 +44,72 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
-               <title>Is the short movie «Empty Socks» from 1927 in the public domain or not?</title>
-               <link>http://people.skolelinux.org/pere/blog/Is_the_short_movie__Empty_Socks__from_1927_in_the_public_domain_or_not_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Is_the_short_movie__Empty_Socks__from_1927_in_the_public_domain_or_not_.html</guid>
-                <pubDate>Tue, 5 Dec 2017 12:30:00 +0100</pubDate>
-               <description>&lt;p&gt;Three years ago, a presumed lost animation film,
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Empty_Socks&quot;&gt;Empty Socks from
-1927&lt;/a&gt;, 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
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html&quot;&gt;my
-reasoning to conclude&lt;/a&gt; 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
-&lt;a href=&quot;http://www.toonzone.net/forums/threads/exposed-disneys-repurchase-of-oswald-the-rabbit-a-sham.4792291/&quot;&gt;a
-blog post claiming the movie was already in the public domain&lt;/a&gt;, 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
-&lt;a href=&quot;http://onlinebooks.library.upenn.edu/cce/1955r.html#film&quot;&gt;available
-from the University of Pennsylvania&lt;/a&gt;, neither in
-&lt;a href=&quot;https://babel.hathitrust.org/cgi/pt?id=mdp.39015084451130;page=root;view=image;size=100;seq=83;num=45&quot;&gt;page
-45 for the first half of 1955&lt;/a&gt;, nor in
-&lt;a href=&quot;https://babel.hathitrust.org/cgi/pt?id=mdp.39015084451130;page=root;view=image;size=100;seq=175;num=119&quot;&gt;page
-119 for the second half of 1955&lt;/a&gt;.  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.
+               <title>Measuring the speaker frequency response using the AUDMES free software GUI - nice free software</title>
+               <link>http://people.skolelinux.org/pere/blog/Measuring_the_speaker_frequency_response_using_the_AUDMES_free_software_GUI___nice_free_software.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Measuring_the_speaker_frequency_response_using_the_AUDMES_free_software_GUI___nice_free_software.html</guid>
+                <pubDate>Mon, 22 Oct 2018 08:40:00 +0200</pubDate>
+               <description>&lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2018-10-22-audmes-measure-speakers.png&quot; align=&quot;right&quot; width=&quot;40%&quot;/&gt;&lt;/p&gt;
+
+&lt;p&gt;My current home stereo is a patchwork of various pieces I got on
+flee markeds over the years.  It is amazing what kind of equipment
+show up there.  I&#39;ve been wondering for a while if it was possible to
+measure how well this equipment is working together, and decided to
+see how far I could get using free software.  After trawling the web I
+came across an article from DIY Audio and Video on
+&lt;a href=&quot;https://www.diyaudioandvideo.com/Tutorial/SpeakerResponseTesting/&quot;&gt;Speaker
+Testing and Analysis&lt;/a&gt; describing how to test speakers, and it listing
+several software options, among them
+&lt;a href=&quot;https://sourceforge.net/projects/audmes/&quot;&gt;AUDio MEasurement
+System (AUDMES)&lt;/a&gt;.  It is the only free software system I could find
+focusing on measuring speakers and audio frequency response.  In the
+process I also found an interesting article from NOVO on
+&lt;a href=&quot;http://novo.press/understanding-speaker-specifications-and-frequency-response/&quot;&gt;Understanding
+Speaker Specifications and Frequency Response&lt;/a&gt; and an article from
+ecoustics on
+&lt;a href=&quot;https://www.ecoustics.com/articles/understanding-speaker-frequency-response/&quot;&gt;Understanding
+Speaker Frequency Response&lt;/a&gt;, with a lot of information on what to
+look for and how to interpret the graphs.  Armed with this knowledge,
+I set out to measure the state of my speakers.&lt;/p&gt;
+
+&lt;p&gt;The first hurdle was that AUDMES hadn&#39;t seen a commit for 10 years
+and did not build with current compilers and libraries.  I got in
+touch with its author, who no longer was spending time on the program
+but gave me write access to the subversion repository on Sourceforge.
+The end result is that now the code build on Linux and is capable of
+saving and loading the collected frequency response data in CSV
+format.  The application is quite nice and flexible, and I was able to
+select the input and output audio interfaces independently.  This made
+it possible to use a USB mixer as the input source, while sending
+output via my laptop headphone connection.  I lacked the hardware and
+cabling to figure out a different way to get independent cabling to
+speakers and microphone.&lt;/p&gt;
+
+&lt;p&gt;Using this setup I could see how a large range of high frequencies
+apparently were not making it out of my speakers.  The picture show
+the frequency response measurement of one of the speakers.  Note the
+frequency lines seem to be slightly misaligned, compared to the CSV
+output from the program.  I can not hear several of these are high
+frequencies, according to measurement from
+&lt;a href=&quot;http://freehearingtestsoftware.com&quot;&gt;Free Hearing Test
+Software&lt;/a&gt;, an freeware system to measure your hearing (still
+looking for a free software alternative), so I do not know if they are
+coming out out the speakers.  I thus do not quite know how to figure
+out if the missing frequencies is a problem with the microphone, the
+amplifier or the speakers, but I managed to rule out the audio card in my
+PC by measuring my Bose noise canceling headset using its own
+microphone.  This setup was able to see the high frequency tones, so
+the problem with my stereo had to be in the amplifier or speakers.&lt;/p&gt;
+
+&lt;p&gt;Anyway, to try to role out one factor I ended up picking up a new
+set of speakers at a flee marked, and these work a lot better than the
+old speakers, so I guess the microphone and amplifier is OK.  If you
+need to measure your own speakers, check out AUDMES.  If more people
+get involved, perhaps the project could become good enough to
+&lt;a href=&quot;https://bugs.debian.org/910876&quot;&gt;include in Debian&lt;/a&gt;?  And if
+you know of some other free software to measure speakers and amplifier
+performance, please let me know.  I am aware of the freeware option
+&lt;a href=&quot;https://www.roomeqwizard.com/&quot;&gt;REW&lt;/a&gt;, but I want something
+that can be developed also when the vendor looses interest.&lt;/p&gt;
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
@@ -566,117 +118,135 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
-               <title>Metadata proposal for movies on the Internet Archive</title>
-               <link>http://people.skolelinux.org/pere/blog/Metadata_proposal_for_movies_on_the_Internet_Archive.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Metadata_proposal_for_movies_on_the_Internet_Archive.html</guid>
-                <pubDate>Tue, 28 Nov 2017 12:00:00 +0100</pubDate>
-               <description>&lt;p&gt;It would be easier to locate the movie you want to watch in
-&lt;a href=&quot;https://www.archive.org/&quot;&gt;the Internet Archive&lt;/a&gt;, 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&#39;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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;Second, I would like the Butter data provider for The Internet
-archive
-(&lt;a href=&quot;https://github.com/butterproviders/butter-provider-archive&quot;&gt;available
-from github&lt;/a&gt;), to list as many of the good movies as possible.  The
-plugin currently do a search in the archive with the following
-parameters:&lt;/p&gt;
+               <title>Web browser integration of VLC with Bittorrent support</title>
+               <link>http://people.skolelinux.org/pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html</guid>
+                <pubDate>Sun, 21 Oct 2018 09:50:00 +0200</pubDate>
+               <description>&lt;p&gt;Bittorrent is as far as I know, currently the most efficient way to
+distribute content on the Internet.  It is used all by all sorts of
+content providers, from national TV stations like
+&lt;a href=&quot;https://www.nrk.no/&quot;&gt;NRK&lt;/a&gt;, Linux distributors like
+&lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; and
+&lt;a href=&quot;https://www.ubuntu.com/&quot;&gt;Ubuntu&lt;/a&gt;, and of course the
+&lt;a href=&quot;https://archive.org/&quot;&gt;Internet archive&lt;/A&gt;.
+
+&lt;p&gt;Almost a month ago
+&lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;a new
+package adding Bittorrent support to VLC&lt;/a&gt; became available in
+Debian testing and unstable.  To test it, simply install it like
+this:&lt;/p&gt;
 
 &lt;p&gt;&lt;pre&gt;
-collection:moviesandfilms
-AND NOT collection:movie_trailers
-AND -mediatype:collection
-AND format:&quot;Archive BitTorrent&quot;
-AND year
+apt install vlc-plugin-bittorrent
 &lt;/pre&gt;&lt;/p&gt;
 
-&lt;p&gt;Most of the cool movies that fail to show up in Butter do so
-because the &#39;year&#39; field is missing.  The &#39;year&#39; field is populated by
-the year part from the &#39;date&#39; field, and should be when the movie was
-released (date or year).  Two such examples are
-&lt;a href=&quot;https://archive.org/details/SidneyOlcottsBen-hur1905&quot;&gt;Ben Hur
-from 1905&lt;/a&gt; and
-&lt;a href=&quot;https://archive.org/details/Caminandes2GranDillama&quot;&gt;Caminandes
-2: Gran Dillama from 2013&lt;/a&gt;, where the year metadata field is
-missing.&lt;/p&gt;
-
-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):
-
-&lt;dl&gt;
-
-&lt;dt&gt;mediatype&lt;/dt&gt;
-&lt;dd&gt;Should be &#39;movie&#39; for movies.&lt;/dd&gt;
-
-&lt;dt&gt;collection&lt;/dt&gt;
-&lt;dd&gt;Should contain &#39;moviesandfilms&#39;.&lt;/dd&gt;
-
-&lt;dt&gt;title&lt;/dt&gt;
-&lt;dd&gt;The title of the movie, without the publication year.&lt;/dd&gt;
+&lt;p&gt;Since the plugin was made available for the first time in Debian,
+several improvements have been made to it.  In version 2.2-4, now
+available in both testing and unstable, a desktop file is provided to
+teach browsers to start VLC when the user click on torrent files or
+magnet links.  The last part is thanks to me finally understanding
+what the strange x-scheme-handler style MIME types in desktop files
+are used for.  By adding x-scheme-handler/magnet to the MimeType entry
+in the desktop file, at least the browsers Firefox and Chromium will
+suggest to start VLC when selecting a magnet URI on a web page.  The
+end result is that now, with the plugin installed in Buster and Sid,
+one can visit any
+&lt;a href=&quot;https://archive.org/details/CopyingIsNotTheft1080p&quot;&gt;Internet
+Archive page with movies&lt;/a&gt; using a web browser and click on the
+torrent link to start streaming the movie.&lt;/p&gt;
+
+&lt;p&gt;Note, there is still some misfeatures in the plugin.  One is the
+fact that it will hang and
+&lt;a href=&quot;https://github.com/johang/vlc-bittorrent/issues/13&quot;&gt;block VLC
+from exiting until the torrent streaming starts&lt;/a&gt;.  Another is the
+fact that it
+&lt;a href=&quot;https://github.com/johang/vlc-bittorrent/issues/9&quot;&gt;will pick
+and play a random file in a multi file torrent&lt;/a&gt;.  This is not
+always the video file you want.  Combined with the first it can be a
+bit hard to get the video streaming going.  But when it work, it seem
+to do a good job.&lt;/p&gt;
+
+&lt;p&gt;For the Debian packaging, I would love to find a good way to test
+if the plugin work with VLC using autopkgtest.  I tried, but do not
+know enough of the inner workings of VLC to get it working.  For now
+the autopkgtest script is only checking if the .so file was
+successfully loaded by VLC.  If you have any suggestions, please
+submit a patch to the Debian bug tracking system.&lt;/p&gt;
 
-&lt;dt&gt;date&lt;/dt&gt;
-&lt;dd&gt;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.&lt;/dd&gt;
-
-&lt;dt&gt;director&lt;/dt&gt;
-&lt;dd&gt;The director of the movie.  This make it easier to know if the
-correct movie is found in movie databases.&lt;/dd&gt;
-
-&lt;dt&gt;publisher&lt;/dt&gt;
-&lt;dd&gt;The production company making the movie.  Also useful for
-identifying the correct movie.&lt;/dd&gt;
-
-&lt;dt&gt;links&lt;/dt&gt;
-
-&lt;dd&gt;Add a link to the IMDB title page, for example like this: &amp;lt;a
-href=&quot;http://www.imdb.com/title/tt0028496/&quot;&amp;gt;Movie in
-IMDB&amp;lt;/a&amp;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.&lt;/dd&gt;
-
-&lt;/dl&gt;
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+</description>
+       </item>
+       
+       <item>
+               <title>Release 0.2 of free software archive system Nikita announced</title>
+               <link>http://people.skolelinux.org/pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html</guid>
+                <pubDate>Thu, 18 Oct 2018 14:40:00 +0200</pubDate>
+               <description>&lt;p&gt;This morning, the new release of the
+&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;Nikita
+Noark 5 core project&lt;/a&gt; was
+&lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2018-October/000406.html&quot;&gt;announced
+on the project mailing list&lt;/a&gt;.  The free software solution is an
+implementation of the Norwegian archive standard Noark 5 used by
+government offices in Norway.  These were the changes in version 0.2
+since version 0.1.1 (from NEWS.md):
 
-&lt;p&gt;I did consider proposing a Custom field for the IMDB title ID (for
-example &#39;imdb_title_url&#39;, &#39;imdb_code&#39; or simply &#39;imdb&#39;, but suspect it
-will be easier to simply place it in the links free text field.&lt;/p&gt;
+&lt;ul&gt;
+  &lt;li&gt;Fix typos in REL names&lt;/li&gt;
+  &lt;li&gt;Tidy up error message reporting&lt;/li&gt;
+  &lt;li&gt;Fix issue where we used Integer.valueOf(), not Integer.getInteger()&lt;/li&gt;
+  &lt;li&gt;Change some String handling to StringBuffer&lt;/li&gt;
+  &lt;li&gt;Fix error reporting&lt;/li&gt;
+  &lt;li&gt;Code tidy-up&lt;/li&gt;
+  &lt;li&gt;Fix issue using static non-synchronized SimpleDateFormat to avoid 
+      race conditions&lt;/li&gt;
+  &lt;li&gt;Fix problem where deserialisers were treating integers as strings&lt;/li&gt;
+  &lt;li&gt;Update methods to make them null-safe&lt;/li&gt;
+  &lt;li&gt;Fix many issues reported by coverity&lt;/li&gt;
+  &lt;li&gt;Improve equals(), compareTo() and hash() in domain model&lt;/li&gt;
+  &lt;li&gt;Improvements to the domain model for metadata classes&lt;/li&gt;
+  &lt;li&gt;Fix CORS issues when downloading document&lt;/li&gt;
+  &lt;li&gt;Implementation of case-handling with registryEntry and document upload&lt;/li&gt;
+  &lt;li&gt;Better support in Javascript for OPTIONS&lt;/li&gt;
+  &lt;li&gt;Adding concept description of mail integration&lt;/li&gt;
+  &lt;li&gt;Improve setting of default values for GET on ny-journalpost&lt;/li&gt;
+  &lt;li&gt;Better handling of required values during deserialisation &lt;/li&gt;
+  &lt;li&gt;Changed tilknyttetDato (M620) from date to dateTime&lt;/li&gt;
+  &lt;li&gt;Corrected some opprettetDato (M600) (de)serialisation errors.&lt;/li&gt;
+  &lt;li&gt;Improve parse error reporting.&lt;/li&gt;
+  &lt;li&gt;Started on OData search and filtering.&lt;/li&gt;
+  &lt;li&gt;Added Contributor Covenant Code of Conduct to project.&lt;/li&gt;
+  &lt;li&gt;Moved repository and project from Github to Gitlab.&lt;/li&gt;
+  &lt;li&gt;Restructured repository, moved code into src/ and web/.&lt;/li&gt;
+  &lt;li&gt;Updated code to use Spring Boot version 2.&lt;/li&gt;
+  &lt;li&gt;Added support for OAuth2 authentication.&lt;/li&gt;
+  &lt;li&gt;Fixed several bugs discovered by Coverity.&lt;/li&gt;
+  &lt;li&gt;Corrected handling of date/datetime fields.&lt;/li&gt;
+  &lt;li&gt;Improved error reporting when rejecting during deserializatoin.&lt;/li&gt;
+  &lt;li&gt;Adjusted default values provided for ny-arkivdel, ny-mappe,
+   ny-saksmappe, ny-journalpost and ny-dokumentbeskrivelse.&lt;/li&gt;
+  &lt;li&gt;Several fixes for korrespondansepart*.&lt;/li&gt;
+  &lt;li&gt;Updated web GUI:
+     &lt;ul&gt;
+       &lt;li&gt;Now handle both file upload and download.&lt;/li&gt;
+       &lt;li&gt;Uses new OAuth2 authentication for login.&lt;/li&gt;
+       &lt;li&gt;Forms now fetches default values from API using GET.&lt;/li&gt;
+       &lt;li&gt;Added RFC 822 (email), TIFF and JPEG to list of possible file formats.&lt;/li&gt;
+     &lt;/ul&gt;&lt;/li&gt;
+&lt;/ul&gt;
 
-&lt;p&gt;I created
-&lt;a href=&quot;https://github.com/petterreinholdtsen/public-domain-free-imdb&quot;&gt;a
-list of IMDB title IDs for several thousand movies in the Internet
-Archive&lt;/a&gt;, 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. :)&lt;/p&gt;
+&lt;p&gt;The changes and improvements are extensive.  Running diffstat on
+the changes between git tab 0.1.1 and 0.2 show 1098 files changed,
+108666 insertions(+), 54066 deletions(-).&lt;/p&gt;
 
-&lt;p&gt;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 &lt;a href=&quot;https://en.wikipedia.org/wiki/Caminandes&quot;&gt;the
-Caminandes example above&lt;/a&gt;, where there are three movies but only
-one Wikidata entry).&lt;/p&gt;
+&lt;p&gt;If free and open standardized archiving API sound interesting to
+you, please contact us on IRC
+(&lt;a href=&quot;irc://irc.freenode.net/%23nikita&quot;&gt;#nikita on
+irc.freenode.net&lt;/a&gt;) or email
+(&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
+mailing list&lt;/a&gt;).&lt;/p&gt;
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
@@ -685,69 +255,104 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
-               <title>Legal to share more than 3000 movies listed on IMDB?</title>
-               <link>http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html</guid>
-                <pubDate>Sat, 18 Nov 2017 21:20:00 +0100</pubDate>
-               <description>&lt;p&gt;A month ago, I blogged about my work to
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html&quot;&gt;automatically
-check the copyright status of IMDB entries&lt;/a&gt;, 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
-&lt;a href=&quot;https://github.com/petterreinholdtsen/public-domain-free-imdb&quot;&gt;a
-git repository&lt;/a&gt;, currently available from github.&lt;/p&gt;
-
-&lt;p&gt;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?&lt;/p&gt;
-
-&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2017-11-18-verk-i-det-fri-filmer.png&quot; /&gt;&lt;/p&gt;
-
-&lt;p&gt;I&#39;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 &#39;make stats&#39; in the git repository:&lt;/p&gt;
+               <title>Fetching trusted timestamps using the rfc3161ng python module</title>
+               <link>http://people.skolelinux.org/pere/blog/Fetching_trusted_timestamps_using_the_rfc3161ng_python_module.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fetching_trusted_timestamps_using_the_rfc3161ng_python_module.html</guid>
+                <pubDate>Mon, 8 Oct 2018 12:30:00 +0200</pubDate>
+               <description>&lt;p&gt;I have  earlier covered the basics of trusted timestamping using the
+&#39;openssl ts&#39; client.  See blog post for
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Public_Trusted_Timestamping_services_for_everyone.html&quot;&gt;2014&lt;/a&gt;,
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/syslog_trusted_timestamp___chain_of_trusted_timestamps_for_your_syslog.html&quot;&gt;2016&lt;/a&gt;
+and
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html&quot;&gt;2017&lt;/a&gt;
+for those stories.  But some times I want to integrate the timestamping
+in other code, and recently I needed to integrate it into Python.
+After searching a bit, I found
+&lt;a href=&quot;https://dev.entrouvert.org/projects/python-rfc3161&quot;&gt;the
+rfc3161 library&lt;/a&gt; which seemed like a good fit, but I soon
+discovered it only worked for python version 2, and I needed something
+that work with python version 3.  Luckily I next came across
+&lt;a href=&quot;https://github.com/trbs/rfc3161ng/&quot;&gt;the rfc3161ng library&lt;/a&gt;,
+a fork of the original rfc3161 library.  Not only is it working with
+python 3, it have fixed a few of the bugs in the original library, and
+it has an active maintainer.  I decided to wrap it up and make it
+&lt;a href=&quot;https://tracker.debian.org/pkg/python-rfc3161ng&quot;&gt;available in
+Debian&lt;/a&gt;, and a few days ago it entered Debian unstable and testing.&lt;/p&gt;
+
+&lt;p&gt;Using the library is fairly straight forward.  The only slightly
+problematic step is to fetch the required certificates to verify the
+timestamp.  For some services it is straight forward, while for others
+I have not yet figured out how to do it.  Here is a small standalone
+code example based on of the integration tests in the library code:&lt;/p&gt;
 
 &lt;pre&gt;
-  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
+#!/usr/bin/python3
+
+&quot;&quot;&quot;
+
+Python 3 script demonstrating how to use the rfc3161ng module to
+get trusted timestamps.
+
+The license of this code is the same as the license of the rfc3161ng
+library, ie MIT/BSD.
+
+&quot;&quot;&quot;
+
+import os
+import pyasn1.codec.der
+import rfc3161ng
+import subprocess
+import tempfile
+import urllib.request
+
+def store(f, data):
+    f.write(data)
+    f.flush()
+    f.seek(0)
+
+def fetch(url, f=None):
+    response = urllib.request.urlopen(url)
+    data = response.read()
+    if f:
+        store(f, data)
+    return data
+
+def main():
+    with tempfile.NamedTemporaryFile() as cert_f,\
+        tempfile.NamedTemporaryFile() as ca_f,\
+        tempfile.NamedTemporaryFile() as msg_f,\
+        tempfile.NamedTemporaryFile() as tsr_f:
+
+        # First fetch certificates used by service
+        certificate_data = fetch(&#39;https://freetsa.org/files/tsa.crt&#39;, cert_f)
+        ca_data_data = fetch(&#39;https://freetsa.org/files/cacert.pem&#39;, ca_f)
+
+        # Then timestamp the message
+        timestamper = \
+            rfc3161ng.RemoteTimestamper(&#39;http://freetsa.org/tsr&#39;,
+                                        certificate=certificate_data)
+        data = b&quot;Python forever!\n&quot;
+        tsr = timestamper(data=data, return_tsr=True)
+
+        # Finally, convert message and response to something &#39;openssl ts&#39; can verify
+        store(msg_f, data)
+        store(tsr_f, pyasn1.codec.der.encoder.encode(tsr))
+        args = [&quot;openssl&quot;, &quot;ts&quot;, &quot;-verify&quot;,
+                &quot;-data&quot;, msg_f.name,
+               &quot;-in&quot;, tsr_f.name,
+               &quot;-CAfile&quot;, ca_f.name,
+                &quot;-untrusted&quot;, cert_f.name]
+        subprocess.check_call(args)
+
+if &#39;__main__&#39; == __name__:
+   main()
 &lt;/pre&gt;
 
-&lt;p&gt;The 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&#39;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.
-
-&lt;p&gt;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?&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
+&lt;p&gt;The code fetches the required certificates, store them as temporary
+files, timestamp a simple message, store the message and timestamp to
+disk and ask &#39;openssl ts&#39; to verify the timestamp.  A timestamp is
+around 1.5 kiB in size, and should be fairly easy to store for future
+use.&lt;/p&gt;
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
@@ -756,80 +361,61 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
-               <title>Some notes on fault tolerant storage systems</title>
-               <link>http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html</guid>
-                <pubDate>Wed, 1 Nov 2017 15:35:00 +0100</pubDate>
-               <description>&lt;p&gt;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.&lt;/p&gt;
-
-&lt;ul&gt;
-
-&lt;li&gt;USENIX :login; &lt;a
-href=&quot;https://www.usenix.org/publications/login/summer2017/ganesan&quot;&gt;Redundancy
-Does Not Imply Fault Tolerance.  Analysis of Distributed Storage
-Reactions to Single Errors and Corruptions&lt;/a&gt; by Aishwarya Ganesan,
-Ramnatthan Alagappan, Andrea C. Arpaci-Dusseau, and Remzi
-H. Arpaci-Dusseau&lt;/li&gt;
-
-&lt;li&gt;ZDNet
-&lt;a href=&quot;http://www.zdnet.com/article/why-raid-5-stops-working-in-2009/&quot;&gt;Why
-RAID 5 stops working in 2009&lt;/a&gt; by Robin Harris&lt;/li&gt;
-
-&lt;li&gt;ZDNet
-&lt;a href=&quot;http://www.zdnet.com/article/why-raid-6-stops-working-in-2019/&quot;&gt;Why
-RAID 6 stops working in 2019&lt;/a&gt; by Robin Harris&lt;/li&gt;
-
-&lt;li&gt;USENIX FAST&#39;07
-&lt;a href=&quot;http://research.google.com/archive/disk_failures.pdf&quot;&gt;Failure
-Trends in a Large Disk Drive Population&lt;/a&gt; by Eduardo Pinheiro,
-Wolf-Dietrich Weber and Luiz André Barroso&lt;/li&gt;
-
-&lt;li&gt;USENIX ;login: &lt;a
-href=&quot;https://www.usenix.org/system/files/login/articles/hughes12-04.pdf&quot;&gt;Data
-Integrity.  Finding Truth in a World of Guesses and Lies&lt;/a&gt; by Doug
-Hughes&lt;/li&gt;
-
-&lt;li&gt;USENIX FAST&#39;08
-&lt;a href=&quot;https://www.usenix.org/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/&quot;&gt;An
-Analysis of Data Corruption in the Storage Stack&lt;/a&gt; by
-L. N. Bairavasundaram, G. R. Goodson, B. Schroeder, A. C.
-Arpaci-Dusseau, and R. H. Arpaci-Dusseau&lt;/li&gt;
-
-&lt;li&gt;USENIX FAST&#39;07 &lt;a
-href=&quot;https://www.usenix.org/legacy/events/fast07/tech/schroeder/schroeder_html/&quot;&gt;Disk
-failures in the real world: what does an MTTF of 1,000,000 hours mean
-to you?&lt;/a&gt; by B. Schroeder and G. A. Gibson.&lt;/li&gt;
-
-&lt;li&gt;USENIX ;login: &lt;a
-href=&quot;https://www.usenix.org/events/fast08/tech/full_papers/jiang/jiang_html/&quot;&gt;Are
-Disks the Dominant Contributor for Storage Failures?  A Comprehensive
-Study of Storage Subsystem Failure Characteristics&lt;/a&gt; by Weihang
-Jiang, Chongfeng Hu, Yuanyuan Zhou, and Arkady Kanevsky&lt;/li&gt;
-
-&lt;li&gt;SIGMETRICS 2007
-&lt;a href=&quot;http://research.cs.wisc.edu/adsl/Publications/latent-sigmetrics07.pdf&quot;&gt;An
-analysis of latent sector errors in disk drives&lt;/a&gt; by
-L. N. Bairavasundaram, G. R. Goodson, S. Pasupathy, and J. Schindler&lt;/li&gt;
-
-&lt;/ul&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
+               <title>Automatic Google Drive sync using grive in Debian</title>
+               <link>http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
+                <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
+               <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian.  To try to
+rescue the remains, I helped set up automatic sync with Google Drive.
+I did not find any sensible Debian package handling this
+automatically, so I rebuild the grive2 source from
+&lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
+task and added a autostart desktop entry and a small shell script to
+run in the background while the user is logged in to do the sync.
+Here is a sketch of the setup for future reference.&lt;/p&gt;
+
+&lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
+ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user.  Next, I
+created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
+to start the sync when the user log in:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+[Desktop Entry]
+Name=Google drive autosync
+Type=Application
+Exec=/home/user/bin/grive-sync
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
+~/googledrive/ with the files in Google Drive.&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+#!/bin/sh
+set -e
+cd ~/
+cleanup() {
+    if [ &quot;$syncpid&quot; ] ; then
+        kill $syncpid
+    fi
+}
+trap cleanup EXIT INT QUIT
+/usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
+syncpdi=$!
+while true; do
+    if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
+        echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
+        exit 1
+    fi
+    if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
+        /usr/lib/grive/grive-sync.sh sync googledrive
+    fi
+    sleep 300
+done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Feel free to use the setup if you want.  It can be assumed to be
+GNU GPL v2 licensed (or any later version, at your leisure), but I
+doubt this code is possible to claim copyright on.&lt;/p&gt;
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
@@ -838,42 +424,154 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
-               <title>Web services for writing academic LaTeX papers as a team</title>
-               <link>http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html</guid>
-                <pubDate>Tue, 31 Oct 2017 21:00:00 +0100</pubDate>
-               <description>&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;There are two commercial services available,
-&lt;a href=&quot;https://sharelatex.com&quot;&gt;ShareLaTeX&lt;/a&gt; and
-&lt;a href=&quot;https://overleaf.com&quot;&gt;Overleaf&lt;/a&gt;.  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&#39;ve used both for different documents, and they
-work just fine.  While
-&lt;a href=&quot;https://github.com/sharelatex/sharelatex&quot;&gt;ShareLaTeX is free
-software&lt;/a&gt;, while the latter is not.  According to &lt;a
-href=&quot;https://www.overleaf.com/help/17-is-overleaf-open-source&quot;&gt;a
-announcement from Overleaf&lt;/a&gt;, they plan to keep the ShareLaTeX code
-base maintained as free software.&lt;/p&gt;
-
-But these two are not the only alternatives.
-&lt;a href=&quot;https://app.fiduswriter.org/&quot;&gt;Fidus Writer&lt;/a&gt; is another free
-software solution with &lt;a href=&quot;https://github.com/fiduswriter&quot;&gt;the
-source available on github&lt;/a&gt;.  I have not used it myself.  Several
-others can be found on the nice
-&lt;a href=&quot;https://alternativeto.net/software/sharelatex/&quot;&gt;alterntiveTo
-web service&lt;/a&gt;.
-
-&lt;p&gt;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. :)&lt;/p&gt;
+               <title>Valutakrambod - A python and bitcoin love story</title>
+               <link>http://people.skolelinux.org/pere/blog/Valutakrambod___A_python_and_bitcoin_love_story.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Valutakrambod___A_python_and_bitcoin_love_story.html</guid>
+                <pubDate>Sat, 29 Sep 2018 22:20:00 +0200</pubDate>
+               <description>&lt;p&gt;It would come as no surprise to anyone that I am interested in
+bitcoins and virtual currencies.  I&#39;ve been keeping an eye on virtual
+currencies for many years, and it is part of the reason a few months
+ago, I started writing a python library for collecting currency
+exchange rates and trade on virtual currency exchanges.  I decided to
+name the end result valutakrambod, which perhaps can be translated to
+small currency shop.&lt;/p&gt;
+
+&lt;p&gt;The library uses the tornado python library to handle HTTP and
+websocket connections, and provide a asynchronous system for
+connecting to and tracking several services.  The code is available
+from
+&lt;a href=&quot;http://github.com/petterreinholdtsen/valutakrambod&quot;&gt;github&lt;/a&gt;.&lt;/p&gt;
+
+&lt;/p&gt;There are two example clients of the library.  One is very simple and
+list every updated buy/sell price received from the various services.
+This code is started by running bin/btc-rates and call the client code
+in valutakrambod/client.py.  The simple client look like this:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+import functools
+import tornado.ioloop
+import valutakrambod
+class SimpleClient(object):
+    def __init__(self):
+        self.services = []
+        self.streams = []
+        pass
+    def newdata(self, service, pair, changed):
+        print(&quot;%-15s %s-%s: %8.3f %8.3f&quot; % (
+            service.servicename(),
+            pair[0],
+            pair[1],
+            service.rates[pair][&#39;ask&#39;],
+            service.rates[pair][&#39;bid&#39;])
+        )
+    async def refresh(self, service):
+        await service.fetchRates(service.wantedpairs)
+    def run(self):
+        self.ioloop = tornado.ioloop.IOLoop.current()
+        self.services = valutakrambod.service.knownServices()
+        for e in self.services:
+            service = e()
+            service.subscribe(self.newdata)
+            stream = service.websocket()
+            if stream:
+                self.streams.append(stream)
+            else:
+                # Fetch information from non-streaming services immediately
+                self.ioloop.call_later(len(self.services),
+                                       functools.partial(self.refresh, service))
+                # as well as regularly
+                service.periodicUpdate(60)
+        for stream in self.streams:
+            stream.connect()
+        try:
+            self.ioloop.start()
+        except KeyboardInterrupt:
+            print(&quot;Interrupted by keyboard, closing all connections.&quot;)
+            pass
+        for stream in self.streams:
+            stream.close()
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;The library client loops over all known &quot;public&quot; services,
+initialises it, subscribes to any updates from the service, checks and
+activates websocket streaming if the service provide it, and if no
+streaming is supported, fetches information from the service and sets
+up a periodic update every 60 seconds.  The output from this client
+can look like this:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+Bl3p            BTC-EUR: 5687.110 5653.690
+Bl3p            BTC-EUR: 5687.110 5653.690
+Bl3p            BTC-EUR: 5687.110 5653.690
+Hitbtc          BTC-USD: 6594.560 6593.690
+Hitbtc          BTC-USD: 6594.560 6593.690
+Bl3p            BTC-EUR: 5687.110 5653.690
+Hitbtc          BTC-USD: 6594.570 6593.690
+Bitstamp        EUR-USD:    1.159    1.154
+Hitbtc          BTC-USD: 6594.570 6593.690
+Hitbtc          BTC-USD: 6594.580 6593.690
+Hitbtc          BTC-USD: 6594.580 6593.690
+Hitbtc          BTC-USD: 6594.580 6593.690
+Bl3p            BTC-EUR: 5687.110 5653.690
+Paymium         BTC-EUR: 5680.000 5620.240
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;The exchange order book is tracked in addition to the best buy/sell
+price, for those that need to know the details.&lt;/p&gt;
+
+&lt;p&gt;The other example client is focusing on providing a curses view
+with updated buy/sell prices as soon as they are received from the
+services.  This code is located in bin/btc-rates-curses and activated
+by using the &#39;-c&#39; argument.  Without the argument the &quot;curses&quot; output
+is printed without using curses, which is useful for debugging.  The
+curses view look like this:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+           Name Pair   Bid         Ask         Spr    Ftcd    Age
+ BitcoinsNorway BTCEUR   5591.8400   5711.0800   2.1%   16    nan     60
+       Bitfinex BTCEUR   5671.0000   5671.2000   0.0%   16     22     59
+        Bitmynt BTCEUR   5580.8000   5807.5200   3.9%   16     41     60
+         Bitpay BTCEUR   5663.2700         nan   nan%   15    nan     60
+       Bitstamp BTCEUR   5664.8400   5676.5300   0.2%    0      1      1
+           Bl3p BTCEUR   5653.6900   5684.9400   0.5%    0    nan     19
+       Coinbase BTCEUR   5600.8200   5714.9000   2.0%   15    nan    nan
+         Kraken BTCEUR   5670.1000   5670.2000   0.0%   14     17     60
+        Paymium BTCEUR   5620.0600   5680.0000   1.1%    1   7515    nan
+ BitcoinsNorway BTCNOK  52898.9700  54034.6100   2.1%   16    nan     60
+        Bitmynt BTCNOK  52960.3200  54031.1900   2.0%   16     41     60
+         Bitpay BTCNOK  53477.7833         nan   nan%   16    nan     60
+       Coinbase BTCNOK  52990.3500  54063.0600   2.0%   15    nan    nan
+        MiraiEx BTCNOK  52856.5300  54100.6000   2.3%   16    nan    nan
+ BitcoinsNorway BTCUSD   6495.5300   6631.5400   2.1%   16    nan     60
+       Bitfinex BTCUSD   6590.6000   6590.7000   0.0%   16     23     57
+         Bitpay BTCUSD   6564.1300         nan   nan%   15    nan     60
+       Bitstamp BTCUSD   6561.1400   6565.6200   0.1%    0      2      1
+       Coinbase BTCUSD   6504.0600   6635.9700   2.0%   14    nan    117
+         Gemini BTCUSD   6567.1300   6573.0700   0.1%   16     89    nan
+         Hitbtc+BTCUSD   6592.6200   6594.2100   0.0%    0      0      0
+         Kraken BTCUSD   6565.2000   6570.9000   0.1%   15     17     58
+  Exchangerates EURNOK      9.4665      9.4665   0.0%   16 107789    nan
+     Norgesbank EURNOK      9.4665      9.4665   0.0%   16 107789    nan
+       Bitstamp EURUSD      1.1537      1.1593   0.5%    4      5      1
+  Exchangerates EURUSD      1.1576      1.1576   0.0%   16 107789    nan
+ BitcoinsNorway LTCEUR      1.0000     49.0000  98.0%   16    nan    nan
+ BitcoinsNorway LTCNOK    492.4800    503.7500   2.2%   16    nan     60
+ BitcoinsNorway LTCUSD      1.0221     49.0000  97.9%   15    nan    nan
+     Norgesbank USDNOK      8.1777      8.1777   0.0%   16 107789    nan
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;The code for this client is too complex for a simple blog post, so
+you will have to check out the git repository to figure out how it
+work.  What I can tell is how the three last numbers on each line
+should be interpreted.  The first is how many seconds ago information
+was received from the service.  The second is how long ago, according
+to the service, the provided information was updated.  The last is an
+estimate on how often the buy/sell values change.&lt;/p&gt;
+
+&lt;p&gt;If you find this library useful, or would like to improve it, I
+would love to hear from you.  Note that for some of the services I&#39;ve
+implemented a trading API.  It might be the topic of a future blog
+post.&lt;/p&gt;
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
@@ -882,285 +580,40 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
-               <title>Locating IMDB IDs of movies in the Internet Archive using Wikidata</title>
-               <link>http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html</guid>
-                <pubDate>Wed, 25 Oct 2017 12:20:00 +0200</pubDate>
-               <description>&lt;p&gt;Recently, I needed to automatically check the copyright status of a
-set of &lt;a href=&quot;http://www.imdb.com/&quot;&gt;The Internet Movie database
-(IMDB)&lt;/a&gt; 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.&lt;/p&gt;
-
-&lt;p&gt;First I tried to look up entries manually in IMDB,
-&lt;a href=&quot;https://www.wikipedia.org/&quot;&gt;Wikipedia&lt;/a&gt; and
-&lt;a href=&quot;https://www.archive.org/&quot;&gt;The Internet Archive&lt;/a&gt;, 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 &quot;out
-of copyright&quot; 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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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 &lt;a href=&quot;https://query.wikidata.org/&quot;&gt;the SPARQL interface on
-Wikidata&lt;/a&gt;:
-
-&lt;p&gt;&lt;pre&gt;
-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) = &quot;en&quot;).
-  }
-}
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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 &quot;disappearing&quot;
-entries (ie 2338-2097-171) are duplicate entries.&lt;/p&gt;
-
-&lt;p&gt;This is not too bad, given that The Internet Archive report to
-contain &lt;a href=&quot;https://archive.org/details/feature_films&quot;&gt;5331
-feature films&lt;/a&gt; at the moment, but it also mean more than 3000
-movies are missing on Wikipedia or are missing the pair of references
-on Wikipedia.&lt;/p&gt;
-
-&lt;p&gt;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:&lt;p&gt;
-
-&lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2017-10-25-verk-i-det-fri-filmer.png&quot;&gt;&lt;/p&gt;
-
-&lt;p&gt;I expect the relative distribution of the remaining 3000 movies to
-be similar.&lt;/p&gt;
-
-&lt;p&gt;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 &quot;External
-links&quot; heading on the Wikipedia article for the movie:&lt;/p&gt;
-
-&lt;p&gt;&lt;pre&gt;
-* {{Internet Archive film|id=FightingLady}}
-* {{IMDb title|id=0036823|title=The Fighting Lady}}
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;Please verify the links on the final page, to make sure you did not
-introduce a typo.&lt;/p&gt;
-
-&lt;p&gt;Here is the complete list, if you want to correct the 171
-identified Wikipedia entries with broken links to The Internet
-Archive: &lt;a href=&quot;http://www.wikidata.org/entity/Q1140317&quot;&gt;Q1140317&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q458656&quot;&gt;Q458656&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q458656&quot;&gt;Q458656&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q470560&quot;&gt;Q470560&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q743340&quot;&gt;Q743340&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q822580&quot;&gt;Q822580&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q480696&quot;&gt;Q480696&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q128761&quot;&gt;Q128761&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1307059&quot;&gt;Q1307059&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1335091&quot;&gt;Q1335091&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1537166&quot;&gt;Q1537166&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1438334&quot;&gt;Q1438334&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1479751&quot;&gt;Q1479751&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1497200&quot;&gt;Q1497200&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1498122&quot;&gt;Q1498122&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q865973&quot;&gt;Q865973&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q834269&quot;&gt;Q834269&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q841781&quot;&gt;Q841781&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q841781&quot;&gt;Q841781&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1548193&quot;&gt;Q1548193&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q499031&quot;&gt;Q499031&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1564769&quot;&gt;Q1564769&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1585239&quot;&gt;Q1585239&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1585569&quot;&gt;Q1585569&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1624236&quot;&gt;Q1624236&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q4796595&quot;&gt;Q4796595&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q4853469&quot;&gt;Q4853469&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q4873046&quot;&gt;Q4873046&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q915016&quot;&gt;Q915016&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q4660396&quot;&gt;Q4660396&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q4677708&quot;&gt;Q4677708&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q4738449&quot;&gt;Q4738449&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q4756096&quot;&gt;Q4756096&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q4766785&quot;&gt;Q4766785&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q880357&quot;&gt;Q880357&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q882066&quot;&gt;Q882066&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q882066&quot;&gt;Q882066&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q204191&quot;&gt;Q204191&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q204191&quot;&gt;Q204191&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1194170&quot;&gt;Q1194170&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q940014&quot;&gt;Q940014&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q946863&quot;&gt;Q946863&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q172837&quot;&gt;Q172837&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q573077&quot;&gt;Q573077&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1219005&quot;&gt;Q1219005&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1219599&quot;&gt;Q1219599&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1643798&quot;&gt;Q1643798&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1656352&quot;&gt;Q1656352&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1659549&quot;&gt;Q1659549&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1660007&quot;&gt;Q1660007&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1698154&quot;&gt;Q1698154&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1737980&quot;&gt;Q1737980&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1877284&quot;&gt;Q1877284&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1199354&quot;&gt;Q1199354&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1199354&quot;&gt;Q1199354&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1199451&quot;&gt;Q1199451&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1211871&quot;&gt;Q1211871&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1212179&quot;&gt;Q1212179&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1238382&quot;&gt;Q1238382&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q4906454&quot;&gt;Q4906454&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q320219&quot;&gt;Q320219&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1148649&quot;&gt;Q1148649&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q645094&quot;&gt;Q645094&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5050350&quot;&gt;Q5050350&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5166548&quot;&gt;Q5166548&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2677926&quot;&gt;Q2677926&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2698139&quot;&gt;Q2698139&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2707305&quot;&gt;Q2707305&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2740725&quot;&gt;Q2740725&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2024780&quot;&gt;Q2024780&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2117418&quot;&gt;Q2117418&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2138984&quot;&gt;Q2138984&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1127992&quot;&gt;Q1127992&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1058087&quot;&gt;Q1058087&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1070484&quot;&gt;Q1070484&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1080080&quot;&gt;Q1080080&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1090813&quot;&gt;Q1090813&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1251918&quot;&gt;Q1251918&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1254110&quot;&gt;Q1254110&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1257070&quot;&gt;Q1257070&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1257079&quot;&gt;Q1257079&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1197410&quot;&gt;Q1197410&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1198423&quot;&gt;Q1198423&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q706951&quot;&gt;Q706951&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q723239&quot;&gt;Q723239&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2079261&quot;&gt;Q2079261&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1171364&quot;&gt;Q1171364&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q617858&quot;&gt;Q617858&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5166611&quot;&gt;Q5166611&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5166611&quot;&gt;Q5166611&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q324513&quot;&gt;Q324513&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q374172&quot;&gt;Q374172&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7533269&quot;&gt;Q7533269&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q970386&quot;&gt;Q970386&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q976849&quot;&gt;Q976849&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7458614&quot;&gt;Q7458614&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5347416&quot;&gt;Q5347416&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5460005&quot;&gt;Q5460005&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5463392&quot;&gt;Q5463392&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3038555&quot;&gt;Q3038555&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5288458&quot;&gt;Q5288458&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2346516&quot;&gt;Q2346516&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5183645&quot;&gt;Q5183645&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5185497&quot;&gt;Q5185497&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5216127&quot;&gt;Q5216127&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5223127&quot;&gt;Q5223127&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5261159&quot;&gt;Q5261159&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q1300759&quot;&gt;Q1300759&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q5521241&quot;&gt;Q5521241&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7733434&quot;&gt;Q7733434&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7736264&quot;&gt;Q7736264&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7737032&quot;&gt;Q7737032&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7882671&quot;&gt;Q7882671&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7719427&quot;&gt;Q7719427&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7719444&quot;&gt;Q7719444&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7722575&quot;&gt;Q7722575&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2629763&quot;&gt;Q2629763&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2640346&quot;&gt;Q2640346&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2649671&quot;&gt;Q2649671&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7703851&quot;&gt;Q7703851&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7747041&quot;&gt;Q7747041&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q6544949&quot;&gt;Q6544949&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q6672759&quot;&gt;Q6672759&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2445896&quot;&gt;Q2445896&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q12124891&quot;&gt;Q12124891&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3127044&quot;&gt;Q3127044&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2511262&quot;&gt;Q2511262&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2517672&quot;&gt;Q2517672&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2543165&quot;&gt;Q2543165&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q426628&quot;&gt;Q426628&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q426628&quot;&gt;Q426628&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q12126890&quot;&gt;Q12126890&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q13359969&quot;&gt;Q13359969&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q13359969&quot;&gt;Q13359969&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2294295&quot;&gt;Q2294295&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2294295&quot;&gt;Q2294295&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2559509&quot;&gt;Q2559509&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2559912&quot;&gt;Q2559912&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7760469&quot;&gt;Q7760469&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q6703974&quot;&gt;Q6703974&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q4744&quot;&gt;Q4744&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7766962&quot;&gt;Q7766962&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7768516&quot;&gt;Q7768516&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7769205&quot;&gt;Q7769205&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7769988&quot;&gt;Q7769988&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q2946945&quot;&gt;Q2946945&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3212086&quot;&gt;Q3212086&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3212086&quot;&gt;Q3212086&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q18218448&quot;&gt;Q18218448&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q18218448&quot;&gt;Q18218448&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q18218448&quot;&gt;Q18218448&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q6909175&quot;&gt;Q6909175&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7405709&quot;&gt;Q7405709&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7416149&quot;&gt;Q7416149&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7239952&quot;&gt;Q7239952&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7317332&quot;&gt;Q7317332&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7783674&quot;&gt;Q7783674&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7783704&quot;&gt;Q7783704&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7857590&quot;&gt;Q7857590&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3372526&quot;&gt;Q3372526&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3372642&quot;&gt;Q3372642&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3372816&quot;&gt;Q3372816&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3372909&quot;&gt;Q3372909&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7959649&quot;&gt;Q7959649&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7977485&quot;&gt;Q7977485&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q7992684&quot;&gt;Q7992684&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3817966&quot;&gt;Q3817966&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3821852&quot;&gt;Q3821852&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3420907&quot;&gt;Q3420907&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q3429733&quot;&gt;Q3429733&lt;/a&gt;, 
-&lt;a href=&quot;http://www.wikidata.org/entity/Q774474&quot;&gt;Q774474&lt;/a&gt;&lt;/p&gt;
+               <title>VLC in Debian now can do bittorrent streaming</title>
+               <link>http://people.skolelinux.org/pere/blog/VLC_in_Debian_now_can_do_bittorrent_streaming.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/VLC_in_Debian_now_can_do_bittorrent_streaming.html</guid>
+                <pubDate>Mon, 24 Sep 2018 21:20:00 +0200</pubDate>
+               <description>&lt;p&gt;Back in February, I got curious to see
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Using_VLC_to_stream_bittorrent_sources.html&quot;&gt;if
+VLC now supported Bittorrent streaming&lt;/a&gt;.  It did not, despite the
+fact that the idea and code to handle such streaming had been floating
+around for years.  I did however find
+&lt;a href=&quot;https://github.com/johang/vlc-bittorrent&quot;&gt;a standalone plugin
+for VLC&lt;/a&gt; to do it, and half a year later I decided to wrap up the
+plugin and get it into Debian.  I uploaded it to NEW a few days ago,
+and am very happy to report that it
+&lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;entered
+Debian&lt;/a&gt; a few hours ago, and should be available in Debian/Unstable
+tomorrow, and Debian/Testing in a few days.&lt;/p&gt;
+
+&lt;p&gt;With the vlc-plugin-bittorrent package installed you should be able
+to stream videos using a simple call to&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+vlc https://archive.org/download/TheGoat/TheGoat_archive.torrent
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;/p&gt;It can handle magnet links too.  Now if only native vlc had
+bittorrent support.  Then a lot more would be helping each other to
+share public domain and creative commons movies.  The plugin need some
+stability work with seeking and picking the right file in a torrent
+with many files, but is already usable.  Please note that the plugin
+is not removing downloaded files when vlc is stopped, so it can fill
+up your disk if you are not careful.  Have fun. :)&lt;/p&gt;
+
+&lt;p&gt;I would love to get help maintaining this package.  Get in touch if
+you are interested.&lt;/p&gt;
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
@@ -1169,23 +622,28 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
-               <title>A one-way wall on the border?</title>
-               <link>http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html</guid>
-                <pubDate>Sat, 14 Oct 2017 22:10:00 +0200</pubDate>
-               <description>&lt;p&gt;I find it fascinating how many of the people being locked inside
-the proposed border wall between USA and Mexico support the idea.  The
-proposal to keep Mexicans out reminds me of
-&lt;a href=&quot;http://www.history.com/news/10-things-you-may-not-know-about-the-berlin-wall&quot;&gt;the
-propaganda twist from the East Germany government&lt;/a&gt; calling the wall
-the “Antifascist Bulwark” after erecting the Berlin Wall, claiming
-that the wall was erected to keep enemies from creeping into East
-Germany, while it was obvious to the people locked inside it that it
-was erected to keep the people from escaping.&lt;/p&gt;
-
-&lt;p&gt;Do the people in USA supporting this wall really believe it is a
-one way wall, only keeping people on the outside from getting in,
-while not keeping people in the inside from getting out?&lt;/p&gt;
+               <title>Using the Kodi API to play Youtube videos</title>
+               <link>http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
+                <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
+               <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
+tell it to play a youtube URL I received in a chat, without having to
+insert search terms using the on-screen keyboard.  After searching the
+web for API access to the Youtube plugin and testing a bit, I managed
+to find a recipe that worked.  If you got a kodi instance with its API
+available from http://kodihost/jsonrpc, you can try the following to
+have check out a nice cover band.&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
+  --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
+  &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
+  &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
+  http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
+first argument.  It can now handle direct video links, youtube links
+and &#39;desktop&#39; to stream my desktop to Kodi.  It is almost like a
+Chromecast. :)&lt;/p&gt;
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
@@ -1193,5 +651,19 @@ activities, please send Bitcoin donations to my address
 </description>
        </item>
        
+       <item>
+               <title>Software created using taxpayers’ money should be Free Software</title>
+               <link>http://people.skolelinux.org/pere/blog/Software_created_using_taxpayers__money_should_be_Free_Software.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_created_using_taxpayers__money_should_be_Free_Software.html</guid>
+                <pubDate>Thu, 30 Aug 2018 13:50:00 +0200</pubDate>
+               <description>&lt;p&gt;It might seem obvious that software created using tax money should
+be available for everyone to use and improve.  Free Software
+Foundation Europe recentlystarted a campaign to help get more people
+to understand this, and I just signed the petition on
+&lt;a href=&quot;https://publiccode.eu/&quot;&gt;Public Money, Public Code&lt;/a&gt; to help
+them. I hope you too will do the same.&lt;/p&gt;
+</description>
+       </item>
+       
         </channel>
 </rss>