1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/' xmlns:
atom=
"http://www.w3.org/2005/Atom">
4 <title>Petter Reinholdtsen
</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
7 <atom:link href=
"http://people.skolelinux.org/pere/blog/index.rss" rel=
"self" type=
"application/rss+xml" />
10 <title>Aftenposten-redaktøren med lua i hånda
</title>
11 <link>http://people.skolelinux.org/pere/blog/Aftenposten_redakt_ren_med_lua_i_h_nda.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Aftenposten_redakt_ren_med_lua_i_h_nda.html
</guid>
13 <pubDate>Fri,
9 Sep
2016 11:
30:
00 +
0200</pubDate>
14 <description><p
>En av dagens nyheter er at Aftenpostens redaktør Espen Egil Hansen
16 <a href=
"https://www.nrk.no/kultur/aftenposten-brukar-heile-forsida-pa-facebook-kritikk-
1.13126918">forsiden
17 av papiravisen på et åpent brev til Facebooks sjef Mark Zuckerberg om
18 Facebooks fjerning av bilder, tekster og sider de ikke liker
</a
>. Det
19 må være uvant for redaktøren i avisen Aftenposten å stå med lua i
20 handa og håpe på å bli hørt. Spesielt siden Aftenposten har vært med
21 på å gi Facebook makten de nå demonstrerer at de har. Ved å melde seg
22 inn i Facebook-samfunnet har de sagt ja til bruksvilkårene og inngått
23 en antagelig bindende avtale. Kanskje de skulle lest og vurdert
24 vilkårene litt nærmere før de sa ja, i stedet for å klage over at
25 reglende de har valgt å akseptere blir fulgt? Personlig synes jeg
26 vilkårene er uakseptable og det ville ikke falle meg inn å gå inn på
27 en avtale med slike vilkår. I tillegg til uakseptable vilkår er det
28 mange andre grunner til å unngå Facebook. Du kan finne en solid
29 gjennomgang av flere slike argumenter hos
30 <a href=
"https://stallman.org/facebook.html
">Richard Stallmans side om
33 <p
>Jeg håper flere norske redaktører på samme vis må stå med lua i
34 hånden inntil de forstår at de selv er med på å føre samfunnet på
35 ville veier ved å omfavne Facebook slik de gjør når de omtaler og
36 løfter frem saker fra Facebook, og tar i bruk Facebook som
37 distribusjonskanal for sine nyheter. De bidrar til
38 overvåkningssamfunnet og raderer ut lesernes privatsfære når de lenker
39 til Facebook på sine sider, og låser seg selv inne i en omgivelse der
40 det er Facebook, og ikke redaktøren, som sitter med makta.
</p
>
42 <p
>Men det vil nok ta tid, i et Norge der de fleste nettredaktører
43 <a href=
"http://people.skolelinux.org/pere/blog/Snurpenot_overv_kning_av_sensitiv_personinformasjon.html
">deler
44 sine leseres personopplysinger med utenlands etterretning
</a
>.
</p
>
46 <p
>For øvrig burde varsleren Edward Snowden få politisk asyl i
52 <title>E-tjenesten ber om innsyn i eposten til partiene på Stortinget
</title>
53 <link>http://people.skolelinux.org/pere/blog/E_tjenesten_ber_om_innsyn_i_eposten_til_partiene_p__Stortinget.html
</link>
54 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/E_tjenesten_ber_om_innsyn_i_eposten_til_partiene_p__Stortinget.html
</guid>
55 <pubDate>Tue,
6 Sep
2016 23:
00:
00 +
0200</pubDate>
56 <description><p
>I helga kom det et hårreisende forslag fra Lysne II-utvalget satt
57 ned av Forsvarsdepartementet. Lysne II-utvalget var bedt om å vurdere
58 ønskelista til Forsvarets etterretningstjeneste (e-tjenesten), og har
60 <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
61 om at e-tjenesten skal få lov til a avlytte all Internett-trafikk
</a
>
62 som passerer Norges grenser. Få er klar over at dette innebærer at
63 e-tjenesten får tilgang til epost sendt til de fleste politiske
64 partiene på Stortinget. Regjeringspartiet Høyre (@hoyre.no),
65 støttepartiene Venstre (@venstre.no) og Kristelig Folkeparti (@krf.no)
66 samt Sosialistisk Ventreparti (@sv.no) og Miljøpartiet de grønne
67 (@mdg.no) har nemlig alle valgt å ta imot eposten sin via utenlandske
68 tjenester. Det betyr at hvis noen sender epost til noen med en slik
69 adresse vil innholdet i eposten, om dette forslaget blir vedtatt, gjøres
70 tilgjengelig for e-tjenesten. Venstre, Sosialistisk Ventreparti og
71 Miljøpartiet De Grønne har valgt å motta sin epost hos Google,
72 Kristelig Folkeparti har valgt å motta sin epost hos Microsoft, og
73 Høyre har valgt å motta sin epost hos Comendo med mottak i Danmark og
74 Irland. Kun Arbeiderpartiet og Fremskrittspartiet har valgt å motta
75 eposten sin i Norge, hos henholdsvis Intility AS og Telecomputing
78 <p
>Konsekvensen er at epost inn og ut av de politiske organisasjonene,
79 til og fra partimedlemmer og partiets tillitsvalgte vil gjøres
80 tilgjengelig for e-tjenesten for analyse og sortering. Jeg mistenker
81 at kunnskapen som slik blir tilgjengelig vil være nyttig hvis en
82 ønsker å vite hvilke argumenter som treffer publikum når en ønsker å
83 påvirke Stortingets representanter.
</p
85 <p
>Ved hjelp av MX-oppslag i DNS for epost-domene, tilhørende
86 whois-oppslag av IP-adressene og traceroute for å se hvorvidt
87 trafikken går via utlandet kan enhver få bekreftet at epost sendt til
88 de omtalte partiene vil gjøres tilgjengelig for forsvarets
89 etterretningstjeneste hvis forslaget blir vedtatt. En kan også bruke
90 den kjekke nett-tjenesten
<a href=
"http://ipinfo.io/
">ipinfo.io
</a
>
91 for å få en ide om hvor i verden en IP-adresse hører til.
</p
>
93 <p
>På den positive siden vil forslaget gjøre at enda flere blir
94 motivert til å ta grep for å bruke
95 <a href=
"https://www.torproject.org/
">Tor
</a
> og krypterte
96 kommunikasjonsløsninger for å kommunisere med sine kjære, for å sikre
97 at privatsfæren vernes. Selv bruker jeg blant annet
98 <a href=
"https://www.freedomboxfoundation.org/
">FreedomBox
</a
> og
99 <a href=
"https://whispersystems.org/
">Signal
</a
> til slikt. Ingen av
100 dem er optimale, men de fungerer ganske bra allerede og øker kostnaden
101 for dem som ønsker å invadere mitt privatliv.
</p
>
103 <p
>For øvrig burde varsleren Edward Snowden få politisk asyl i
109 venstre.no mail is handled by
10 aspmx.l.google.com.
110 venstre.no mail is handled by
20 alt1.aspmx.l.google.com.
111 venstre.no mail is handled by
20 alt2.aspmx.l.google.com.
112 venstre.no mail is handled by
30 aspmx2.googlemail.com.
113 venstre.no mail is handled by
30 aspmx3.googlemail.com.
115 traceroute to aspmx.l.google.com (
173.194.222.27),
30 hops max,
60 byte packets
116 1 uio-gw10.uio.no (
129.240.6.1)
0.411 ms
0.438 ms
0.536 ms
117 2 uio-gw8.uio.no (
129.240.24.229)
0.375 ms
0.452 ms
0.548 ms
118 3 oslo-gw1.uninett.no (
128.39.65.17)
1.940 ms
1.950 ms
1.942 ms
119 4 se-tug.nordu.net (
109.105.102.108)
6.910 ms
6.949 ms
7.283 ms
120 5 google-gw.nordu.net (
109.105.98.6)
6.975 ms
6.967 ms
6.958 ms
121 6 209.85.250.192 (
209.85.250.192)
7.337 ms
7.286 ms
10.890 ms
122 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
123 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
124 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
128 mdg.no mail is handled by
1 aspmx.l.google.com.
129 mdg.no mail is handled by
5 alt2.aspmx.l.google.com.
130 mdg.no mail is handled by
5 alt1.aspmx.l.google.com.
131 mdg.no mail is handled by
10 aspmx2.googlemail.com.
132 mdg.no mail is handled by
10 aspmx3.googlemail.com.
134 sv.no mail is handled by
1 aspmx.l.google.com.
135 sv.no mail is handled by
5 alt1.aspmx.l.google.com.
136 sv.no mail is handled by
5 alt2.aspmx.l.google.com.
137 sv.no mail is handled by
10 aspmx3.googlemail.com.
138 sv.no mail is handled by
10 aspmx2.googlemail.com.
140 hoyre.no mail is handled by
10 hoyre-no.mx1.comendosystems.com.
141 hoyre.no mail is handled by
20 hoyre-no.mx2.comendosystems.net.
143 traceroute to hoyre-no.mx1.comendosystems.com (
89.104.206.4),
30 hops max,
60 byte packets
144 1 uio-gw10.uio.no (
129.240.6.1)
0.450 ms
0.510 ms
0.591 ms
145 2 uio-gw8.uio.no (
129.240.24.229)
0.383 ms
0.508 ms
0.596 ms
146 3 oslo-gw1.uninett.no (
128.39.65.17)
0.311 ms
0.315 ms
0.300 ms
147 4 se-tug.nordu.net (
109.105.102.108)
6.837 ms
6.842 ms
6.834 ms
148 5 dk-uni.nordu.net (
109.105.97.10)
26.073 ms
26.085 ms
26.076 ms
149 6 dix
.1000m.soeborg.ip.comendo.dk (
192.38.7.22)
15.372 ms
15.046 ms
15.123 ms
150 7 89.104.192.65 (
89.104.192.65)
15.875 ms
15.990 ms
16.239 ms
151 8 89.104.192.179 (
89.104.192.179)
15.676 ms
15.674 ms
15.664 ms
152 9 03dm-com.mx1.staysecuregroup.com (
89.104.206.4)
15.637 ms * *
155 krf.no mail is handled by
10 krf-no.mail.protection.outlook.com.
157 traceroute to krf-no.mail.protection.outlook.com (
213.199.154.42),
30 hops max,
60 byte packets
158 1 uio-gw10.uio.no (
129.240.6.1)
0.401 ms
0.438 ms
0.536 ms
159 2 uio-gw8.uio.no (
129.240.24.229)
11.076 ms
11.120 ms
11.204 ms
160 3 oslo-gw1.uninett.no (
128.39.65.17)
0.232 ms
0.234 ms
0.271 ms
161 4 se-tug.nordu.net (
109.105.102.108)
6.811 ms
6.820 ms
6.815 ms
162 5 netnod-ix-ge-a-sth-
4470.microsoft.com (
195.245.240.181)
7.074 ms
7.013 ms
7.061 ms
163 6 ae1-
0.sto-
96cbe-
1b.ntwk.msn.net (
104.44.225.161)
7.227 ms
7.362 ms
7.293 ms
164 7 be-
8-
0.ibr01.ams.ntwk.msn.net (
104.44.5.7)
41.993 ms
43.334 ms
41.939 ms
165 8 be-
1-
0.ibr02.ams.ntwk.msn.net (
104.44.4.214)
43.153 ms
43.507 ms
43.404 ms
166 9 ae3-
0.fra-
96cbe-
1b.ntwk.msn.net (
104.44.5.17)
29.897 ms
29.831 ms
29.794 ms
167 10 ae10-
0.vie-
96cbe-
1a.ntwk.msn.net (
198.206.164.1)
42.309 ms
42.130 ms
41.808 ms
168 11 * ae8-
0.vie-
96cbe-
1b.ntwk.msn.net (
104.44.227.29)
41.425 ms *
172 arbeiderpartiet.no mail is handled by
10 mail.intility.com.
173 arbeiderpartiet.no mail is handled by
20 mail2.intility.com.
175 traceroute to mail.intility.com (
188.95.245.87),
30 hops max,
60 byte packets
176 1 uio-gw10.uio.no (
129.240.6.1)
0.486 ms
0.508 ms
0.649 ms
177 2 uio-gw8.uio.no (
129.240.24.229)
0.416 ms
0.508 ms
0.620 ms
178 3 oslo-gw1.uninett.no (
128.39.65.17)
0.276 ms
0.278 ms
0.275 ms
179 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
0.374 ms
0.371 ms
0.416 ms
180 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
181 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
182 7 cD2EC45C1.static.as2116.net (
193.69.236.210)
0.654 ms
0.615 ms
0.590 ms
183 8 185.7.132.38 (
185.7.132.38)
1.661 ms
1.808 ms
1.695 ms
184 9 185.7.132.100 (
185.7.132.100)
1.793 ms
1.943 ms
1.546 ms
188 frp.no mail is handled by
10 mx03.telecomputing.no.
189 frp.no mail is handled by
20 mx01.telecomputing.no.
191 traceroute to mx03.telecomputing.no (
95.128.105.102),
30 hops max,
60 byte packets
192 1 uio-gw10.uio.no (
129.240.6.1)
0.378 ms
0.402 ms
0.479 ms
193 2 uio-gw8.uio.no (
129.240.24.229)
0.361 ms
0.458 ms
0.548 ms
194 3 oslo-gw1.uninett.no (
128.39.65.17)
0.361 ms
0.352 ms
0.336 ms
195 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
196 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
197 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
198 7 95.128.105.3 (
95.128.105.3)
1.050 ms
1.288 ms
1.182 ms
199 8 mx03.telecomputing.no (
95.128.105.102)
0.717 ms
0.703 ms
0.692 ms
206 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
207 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
208 <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>
209 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
210 <description><p
>In April we
211 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
212 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
213 how to set up and administrate a Debian system. Today I am happy to
214 report that the first draft is now publicly available. You can find
215 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
216 Administrator
's Handbook page
</a
> (under Other languages). The first
217 eight chapters have a first draft translation, and we are working on
218 proofreading the content. If you want to help out, please start
220 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
221 hosted weblate project page
</a
>, and get in touch using
222 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
223 translators mailing list
</a
>. Please also check out
224 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
225 contributors
</a
>. A good way to contribute is to proofread the text
226 and update weblate if you find errors.
</p
>
228 <p
>Our goal is still to make the Norwegian book available on paper as well as
229 electronic form.
</p
>
234 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
235 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
236 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
237 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
238 <description><p
>This summer, I read a great article
239 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
240 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
241 how to profile multi-threaded programs. It presented a system for
242 profiling software by running experiences in the running program,
243 testing how run time performance is affected by
"speeding up
" parts of
244 the code to various degrees compared to a normal run. It does this by
245 slowing down parallel threads while the
"faster up
" code is running
246 and measure how this affect processing time. The processing time is
247 measured using probes inserted into the code, either using progress
248 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
249 can also measure unmodified code by measuring complete the program
250 runtime and running the program several times instead.
</p
>
252 <p
>The project and presentation was so inspiring that I would like to
253 get the system into Debian. I
254 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
255 a WNPP request for it
</a
> and contacted upstream to try to make the
256 system ready for Debian by sending patches. The build process need to
257 be changed a bit to avoid running
'git clone
' to get dependencies, and
258 to include the JavaScript web page used to visualize the collected
259 profiling information included in the source package.
260 But I expect that should work out fairly soon.
</p
>
262 <p
>The way the system work is fairly simple. To run an coz experiment
263 on a binary with debug symbols available, start the program like this:
265 <p
><blockquote
><pre
>
266 coz run --- program-to-run
267 </pre
></blockquote
></p
>
269 <p
>This will create a text file profile.coz with the instrumentation
270 information. To show what part of the code affect the performance
271 most, use a web browser and either point it to
272 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
273 or use the copy from git (in the gh-pages branch). Check out this web
274 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
275 profiling more useful you include
&lt;coz.h
&gt; and insert the
276 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
277 code, rebuild and run the profiler. This allow coz to do more
278 targeted experiments.
</p
>
280 <p
>A video published by ACM
281 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
282 Coz profiler
</a
> is available from Youtube. There is also a paper
283 from the
25th Symposium on Operating Systems Principles available
285 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
286 finding code that counts with causal profiling
</a
>.
</p
>
288 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
289 for Coz is available from github. It will only build with clang
291 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
292 feature missing in GCC
</a
>, but I
've submitted
293 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
294 it
</a
> and hope it will be included in the upstream source soon.
</p
>
296 <p
>Please get in touch if you, like me, would like to see this piece
297 of software in Debian. I would very much like some help with the
298 packaging effort, as I lack the in depth knowledge on how to package
299 C++ libraries.
</p
>
304 <title>Sales number for the Free Culture translation, first half of
2016</title>
305 <link>http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html
</link>
306 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html
</guid>
307 <pubDate>Fri,
5 Aug
2016 22:
45:
00 +
0200</pubDate>
308 <description><p
>As my regular readers probably remember, the last year I published
309 a French and Norwegian translation of the classic
310 <a href=
"http://www.free-culture.cc/
">Free Culture book
</a
> by the
311 founder of the Creative Commons movement, Lawrence Lessig. A bit less
312 known is the fact that due to the way I created the translations,
313 using docbook and po4a, I also recreated the English original. And
314 because I already had created a new the PDF edition, I published it
315 too. The revenue from the books are sent to the Creative Commons
316 Corporation. In other words, I do not earn any money from this
317 project, I just earn the warm fuzzy feeling that the text is available
318 for a wider audience and more people can learn why the Creative
319 Commons is needed.
</p
>
321 <p
>Today, just for fun, I had a look at the sales number over at
322 Lulu.com, which take care of payment, printing and shipping. Much to
323 my surprise, the English edition is selling better than both the
324 French and Norwegian edition, despite the fact that it has been
325 available in English since it was first published. In total,
24 paper
326 books was sold for USD $
19.99 between
2016-
01-
01 and
2016-
07-
31:
</p
>
328 <table border=
"0">
329 <tr
><th
>Title / language
</th
><th
>Quantity
</th
></tr
>
330 <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
>
331 <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
>
332 <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
>
335 <p
>The books are available both from Lulu.com and from large book
336 stores like Amazon and Barnes
&Noble. Most revenue, around $
10 per
337 book, is sent to the Creative Commons project when the book is sold
338 directly by Lulu.com. The other channels give less revenue. The
339 summary from Lulu tell me
10 books was sold via the Amazon channel,
10
340 via Ingram (what is this?) and
4 directly by Lulu. And Lulu.com tells
341 me that the revenue sent so far this year is USD $
101.42. No idea
342 what kind of sales numbers to expect, so I do not know if that is a
343 good amount of sales for a
10 year old book or not. But it make me
344 happy that the buyers find the book, and I hope they enjoy reading it
345 as much as I did.
</p
>
347 <p
>The ebook edition is available for free from
348 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Github
</a
>.
</p
>
350 <p
>If you would like to translate and publish the book in your native
351 language, I would be happy to help make it happen. Please get in
357 <title>Vitenskapen tar som vanlig feil igjen - relativt feil
</title>
358 <link>http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html
</link>
359 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html
</guid>
360 <pubDate>Mon,
1 Aug
2016 16:
00:
00 +
0200</pubDate>
361 <description><p
>For mange år siden leste jeg en klassisk tekst som gjorde såpass
362 inntrykk på meg at jeg husker den fortsatt, flere år senere, og bruker
363 argumentene fra den stadig vekk. Teksten var «The Relativity of
364 Wrong» som Isaac Asimov publiserte i Skeptical Inquirer i
1989. Den
365 gir litt perspektiv rundt formidlingen av vitenskapelige resultater.
366 Jeg har hatt lyst til å kunne dele den også med folk som ikke
367 behersker engelsk så godt, som barn og noen av mine eldre slektninger,
368 og har savnet å ha den tilgjengelig på norsk. For to uker siden tok
369 jeg meg sammen og kontaktet Asbjørn Dyrendal i foreningen Skepsis om
370 de var interessert i å publisere en norsk utgave på bloggen sin, og da
371 han var positiv tok jeg kontakt med Skeptical Inquirer og spurte om
372 det var greit for dem. I løpet av noen dager fikk vi tilbakemelding
373 fra Barry Karr hos The Skeptical Inquirer som hadde sjekket og fått OK
374 fra Robyn Asimov som representerte arvingene i Asmiov-familien og gikk
375 igang med oversettingen.
</p
>
377 <p
>Resultatet,
<a href=
"http://www.skepsis.no/?p=
1617">«Relativt
378 feil»
</a
>, ble publisert på skepsis-bloggen for noen minutter siden.
379 Jeg anbefaler deg på det varmeste å lese denne teksten og dele den med
380 dine venner.
</p
>
382 <p
>For å håndtere oversettelsen og sikre at original og oversettelse
383 var i sync brukte vi git, po4a, GNU make og Transifex. Det hele
384 fungerte utmerket og gjorde det enkelt å dele tekstene og jobbe sammen
385 om finpuss på formuleringene. Hadde hosted.weblate.org latt meg
386 opprette nye prosjekter selv i stedet for å måtte kontakte
387 administratoren der, så hadde jeg brukt weblate i stedet.
</p
>
392 <title>Techno TV broadcasting live across Norway and the Internet (#debconf16, #nuug) on @frikanalen
</title>
393 <link>http://people.skolelinux.org/pere/blog/Techno_TV_broadcasting_live_across_Norway_and_the_Internet___debconf16___nuug__on__frikanalen.html
</link>
394 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Techno_TV_broadcasting_live_across_Norway_and_the_Internet___debconf16___nuug__on__frikanalen.html
</guid>
395 <pubDate>Mon,
1 Aug
2016 10:
30:
00 +
0200</pubDate>
396 <description><p
>Did you know there is a TV channel broadcasting talks from DebConf
397 16 across an entire country? Or that there is a TV channel
398 broadcasting talks by or about
399 <a href=
"http://beta.frikanalen.no/video/
625529/
">Linus Torvalds
</a
>,
400 <a href=
"http://beta.frikanalen.no/video/
625599/
">Tor
</a
>,
401 <a href=
"http://beta.frikanalen.no/video/
624019/
">OpenID
</A
>,
402 <a href=
"http://beta.frikanalen.no/video/
625624/
">Common Lisp
</a
>,
403 <a href=
"http://beta.frikanalen.no/video/
625446/
">Civic Tech
</a
>,
404 <a href=
"http://beta.frikanalen.no/video/
625090/
">EFF founder John Barlow
</a
>,
405 <a href=
"http://beta.frikanalen.no/video/
625432/
">how to make
3D
406 printer electronics
</a
> and many more fascinating topics? It works
407 using only free software (all of it
408 <a href=
"http://github.com/Frikanalen
">available from Github
</a
>), and
409 is administrated using a web browser and a web API.
</p
>
411 <p
>The TV channel is the Norwegian open channel
412 <a href=
"http://www.frikanalen.no/
">Frikanalen
</a
>, and I am involved
413 via
<a href=
"https://www.nuug.no/
">the NUUG member association
</a
> in
414 running and developing the software for the channel. The channel is
415 organised as a member organisation where its members can upload and
416 broadcast what they want (think of it as Youtube for national
417 broadcasting television). Individuals can broadcast too. The time
418 slots are handled on a first come, first serve basis. Because the
419 channel have almost no viewers and very few active members, we can
420 experiment with TV technology without too much flack when we make
421 mistakes. And thanks to the few active members, most of the slots on
422 the schedule are free. I see this as an opportunity to spread
423 knowledge about technology and free software, and have a script I run
424 regularly to fill up all the open slots the next few days with
425 technology related video. The end result is a channel I like to
426 describe as Techno TV - filled with interesting talks and
427 presentations.
</p
>
429 <p
>It is available on channel
50 on the Norwegian national digital TV
430 network (RiksTV). It is also available as a multicast stream on
431 Uninett. And finally, it is available as
432 <a href=
"http://beta.frikanalen.no/
">a WebM unicast stream
</a
> from
433 Frikanalen and NUUG. Check it out. :)
</p
>
438 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
439 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
440 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
441 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
442 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
443 to be a slight challenge. Here is the recipe if I ever need to do it
444 again. It all started by me wanting to try the recipe to set up
445 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
446 hardened Android installation
</a
> from the Tor project blog on a
447 device I had access to. It is a old mobile phone with a broken
448 microphone The initial idea had been to just
449 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
450 CyanogenMod on it
</a
>, but did not quite find time to start on it
451 until a few days ago.
</p
>
453 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
454 loader (press volume down and power at the same time), (
2) select
455 'fastboot
' before (
3) connecting the device via USB to a Linux
456 machine, (
4) request the device identifier token by running
'fastboot
457 oem get_identifier_token
', (
5) request the device unlocking key using
458 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
459 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
461 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
462 or newer, and the device I was working on had
2.00.0027. This
463 apparently can be easily fixed by downloading a Windows program and
464 running it on your Windows machine, if you accept the terms Microsoft
465 require you to accept to use Windows - which I do not. So I had to
466 come up with a different approach. I got a lot of help from AndyCap
467 on #nuug, and would not have been able to get this working without
470 <p
>First I needed to extract the hboot firmware from
471 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
472 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
473 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
474 project named unruu
</a
> using libunshield. The unshield tool did not
475 recognise the file format, but unruu worked and extracted rom.zip,
476 containing the new hboot firmware and a text file describing which
477 devices it would work for.
</p
>
479 <p
>Next, I needed to get the new firmware into the device. For this I
480 followed some instructions
481 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
482 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
483 machine with Debian testing:
</p
>
486 adb reboot-bootloader
487 fastboot oem rebootRUU
488 fastboot flash zip rom.zip
489 fastboot flash zip rom.zip
491 </pre
></p
>
493 <p
>The flash command apparently need to be done twice to take effect,
494 as the first is just preparations and the second one do the flashing.
495 The adb command is just to get to the boot loader menu, so turning the
496 device on while holding volume down and the power button should work
499 <p
>With the new hboot version in place I could start following the
500 instructions on the HTC developer web site. I got the device token
504 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
507 <p
>And once I got the unlock code via email, I could use it like
511 fastboot flash unlocktoken Unlock_code.bin
512 </pre
></p
>
514 <p
>And with that final step in place, the phone was unlocked and I
515 could start stuffing the software of my own choosing into the device.
516 So far I only inserted a replacement recovery image to wipe the phone
517 before I start. We will see what happen next. Perhaps I should
518 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
523 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
524 <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</link>
525 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</guid>
526 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
527 <description><p
>For a while now, I have wanted to test
528 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
529 said to provide end to end encrypted communication and several of my
530 friends and family are already using it. As I by choice do not own a
531 mobile phone, this proved to be harder than expected. And I wanted to
532 have the source of the client and know that it was the code used on my
533 machine. But yesterday I managed to get it working. I used the
534 Github source, compared it to the source in
535 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
536 Signal Chrome app
</a
> available from the Chrome web store, applied
537 patches to use the production Signal servers, started the app and
538 asked for the hidden
"register without a smart phone
" form. Here is
539 the recipe how I did it.
</p
>
541 <p
>First, I fetched the Signal desktop source from Github, using
544 git clone https://github.com/WhisperSystems/Signal-Desktop.git
547 <p
>Next, I patched the source to use the production servers, to be
548 able to talk to other Signal users:
</p
>
551 cat
&lt;
&lt;EOF | patch -p0
552 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
553 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
554 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
559 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
560 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
561 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
562 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
564 window.getSocketStatus = function() {
565 if (messageReceiver) {
566 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
567 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
568 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
571 'use strict
';
572 - var BUILD_EXPIRATION =
0;
573 + var BUILD_EXPIRATION =
1474492690000;
575 window.extension = window.extension || {};
580 <p
>The first part is changing the servers, and the second is updating
581 an expiration timestamp. This timestamp need to be updated regularly.
582 It is set
90 days in the future by the build process (Gruntfile.js).
583 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
585 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
586 script to launch Signal in Chromium.
</p
>
593 --proxy-server=
"socks://localhost:
9050" \
594 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
597 <p
> The script start the app and configure Chromium to use the Tor
598 SOCKS5 proxy to make sure those controlling the Signal servers (today
599 Amazon and Whisper Systems) as well as those listening on the lines
600 will have a harder time location my laptop based on the Signal
601 connections if they use source IP address.
</p
>
603 <p
>When the script starts, one need to follow the instructions under
604 "Standalone Registration
" in the CONTRIBUTING.md file in the git
605 repository. I right clicked on the Signal window to get up the
606 Chromium debugging tool, visited the
'Console
' tab and wrote
607 'extension.install(
"standalone
")
' on the console prompt to get the
608 registration form. Then I entered by land line phone number and
609 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
610 repeated the verification code three times. After entering the number
611 into the verification code field in the form, I could start using
612 Signal from my laptop.
614 <p
>As far as I can tell, The Signal app will leak who is talking to
615 whom and thus who know who to those controlling the central server,
616 but such leakage is hard to avoid with a centrally controlled server
617 setup. It is something to keep in mind when using Signal - the
618 content of your chats are harder to intercept, but the meta data
619 exposing your contact network is available to people you do not know.
620 So better than many options, but not great. And sadly the usage is
621 connected to my land line, thus allowing those controlling the server
622 to associate it to my home and person. I would prefer it if only
623 those I knew could tell who I was on Signal. There are options
624 avoiding such information leakage, but most of my friends are not
625 using them, so I am stuck with Signal for now.
</p
>
630 <title>The new
"best
" multimedia player in Debian?
</title>
631 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
632 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
633 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
634 <description><p
>When I set out a few weeks ago to figure out
635 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
636 multimedia player in Debian claimed to support most file formats /
637 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
638 the various players claimed support for. The range was from
55 to
130
639 MIME types. I suspect most media formats are supported by all
640 players, but this is not really reflected in the MimeTypes values in
641 their desktop files. There are probably also some bogus MIME types
642 listed, but it is hard to identify which one this is.
</p
>
644 <p
>Anyway, in the mean time I got in touch with upstream for some of
645 the players suggesting to add more MIME types to their desktop files,
646 and decided to spend some time myself improving the situation for my
647 favorite media player VLC. The fixes for VLC entered Debian unstable
648 yesterday. The complete list of MIME types can be seen on the
649 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
650 player MIME type support status
</a
> Debian wiki page.
</p
>
652 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
653 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
654 kmplayer. I am sure some of the other players desktop files support
655 several of the formats currently listed as working only with vlc,
656 toten and parole.
</p
>
658 <p
>A sad observation is that only
14 MIME types are listed as
659 supported by all the tested multimedia players in Debian in their
660 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
661 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
662 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
663 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
664 it sad that video/ogg and video/webm is not supported by all the media
665 players in Debian. As far as I can tell, all of them can handle both
projects / homepage.git / blob