]> pere.pagekite.me Git - homepage.git/blob - blog/index.html
projects / homepage.git / blob
? search:
summary | shortlog | log | commit | commitdiff | tree
blame | history | raw | HEAD
Bedre språk.
[homepage.git] / blog / index.html
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
4 <head>
5 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
6 <title>Petter Reinholdtsen</title>
7 <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
8 <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
9 <link rel="alternate" title="RSS Feed" href="http://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml" />
10 </head>
11 <body>
12 <div class="title">
13 <h1>
14 <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
15
16 </h1>
17
18 </div>
19
20
21
22 <div class="entry">
23 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html">Experience and updated recipe for using the Signal app without a mobile phone</a></div>
24 <div class="date">10th October 2016</div>
25 <div class="body"><p>In July
26 <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
27 wrote how to get the Signal Chrome/Chromium app working</a> without
28 the ability to receive SMS messages (aka without a cell phone). It is
29 time to share some experiences and provide an updated setup.</p>
30
31 <p>The Signal app have worked fine for several months now, and I use
32 it regularly to chat with my loved ones. I had a major snag at the
33 end of my summer vacation, when the the app completely forgot my
34 setup, identity and keys. The reason behind this major mess was
35 running out of disk space. To avoid that ever happening again I have
36 started storing everything in <tt>userdata/</tt> in git, to be able to
37 roll back to an earlier version if the files are wiped by mistake. I
38 had to use it once after introducing the git backup. When rolling
39 back to an earlier version, one need to use the 'reset session' option
40 in Signal to get going, and notify the people you talk with about the
41 problem. I assume there is some sequence number tracking in the
42 protocol to detect rollback attacks. The git repository is rather big
43 (674 MiB so far), but I have not tried to figure out if some of the
44 content can be added to a .gitignore file due to lack of spare
45 time.</p>
46
47 <p>I've also hit the 90 days timeout blocking, and noticed that this
48 make it impossible to send messages using Signal. I could still
49 receive them, but had to patch the code with a new timestamp to send.
50 I believe the timeout is added by the developers to force people to
51 upgrade to the latest version of the app, even when there is no
52 protocol changes, to reduce the version skew among the user base and
53 thus try to keep the number of support requests down.</p>
54
55 <p>Since my original recipe, the Signal source code changed slightly,
56 making the old patch fail to apply cleanly. Below is an updated
57 patch, including the shell wrapper I use to start Signal. The
58 original version required a new user to locate the JavaScript console
59 and call a function from there. I got help from a friend with more
60 JavaScript knowledge than me to modify the code to provide a GUI
61 button instead. This mean that to get started you just need to run
62 the wrapper and click the 'Register without mobile phone' to get going
63 now. I've also modified the timeout code to always set it to 90 days
64 in the future, to avoid having to patch the code regularly.</p>
65
66 <p>So, the updated recipe for Debian Jessie:</p>
67
68 <ol>
69
70 <li>First, install required packages to get the source code and the
71 browser you need. Signal only work with Chrome/Chromium, as far as I
72 know, so you need to install it.
73
74 <pre>
75 apt install git tor chromium
76 git clone https://github.com/WhisperSystems/Signal-Desktop.git
77 </pre></li>
78
79 <li>Modify the source code using command listed in the the patch
80 block below.</li>
81
82 <li>Start Signal using the run-signal-app wrapper (for example using
83 <tt>`pwd`/run-signal-app</tt>).
84
85 <li>Click on the 'Register without mobile phone', will in a phone
86 number you can receive calls to the next minute, receive the
87 verification code and enter it into the form field and press
88 'Register'. Note, the phone number you use will be user Signal
89 username, ie the way others can find you on Signal.</li>
90
91 <li>You can now use Signal to contact others. Note, new contacts do
92 not show up in the contact list until you restart Signal, and there is
93 no way to assign names to Contacts. There is also no way to create or
94 update chat groups. I suspect this is because the web app do not have
95 a associated contact database.</li>
96
97 </ol>
98
99 <p>I am still a bit uneasy about using Signal, because of the way its
100 main author moxie0 reject federation and accept dependencies to major
101 corporations like Google (part of the code is fetched from Google) and
102 Amazon (the central coordination point is owned by Amazon). See for
103 example
104 <a href="https://github.com/LibreSignal/LibreSignal/issues/37">the
105 LibreSignal issue tracker</a> for a thread documenting the authors
106 view on these issues. But the network effect is strong in this case,
107 and several of the people I want to communicate with already use
108 Signal. Perhaps we can all move to <a href="https://ring.cx/">Ring</a>
109 once it <a href="https://bugs.debian.org/830265">work on my
110 laptop</a>? It already work on Windows and Android, and is included
111 in <a href="https://tracker.debian.org/pkg/ring">Debian</a> and
112 <a href="https://launchpad.net/ubuntu/+source/ring">Ubuntu</a>, but not
113 working on Debian Stable.</p>
114
115 <p>Anyway, this is the patch I apply to the Signal code to get it
116 working. It switch to the production servers, disable to timeout,
117 make registration easier and add the shell wrapper:</p>
118
119 <pre>
120 cd Signal-Desktop; cat &lt;&lt;EOF | patch -p1
121 diff --git a/js/background.js b/js/background.js
122 index 24b4c1d..579345f 100644
123 --- a/js/background.js
124 +++ b/js/background.js
125 @@ -33,9 +33,9 @@
126 });
127 });
128
129 - var SERVER_URL = 'https://textsecure-service-staging.whispersystems.org';
130 + var SERVER_URL = 'https://textsecure-service-ca.whispersystems.org';
131 var SERVER_PORTS = [80, 4433, 8443];
132 - var ATTACHMENT_SERVER_URL = 'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com';
133 + var ATTACHMENT_SERVER_URL = 'https://whispersystems-textsecure-attachments.s3.amazonaws.com';
134 var messageReceiver;
135 window.getSocketStatus = function() {
136 if (messageReceiver) {
137 diff --git a/js/expire.js b/js/expire.js
138 index 639aeae..beb91c3 100644
139 --- a/js/expire.js
140 +++ b/js/expire.js
141 @@ -1,6 +1,6 @@
142 ;(function() {
143 'use strict';
144 - var BUILD_EXPIRATION = 0;
145 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
146
147 window.extension = window.extension || {};
148
149 diff --git a/js/views/install_view.js b/js/views/install_view.js
150 index 7816f4f..1d6233b 100644
151 --- a/js/views/install_view.js
152 +++ b/js/views/install_view.js
153 @@ -38,7 +38,8 @@
154 return {
155 'click .step1': this.selectStep.bind(this, 1),
156 'click .step2': this.selectStep.bind(this, 2),
157 - 'click .step3': this.selectStep.bind(this, 3)
158 + 'click .step3': this.selectStep.bind(this, 3),
159 + 'click .callreg': function() { extension.install('standalone') },
160 };
161 },
162 clearQR: function() {
163 diff --git a/options.html b/options.html
164 index dc0f28e..8d709f6 100644
165 --- a/options.html
166 +++ b/options.html
167 @@ -14,7 +14,10 @@
168 &lt;div class='nav'>
169 &lt;h1>{{ installWelcome }}&lt;/h1>
170 &lt;p>{{ installTagline }}&lt;/p>
171 - &lt;div> &lt;a class='button step2'>{{ installGetStartedButton }}&lt;/a> &lt;/div>
172 + &lt;div> &lt;a class='button step2'>{{ installGetStartedButton }}&lt;/a>
173 + &lt;br> &lt;a class="button callreg">Register without mobile phone&lt;/a>
174 +
175 + &lt;/div>
176 &lt;span class='dot step1 selected'>&lt;/span>
177 &lt;span class='dot step2'>&lt;/span>
178 &lt;span class='dot step3'>&lt;/span>
179 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
180 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
181 @@ -0,0 +1,12 @@
182 +#!/bin/sh
183 +set -e
184 +cd $(dirname $0)
185 +mkdir -p userdata
186 +userdata="`pwd`/userdata"
187 +if [ -d "$userdata" ] && [ ! -d "$userdata/.git" ] ; then
188 + (cd $userdata && git init)
189 +fi
190 +(cd $userdata && git add . && git commit -m "Current status." || true)
191 +exec chromium \
192 + --proxy-server="socks://localhost:9050" \
193 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
194 EOF
195 chmod a+rx run-signal-app
196 </pre>
197
198 <p>As usual, if you use Bitcoin and want to show your support of my
199 activities, please send Bitcoin donations to my address
200 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
201 </div>
202 <div class="tags">
203
204
205 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
206
207
208 </div>
209 </div>
210 <div class="padding"></div>
211
212 <div class="entry">
213 <div class="title"><a href="http://people.skolelinux.org/pere/blog/NRKs_kildevern_n_r_NRK_epost_deles_med_utenlands_etterretning_.html">NRKs kildevern når NRK-epost deles med utenlands etterretning?</a></div>
214 <div class="date"> 8th October 2016</div>
215 <div class="body"><p>NRK
216 <a href="https://nrkbeta.no/2016/09/02/securing-whistleblowers/">lanserte
217 for noen uker siden</a> en ny
218 <a href="https://www.nrk.no/varsle/">varslerportal som bruker
219 SecureDrop til å ta imot tips</a> der det er vesentlig at ingen
220 utenforstående får vite at NRK er tipset. Det er et langt steg
221 fremover for NRK, og når en leser bloggposten om hva de har tenkt på
222 og hvordan løsningen er satt opp virker det som om de har gjort en
223 grundig jobb der. Men det er ganske mye ekstra jobb å motta tips via
224 SecureDrop, så varslersiden skriver "Nyhetstips som ikke krever denne
225 typen ekstra vern vil vi gjerne ha på nrk.no/03030", og 03030-siden
226 foreslår i tillegg til et webskjema å bruke epost, SMS, telefon,
227 personlig oppmøte og brevpost. Denne artikkelen handler disse andre
228 metodene.</p>
229
230 <p>Når en sender epost til en @nrk.no-adresse så vil eposten sendes ut
231 av landet til datamaskiner kontrollert av Microsoft. En kan sjekke
232 dette selv ved å slå opp epostleveringsadresse (MX) i DNS. For NRK er
233 dette i dag "nrk-no.mail.protection.outlook.com". NRK har som en ser
234 valgt å sette bort epostmottaket sitt til de som står bak outlook.com,
235 dvs. Microsoft. En kan sjekke hvor nettverkstrafikken tar veien
236 gjennom Internett til epostmottaket vha. programmet
237 <tt>traceroute</tt>, og finne ut hvem som eier en Internett-adresse
238 vha. whois-systemet. Når en gjør dette for epost-trafikk til @nrk.no
239 ser en at trafikken fra Norge mot nrk-no.mail.protection.outlook.com
240 går via Sverige mot enten Irland eller Tyskland (det varierer fra gang
241 til gang og kan endre seg over tid).</p>
242
243 <p>Vi vet fra
244 <a href="https://no.wikipedia.org/wiki/FRA-loven">introduksjonen av
245 FRA-loven</a> at IP-trafikk som passerer grensen til Sverige avlyttes
246 av Försvarets radioanstalt (FRA). Vi vet videre takket være
247 Snowden-bekreftelsene at trafikk som passerer grensen til
248 Storbritannia avlyttes av Government Communications Headquarters
249 (GCHQ). I tillegg er er det nettopp lansert et forslag i Norge om at
250 forsvarets E-tjeneste skal få avlytte trafikk som krysser grensen til
251 Norge. Jeg er ikke kjent med dokumentasjon på at Irland og Tyskland
252 gjør det samme. Poenget er uansett at utenlandsk etterretning har
253 mulighet til å snappe opp trafikken når en sender epost til @nrk.no.
254 I tillegg er det selvsagt tilgjengelig for Microsoft som er underlagt USAs
255 jurisdiksjon og
256 <a href="https://www.theguardian.com/world/2013/jul/11/microsoft-nsa-collaboration-user-data">samarbeider
257 med USAs etterretning på flere områder</a>. De som tipser NRK om
258 nyheter via epost kan dermed gå ut fra at det blir kjent for mange
259 andre enn NRK at det er gjort.</p>
260
261 <p>Bruk av SMS og telefon registreres av blant annet telefonselskapene
262 og er tilgjengelig i følge lov og forskrift for blant annet Politi,
263 NAV og Finanstilsynet, i tillegg til IT-folkene hos telefonselskapene
264 og deres overordnede. Hvis innringer eller mottaker bruker
265 smarttelefon vil slik kontakt også gjøres tilgjengelig for ulike
266 app-leverandører og de som lytter på trafikken mellom telefon og
267 app-leverandør, alt etter hva som er installert på telefonene som
268 brukes.</p>
269
270 <p>Brevpost kan virke trygt, og jeg vet ikke hvor mye som registreres
271 og lagres av postens datastyrte postsorteringssentraler. Det vil ikke
272 overraske meg om det lagres hvor i landet hver konvolutt kommer fra og
273 hvor den er adressert, i hvert fall for en kortere periode. Jeg vet
274 heller ikke hvem slik informasjon gjøres tilgjengelig for. Det kan
275 være nok til å ringe inn potensielle kilder når det krysses med hvem
276 som kjente til aktuell informasjon og hvor de befant seg (tilgjengelig
277 f.eks. hvis de bærer mobiltelefon eller bor i nærheten).</p>
278
279 <p>Personlig oppmøte hos en NRK-journalist er antagelig det tryggeste,
280 men en bør passe seg for å bruke NRK-kantina. Der bryter de nemlig
281 <a href="http://www.lovdata.no/all/hl-19850524-028.html#14">Sentralbanklovens
282 paragraf 14</a> og nekter folk å betale med kontanter. I stedet
283 krever de at en varsle sin bankkortutsteder om hvor en befinner seg
284 ved å bruke bankkort. Banktransaksjoner er tilgjengelig for
285 bankkortutsteder (det være seg VISA, Mastercard, Nets og/eller en
286 bank) i tillegg til politiet og i hvert fall tidligere med Se & Hør
287 (via utro tjenere, slik det ble avslørt etter utgivelsen av boken
288 «Livet, det forbannede» av Ken B. Rasmussen). Men hvor mange kjenner
289 en NRK-journalist personlig? Besøk på NRK på Marienlyst krever at en
290 registrerer sin ankost elektronisk i besøkssystemet. Jeg vet ikke hva
291 som skjer med det datasettet, men har grunn til å tro at det sendes ut
292 SMS til den en skal besøke med navnet som er oppgitt. Kanskje greit å
293 oppgi falskt navn.</p>
294
295 <p>Når så tipset er kommet frem til NRK skal det behandles
296 redaksjonelt i NRK. Der vet jeg via ulike kilder at de fleste
297 journalistene bruker lokalt installert programvare, men noen bruker
298 Google Docs og andre skytjenester i strid med interne retningslinjer
299 når de skriver. Hvordan vet en hvem det gjelder? Ikke vet jeg, men
300 det kan være greit å spørre for å sjekke at journalisten har tenkt på
301 problemstillingen, før en gir et tips. Og hvis tipset omtales internt
302 på epost, er det jo grunn til å tro at også intern eposten vil deles
303 med Microsoft og utenlands etterretning, slik tidligere nevnt, men det
304 kan hende at det holdes internt i NRKs interne MS Exchange-løsning.
305 Men Microsoft ønsker å få alle Exchange-kunder over "i skyen" (eller
306 andre folks datamaskiner, som det jo innebærer), så jeg vet ikke hvor
307 lenge det i så fall vil vare.</p>
308
309 <p>I tillegg vet en jo at
310 <a href="https://www.nrk.no/ytring/elektronisk-kildevern-i-nrk-1.11941196">NRK
311 har valgt å gi nasjonal sikkerhetsmyndighet (NSM) tilgang til å se på
312 intern og ekstern Internett-trafikk</a> hos NRK ved oppsett av såkalte
313 VDI-noder, på tross av
314 <a href="https://www.nrk.no/ytring/bekymring-for-nrks-kildevern-1.11941584">protester
315 fra NRKs journalistlag</a>. Jeg vet ikke om den vil kunne snappe opp
316 dokumenter som lagres på interne filtjenere eller dokumenter som lages
317 i de interne webbaserte publiseringssystemene, men vet at hva noden
318 ser etter på nettet kontrolleres av NSM og oppdateres automatisk, slik
319 at det ikke gir så mye mening å sjekke hva noden ser etter i dag når
320 det kan endres automatisk i morgen.</p>
321
322 <p>Personlig vet jeg ikke om jeg hadde turt tipse NRK hvis jeg satt på
323 noe som kunne være en trussel mot den bestående makten i Norge eller
324 verden. Til det virker det å være for mange åpninger for
325 utenforstående med andre prioriteter enn NRKs journalistiske fokus.
326 Og den største truslen for en varsler er jo om metainformasjon kommer
327 på avveie, dvs. informasjon om at en har vært i kontakt med en
328 journalist. Det kan være nok til at en kommer i myndighetenes
329 søkelys, og de færreste har nok operasjonell sikkerhet til at vil tåle
330 slik flombelysning på sitt privatliv.</p>
331 </div>
332 <div class="tags">
333
334
335 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/dld">dld</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
336
337
338 </div>
339 </div>
340 <div class="padding"></div>
341
342 <div class="entry">
343 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html">Isenkram, Appstream and udev make life as a LEGO builder easier</a></div>
344 <div class="date"> 7th October 2016</div>
345 <div class="body"><p><a href="http://packages.qa.debian.org/isenkram">The Isenkram
346 system</a> provide a practical and easy way to figure out which
347 packages support the hardware in a given machine. The command line
348 tool <tt>isenkram-lookup</tt> and the tasksel options provide a
349 convenient way to list and install packages relevant for the current
350 hardware during system installation, both user space packages and
351 firmware packages. The GUI background daemon on the other hand provide
352 a pop-up proposing to install packages when a new dongle is inserted
353 while using the computer. For example, if you plug in a smart card
354 reader, the system will ask if you want to install <tt>pcscd</tt> if
355 that package isn't already installed, and if you plug in a USB video
356 camera the system will ask if you want to install <tt>cheese</tt> if
357 cheese is currently missing. This already work just fine.</p>
358
359 <p>But Isenkram depend on a database mapping from hardware IDs to
360 package names. When I started no such database existed in Debian, so
361 I made my own data set and included it with the isenkram package and
362 made isenkram fetch the latest version of this database from git using
363 http. This way the isenkram users would get updated package proposals
364 as soon as I learned more about hardware related packages.</p>
365
366 <p>The hardware is identified using modalias strings. The modalias
367 design is from the Linux kernel where most hardware descriptors are
368 made available as a strings that can be matched using filename style
369 globbing. It handle USB, PCI, DMI and a lot of other hardware related
370 identifiers.</p>
371
372 <p>The downside to the Isenkram specific database is that there is no
373 information about relevant distribution / Debian version, making
374 isenkram propose obsolete packages too. But along came AppStream, a
375 cross distribution mechanism to store and collect metadata about
376 software packages. When I heard about the proposal, I contacted the
377 people involved and suggested to add a hardware matching rule using
378 modalias strings in the specification, to be able to use AppStream for
379 mapping hardware to packages. This idea was accepted and AppStream is
380 now a great way for a package to announce the hardware it support in a
381 distribution neutral way. I wrote
382 <a href="http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html">a
383 recipe on how to add such meta-information</a> in a blog post last
384 December. If you have a hardware related package in Debian, please
385 announce the relevant hardware IDs using AppStream.</p>
386
387 <p>In Debian, almost all packages that can talk to a LEGO Mindestorms
388 RCX or NXT unit, announce this support using AppStream. The effect is
389 that when you insert such LEGO robot controller into your Debian
390 machine, Isenkram will propose to install the packages needed to get
391 it working. The intention is that this should allow the local user to
392 start programming his robot controller right away without having to
393 guess what packages to use or which permissions to fix.</p>
394
395 <p>But when I sat down with my son the other day to program our NXT
396 unit using his Debian Stretch computer, I discovered something
397 annoying. The local console user (ie my son) did not get access to
398 the USB device for programming the unit. This used to work, but no
399 longer in Jessie and Stretch. After some investigation and asking
400 around on #debian-devel, I discovered that this was because udev had
401 changed the mechanism used to grant access to local devices. The
402 ConsoleKit mechanism from <tt>/lib/udev/rules.d/70-udev-acl.rules</tt>
403 no longer applied, because LDAP users no longer was added to the
404 plugdev group during login. Michael Biebl told me that this method
405 was obsolete and the new method used ACLs instead. This was good
406 news, as the plugdev mechanism is a mess when using a remote user
407 directory like LDAP. Using ACLs would make sure a user lost device
408 access when she logged out, even if the user left behind a background
409 process which would retain the plugdev membership with the ConsoleKit
410 setup. Armed with this knowledge I moved on to fix the access problem
411 for the LEGO Mindstorms related packages.</p>
412
413 <p>The new system uses a udev tag, 'uaccess'. It can either be
414 applied directly for a device, or is applied in
415 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
416 LEGO Mindstorms udev rules did not have a class, I decided to add the
417 tag directly in the udev rules files included in the packages. Here
418 is one example. For the nqc C compiler for the RCX, the
419 <tt>/lib/udev/rules.d/60-nqc.rules</tt> file now look like this:
420
421 <p><pre>
422 SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694", ATTR{idProduct}=="0001", \
423 SYMLINK+="rcx-%k", TAG+="uaccess"
424 </pre></p>
425
426 <p>The key part is the 'TAG+="uaccess"' at the end. I suspect all
427 packages using plugdev in their /lib/udev/rules.d/ files should be
428 changed to use this tag (either directly or indirectly via
429 <tt>70-uaccess.rules</tt>). Perhaps a lintian check should be created
430 to detect this?</p>
431
432 <p>I've been unable to find good documentation on the uaccess feature.
433 It is unclear to me if the uaccess tag is an internal implementation
434 detail like the udev-acl tag used by
435 <tt>/lib/udev/rules.d/70-udev-acl.rules</tt>. If it is, I guess the
436 indirect method is the preferred way. Michael
437 <a href="https://github.com/systemd/systemd/issues/4288">asked for more
438 documentation from the systemd project</a> and I hope it will make
439 this clearer. For now I use the generic classes when they exist and
440 is already handled by <tt>70-uaccess.rules</tt>, and add the tag
441 directly if no such class exist.</p>
442
443 <p>To learn more about the isenkram system, please check out
444 <a href="http://people.skolelinux.org/pere/blog/tags/isenkram/">my
445 blog posts tagged isenkram</a>.</p>
446
447 <p>To help out making life for LEGO constructors in Debian easier,
448 please join us on our IRC channel
449 <a href="irc://irc.debian.org/%23debian-lego">#debian-lego</a> and join
450 the <a href="https://alioth.debian.org/projects/debian-lego/">Debian
451 LEGO team</a> in the Alioth project we created yesterday. A mailing
452 list is not yet created, but we are working on it. :)</p>
453
454 <p>As usual, if you use Bitcoin and want to show your support of my
455 activities, please send Bitcoin donations to my address
456 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
457 </div>
458 <div class="tags">
459
460
461 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>.
462
463
464 </div>
465 </div>
466 <div class="padding"></div>
467
468 <div class="entry">
469 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Aftenposten_redakt_ren_med_lua_i_h_nda.html">Aftenposten-redaktøren med lua i hånda</a></div>
470 <div class="date"> 9th September 2016</div>
471 <div class="body"><p>En av dagens nyheter er at Aftenpostens redaktør Espen Egil Hansen
472 bruker
473 <a href="https://www.nrk.no/kultur/aftenposten-brukar-heile-forsida-pa-facebook-kritikk-1.13126918">forsiden
474 av papiravisen på et åpent brev til Facebooks sjef Mark Zuckerberg om
475 Facebooks fjerning av bilder, tekster og sider de ikke liker</a>. Det
476 må være uvant for redaktøren i avisen Aftenposten å stå med lua i
477 handa og håpe på å bli hørt. Spesielt siden Aftenposten har vært med
478 på å gi Facebook makten de nå demonstrerer at de har. Ved å melde seg
479 inn i Facebook-samfunnet har de sagt ja til bruksvilkårene og inngått
480 en antagelig bindende avtale. Kanskje de skulle lest og vurdert
481 vilkårene litt nærmere før de sa ja, i stedet for å klage over at
482 reglende de har valgt å akseptere blir fulgt? Personlig synes jeg
483 vilkårene er uakseptable og det ville ikke falle meg inn å gå inn på
484 en avtale med slike vilkår. I tillegg til uakseptable vilkår er det
485 mange andre grunner til å unngå Facebook. Du kan finne en solid
486 gjennomgang av flere slike argumenter hos
487 <a href="https://stallman.org/facebook.html">Richard Stallmans side om
488 Facebook</a>.
489
490 <p>Jeg håper flere norske redaktører på samme vis må stå med lua i
491 hånden inntil de forstår at de selv er med på å føre samfunnet på
492 ville veier ved å omfavne Facebook slik de gjør når de omtaler og
493 løfter frem saker fra Facebook, og tar i bruk Facebook som
494 distribusjonskanal for sine nyheter. De bidrar til
495 overvåkningssamfunnet og raderer ut lesernes privatsfære når de lenker
496 til Facebook på sine sider, og låser seg selv inne i en omgivelse der
497 det er Facebook, og ikke redaktøren, som sitter med makta.</p>
498
499 <p>Men det vil nok ta tid, i et Norge der de fleste nettredaktører
500 <a href="http://people.skolelinux.org/pere/blog/Snurpenot_overv_kning_av_sensitiv_personinformasjon.html">deler
501 sine leseres personopplysinger med utenlands etterretning</a>.</p>
502
503 <p>For øvrig burde varsleren Edward Snowden få politisk asyl i
504 Norge.</p>
505 </div>
506 <div class="tags">
507
508
509 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
510
511
512 </div>
513 </div>
514 <div class="padding"></div>
515
516 <div class="entry">
517 <div class="title"><a href="http://people.skolelinux.org/pere/blog/E_tjenesten_ber_om_innsyn_i_eposten_til_partiene_p__Stortinget.html">E-tjenesten ber om innsyn i eposten til partiene på Stortinget</a></div>
518 <div class="date"> 6th September 2016</div>
519 <div class="body"><p>I helga kom det et hårreisende forslag fra Lysne II-utvalget satt
520 ned av Forsvarsdepartementet. Lysne II-utvalget var bedt om å vurdere
521 ønskelista til Forsvarets etterretningstjeneste (e-tjenesten), og har
522 kommet med
523 <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
524 om at e-tjenesten skal få lov til a avlytte all Internett-trafikk</a>
525 som passerer Norges grenser. Få er klar over at dette innebærer at
526 e-tjenesten får tilgang til epost sendt til de fleste politiske
527 partiene på Stortinget. Regjeringspartiet Høyre (@hoyre.no),
528 støttepartiene Venstre (@venstre.no) og Kristelig Folkeparti (@krf.no)
529 samt Sosialistisk Ventreparti (@sv.no) og Miljøpartiet de grønne
530 (@mdg.no) har nemlig alle valgt å ta imot eposten sin via utenlandske
531 tjenester. Det betyr at hvis noen sender epost til noen med en slik
532 adresse vil innholdet i eposten, om dette forslaget blir vedtatt, gjøres
533 tilgjengelig for e-tjenesten. Venstre, Sosialistisk Ventreparti og
534 Miljøpartiet De Grønne har valgt å motta sin epost hos Google,
535 Kristelig Folkeparti har valgt å motta sin epost hos Microsoft, og
536 Høyre har valgt å motta sin epost hos Comendo med mottak i Danmark og
537 Irland. Kun Arbeiderpartiet og Fremskrittspartiet har valgt å motta
538 eposten sin i Norge, hos henholdsvis Intility AS og Telecomputing
539 AS.</p>
540
541 <p>Konsekvensen er at epost inn og ut av de politiske organisasjonene,
542 til og fra partimedlemmer og partiets tillitsvalgte vil gjøres
543 tilgjengelig for e-tjenesten for analyse og sortering. Jeg mistenker
544 at kunnskapen som slik blir tilgjengelig vil være nyttig hvis en
545 ønsker å vite hvilke argumenter som treffer publikum når en ønsker å
546 påvirke Stortingets representanter.</p
547
548 <p>Ved hjelp av MX-oppslag i DNS for epost-domene, tilhørende
549 whois-oppslag av IP-adressene og traceroute for å se hvorvidt
550 trafikken går via utlandet kan enhver få bekreftet at epost sendt til
551 de omtalte partiene vil gjøres tilgjengelig for forsvarets
552 etterretningstjeneste hvis forslaget blir vedtatt. En kan også bruke
553 den kjekke nett-tjenesten <a href="http://ipinfo.io/">ipinfo.io</a>
554 for å få en ide om hvor i verden en IP-adresse hører til.</p>
555
556 <p>På den positive siden vil forslaget gjøre at enda flere blir
557 motivert til å ta grep for å bruke
558 <a href="https://www.torproject.org/">Tor</a> og krypterte
559 kommunikasjonsløsninger for å kommunisere med sine kjære, for å sikre
560 at privatsfæren vernes. Selv bruker jeg blant annet
561 <a href="https://www.freedomboxfoundation.org/">FreedomBox</a> og
562 <a href="https://whispersystems.org/">Signal</a> til slikt. Ingen av
563 dem er optimale, men de fungerer ganske bra allerede og øker kostnaden
564 for dem som ønsker å invadere mitt privatliv.</p>
565
566 <p>For øvrig burde varsleren Edward Snowden få politisk asyl i
567 Norge.</p>
568
569 <!--
570
571 venstre.no
572 venstre.no mail is handled by 10 aspmx.l.google.com.
573 venstre.no mail is handled by 20 alt1.aspmx.l.google.com.
574 venstre.no mail is handled by 20 alt2.aspmx.l.google.com.
575 venstre.no mail is handled by 30 aspmx2.googlemail.com.
576 venstre.no mail is handled by 30 aspmx3.googlemail.com.
577
578 traceroute to aspmx.l.google.com (173.194.222.27), 30 hops max, 60 byte packets
579 1 uio-gw10.uio.no (129.240.6.1) 0.411 ms 0.438 ms 0.536 ms
580 2 uio-gw8.uio.no (129.240.24.229) 0.375 ms 0.452 ms 0.548 ms
581 3 oslo-gw1.uninett.no (128.39.65.17) 1.940 ms 1.950 ms 1.942 ms
582 4 se-tug.nordu.net (109.105.102.108) 6.910 ms 6.949 ms 7.283 ms
583 5 google-gw.nordu.net (109.105.98.6) 6.975 ms 6.967 ms 6.958 ms
584 6 209.85.250.192 (209.85.250.192) 7.337 ms 7.286 ms 10.890 ms
585 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
586 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
587 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
588 10 * * *
589
590 mdg.no
591 mdg.no mail is handled by 1 aspmx.l.google.com.
592 mdg.no mail is handled by 5 alt2.aspmx.l.google.com.
593 mdg.no mail is handled by 5 alt1.aspmx.l.google.com.
594 mdg.no mail is handled by 10 aspmx2.googlemail.com.
595 mdg.no mail is handled by 10 aspmx3.googlemail.com.
596 sv.no
597 sv.no mail is handled by 1 aspmx.l.google.com.
598 sv.no mail is handled by 5 alt1.aspmx.l.google.com.
599 sv.no mail is handled by 5 alt2.aspmx.l.google.com.
600 sv.no mail is handled by 10 aspmx3.googlemail.com.
601 sv.no mail is handled by 10 aspmx2.googlemail.com.
602 hoyre.no
603 hoyre.no mail is handled by 10 hoyre-no.mx1.comendosystems.com.
604 hoyre.no mail is handled by 20 hoyre-no.mx2.comendosystems.net.
605
606 traceroute to hoyre-no.mx1.comendosystems.com (89.104.206.4), 30 hops max, 60 byte packets
607 1 uio-gw10.uio.no (129.240.6.1) 0.450 ms 0.510 ms 0.591 ms
608 2 uio-gw8.uio.no (129.240.24.229) 0.383 ms 0.508 ms 0.596 ms
609 3 oslo-gw1.uninett.no (128.39.65.17) 0.311 ms 0.315 ms 0.300 ms
610 4 se-tug.nordu.net (109.105.102.108) 6.837 ms 6.842 ms 6.834 ms
611 5 dk-uni.nordu.net (109.105.97.10) 26.073 ms 26.085 ms 26.076 ms
612 6 dix.1000m.soeborg.ip.comendo.dk (192.38.7.22) 15.372 ms 15.046 ms 15.123 ms
613 7 89.104.192.65 (89.104.192.65) 15.875 ms 15.990 ms 16.239 ms
614 8 89.104.192.179 (89.104.192.179) 15.676 ms 15.674 ms 15.664 ms
615 9 03dm-com.mx1.staysecuregroup.com (89.104.206.4) 15.637 ms * *
616
617 krf.no
618 krf.no mail is handled by 10 krf-no.mail.protection.outlook.com.
619
620 traceroute to krf-no.mail.protection.outlook.com (213.199.154.42), 30 hops max, 60 byte packets
621 1 uio-gw10.uio.no (129.240.6.1) 0.401 ms 0.438 ms 0.536 ms
622 2 uio-gw8.uio.no (129.240.24.229) 11.076 ms 11.120 ms 11.204 ms
623 3 oslo-gw1.uninett.no (128.39.65.17) 0.232 ms 0.234 ms 0.271 ms
624 4 se-tug.nordu.net (109.105.102.108) 6.811 ms 6.820 ms 6.815 ms
625 5 netnod-ix-ge-a-sth-4470.microsoft.com (195.245.240.181) 7.074 ms 7.013 ms 7.061 ms
626 6 ae1-0.sto-96cbe-1b.ntwk.msn.net (104.44.225.161) 7.227 ms 7.362 ms 7.293 ms
627 7 be-8-0.ibr01.ams.ntwk.msn.net (104.44.5.7) 41.993 ms 43.334 ms 41.939 ms
628 8 be-1-0.ibr02.ams.ntwk.msn.net (104.44.4.214) 43.153 ms 43.507 ms 43.404 ms
629 9 ae3-0.fra-96cbe-1b.ntwk.msn.net (104.44.5.17) 29.897 ms 29.831 ms 29.794 ms
630 10 ae10-0.vie-96cbe-1a.ntwk.msn.net (198.206.164.1) 42.309 ms 42.130 ms 41.808 ms
631 11 * ae8-0.vie-96cbe-1b.ntwk.msn.net (104.44.227.29) 41.425 ms *
632 12 * * *
633
634 arbeiderpartiet.no
635 arbeiderpartiet.no mail is handled by 10 mail.intility.com.
636 arbeiderpartiet.no mail is handled by 20 mail2.intility.com.
637
638 traceroute to mail.intility.com (188.95.245.87), 30 hops max, 60 byte packets
639 1 uio-gw10.uio.no (129.240.6.1) 0.486 ms 0.508 ms 0.649 ms
640 2 uio-gw8.uio.no (129.240.24.229) 0.416 ms 0.508 ms 0.620 ms
641 3 oslo-gw1.uninett.no (128.39.65.17) 0.276 ms 0.278 ms 0.275 ms
642 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 0.374 ms 0.371 ms 0.416 ms
643 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
644 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
645 7 cD2EC45C1.static.as2116.net (193.69.236.210) 0.654 ms 0.615 ms 0.590 ms
646 8 185.7.132.38 (185.7.132.38) 1.661 ms 1.808 ms 1.695 ms
647 9 185.7.132.100 (185.7.132.100) 1.793 ms 1.943 ms 1.546 ms
648 10 * * *
649
650 frp.no
651 frp.no mail is handled by 10 mx03.telecomputing.no.
652 frp.no mail is handled by 20 mx01.telecomputing.no.
653
654 traceroute to mx03.telecomputing.no (95.128.105.102), 30 hops max, 60 byte packets
655 1 uio-gw10.uio.no (129.240.6.1) 0.378 ms 0.402 ms 0.479 ms
656 2 uio-gw8.uio.no (129.240.24.229) 0.361 ms 0.458 ms 0.548 ms
657 3 oslo-gw1.uninett.no (128.39.65.17) 0.361 ms 0.352 ms 0.336 ms
658 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
659 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
660 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
661 7 95.128.105.3 (95.128.105.3) 1.050 ms 1.288 ms 1.182 ms
662 8 mx03.telecomputing.no (95.128.105.102) 0.717 ms 0.703 ms 0.692 ms
663
664 -->
665 </div>
666 <div class="tags">
667
668
669 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
670
671
672 </div>
673 </div>
674 <div class="padding"></div>
675
676 <div class="entry">
677 <div class="title"><a href="http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html">First draft Norwegian Bokmål edition of The Debian Administrator's Handbook now public</a></div>
678 <div class="date">30th August 2016</div>
679 <div class="body"><p>In April we
680 <a href="http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html">started
681 to work</a> on a Norwegian Bokmål edition of the "open access" book on
682 how to set up and administrate a Debian system. Today I am happy to
683 report that the first draft is now publicly available. You can find
684 it on <a href="https://debian-handbook.info/get/">get the Debian
685 Administrator's Handbook page</a> (under Other languages). The first
686 eight chapters have a first draft translation, and we are working on
687 proofreading the content. If you want to help out, please start
688 contributing using
689 <a href="https://hosted.weblate.org/projects/debian-handbook/">the
690 hosted weblate project page</a>, and get in touch using
691 <a href="http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators">the
692 translators mailing list</a>. Please also check out
693 <a href="https://debian-handbook.info/contribute/">the instructions for
694 contributors</a>. A good way to contribute is to proofread the text
695 and update weblate if you find errors.</p>
696
697 <p>Our goal is still to make the Norwegian book available on paper as well as
698 electronic form.</p>
699 </div>
700 <div class="tags">
701
702
703 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
704
705
706 </div>
707 </div>
708 <div class="padding"></div>
709
710 <div class="entry">
711 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html">Coz can help you find bottlenecks in multi-threaded software - nice free software</a></div>
712 <div class="date">11th August 2016</div>
713 <div class="body"><p>This summer, I read a great article
714 "<a href="https://www.usenix.org/publications/login/summer2016/curtsinger">coz:
715 This Is the Profiler You're Looking For</a>" in USENIX ;login: about
716 how to profile multi-threaded programs. It presented a system for
717 profiling software by running experiences in the running program,
718 testing how run time performance is affected by "speeding up" parts of
719 the code to various degrees compared to a normal run. It does this by
720 slowing down parallel threads while the "faster up" code is running
721 and measure how this affect processing time. The processing time is
722 measured using probes inserted into the code, either using progress
723 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
724 can also measure unmodified code by measuring complete the program
725 runtime and running the program several times instead.</p>
726
727 <p>The project and presentation was so inspiring that I would like to
728 get the system into Debian. I
729 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708">created
730 a WNPP request for it</a> and contacted upstream to try to make the
731 system ready for Debian by sending patches. The build process need to
732 be changed a bit to avoid running 'git clone' to get dependencies, and
733 to include the JavaScript web page used to visualize the collected
734 profiling information included in the source package.
735 But I expect that should work out fairly soon.</p>
736
737 <p>The way the system work is fairly simple. To run an coz experiment
738 on a binary with debug symbols available, start the program like this:
739
740 <p><blockquote><pre>
741 coz run --- program-to-run
742 </pre></blockquote></p>
743
744 <p>This will create a text file profile.coz with the instrumentation
745 information. To show what part of the code affect the performance
746 most, use a web browser and either point it to
747 <a href="http://plasma-umass.github.io/coz/">http://plasma-umass.github.io/coz/</a>
748 or use the copy from git (in the gh-pages branch). Check out this web
749 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
750 profiling more useful you include &lt;coz.h&gt; and insert the
751 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
752 code, rebuild and run the profiler. This allow coz to do more
753 targeted experiments.</p>
754
755 <p>A video published by ACM
756 <a href="https://www.youtube.com/watch?v=jE0V-p1odPg">presenting the
757 Coz profiler</a> is available from Youtube. There is also a paper
758 from the 25th Symposium on Operating Systems Principles available
759 titled
760 <a href="https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger">Coz:
761 finding code that counts with causal profiling</a>.</p>
762
763 <p><a href="https://github.com/plasma-umass/coz">The source code</a>
764 for Coz is available from github. It will only build with clang
765 because it uses a
766 <a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606">C++
767 feature missing in GCC</a>, but I've submitted
768 <a href="https://github.com/plasma-umass/coz/pull/67">a patch to solve
769 it</a> and hope it will be included in the upstream source soon.</p>
770
771 <p>Please get in touch if you, like me, would like to see this piece
772 of software in Debian. I would very much like some help with the
773 packaging effort, as I lack the in depth knowledge on how to package
774 C++ libraries.</p>
775 </div>
776 <div class="tags">
777
778
779 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>.
780
781
782 </div>
783 </div>
784 <div class="padding"></div>
785
786 <div class="entry">
787 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html">Sales number for the Free Culture translation, first half of 2016</a></div>
788 <div class="date"> 5th August 2016</div>
789 <div class="body"><p>As my regular readers probably remember, the last year I published
790 a French and Norwegian translation of the classic
791 <a href="http://www.free-culture.cc/">Free Culture book</a> by the
792 founder of the Creative Commons movement, Lawrence Lessig. A bit less
793 known is the fact that due to the way I created the translations,
794 using docbook and po4a, I also recreated the English original. And
795 because I already had created a new the PDF edition, I published it
796 too. The revenue from the books are sent to the Creative Commons
797 Corporation. In other words, I do not earn any money from this
798 project, I just earn the warm fuzzy feeling that the text is available
799 for a wider audience and more people can learn why the Creative
800 Commons is needed.</p>
801
802 <p>Today, just for fun, I had a look at the sales number over at
803 Lulu.com, which take care of payment, printing and shipping. Much to
804 my surprise, the English edition is selling better than both the
805 French and Norwegian edition, despite the fact that it has been
806 available in English since it was first published. In total, 24 paper
807 books was sold for USD $19.99 between 2016-01-01 and 2016-07-31:</p>
808
809 <table border="0">
810 <tr><th>Title / language</th><th>Quantity</th></tr>
811 <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>
812 <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>
813 <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>
814 </table>
815
816 <p>The books are available both from Lulu.com and from large book
817 stores like Amazon and Barnes&Noble. Most revenue, around $10 per
818 book, is sent to the Creative Commons project when the book is sold
819 directly by Lulu.com. The other channels give less revenue. The
820 summary from Lulu tell me 10 books was sold via the Amazon channel, 10
821 via Ingram (what is this?) and 4 directly by Lulu. And Lulu.com tells
822 me that the revenue sent so far this year is USD $101.42. No idea
823 what kind of sales numbers to expect, so I do not know if that is a
824 good amount of sales for a 10 year old book or not. But it make me
825 happy that the buyers find the book, and I hope they enjoy reading it
826 as much as I did.</p>
827
828 <p>The ebook edition is available for free from
829 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p>
830
831 <p>If you would like to translate and publish the book in your native
832 language, I would be happy to help make it happen. Please get in
833 touch.</p>
834 </div>
835 <div class="tags">
836
837
838 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
839
840
841 </div>
842 </div>
843 <div class="padding"></div>
844
845 <div class="entry">
846 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html">Vitenskapen tar som vanlig feil igjen - relativt feil</a></div>
847 <div class="date"> 1st August 2016</div>
848 <div class="body"><p>For mange år siden leste jeg en klassisk tekst som gjorde såpass
849 inntrykk på meg at jeg husker den fortsatt, flere år senere, og bruker
850 argumentene fra den stadig vekk. Teksten var «The Relativity of
851 Wrong» som Isaac Asimov publiserte i Skeptical Inquirer i 1989. Den
852 gir litt perspektiv rundt formidlingen av vitenskapelige resultater.
853 Jeg har hatt lyst til å kunne dele den også med folk som ikke
854 behersker engelsk så godt, som barn og noen av mine eldre slektninger,
855 og har savnet å ha den tilgjengelig på norsk. For to uker siden tok
856 jeg meg sammen og kontaktet Asbjørn Dyrendal i foreningen Skepsis om
857 de var interessert i å publisere en norsk utgave på bloggen sin, og da
858 han var positiv tok jeg kontakt med Skeptical Inquirer og spurte om
859 det var greit for dem. I løpet av noen dager fikk vi tilbakemelding
860 fra Barry Karr hos The Skeptical Inquirer som hadde sjekket og fått OK
861 fra Robyn Asimov som representerte arvingene i Asmiov-familien og gikk
862 igang med oversettingen.</p>
863
864 <p>Resultatet, <a href="http://www.skepsis.no/?p=1617">«Relativt
865 feil»</a>, ble publisert på skepsis-bloggen for noen minutter siden.
866 Jeg anbefaler deg på det varmeste å lese denne teksten og dele den med
867 dine venner.</p>
868
869 <p>For å håndtere oversettelsen og sikre at original og oversettelse
870 var i sync brukte vi git, po4a, GNU make og Transifex. Det hele
871 fungerte utmerket og gjorde det enkelt å dele tekstene og jobbe sammen
872 om finpuss på formuleringene. Hadde hosted.weblate.org latt meg
873 opprette nye prosjekter selv i stedet for å måtte kontakte
874 administratoren der, så hadde jeg brukt weblate i stedet.</p>
875 </div>
876 <div class="tags">
877
878
879 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis</a>.
880
881
882 </div>
883 </div>
884 <div class="padding"></div>
885
886 <div class="entry">
887 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Techno_TV_broadcasting_live_across_Norway_and_the_Internet___debconf16___nuug__on__frikanalen.html">Techno TV broadcasting live across Norway and the Internet (#debconf16, #nuug) on @frikanalen</a></div>
888 <div class="date"> 1st August 2016</div>
889 <div class="body"><p>Did you know there is a TV channel broadcasting talks from DebConf
890 16 across an entire country? Or that there is a TV channel
891 broadcasting talks by or about
892 <a href="http://beta.frikanalen.no/video/625529/">Linus Torvalds</a>,
893 <a href="http://beta.frikanalen.no/video/625599/">Tor</a>,
894 <a href="http://beta.frikanalen.no/video/624019/">OpenID</A>,
895 <a href="http://beta.frikanalen.no/video/625624/">Common Lisp</a>,
896 <a href="http://beta.frikanalen.no/video/625446/">Civic Tech</a>,
897 <a href="http://beta.frikanalen.no/video/625090/">EFF founder John Barlow</a>,
898 <a href="http://beta.frikanalen.no/video/625432/">how to make 3D
899 printer electronics</a> and many more fascinating topics? It works
900 using only free software (all of it
901 <a href="http://github.com/Frikanalen">available from Github</a>), and
902 is administrated using a web browser and a web API.</p>
903
904 <p>The TV channel is the Norwegian open channel
905 <a href="http://www.frikanalen.no/">Frikanalen</a>, and I am involved
906 via <a href="https://www.nuug.no/">the NUUG member association</a> in
907 running and developing the software for the channel. The channel is
908 organised as a member organisation where its members can upload and
909 broadcast what they want (think of it as Youtube for national
910 broadcasting television). Individuals can broadcast too. The time
911 slots are handled on a first come, first serve basis. Because the
912 channel have almost no viewers and very few active members, we can
913 experiment with TV technology without too much flack when we make
914 mistakes. And thanks to the few active members, most of the slots on
915 the schedule are free. I see this as an opportunity to spread
916 knowledge about technology and free software, and have a script I run
917 regularly to fill up all the open slots the next few days with
918 technology related video. The end result is a channel I like to
919 describe as Techno TV - filled with interesting talks and
920 presentations.</p>
921
922 <p>It is available on channel 50 on the Norwegian national digital TV
923 network (RiksTV). It is also available as a multicast stream on
924 Uninett. And finally, it is available as
925 <a href="http://beta.frikanalen.no/">a WebM unicast stream</a> from
926 Frikanalen and NUUG. Check it out. :)</p>
927 </div>
928 <div class="tags">
929
930
931 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
932
933
934 </div>
935 </div>
936 <div class="padding"></div>
937
938 <p style="text-align: right;"><a href="index.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14" /></a></p>
939 <div id="sidebar">
940
941
942
943 <h2>Archive</h2>
944 <ul>
945
946 <li>2016
947 <ul>
948
949 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
950
951 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
952
953 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
954
955 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
956
957 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
958
959 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
960
961 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
962
963 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
964
965 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
966
967 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
968
969 </ul></li>
970
971 <li>2015
972 <ul>
973
974 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
975
976 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
977
978 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
979
980 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
981
982 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
983
984 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
985
986 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
987
988 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
989
990 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
991
992 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
993
994 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
995
996 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
997
998 </ul></li>
999
1000 <li>2014
1001 <ul>
1002
1003 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
1004
1005 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
1006
1007 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
1008
1009 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
1010
1011 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
1012
1013 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
1014
1015 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
1016
1017 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
1018
1019 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
1020
1021 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
1022
1023 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
1024
1025 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
1026
1027 </ul></li>
1028
1029 <li>2013
1030 <ul>
1031
1032 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1033
1034 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1035
1036 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1037
1038 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1039
1040 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1041
1042 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1043
1044 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1045
1046 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1047
1048 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1049
1050 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1051
1052 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1053
1054 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1055
1056 </ul></li>
1057
1058 <li>2012
1059 <ul>
1060
1061 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1062
1063 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1064
1065 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1066
1067 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1068
1069 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1070
1071 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1072
1073 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
1074
1075 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
1076
1077 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
1078
1079 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
1080
1081 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
1082
1083 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
1084
1085 </ul></li>
1086
1087 <li>2011
1088 <ul>
1089
1090 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1091
1092 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1093
1094 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1095
1096 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1097
1098 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1099
1100 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1101
1102 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1103
1104 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1105
1106 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1107
1108 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1109
1110 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1111
1112 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1113
1114 </ul></li>
1115
1116 <li>2010
1117 <ul>
1118
1119 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1120
1121 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1122
1123 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1124
1125 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1126
1127 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1128
1129 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1130
1131 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1132
1133 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1134
1135 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1136
1137 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1138
1139 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1140
1141 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1142
1143 </ul></li>
1144
1145 <li>2009
1146 <ul>
1147
1148 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1149
1150 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1151
1152 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1153
1154 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1155
1156 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1157
1158 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1159
1160 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1161
1162 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1163
1164 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1165
1166 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1167
1168 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1169
1170 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1171
1172 </ul></li>
1173
1174 <li>2008
1175 <ul>
1176
1177 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1178
1179 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1180
1181 </ul></li>
1182
1183 </ul>
1184
1185
1186
1187 <h2>Tags</h2>
1188 <ul>
1189
1190 <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1191
1192 <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1193
1194 <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1195
1196 <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1197
1198 <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
1199
1200 <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (16)</a></li>
1201
1202 <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1203
1204 <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1205
1206 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (137)</a></li>
1207
1208 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (157)</a></li>
1209
1210 <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1211
1212 <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (16)</a></li>
1213
1214 <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (23)</a></li>
1215
1216 <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1217
1218 <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (329)</a></li>
1219
1220 <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1221
1222 <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1223
1224 <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (28)</a></li>
1225
1226 <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
1227
1228 <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (18)</a></li>
1229
1230 <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
1231
1232 <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
1233
1234 <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (13)</a></li>
1235
1236 <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (19)</a></li>
1237
1238 <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1239
1240 <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
1241
1242 <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
1243
1244 <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1245
1246 <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1247
1248 <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (39)</a></li>
1249
1250 <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (8)</a></li>
1251
1252 <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (279)</a></li>
1253
1254 <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (182)</a></li>
1255
1256 <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (26)</a></li>
1257
1258 <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1259
1260 <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (61)</a></li>
1261
1262 <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (93)</a></li>
1263
1264 <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1265
1266 <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1267
1268 <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1269
1270 <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
1271
1272 <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1273
1274 <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1275
1276 <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1277
1278 <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1279
1280 <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (50)</a></li>
1281
1282 <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1283
1284 <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
1285
1286 <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (49)</a></li>
1287
1288 <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (4)</a></li>
1289
1290 <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (10)</a></li>
1291
1292 <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (41)</a></li>
1293
1294 <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (2)</a></li>
1295
1296 <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1297
1298 <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1299
1300 <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (59)</a></li>
1301
1302 <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1303
1304 <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (38)</a></li>
1305
1306 </ul>
1307
1308
1309 </div>
1310 <p style="text-align: right">
1311 Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1312 </p>
1313
1314 </body>
1315 </html>
Nettsider og blogg.