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>Locating IMDB IDs of movies in the Internet Archive using Wikidata
</title>
11 <link>http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html
</guid>
13 <pubDate>Wed,
25 Oct
2017 12:
20:
00 +
0200</pubDate>
14 <description><p
>Recently, I needed to automatically check the copyright status of a
15 set of
<a href=
"http://www.imdb.com/
">The Internet Movie database
16 (IMDB)
</a
> entries, to figure out which one of the movies they refer
17 to can be freely distributed on the Internet. This proved to be
18 harder than it sounds. IMDB for sure list movies without any
19 copyright protection, where the copyright protection has expired or
20 where the movie is lisenced using a permissive license like one from
21 Creative Commons. These are mixed with copyright protected movies,
22 and there seem to be no way to separate these classes of movies using
23 the information in IMDB.
</p
>
25 <p
>First I tried to look up entries manually in IMDB,
26 <a href=
"https://www.wikipedia.org/
">Wikipedia
</a
> and
27 <a href=
"https://www.archive.org/
">The Internet Archive
</a
>, to get a
28 feel how to do this. It is hard to know for sure using these sources,
29 but it should be possible to be reasonable confident a movie is
"out
30 of copyright
" with a few hours work per movie. As I needed to check
31 almost
20,
000 entries, this approach was not sustainable. I simply
32 can not work around the clock for about
6 years to check this data
35 <p
>I asked the people behind The Internet Archive if they could
36 introduce a new metadata field in their metadata XML for IMDB ID, but
37 was told that they leave it completely to the uploaders to update the
38 metadata. Some of the metadata entries had IMDB links in the
39 description, but I found no way to download all metadata files in bulk
40 to locate those ones and put that approach aside.
</p
>
42 <p
>In the process I noticed several Wikipedia articles about movies
43 had links to both IMDB and The Internet Archive, and it occured to me
44 that I could use the Wikipedia RDF data set to locate entries with
45 both, to at least get a lower bound on the number of movies on The
46 Internet Archive with a IMDB ID. This is useful based on the
47 assumption that movies distributed by The Internet Archive can be
48 legally distributed on the Internet. With some help from the RDF
49 community (thank you DanC), I was able to come up with this query to
50 pass to
<a href=
"https://query.wikidata.org/
">the SPARQL interface on
54 SELECT ?work ?imdb ?ia ?when ?label
57 ?work wdt:P31/wdt:P279* wd:Q11424.
62 ?work rdfs:label ?label.
63 FILTER(LANG(?label) =
"en
").
66 </pre
></p
>
68 <p
>If I understand the query right, for every film entry anywhere in
69 Wikpedia, it will return the IMDB ID and The Internet Archive ID, and
70 when the movie was released and its English title, if either or both
71 of the latter two are available. At the moment the result set contain
72 2338 entries. Of course, it depend on volunteers including both
73 correct IMDB and The Internet Archive IDs in the wikipedia articles
74 for the movie. It should be noted that the result will include
75 duplicates if the movie have entries in several languages. There are
76 some bogus entries, either because The Internet Archive ID contain a
77 typo or because the movie is not available from The Internet Archive.
78 I did not verify the IMDB IDs, as I am unsure how to do that
79 automatically.
</p
>
81 <p
>I wrote a small python script to extract the data set from Wikidata
82 and check if the XML metadata for the movie is available from The
83 Internet Archive, and after around
1.5 hour it produced a list of
2097
84 free movies and their IMDB ID. In total,
171 entries in Wikidata lack
85 the refered Internet Archive entry. I assume the
60 "disappearing
"
86 entries (ie
2338-
2097-
171) are duplicate entries.
</p
>
88 <p
>This is not too bad, given that The Internet Archive report to
89 contain
<a href=
"https://archive.org/details/feature_films
">5331
90 feature films
</a
> at the moment, but it also mean more than
3000
91 movies are missing on Wikipedia or are missing the pair of references
92 on Wikipedia.
</p
>
94 <p
>I was curious about the distribution by release year, and made a
95 little graph to show how the amount of free movies is spread over the
98 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2017-
10-
25-verk-i-det-fri-filmer.png
"></p
>
100 <p
>I expect the relative distribution of the remaining
3000 movies to
101 be similar.
</p
>
103 <p
>If you want to help, and want to ensure Wikipedia can be used to
104 cross reference The Internet Archive and The Internet Movie Database,
105 please make sure entries like this are listed under the
"External
106 links
" heading on the Wikipedia article for the movie:
</p
>
109 * {{Internet Archive film|id=FightingLady}}
110 * {{IMDb title|id=
0036823|title=The Fighting Lady}}
111 </pre
></p
>
113 <p
>Please verify the links on the final page, to make sure you did not
114 introduce a typo.
</p
>
116 <p
>Here is the complete list, if you want to correct the
171
117 identified Wikipedia entries with broken links to The Internet
118 Archive:
<a href=
"http://www.wikidata.org/entity/Q1140317
">Q1140317
</a
>,
119 <a href=
"http://www.wikidata.org/entity/Q458656
">Q458656
</a
>,
120 <a href=
"http://www.wikidata.org/entity/Q458656
">Q458656
</a
>,
121 <a href=
"http://www.wikidata.org/entity/Q470560
">Q470560
</a
>,
122 <a href=
"http://www.wikidata.org/entity/Q743340
">Q743340
</a
>,
123 <a href=
"http://www.wikidata.org/entity/Q822580
">Q822580
</a
>,
124 <a href=
"http://www.wikidata.org/entity/Q480696
">Q480696
</a
>,
125 <a href=
"http://www.wikidata.org/entity/Q128761
">Q128761
</a
>,
126 <a href=
"http://www.wikidata.org/entity/Q1307059
">Q1307059
</a
>,
127 <a href=
"http://www.wikidata.org/entity/Q1335091
">Q1335091
</a
>,
128 <a href=
"http://www.wikidata.org/entity/Q1537166
">Q1537166
</a
>,
129 <a href=
"http://www.wikidata.org/entity/Q1438334
">Q1438334
</a
>,
130 <a href=
"http://www.wikidata.org/entity/Q1479751
">Q1479751
</a
>,
131 <a href=
"http://www.wikidata.org/entity/Q1497200
">Q1497200
</a
>,
132 <a href=
"http://www.wikidata.org/entity/Q1498122
">Q1498122
</a
>,
133 <a href=
"http://www.wikidata.org/entity/Q865973
">Q865973
</a
>,
134 <a href=
"http://www.wikidata.org/entity/Q834269
">Q834269
</a
>,
135 <a href=
"http://www.wikidata.org/entity/Q841781
">Q841781
</a
>,
136 <a href=
"http://www.wikidata.org/entity/Q841781
">Q841781
</a
>,
137 <a href=
"http://www.wikidata.org/entity/Q1548193
">Q1548193
</a
>,
138 <a href=
"http://www.wikidata.org/entity/Q499031
">Q499031
</a
>,
139 <a href=
"http://www.wikidata.org/entity/Q1564769
">Q1564769
</a
>,
140 <a href=
"http://www.wikidata.org/entity/Q1585239
">Q1585239
</a
>,
141 <a href=
"http://www.wikidata.org/entity/Q1585569
">Q1585569
</a
>,
142 <a href=
"http://www.wikidata.org/entity/Q1624236
">Q1624236
</a
>,
143 <a href=
"http://www.wikidata.org/entity/Q4796595
">Q4796595
</a
>,
144 <a href=
"http://www.wikidata.org/entity/Q4853469
">Q4853469
</a
>,
145 <a href=
"http://www.wikidata.org/entity/Q4873046
">Q4873046
</a
>,
146 <a href=
"http://www.wikidata.org/entity/Q915016
">Q915016
</a
>,
147 <a href=
"http://www.wikidata.org/entity/Q4660396
">Q4660396
</a
>,
148 <a href=
"http://www.wikidata.org/entity/Q4677708
">Q4677708
</a
>,
149 <a href=
"http://www.wikidata.org/entity/Q4738449
">Q4738449
</a
>,
150 <a href=
"http://www.wikidata.org/entity/Q4756096
">Q4756096
</a
>,
151 <a href=
"http://www.wikidata.org/entity/Q4766785
">Q4766785
</a
>,
152 <a href=
"http://www.wikidata.org/entity/Q880357
">Q880357
</a
>,
153 <a href=
"http://www.wikidata.org/entity/Q882066
">Q882066
</a
>,
154 <a href=
"http://www.wikidata.org/entity/Q882066
">Q882066
</a
>,
155 <a href=
"http://www.wikidata.org/entity/Q204191
">Q204191
</a
>,
156 <a href=
"http://www.wikidata.org/entity/Q204191
">Q204191
</a
>,
157 <a href=
"http://www.wikidata.org/entity/Q1194170
">Q1194170
</a
>,
158 <a href=
"http://www.wikidata.org/entity/Q940014
">Q940014
</a
>,
159 <a href=
"http://www.wikidata.org/entity/Q946863
">Q946863
</a
>,
160 <a href=
"http://www.wikidata.org/entity/Q172837
">Q172837
</a
>,
161 <a href=
"http://www.wikidata.org/entity/Q573077
">Q573077
</a
>,
162 <a href=
"http://www.wikidata.org/entity/Q1219005
">Q1219005
</a
>,
163 <a href=
"http://www.wikidata.org/entity/Q1219599
">Q1219599
</a
>,
164 <a href=
"http://www.wikidata.org/entity/Q1643798
">Q1643798
</a
>,
165 <a href=
"http://www.wikidata.org/entity/Q1656352
">Q1656352
</a
>,
166 <a href=
"http://www.wikidata.org/entity/Q1659549
">Q1659549
</a
>,
167 <a href=
"http://www.wikidata.org/entity/Q1660007
">Q1660007
</a
>,
168 <a href=
"http://www.wikidata.org/entity/Q1698154
">Q1698154
</a
>,
169 <a href=
"http://www.wikidata.org/entity/Q1737980
">Q1737980
</a
>,
170 <a href=
"http://www.wikidata.org/entity/Q1877284
">Q1877284
</a
>,
171 <a href=
"http://www.wikidata.org/entity/Q1199354
">Q1199354
</a
>,
172 <a href=
"http://www.wikidata.org/entity/Q1199354
">Q1199354
</a
>,
173 <a href=
"http://www.wikidata.org/entity/Q1199451
">Q1199451
</a
>,
174 <a href=
"http://www.wikidata.org/entity/Q1211871
">Q1211871
</a
>,
175 <a href=
"http://www.wikidata.org/entity/Q1212179
">Q1212179
</a
>,
176 <a href=
"http://www.wikidata.org/entity/Q1238382
">Q1238382
</a
>,
177 <a href=
"http://www.wikidata.org/entity/Q4906454
">Q4906454
</a
>,
178 <a href=
"http://www.wikidata.org/entity/Q320219
">Q320219
</a
>,
179 <a href=
"http://www.wikidata.org/entity/Q1148649
">Q1148649
</a
>,
180 <a href=
"http://www.wikidata.org/entity/Q645094
">Q645094
</a
>,
181 <a href=
"http://www.wikidata.org/entity/Q5050350
">Q5050350
</a
>,
182 <a href=
"http://www.wikidata.org/entity/Q5166548
">Q5166548
</a
>,
183 <a href=
"http://www.wikidata.org/entity/Q2677926
">Q2677926
</a
>,
184 <a href=
"http://www.wikidata.org/entity/Q2698139
">Q2698139
</a
>,
185 <a href=
"http://www.wikidata.org/entity/Q2707305
">Q2707305
</a
>,
186 <a href=
"http://www.wikidata.org/entity/Q2740725
">Q2740725
</a
>,
187 <a href=
"http://www.wikidata.org/entity/Q2024780
">Q2024780
</a
>,
188 <a href=
"http://www.wikidata.org/entity/Q2117418
">Q2117418
</a
>,
189 <a href=
"http://www.wikidata.org/entity/Q2138984
">Q2138984
</a
>,
190 <a href=
"http://www.wikidata.org/entity/Q1127992
">Q1127992
</a
>,
191 <a href=
"http://www.wikidata.org/entity/Q1058087
">Q1058087
</a
>,
192 <a href=
"http://www.wikidata.org/entity/Q1070484
">Q1070484
</a
>,
193 <a href=
"http://www.wikidata.org/entity/Q1080080
">Q1080080
</a
>,
194 <a href=
"http://www.wikidata.org/entity/Q1090813
">Q1090813
</a
>,
195 <a href=
"http://www.wikidata.org/entity/Q1251918
">Q1251918
</a
>,
196 <a href=
"http://www.wikidata.org/entity/Q1254110
">Q1254110
</a
>,
197 <a href=
"http://www.wikidata.org/entity/Q1257070
">Q1257070
</a
>,
198 <a href=
"http://www.wikidata.org/entity/Q1257079
">Q1257079
</a
>,
199 <a href=
"http://www.wikidata.org/entity/Q1197410
">Q1197410
</a
>,
200 <a href=
"http://www.wikidata.org/entity/Q1198423
">Q1198423
</a
>,
201 <a href=
"http://www.wikidata.org/entity/Q706951
">Q706951
</a
>,
202 <a href=
"http://www.wikidata.org/entity/Q723239
">Q723239
</a
>,
203 <a href=
"http://www.wikidata.org/entity/Q2079261
">Q2079261
</a
>,
204 <a href=
"http://www.wikidata.org/entity/Q1171364
">Q1171364
</a
>,
205 <a href=
"http://www.wikidata.org/entity/Q617858
">Q617858
</a
>,
206 <a href=
"http://www.wikidata.org/entity/Q5166611
">Q5166611
</a
>,
207 <a href=
"http://www.wikidata.org/entity/Q5166611
">Q5166611
</a
>,
208 <a href=
"http://www.wikidata.org/entity/Q324513
">Q324513
</a
>,
209 <a href=
"http://www.wikidata.org/entity/Q374172
">Q374172
</a
>,
210 <a href=
"http://www.wikidata.org/entity/Q7533269
">Q7533269
</a
>,
211 <a href=
"http://www.wikidata.org/entity/Q970386
">Q970386
</a
>,
212 <a href=
"http://www.wikidata.org/entity/Q976849
">Q976849
</a
>,
213 <a href=
"http://www.wikidata.org/entity/Q7458614
">Q7458614
</a
>,
214 <a href=
"http://www.wikidata.org/entity/Q5347416
">Q5347416
</a
>,
215 <a href=
"http://www.wikidata.org/entity/Q5460005
">Q5460005
</a
>,
216 <a href=
"http://www.wikidata.org/entity/Q5463392
">Q5463392
</a
>,
217 <a href=
"http://www.wikidata.org/entity/Q3038555
">Q3038555
</a
>,
218 <a href=
"http://www.wikidata.org/entity/Q5288458
">Q5288458
</a
>,
219 <a href=
"http://www.wikidata.org/entity/Q2346516
">Q2346516
</a
>,
220 <a href=
"http://www.wikidata.org/entity/Q5183645
">Q5183645
</a
>,
221 <a href=
"http://www.wikidata.org/entity/Q5185497
">Q5185497
</a
>,
222 <a href=
"http://www.wikidata.org/entity/Q5216127
">Q5216127
</a
>,
223 <a href=
"http://www.wikidata.org/entity/Q5223127
">Q5223127
</a
>,
224 <a href=
"http://www.wikidata.org/entity/Q5261159
">Q5261159
</a
>,
225 <a href=
"http://www.wikidata.org/entity/Q1300759
">Q1300759
</a
>,
226 <a href=
"http://www.wikidata.org/entity/Q5521241
">Q5521241
</a
>,
227 <a href=
"http://www.wikidata.org/entity/Q7733434
">Q7733434
</a
>,
228 <a href=
"http://www.wikidata.org/entity/Q7736264
">Q7736264
</a
>,
229 <a href=
"http://www.wikidata.org/entity/Q7737032
">Q7737032
</a
>,
230 <a href=
"http://www.wikidata.org/entity/Q7882671
">Q7882671
</a
>,
231 <a href=
"http://www.wikidata.org/entity/Q7719427
">Q7719427
</a
>,
232 <a href=
"http://www.wikidata.org/entity/Q7719444
">Q7719444
</a
>,
233 <a href=
"http://www.wikidata.org/entity/Q7722575
">Q7722575
</a
>,
234 <a href=
"http://www.wikidata.org/entity/Q2629763
">Q2629763
</a
>,
235 <a href=
"http://www.wikidata.org/entity/Q2640346
">Q2640346
</a
>,
236 <a href=
"http://www.wikidata.org/entity/Q2649671
">Q2649671
</a
>,
237 <a href=
"http://www.wikidata.org/entity/Q7703851
">Q7703851
</a
>,
238 <a href=
"http://www.wikidata.org/entity/Q7747041
">Q7747041
</a
>,
239 <a href=
"http://www.wikidata.org/entity/Q6544949
">Q6544949
</a
>,
240 <a href=
"http://www.wikidata.org/entity/Q6672759
">Q6672759
</a
>,
241 <a href=
"http://www.wikidata.org/entity/Q2445896
">Q2445896
</a
>,
242 <a href=
"http://www.wikidata.org/entity/Q12124891
">Q12124891
</a
>,
243 <a href=
"http://www.wikidata.org/entity/Q3127044
">Q3127044
</a
>,
244 <a href=
"http://www.wikidata.org/entity/Q2511262
">Q2511262
</a
>,
245 <a href=
"http://www.wikidata.org/entity/Q2517672
">Q2517672
</a
>,
246 <a href=
"http://www.wikidata.org/entity/Q2543165
">Q2543165
</a
>,
247 <a href=
"http://www.wikidata.org/entity/Q426628
">Q426628
</a
>,
248 <a href=
"http://www.wikidata.org/entity/Q426628
">Q426628
</a
>,
249 <a href=
"http://www.wikidata.org/entity/Q12126890
">Q12126890
</a
>,
250 <a href=
"http://www.wikidata.org/entity/Q13359969
">Q13359969
</a
>,
251 <a href=
"http://www.wikidata.org/entity/Q13359969
">Q13359969
</a
>,
252 <a href=
"http://www.wikidata.org/entity/Q2294295
">Q2294295
</a
>,
253 <a href=
"http://www.wikidata.org/entity/Q2294295
">Q2294295
</a
>,
254 <a href=
"http://www.wikidata.org/entity/Q2559509
">Q2559509
</a
>,
255 <a href=
"http://www.wikidata.org/entity/Q2559912
">Q2559912
</a
>,
256 <a href=
"http://www.wikidata.org/entity/Q7760469
">Q7760469
</a
>,
257 <a href=
"http://www.wikidata.org/entity/Q6703974
">Q6703974
</a
>,
258 <a href=
"http://www.wikidata.org/entity/Q4744
">Q4744
</a
>,
259 <a href=
"http://www.wikidata.org/entity/Q7766962
">Q7766962
</a
>,
260 <a href=
"http://www.wikidata.org/entity/Q7768516
">Q7768516
</a
>,
261 <a href=
"http://www.wikidata.org/entity/Q7769205
">Q7769205
</a
>,
262 <a href=
"http://www.wikidata.org/entity/Q7769988
">Q7769988
</a
>,
263 <a href=
"http://www.wikidata.org/entity/Q2946945
">Q2946945
</a
>,
264 <a href=
"http://www.wikidata.org/entity/Q3212086
">Q3212086
</a
>,
265 <a href=
"http://www.wikidata.org/entity/Q3212086
">Q3212086
</a
>,
266 <a href=
"http://www.wikidata.org/entity/Q18218448
">Q18218448
</a
>,
267 <a href=
"http://www.wikidata.org/entity/Q18218448
">Q18218448
</a
>,
268 <a href=
"http://www.wikidata.org/entity/Q18218448
">Q18218448
</a
>,
269 <a href=
"http://www.wikidata.org/entity/Q6909175
">Q6909175
</a
>,
270 <a href=
"http://www.wikidata.org/entity/Q7405709
">Q7405709
</a
>,
271 <a href=
"http://www.wikidata.org/entity/Q7416149
">Q7416149
</a
>,
272 <a href=
"http://www.wikidata.org/entity/Q7239952
">Q7239952
</a
>,
273 <a href=
"http://www.wikidata.org/entity/Q7317332
">Q7317332
</a
>,
274 <a href=
"http://www.wikidata.org/entity/Q7783674
">Q7783674
</a
>,
275 <a href=
"http://www.wikidata.org/entity/Q7783704
">Q7783704
</a
>,
276 <a href=
"http://www.wikidata.org/entity/Q7857590
">Q7857590
</a
>,
277 <a href=
"http://www.wikidata.org/entity/Q3372526
">Q3372526
</a
>,
278 <a href=
"http://www.wikidata.org/entity/Q3372642
">Q3372642
</a
>,
279 <a href=
"http://www.wikidata.org/entity/Q3372816
">Q3372816
</a
>,
280 <a href=
"http://www.wikidata.org/entity/Q3372909
">Q3372909
</a
>,
281 <a href=
"http://www.wikidata.org/entity/Q7959649
">Q7959649
</a
>,
282 <a href=
"http://www.wikidata.org/entity/Q7977485
">Q7977485
</a
>,
283 <a href=
"http://www.wikidata.org/entity/Q7992684
">Q7992684
</a
>,
284 <a href=
"http://www.wikidata.org/entity/Q3817966
">Q3817966
</a
>,
285 <a href=
"http://www.wikidata.org/entity/Q3821852
">Q3821852
</a
>,
286 <a href=
"http://www.wikidata.org/entity/Q3420907
">Q3420907
</a
>,
287 <a href=
"http://www.wikidata.org/entity/Q3429733
">Q3429733
</a
>,
288 <a href=
"http://www.wikidata.org/entity/Q774474
">Q774474
</a
></p
>
293 <title>A one-way wall on the border?
</title>
294 <link>http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html
</link>
295 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html
</guid>
296 <pubDate>Sat,
14 Oct
2017 22:
10:
00 +
0200</pubDate>
297 <description><p
>I find it fascinating how many of the people being locked inside
298 the proposed border wall between USA and Mexico support the idea. The
299 proposal to keep Mexicans out reminds me of
300 <a href=
"http://www.history.com/news/
10-things-you-may-not-know-about-the-berlin-wall
">the
301 propaganda twist from the East Germany government
</a
> calling the wall
302 the “Antifascist Bulwark” after erecting the Berlin Wall, claiming
303 that the wall was erected to keep enemies from creeping into East
304 Germany, while it was obvious to the people locked inside it that it
305 was erected to keep the people from escaping.
</p
>
307 <p
>Do the people in USA supporting this wall really believe it is a
308 one way wall, only keeping people on the outside from getting in,
309 while not keeping people in the inside from getting out?
</p
>
314 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
315 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
316 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
317 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
318 <description><p
>At my nearby maker space,
319 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
320 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
321 on Windows and MacOS X than Linux, because the software involved had
322 to be manually compiled and set up on Linux while premade packages
323 worked out of the box on Windows and MacOS X. I found this annoying,
324 as the software involved,
325 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
326 and should be trivial to get up and running on Linux if someone took
327 the time to package it for the relevant distributions. I even found
328 <a href=
"https://bugs.debian.org/
706656">a request for adding into
329 Debian
</a
> from
2013, which had seem some activity over the years but
330 never resulted in the software showing up in Debian. So a few days
331 ago I offered my help to try to improve the situation.
</p
>
333 <p
>Now I am very happy to see that all the packages required by a
334 working Cura in Debian are uploaded into Debian and waiting in the NEW
335 queue for the ftpmasters to have a look. You can track the progress
337 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
338 status page for the
3D printer team
</a
>.
</p
>
340 <p
>The uploaded packages are a bit behind upstream, and was uploaded
341 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
342 queue
</a
> while we work up updating the packages to the latest
343 upstream version.
</p
>
345 <p
>On a related note, two competitors for Cura, which I found harder
346 to use and was unable to configure correctly for Ultimaker
2+ in the
347 short time I spent on it, are already in Debian. If you are looking
348 for
3D printer
"slicers
" and want something already available in
350 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
351 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
352 The latter is a fork of the former.
</p
>
357 <title>Mangler du en skrue, eller har du en skrue løs?
</title>
358 <link>http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html
</link>
359 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html
</guid>
360 <pubDate>Wed,
4 Oct
2017 09:
40:
00 +
0200</pubDate>
361 <description>Når jeg holder på med ulike prosjekter, så trenger jeg stadig ulike
362 skruer. Det siste prosjektet jeg holder på med er å lage
363 <a href=
"https://www.thingiverse.com/thing:
676916">en boks til en
364 HDMI-touch-skjerm
</a
> som skal brukes med Raspberry Pi. Boksen settes
365 sammen med skruer og bolter, og jeg har vært i tvil om hvor jeg kan
366 få tak i de riktige skruene. Clas Ohlson og Jernia i nærheten har
367 sjelden hatt det jeg trenger. Men her om dagen fikk jeg et fantastisk
368 tips for oss som bor i Oslo.
369 <a href=
"http://www.zachskruer.no/
">Zachariassen Jernvare AS
</a
> i
370 <a href=
"http://www.openstreetmap.org/?mlat=
59.93421&mlon=
10.76795#map=
19/
59.93421/
10.76795">Hegermannsgate
371 23A på Torshov
</a
> har et fantastisk utvalg, og åpent mellom
09:
00 og
372 17:
00. De selger skruer, muttere, bolter, skiver etc i løs vekt, og
373 så langt har jeg fått alt jeg har lett etter. De har i tillegg det
374 meste av annen jernvare, som verktøy, lamper, ledninger, etc. Jeg
375 håper de har nok kunder til å holde det gående lenge, da dette er en
376 butikk jeg kommer til å besøke ofte. Butikken er et funn å ha i
377 nabolaget for oss som liker å bygge litt selv. :)
</p
>
382 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
383 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
384 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
385 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
386 <description><p
>Every mobile phone announce its existence over radio to the nearby
387 mobile cell towers. And this radio chatter is available for anyone
388 with a radio receiver capable of receiving them. Details about the
389 mobile phones with very good accuracy is of course collected by the
390 phone companies, but this is not the topic of this blog post. The
391 mobile phone radio chatter make it possible to figure out when a cell
392 phone is nearby, as it include the SIM card ID (IMSI). By paying
393 attention over time, one can see when a phone arrive and when it leave
394 an area. I believe it would be nice to make this information more
395 available to the general public, to make more people aware of how
396 their phones are announcing their whereabouts to anyone that care to
399 <p
>I am very happy to report that we managed to get something
400 visualizing this information up and running for
401 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
402 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
403 library. The solution is based on the
404 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
405 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
406 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
407 Sone from the Computer Science department of the University of
408 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
409 IMSIs) as dots in a web browser graph, with lines to the dot
410 representing mobile base station it is talking to. It was working in
411 the lab yesterday, and was moved into place this morning.
</p
>
413 <p
>We set up a fairly powerful desktop machine using Debian
414 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
415 connected and visualize the visible cell phone towers using an
416 <a href=
"https://github.com/marlow925/hopglass
">English version of
417 Hopglass
</a
>. A fairly powerfull machine is needed as the
418 grgsm_livemon_headless processes from
419 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
420 the radio signal to data packages is quite CPU intensive.
</p
>
422 <p
>The frequencies to listen to, are identified using a slightly
423 patched scan-and-livemon (to set the --args values for each receiver),
424 and the Hopglass data is generated using the
425 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
426 in my meshviewer-output branch
</a
>. For some reason we could not get
427 more than four SDRs working. There is also a geographical map trying
428 to show the location of the base stations, but I believe their
429 coordinates are hardcoded to some random location in Germany, I
430 believe. The code should be replaced with code to look up location in
431 a text file, a sqlite database or one of the online databases
433 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
434 issue for the topic
</a
>.
436 <p
>If this sound interesting, visit the stand at the festival!
</p
>
441 <title>Easier recipe to observe the cell phones around you
</title>
442 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
443 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
444 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
445 <description><p
>A little more than a month ago I wrote
446 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
447 to observe the SIM card ID (aka IMSI number) of mobile phones talking
448 to nearby mobile phone base stations using Debian GNU/Linux and a
449 cheap USB software defined radio
</a
>, and thus being able to pinpoint
450 the location of people and equipment (like cars and trains) with an
451 accuracy of a few kilometer. Since then we have worked to make the
452 procedure even simpler, and it is now possible to do this without any
453 manual frequency tuning and without building your own packages.
</p
>
455 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
456 package is now included in Debian testing and unstable, and the
457 IMSI-catcher code no longer require root access to fetch and decode
458 the GSM data collected using gr-gsm.
</p
>
460 <p
>Here is an updated recipe, using packages built by Debian and a git
461 clone of two python scripts:
</p
>
465 <li
>Start with a Debian machine running the Buster version (aka
468 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
469 python-scapy
</tt
>' as root to install required packages.
</li
>
471 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
472 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
474 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
476 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
477 scan-and-livemon
</tt
>' to locate the frequency of nearby base
478 stations and start listening for GSM packages on one of them.
</li
>
480 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
481 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
485 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
486 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
487 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
488 work with RTL
8232 and other similar USB radio receivers you can get
490 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
491 from ebay
</a
>), so for now the solution is to scan using the RTL radio
492 and only use HackRF for fetching GSM data.
</p
>
494 <p
>As far as I can tell, a cell phone only show up on one of the
495 frequencies at the time, so if you are going to track and count every
496 cell phone around you, you need to listen to all the frequencies used.
497 To listen to several frequencies, use the --numrecv argument to
498 scan-and-livemon to use several receivers. Further, I am not sure if
499 phones using
3G or
4G will show as talking GSM to base stations, so
500 this approach might not see all phones around you. I typically see
501 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
503 <p
>I
've tried to run the scanner on a
504 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
505 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
506 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
507 stdout, I am told there it is caused by a buffer overflow between the
508 radio and GNU Radio, caused by the program being unable to read the
509 GSM data fast enough. If you see a stream of
'O
's from the terminal
510 where you started scan-and-livemon, you need a give the process more
511 CPU power. Perhaps someone are able to optimize the code to a point
512 where it become possible to set up RPi3 based GSM sniffers? I tried
513 using Raspbian instead of Debian, but there seem to be something wrong
514 with GNU Radio on raspbian, causing glibc to abort().
</p
>
519 <title>Datalagringsdirektivet kaster skygger over Høyre og Arbeiderpartiet
</title>
520 <link>http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html
</link>
521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html
</guid>
522 <pubDate>Thu,
7 Sep
2017 21:
35:
00 +
0200</pubDate>
523 <description><p
>For noen dager siden publiserte Jon Wessel-Aas en bloggpost om
524 «
<a href=
"http://www.uhuru.biz/?p=
1821">Konklusjonen om datalagring som
525 EU-kommisjonen ikke ville at vi skulle få se
</a
>». Det er en
526 interessant gjennomgang av EU-domstolens syn på snurpenotovervåkning
527 av befolkningen, som er klar på at det er i strid med
528 EU-lovgivingen.
</p
>
530 <p
>Valgkampen går for fullt i Norge, og om noen få dager er siste
531 frist for å avgi stemme. En ting er sikkert, Høyre og Arbeiderpartiet
533 <a href=
"http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_gj_r_at_Oslo_H_yre_og_Arbeiderparti_ikke_f_r_min_stemme_i__r.html
">denne
534 gangen heller
</a
>. Jeg har ikke glemt at de tvang igjennom loven som
535 skulle pålegge alle data- og teletjenesteleverandører å overvåke alle
536 sine kunder. En lov som er vedtatt, og aldri opphevet igjen.
</p
>
538 <p
>Det er tydelig fra diskusjonen rundt grenseløs digital overvåkning
539 (eller
"Digital Grenseforsvar
" som det kalles i Orvellisk nytale) at
540 hverken Høyre og Arbeiderpartiet har noen prinsipielle sperrer mot å
541 overvåke hele befolkningen, og diskusjonen så langt tyder på at flere
542 av de andre partiene heller ikke har det. Mange av
543 <a href=
"https://data.holderdeord.no/votes/
1301946411e
">de som stemte
544 for Datalagringsdirektivet i Stortinget
</a
> (
64 fra Arbeiderpartiet,
545 25 fra Høyre) er fortsatt aktive og argumenterer fortsatt for å radere
546 vekk mer av innbyggernes privatsfære.
</p
>
548 <p
>Når myndighetene demonstrerer sin mistillit til folket, tror jeg
549 folket selv bør legge litt innsats i å verne sitt privatliv, ved å ta
550 i bruk ende-til-ende-kryptert kommunikasjon med sine kjente og kjære,
551 og begrense hvor mye privat informasjon som deles med uvedkommende.
552 Det er jo ingenting som tyder på at myndighetene kommer til å være vår
554 <a href=
"http://people.skolelinux.org/pere/blog/How_to_talk_with_your_loved_ones_in_private.html
">Det
555 er mange muligheter
</a
>. Selv har jeg litt sans for
556 <a href=
"https://ring.cx/
">Ring
</a
>, som er basert på p2p-teknologi
557 uten sentral kontroll, er fri programvare, og støtter meldinger, tale
558 og video. Systemet er tilgjengelig ut av boksen fra
559 <a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> og
560 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, og det
561 finnes pakker for Android, MacOSX og Windows. Foreløpig er det få
562 brukere med Ring, slik at jeg også bruker
563 <a href=
"https://signal.org/
">Signal
</a
> som nettleserutvidelse.
</p
>
568 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
569 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
570 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
571 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
572 <description><p
>On friday, I came across an interesting article in the Norwegian
573 web based ICT news magazine digi.no on
574 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
575 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
576 DVB-T software defined radios. The article refered to instructions
577 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
578 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
580 <p
>The instructions said to use Ubuntu, install pip using apt (to
581 bypass apt), use pip to install pybombs (to bypass both apt and pip),
582 and the ask pybombs to fetch and build everything you need from
583 scratch. I wanted to see if I could do the same on the most recent
584 Debian packages, but this did not work because pybombs tried to build
585 stuff that no longer build with the most recent openssl library or
586 some other version skew problem. While trying to get this recipe
587 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
588 and the only piece of software dependency missing in Debian was the
589 gr-gsm package. I also found out that the lead upstream developer of
590 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
591 Debian packages provided in an Ubuntu PPA repository. All I needed to
592 do was to dget the Debian source package and built it.
</p
>
594 <p
>The IMSI collector is a python script listening for packages on the
595 loopback network device and printing to the terminal some specific GSM
596 packages with IMSI numbers in them. The code is fairly short and easy
597 to understand. The reason this work is because gr-gsm include a tool
598 to read GSM data from a software defined radio like a DVB-T USB stick
599 and other software defined radios, decode them and inject them into a
600 network device on your Linux machine (using the loopback device by
601 default). This proved to work just fine, and I
've been testing the
602 collector for a few days now.
</p
>
604 <p
>The updated and simpler recipe is thus to
</p
>
608 <li
>start with a Debian machine running Stretch or newer,
</li
>
610 <li
>build and install the gr-gsm package available from
611 <a href=
"http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
">http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
</a
>,
</li
>
613 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
615 <li
>run grgsm_livemon and adjust the frequency until the terminal
616 where it was started is filled with a stream of text (meaning you
617 found a GSM station).
</li
>
619 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
623 <p
>To make it even easier in the future to get this sniffer up and
624 running, I decided to package
625 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
626 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
627 #
871055</a
>), and the package was uploaded into the NEW queue today.
628 Luckily the gnuradio maintainer has promised to help me, as I do not
629 know much about gnuradio stuff yet.
</p
>
631 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
632 commercial tools like
633 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
634 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
635 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
636 Stingray
</a
>, but I hope the existance of cheap alternatives can make
637 more people realise how their whereabouts when carrying a cell phone
638 is easily tracked. Seeing the data flow on the screen, realizing that
639 I live close to a police station and knowing that the police is also
640 wearing cell phones, I wonder how hard it would be for criminals to
641 track the position of the police officers to discover when there are
642 police near by, or for foreign military forces to track the location
643 of the Norwegian military forces, or for anyone to track the location
644 of government officials...
</p
>
646 <p
>It is worth noting that the data reported by the IMSI-catcher
647 script mentioned above is only a fraction of the data broadcasted on
648 the GSM network. It will only collect one frequency at the time,
649 while a typical phone will be using several frequencies, and not all
650 phones will be using the frequencies tracked by the grgsm_livemod
651 program. Also, there is a lot of radio chatter being ignored by the
652 simple_IMSI-catcher script, which would be collected by extending the
653 parser code. I wonder if gr-gsm can be set up to listen to more than
654 one frequency?
</p
>
659 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
660 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
661 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
662 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
663 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
665 <p
>I finally received a copy of the Norwegian Bokmål edition of
666 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
667 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
668 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
669 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
670 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
671 price. The book is also available for download in electronic form as
672 PDF, EPUB and Mobipocket, as can be
673 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
674 as a web page
</a
>.
</p
>
676 <p
>This is the second book I publish (the first was the book
677 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
679 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
680 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
682 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
683 Bokmål
</a
>), and I am very excited to finally wrap up this
685 "<a href=
"http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-
23262290.html
">Håndbok
686 for Debian-administratoren
</a
>" will be well received.
</p
>
691 <title>«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig integritet»
</title>
692 <link>http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html
</link>
693 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html
</guid>
694 <pubDate>Tue,
27 Jun
2017 17:
50:
00 +
0200</pubDate>
695 <description><p
>Jeg kom over teksten
696 «
<a href=
"https://freedom-to-tinker.com/
2017/
06/
21/killing-car-privacy-by-federal-mandate/
">Killing
697 car privacy by federal mandate
</a
>» av Leonid Reyzin på Freedom to
698 Tinker i dag, og det gleder meg å se en god gjennomgang om hvorfor det
699 er et urimelig inngrep i privatsfæren å la alle biler kringkaste sin
700 posisjon og bevegelse via radio. Det omtalte forslaget basert på
701 Dedicated Short Range Communication (DSRC) kalles Basic Safety Message
702 (BSM) i USA og Cooperative Awareness Message (CAM) i Europa, og det
703 norske Vegvesenet er en av de som ser ut til å kunne tenke seg å
704 pålegge alle biler å fjerne nok en bit av innbyggernes privatsfære.
705 Anbefaler alle å lese det som står der.
707 <p
>Mens jeg tittet litt på DSRC på biler i Norge kom jeg over et sitat
708 jeg synes er illustrativt for hvordan det offentlige Norge håndterer
709 problemstillinger rundt innbyggernes privatsfære i SINTEF-rapporten
710 «
<a href=
"https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933
">Informasjonssikkerhet
711 i AutoPASS-brikker
</a
>» av Trond Foss:
</p
>
713 <p
><blockquote
>
714 «Rapporten ser ikke på informasjonssikkerhet knyttet til personlig
716 </blockquote
></p
>
718 <p
>Så enkelt kan det tydeligvis gjøres når en vurderer
719 informasjonssikkerheten. Det holder vel at folkene på toppen kan si
720 at «Personvernet er ivaretatt», som jo er den populære intetsigende
721 frasen som gjør at mange tror enkeltindividers integritet tas vare på.
722 Sitatet fikk meg til å undres på hvor ofte samme tilnærming, å bare se
723 bort fra behovet for personlig itegritet, blir valgt når en velger å
724 legge til rette for nok et inngrep i privatsfæren til personer i
725 Norge. Det er jo sjelden det får reaksjoner. Historien om
726 reaksjonene på Helse Sør-Østs tjenesteutsetting er jo sørgelig nok et
727 unntak og toppen av isfjellet, desverre. Tror jeg fortsatt takker nei
728 til både AutoPASS og holder meg så langt unna det norske helsevesenet
729 som jeg kan, inntil de har demonstrert og dokumentert at de verdsetter
730 individets privatsfære og personlige integritet høyere enn kortsiktig
731 gevist og samfunnsnytte.
</p
>
projects / homepage.git / blob