<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
<item>
- <title>Alle Stortingets mobiltelefoner kontrolleres fra USA...</title>
- <link>http://people.skolelinux.org/pere/blog/Alle_Stortingets_mobiltelefoner_kontrolleres_fra_USA___.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Alle_Stortingets_mobiltelefoner_kontrolleres_fra_USA___.html</guid>
- <pubDate>Wed, 7 Oct 2015 09:55:00 +0200</pubDate>
- <description><p>Jeg lot meg fascinere av
-<a href="http://www.aftenposten.no/nyheter/iriks/politikk/Stortinget-har-tilgang-til-a-fjernstyre-600-mobiler-8192692.html">en
-artikkel i Aftenposten</a> der det fortelles at over 600 telefoner som
-benyttes av stortingsrepresentanter, rådgivere og ansatte på
-Stortinget, kan «fjernstyres» ved hjelp av
-<a href="https://play.google.com/store/apps/details?id=com.airwatch.androidagent">programvaren
-Airwatch</a>, et såkalte MDM-program (Mobile Device Managment). Det
-hele bagatelliseres av Stortingets IT-stab, men det er i hovedsak på
-grunn av at journalisten ikke stiller de relevante spørsmålene. For
-meg er det relevante spørsmålet hvem som har lovlig tilgang (i henhold
-til lokal lovgiving, dvs. i hvert fall i Norge, Sverige, UK og USA)
-til informasjon om og på telefonene, og hvor enkelt det er å skaffe
-seg tilgang til hvor mobilene befinner seg og informasjon som befinner
-seg på telefonene ved hjelp av utro tjenere, trusler, innbrudd og
-andre ulovlige metoder.</p>
-
-<p>Bruken av AirWatch betyr i realiteten at USAs etteretning og
-politimyndigheter har full tilgang til stortingets mobiltelefoner,
-inkludert posisjon og innhold, takket være
-<a href="https://en.wikipedia.org/wiki/Foreign_Intelligence_Surveillance_Act_of_1978_Amendments_Act_of_2008">FISAAA-loven</a>
-og
-"<a href="https://en.wikipedia.org/wiki/National_security_letter">National
-Security Letters</a>" og det enkle faktum at AirWatch er kontrollert
-av et selskap i USA. I tillegg er det kjent at kan flere lands
-etterretningstjenester kan lytte på trafikken når den passerer
-landegrensene.</p>
-
-<p>Jeg har bedt om mer informasjon
-<a href="https://www.mimesbronn.no/request/saksnummer_for_saker_anganede_br">fra
-Stortinget om bruken av AirWatch</a> via Mimes brønn så får vi se hva
-de har å fortelle om saken. Fant ingenting om 'airwatch' i
-postjournalen til Stortinget, så jeg trenger hjelp før jeg kan be om
-innsyn i konkrete dokumenter.</p>
+ <title>My own self balancing Lego Segway</title>
+ <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
+ <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
+ <description><p>A while back I received a Gyro sensor for the NXT
+<a href="mindstorms.lego.com">Mindstorms</a> controller as a birthday
+present. It had been on my wishlist for a while, because I wanted to
+build a Segway like balancing lego robot. I had already built
+<a href="http://www.nxtprograms.com/NXT2/segway/">a simple balancing
+robot</a> with the kids, using the light/color sensor included in the
+NXT kit as the balance sensor, but it was not working very well. It
+could balance for a while, but was very sensitive to the light
+condition in the room and the reflective properties of the surface and
+would fall over after a short while. I wanted something more robust,
+and had
+<a href="https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&key=NGY1044">the
+gyro sensor from HiTechnic</a> I believed would solve it on my
+wishlist for some years before it suddenly showed up as a gift from my
+loved ones. :)</p>
+
+<p>Unfortunately I have not had time to sit down and play with it
+since then. But that changed some days ago, when I was searching for
+lego segway information and came across a recipe from HiTechnic for
+building
+<a href="http://www.hitechnic.com/blog/gyro-sensor/htway/">the
+HTWay</a>, a segway like balancing robot. Build instructions and
+<a href="https://www.hitechnic.com/upload/786-HTWayC.nxc">source
+code</a> was included, so it was just a question of putting it all
+together. And thanks to the great work of many Debian developers, the
+compiler needed to build the source for the NXT is already included in
+Debian, so I was read to go in less than an hour. The resulting robot
+do not look very impressive in its simplicity:</p>
+
+<p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-robot.jpeg"></p>
+
+<p>Because I lack the infrared sensor used to control the robot in the
+design from HiTechnic, I had to comment out the last task
+(taskControl). I simply placed /* and */ around it get the program
+working without that sensor present. Now it balances just fine until
+the battery status run low:</p>
+
+<p align="center"><video width="70%" controls="true">
+ <source src="http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-balancing.ogv" type="video/ogg">
+</video></p>
+
+<p>Now we would like to teach it how to follow a line and take remote
+control instructions using the included Bluetooth receiver in the NXT.</p>
+
+<p>If you, like me, love LEGO and want to make sure we find the tools
+they need to work with LEGO in Debian and all our derivative
+distributions like Ubuntu, check out
+<a href="http://wiki.debian.org/LegoDesigners">the LEGO designers
+project page</a> and join the Debian LEGO team. Personally I own a
+RCX and NXT controller (no EV3), and would like to make sure the
+Debian tools needed to program the systems I own work as they
+should.</p>
</description>
</item>
<item>
- <title>French Docbook/PDF/EPUB/MOBI edition of the Free Culture book</title>
- <link>http://people.skolelinux.org/pere/blog/French_Docbook_PDF_EPUB_MOBI_edition_of_the_Free_Culture_book.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/French_Docbook_PDF_EPUB_MOBI_edition_of_the_Free_Culture_book.html</guid>
- <pubDate>Thu, 1 Oct 2015 13:20:00 +0200</pubDate>
- <description><p>As I wrap up the Norwegian version of
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">Free
-Culture</a> book by Lawrence Lessig (still waiting for my final proof
-reading copy to arrive in the mail), my great
-<a href="http://dblatex.sourceforge.net/">dblatex</a> helper and
-developer of the dblatex docbook processor, Benoît Guillon, decided a
-to try to create a French version of the book. He started with the
-French translation available from the
-<a href="http://www.wikilivres.ca/wiki/Culture_libre">Wikilivres wiki
-pages</a>, and wrote a program to convert it into a PO file, allowing
-the translation to be integrated into the po4a based framework I use
-to create the Norwegian translation from the English edition. We meet
-on the <a href="irc://irc.freenode.net/%23dblatex">#dblatex IRC
-channel</a> to discuss the work. If you want to help create a French
-edition, check out
-<a href="https://github.com/marsgui/free-culture-lessig">his git
-repository</a> and join us on IRC. If the French edition look good,
-we might publish it as a paper book on lulu.com. A French version of
-the drawings and the cover need to be provided for this to happen.</p>
+ <title>Aktivitetsbånd som beskytter privatsfæren</title>
+ <link>http://people.skolelinux.org/pere/blog/Aktivitetsb_nd_som_beskytter_privatsf_ren.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Aktivitetsb_nd_som_beskytter_privatsf_ren.html</guid>
+ <pubDate>Thu, 3 Nov 2016 09:55:00 +0100</pubDate>
+ <description><p>Jeg ble så imponert over
+<a href="https://www.nrk.no/norge/forbrukerradet-mener-aktivitetsarmband-strider-mot-norsk-lov-1.13209079">dagens
+gladnyhet på NRK</a>, om at Forbrukerrådet klager inn vilkårene for
+bruk av aktivitetsbånd fra Fitbit, Garmin, Jawbone og Mio til
+Datatilsynet og forbrukerombudet, at jeg sendte følgende brev til
+forbrukerrådet for å uttrykke min støtte:
+
+<blockquote>
+
+<p>Jeg ble veldig glad over å lese at Forbrukerrådet
+<a href="http://www.forbrukerradet.no/siste-nytt/klager-inn-aktivitetsarmband-for-brudd-pa-norsk-lov/">klager
+inn flere aktivitetsbånd til Datatilsynet for dårlige vilkår</a>. Jeg
+har ønsket meg et aktivitetsbånd som kan måle puls, bevegelse og
+gjerne også andre helserelaterte indikatorer en stund nå. De eneste
+jeg har funnet i salg gjør, som dere også har oppdaget, graverende
+inngrep i privatsfæren og sender informasjonen ut av huset til folk og
+organisasjoner jeg ikke ønsker å dele aktivitets- og helseinformasjon
+med. Jeg ønsker et alternativ som <em>ikke</em> sender informasjon til
+skyen, men derimot bruker
+<a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">en
+fritt og åpent standardisert</a> protokoll (eller i det minste en
+dokumentert protokoll uten patent- og opphavsrettslige
+bruksbegrensinger) til å kommunisere med datautstyr jeg kontrollerer.
+Er jo ikke interessert i å betale noen for å tilrøve seg
+personopplysninger fra meg. Desverre har jeg ikke funnet noe
+alternativ så langt.</p>
+
+<p>Det holder ikke å endre på bruksvilkårene for enhetene, slik
+Datatilsynet ofte legger opp til i sin behandling, når de gjør slik
+f.eks. Fitbit (den jeg har sett mest på). Fitbit krypterer
+informasjonen på enheten og sender den kryptert til leverandøren. Det
+gjør det i praksis umulig både å sjekke hva slags informasjon som
+sendes over, og umulig å ta imot informasjonen selv i stedet for
+Fitbit. Uansett hva slags historie som forteller i bruksvilkårene er
+en jo både prisgitt leverandørens godvilje og at de ikke tvinges av
+sitt lands myndigheter til å lyve til sine kunder om hvorvidt
+personopplysninger spres ut over det bruksvilkårene sier. Det er
+veldokumentert hvordan f.eks. USA tvinger selskaper vha. såkalte
+National security letters til å utlevere personopplysninger samtidig
+som de ikke får lov til å fortelle dette til kundene sine.</p>
+
+<p>Stå på, jeg er veldig glade for at dere har sett på saken. Vet
+dere om aktivitetsbånd i salg i dag som ikke tvinger en til å utlevere
+aktivitets- og helseopplysninger med leverandøren?</p>
+
+</blockquote>
+
+<p>Jeg håper en konkurrent som respekterer kundenes privatliv klarer å
+nå opp i markedet, slik at det finnes et reelt alternativ for oss som
+har full tillit til at skyleverandører vil prioritere egen inntjening
+og myndighetspålegg langt foran kundenes rett til privatliv. Jeg har
+ingen tiltro til at Datatilsynet vil kreve noe mer enn at vilkårene
+endres slik at de forklarer eksplisitt i hvor stor grad bruk av
+produktene utraderer privatsfæren til kundene. Det vil nok gjøre de
+innklagede armbåndene «lovlige», men fortsatt tvinge kundene til å
+dele sine personopplysninger med leverandøren.</p>
</description>
</item>
<item>
- <title>The life and death of a laptop battery</title>
- <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
- <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
- <description><p>When I get a new laptop, the battery life time at the start is OK.
-But this do not last. The last few laptops gave me a feeling that
-within a year, the life time is just a fraction of what it used to be,
-and it slowly become painful to use the laptop without power connected
-all the time. Because of this, when I got a new Thinkpad X230 laptop
-about two years ago, I decided to monitor its battery state to have
-more hard facts when the battery started to fail.</p>
-
-<img src="http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png"/>
-
-<p>First I tried to find a sensible Debian package to record the
-battery status, assuming that this must be a problem already handled
-by someone else. I found
-<a href="https://tracker.debian.org/pkg/battery-stats">battery-stats</a>,
-which collects statistics from the battery, but it was completely
-broken. I sent a few suggestions to the maintainer, but decided to
-write my own collector as a shell script while I waited for feedback
-from him. Via
-<a href="http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html">a
-blog post about the battery development on a MacBook Air</a> I also
-discovered
-<a href="https://github.com/jradavenport/batlog.git">batlog</a>, not
-available in Debian.</p>
-
-<p>I started my collector 2013-07-15, and it has been collecting
-battery stats ever since. Now my
-/var/log/hjemmenett-battery-status.log file contain around 115,000
-measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capacity. My
-collector shell script is quite simple and look like this:</p>
+ <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
+ <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
+ <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
+ <description><p>In July
+<a href="http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html">I
+wrote how to get the Signal Chrome/Chromium app working</a> without
+the ability to receive SMS messages (aka without a cell phone). It is
+time to share some experiences and provide an updated setup.</p>
+
+<p>The Signal app have worked fine for several months now, and I use
+it regularly to chat with my loved ones. I had a major snag at the
+end of my summer vacation, when the the app completely forgot my
+setup, identity and keys. The reason behind this major mess was
+running out of disk space. To avoid that ever happening again I have
+started storing everything in <tt>userdata/</tt> in git, to be able to
+roll back to an earlier version if the files are wiped by mistake. I
+had to use it once after introducing the git backup. When rolling
+back to an earlier version, one need to use the 'reset session' option
+in Signal to get going, and notify the people you talk with about the
+problem. I assume there is some sequence number tracking in the
+protocol to detect rollback attacks. The git repository is rather big
+(674 MiB so far), but I have not tried to figure out if some of the
+content can be added to a .gitignore file due to lack of spare
+time.</p>
+
+<p>I've also hit the 90 days timeout blocking, and noticed that this
+make it impossible to send messages using Signal. I could still
+receive them, but had to patch the code with a new timestamp to send.
+I believe the timeout is added by the developers to force people to
+upgrade to the latest version of the app, even when there is no
+protocol changes, to reduce the version skew among the user base and
+thus try to keep the number of support requests down.</p>
+
+<p>Since my original recipe, the Signal source code changed slightly,
+making the old patch fail to apply cleanly. Below is an updated
+patch, including the shell wrapper I use to start Signal. The
+original version required a new user to locate the JavaScript console
+and call a function from there. I got help from a friend with more
+JavaScript knowledge than me to modify the code to provide a GUI
+button instead. This mean that to get started you just need to run
+the wrapper and click the 'Register without mobile phone' to get going
+now. I've also modified the timeout code to always set it to 90 days
+in the future, to avoid having to patch the code regularly.</p>
+
+<p>So, the updated recipe for Debian Jessie:</p>
+
+<ol>
+
+<li>First, install required packages to get the source code and the
+browser you need. Signal only work with Chrome/Chromium, as far as I
+know, so you need to install it.
<pre>
-#!/bin/sh
-# Inspired by
-# http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
-# See also
-# http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
-logfile=/var/log/hjemmenett-battery-status.log
-
-files="manufacturer model_name technology serial_number \
- energy_full energy_full_design energy_now cycle_count status"
-
-if [ ! -e "$logfile" ] ; then
- (
- printf "timestamp,"
- for f in $files; do
- printf "%s," $f
- done
- echo
- ) > "$logfile"
-fi
-
-log_battery() {
- # Print complete message in one echo call, to avoid race condition
- # when several log processes run in parallel.
- msg=$(printf "%s," $(date +%s); \
- for f in $files; do \
- printf "%s," $(cat $f); \
- done)
- echo "$msg"
-}
-
-cd /sys/class/power_supply
-
-for bat in BAT*; do
- (cd $bat && log_battery >> "$logfile")
-done
-</pre>
-
-<p>The script is called when the power management system detect a
-change in the power status (power plug in or out), and when going into
-and out of hibernation and suspend. In addition, it collect a value
-every 10 minutes. This make it possible for me know when the battery
-is discharging, charging and how the maximum charge change over time.
-The code for the Debian package
-<a href="https://github.com/petterreinholdtsen/battery-status">is now
-available on github</a>.</p>
-
-<p>The collected log file look like this:</p>
+apt install git tor chromium
+git clone https://github.com/WhisperSystems/Signal-Desktop.git
+</pre></li>
+
+<li>Modify the source code using command listed in the the patch
+block below.</li>
+
+<li>Start Signal using the run-signal-app wrapper (for example using
+<tt>`pwd`/run-signal-app</tt>).
+
+<li>Click on the 'Register without mobile phone', will in a phone
+number you can receive calls to the next minute, receive the
+verification code and enter it into the form field and press
+'Register'. Note, the phone number you use will be user Signal
+username, ie the way others can find you on Signal.</li>
+
+<li>You can now use Signal to contact others. Note, new contacts do
+not show up in the contact list until you restart Signal, and there is
+no way to assign names to Contacts. There is also no way to create or
+update chat groups. I suspect this is because the web app do not have
+a associated contact database.</li>
+
+</ol>
+
+<p>I am still a bit uneasy about using Signal, because of the way its
+main author moxie0 reject federation and accept dependencies to major
+corporations like Google (part of the code is fetched from Google) and
+Amazon (the central coordination point is owned by Amazon). See for
+example
+<a href="https://github.com/LibreSignal/LibreSignal/issues/37">the
+LibreSignal issue tracker</a> for a thread documenting the authors
+view on these issues. But the network effect is strong in this case,
+and several of the people I want to communicate with already use
+Signal. Perhaps we can all move to <a href="https://ring.cx/">Ring</a>
+once it <a href="https://bugs.debian.org/830265">work on my
+laptop</a>? It already work on Windows and Android, and is included
+in <a href="https://tracker.debian.org/pkg/ring">Debian</a> and
+<a href="https://launchpad.net/ubuntu/+source/ring">Ubuntu</a>, but not
+working on Debian Stable.</p>
+
+<p>Anyway, this is the patch I apply to the Signal code to get it
+working. It switch to the production servers, disable to timeout,
+make registration easier and add the shell wrapper:</p>
<pre>
-timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
-1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
-[...]
-1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
-1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
+cd Signal-Desktop; cat &lt;&lt;EOF | patch -p1
+diff --git a/js/background.js b/js/background.js
+index 24b4c1d..579345f 100644
+--- a/js/background.js
++++ b/js/background.js
+@@ -33,9 +33,9 @@
+ });
+ });
+
+- var SERVER_URL = 'https://textsecure-service-staging.whispersystems.org';
++ var SERVER_URL = 'https://textsecure-service-ca.whispersystems.org';
+ var SERVER_PORTS = [80, 4433, 8443];
+- var ATTACHMENT_SERVER_URL = 'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com';
++ var ATTACHMENT_SERVER_URL = 'https://whispersystems-textsecure-attachments.s3.amazonaws.com';
+ var messageReceiver;
+ window.getSocketStatus = function() {
+ if (messageReceiver) {
+diff --git a/js/expire.js b/js/expire.js
+index 639aeae..beb91c3 100644
+--- a/js/expire.js
++++ b/js/expire.js
+@@ -1,6 +1,6 @@
+ ;(function() {
+ 'use strict';
+- var BUILD_EXPIRATION = 0;
++ var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
+
+ window.extension = window.extension || {};
+
+diff --git a/js/views/install_view.js b/js/views/install_view.js
+index 7816f4f..1d6233b 100644
+--- a/js/views/install_view.js
++++ b/js/views/install_view.js
+@@ -38,7 +38,8 @@
+ return {
+ 'click .step1': this.selectStep.bind(this, 1),
+ 'click .step2': this.selectStep.bind(this, 2),
+- 'click .step3': this.selectStep.bind(this, 3)
++ 'click .step3': this.selectStep.bind(this, 3),
++ 'click .callreg': function() { extension.install('standalone') },
+ };
+ },
+ clearQR: function() {
+diff --git a/options.html b/options.html
+index dc0f28e..8d709f6 100644
+--- a/options.html
++++ b/options.html
+@@ -14,7 +14,10 @@
+ &lt;div class='nav'>
+ &lt;h1>{{ installWelcome }}&lt;/h1>
+ &lt;p>{{ installTagline }}&lt;/p>
+- &lt;div> &lt;a class='button step2'>{{ installGetStartedButton }}&lt;/a> &lt;/div>
++ &lt;div> &lt;a class='button step2'>{{ installGetStartedButton }}&lt;/a>
++ &lt;br> &lt;a class="button callreg">Register without mobile phone&lt;/a>
++
++ &lt;/div>
+ &lt;span class='dot step1 selected'>&lt;/span>
+ &lt;span class='dot step2'>&lt;/span>
+ &lt;span class='dot step3'>&lt;/span>
+--- /dev/null 2016-10-07 09:55:13.730181472 +0200
++++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
+@@ -0,0 +1,12 @@
++#!/bin/sh
++set -e
++cd $(dirname $0)
++mkdir -p userdata
++userdata="`pwd`/userdata"
++if [ -d "$userdata" ] && [ ! -d "$userdata/.git" ] ; then
++ (cd $userdata && git init)
++fi
++(cd $userdata && git add . && git commit -m "Current status." || true)
++exec chromium \
++ --proxy-server="socks://localhost:9050" \
++ --user-data-dir=$userdata --load-and-launch-app=`pwd`
+EOF
+chmod a+rx run-signal-app
</pre>
-<p>I wrote a small script to create a graph of the charge development
-over time. This graph depicted above show the slow death of my laptop
-battery.</p>
-
-<p>But why is this happening? Why are my laptop batteries always
-dying in a year or two, while the batteries of space probes and
-satellites keep working year after year. If we are to believe
-<a href="http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries">Battery
-University</a>, the cause is me charging the battery whenever I have a
-chance, and the fix is to not charge the Lithium-ion batteries to 100%
-all the time, but to stay below 90% of full charge most of the time.
-I've been told that the Tesla electric cars
-<a href="http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit">limit
-the charge of their batteries to 80%</a>, with the option to charge to
-100% when preparing for a longer trip (not that I would want a car
-like Tesla where rights to privacy is abandoned, but that is another
-story), which I guess is the option we should have for laptops on
-Linux too.</p>
-
-<p>Is there a good and generic way with Linux to tell the battery to
-stop charging at 80%, unless requested to charge to 100% once in
-preparation for a longer trip? I found
-<a href="http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity">one
-recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
-80%</a>, but could not get it to work (kernel module refused to
-load).</p>
-
-<p>I wonder why the battery capacity was reported to be more than 100%
-at the start. I also wonder why the "full capacity" increases some
-times, and if it is possible to repeat the process to get the battery
-back to design capacity. And I wonder if the discharge and charge
-speed change over time, or if this stay the same. I did not yet try
-to write a tool to calculate the derivative values of the battery
-level, but suspect some interesting insights might be learned from
-those.</p>
-
-<p>Update 2015-09-24: I got a tip to install the packages
-acpi-call-dkms and tlp (unfortunately missing in Debian stable)
-packages instead of the tp-smapi-dkms package I had tried to use
-initially, and use 'tlp setcharge 40 80' to change when charging start
-and stop. I've done so now, but expect my existing battery is toast
-and need to be replaced. The proposal is unfortunately Thinkpad
-specific.</p>
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</description>
</item>
<item>
- <title>Book cover for the Free Culture book finally done</title>
- <link>http://people.skolelinux.org/pere/blog/Book_cover_for_the_Free_Culture_book_finally_done.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Book_cover_for_the_Free_Culture_book_finally_done.html</guid>
- <pubDate>Thu, 3 Sep 2015 21:00:00 +0200</pubDate>
- <description><p>Creating a good looking book cover proved harder than I expected.
-I wanted to create a cover looking similar to the original cover of
-the
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">Free
-Culture</a> book we are translating to Norwegian, and I wanted it in
-vector format for high resolution printing. But my inkscape knowledge
-were not nearly good enough to pull that off.
-
-<p>But thanks to the great inkscape community, I was able to wrap up
-the cover yesterday evening. I asked on the
-<a href="irc://irc.freenode.net/%23inkscape">#inkscape IRC channel</a>
-on Freenode for help and clues, and Marc Jeanmougin (Mc-) volunteered
-to try to recreate it based on the PDF of the cover from the HTML
-version. Not only did he create a
-<a href="https://marc.jeanmougin.fr/share/copy1.svg ">SVG document with
-the original and his vector version side by side</a>, he even provided
-an <a href="https://marc.jeanmougin.fr/share/out-1.ogv">instruction
-video</a> explaining how he did it</a>. But the instruction video is
-not easy to follow for an untrained inkscape user. The video is a
-recording on how he did it, and he is obviously very experienced as
-the menu selections are very quick and he mentioned on IRC that he did
-use some keyboard shortcuts that can't be seen on the video, but it
-give a good idea about the inkscape operations to use to create the
-stripes with the embossed copyright sign in the center.</p>
-
-<p>I took his SVG file, copied the vector image and re-sized it to fit
-on the cover I was drawing. I am happy with the end result, and the
-current english version look like this:</p>
-
-<img src="http://people.skolelinux.org/pere/blog/images/2015-09-03-free-culture-cover.png" width="70%" align="center"/>
-
-<p>I am not quite sure about the text on the back, but guess it will
-do. I picked three quotes from the official site for the book, and
-hope it will work to trigger the interest of potential readers. The
-Norwegian cover will look the same, but with the texts and bar code
-replaced with the Norwegian version.</p>
-
-<p>The book is very close to being ready for publication, and I expect
-to upload the final draft to Lulu in the next few days and order a
-final proof reading copy to verify that everything look like it should
-before allowing everyone to order their own copy of Free Culture, in
-English or Norwegian Bokmål. I'm waiting to give the the productive
-proof readers a chance to complete their work.</p>
+ <title>NRKs kildevern når NRK-epost deles med utenlands etterretning?</title>
+ <link>http://people.skolelinux.org/pere/blog/NRKs_kildevern_n_r_NRK_epost_deles_med_utenlands_etterretning_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/NRKs_kildevern_n_r_NRK_epost_deles_med_utenlands_etterretning_.html</guid>
+ <pubDate>Sat, 8 Oct 2016 08:15:00 +0200</pubDate>
+ <description><p>NRK
+<a href="https://nrkbeta.no/2016/09/02/securing-whistleblowers/">lanserte
+for noen uker siden</a> en ny
+<a href="https://www.nrk.no/varsle/">varslerportal som bruker
+SecureDrop til å ta imot tips</a> der det er vesentlig at ingen
+utenforstående får vite at NRK er tipset. Det er et langt steg
+fremover for NRK, og når en leser bloggposten om hva de har tenkt på
+og hvordan løsningen er satt opp virker det som om de har gjort en
+grundig jobb der. Men det er ganske mye ekstra jobb å motta tips via
+SecureDrop, så varslersiden skriver "Nyhetstips som ikke krever denne
+typen ekstra vern vil vi gjerne ha på nrk.no/03030", og 03030-siden
+foreslår i tillegg til et webskjema å bruke epost, SMS, telefon,
+personlig oppmøte og brevpost. Denne artikkelen handler disse andre
+metodene.</p>
+
+<p>Når en sender epost til en @nrk.no-adresse så vil eposten sendes ut
+av landet til datamaskiner kontrollert av Microsoft. En kan sjekke
+dette selv ved å slå opp epostleveringsadresse (MX) i DNS. For NRK er
+dette i dag "nrk-no.mail.protection.outlook.com". NRK har som en ser
+valgt å sette bort epostmottaket sitt til de som står bak outlook.com,
+dvs. Microsoft. En kan sjekke hvor nettverkstrafikken tar veien
+gjennom Internett til epostmottaket vha. programmet
+<tt>traceroute</tt>, og finne ut hvem som eier en Internett-adresse
+vha. whois-systemet. Når en gjør dette for epost-trafikk til @nrk.no
+ser en at trafikken fra Norge mot nrk-no.mail.protection.outlook.com
+går via Sverige mot enten Irland eller Tyskland (det varierer fra gang
+til gang og kan endre seg over tid).</p>
+
+<p>Vi vet fra
+<a href="https://no.wikipedia.org/wiki/FRA-loven">introduksjonen av
+FRA-loven</a> at IP-trafikk som passerer grensen til Sverige avlyttes
+av Försvarets radioanstalt (FRA). Vi vet videre takket være
+Snowden-bekreftelsene at trafikk som passerer grensen til
+Storbritannia avlyttes av Government Communications Headquarters
+(GCHQ). I tillegg er er det nettopp lansert et forslag i Norge om at
+forsvarets E-tjeneste skal få avlytte trafikk som krysser grensen til
+Norge. Jeg er ikke kjent med dokumentasjon på at Irland og Tyskland
+gjør det samme. Poenget er uansett at utenlandsk etterretning har
+mulighet til å snappe opp trafikken når en sender epost til @nrk.no.
+I tillegg er det selvsagt tilgjengelig for Microsoft som er underlagt USAs
+jurisdiksjon og
+<a href="https://www.theguardian.com/world/2013/jul/11/microsoft-nsa-collaboration-user-data">samarbeider
+med USAs etterretning på flere områder</a>. De som tipser NRK om
+nyheter via epost kan dermed gå ut fra at det blir kjent for mange
+andre enn NRK at det er gjort.</p>
+
+<p>Bruk av SMS og telefon registreres av blant annet telefonselskapene
+og er tilgjengelig i følge lov og forskrift for blant annet Politi,
+NAV og Finanstilsynet, i tillegg til IT-folkene hos telefonselskapene
+og deres overordnede. Hvis innringer eller mottaker bruker
+smarttelefon vil slik kontakt også gjøres tilgjengelig for ulike
+app-leverandører og de som lytter på trafikken mellom telefon og
+app-leverandør, alt etter hva som er installert på telefonene som
+brukes.</p>
+
+<p>Brevpost kan virke trygt, og jeg vet ikke hvor mye som registreres
+og lagres av postens datastyrte postsorteringssentraler. Det vil ikke
+overraske meg om det lagres hvor i landet hver konvolutt kommer fra og
+hvor den er adressert, i hvert fall for en kortere periode. Jeg vet
+heller ikke hvem slik informasjon gjøres tilgjengelig for. Det kan
+være nok til å ringe inn potensielle kilder når det krysses med hvem
+som kjente til aktuell informasjon og hvor de befant seg (tilgjengelig
+f.eks. hvis de bærer mobiltelefon eller bor i nærheten).</p>
+
+<p>Personlig oppmøte hos en NRK-journalist er antagelig det tryggeste,
+men en bør passe seg for å bruke NRK-kantina. Der bryter de nemlig
+<a href="http://www.lovdata.no/all/hl-19850524-028.html#14">Sentralbanklovens
+paragraf 14</a> og nekter folk å betale med kontanter. I stedet
+krever de at en varsle sin bankkortutsteder om hvor en befinner seg
+ved å bruke bankkort. Banktransaksjoner er tilgjengelig for
+bankkortutsteder (det være seg VISA, Mastercard, Nets og/eller en
+bank) i tillegg til politiet og i hvert fall tidligere med Se & Hør
+(via utro tjenere, slik det ble avslørt etter utgivelsen av boken
+«Livet, det forbannede» av Ken B. Rasmussen). Men hvor mange kjenner
+en NRK-journalist personlig? Besøk på NRK på Marienlyst krever at en
+registrerer sin ankost elektronisk i besøkssystemet. Jeg vet ikke hva
+som skjer med det datasettet, men har grunn til å tro at det sendes ut
+SMS til den en skal besøke med navnet som er oppgitt. Kanskje greit å
+oppgi falskt navn.</p>
+
+<p>Når så tipset er kommet frem til NRK skal det behandles
+redaksjonelt i NRK. Der vet jeg via ulike kilder at de fleste
+journalistene bruker lokalt installert programvare, men noen bruker
+Google Docs og andre skytjenester i strid med interne retningslinjer
+når de skriver. Hvordan vet en hvem det gjelder? Ikke vet jeg, men
+det kan være greit å spørre for å sjekke at journalisten har tenkt på
+problemstillingen, før en gir et tips. Og hvis tipset omtales internt
+på epost, er det jo grunn til å tro at også intern eposten vil deles
+med Microsoft og utenlands etterretning, slik tidligere nevnt, men det
+kan hende at det holdes internt i NRKs interne MS Exchange-løsning.
+Men Microsoft ønsker å få alle Exchange-kunder over "i skyen" (eller
+andre folks datamaskiner, som det jo innebærer), så jeg vet ikke hvor
+lenge det i så fall vil vare.</p>
+
+<p>I tillegg vet en jo at
+<a href="https://www.nrk.no/ytring/elektronisk-kildevern-i-nrk-1.11941196">NRK
+har valgt å gi nasjonal sikkerhetsmyndighet (NSM) tilgang til å se på
+intern og ekstern Internett-trafikk</a> hos NRK ved oppsett av såkalte
+VDI-noder, på tross av
+<a href="https://www.nrk.no/ytring/bekymring-for-nrks-kildevern-1.11941584">protester
+fra NRKs journalistlag</a>. Jeg vet ikke om den vil kunne snappe opp
+dokumenter som lagres på interne filtjenere eller dokumenter som lages
+i de interne webbaserte publiseringssystemene, men vet at hva noden
+ser etter på nettet kontrolleres av NSM og oppdateres automatisk, slik
+at det ikke gir så mye mening å sjekke hva noden ser etter i dag når
+det kan endres automatisk i morgen.</p>
+
+<p>Personlig vet jeg ikke om jeg hadde turt tipse NRK hvis jeg satt på
+noe som kunne være en trussel mot den bestående makten i Norge eller
+verden. Til det virker det å være for mange åpninger for
+utenforstående med andre prioriteter enn NRKs journalistiske fokus.
+Og den største truslen for en varsler er jo om metainformasjon kommer
+på avveie, dvs. informasjon om at en har vært i kontakt med en
+journalist. Det kan være nok til at en kommer i myndighetenes
+søkelys, og de færreste har nok operasjonell sikkerhet til at vil tåle
+slik flombelysning på sitt privatliv.</p>
</description>
</item>
<item>
- <title>In my hand, a pocket book edition of the Norwegian Free Culture book!</title>
- <link>http://people.skolelinux.org/pere/blog/In_my_hand__a_pocket_book_edition_of_the_Norwegian_Free_Culture_book_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/In_my_hand__a_pocket_book_edition_of_the_Norwegian_Free_Culture_book_.html</guid>
- <pubDate>Wed, 19 Aug 2015 22:10:00 +0200</pubDate>
- <description><p>Today, finally, my first printed draft edition of the Norwegian
-translation of Free Culture I have been working on for the last few
-years arrived in the mail. I had to fake a cover to get the interior
-printed, and the exterior of the book look awful, but that is
-irrelevant at this point. I asked for a printed pocket book version
-to get an idea about the font sizes and paper format as well as how
-good the figures and images look in print, but also to test what the
-pocket book version would look like. After receiving the 500 page
-pocket book, it became obvious to me that that pocket book size is too
-small for this book. I believe the book is too thick, and several
-tables and figures do not look good in the size they get with that
-small page sizes. I believe I will go with the 5.5x8.5 inch size
-instead. A surprise discovery from the paper version was how bad the
-URLs look in print. They are very hard to read in the colophon page.
-The URLs are red in the PDF, but light gray on paper. I need to
-change the color of links somehow to look better. But there is a
-printed book in my hand, and it feels great. :)</p>
-
-<p>Now I only need to fix the cover, wrap up the postscript with the
-store behind the book, and collect the last corrections from the proof
-readers before the book is ready for proper printing. Cover artists
-willing to work for free and create a Creative Commons licensed vector
-file looking similar to the original is most welcome, as my skills as
-a graphics designer are mostly missing.</p>
+ <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
+ <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
+ <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
+ <description><p><a href="http://packages.qa.debian.org/isenkram">The Isenkram
+system</a> provide a practical and easy way to figure out which
+packages support the hardware in a given machine. The command line
+tool <tt>isenkram-lookup</tt> and the tasksel options provide a
+convenient way to list and install packages relevant for the current
+hardware during system installation, both user space packages and
+firmware packages. The GUI background daemon on the other hand provide
+a pop-up proposing to install packages when a new dongle is inserted
+while using the computer. For example, if you plug in a smart card
+reader, the system will ask if you want to install <tt>pcscd</tt> if
+that package isn't already installed, and if you plug in a USB video
+camera the system will ask if you want to install <tt>cheese</tt> if
+cheese is currently missing. This already work just fine.</p>
+
+<p>But Isenkram depend on a database mapping from hardware IDs to
+package names. When I started no such database existed in Debian, so
+I made my own data set and included it with the isenkram package and
+made isenkram fetch the latest version of this database from git using
+http. This way the isenkram users would get updated package proposals
+as soon as I learned more about hardware related packages.</p>
+
+<p>The hardware is identified using modalias strings. The modalias
+design is from the Linux kernel where most hardware descriptors are
+made available as a strings that can be matched using filename style
+globbing. It handle USB, PCI, DMI and a lot of other hardware related
+identifiers.</p>
+
+<p>The downside to the Isenkram specific database is that there is no
+information about relevant distribution / Debian version, making
+isenkram propose obsolete packages too. But along came AppStream, a
+cross distribution mechanism to store and collect metadata about
+software packages. When I heard about the proposal, I contacted the
+people involved and suggested to add a hardware matching rule using
+modalias strings in the specification, to be able to use AppStream for
+mapping hardware to packages. This idea was accepted and AppStream is
+now a great way for a package to announce the hardware it support in a
+distribution neutral way. I wrote
+<a href="http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html">a
+recipe on how to add such meta-information</a> in a blog post last
+December. If you have a hardware related package in Debian, please
+announce the relevant hardware IDs using AppStream.</p>
+
+<p>In Debian, almost all packages that can talk to a LEGO Mindestorms
+RCX or NXT unit, announce this support using AppStream. The effect is
+that when you insert such LEGO robot controller into your Debian
+machine, Isenkram will propose to install the packages needed to get
+it working. The intention is that this should allow the local user to
+start programming his robot controller right away without having to
+guess what packages to use or which permissions to fix.</p>
+
+<p>But when I sat down with my son the other day to program our NXT
+unit using his Debian Stretch computer, I discovered something
+annoying. The local console user (ie my son) did not get access to
+the USB device for programming the unit. This used to work, but no
+longer in Jessie and Stretch. After some investigation and asking
+around on #debian-devel, I discovered that this was because udev had
+changed the mechanism used to grant access to local devices. The
+ConsoleKit mechanism from <tt>/lib/udev/rules.d/70-udev-acl.rules</tt>
+no longer applied, because LDAP users no longer was added to the
+plugdev group during login. Michael Biebl told me that this method
+was obsolete and the new method used ACLs instead. This was good
+news, as the plugdev mechanism is a mess when using a remote user
+directory like LDAP. Using ACLs would make sure a user lost device
+access when she logged out, even if the user left behind a background
+process which would retain the plugdev membership with the ConsoleKit
+setup. Armed with this knowledge I moved on to fix the access problem
+for the LEGO Mindstorms related packages.</p>
+
+<p>The new system uses a udev tag, 'uaccess'. It can either be
+applied directly for a device, or is applied in
+/lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
+LEGO Mindstorms udev rules did not have a class, I decided to add the
+tag directly in the udev rules files included in the packages. Here
+is one example. For the nqc C compiler for the RCX, the
+<tt>/lib/udev/rules.d/60-nqc.rules</tt> file now look like this:
+
+<p><pre>
+SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694", ATTR{idProduct}=="0001", \
+ SYMLINK+="rcx-%k", TAG+="uaccess"
+</pre></p>
+
+<p>The key part is the 'TAG+="uaccess"' at the end. I suspect all
+packages using plugdev in their /lib/udev/rules.d/ files should be
+changed to use this tag (either directly or indirectly via
+<tt>70-uaccess.rules</tt>). Perhaps a lintian check should be created
+to detect this?</p>
+
+<p>I've been unable to find good documentation on the uaccess feature.
+It is unclear to me if the uaccess tag is an internal implementation
+detail like the udev-acl tag used by
+<tt>/lib/udev/rules.d/70-udev-acl.rules</tt>. If it is, I guess the
+indirect method is the preferred way. Michael
+<a href="https://github.com/systemd/systemd/issues/4288">asked for more
+documentation from the systemd project</a> and I hope it will make
+this clearer. For now I use the generic classes when they exist and
+is already handled by <tt>70-uaccess.rules</tt>, and add the tag
+directly if no such class exist.</p>
+
+<p>To learn more about the isenkram system, please check out
+<a href="http://people.skolelinux.org/pere/blog/tags/isenkram/">my
+blog posts tagged isenkram</a>.</p>
+
+<p>To help out making life for LEGO constructors in Debian easier,
+please join us on our IRC channel
+<a href="irc://irc.debian.org/%23debian-lego">#debian-lego</a> and join
+the <a href="https://alioth.debian.org/projects/debian-lego/">Debian
+LEGO team</a> in the Alioth project we created yesterday. A mailing
+list is not yet created, but we are working on it. :)</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</description>
</item>
<item>
- <title>First paper version of the Norwegian Free Culture book heading my way</title>
- <link>http://people.skolelinux.org/pere/blog/First_paper_version_of_the_Norwegian_Free_Culture_book_heading_my_way.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_paper_version_of_the_Norwegian_Free_Culture_book_heading_my_way.html</guid>
- <pubDate>Sun, 9 Aug 2015 10:15:00 +0200</pubDate>
- <description><p>Typesetting a book is harder than I hoped. As the translation is
-mostly done, and a volunteer proof reader was going to check the text
-on paper, it was time this summer to focus on formatting my translated
-<a href="http://www.docbook.org/">docbook</a> based version of the
-<a href="http://free-culture.cc/">Free Culture</a> book by Lawrence
-Lessig. I've been trying to get both docboox-xsl+fop and dblatex to
-give me a good looking PDF, but in the end I went with dblatex, because
-its Debian maintainer and upstream developer were responsive and very
-helpful in solving my formatting challenges.</p>
-
-<p>Last night, I finally managed to create a PDF that no longer made
-<a href="http://www.lulu.com/">Lulu.com</a> complain after uploading,
-and I ordered a text version of the book on paper. It is lacking a
-proper book cover and is not tagged with the correct ISBN number, but
-should give me an idea what the finished book will look like.</p>
-
-<p>Instead of using Lulu, I did consider printing the book using
-<a href="http://www.createspace.com/">CreateSpace</a>, but ended up
-using Lulu because it had smaller book size options (CreateSpace seem
-to lack pocket book with extended distribution). I looked for a
-similar service in Norway, but have not seen anything so far. Please
-let me know if I am missing out on something here.</p>
-
-<p>But I still struggle to decide the book size. Should I go for
-pocket book (4.25x6.875 inches / 10.8x17.5 cm) with 556 pages, Digest
-(5.5x8.5 inches / 14x21.6 cm) with 323 pages or US Trade (6x8 inches /
-15.3x22.9 cm) with 280 pages? Fewer pager give a cheaper book, and a
-smaller book is easier to carry around. The test book I ordered was
-pocket book sized, to give me an idea how well that fit in my hand,
-but I suspect I will end up using a digest sized book in the end to
-bring the prize down further.</p>
-
-<p>My biggest challenge at the moment is making nice cover art. My
-inkscape skills are not yet up to the task of replicating the original
-cover in SVG format. I also need to figure out what to write about
-the book on the back (will most likely use the same text as the
-description on web based book stores). I would love help with this,
-if you are willing to license the art source and final version using
-the same CC license as the book. My artistic skills are not really up
-to the task.</p>
-
-<p>I plan to publish the book in both English and Norwegian and on
-paper, in PDF form as well as EPUB and MOBI format. The current
-status can as usual be found on
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>
-in the archive/ directory. So far I have spent all time on making the
-PDF version look good. Someone should probably do the same with the
-dbtoepub generated e-book. Help is definitely needed here, as I
-expect to run out of steem before I find time to improve the epub
-formatting.</p>
-
-<p>Please let me know via github if you find typos in the book or
-discover translations that should be improved. The final proof
-reading is being done right now, and I expect to publish the finished
-result in a few months.</p>
+ <title>Aftenposten-redaktøren med lua i hånda</title>
+ <link>http://people.skolelinux.org/pere/blog/Aftenposten_redakt_ren_med_lua_i_h_nda.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Aftenposten_redakt_ren_med_lua_i_h_nda.html</guid>
+ <pubDate>Fri, 9 Sep 2016 11:30:00 +0200</pubDate>
+ <description><p>En av dagens nyheter er at Aftenpostens redaktør Espen Egil Hansen
+bruker
+<a href="https://www.nrk.no/kultur/aftenposten-brukar-heile-forsida-pa-facebook-kritikk-1.13126918">forsiden
+av papiravisen på et åpent brev til Facebooks sjef Mark Zuckerberg om
+Facebooks fjerning av bilder, tekster og sider de ikke liker</a>. Det
+må være uvant for redaktøren i avisen Aftenposten å stå med lua i
+handa og håpe på å bli hørt. Spesielt siden Aftenposten har vært med
+på å gi Facebook makten de nå demonstrerer at de har. Ved å melde seg
+inn i Facebook-samfunnet har de sagt ja til bruksvilkårene og inngått
+en antagelig bindende avtale. Kanskje de skulle lest og vurdert
+vilkårene litt nærmere før de sa ja, i stedet for å klage over at
+reglende de har valgt å akseptere blir fulgt? Personlig synes jeg
+vilkårene er uakseptable og det ville ikke falle meg inn å gå inn på
+en avtale med slike vilkår. I tillegg til uakseptable vilkår er det
+mange andre grunner til å unngå Facebook. Du kan finne en solid
+gjennomgang av flere slike argumenter hos
+<a href="https://stallman.org/facebook.html">Richard Stallmans side om
+Facebook</a>.
+
+<p>Jeg håper flere norske redaktører på samme vis må stå med lua i
+hånden inntil de forstår at de selv er med på å føre samfunnet på
+ville veier ved å omfavne Facebook slik de gjør når de omtaler og
+løfter frem saker fra Facebook, og tar i bruk Facebook som
+distribusjonskanal for sine nyheter. De bidrar til
+overvåkningssamfunnet og raderer ut lesernes privatsfære når de lenker
+til Facebook på sine sider, og låser seg selv inne i en omgivelse der
+det er Facebook, og ikke redaktøren, som sitter med makta.</p>
+
+<p>Men det vil nok ta tid, i et Norge der de fleste nettredaktører
+<a href="http://people.skolelinux.org/pere/blog/Snurpenot_overv_kning_av_sensitiv_personinformasjon.html">deler
+sine leseres personopplysinger med utenlands etterretning</a>.</p>
+
+<p>For øvrig burde varsleren Edward Snowden få politisk asyl i
+Norge.</p>
</description>
</item>
<item>
- <title>Typesetting DocBook footnotes as endnotes with dblatex</title>
- <link>http://people.skolelinux.org/pere/blog/Typesetting_DocBook_footnotes_as_endnotes_with_dblatex.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Typesetting_DocBook_footnotes_as_endnotes_with_dblatex.html</guid>
- <pubDate>Thu, 16 Jul 2015 18:10:00 +0200</pubDate>
- <description><p>I'm still working on the Norwegian version of the
-<a href="http://free-culture.cc/">Free Culture book by Lawrence
-Lessig</a>, and is now working on the final typesetting and layout.
-One of the features I want to get the structure similar to the
-original book is to typeset the footnotes as endnotes in the notes
-chapter. Based on the
-<a href="https://bugs.debian.org/685063">feedback from the Debian
-maintainer and the dblatex developer</a>, I came up with this recipe I
-would like to share with you. The proposal was to create a new LaTeX
-class file and add the LaTeX code there, but this is not always
-practical, when I want to be able to replace the class using a make
-file variable. So my proposal misuses the latex.begindocument XSL
-parameter value, to get a small fragment into the correct location in
-the generated LaTeX File.</p>
-
-<p>First, decide where in the DocBook document to place the endnotes,
-and add this text there:</p>
-
-<pre>
-&lt;?latex \theendnotes ?&gt;
-</pre>
-
-<p>Next, create a xsl stylesheet file dblatex-endnotes.xsl to add the
-code needed to add the endnote instructions in the preamble of the
-generated LaTeX document, with content like this:</p>
-
-<pre>
-&lt;?xml version='1.0'?&gt;
-&lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'&gt;
- &lt;xsl:param name="latex.begindocument"&gt;
- &lt;xsl:text&gt;
-\usepackage{endnotes}
-\let\footnote=\endnote
-\def\enoteheading{\mbox{}\par\vskip-\baselineskip }
-\begin{document}
- &lt;/xsl:text&gt;
- &lt;/xsl:param&gt;
-&lt;/xsl:stylesheet&gt;
-</pre>
-
-<p>Finally, load this xsl file when running dblatex, for example like
-this:</p>
-
-<pre>
-dblatex --xsl-user=dblatex-endnotes.xsl freeculture.nb.xml
-</pre>
-
-<p>The end result can be seen on github, where
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">my
-book project</a> is located.</p>
+ <title>E-tjenesten ber om innsyn i eposten til partiene på Stortinget</title>
+ <link>http://people.skolelinux.org/pere/blog/E_tjenesten_ber_om_innsyn_i_eposten_til_partiene_p__Stortinget.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/E_tjenesten_ber_om_innsyn_i_eposten_til_partiene_p__Stortinget.html</guid>
+ <pubDate>Tue, 6 Sep 2016 23:00:00 +0200</pubDate>
+ <description><p>I helga kom det et hårreisende forslag fra Lysne II-utvalget satt
+ned av Forsvarsdepartementet. Lysne II-utvalget var bedt om å vurdere
+ønskelista til Forsvarets etterretningstjeneste (e-tjenesten), og har
+kommet med
+<a href="http://www.aftenposten.no/norge/Utvalg-sier-ja-til-at-E-tjenesten-far-overvake-innholdet-i-all-internett--og-telefontrafikk-som-krysser-riksgrensen-603232b.html">forslag
+om at e-tjenesten skal få lov til a avlytte all Internett-trafikk</a>
+som passerer Norges grenser. Få er klar over at dette innebærer at
+e-tjenesten får tilgang til epost sendt til de fleste politiske
+partiene på Stortinget. Regjeringspartiet Høyre (@hoyre.no),
+støttepartiene Venstre (@venstre.no) og Kristelig Folkeparti (@krf.no)
+samt Sosialistisk Ventreparti (@sv.no) og Miljøpartiet de grønne
+(@mdg.no) har nemlig alle valgt å ta imot eposten sin via utenlandske
+tjenester. Det betyr at hvis noen sender epost til noen med en slik
+adresse vil innholdet i eposten, om dette forslaget blir vedtatt, gjøres
+tilgjengelig for e-tjenesten. Venstre, Sosialistisk Ventreparti og
+Miljøpartiet De Grønne har valgt å motta sin epost hos Google,
+Kristelig Folkeparti har valgt å motta sin epost hos Microsoft, og
+Høyre har valgt å motta sin epost hos Comendo med mottak i Danmark og
+Irland. Kun Arbeiderpartiet og Fremskrittspartiet har valgt å motta
+eposten sin i Norge, hos henholdsvis Intility AS og Telecomputing
+AS.</p>
+
+<p>Konsekvensen er at epost inn og ut av de politiske organisasjonene,
+til og fra partimedlemmer og partiets tillitsvalgte vil gjøres
+tilgjengelig for e-tjenesten for analyse og sortering. Jeg mistenker
+at kunnskapen som slik blir tilgjengelig vil være nyttig hvis en
+ønsker å vite hvilke argumenter som treffer publikum når en ønsker å
+påvirke Stortingets representanter.</p
+
+<p>Ved hjelp av MX-oppslag i DNS for epost-domene, tilhørende
+whois-oppslag av IP-adressene og traceroute for å se hvorvidt
+trafikken går via utlandet kan enhver få bekreftet at epost sendt til
+de omtalte partiene vil gjøres tilgjengelig for forsvarets
+etterretningstjeneste hvis forslaget blir vedtatt. En kan også bruke
+den kjekke nett-tjenesten <a href="http://ipinfo.io/">ipinfo.io</a>
+for å få en ide om hvor i verden en IP-adresse hører til.</p>
+
+<p>På den positive siden vil forslaget gjøre at enda flere blir
+motivert til å ta grep for å bruke
+<a href="https://www.torproject.org/">Tor</a> og krypterte
+kommunikasjonsløsninger for å kommunisere med sine kjære, for å sikre
+at privatsfæren vernes. Selv bruker jeg blant annet
+<a href="https://www.freedomboxfoundation.org/">FreedomBox</a> og
+<a href="https://whispersystems.org/">Signal</a> til slikt. Ingen av
+dem er optimale, men de fungerer ganske bra allerede og øker kostnaden
+for dem som ønsker å invadere mitt privatliv.</p>
+
+<p>For øvrig burde varsleren Edward Snowden få politisk asyl i
+Norge.</p>
+
+<!--
+
+venstre.no
+ venstre.no mail is handled by 10 aspmx.l.google.com.
+ venstre.no mail is handled by 20 alt1.aspmx.l.google.com.
+ venstre.no mail is handled by 20 alt2.aspmx.l.google.com.
+ venstre.no mail is handled by 30 aspmx2.googlemail.com.
+ venstre.no mail is handled by 30 aspmx3.googlemail.com.
+
+traceroute to aspmx.l.google.com (173.194.222.27), 30 hops max, 60 byte packets
+ 1 uio-gw10.uio.no (129.240.6.1) 0.411 ms 0.438 ms 0.536 ms
+ 2 uio-gw8.uio.no (129.240.24.229) 0.375 ms 0.452 ms 0.548 ms
+ 3 oslo-gw1.uninett.no (128.39.65.17) 1.940 ms 1.950 ms 1.942 ms
+ 4 se-tug.nordu.net (109.105.102.108) 6.910 ms 6.949 ms 7.283 ms
+ 5 google-gw.nordu.net (109.105.98.6) 6.975 ms 6.967 ms 6.958 ms
+ 6 209.85.250.192 (209.85.250.192) 7.337 ms 7.286 ms 10.890 ms
+ 7 209.85.254.13 (209.85.254.13) 7.394 ms 209.85.254.31 (209.85.254.31) 7.586 ms 209.85.254.33 (209.85.254.33) 7.570 ms
+ 8 209.85.251.255 (209.85.251.255) 15.686 ms 209.85.249.229 (209.85.249.229) 16.118 ms 209.85.251.255 (209.85.251.255) 16.073 ms
+ 9 74.125.37.255 (74.125.37.255) 16.794 ms 216.239.40.248 (216.239.40.248) 16.113 ms 74.125.37.44 (74.125.37.44) 16.764 ms
+10 * * *
+
+mdg.no
+ mdg.no mail is handled by 1 aspmx.l.google.com.
+ mdg.no mail is handled by 5 alt2.aspmx.l.google.com.
+ mdg.no mail is handled by 5 alt1.aspmx.l.google.com.
+ mdg.no mail is handled by 10 aspmx2.googlemail.com.
+ mdg.no mail is handled by 10 aspmx3.googlemail.com.
+sv.no
+ sv.no mail is handled by 1 aspmx.l.google.com.
+ sv.no mail is handled by 5 alt1.aspmx.l.google.com.
+ sv.no mail is handled by 5 alt2.aspmx.l.google.com.
+ sv.no mail is handled by 10 aspmx3.googlemail.com.
+ sv.no mail is handled by 10 aspmx2.googlemail.com.
+hoyre.no
+ hoyre.no mail is handled by 10 hoyre-no.mx1.comendosystems.com.
+ hoyre.no mail is handled by 20 hoyre-no.mx2.comendosystems.net.
+
+traceroute to hoyre-no.mx1.comendosystems.com (89.104.206.4), 30 hops max, 60 byte packets
+ 1 uio-gw10.uio.no (129.240.6.1) 0.450 ms 0.510 ms 0.591 ms
+ 2 uio-gw8.uio.no (129.240.24.229) 0.383 ms 0.508 ms 0.596 ms
+ 3 oslo-gw1.uninett.no (128.39.65.17) 0.311 ms 0.315 ms 0.300 ms
+ 4 se-tug.nordu.net (109.105.102.108) 6.837 ms 6.842 ms 6.834 ms
+ 5 dk-uni.nordu.net (109.105.97.10) 26.073 ms 26.085 ms 26.076 ms
+ 6 dix.1000m.soeborg.ip.comendo.dk (192.38.7.22) 15.372 ms 15.046 ms 15.123 ms
+ 7 89.104.192.65 (89.104.192.65) 15.875 ms 15.990 ms 16.239 ms
+ 8 89.104.192.179 (89.104.192.179) 15.676 ms 15.674 ms 15.664 ms
+ 9 03dm-com.mx1.staysecuregroup.com (89.104.206.4) 15.637 ms * *
+
+krf.no
+ krf.no mail is handled by 10 krf-no.mail.protection.outlook.com.
+
+traceroute to krf-no.mail.protection.outlook.com (213.199.154.42), 30 hops max, 60 byte packets
+ 1 uio-gw10.uio.no (129.240.6.1) 0.401 ms 0.438 ms 0.536 ms
+ 2 uio-gw8.uio.no (129.240.24.229) 11.076 ms 11.120 ms 11.204 ms
+ 3 oslo-gw1.uninett.no (128.39.65.17) 0.232 ms 0.234 ms 0.271 ms
+ 4 se-tug.nordu.net (109.105.102.108) 6.811 ms 6.820 ms 6.815 ms
+ 5 netnod-ix-ge-a-sth-4470.microsoft.com (195.245.240.181) 7.074 ms 7.013 ms 7.061 ms
+ 6 ae1-0.sto-96cbe-1b.ntwk.msn.net (104.44.225.161) 7.227 ms 7.362 ms 7.293 ms
+ 7 be-8-0.ibr01.ams.ntwk.msn.net (104.44.5.7) 41.993 ms 43.334 ms 41.939 ms
+ 8 be-1-0.ibr02.ams.ntwk.msn.net (104.44.4.214) 43.153 ms 43.507 ms 43.404 ms
+ 9 ae3-0.fra-96cbe-1b.ntwk.msn.net (104.44.5.17) 29.897 ms 29.831 ms 29.794 ms
+10 ae10-0.vie-96cbe-1a.ntwk.msn.net (198.206.164.1) 42.309 ms 42.130 ms 41.808 ms
+11 * ae8-0.vie-96cbe-1b.ntwk.msn.net (104.44.227.29) 41.425 ms *
+12 * * *
+
+arbeiderpartiet.no
+ arbeiderpartiet.no mail is handled by 10 mail.intility.com.
+ arbeiderpartiet.no mail is handled by 20 mail2.intility.com.
+
+traceroute to mail.intility.com (188.95.245.87), 30 hops max, 60 byte packets
+ 1 uio-gw10.uio.no (129.240.6.1) 0.486 ms 0.508 ms 0.649 ms
+ 2 uio-gw8.uio.no (129.240.24.229) 0.416 ms 0.508 ms 0.620 ms
+ 3 oslo-gw1.uninett.no (128.39.65.17) 0.276 ms 0.278 ms 0.275 ms
+ 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 0.374 ms 0.371 ms 0.416 ms
+ 5 he16-1-1.cr1.san110.as2116.net (195.0.244.234) 3.132 ms he16-1-1.cr2.oslosda310.as2116.net (195.0.244.48) 10.079 ms he16-1-1.cr1.san110.as2116.net (195.0.244.234) 3.353 ms
+ 6 te1-2-0.ar2.ulv89.as2116.net (195.0.243.194) 0.569 ms te5-0-0.ar2.ulv89.as2116.net (195.0.243.192) 0.661 ms 0.653 ms
+ 7 cD2EC45C1.static.as2116.net (193.69.236.210) 0.654 ms 0.615 ms 0.590 ms
+ 8 185.7.132.38 (185.7.132.38) 1.661 ms 1.808 ms 1.695 ms
+ 9 185.7.132.100 (185.7.132.100) 1.793 ms 1.943 ms 1.546 ms
+10 * * *
+
+frp.no
+ frp.no mail is handled by 10 mx03.telecomputing.no.
+ frp.no mail is handled by 20 mx01.telecomputing.no.
+
+traceroute to mx03.telecomputing.no (95.128.105.102), 30 hops max, 60 byte packets
+ 1 uio-gw10.uio.no (129.240.6.1) 0.378 ms 0.402 ms 0.479 ms
+ 2 uio-gw8.uio.no (129.240.24.229) 0.361 ms 0.458 ms 0.548 ms
+ 3 oslo-gw1.uninett.no (128.39.65.17) 0.361 ms 0.352 ms 0.336 ms
+ 4 xe-2-2-0-0.san-peer2.osl.no.ip.tdc.net (193.156.90.16) 0.375 ms 0.366 ms 0.346 ms
+ 5 xe-2-0-2-0.ost-pe1.osl.no.ip.tdc.net (85.19.121.97) 0.780 ms xe-2-0-0-0.ost-pe1.osl.no.ip.tdc.net (85.19.121.101) 0.713 ms xe-2-0-2-0.ost-pe1.osl.no.ip.tdc.net (85.19.121.97) 0.759 ms
+ 6 cpe.xe-0-2-0-100.ost-pe1.osl.no.customer.tdc.net (85.19.26.46) 0.837 ms 0.755 ms 0.759 ms
+ 7 95.128.105.3 (95.128.105.3) 1.050 ms 1.288 ms 1.182 ms
+ 8 mx03.telecomputing.no (95.128.105.102) 0.717 ms 0.703 ms 0.692 ms
+
+-->
</description>
</item>
<item>
- <title>Mimes brønn, norsk utgave av Alaveteli / WhatDoTheyKnow, endelig lansert</title>
- <link>http://people.skolelinux.org/pere/blog/Mimes_br_nn__norsk_utgave_av_Alaveteli___WhatDoTheyKnow__endelig_lansert.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Mimes_br_nn__norsk_utgave_av_Alaveteli___WhatDoTheyKnow__endelig_lansert.html</guid>
- <pubDate>Thu, 9 Jul 2015 11:40:00 +0200</pubDate>
- <description><p>I går fikk vi endelig lansert en norsk version av mySocietys
-<a href="https://www.whatdotheyknow.com/">WhatDoTheyKnow</a>.
-Tjenesten heter Mimes brønn, og ble
-<a href="http://www.nuug.no/news/NUUG_lanserer_innsynstjenesten_Mimes_Br_nn.shtml">annonsert
-av NUUG</a> via blogg, epost og twitter til NUUG-assosierte personer.
-Det har tatt noen år, men de siste dagene fikk vi endelig tid til å få
-på plass de siste bitene. Vi er to, Gorm og meg selv, som har vært
-primus motor for det hele, men vi har fått hjelp med oversettelser og
-oppsett fra mange flere. Jeg vil si tusen takk til hver og en av dem,
-og er veldig fornøyd med at vi klarte å få tjenesten opp å kjøre før
-ferietiden slo inn for fullt.</p>
-
-<p>Vi er usikker på hvor mye belastning den virtuelle maskinen der
-tjenesten kjører klarer, så vi har lansert litt i det stille og ikke
-til for mange folk for å se hvordan maskinen klarer seg over sommeren,
-før vi går mer aktivt ut og annonserer til høsten. Ta en titt, og se
-om du kanskje har et spørsmål til det offentlige som er egnet å sende
-inn via Mimes brønn.</p>
-
-<p>Hvis du lurer på hva i alle dager en slik tjenestes kan brukes til,
-anbefaler jeg deg å se
-<a href="http://beta.frikanalen.no/video/625321">TED-foredraget til
-Heather Brook</a> om hvordan hun brukte WhatDoTheyKnow til å lære
-hvordan offentlige midler ble misbrukt. Det er en inspirerende
-historie.</p>
+ <title>First draft Norwegian Bokmål edition of The Debian Administrator's Handbook now public</title>
+ <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</guid>
+ <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
+ <description><p>In April we
+<a href="http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html">started
+to work</a> on a Norwegian Bokmål edition of the "open access" book on
+how to set up and administrate a Debian system. Today I am happy to
+report that the first draft is now publicly available. You can find
+it on <a href="https://debian-handbook.info/get/">get the Debian
+Administrator's Handbook page</a> (under Other languages). The first
+eight chapters have a first draft translation, and we are working on
+proofreading the content. If you want to help out, please start
+contributing using
+<a href="https://hosted.weblate.org/projects/debian-handbook/">the
+hosted weblate project page</a>, and get in touch using
+<a href="http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators">the
+translators mailing list</a>. Please also check out
+<a href="https://debian-handbook.info/contribute/">the instructions for
+contributors</a>. A good way to contribute is to proofread the text
+and update weblate if you find errors.</p>
+
+<p>Our goal is still to make the Norwegian book available on paper as well as
+electronic form.</p>
</description>
</item>
<item>
- <title>MPEG LA on "Internet Broadcast AVC Video" licensing and non-private use</title>
- <link>http://people.skolelinux.org/pere/blog/MPEG_LA_on__Internet_Broadcast_AVC_Video__licensing_and_non_private_use.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/MPEG_LA_on__Internet_Broadcast_AVC_Video__licensing_and_non_private_use.html</guid>
- <pubDate>Tue, 7 Jul 2015 09:50:00 +0200</pubDate>
- <description><p>After asking the Norwegian Broadcasting Company (NRK)
-<a href="http://people.skolelinux.org/pere/blog/Hva_gj_r_at_NRK_kan_distribuere_H_264_video_uten_patentavtale_med_MPEG_LA_.html">why
-they can broadcast and stream H.264 video without an agreement with
-the MPEG LA</a>, I was wiser, but still confused. So I asked MPEG LA
-if their understanding matched that of NRK. As far as I can tell, it
-does not.</p>
-
-<p>I started by asking for more information about the various
-licensing classes and what exactly is covered by the "Internet
-Broadcast AVC Video" class that NRK pointed me at to explain why NRK
-did not need a license for streaming H.264 video:
-
-<p><blockquote>
-
-<p>According to
-<a href="http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf">a
-MPEG LA press release dated 2010-02-02</a>, there is no charge when
-using MPEG AVC/H.264 according to the terms of "Internet Broadcast AVC
-Video". I am trying to understand exactly what the terms of "Internet
-Broadcast AVC Video" is, and wondered if you could help me. What
-exactly is covered by these terms, and what is not?</p>
-
-<p>The only source of more information I have been able to find is a
-PDF named
-<a href="http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf">AVC
-Patent Portfolio License Briefing</a>, which states this about the
-fees:</p>
-
-<ul>
- <li>Where End User pays for AVC Video
- <ul>
- <li>Subscription (not limited by title) – 100,000 or fewer
- subscribers/yr = no royalty; &gt; 100,000 to 250,000 subscribers/yr =
- $25,000; &gt;250,000 to 500,000 subscribers/yr = $50,000; &gt;500,000 to
- 1M subscribers/yr = $75,000; &gt;1M subscribers/yr = $100,000</li>
-
- <li>Title-by-Title - 12 minutes or less = no royalty; &gt;12 minutes in
- length = lower of (a) 2% or (b) $0.02 per title</li>
- </ul></li>
-
- <li>Where remuneration is from other sources
- <ul>
- <li>Free Television - (a) one-time $2,500 per transmission encoder or
- (b) annual fee starting at $2,500 for &gt; 100,000 HH rising to
- maximum $10,000 for &gt;1,000,000 HH</li>
-
- <li>Internet Broadcast AVC Video (not title-by-title, not subscription)
- – no royalty for life of the AVC Patent Portfolio License</li>
- </ul></li>
-</ul>
-
-<p>Am I correct in assuming that the four categories listed is the
-categories used when selecting licensing terms, and that "Internet
-Broadcast AVC Video" is the category for things that do not fall into
-one of the other three categories? Can you point me to a good source
-explaining what is ment by "title-by-title" and "Free Television" in
-the license terms for AVC/H.264?</p>
-
-<p>Will a web service providing H.264 encoded video content in a
-"video on demand" fashing similar to Youtube and Vimeo, where no
-subscription is required and no payment is required from end users to
-get access to the videos, fall under the terms of the "Internet
-Broadcast AVC Video", ie no royalty for life of the AVC Patent
-Portfolio license? Does it matter if some users are subscribed to get
-access to personalized services?</p>
-
-<p>Note, this request and all answers will be published on the
-Internet.</p>
-</blockquote></p>
-
-<p>The answer came quickly from Benjamin J. Myers, Licensing Associate
-with the MPEG LA:</p>
-
-<p><blockquote>
-<p>Thank you for your message and for your interest in MPEG LA. We
-appreciate hearing from you and I will be happy to assist you.</p>
-
-<p>As you are aware, MPEG LA offers our AVC Patent Portfolio License
-which provides coverage under patents that are essential for use of
-the AVC/H.264 Standard (MPEG-4 Part 10). Specifically, coverage is
-provided for end products and video content that make use of AVC/H.264
-technology. Accordingly, the party offering such end products and
-video to End Users concludes the AVC License and is responsible for
-paying the applicable royalties.</p>
-
-<p>Regarding Internet Broadcast AVC Video, the AVC License generally
-defines such content to be video that is distributed to End Users over
-the Internet free-of-charge. Therefore, if a party offers a service
-which allows users to upload AVC/H.264 video to its website, and such
-AVC Video is delivered to End Users for free, then such video would
-receive coverage under the sublicense for Internet Broadcast AVC
-Video, which is not subject to any royalties for the life of the AVC
-License. This would also apply in the scenario where a user creates a
-free online account in order to receive a customized offering of free
-AVC Video content. In other words, as long as the End User is given
-access to or views AVC Video content at no cost to the End User, then
-no royalties would be payable under our AVC License.</p>
-
-<p>On the other hand, if End Users pay for access to AVC Video for a
-specific period of time (e.g., one month, one year, etc.), then such
-video would constitute Subscription AVC Video. In cases where AVC
-Video is delivered to End Users on a pay-per-view basis, then such
-content would constitute Title-by-Title AVC Video. If a party offers
-Subscription or Title-by-Title AVC Video to End Users, then they would
-be responsible for paying the applicable royalties you noted below.</p>
-
-<p>Finally, in the case where AVC Video is distributed for free
-through an "over-the-air, satellite and/or cable transmission", then
-such content would constitute Free Television AVC Video and would be
-subject to the applicable royalties.</p>
-
-<p>For your reference, I have attached
-<a href="http://people.skolelinux.org/pere/blog/images/2015-07-07-mpegla.pdf">a
-.pdf copy of the AVC License</a>. You will find the relevant
-sublicense information regarding AVC Video in Sections 2.2 through
-2.5, and the corresponding royalties in Section 3.1.2 through 3.1.4.
-You will also find the definitions of Title-by-Title AVC Video,
-Subscription AVC Video, Free Television AVC Video, and Internet
-Broadcast AVC Video in Section 1 of the License. Please note that the
-electronic copy is provided for informational purposes only and cannot
-be used for execution.</p>
-
-<p>I hope the above information is helpful. If you have additional
-questions or need further assistance with the AVC License, please feel
-free to contact me directly.</p>
-</blockquote></p>
-
-<p>Having a fresh copy of the license text was useful, and knowing
-that the definition of Title-by-Title required payment per title made
-me aware that my earlier understanding of that phrase had been wrong.
-But I still had a few questions:</p>
-
-<p><blockquote>
-<p>I have a small followup question. Would it be possible for me to get
-a license with MPEG LA even if there are no royalties to be paid? The
-reason I ask, is that some video related products have a copyright
-clause limiting their use without a license with MPEG LA. The clauses
-typically look similar to this:
-
-<p><blockquote>
- This product is licensed under the AVC patent portfolio license for
- the personal and non-commercial use of a consumer to (a) encode
- video in compliance with the AVC standard ("AVC video") and/or (b)
- decode AVC video that was encoded by a consumer engaged in a
- personal and non-commercial activity and/or AVC video that was
- obtained from a video provider licensed to provide AVC video. No
- license is granted or shall be implied for any other use. additional
- information may be obtained from MPEG LA L.L.C.
-</blockquote></p>
-
-<p>It is unclear to me if this clause mean that I need to enter into
-an agreement with MPEG LA to use the product in question, even if
-there are no royalties to be paid to MPEG LA. I suspect it will
-differ depending on the jurisdiction, and mine is Norway. What is
-MPEG LAs view on this?</p>
-</blockquote></p>
-
-<p>According to the answer, MPEG LA believe those using such tools for
-non-personal or commercial use need a license with them:</p>
-
-<p><blockquote>
-
-<p>With regard to the Notice to Customers, I would like to begin by
-clarifying that the Notice from Section 7.1 of the AVC License
-reads:</p>
-
-<p>THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
-THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT
-RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC
-STANDARD ("AVC VIDEO") AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED
-BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM
-A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
-OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE
-OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM</p>
-
-<p>The Notice to Customers is intended to inform End Users of the
-personal usage rights (for example, to watch video content) included
-with the product they purchased, and to encourage any party using the
-product for commercial purposes to contact MPEG LA in order to become
-licensed for such use (for example, when they use an AVC Product to
-deliver Title-by-Title, Subscription, Free Television or Internet
-Broadcast AVC Video to End Users, or to re-Sell a third party's AVC
-Product as their own branded AVC Product).</p>
-
-<p>Therefore, if a party is to be licensed for its use of an AVC
-Product to Sell AVC Video on a Title-by-Title, Subscription, Free
-Television or Internet Broadcast basis, that party would need to
-conclude the AVC License, even in the case where no royalties were
-payable under the License. On the other hand, if that party (either a
-Consumer or business customer) simply uses an AVC Product for their
-own internal purposes and not for the commercial purposes referenced
-above, then such use would be included in the royalty paid for the AVC
-Products by the licensed supplier.</p>
-
-<p>Finally, I note that our AVC License provides worldwide coverage in
-countries that have AVC Patent Portfolio Patents, including
-Norway.</p>
-
-<p>I hope this clarification is helpful. If I may be of any further
-assistance, just let me know.</p>
-</blockquote></p>
-
-<p>The mentioning of Norwegian patents made me a bit confused, so I
-asked for more information:</p>
-
-<p><blockquote>
-
-<p>But one minor question at the end. If I understand you correctly,
-you state in the quote above that there are patents in the AVC Patent
-Portfolio that are valid in Norway. This make me believe I read the
-list available from &lt;URL:
-<a href="http://www.mpegla.com/main/programs/AVC/Pages/PatentList.aspx">http://www.mpegla.com/main/programs/AVC/Pages/PatentList.aspx</a>
-&gt; incorrectly, as I believed the "NO" prefix in front of patents
-were Norwegian patents, and the only one I could find under Mitsubishi
-Electric Corporation expired in 2012. Which patents are you referring
-to that are relevant for Norway?</p>
-
-</blockquote></p>
-
-<p>Again, the quick answer explained how to read the list of patents
-in that list:</p>
-
-<p><blockquote>
-
-<p>Your understanding is correct that the last AVC Patent Portfolio
-Patent in Norway expired on 21 October 2012. Therefore, where AVC
-Video is both made and Sold in Norway after that date, then no
-royalties would be payable for such AVC Video under the AVC License.
-With that said, our AVC License provides historic coverage for AVC
-Products and AVC Video that may have been manufactured or Sold before
-the last Norwegian AVC patent expired. I would also like to clarify
-that coverage is provided for the country of manufacture and the
-country of Sale that has active AVC Patent Portfolio Patents.</p>
-
-<p>Therefore, if a party offers AVC Products or AVC Video for Sale in
-a country with active AVC Patent Portfolio Patents (for example,
-Sweden, Denmark, Finland, etc.), then that party would still need
-coverage under the AVC License even if such products or video are
-initially made in a country without active AVC Patent Portfolio
-Patents (for example, Norway). Similarly, a party would need to
-conclude the AVC License if they make AVC Products or AVC Video in a
-country with active AVC Patent Portfolio Patents, but eventually Sell
-such AVC Products or AVC Video in a country without active AVC Patent
-Portfolio Patents.</p>
-</blockquote></p>
-
-<p>As far as I understand it, MPEG LA believe anyone using Adobe
-Premiere and other video related software with a H.264 distribution
-license need a license agreement with MPEG LA to use such tools for
-anything non-private or commercial, while it is OK to set up a
-Youtube-like service as long as no-one pays to get access to the
-content. I still have no clear idea how this applies to Norway, where
-none of the patents MPEG LA is licensing are valid. Will the
-copyright terms take precedence or can those terms be ignored because
-the patents are not valid in Norway?</p>
+ <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
+ <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
+ <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
+ <description><p>This summer, I read a great article
+"<a href="https://www.usenix.org/publications/login/summer2016/curtsinger">coz:
+This Is the Profiler You're Looking For</a>" in USENIX ;login: about
+how to profile multi-threaded programs. It presented a system for
+profiling software by running experiences in the running program,
+testing how run time performance is affected by "speeding up" parts of
+the code to various degrees compared to a normal run. It does this by
+slowing down parallel threads while the "faster up" code is running
+and measure how this affect processing time. The processing time is
+measured using probes inserted into the code, either using progress
+counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
+can also measure unmodified code by measuring complete the program
+runtime and running the program several times instead.</p>
+
+<p>The project and presentation was so inspiring that I would like to
+get the system into Debian. I
+<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708">created
+a WNPP request for it</a> and contacted upstream to try to make the
+system ready for Debian by sending patches. The build process need to
+be changed a bit to avoid running 'git clone' to get dependencies, and
+to include the JavaScript web page used to visualize the collected
+profiling information included in the source package.
+But I expect that should work out fairly soon.</p>
+
+<p>The way the system work is fairly simple. To run an coz experiment
+on a binary with debug symbols available, start the program like this:
+
+<p><blockquote><pre>
+coz run --- program-to-run
+</pre></blockquote></p>
+
+<p>This will create a text file profile.coz with the instrumentation
+information. To show what part of the code affect the performance
+most, use a web browser and either point it to
+<a href="http://plasma-umass.github.io/coz/">http://plasma-umass.github.io/coz/</a>
+or use the copy from git (in the gh-pages branch). Check out this web
+site to have a look at several example profiling runs and get an idea what the end result from the profile runs look like. To make the
+profiling more useful you include &lt;coz.h&gt; and insert the
+COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
+code, rebuild and run the profiler. This allow coz to do more
+targeted experiments.</p>
+
+<p>A video published by ACM
+<a href="https://www.youtube.com/watch?v=jE0V-p1odPg">presenting the
+Coz profiler</a> is available from Youtube. There is also a paper
+from the 25th Symposium on Operating Systems Principles available
+titled
+<a href="https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger">Coz:
+finding code that counts with causal profiling</a>.</p>
+
+<p><a href="https://github.com/plasma-umass/coz">The source code</a>
+for Coz is available from github. It will only build with clang
+because it uses a
+<a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606">C++
+feature missing in GCC</a>, but I've submitted
+<a href="https://github.com/plasma-umass/coz/pull/67">a patch to solve
+it</a> and hope it will be included in the upstream source soon.</p>
+
+<p>Please get in touch if you, like me, would like to see this piece
+of software in Debian. I would very much like some help with the
+packaging effort, as I lack the in depth knowledge on how to package
+C++ libraries.</p>
</description>
</item>
<item>
- <title>New laptop - some more clues and ideas based on feedback</title>
- <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
- <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
- <description><p>Several people contacted me after my previous blog post about my
-need for a new laptop, and provided very useful feedback. I wish to
-thank every one of these. Several pointed me to the possibility of
-fixing my X230, and I am already in the process of getting Lenovo to
-do so thanks to the on site, next day support contract covering the
-machine. But the battery is almost useless (I expect to replace it
-with a non-official battery) and I do not expect the machine to live
-for many more years, so it is time to plan its replacement. If I did
-not have a support contract, it was suggested to find replacement parts
-using <a href="http://www.francecrans.com/">FrancEcrans</a>, but it
-might present a language barrier as I do not understand French.</p>
-
-<p>One tip I got was to use the
-<a href="https://skinflint.co.uk/?cat=nb">Skinflint</a> web service to
-compare laptop models. It seem to have more models available than
-prisjakt.no. Another tip I got from someone I know have similar
-keyboard preferences was that the HP EliteBook 840 keyboard is not
-very good, and this matches my experience with earlier EliteBook
-keyboards I tested. Because of this, I will not consider it any further.
-
-<p>When I wrote my blog post, I was not aware of Thinkpad X250, the
-newest Thinkpad X model. The keyboard reintroduces mouse buttons
-(which is missing from the X240), and is working fairly well with
-Debian Sid/Unstable according to
-<a href="http://www.corsac.net/X250/">Corsac.net</a>. The reports I
-got on the keyboard quality are not consistent. Some say the keyboard
-is good, others say it is ok, while others say it is not very good.
-Those with experience from X41 and and X60 agree that the X250
-keyboard is not as good as those trusty old laptops, and suggest I
-keep and fix my X230 instead of upgrading, or get a used X230 to
-replace it. I'm also told that the X250 lack leds for caps lock, disk
-activity and battery status, which is very convenient on my X230. I'm
-also told that the CPU fan is running very often, making it a bit
-noisy. In any case, the X250 do not work out of the box with Debian
-Stable/Jessie, one of my requirements.</p>
-
-<p>I have also gotten a few vendor proposals, one was
-<a href="http://pro-star.com">Pro-Star</a>, another was
-<a href="http://shop.gluglug.org.uk/product/libreboot-x200/">Libreboot</a>.
-The latter look very attractive to me.</p>
-
-<p>Again, thank you all for the very useful feedback. It help a lot
-as I keep looking for a replacement.</p>
-
-<p>Update 2015-07-06: I was recommended to check out the
-<a href="">lapstore.de</a> web shop for used laptops. They got several
-different
-<a href="http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/">old
-thinkpad X models</a>, and provide one year warranty.</p>
+ <title>Sales number for the Free Culture translation, first half of 2016</title>
+ <link>http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html</guid>
+ <pubDate>Fri, 5 Aug 2016 22:45:00 +0200</pubDate>
+ <description><p>As my regular readers probably remember, the last year I published
+a French and Norwegian translation of the classic
+<a href="http://www.free-culture.cc/">Free Culture book</a> by the
+founder of the Creative Commons movement, Lawrence Lessig. A bit less
+known is the fact that due to the way I created the translations,
+using docbook and po4a, I also recreated the English original. And
+because I already had created a new the PDF edition, I published it
+too. The revenue from the books are sent to the Creative Commons
+Corporation. In other words, I do not earn any money from this
+project, I just earn the warm fuzzy feeling that the text is available
+for a wider audience and more people can learn why the Creative
+Commons is needed.</p>
+
+<p>Today, just for fun, I had a look at the sales number over at
+Lulu.com, which take care of payment, printing and shipping. Much to
+my surprise, the English edition is selling better than both the
+French and Norwegian edition, despite the fact that it has been
+available in English since it was first published. In total, 24 paper
+books was sold for USD $19.99 between 2016-01-01 and 2016-07-31:</p>
+
+<table border="0">
+<tr><th>Title / language</th><th>Quantity</th></tr>
+<tr><td><a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">Culture Libre / French</a></td><td align="right">3</td></tr>
+<tr><td><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Fri kultur / Norwegian</a></td><td align="right">7</td></tr>
+<tr><td><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">Free Culture / English</a></td><td align="right">14</td></tr>
+</table>
+
+<p>The books are available both from Lulu.com and from large book
+stores like Amazon and Barnes&Noble. Most revenue, around $10 per
+book, is sent to the Creative Commons project when the book is sold
+directly by Lulu.com. The other channels give less revenue. The
+summary from Lulu tell me 10 books was sold via the Amazon channel, 10
+via Ingram (what is this?) and 4 directly by Lulu. And Lulu.com tells
+me that the revenue sent so far this year is USD $101.42. No idea
+what kind of sales numbers to expect, so I do not know if that is a
+good amount of sales for a 10 year old book or not. But it make me
+happy that the buyers find the book, and I hope they enjoy reading it
+as much as I did.</p>
+
+<p>The ebook edition is available for free from
+<a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p>
+
+<p>If you would like to translate and publish the book in your native
+language, I would be happy to help make it happen. Please get in
+touch.</p>
</description>
</item>
projects / homepage.git / blobdiff