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>Is the short movie «Empty Socks» from
1927 in the public domain or not?
</title>
11 <link>http://people.skolelinux.org/pere/blog/Is_the_short_movie__Empty_Socks__from_1927_in_the_public_domain_or_not_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Is_the_short_movie__Empty_Socks__from_1927_in_the_public_domain_or_not_.html
</guid>
13 <pubDate>Tue,
5 Dec
2017 12:
30:
00 +
0100</pubDate>
14 <description><p
>Three years ago, a presumed lost animation film,
15 <a href=
"https://en.wikipedia.org/wiki/Empty_Socks
">Empty Socks from
16 1927</a
>, was discovered in the Norwegian National Library. At the
17 time it was discovered, it was generally assumed to be copyrighted by
18 The Walt Disney Company, and I blogged about
19 <a href=
"http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html
">my
20 reasoning to conclude
</a
> that it would would enter the Norwegian
21 equivalent of the public domain in
2053, based on my understanding of
22 Norwegian Copyright Law. But a few days ago, I came across
23 <a href=
"http://www.toonzone.net/forums/threads/exposed-disneys-repurchase-of-oswald-the-rabbit-a-sham
.4792291/
">a
24 blog post claiming the movie was already in the public domain
</a
>, at
25 least in USA. The reasoning is as follows: The film was released in
26 November or Desember
1927 (sources disagree), and presumably
27 registered its copyright that year. At that time, right holders of
28 movies registered by the copyright office received government
29 protection for there work for
28 years. After
28 years, the copyright
30 had to be renewed if the wanted the government to protect it further.
31 The blog post I found claim such renewal did not happen for this
32 movie, and thus it entered the public domain in
1956. Yet someone
33 claim the copyright was renewed and the movie is still copyright
34 protected. Can anyone help me to figure out which claim is correct?
35 I have not been able to find Empty Socks in Catalog of copyright
36 entries. Ser
.3 pt
.12-
13 v
.9-
12 1955-
1958 Motion Pictures
37 <a href=
"http://onlinebooks.library.upenn.edu/cce/
1955r.html#film
">available
38 from the University of Pennsylvania
</a
>, neither in
39 <a href=
"https://babel.hathitrust.org/cgi/pt?id=mdp
.39015084451130;page=root;view=image;size=
100;seq=
83;num=
45">page
40 45 for the first half of
1955</a
>, nor in
41 <a href=
"https://babel.hathitrust.org/cgi/pt?id=mdp
.39015084451130;page=root;view=image;size=
100;seq=
175;num=
119">page
42 119 for the second half of
1955</a
>. It is of course possible that
43 the renewal entry was left out of the printed catalog by mistake. Is
44 there some way to rule out this possibility? Please help, and update
45 the wikipedia page with your findings.
47 <p
>As usual, if you use Bitcoin and want to show your support of my
48 activities, please send Bitcoin donations to my address
49 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
54 <title>Metadata proposal for movies on the Internet Archive
</title>
55 <link>http://people.skolelinux.org/pere/blog/Metadata_proposal_for_movies_on_the_Internet_Archive.html
</link>
56 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Metadata_proposal_for_movies_on_the_Internet_Archive.html
</guid>
57 <pubDate>Tue,
28 Nov
2017 12:
00:
00 +
0100</pubDate>
58 <description><p
>It would be easier to locate the movie you want to watch in
59 <a href=
"https://www.archive.org/
">the Internet Archive
</a
>, if the
60 metadata about each movie was more complete and accurate. In the
61 archiving community, a well known saying state that good metadata is a
62 love letter to the future. The metadata in the Internet Archive could
63 use a face lift for the future to love us back. Here is a proposal
64 for a small improvement that would make the metadata more useful
65 today. I
've been unable to find any document describing the various
66 standard fields available when uploading videos to the archive, so
67 this proposal is based on my best quess and searching through several
68 of the existing movies.
</p
>
70 <p
>I have a few use cases in mind. First of all, I would like to be
71 able to count the number of distinct movies in the Internet Archive,
72 without duplicates. I would further like to identify the IMDB title
73 ID of the movies in the Internet Archive, to be able to look up a IMDB
74 title ID and know if I can fetch the video from there and share it
75 with my friends.
</p
>
77 <p
>Second, I would like the Butter data provider for The Internet
79 (
<a href=
"https://github.com/butterproviders/butter-provider-archive
">available
80 from github
</a
>), to list as many of the good movies as possible. The
81 plugin currently do a search in the archive with the following
85 collection:moviesandfilms
86 AND NOT collection:movie_trailers
87 AND -mediatype:collection
88 AND format:
"Archive BitTorrent
"
90 </pre
></p
>
92 <p
>Most of the cool movies that fail to show up in Butter do so
93 because the
'year
' field is missing. The
'year
' field is populated by
94 the year part from the
'date
' field, and should be when the movie was
95 released (date or year). Two such examples are
96 <a href=
"https://archive.org/details/SidneyOlcottsBen-hur1905
">Ben Hur
97 from
1905</a
> and
98 <a href=
"https://archive.org/details/Caminandes2GranDillama
">Caminandes
99 2: Gran Dillama from
2013</a
>, where the year metadata field is
102 So, my proposal is simply, for every movie in The Internet Archive
103 where an IMDB title ID exist, please fill in these metadata fields
104 (note, they can be updated also long after the video was uploaded, but
105 as far as I can tell, only by the uploader):
109 <dt
>mediatype
</dt
>
110 <dd
>Should be
'movie
' for movies.
</dd
>
112 <dt
>collection
</dt
>
113 <dd
>Should contain
'moviesandfilms
'.
</dd
>
115 <dt
>title
</dt
>
116 <dd
>The title of the movie, without the publication year.
</dd
>
118 <dt
>date
</dt
>
119 <dd
>The data or year the movie was released. This make the movie show
120 up in Butter, as well as make it possible to know the age of the
121 movie and is useful to figure out copyright status.
</dd
>
123 <dt
>director
</dt
>
124 <dd
>The director of the movie. This make it easier to know if the
125 correct movie is found in movie databases.
</dd
>
127 <dt
>publisher
</dt
>
128 <dd
>The production company making the movie. Also useful for
129 identifying the correct movie.
</dd
>
131 <dt
>links
</dt
>
133 <dd
>Add a link to the IMDB title page, for example like this:
&lt;a
134 href=
"http://www.imdb.com/title/tt0028496/
"&gt;Movie in
135 IMDB
&lt;/a
&gt;. This make it easier to find duplicates and allow for
136 counting of number of unique movies in the Archive. Other external
137 references, like to TMDB, could be added like this too.
</dd
>
141 <p
>I did consider proposing a Custom field for the IMDB title ID (for
142 example
'imdb_title_url
',
'imdb_code
' or simply
'imdb
', but suspect it
143 will be easier to simply place it in the links free text field.
</p
>
146 <a href=
"https://github.com/petterreinholdtsen/public-domain-free-imdb
">a
147 list of IMDB title IDs for several thousand movies in the Internet
148 Archive
</a
>, but I also got a list of several thousand movies without
149 such IMDB title ID (and quite a few duplicates). It would be great if
150 this data set could be integrated into the Internet Archive metadata
151 to be available for everyone in the future, but with the current
152 policy of leaving metadata editing to the uploaders, it will take a
153 while before this happen. If you have uploaded movies into the
154 Internet Archive, you can help. Please consider following my proposal
155 above for your movies, to ensure that movie is properly
156 counted. :)
</p
>
158 <p
>The list is mostly generated using wikidata, which based on
159 Wikipedia articles make it possible to link between IMDB and movies in
160 the Internet Archive. But there are lots of movies without a
161 Wikipedia article, and some movies where only a collection page exist
162 (like for
<a href=
"https://en.wikipedia.org/wiki/Caminandes
">the
163 Caminandes example above
</a
>, where there are three movies but only
164 one Wikidata entry).
</p
>
166 <p
>As usual, if you use Bitcoin and want to show your support of my
167 activities, please send Bitcoin donations to my address
168 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
173 <title>Legal to share more than
3000 movies listed on IMDB?
</title>
174 <link>http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html
</link>
175 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html
</guid>
176 <pubDate>Sat,
18 Nov
2017 21:
20:
00 +
0100</pubDate>
177 <description><p
>A month ago, I blogged about my work to
178 <a href=
"http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html
">automatically
179 check the copyright status of IMDB entries
</a
>, and try to count the
180 number of movies listed in IMDB that is legal to distribute on the
181 Internet. I have continued to look for good data sources, and
182 identified a few more. The code used to extract information from
183 various data sources is available in
184 <a href=
"https://github.com/petterreinholdtsen/public-domain-free-imdb
">a
185 git repository
</a
>, currently available from github.
</p
>
187 <p
>So far I have identified
3186 unique IMDB title IDs. To gain
188 better understanding of the structure of the data set, I created a
189 histogram of the year associated with each movie (typically release
190 year). It is interesting to notice where the peaks and dips in the
191 graph are located. I wonder why they are placed there. I suspect
192 World War II caused the dip around
1940, but what caused the peak
193 around
2010?
</p
>
195 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2017-
11-
18-verk-i-det-fri-filmer.png
" /
></p
>
197 <p
>I
've so far identified ten sources for IMDB title IDs for movies in
198 the public domain or with a free license. This is the statistics
199 reported when running
'make stats
' in the git repository:
</p
>
202 249 entries (
6 unique) with and
288 without IMDB title ID in free-movies-archive-org-butter.json
203 2301 entries (
540 unique) with and
0 without IMDB title ID in free-movies-archive-org-wikidata.json
204 830 entries (
29 unique) with and
0 without IMDB title ID in free-movies-icheckmovies-archive-mochard.json
205 2109 entries (
377 unique) with and
0 without IMDB title ID in free-movies-imdb-pd.json
206 291 entries (
122 unique) with and
0 without IMDB title ID in free-movies-letterboxd-pd.json
207 144 entries (
135 unique) with and
0 without IMDB title ID in free-movies-manual.json
208 350 entries (
1 unique) with and
801 without IMDB title ID in free-movies-publicdomainmovies.json
209 4 entries (
0 unique) with and
124 without IMDB title ID in free-movies-publicdomainreview.json
210 698 entries (
119 unique) with and
118 without IMDB title ID in free-movies-publicdomaintorrents.json
211 8 entries (
8 unique) with and
196 without IMDB title ID in free-movies-vodo.json
212 3186 unique IMDB title IDs in total
215 <p
>The entries without IMDB title ID are candidates to increase the
216 data set, but might equally well be duplicates of entries already
217 listed with IMDB title ID in one of the other sources, or represent
218 movies that lack a IMDB title ID. I
've seen examples of all these
219 situations when peeking at the entries without IMDB title ID. Based
220 on these data sources, the lower bound for movies listed in IMDB that
221 are legal to distribute on the Internet is between
3186 and
4713.
223 <p
>It would be great for improving the accuracy of this measurement,
224 if the various sources added IMDB title ID to their metadata. I have
225 tried to reach the people behind the various sources to ask if they
226 are interested in doing this, without any replies so far. Perhaps you
227 can help me get in touch with the people behind VODO, Public Domain
228 Torrents, Public Domain Movies and Public Domain Review to try to
229 convince them to add more metadata to their movie entries?
</p
>
231 <p
>Another way you could help is by adding pages to Wikipedia about
232 movies that are legal to distribute on the Internet. If such page
233 exist and include a link to both IMDB and The Internet Archive, the
234 script used to generate free-movies-archive-org-wikidata.json should
235 pick up the mapping as soon as wikidata is updates.
</p
>
237 <p
>As usual, if you use Bitcoin and want to show your support of my
238 activities, please send Bitcoin donations to my address
239 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
244 <title>Some notes on fault tolerant storage systems
</title>
245 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html
</link>
246 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html
</guid>
247 <pubDate>Wed,
1 Nov
2017 15:
35:
00 +
0100</pubDate>
248 <description><p
>If you care about how fault tolerant your storage is, you might
249 find these articles and papers interesting. They have formed how I
250 think of when designing a storage system.
</p
>
254 <li
>USENIX :login;
<a
255 href=
"https://www.usenix.org/publications/login/summer2017/ganesan
">Redundancy
256 Does Not Imply Fault Tolerance. Analysis of Distributed Storage
257 Reactions to Single Errors and Corruptions
</a
> by Aishwarya Ganesan,
258 Ramnatthan Alagappan, Andrea C. Arpaci-Dusseau, and Remzi
259 H. Arpaci-Dusseau
</li
>
262 <a href=
"http://www.zdnet.com/article/why-raid-
5-stops-working-in-
2009/
">Why
263 RAID
5 stops working in
2009</a
> by Robin Harris
</li
>
266 <a href=
"http://www.zdnet.com/article/why-raid-
6-stops-working-in-
2019/
">Why
267 RAID
6 stops working in
2019</a
> by Robin Harris
</li
>
269 <li
>USENIX FAST
'07
270 <a href=
"http://research.google.com/archive/disk_failures.pdf
">Failure
271 Trends in a Large Disk Drive Population
</a
> by Eduardo Pinheiro,
272 Wolf-Dietrich Weber and Luiz André Barroso
</li
>
274 <li
>USENIX ;login:
<a
275 href=
"https://www.usenix.org/system/files/login/articles/hughes12-
04.pdf
">Data
276 Integrity. Finding Truth in a World of Guesses and Lies
</a
> by Doug
279 <li
>USENIX FAST
'08
280 <a href=
"https://www.usenix.org/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/
">An
281 Analysis of Data Corruption in the Storage Stack
</a
> by
282 L. N. Bairavasundaram, G. R. Goodson, B. Schroeder, A. C.
283 Arpaci-Dusseau, and R. H. Arpaci-Dusseau
</li
>
285 <li
>USENIX FAST
'07 <a
286 href=
"https://www.usenix.org/legacy/events/fast07/tech/schroeder/schroeder_html/
">Disk
287 failures in the real world: what does an MTTF of
1,
000,
000 hours mean
288 to you?
</a
> by B. Schroeder and G. A. Gibson.
</li
>
290 <li
>USENIX ;login:
<a
291 href=
"https://www.usenix.org/events/fast08/tech/full_papers/jiang/jiang_html/
">Are
292 Disks the Dominant Contributor for Storage Failures? A Comprehensive
293 Study of Storage Subsystem Failure Characteristics
</a
> by Weihang
294 Jiang, Chongfeng Hu, Yuanyuan Zhou, and Arkady Kanevsky
</li
>
296 <li
>SIGMETRICS
2007
297 <a href=
"http://research.cs.wisc.edu/adsl/Publications/latent-sigmetrics07.pdf
">An
298 analysis of latent sector errors in disk drives
</a
> by
299 L. N. Bairavasundaram, G. R. Goodson, S. Pasupathy, and J. Schindler
</li
>
303 <p
>Several of these research papers are based on data collected from
304 hundred thousands or millions of disk, and their findings are eye
305 opening. The short story is simply do not implicitly trust RAID or
306 redundant storage systems. Details matter. And unfortunately there
307 are few options on Linux addressing all the identified issues. Both
308 ZFS and Btrfs are doing a fairly good job, but have legal and
309 practical issues on their own. I wonder how cluster file systems like
310 Ceph do in this regard. After all, there is an old saying, you know
311 you have a distributed system when the crash of a computer you have
312 never heard of stops you from getting any work done. The same holds
313 true if fault tolerance do not work.
</p
>
315 <p
>Just remember, in the end, it do not matter how redundant, or how
316 fault tolerant your storage is, if you do not continuously monitor its
317 status to detect and replace failed disks.
</p
>
319 <p
>As usual, if you use Bitcoin and want to show your support of my
320 activities, please send Bitcoin donations to my address
321 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
326 <title>Web services for writing academic LaTeX papers as a team
</title>
327 <link>http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html
</link>
328 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html
</guid>
329 <pubDate>Tue,
31 Oct
2017 21:
00:
00 +
0100</pubDate>
330 <description><p
>I was surprised today to learn that a friend in academia did not
331 know there are easily available web services available for writing
332 LaTeX documents as a team. I thought it was common knowledge, but to
333 make sure at least my readers are aware of it, I would like to mention
334 these useful services for writing LaTeX documents. Some of them even
335 provide a WYSIWYG editor to ease writing even further.
</p
>
337 <p
>There are two commercial services available,
338 <a href=
"https://sharelatex.com
">ShareLaTeX
</a
> and
339 <a href=
"https://overleaf.com
">Overleaf
</a
>. They are very easy to
340 use. Just start a new document, select which publisher to write for
341 (ie which LaTeX style to use), and start writing. Note, these two
342 have announced their intention to join forces, so soon it will only be
343 one joint service. I
've used both for different documents, and they
344 work just fine. While
345 <a href=
"https://github.com/sharelatex/sharelatex
">ShareLaTeX is free
346 software
</a
>, while the latter is not. According to
<a
347 href=
"https://www.overleaf.com/help/
17-is-overleaf-open-source
">a
348 announcement from Overleaf
</a
>, they plan to keep the ShareLaTeX code
349 base maintained as free software.
</p
>
351 But these two are not the only alternatives.
352 <a href=
"https://app.fiduswriter.org/
">Fidus Writer
</a
> is another free
353 software solution with
<a href=
"https://github.com/fiduswriter
">the
354 source available on github
</a
>. I have not used it myself. Several
355 others can be found on the nice
356 <a href=
"https://alternativeto.net/software/sharelatex/
">alterntiveTo
357 web service
</a
>.
359 <p
>If you like Google Docs or Etherpad, but would like to write
360 documents in LaTeX, you should check out these services. You can even
361 host your own, if you want to. :)
</p
>
363 <p
>As usual, if you use Bitcoin and want to show your support of my
364 activities, please send Bitcoin donations to my address
365 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
370 <title>Locating IMDB IDs of movies in the Internet Archive using Wikidata
</title>
371 <link>http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html
</link>
372 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html
</guid>
373 <pubDate>Wed,
25 Oct
2017 12:
20:
00 +
0200</pubDate>
374 <description><p
>Recently, I needed to automatically check the copyright status of a
375 set of
<a href=
"http://www.imdb.com/
">The Internet Movie database
376 (IMDB)
</a
> entries, to figure out which one of the movies they refer
377 to can be freely distributed on the Internet. This proved to be
378 harder than it sounds. IMDB for sure list movies without any
379 copyright protection, where the copyright protection has expired or
380 where the movie is lisenced using a permissive license like one from
381 Creative Commons. These are mixed with copyright protected movies,
382 and there seem to be no way to separate these classes of movies using
383 the information in IMDB.
</p
>
385 <p
>First I tried to look up entries manually in IMDB,
386 <a href=
"https://www.wikipedia.org/
">Wikipedia
</a
> and
387 <a href=
"https://www.archive.org/
">The Internet Archive
</a
>, to get a
388 feel how to do this. It is hard to know for sure using these sources,
389 but it should be possible to be reasonable confident a movie is
"out
390 of copyright
" with a few hours work per movie. As I needed to check
391 almost
20,
000 entries, this approach was not sustainable. I simply
392 can not work around the clock for about
6 years to check this data
395 <p
>I asked the people behind The Internet Archive if they could
396 introduce a new metadata field in their metadata XML for IMDB ID, but
397 was told that they leave it completely to the uploaders to update the
398 metadata. Some of the metadata entries had IMDB links in the
399 description, but I found no way to download all metadata files in bulk
400 to locate those ones and put that approach aside.
</p
>
402 <p
>In the process I noticed several Wikipedia articles about movies
403 had links to both IMDB and The Internet Archive, and it occured to me
404 that I could use the Wikipedia RDF data set to locate entries with
405 both, to at least get a lower bound on the number of movies on The
406 Internet Archive with a IMDB ID. This is useful based on the
407 assumption that movies distributed by The Internet Archive can be
408 legally distributed on the Internet. With some help from the RDF
409 community (thank you DanC), I was able to come up with this query to
410 pass to
<a href=
"https://query.wikidata.org/
">the SPARQL interface on
414 SELECT ?work ?imdb ?ia ?when ?label
417 ?work wdt:P31/wdt:P279* wd:Q11424.
418 ?work wdt:P345 ?imdb.
421 ?work wdt:P577 ?when.
422 ?work rdfs:label ?label.
423 FILTER(LANG(?label) =
"en
").
426 </pre
></p
>
428 <p
>If I understand the query right, for every film entry anywhere in
429 Wikpedia, it will return the IMDB ID and The Internet Archive ID, and
430 when the movie was released and its English title, if either or both
431 of the latter two are available. At the moment the result set contain
432 2338 entries. Of course, it depend on volunteers including both
433 correct IMDB and The Internet Archive IDs in the wikipedia articles
434 for the movie. It should be noted that the result will include
435 duplicates if the movie have entries in several languages. There are
436 some bogus entries, either because The Internet Archive ID contain a
437 typo or because the movie is not available from The Internet Archive.
438 I did not verify the IMDB IDs, as I am unsure how to do that
439 automatically.
</p
>
441 <p
>I wrote a small python script to extract the data set from Wikidata
442 and check if the XML metadata for the movie is available from The
443 Internet Archive, and after around
1.5 hour it produced a list of
2097
444 free movies and their IMDB ID. In total,
171 entries in Wikidata lack
445 the refered Internet Archive entry. I assume the
70 "disappearing
"
446 entries (ie
2338-
2097-
171) are duplicate entries.
</p
>
448 <p
>This is not too bad, given that The Internet Archive report to
449 contain
<a href=
"https://archive.org/details/feature_films
">5331
450 feature films
</a
> at the moment, but it also mean more than
3000
451 movies are missing on Wikipedia or are missing the pair of references
452 on Wikipedia.
</p
>
454 <p
>I was curious about the distribution by release year, and made a
455 little graph to show how the amount of free movies is spread over the
458 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2017-
10-
25-verk-i-det-fri-filmer.png
"></p
>
460 <p
>I expect the relative distribution of the remaining
3000 movies to
461 be similar.
</p
>
463 <p
>If you want to help, and want to ensure Wikipedia can be used to
464 cross reference The Internet Archive and The Internet Movie Database,
465 please make sure entries like this are listed under the
"External
466 links
" heading on the Wikipedia article for the movie:
</p
>
469 * {{Internet Archive film|id=FightingLady}}
470 * {{IMDb title|id=
0036823|title=The Fighting Lady}}
471 </pre
></p
>
473 <p
>Please verify the links on the final page, to make sure you did not
474 introduce a typo.
</p
>
476 <p
>Here is the complete list, if you want to correct the
171
477 identified Wikipedia entries with broken links to The Internet
478 Archive:
<a href=
"http://www.wikidata.org/entity/Q1140317
">Q1140317
</a
>,
479 <a href=
"http://www.wikidata.org/entity/Q458656
">Q458656
</a
>,
480 <a href=
"http://www.wikidata.org/entity/Q458656
">Q458656
</a
>,
481 <a href=
"http://www.wikidata.org/entity/Q470560
">Q470560
</a
>,
482 <a href=
"http://www.wikidata.org/entity/Q743340
">Q743340
</a
>,
483 <a href=
"http://www.wikidata.org/entity/Q822580
">Q822580
</a
>,
484 <a href=
"http://www.wikidata.org/entity/Q480696
">Q480696
</a
>,
485 <a href=
"http://www.wikidata.org/entity/Q128761
">Q128761
</a
>,
486 <a href=
"http://www.wikidata.org/entity/Q1307059
">Q1307059
</a
>,
487 <a href=
"http://www.wikidata.org/entity/Q1335091
">Q1335091
</a
>,
488 <a href=
"http://www.wikidata.org/entity/Q1537166
">Q1537166
</a
>,
489 <a href=
"http://www.wikidata.org/entity/Q1438334
">Q1438334
</a
>,
490 <a href=
"http://www.wikidata.org/entity/Q1479751
">Q1479751
</a
>,
491 <a href=
"http://www.wikidata.org/entity/Q1497200
">Q1497200
</a
>,
492 <a href=
"http://www.wikidata.org/entity/Q1498122
">Q1498122
</a
>,
493 <a href=
"http://www.wikidata.org/entity/Q865973
">Q865973
</a
>,
494 <a href=
"http://www.wikidata.org/entity/Q834269
">Q834269
</a
>,
495 <a href=
"http://www.wikidata.org/entity/Q841781
">Q841781
</a
>,
496 <a href=
"http://www.wikidata.org/entity/Q841781
">Q841781
</a
>,
497 <a href=
"http://www.wikidata.org/entity/Q1548193
">Q1548193
</a
>,
498 <a href=
"http://www.wikidata.org/entity/Q499031
">Q499031
</a
>,
499 <a href=
"http://www.wikidata.org/entity/Q1564769
">Q1564769
</a
>,
500 <a href=
"http://www.wikidata.org/entity/Q1585239
">Q1585239
</a
>,
501 <a href=
"http://www.wikidata.org/entity/Q1585569
">Q1585569
</a
>,
502 <a href=
"http://www.wikidata.org/entity/Q1624236
">Q1624236
</a
>,
503 <a href=
"http://www.wikidata.org/entity/Q4796595
">Q4796595
</a
>,
504 <a href=
"http://www.wikidata.org/entity/Q4853469
">Q4853469
</a
>,
505 <a href=
"http://www.wikidata.org/entity/Q4873046
">Q4873046
</a
>,
506 <a href=
"http://www.wikidata.org/entity/Q915016
">Q915016
</a
>,
507 <a href=
"http://www.wikidata.org/entity/Q4660396
">Q4660396
</a
>,
508 <a href=
"http://www.wikidata.org/entity/Q4677708
">Q4677708
</a
>,
509 <a href=
"http://www.wikidata.org/entity/Q4738449
">Q4738449
</a
>,
510 <a href=
"http://www.wikidata.org/entity/Q4756096
">Q4756096
</a
>,
511 <a href=
"http://www.wikidata.org/entity/Q4766785
">Q4766785
</a
>,
512 <a href=
"http://www.wikidata.org/entity/Q880357
">Q880357
</a
>,
513 <a href=
"http://www.wikidata.org/entity/Q882066
">Q882066
</a
>,
514 <a href=
"http://www.wikidata.org/entity/Q882066
">Q882066
</a
>,
515 <a href=
"http://www.wikidata.org/entity/Q204191
">Q204191
</a
>,
516 <a href=
"http://www.wikidata.org/entity/Q204191
">Q204191
</a
>,
517 <a href=
"http://www.wikidata.org/entity/Q1194170
">Q1194170
</a
>,
518 <a href=
"http://www.wikidata.org/entity/Q940014
">Q940014
</a
>,
519 <a href=
"http://www.wikidata.org/entity/Q946863
">Q946863
</a
>,
520 <a href=
"http://www.wikidata.org/entity/Q172837
">Q172837
</a
>,
521 <a href=
"http://www.wikidata.org/entity/Q573077
">Q573077
</a
>,
522 <a href=
"http://www.wikidata.org/entity/Q1219005
">Q1219005
</a
>,
523 <a href=
"http://www.wikidata.org/entity/Q1219599
">Q1219599
</a
>,
524 <a href=
"http://www.wikidata.org/entity/Q1643798
">Q1643798
</a
>,
525 <a href=
"http://www.wikidata.org/entity/Q1656352
">Q1656352
</a
>,
526 <a href=
"http://www.wikidata.org/entity/Q1659549
">Q1659549
</a
>,
527 <a href=
"http://www.wikidata.org/entity/Q1660007
">Q1660007
</a
>,
528 <a href=
"http://www.wikidata.org/entity/Q1698154
">Q1698154
</a
>,
529 <a href=
"http://www.wikidata.org/entity/Q1737980
">Q1737980
</a
>,
530 <a href=
"http://www.wikidata.org/entity/Q1877284
">Q1877284
</a
>,
531 <a href=
"http://www.wikidata.org/entity/Q1199354
">Q1199354
</a
>,
532 <a href=
"http://www.wikidata.org/entity/Q1199354
">Q1199354
</a
>,
533 <a href=
"http://www.wikidata.org/entity/Q1199451
">Q1199451
</a
>,
534 <a href=
"http://www.wikidata.org/entity/Q1211871
">Q1211871
</a
>,
535 <a href=
"http://www.wikidata.org/entity/Q1212179
">Q1212179
</a
>,
536 <a href=
"http://www.wikidata.org/entity/Q1238382
">Q1238382
</a
>,
537 <a href=
"http://www.wikidata.org/entity/Q4906454
">Q4906454
</a
>,
538 <a href=
"http://www.wikidata.org/entity/Q320219
">Q320219
</a
>,
539 <a href=
"http://www.wikidata.org/entity/Q1148649
">Q1148649
</a
>,
540 <a href=
"http://www.wikidata.org/entity/Q645094
">Q645094
</a
>,
541 <a href=
"http://www.wikidata.org/entity/Q5050350
">Q5050350
</a
>,
542 <a href=
"http://www.wikidata.org/entity/Q5166548
">Q5166548
</a
>,
543 <a href=
"http://www.wikidata.org/entity/Q2677926
">Q2677926
</a
>,
544 <a href=
"http://www.wikidata.org/entity/Q2698139
">Q2698139
</a
>,
545 <a href=
"http://www.wikidata.org/entity/Q2707305
">Q2707305
</a
>,
546 <a href=
"http://www.wikidata.org/entity/Q2740725
">Q2740725
</a
>,
547 <a href=
"http://www.wikidata.org/entity/Q2024780
">Q2024780
</a
>,
548 <a href=
"http://www.wikidata.org/entity/Q2117418
">Q2117418
</a
>,
549 <a href=
"http://www.wikidata.org/entity/Q2138984
">Q2138984
</a
>,
550 <a href=
"http://www.wikidata.org/entity/Q1127992
">Q1127992
</a
>,
551 <a href=
"http://www.wikidata.org/entity/Q1058087
">Q1058087
</a
>,
552 <a href=
"http://www.wikidata.org/entity/Q1070484
">Q1070484
</a
>,
553 <a href=
"http://www.wikidata.org/entity/Q1080080
">Q1080080
</a
>,
554 <a href=
"http://www.wikidata.org/entity/Q1090813
">Q1090813
</a
>,
555 <a href=
"http://www.wikidata.org/entity/Q1251918
">Q1251918
</a
>,
556 <a href=
"http://www.wikidata.org/entity/Q1254110
">Q1254110
</a
>,
557 <a href=
"http://www.wikidata.org/entity/Q1257070
">Q1257070
</a
>,
558 <a href=
"http://www.wikidata.org/entity/Q1257079
">Q1257079
</a
>,
559 <a href=
"http://www.wikidata.org/entity/Q1197410
">Q1197410
</a
>,
560 <a href=
"http://www.wikidata.org/entity/Q1198423
">Q1198423
</a
>,
561 <a href=
"http://www.wikidata.org/entity/Q706951
">Q706951
</a
>,
562 <a href=
"http://www.wikidata.org/entity/Q723239
">Q723239
</a
>,
563 <a href=
"http://www.wikidata.org/entity/Q2079261
">Q2079261
</a
>,
564 <a href=
"http://www.wikidata.org/entity/Q1171364
">Q1171364
</a
>,
565 <a href=
"http://www.wikidata.org/entity/Q617858
">Q617858
</a
>,
566 <a href=
"http://www.wikidata.org/entity/Q5166611
">Q5166611
</a
>,
567 <a href=
"http://www.wikidata.org/entity/Q5166611
">Q5166611
</a
>,
568 <a href=
"http://www.wikidata.org/entity/Q324513
">Q324513
</a
>,
569 <a href=
"http://www.wikidata.org/entity/Q374172
">Q374172
</a
>,
570 <a href=
"http://www.wikidata.org/entity/Q7533269
">Q7533269
</a
>,
571 <a href=
"http://www.wikidata.org/entity/Q970386
">Q970386
</a
>,
572 <a href=
"http://www.wikidata.org/entity/Q976849
">Q976849
</a
>,
573 <a href=
"http://www.wikidata.org/entity/Q7458614
">Q7458614
</a
>,
574 <a href=
"http://www.wikidata.org/entity/Q5347416
">Q5347416
</a
>,
575 <a href=
"http://www.wikidata.org/entity/Q5460005
">Q5460005
</a
>,
576 <a href=
"http://www.wikidata.org/entity/Q5463392
">Q5463392
</a
>,
577 <a href=
"http://www.wikidata.org/entity/Q3038555
">Q3038555
</a
>,
578 <a href=
"http://www.wikidata.org/entity/Q5288458
">Q5288458
</a
>,
579 <a href=
"http://www.wikidata.org/entity/Q2346516
">Q2346516
</a
>,
580 <a href=
"http://www.wikidata.org/entity/Q5183645
">Q5183645
</a
>,
581 <a href=
"http://www.wikidata.org/entity/Q5185497
">Q5185497
</a
>,
582 <a href=
"http://www.wikidata.org/entity/Q5216127
">Q5216127
</a
>,
583 <a href=
"http://www.wikidata.org/entity/Q5223127
">Q5223127
</a
>,
584 <a href=
"http://www.wikidata.org/entity/Q5261159
">Q5261159
</a
>,
585 <a href=
"http://www.wikidata.org/entity/Q1300759
">Q1300759
</a
>,
586 <a href=
"http://www.wikidata.org/entity/Q5521241
">Q5521241
</a
>,
587 <a href=
"http://www.wikidata.org/entity/Q7733434
">Q7733434
</a
>,
588 <a href=
"http://www.wikidata.org/entity/Q7736264
">Q7736264
</a
>,
589 <a href=
"http://www.wikidata.org/entity/Q7737032
">Q7737032
</a
>,
590 <a href=
"http://www.wikidata.org/entity/Q7882671
">Q7882671
</a
>,
591 <a href=
"http://www.wikidata.org/entity/Q7719427
">Q7719427
</a
>,
592 <a href=
"http://www.wikidata.org/entity/Q7719444
">Q7719444
</a
>,
593 <a href=
"http://www.wikidata.org/entity/Q7722575
">Q7722575
</a
>,
594 <a href=
"http://www.wikidata.org/entity/Q2629763
">Q2629763
</a
>,
595 <a href=
"http://www.wikidata.org/entity/Q2640346
">Q2640346
</a
>,
596 <a href=
"http://www.wikidata.org/entity/Q2649671
">Q2649671
</a
>,
597 <a href=
"http://www.wikidata.org/entity/Q7703851
">Q7703851
</a
>,
598 <a href=
"http://www.wikidata.org/entity/Q7747041
">Q7747041
</a
>,
599 <a href=
"http://www.wikidata.org/entity/Q6544949
">Q6544949
</a
>,
600 <a href=
"http://www.wikidata.org/entity/Q6672759
">Q6672759
</a
>,
601 <a href=
"http://www.wikidata.org/entity/Q2445896
">Q2445896
</a
>,
602 <a href=
"http://www.wikidata.org/entity/Q12124891
">Q12124891
</a
>,
603 <a href=
"http://www.wikidata.org/entity/Q3127044
">Q3127044
</a
>,
604 <a href=
"http://www.wikidata.org/entity/Q2511262
">Q2511262
</a
>,
605 <a href=
"http://www.wikidata.org/entity/Q2517672
">Q2517672
</a
>,
606 <a href=
"http://www.wikidata.org/entity/Q2543165
">Q2543165
</a
>,
607 <a href=
"http://www.wikidata.org/entity/Q426628
">Q426628
</a
>,
608 <a href=
"http://www.wikidata.org/entity/Q426628
">Q426628
</a
>,
609 <a href=
"http://www.wikidata.org/entity/Q12126890
">Q12126890
</a
>,
610 <a href=
"http://www.wikidata.org/entity/Q13359969
">Q13359969
</a
>,
611 <a href=
"http://www.wikidata.org/entity/Q13359969
">Q13359969
</a
>,
612 <a href=
"http://www.wikidata.org/entity/Q2294295
">Q2294295
</a
>,
613 <a href=
"http://www.wikidata.org/entity/Q2294295
">Q2294295
</a
>,
614 <a href=
"http://www.wikidata.org/entity/Q2559509
">Q2559509
</a
>,
615 <a href=
"http://www.wikidata.org/entity/Q2559912
">Q2559912
</a
>,
616 <a href=
"http://www.wikidata.org/entity/Q7760469
">Q7760469
</a
>,
617 <a href=
"http://www.wikidata.org/entity/Q6703974
">Q6703974
</a
>,
618 <a href=
"http://www.wikidata.org/entity/Q4744
">Q4744
</a
>,
619 <a href=
"http://www.wikidata.org/entity/Q7766962
">Q7766962
</a
>,
620 <a href=
"http://www.wikidata.org/entity/Q7768516
">Q7768516
</a
>,
621 <a href=
"http://www.wikidata.org/entity/Q7769205
">Q7769205
</a
>,
622 <a href=
"http://www.wikidata.org/entity/Q7769988
">Q7769988
</a
>,
623 <a href=
"http://www.wikidata.org/entity/Q2946945
">Q2946945
</a
>,
624 <a href=
"http://www.wikidata.org/entity/Q3212086
">Q3212086
</a
>,
625 <a href=
"http://www.wikidata.org/entity/Q3212086
">Q3212086
</a
>,
626 <a href=
"http://www.wikidata.org/entity/Q18218448
">Q18218448
</a
>,
627 <a href=
"http://www.wikidata.org/entity/Q18218448
">Q18218448
</a
>,
628 <a href=
"http://www.wikidata.org/entity/Q18218448
">Q18218448
</a
>,
629 <a href=
"http://www.wikidata.org/entity/Q6909175
">Q6909175
</a
>,
630 <a href=
"http://www.wikidata.org/entity/Q7405709
">Q7405709
</a
>,
631 <a href=
"http://www.wikidata.org/entity/Q7416149
">Q7416149
</a
>,
632 <a href=
"http://www.wikidata.org/entity/Q7239952
">Q7239952
</a
>,
633 <a href=
"http://www.wikidata.org/entity/Q7317332
">Q7317332
</a
>,
634 <a href=
"http://www.wikidata.org/entity/Q7783674
">Q7783674
</a
>,
635 <a href=
"http://www.wikidata.org/entity/Q7783704
">Q7783704
</a
>,
636 <a href=
"http://www.wikidata.org/entity/Q7857590
">Q7857590
</a
>,
637 <a href=
"http://www.wikidata.org/entity/Q3372526
">Q3372526
</a
>,
638 <a href=
"http://www.wikidata.org/entity/Q3372642
">Q3372642
</a
>,
639 <a href=
"http://www.wikidata.org/entity/Q3372816
">Q3372816
</a
>,
640 <a href=
"http://www.wikidata.org/entity/Q3372909
">Q3372909
</a
>,
641 <a href=
"http://www.wikidata.org/entity/Q7959649
">Q7959649
</a
>,
642 <a href=
"http://www.wikidata.org/entity/Q7977485
">Q7977485
</a
>,
643 <a href=
"http://www.wikidata.org/entity/Q7992684
">Q7992684
</a
>,
644 <a href=
"http://www.wikidata.org/entity/Q3817966
">Q3817966
</a
>,
645 <a href=
"http://www.wikidata.org/entity/Q3821852
">Q3821852
</a
>,
646 <a href=
"http://www.wikidata.org/entity/Q3420907
">Q3420907
</a
>,
647 <a href=
"http://www.wikidata.org/entity/Q3429733
">Q3429733
</a
>,
648 <a href=
"http://www.wikidata.org/entity/Q774474
">Q774474
</a
></p
>
650 <p
>As usual, if you use Bitcoin and want to show your support of my
651 activities, please send Bitcoin donations to my address
652 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
657 <title>A one-way wall on the border?
</title>
658 <link>http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html
</link>
659 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html
</guid>
660 <pubDate>Sat,
14 Oct
2017 22:
10:
00 +
0200</pubDate>
661 <description><p
>I find it fascinating how many of the people being locked inside
662 the proposed border wall between USA and Mexico support the idea. The
663 proposal to keep Mexicans out reminds me of
664 <a href=
"http://www.history.com/news/
10-things-you-may-not-know-about-the-berlin-wall
">the
665 propaganda twist from the East Germany government
</a
> calling the wall
666 the “Antifascist Bulwark” after erecting the Berlin Wall, claiming
667 that the wall was erected to keep enemies from creeping into East
668 Germany, while it was obvious to the people locked inside it that it
669 was erected to keep the people from escaping.
</p
>
671 <p
>Do the people in USA supporting this wall really believe it is a
672 one way wall, only keeping people on the outside from getting in,
673 while not keeping people in the inside from getting out?
</p
>
675 <p
>As usual, if you use Bitcoin and want to show your support of my
676 activities, please send Bitcoin donations to my address
677 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
682 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
683 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
685 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
686 <description><p
>At my nearby maker space,
687 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
688 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
689 on Windows and MacOS X than Linux, because the software involved had
690 to be manually compiled and set up on Linux while premade packages
691 worked out of the box on Windows and MacOS X. I found this annoying,
692 as the software involved,
693 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
694 and should be trivial to get up and running on Linux if someone took
695 the time to package it for the relevant distributions. I even found
696 <a href=
"https://bugs.debian.org/
706656">a request for adding into
697 Debian
</a
> from
2013, which had seem some activity over the years but
698 never resulted in the software showing up in Debian. So a few days
699 ago I offered my help to try to improve the situation.
</p
>
701 <p
>Now I am very happy to see that all the packages required by a
702 working Cura in Debian are uploaded into Debian and waiting in the NEW
703 queue for the ftpmasters to have a look. You can track the progress
705 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
706 status page for the
3D printer team
</a
>.
</p
>
708 <p
>The uploaded packages are a bit behind upstream, and was uploaded
709 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
710 queue
</a
> while we work up updating the packages to the latest
711 upstream version.
</p
>
713 <p
>On a related note, two competitors for Cura, which I found harder
714 to use and was unable to configure correctly for Ultimaker
2+ in the
715 short time I spent on it, are already in Debian. If you are looking
716 for
3D printer
"slicers
" and want something already available in
718 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
719 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
720 The latter is a fork of the former.
</p
>
722 <p
>As usual, if you use Bitcoin and want to show your support of my
723 activities, please send Bitcoin donations to my address
724 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
729 <title>Mangler du en skrue, eller har du en skrue løs?
</title>
730 <link>http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html
</link>
731 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html
</guid>
732 <pubDate>Wed,
4 Oct
2017 09:
40:
00 +
0200</pubDate>
733 <description>Når jeg holder på med ulike prosjekter, så trenger jeg stadig ulike
734 skruer. Det siste prosjektet jeg holder på med er å lage
735 <a href=
"https://www.thingiverse.com/thing:
676916">en boks til en
736 HDMI-touch-skjerm
</a
> som skal brukes med Raspberry Pi. Boksen settes
737 sammen med skruer og bolter, og jeg har vært i tvil om hvor jeg kan
738 få tak i de riktige skruene. Clas Ohlson og Jernia i nærheten har
739 sjelden hatt det jeg trenger. Men her om dagen fikk jeg et fantastisk
740 tips for oss som bor i Oslo.
741 <a href=
"http://www.zachskruer.no/
">Zachariassen Jernvare AS
</a
> i
742 <a href=
"http://www.openstreetmap.org/?mlat=
59.93421&mlon=
10.76795#map=
19/
59.93421/
10.76795">Hegermannsgate
743 23A på Torshov
</a
> har et fantastisk utvalg, og åpent mellom
09:
00 og
744 17:
00. De selger skruer, muttere, bolter, skiver etc i løs vekt, og
745 så langt har jeg fått alt jeg har lett etter. De har i tillegg det
746 meste av annen jernvare, som verktøy, lamper, ledninger, etc. Jeg
747 håper de har nok kunder til å holde det gående lenge, da dette er en
748 butikk jeg kommer til å besøke ofte. Butikken er et funn å ha i
749 nabolaget for oss som liker å bygge litt selv. :)
</p
>
751 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
752 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
754 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
759 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
760 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
761 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
762 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
763 <description><p
>Every mobile phone announce its existence over radio to the nearby
764 mobile cell towers. And this radio chatter is available for anyone
765 with a radio receiver capable of receiving them. Details about the
766 mobile phones with very good accuracy is of course collected by the
767 phone companies, but this is not the topic of this blog post. The
768 mobile phone radio chatter make it possible to figure out when a cell
769 phone is nearby, as it include the SIM card ID (IMSI). By paying
770 attention over time, one can see when a phone arrive and when it leave
771 an area. I believe it would be nice to make this information more
772 available to the general public, to make more people aware of how
773 their phones are announcing their whereabouts to anyone that care to
776 <p
>I am very happy to report that we managed to get something
777 visualizing this information up and running for
778 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
779 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
780 library. The solution is based on the
781 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
782 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
783 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
784 Sone from the Computer Science department of the University of
785 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
786 IMSIs) as dots in a web browser graph, with lines to the dot
787 representing mobile base station it is talking to. It was working in
788 the lab yesterday, and was moved into place this morning.
</p
>
790 <p
>We set up a fairly powerful desktop machine using Debian
791 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
792 connected and visualize the visible cell phone towers using an
793 <a href=
"https://github.com/marlow925/hopglass
">English version of
794 Hopglass
</a
>. A fairly powerfull machine is needed as the
795 grgsm_livemon_headless processes from
796 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
797 the radio signal to data packages is quite CPU intensive.
</p
>
799 <p
>The frequencies to listen to, are identified using a slightly
800 patched scan-and-livemon (to set the --args values for each receiver),
801 and the Hopglass data is generated using the
802 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
803 in my meshviewer-output branch
</a
>. For some reason we could not get
804 more than four SDRs working. There is also a geographical map trying
805 to show the location of the base stations, but I believe their
806 coordinates are hardcoded to some random location in Germany, I
807 believe. The code should be replaced with code to look up location in
808 a text file, a sqlite database or one of the online databases
810 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
811 issue for the topic
</a
>.
813 <p
>If this sound interesting, visit the stand at the festival!
</p
>