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