]> pere.pagekite.me Git - homepage.git/blob - blog/tags/web/web.rss
dc21f2097b499f8510dcfba1f63294efe5cf9bde
[homepage.git] / blog / tags / web / web.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries tagged web</title>
5 <description>Entries tagged web</description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>Do you need an agreement with MPEG-LA to publish and broadcast H.264 video in Norway?</title>
11 <link>http://people.skolelinux.org/pere/blog/Do_you_need_an_agreement_with_MPEG_LA_to_publish_and_broadcast_H_264_video_in_Norway_.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Do_you_need_an_agreement_with_MPEG_LA_to_publish_and_broadcast_H_264_video_in_Norway_.html</guid>
13 <pubDate>Mon, 25 Aug 2014 22:10:00 +0200</pubDate>
14 <description>&lt;p&gt;Two years later, I am still not sure if it is legal here in Norway
15 to use or publish a video in H.264 or MPEG4 format edited by the
16 commercially licensed video editors, without limiting the use to
17 create &quot;personal&quot; or &quot;non-commercial&quot; videos or get a license
18 agreement with &lt;a href=&quot;http://www.mpegla.com&quot;&gt;MPEG LA&lt;/a&gt;. If one
19 want to publish and broadcast video in a non-personal or commercial
20 setting, it might be that those tools can not be used, or that video
21 format can not be used, without breaking their copyright license. I
22 am not sure.
23 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html&quot;&gt;Back
24 then&lt;/a&gt;, I found that the copyright license terms for Adobe Premiere
25 and Apple Final Cut Pro both specified that one could not use the
26 program to produce anything else without a patent license from MPEG
27 LA. The issue is not limited to those two products, though. Other
28 much used products like those from Avid and Sorenson Media have terms
29 of use are similar to those from Adobe and Apple. The complicating
30 factor making me unsure if those terms have effect in Norway or not is
31 that the patents in question are not valid in Norway, but copyright
32 licenses are.&lt;/p&gt;
33
34 &lt;p&gt;These are the terms for Avid Artist Suite, according to their
35 &lt;a href=&quot;http://www.avid.com/US/about-avid/legal-notices/legal-enduserlicense2&quot;&gt;published
36 end user&lt;/a&gt;
37 &lt;a href=&quot;http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf&quot;&gt;license
38 text&lt;/a&gt; (converted to lower case text for easier reading):&lt;/p&gt;
39
40 &lt;p&gt;&lt;blockquote&gt;
41 &lt;p&gt;18.2. MPEG-4. MPEG-4 technology may be included with the
42 software. MPEG LA, L.L.C. requires this notice: &lt;/p&gt;
43
44 &lt;p&gt;This product is licensed under the MPEG-4 visual patent portfolio
45 license for the personal and non-commercial use of a consumer for (i)
46 encoding video in compliance with the MPEG-4 visual standard (“MPEG-4
47 video”) and/or (ii) decoding MPEG-4 video that was encoded by a
48 consumer engaged in a personal and non-commercial activity and/or was
49 obtained from a video provider licensed by MPEG LA to provide MPEG-4
50 video. No license is granted or shall be implied for any other
51 use. Additional information including that relating to promotional,
52 internal and commercial uses and licensing may be obtained from MPEG
53 LA, LLC. See http://www.mpegla.com. This product is licensed under
54 the MPEG-4 systems patent portfolio license for encoding in compliance
55 with the MPEG-4 systems standard, except that an additional license
56 and payment of royalties are necessary for encoding in connection with
57 (i) data stored or replicated in physical media which is paid for on a
58 title by title basis and/or (ii) data which is paid for on a title by
59 title basis and is transmitted to an end user for permanent storage
60 and/or use, such additional license may be obtained from MPEG LA,
61 LLC. See http://www.mpegla.com for additional details.&lt;/p&gt;
62
63 &lt;p&gt;18.3. H.264/AVC. H.264/AVC technology may be included with the
64 software. MPEG LA, L.L.C. requires this notice:&lt;/p&gt;
65
66 &lt;p&gt;This product is licensed under the AVC patent portfolio license for
67 the personal use of a consumer or other uses in which it does not
68 receive remuneration to (i) encode video in compliance with the AVC
69 standard (“AVC video”) and/or (ii) decode AVC video that was encoded
70 by a consumer engaged in a personal activity and/or was obtained from
71 a video provider licensed to provide AVC video. No license is granted
72 or shall be implied for any other use. Additional information may be
73 obtained from MPEG LA, L.L.C. See http://www.mpegla.com.&lt;/p&gt;
74 &lt;/blockquote&gt;&lt;/p&gt;
75
76 &lt;p&gt;Note the requirement that the videos created can only be used for
77 personal or non-commercial purposes.&lt;/p&gt;
78
79 &lt;p&gt;The Sorenson Media software have
80 &lt;a href=&quot;http://www.sorensonmedia.com/terms/&quot;&gt;similar terms&lt;/a&gt;:&lt;/p&gt;
81
82 &lt;p&gt;&lt;blockquote&gt;
83
84 &lt;p&gt;With respect to a license from Sorenson pertaining to MPEG-4 Video
85 Decoders and/or Encoders: Any such product is licensed under the
86 MPEG-4 visual patent portfolio license for the personal and
87 non-commercial use of a consumer for (i) encoding video in compliance
88 with the MPEG-4 visual standard (“MPEG-4 video”) and/or (ii) decoding
89 MPEG-4 video that was encoded by a consumer engaged in a personal and
90 non-commercial activity and/or was obtained from a video provider
91 licensed by MPEG LA to provide MPEG-4 video. No license is granted or
92 shall be implied for any other use. Additional information including
93 that relating to promotional, internal and commercial uses and
94 licensing may be obtained from MPEG LA, LLC. See
95 http://www.mpegla.com.&lt;/p&gt;
96
97 &lt;p&gt;With respect to a license from Sorenson pertaining to MPEG-4
98 Consumer Recorded Data Encoder, MPEG-4 Systems Internet Data Encoder,
99 MPEG-4 Mobile Data Encoder, and/or MPEG-4 Unique Use Encoder: Any such
100 product is licensed under the MPEG-4 systems patent portfolio license
101 for encoding in compliance with the MPEG-4 systems standard, except
102 that an additional license and payment of royalties are necessary for
103 encoding in connection with (i) data stored or replicated in physical
104 media which is paid for on a title by title basis and/or (ii) data
105 which is paid for on a title by title basis and is transmitted to an
106 end user for permanent storage and/or use. Such additional license may
107 be obtained from MPEG LA, LLC. See http://www.mpegla.com for
108 additional details.&lt;/p&gt;
109
110 &lt;/blockquote&gt;&lt;/p&gt;
111
112 &lt;p&gt;Some free software like
113 &lt;a href=&quot;https://handbrake.fr/&quot;&gt;Handbrake&lt;/A&gt; and
114 &lt;a href=&quot;http://ffmpeg.org/&quot;&gt;FFMPEG&lt;/a&gt; uses GPL/LGPL licenses and do
115 not have any such terms included, so for those, there is no
116 requirement to limit the use to personal and non-commercial.&lt;/p&gt;
117 </description>
118 </item>
119
120 <item>
121 <title>Hvordan enkelt laste ned filmer fra NRK med den &quot;nye&quot; løsningen</title>
122 <link>http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html</link>
123 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html</guid>
124 <pubDate>Mon, 16 Jun 2014 19:20:00 +0200</pubDate>
125 <description>&lt;p&gt;Jeg har fortsatt behov for å kunne laste ned innslag fra NRKs
126 nettsted av og til for å se senere når jeg ikke er på nett, men
127 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html&quot;&gt;min
128 oppskrift fra 2011&lt;/a&gt; sluttet å fungere da NRK byttet
129 avspillermetode. I dag fikk jeg endelig lett etter oppdatert løsning,
130 og jeg er veldig glad for å fortelle at den enkleste måten å laste ned
131 innslag er å bruke siste versjon 2014.06.07 av
132 &lt;a href=&quot;http://rg3.github.io/youtube-dl/&quot;&gt;youtube-dl&lt;/a&gt;. Støtten i
133 youtube-dl &lt;a href=&quot;https://github.com/rg3/youtube-dl/issues/2980&quot;&gt;kom
134 inn for 23 dager siden&lt;/a&gt; og
135 &lt;a href=&quot;http://packages.qa.debian.org/y/youtube-dl.html&quot;&gt;versjonen i
136 Debian&lt;/a&gt; fungerer fint også som backport til Debian Wheezy. Det er
137 et lite problem, det håndterer kun URLer med små bokstaver, men hvis
138 en har en URL med store bokstaver kan en bare gjøre alle store om til
139 små bokstaver for å få youtube-dl til å laste ned. Rapporterte
140 nettopp
141 &lt;a href=&quot;https://github.com/rg3/youtube-dl/issues/2980&quot;&gt;problemet til
142 utviklerne&lt;/a&gt;, og antar de får fikset det snart.&lt;/p&gt;
143
144 &lt;p&gt;Dermed er alt klart til å laste ned dokumentarene om
145 &lt;a href=&quot;http://tv.nrk.no/program/KOID23005014/usas-hemmelige-avlytting&quot;&gt;USAs
146 hemmelige avlytting&lt;/a&gt; og
147 &lt;a href=&quot;http://tv.nrk.no/program/KOID23005114/selskapene-bak-usas-avlytting&quot;&gt;Selskapene
148 bak USAs avlytting&lt;/a&gt;, i tillegg til
149 &lt;a href=&quot;http://tv.nrk.no/program/KOID20005814/et-moete-med-edward-snowden&quot;&gt;intervjuet
150 med Edward Snowden gjort av den tyske tv-kanalen ARD&lt;/a&gt;. Anbefaler
151 alle å se disse, sammen med
152 &lt;a href=&quot;http://media.ccc.de/browse/congress/2013/30C3_-_5713_-_en_-_saal_2_-_201312301130_-_to_protect_and_infect_part_2_-_jacob.html&quot;&gt;foredraget
153 til Jacob Appelbaum på siste CCC-konferanse&lt;/a&gt;, for å forstå mer om
154 hvordan overvåkningen av borgerne brer om seg.&lt;/p&gt;
155
156 &lt;p&gt;Takk til gode venner på foreningen NUUGs IRC-kanal
157 &lt;a href=&quot;irc://irc.freenode.net/%23nuug&quot;&gt;#nuug på irc.freenode.net&lt;/a&gt;
158 for tipsene som fikk meg i mål&lt;/a&gt;.&lt;/p&gt;
159
160 &lt;p&gt;&lt;strong&gt;Oppdatering 2014-06-17&lt;/strong&gt;: Etter at jeg publiserte
161 denne, ble jeg tipset om bloggposten
162 &quot;&lt;a href=&quot;http://ingvar.blog.redpill-linpro.com/2012/05/31/downloading-hd-content-from-tv-nrk-no/&quot;&gt;Downloading
163 HD content from tv.nrk.no&lt;/a&gt;&quot; av Ingvar Hagelund, som har alternativ
164 implementasjon og tips for å lage mkv-fil med undertekstene inkludert.
165 Kanskje den passer bedre for deg? I tillegg ble feilen i youtube-dl
166 ble fikset litt senere ut på dagen i går, samt at youtube-dl fikk
167 støtte for å laste ned undertitler. Takk til Anders Einar Hilden for
168 god innsats og youtube-dl-utviklerne for rask respons.&lt;/p&gt;
169 </description>
170 </item>
171
172 <item>
173 <title>Half the Coverity issues in Gnash fixed in the next release</title>
174 <link>http://people.skolelinux.org/pere/blog/Half_the_Coverity_issues_in_Gnash_fixed_in_the_next_release.html</link>
175 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Half_the_Coverity_issues_in_Gnash_fixed_in_the_next_release.html</guid>
176 <pubDate>Tue, 29 Apr 2014 14:20:00 +0200</pubDate>
177 <description>&lt;p&gt;I&#39;ve been following &lt;a href=&quot;http://www.getgnash.org/&quot;&gt;the Gnash
178 project&lt;/a&gt; for quite a while now. It is a free software
179 implementation of Adobe Flash, both a standalone player and a browser
180 plugin. Gnash implement support for the AVM1 format (and not the
181 newer AVM2 format - see
182 &lt;a href=&quot;http://lightspark.github.io/&quot;&gt;Lightspark&lt;/a&gt; for that one),
183 allowing several flash based sites to work. Thanks to the friendly
184 developers at Youtube, it also work with Youtube videos, because the
185 Javascript code at Youtube detect Gnash and serve a AVM1 player to
186 those users. :) Would be great if someone found time to implement AVM2
187 support, but it has not happened yet. If you install both Lightspark
188 and Gnash, Lightspark will invoke Gnash if it find a AVM1 flash file,
189 so you can get both handled as free software. Unfortunately,
190 Lightspark so far only implement a small subset of AVM2, and many
191 sites do not work yet.&lt;/p&gt;
192
193 &lt;p&gt;A few months ago, I started looking at
194 &lt;a href=&quot;http://scan.coverity.com/&quot;&gt;Coverity&lt;/a&gt;, the static source
195 checker used to find heaps and heaps of bugs in free software (thanks
196 to the donation of a scanning service to free software projects by the
197 company developing this non-free code checker), and Gnash was one of
198 the projects I decided to check out. Coverity is able to find lock
199 errors, memory errors, dead code and more. A few days ago they even
200 extended it to also be able to find the heartbleed bug in OpenSSL.
201 There are heaps of checks being done on the instrumented code, and the
202 amount of bogus warnings is quite low compared to the other static
203 code checkers I have tested over the years.&lt;/p&gt;
204
205 &lt;p&gt;Since a few weeks ago, I&#39;ve been working with the other Gnash
206 developers squashing bugs discovered by Coverity. I was quite happy
207 today when I checked the current status and saw that of the 777 issues
208 detected so far, 374 are marked as fixed. This make me confident that
209 the next Gnash release will be more stable and more dependable than
210 the previous one. Most of the reported issues were and are in the
211 test suite, but it also found a few in the rest of the code.&lt;/p&gt;
212
213 &lt;p&gt;If you want to help out, you find us on
214 &lt;a href=&quot;https://lists.gnu.org/mailman/listinfo/gnash-dev&quot;&gt;the
215 gnash-dev mailing list&lt;/a&gt; and on
216 &lt;a href=&quot;irc://irc.freenode.net/#gnash&quot;&gt;the #gnash channel on
217 irc.freenode.net IRC server&lt;/a&gt;.&lt;/p&gt;
218 </description>
219 </item>
220
221 <item>
222 <title>FreedomBox milestone - all packages now in Debian Sid</title>
223 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
224 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
225 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
226 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
227 project&lt;/a&gt; is working on providing the software and hardware to make
228 it easy for non-technical people to host their data and communication
229 at home, and being able to communicate with their friends and family
230 encrypted and away from prying eyes. It is still going strong, and
231 today a major mile stone was reached.&lt;/p&gt;
232
233 &lt;p&gt;Today, the last of the packages currently used by the project to
234 created the system images were accepted into Debian Unstable. It was
235 the freedombox-setup package, which is used to configure the images
236 during build and on the first boot. Now all one need to get going is
237 the build code from the freedom-maker git repository and packages from
238 Debian. And once the freedombox-setup package enter testing, we can
239 build everything directly from Debian. :)&lt;/p&gt;
240
241 &lt;p&gt;Some key packages used by Freedombox are
242 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
243 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
244 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
245 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
246 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
247 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
248 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
249 are plans to integrate more packages into the setup. User
250 documentation is maintained on the Debian wiki. Please
251 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
252 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
253
254 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
255 setup, run this on a Debian machine using a user with sudo rights to
256 become root:&lt;/p&gt;
257
258 &lt;p&gt;&lt;pre&gt;
259 sudo apt-get install git vmdebootstrap mercurial python-docutils \
260 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
261 u-boot-tools
262 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
263 freedom-maker
264 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
265 &lt;/pre&gt;&lt;/p&gt;
266
267 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
268 devices. See the README in the freedom-maker git repo for more
269 details on the build. If you do not want all three images, trim the
270 make line. Note that the virtualbox-image target is not really
271 virtualbox specific. It create a x86 image usable in kvm, qemu,
272 vmware and any other x86 virtual machine environment. You might need
273 the version of vmdebootstrap in Jessie to get the build working, as it
274 include fixes for a race condition with kpartx.&lt;/p&gt;
275
276 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
277 method, boot a Debian Wheezy ISO and use this boot argument to load
278 the preseed values:&lt;/p&gt;
279
280 &lt;p&gt;&lt;pre&gt;
281 url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&lt;/a&gt;
282 &lt;/pre&gt;&lt;/p&gt;
283
284 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
285 it still work.&lt;/p&gt;
286
287 &lt;p&gt;If you wonder how to help, one task you could look at is using
288 systemd as the boot system. It will become the default for Linux in
289 Jessie, so we need to make sure it is usable on the Freedombox. I did
290 a simple test a few weeks ago, and noticed dnsmasq failed to start
291 during boot when using systemd. I suspect there are other problems
292 too. :) To detect problems, there is a test suite included, which can
293 be run from the plinth web interface.&lt;/p&gt;
294
295 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
296 us get the new release published. :) Please join us on
297 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
298 irc.debian.org)&lt;/a&gt; and
299 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
300 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
301 </description>
302 </item>
303
304 <item>
305 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
306 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
307 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
308 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
309 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
310 project&lt;/a&gt; is working on providing the software and hardware for
311 making it easy for non-technical people to host their data and
312 communication at home, and being able to communicate with their
313 friends and family encrypted and away from prying eyes. It has been
314 going on for a while, and is slowly progressing towards a new test
315 release (0.2).&lt;/p&gt;
316
317 &lt;p&gt;And what day could be better than the Pi day to announce that the
318 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
319 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
320 system), and can also be installed using a Debian installer preseed
321 file. The Debian based Freedombox is now based on Debian Jessie,
322 where most of the needed packages used are already present. Only one,
323 the freedombox-setup package, is missing. To try to build your own
324 boot image to test the current status, fetch the freedom-maker scripts
325 and build using
326 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
327 with a user with sudo access to become root:
328
329 &lt;pre&gt;
330 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
331 freedom-maker
332 sudo apt-get install git vmdebootstrap mercurial python-docutils \
333 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
334 u-boot-tools
335 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
336 &lt;/pre&gt;
337
338 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
339 devices. See the README for more details on the build. If you do not
340 want all three images, trim the make line. But note that thanks to &lt;a
341 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
342 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
343 kpartx call.&lt;/p&gt;
344
345 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
346 method, boot a Debian Wheezy ISO and use this boot argument to load
347 the preseed values:&lt;/p&gt;
348
349 &lt;pre&gt;
350 url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&lt;/a&gt;
351 &lt;/pre&gt;
352
353 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
354 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
355 currently hang while setting up APT sources. Killing the
356 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
357 installation will get the installation going. This affect all
358 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
359
360 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
361 us get the new release published. :) Please join us on
362 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
363 irc.debian.org)&lt;/a&gt; and
364 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
365 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
366 </description>
367 </item>
368
369 <item>
370 <title>Videos about the Freedombox project - for inspiration and learning</title>
371 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
372 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
373 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
374 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
375 project&lt;/a&gt; have been going on for a while, and have presented the
376 vision, ideas and solution several places. Here is a little
377 collection of videos of talks and presentation of the project.&lt;/p&gt;
378
379 &lt;ul&gt;
380
381 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
382 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
383
384 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
385 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
386
387 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
388 Freedom in the Cloud - Software Freedom, Privacy and and Security for
389 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
390 (Youtube)&lt;/li&gt;
391
392 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
393 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
394
395 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
396 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
397
398 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
399 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
400 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
401
402 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
403 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
404 (Youtube)&lt;/li&gt;
405
406 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
407 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
408
409 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
410 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
411
412 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
413 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
414 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
415
416 &lt;/ul&gt;
417
418 &lt;p&gt;A larger list is available from
419 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
420 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
421
422 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
423 Jessie is coming along quite well, and soon both Owncloud and using
424 Tor should be available for testers of the Freedombox solution. :) In
425 a few weeks I hope everything needed to test it is included in Debian.
426 The withsqlite package is already in Debian, and the plinth package is
427 pending in NEW. The third and vital part of that puzzle is the
428 metapackage/setup framework, which is still pending an upload. Join
429 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
430 (#freedombox on irc.debian.org)&lt;/a&gt; and
431 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
432 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
433 </description>
434 </item>
435
436 <item>
437 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
438 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
439 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
440 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
441 <description>&lt;p&gt;I was introduced to the
442 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
443 in 2010, when Eben Moglen presented his vision about serving the need
444 of non-technical people to keep their personal information private and
445 within the legal protection of their own homes. The idea is to give
446 people back the power over their network and machines, and return
447 Internet back to its intended peer-to-peer architecture. Instead of
448 depending on a central service, the Freedombox will give everyone
449 control over their own basic infrastructure.&lt;/p&gt;
450
451 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
452 taken priority. But this summers nasty news about the misuse of trust
453 and privilege exercised by the &quot;western&quot; intelligence gathering
454 communities increased my eagerness to contribute to a point where I
455 actually started working on the project a while back.&lt;/p&gt;
456
457 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
458 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
459 create a simple and cheap Debian based appliance that anyone can hook
460 up in their home and get access to secure and private services and
461 communication. The initial deployment platform have been the
462 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
463 which is a piece of hardware I do not own. So to be able to test what
464 the current Freedombox setup look like, I had to come up with a way to install
465 it on some hardware I do have access to. I have rewritten the
466 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
467 image build framework to use .deb packages instead of only copying
468 setup into the boot images, and thanks to this rewrite I am able to
469 set up any machine supported by Debian Wheezy as a Freedombox, using
470 the previously mentioned deb (and a few support debs for packages
471 missing in Debian).&lt;/p&gt;
472
473 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
474 scripts
475 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
476 and a administrative web interface
477 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
478 withsqlite), as well as a privacy enhancing proxy based on
479 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
480 (freedombox-privoxy). There is also a web/javascript based XMPP
481 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
482 trying (unsuccessfully so far) to talk to the XMPP server
483 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
484 web interface is pluggable, and the goal is to use it to enable OpenID
485 services, mesh network connectivity, use of TOR, etc, etc. Not much of
486 this is really working yet, see
487 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
488 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
489 on github at the moment. The HTTP proxy is operational out of the
490 box, and the admin web interface can be used to add/remove plinth
491 users. I&#39;ve not been able to do anything else with it so far, but
492 know there are several branches spread around github and other places
493 with lots of half baked features.&lt;/p&gt;
494
495 &lt;p&gt;Anyway, if you want to have a look at the current state, the
496 following recipes should work to give you a test machine to poke
497 at.&lt;/p&gt;
498
499 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
500
501 &lt;ol&gt;
502
503 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
504 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
505 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
506 to the Debian installer:&lt;p&gt;
507 &lt;pre&gt;url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat&lt;/a&gt;&lt;/pre&gt;&lt;/li&gt;
508
509 &lt;li&gt;Answer the few language/region/password questions and pick disk to
510 install on.&lt;/li&gt;
511
512 &lt;li&gt;When the installation is finished and the machine have rebooted a
513 few times, your Freedombox is ready for testing.&lt;/li&gt;
514
515 &lt;/ol&gt;
516
517 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
518
519 &lt;ol&gt;
520
521 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
522 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
523 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
524 &lt;pre&gt;
525 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
526 &lt;/pre&gt;&lt;/li&gt;
527 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
528 &lt;pre&gt;
529 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
530 apt-key add -
531 apt-get update
532 apt-get install freedombox-setup
533 /usr/lib/freedombox/setup
534 &lt;/pre&gt;&lt;/li&gt;
535 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
536
537 &lt;/ol&gt;
538
539 &lt;p&gt;You can test it on other architectures too, but because the
540 freedombox-privoxy package is binary, it will only work as intended on
541 the architectures where I have had time to build the binary and put it
542 in my APT repository. But do not let this stop you. It is only a
543 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
544
545 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
546 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
547 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
548 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
549
550 &lt;p&gt;Please let me know if this works for you, or if you have any
551 problems. We gather on the IRC channel
552 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
553 irc.debian.org and the
554 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
555 mailing list&lt;/a&gt;.&lt;/p&gt;
556
557 &lt;p&gt;Once you get your freedombox operational, you can visit
558 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
559 welcome screen (dead end - do not be surprised if you are unable to
560 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
561 to look at the rest of plinth. The default user is &#39;admin&#39; and the
562 default password is &#39;secret&#39;.&lt;/p&gt;
563 </description>
564 </item>
565
566 <item>
567 <title>Netflix krever at du frasier deg dine forbrukerrettigheter...</title>
568 <link>http://people.skolelinux.org/pere/blog/Netflix_krever_at_du_frasier_deg_dine_forbrukerrettigheter___.html</link>
569 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Netflix_krever_at_du_frasier_deg_dine_forbrukerrettigheter___.html</guid>
570 <pubDate>Wed, 17 Oct 2012 15:30:00 +0200</pubDate>
571 <description>&lt;p&gt;Filmtjenesten Netflix lanseres i Norge, med en jublende presse på
572 sidelinjen. Men har journalistene lest bruksvilkårene? Synes de
573 avsnitt nummer to i
574 «&lt;a href=&quot;https://signup.netflix.com/TermsOfUse?locale=nb-NO&quot;&gt;Vilkår
575 for bruk&lt;/a&gt;» høres greit ut for en forbrukertjeneste i Norge?
576 Avsnittet lyder slik:
577
578 &lt;blockquote&gt;
579
580 «Disse vilkårene for bruk innebærer at alle tvister mellom deg og
581 Netflix vil bli løst ved BINDENDE VOLDGIFT. DU SAMTYKKER I AT DU
582 FRASIER DEG ENHVER RETT TIL RETTSLIGE SKRITT for å hevde eller
583 forsvare rettighetene dine under denne kontrakten (med unntak for
584 mindre saker som kan avgjøres i forliksretten). Rettighetene dine vil
585 bli bestemt av en NØYTRAL VOLDGIFTSMANN/MEKLER og IKKE en dommer eller
586 jury, og krav kan ikke framstilles i form av gruppesøksmål. Les
587 gjennom voldgiftsavtalen nedenfor for å finne alle detaljer vedrørende
588 avtalen, slik at du kan se hvordan en eventuell konflikt med Netflix
589 skal håndteres og vil avgjøres.»
590
591 &lt;/blockquote&gt;
592
593 &lt;p&gt;Ikke nok med det, men må akseptere at det er USAs lov som skal
594 regulere bruken, og dermed akseptere å miste norsk forbruker- og
595 personvernlovgiving (hvilket så vidt jeg vet ikke kan gjøres i
596 Norge).&lt;/p&gt;
597
598 &lt;blockquote&gt;
599 «Gjennom å godta disse vilkår for bruk samtykker du i at tolkingen og
600 håndhevelsen av denne voldgiftsavtalen er underlagt den føderale
601 voldgiftsloven i USA, U.S. Federal Arbitration Act, og at både du og
602 Netflix frasier dere retten til en juryprosess eller deltakelse i
603 gruppesøksmål. Denne voldgiftsbetingelsen gjelder selv etter at denne
604 avtalen er oppsagt og Netflix-medlemskapet ditt har opphørt.»
605 &lt;/blockquote&gt;
606
607 &lt;p&gt;En må altså si ja til å frasi seg de vanlige forbrukerrettighetene
608 i Norge for å bruke Netflix. Vilkårene til Netflix vil neppe stå seg
609 i norsk rett, men det er usedvanlig frekt å bare foreslå det, da de
610 aller fleste som leser dem vil anta at vilkårene gjelder med mindre de
611 er svært godt kjent med norsk forbrukerrett. Skal en frasi seg
612 muligheten til å hevde sin rett hvis Netflix lekker personopplysninger
613 (USAs lovgiving er svært mangelfull i forhold til den norske
614 personvernlovgivingen) eller leverer en tjeneste som ikke holder mål?
615 Nei takk. Med slike bruksvilkår takker jeg høflig nei til tilbudet,
616 og de får ikke meg som kunde før de har en helt annen tilnærming mot
617 sine kunder.&lt;/p&gt;
618
619 &lt;p&gt;Oppdatering 2012-10-18: Både
620 &lt;a href=&quot;http://www.aftenposten.no/digital/Netflix-krever-at-du-sier-fra-deg-norske-forbrukerrettigheter-7021182.html&quot;&gt;Aftenposten&lt;/a&gt;,
621 &lt;a href=&quot;http://nrk.no/helse-forbruk-og-livsstil/1.8362951&quot;&gt;NRK&lt;/a&gt; og
622 &lt;a href=&quot;http://www.teknofil.no/artikler/forbrukerradet-slakter-netflix/113679&quot;&gt;Teknofil&lt;/a&gt;
623 har snappet opp saken (dog nevner ikke NRK kilde, så de kan jo ha
624 oppdaget det selv). Veldig bra at flere blir oppmerksom på slike
625 ting. «- Helt hinsides, mener Forbrukerrådet om Netflix&#39;
626 brukervilkår», siterer Aftenposten. Og
627 &lt;a href=&quot;http://www.aftenposten.no/nyheter/Forbrukerombudet-vil-granske-TV-markedet-7021465.html&quot;&gt;Aftenposten&lt;/a&gt;
628 melder videre at Forbrukerrådet vil granske TV-bransjen med bakgrunn i
629 dette.&lt;/p&gt;
630 </description>
631 </item>
632
633 <item>
634 <title>Mer oppfølging fra MPEG-LA om avtale med dem for å kringkaste og publisere H.264-video</title>
635 <link>http://people.skolelinux.org/pere/blog/Mer_oppf_lging_fra_MPEG_LA_om_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html</link>
636 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Mer_oppf_lging_fra_MPEG_LA_om_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html</guid>
637 <pubDate>Thu, 5 Jul 2012 23:50:00 +0200</pubDate>
638 <description>&lt;p&gt;I føljetongen om H.264
639 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html&quot;&gt;forlot
640 jeg leserne i undring&lt;/a&gt; om hvor pakken fra MPEG-LA tok veien, og om
641 hvilke selskaper i Norge som har avtale med MPEG-LA. Da Ryan hos
642 MPEG-LA dro på ferie sendte jeg min melding videre til hans kollega,
643 og dagen etter fikk jeg følgende svar derfra:&lt;/p&gt;
644
645 &lt;p&gt;&lt;blockquote&gt;
646 &lt;p&gt;Date: Fri, 29 Jun 2012 18:32:34 +0000
647 &lt;br&gt;From: Sidney Wolf &amp;lt;SWolf (at) mpegla.com&amp;gt;
648 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
649 &lt;br&gt;Cc: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
650 &lt;br&gt;Subject: RE: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
651
652 &lt;p&gt;Dear Mr. Reinholdtsen,&lt;/p&gt;
653
654 &lt;p&gt;Thank you for your message. As you know, Ryan is currently our of the
655 office, so it will be my pleasure to assist you.&lt;/p&gt;
656
657 &lt;p&gt;Per your request, attached please find an electronic copy of the
658 AVC Patent Portfolio License. Please note that the electronic copy of
659 the License is provided as a convenience and for informational
660 purposes only. When concluding the Licenses, only the hard copies
661 provided by MPEG LA may be used.&lt;/p&gt;
662
663 &lt;p&gt;To your question, MPEG LA lists our Licensees on our website
664 according to each program. The lists are in alphabetical order, so it
665 is very easy to search.&lt;/p&gt;
666
667 &lt;p&gt;I hope that this was helpful. If we can be of additional
668 assistance, please let me know.&lt;/p&gt;
669
670 &lt;p&gt;Kind regards,&lt;/p&gt;
671
672 &lt;p&gt;Sidney A. Wolf
673 &lt;br&gt;Manager, Global Licensing
674 &lt;br&gt;MPEG LA&lt;/p&gt;
675 &lt;/blockquote&gt;&lt;/p&gt;
676
677 &lt;p&gt;Selv om et epostvedlegg er nyttig for mottakeren, så håpet jeg å få
678 et dokument jeg kunne dele med alle leserne av bloggen min, og ikke et
679 som må deles på individuell basis. Opphavsretten krever godkjenning
680 fra rettighetsinnehaver før en kan gjøre slikt, så dermed fulgte jeg
681 opp med et spørsmål om dette var greit.&lt;/p&gt;
682
683 &lt;p&gt;&lt;blockquote&gt;
684 &lt;p&gt;Date: Wed, 4 Jul 2012 20:25:06 +0200
685 &lt;br&gt;From: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
686 &lt;br&gt;To: Sidney Wolf &amp;lt;SWolf (at) mpegla.com&amp;gt;
687 &lt;br&gt;Cc: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
688 &lt;br&gt;Subject: Re: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
689
690 &lt;p&gt;Thank you for your reply.&lt;/p&gt;
691
692 &lt;p&gt;[Sidney Wolf]
693 &lt;br&gt;&amp;gt; Per your request, attached please find an electronic copy of the AVC
694 &lt;br&gt;&amp;gt; Patent Portfolio License. Please note that the electronic copy of
695 &lt;br&gt;&amp;gt; the License is provided as a convenience and for informational
696 &lt;br&gt;&amp;gt; purposes only. When concluding the Licenses, only the hard copies
697 &lt;br&gt;&amp;gt; provided by MPEG LA may be used.&lt;/p&gt;
698
699 &lt;p&gt;This is useful for me to learn, but the reason I asked for the
700 Internet address of the licensing document was to ensure I could
701 publish a link to it when I discuss the topic of H.264 licensing here
702 in Norway, and allow others to verify my observations. I can not do
703 the same with an email attachment. Thus I would like to ask you if it
704 is OK with MPEG LA that I publish this document on the Internet for
705 others to read?&lt;/p&gt;
706
707 &lt;p&gt;&amp;gt; To your question, MPEG LA lists our Licensees on our website
708 &lt;br&gt;&amp;gt; according to each program. The lists are in alphabetical order, so
709 &lt;br&gt;&amp;gt; it is very easy to search.&lt;/p&gt;
710
711 &lt;p&gt;I am afraid this do not help me locate Norwegian companies in the
712 list of Licensees. I do not know the name of all companies and
713 organisations in Norway, and thus do not know how to locate the
714 Norwegian ones on that list.&lt;/p&gt;
715
716 &lt;p&gt;&amp;gt; I hope that this was helpful. If we can be of additional assistance,
717 &lt;br&gt;&amp;gt; please let me know.&lt;/p&gt;
718
719 &lt;p&gt;Absoutely helpful to learn more about how MPEG LA handle licensing.&lt;/p&gt;
720
721 &lt;p&gt;--
722 &lt;br&gt;Happy hacking
723 &lt;br&gt;Petter Reinholdtsen&lt;/p&gt;
724 &lt;/blockquote&gt;&lt;/p&gt;
725
726 &lt;p&gt;Jeg håpet også at det skulle være mulig å få vite hvilke av de
727 mange hundre som har avtale med MPEG-LA om bruk av H.264 som holdt til
728 i Norge. Begge mine håp falt i grus med svaret fra MPEG-LA.
729
730 &lt;p&gt;&lt;blockquote&gt;
731 &lt;p&gt;Date: Thu, 5 Jul 2012 17:42:39 +0000
732 &lt;br&gt;From: Sidney Wolf &amp;lt;SWolf (at) mpegla.com&amp;gt;
733 &lt;br&gt;To: &#39;Petter Reinholdtsen&#39; &amp;lt;pere (at) hungry.com&amp;gt;
734 &lt;br&gt;Cc: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
735 &lt;br&gt;Subject: RE: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
736
737 &lt;p&gt;Dear Mr. Reinholdtsen,&lt;/p&gt;
738
739 &lt;p&gt;Thank you for your reply.&lt;/p&gt;
740
741 &lt;p&gt;We appreciate the additional explanation you have provided and for
742 asking our permission to publish the electronic copy of the License in
743 advance of doing so. Typically, MPEG LA prefers to distribute the
744 electronic copies of our Licenses to interested parties. Therefore,
745 please feel free to send interested parties to the AVC portion of our
746 website, http://www.mpegla.com/main/programs/AVC/Pages/Intro.aspx for
747 their further reference.&lt;/p&gt;
748
749 &lt;p&gt;As previously mentioned, MPEG LA maintains a list of Licensees in good
750 standing on our website according to each program. Due to the large
751 volume of Licensees, it would be administratively impractical to
752 provide this level of detail to interested parties. Therefore, I am
753 afraid we are not in a position to assist you with your request.&lt;/p&gt;
754
755 &lt;p&gt;Kind regards,&lt;/p&gt;
756
757 &lt;p&gt;Sidney A. Wolf
758 &lt;br&gt;Manager, Global Licensing
759 &lt;br&gt;MPEG LA&lt;/p&gt;
760 &lt;/blockquote&gt;&lt;/p&gt;
761
762 &lt;p&gt;Men takket være epostvedlegget kunne jeg søke på Google etter
763 setningen &quot;WHEREAS, a video standard commonly referred to as AVC has
764 been defined and is referred to in this Agreement as the “AVC
765 Standard” (as more fully defined herein below)&quot; som finnes i avtalen,
766 og lokalisere en kopi fra 2007 av
767 &lt;a href=&quot;http://www.sec.gov/Archives/edgar/data/1342960/000119312509050004/dex1024.htm&quot;&gt;lisensavtalen
768 mellom MPEG-LA og DivX, Inc.&lt;/a&gt;, slik at mine lesere kan se hvordan
769 avtalen så ut da. Jeg har ikke sammenlignet tekstene for å se om noe
770 har endret seg siden den tid, men satser på at teksten er representativ.&lt;/p&gt;
771
772 &lt;p&gt;Jeg aner fortsatt ikke hvor FedEx tok veien med pakken fra
773 MPEG-LA.&lt;/p&gt;
774
775 &lt;p&gt;Update 2012-07-06: Jeg er visst ikke den første som forsøker å få
776 klarhet i problemstillinger rundt H.264, og kom nettopp over en veldig
777 interessant bloggpost fra 2010 hos LibreVideo med tittelen
778 &quot;&lt;a href=&quot;http://www.librevideo.org/blog/2010/06/14/mpeg-la-answers-some-questions-about-avch-264-licensing/&quot;&gt;MPEG-LA
779 answers some questions about AVC/H.264 licensing&lt;/a&gt;. Anbefales!&lt;/p&gt;
780 </description>
781 </item>
782
783 <item>
784 <title>Departementenes servicesenter har ingen avtale om bruk av H.264 med MPEG-LA</title>
785 <link>http://people.skolelinux.org/pere/blog/Departementenes_servicesenter_har_ingen_avtale_om_bruk_av_H_264_med_MPEG_LA.html</link>
786 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Departementenes_servicesenter_har_ingen_avtale_om_bruk_av_H_264_med_MPEG_LA.html</guid>
787 <pubDate>Fri, 29 Jun 2012 09:40:00 +0200</pubDate>
788 <description>&lt;p&gt;Da fikk jeg nettopp svar fra
789 &lt;a href=&quot;http://www.dss.dep.no/&quot;&gt;Departementenes servicesenter&lt;/a&gt;
790 (DSS) på
791 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html&quot;&gt;mitt
792 spørsmål om avtale rundt bruk av H.264&lt;/a&gt;. De har ingen avtale med
793 MPEG LA eller dets representanter. Her er svaret.
794
795 &lt;p&gt;&lt;blockquote&gt;
796
797 &lt;p&gt;Date: Fri, 29 Jun 2012 07:04:42 +0000
798 &lt;br&gt;From: Nielsen Mette Haga &amp;lt;Mette-Haga.Nielsen (at) dss.dep.no&amp;gt;
799 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;petter.reinholdtsen (at) ...&amp;gt;
800 &lt;br&gt;CC: Postmottak &amp;lt;Postmottak (at) dss.dep.no&amp;gt;
801 &lt;br&gt;Subject: SV: Innsynsbegjæring om MPEG/H.264-relaterte avtaler&lt;/p&gt;
802
803 &lt;p&gt;DSS har ikke inngått noen egen lisensavtale med MPEG-LA eller noen som
804 representerer MPEG-LA i Norge. Videoløsningen på regjeringen.no er
805 levert av Smartcom:tv. Lisensforholdet rundt H.264 er ikke omtalt i
806 vår avtale med Smartcom.&lt;/p&gt;
807
808 &lt;p&gt;Vennlig hilsen&lt;/p&gt;
809
810 &lt;p&gt;Mette Haga Nielsen
811 &lt;br&gt;Fung. seksjonssjef&lt;/p&gt;
812
813 &lt;p&gt;Departementenes servicesenter&lt;/p&gt;
814
815 &lt;p&gt;Informasjonsforvaltning
816
817 &lt;p&gt;Mobil 93 09 83 51
818 &lt;br&gt;E-post mette-haga.nielsen (at) dss.dep.no&lt;/p&gt;
819 &lt;/blockquote&gt;&lt;/p&gt;
820
821 &lt;p&gt;Hvis den norske regjeringen representert ved DSS ikke har slik
822 avtale, så kan en kanskje konkludere med at det ikke trengs? Jeg er
823 ikke trygg på at det er god juridisk grunn å stå på, men det er i det
824 minste interessant å vite at hverken NRK eller DSS har funnet det
825 nødvendig å ha avtale om bruk av H.264.&lt;/p&gt;
826
827 &lt;p&gt;Det forklarer ikke hvordan de kan ignorere bruksvilkårene knyttet
828 til bruk av opphavsrettsbeskyttet materiale de bruker til
829 videoproduksjon, med mindre slike vilkår kan ignoreres av selskaper og
830 privatpersoner i Norge. Har de lov til å bryte vilkårene, eller har
831 de brutt dem og så langt sluppet unna med det? Jeg aner ikke.&lt;/p&gt;
832 </description>
833 </item>
834
835 <item>
836 <title>MPEG-LA mener NRK må ha avtale med dem for å kringkaste og publisere H.264-video</title>
837 <link>http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html</link>
838 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html</guid>
839 <pubDate>Thu, 28 Jun 2012 20:00:00 +0200</pubDate>
840 <description>&lt;p&gt;Etter at NRK
841 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html&quot;&gt;nektet
842 å spore opp eventuell avtale med MPEG-LA&lt;/a&gt; eller andre om bruk av
843 MPEG/H.264-video etter at jeg &lt;a
844 href=&quot;http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html&quot;&gt;ba
845 om innsyn i slike avtaler&lt;/a&gt;, tenkte jeg at i stedet for å forsøke å
846 få NRK til å finne en slik avtale, så burde det være like enkelt å
847 spørre MPEG-LA om de hadde avtale med NRK. Spørsmålet ble sendt før
848 jeg fikk tips fra Kieran Kunhya om hvor listen over lisensinnehavere
849 &quot;in Good Standing&quot; befant seg. MPEG-LA svarte meg i dag, og kan
850 fortelle at NRK ikke har noen avtale med dem, så da er i det minste det
851 slått fast. Ikke overraskende mener MPEG-LA at det trengs en avtale
852 med MPEG-LA for å streame H.264, men deres rammer er jo
853 rettstilstanden i USA og ikke Norge. Jeg tar dermed den delen av
854 svaret med en klype salt. Jeg er dermed fortsatt ikke klok på om det
855 trengs en avtale, og hvis det trengs en avtale her i Norge, heller
856 ikke sikker på om NRK har en avtale med noen andre enn MPEG-LA som
857 gjør at de ikke trenger avtale direkte med MPEG-LA. Jeg håper NRKs
858 jurister har vurdert dette, og at det er mulig å få tilgang til
859 vurderingen uansett om de trenger en avtale eller ikke.&lt;/p&gt;
860
861 &lt;p&gt;Her er epostutvekslingen med MPEG-LA så langt. Håper ikke
862 utvekslingen fører til NRK plutselig får en litt uventet pakke fra
863 MPEG-LA.&lt;/p&gt;
864
865 &lt;p&gt;&lt;blockquote&gt;
866 &lt;p&gt;Date: Mon, 25 Jun 2012 15:29:37 +0200
867 &lt;br&gt;From: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
868 &lt;br&gt;To: licensing-web (at) mpegla.com
869 &lt;br&gt;Subject: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
870
871 &lt;p&gt;Hi. I have a small question for you, that I hope it is OK that I
872 ask.&lt;/p&gt;
873
874 &lt;p&gt;Is there any license agreements between MPEG-LA and NRK, &amp;lt;URL:
875 &lt;a href=&quot;http://www.nrk.no/&quot;&gt;http://www.nrk.no/&lt;/a&gt; &amp;gt;, the
876 Norwegian national broadcasting cooperation? I am not sure if they
877 need one, and am just curious if such agreeement exist.&lt;/p&gt;
878
879 &lt;p&gt;The postal address is&lt;/p&gt;
880
881 &lt;p&gt;&lt;blockquote&gt;
882 NRK
883 &lt;br&gt;Postbox 8500, Majorstuen
884 &lt;br&gt;0340 Oslo
885 &lt;br&gt;Norway
886 &lt;/blockquote&gt;&lt;/p&gt;
887
888 &lt;p&gt;if it make it easier for you to locate such agreement.&lt;/p&gt;
889
890 &lt;p&gt;Can you tell me how many entities in Norway have an agreement with
891 MPEG-LA, and the name of these entities?&lt;/p&gt;
892
893 &lt;p&gt;--
894 &lt;br&gt;Happy hacking
895 &lt;br&gt;Petter Reinholdtsen
896 &lt;/blockquote&gt;&lt;/p&gt;
897
898 &lt;p&gt;I dag, to dager senere, fikk jeg følgende svar:&lt;/p&gt;
899
900 &lt;p&gt;&lt;blockquote&gt;
901 &lt;p&gt;Date: Thu, 28 Jun 2012 14:11:17 +0000
902 &lt;br&gt;From: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&gt;
903 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&gt;
904 &lt;br&gt;CC: MD Administration &amp;lt;MDAdministration (at) mpegla.com&gt;
905 &lt;br&gt;Subject: RE: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
906
907 &lt;p&gt;Dear Mr. Reinholdtsen,&lt;/p&gt;
908
909 &lt;p&gt;Thank you for your message and for your interest in MPEG LA. We
910 appreciate hearing from you and I will be happy to assist you.&lt;/p&gt;
911
912 &lt;p&gt;To begin, I will assume that you are referring to AVC/H.264
913 technology in your message below, as this technology is commonly used
914 in the transmission of video content. In that case, please allow me
915 to briefly summarize the coverage provided by our AVC Patent Portfolio
916 License.&lt;/p&gt;
917
918 &lt;P&gt;Our AVC License provides coverage for end products and video
919 services that make use of AVC/H.264 technology. Accordingly, the
920 party offering such end products and video to End Users concludes the
921 AVC License and is responsible for paying the applicable royalties
922 associated with the end products/video they offer.&lt;/p&gt;
923
924 &lt;p&gt;While the Norwegian Broadcast Corporation (NRK) is not currently a
925 Licensee to MPEG LA&#39;s AVC License (or any other Portfolio License
926 offered by MPEG LA), if NRK offers AVC Video to End Users for
927 remuneration (for example, Title-by-Title, Subscription, Free
928 Television, or Internet Broadcast AVC Video), then NRK will need to
929 conclude the AVC License and may be responsible for paying applicable
930 royalties associated with the AVC Video it distributes.&lt;/p&gt;
931
932 &lt;p&gt;Today I will send you a FedEx package containing a copy of our AVC
933 License for your review. You should receive the License document
934 within the next few days.&lt;/p&gt;
935
936 &lt;p&gt;Meanwhile, MPEG LA currently has several Norwegian Licensees that
937 can be found under the &quot;Licensees&quot; header within the respective
938 portion of our website. For example, you may find our list of
939 Licensees in Good Standing to our AVC License in the AVC portion of
940 our website,
941 &lt;a href=&quot;http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx&quot;&gt;http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx&lt;/a&gt;&lt;/p&gt;
942
943 &lt;p&gt;I hope the above information is helpful. If you have additional
944 questions or need further assistance with the AVC License, please feel
945 free to contact me directly. I look forward to hearing from you again
946 soon.&lt;/p&gt;
947
948 &lt;p&gt;Best regards,&lt;/p&gt;
949
950 &lt;p&gt;Ryan&lt;/p&gt;
951
952 &lt;p&gt;Ryan M. Rodriguez
953 &lt;br&gt;Licensing Associate
954 &lt;br&gt;MPEG LA
955 &lt;br&gt;5425 Wisconsin Avenue
956 &lt;br&gt;Suite 801
957 &lt;br&gt;Chevy Chase, MD 20815
958 &lt;br&gt;U.S.A.
959 &lt;br&gt;Phone: +1 (301) 986-6660 x211
960 &lt;br&gt;Fax: +1 (301) 986-8575
961 &lt;br&gt;Email: rrodriguez (at) mpegla.com&lt;/p&gt;
962
963 &lt;/blockquote&gt;&lt;/p&gt;
964
965 &lt;p&gt;Meldingen om utsendt FedEx-pakke var så merkelig at jeg
966 øyeblikkelig sendte svar tilbake og spurte hva i alle dager han mente,
967 da han jo ikke hadde fått noen postadresse som nådde meg.&lt;/p&gt;
968
969 &lt;p&gt;&lt;blockquote&gt;
970
971 &lt;p&gt;Date: Thu, 28 Jun 2012 16:36:15 +0200
972 &lt;br&gt;From: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
973 &lt;br&gt;To: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
974 &lt;br&gt;Cc: MD Administration &amp;lt;MDAdministration (at) mpegla.com&amp;gt;
975 &lt;br&gt;Subject: Re: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
976
977 &lt;p&gt;[Ryan Rodriguez]
978 &lt;br&gt;&amp;gt; Dear Mr. Reinholdtsen,&lt;/p&gt;
979
980 &lt;p&gt;Thank you for your quick reply.&lt;/p&gt;
981
982 &lt;p&gt;&amp;gt; Today I will send you a FedEx package containing a copy of our AVC
983 &lt;br&gt;&amp;gt; License for your review. You should receive the License document
984 &lt;br&gt;&amp;gt; within the next few days.&lt;/p&gt;
985
986 &lt;p&gt;The part about sending a FedEx package confused me, though. I did not
987 &lt;br&gt;give you my address, nor am I associated with NRK in any way, so I hope
988 &lt;br&gt;you did not try to send me a package using the address of NRK. If you
989 &lt;br&gt;would send me the Internet address of to the document, it would be more
990 &lt;br&gt;useful to me to be able to download it as an electronic document.&lt;/p&gt;
991
992 &lt;p&gt;&amp;gt; Meanwhile, MPEG LA currently has several Norwegian Licensees that can
993 &lt;br&gt;&amp;gt; be found under the &quot;Licensees&quot; header within the respective portion
994 &lt;br&gt;&amp;gt; of our website. For example, you may find our list of Licensees in
995 &lt;br&gt;&amp;gt; Good Standing to our AVC License in the AVC portion of our website,
996 &lt;br&gt;&amp;gt; http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx&lt;/p&gt;
997
998 &lt;p&gt;How can I recognize the Norwegian licensees?&lt;/p&gt;
999
1000 &lt;p&gt;--
1001 &lt;br&gt;Happy hacking
1002 &lt;br&gt;Petter Reinholdtsen&lt;/p&gt;
1003 &lt;/blockquote&gt;&lt;/p&gt;
1004
1005 &lt;p&gt;Selv om jeg svarte kun noen minutter etter at jeg fikk eposten fra
1006 MPEG-LA, fikk jeg eposten under som automatisk var beskjed på min
1007 siste epost. Får håpe noen likevel følger opp &quot;FedEx-pakken&quot;. For å
1008 øke sjansen for at noen revurderer utsending av pakke uten mottaker,
1009 videresendte jeg min epost til swolf (at) mpegla.com, så får vi se.
1010 Har ikke hørt noe mer 3 timer senere, så jeg mistenker at ingen leste
1011 min epost tidsnok.&lt;/p&gt;
1012
1013 &lt;p&gt;&lt;blockquote&gt;
1014
1015 &lt;p&gt;Date: Thu, 28 Jun 2012 14:36:20 +0000
1016 &lt;br&gt;From: Ryan Rodriguez &amp;lt;RRodriguez (at) mpegla.com&amp;gt;
1017 &lt;br&gt;To: Petter Reinholdtsen &amp;lt;pere (at) hungry.com&amp;gt;
1018 &lt;br&gt;Subject: Automatic reply: Do NRK have a license agreement with MPEG-LA?&lt;/p&gt;
1019
1020 &lt;p&gt;Thank you for your message.&lt;/p&gt;
1021
1022 &lt;p&gt;I will be out of the office until Thursday, July 5 and will respond
1023 to all messages upon my return. If this is a matter that requires
1024 immediate attention, please contact Sidney Wolf (swolf (at)
1025 mpegla.com)&lt;/p&gt;
1026
1027 &lt;p&gt;Best regards,&lt;/p&gt;
1028
1029 &lt;p&gt;Ryan&lt;/p&gt;
1030
1031 &lt;p&gt;Ryan M. Rodriguez
1032 &lt;br&gt;Licensing Associate
1033 &lt;br&gt;MPEG LA&lt;/p&gt;
1034
1035 &lt;/blockquote&gt;&lt;/p&gt;
1036
1037 &lt;p&gt;Litt klokere, men fortsatt ikke klok på mitt opprinnelige spørsmål,
1038 som er om en trenger avtale med MPEG-LA for å publisere eller
1039 kringkaste H.264-video i Norge.&lt;/p&gt;
1040 </description>
1041 </item>
1042
1043 <item>
1044 <title>NRK nekter å finne og utlevere eventuell avtale med MPEG-LA</title>
1045 <link>http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html</link>
1046 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html</guid>
1047 <pubDate>Mon, 25 Jun 2012 15:10:00 +0200</pubDate>
1048 <description>&lt;p&gt;Jeg fikk nettopp svar fra NRK på
1049 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html&quot;&gt;min
1050 forespørsel om kopi av avtale&lt;/a&gt; med MPEG-LA eller andre om bruk av
1051 MPEG og/eller H.264. Svaret har fått saksreferanse 2011/371 (mon tro
1052 hva slags sak fra 2011 dette er?) hos NRK og lyder som følger:&lt;/p&gt;
1053
1054 &lt;p&gt;&lt;blockquote&gt;
1055
1056 &lt;p&gt;&lt;strong&gt;Svar på innsynsbegjæring i MPEG / H.264-relaterte
1057 avtaler&lt;/strong&gt;&lt;/p&gt;
1058
1059 &lt;p&gt;Viser til innsynsbegjæring av 19. juni 2012. Kravet om innsyn
1060 gjelder avtale som gjør at NRK «ikke er begrenset av de generelle
1061 bruksvilkårene som gjelder for utstyr som bruker MPEG og/eller
1062 H.264».&lt;/p&gt;
1063
1064 &lt;p&gt;I henhold til offentleglova § 28 annet ledd må innsynskravet gjelde
1065 en bestemt sak eller i rimelig utstrekning saker av en bestemt
1066 sak. Det er på det rene at det aktuelle innsynskravet ikke gjelder en
1067 bestemt sak. Spørsmålet som reiser seg er om identifiseringsgraden er
1068 tilstrekkelig. I Justisdepartementets «Rettleiar til offentleglova»
1069 står følgende:&lt;/p&gt;
1070
1071 &lt;p&gt;«Kravet om at innsynskravet må gjelde ei bestemt sak er til hinder
1072 for at eit innsynskrav kan gjelde alle saker av ein bestemt art, utan
1073 at den enkelte saka blir identifisert. Ein kan med andre ord i
1074 utgangspunktet ikkje krevje innsyn i til dømes alle saker om
1075 utsleppsløyve hos Statens forureiningstilsyn frå dei siste tre åra,
1076 med mindre ein identifiserer kvar enkelt sak, til dømes med tilvising
1077 til dato, partar eller liknande.»&lt;/p&gt;
1078
1079 &lt;p&gt;Vedrørende denne begrensningen har Justisdepartementet uttalt
1080 følgende (Lovavdelingens uttalelser JDLOV-2010-3295):&lt;/p&gt;
1081
1082 &lt;p&gt;&lt;em&gt;«Bakgrunnen for avgrensinga av kva innsynskravet kan gjelde,
1083 er fyrst og fremst at meir generelle innsynskrav, utan noka form for
1084 identifikasjon av kva ein eigentleg ynskjer, ville vere svært
1085 vanskelege å handsame for forvaltninga.»&lt;/em&gt;&lt;/p&gt;
1086
1087 &lt;p&gt;I samme sak uttaler Lovavdelingen følgende:&lt;/p&gt;
1088
1089 &lt;p&gt;&lt;em&gt;«Det følgjer vidare av offentleglova § 28 andre ledd at det `i
1090 rimeleg utstrekning&#39; kan krevjast innsyn i `saker av ein bestemt
1091 art&#39;. Vilkåret om at eit innsynskrav berre `i rimeleg utstrekning&#39; kan
1092 gjelde saker av ein bestemt art, er i hovudsak knytt til kor
1093 arbeidskrevjande det vil vere å finne fram til dei aktuelle
1094 dokumenta. I tillegg reknar vi med at vilkåret kan gje grunnlag for å
1095 nekte innsyn i tilfelle der innsynskravet er så omfattande (gjeld så
1096 mange dokument) at arbeidsmengda som ville gått med til å handsame
1097 det, er større enn det ein `i rimeleg utstrekning&#39; kan krevje (sjølv
1098 om det nok skal mykje til).»&lt;/em&gt;&lt;/p&gt;
1099
1100 &lt;p&gt;NRK har ikke noen egen sammenstilling over avtaler innenfor
1101 bestemte områder som omtales i innsynsbegjæringen. De måtte søkes på
1102 vanlig måte. I tillegg finnes ikke noen automatisert måte å finne
1103 avtaler som «ikke er begrenset av de generelle bruksvilkårene som
1104 gjelder for utstyr som bruker MPEG og/eller H.264». En slik
1105 gjennomgang av avtaler måtte gjøres manuelt av en person med
1106 spesialistkunnskap. Dette vil kreve at NRK avsetter omfattende
1107 ressurser for å finne frem relevante avtaler og for deretter å vurdere
1108 om de dekkes av det innsynsbegjæringen omfattes.&lt;/p&gt;
1109
1110 &lt;p&gt;På bakgrunn av dette nekter NRK innsyn, med den begrunnelsen at
1111 innsynskravet er så omfattende at arbeidsmengden for å håndtere kravet
1112 vil være langt større enn det som i rimelig utstrekning kan kreves i
1113 henhold til offentleglova § 28 annet ledd.&lt;/p&gt;
1114
1115 &lt;p&gt;Avslag på deres innsynsbegjæring kan påklages til Kultur- og
1116 kirkedepartementet innen tre uker fra det tidspunkt avslaget kommer
1117 frem til mottakeren, i henhold til reglene i offentleglova § 32,
1118 jf. forvaltningsloven kapittel VI. Klagen skal stiles til Kultur- og
1119 kirkedepartementet, og sendes til NRK.&lt;/p&gt;
1120
1121 &lt;p&gt;NRK er imidlertid etter Offentleglova forpliktet å gi ut journaler,
1122 slik at en eventuell søknad om innsyn kan tydeligere identifisere
1123 hvilke dokumenter som det ønskes innsyn i. NRKs offentlige journaler
1124 for inneværende og forrige måned ligger ute på
1125 NRK.no/innsyn. Journaler som går lengre tilbake i tid, kan sendes ut
1126 på forespørsel til innsyn (at) nrk.no.&lt;/p&gt;
1127
1128 &lt;p&gt;Med hilsen
1129 &lt;br&gt;Dokumentarkivet i NRK
1130 &lt;br&gt;v/ Elin Brandsrud
1131 &lt;br&gt;Tel. direkte: 23 04 29 29
1132 &lt;br&gt;Post: RBM3, Postboks 8500 Majorstuen, 0340 Oslo
1133 &lt;br&gt;innsyn (at) nrk.no&lt;/p&gt;
1134
1135 &lt;/blockquote&gt;&lt;/p&gt;
1136
1137 &lt;p&gt;Svaret kom
1138 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2012-06-25-video-mpegla-nrk.pdf&quot;&gt;i
1139 PDF-form som vedlegg på epost&lt;/a&gt;. Jeg er litt usikker på hvordan jeg
1140 best går videre for å bli klok, men jeg har jo i hvert fall tre uker
1141 på å vurdere om jeg skal klage. Enten må nok forespørselen
1142 reformuleres eller så må jeg vel klage. Synes jo det er merkelig at
1143 NRK ikke har bedre kontroll med hvilke avtaler de har inngått. Det
1144 burde jo være noen i ledelsen som vet om de har signert en avtale med
1145 MPEG-LA eller ikke...&lt;/p&gt;
1146
1147 &lt;p&gt;Oppdatering 2012-06-25 20:20: Et google-søk på &quot;2011/371 nrk&quot;
1148 sendte meg til postjournalen for
1149 &lt;a href=&quot;http://nrk.no/contentfile/file/1.8212365!offentligjournal19062012.pdf&quot;&gt;2012-06-19&lt;/a&gt;
1150 og
1151 &lt;a href=&quot;http://nrk.no/contentfile/file/1.8214156!offentligjournal20062012.pdf&quot;&gt;2012-06-20&lt;/a&gt;
1152 hos NRK som viser mine forespørsler og viser at sakens tittel hos NRK
1153 er &quot;Graphic Systems Regions MA 2378/10E&quot;. Videre søk etter &quot;Graphic
1154 Systems Regions&quot; viser at dette er saken til et anbud om
1155 &quot;&lt;a href=&quot;http://no.mercell.com/m/mts/Tender/27179412.aspx&quot;&gt;a graphics
1156 system for 12 or 13 sites broadcasting regional news&lt;/a&gt;&quot; hos Mercell
1157 Sourcing Service, også omtalt på
1158 &lt;a href=&quot;http://www.publictenders.net/tender/595705&quot;&gt;Public
1159 Tenders&lt;/a&gt; og
1160 &lt;a href=&quot;http://www.doffin.no/search/show/search_view.aspx?ID=JAN155521&quot;&gt;Doffin&lt;/a&gt;.
1161 Jeg er dog usikker på hvordan dette er relatert til min
1162 forespørsel.&lt;/p&gt;
1163
1164 &lt;p&gt;Oppdatering 2012-06-25 22:40: Ble tipset av Kieran Kunhya, fra
1165 miljøet rundt
1166 &lt;a href=&quot;http://code.google.com/p/open-broadcast-encoder/&quot;&gt;Open
1167 Broadcast Encoder&lt;/a&gt;, at listen over de som har lisensavtale med
1168 MPEG-LA er
1169 &lt;a href=&quot;http://www.mpeg-la.com/main/programs/AVC/Pages/Licensees.aspx&quot;&gt;tilgjengelig
1170 på web&lt;/a&gt;. Veldig fint å oppdage hvor den finnes, da jeg må ha lett
1171 etter feil ting da jeg forsøke å finne den. Der står ikke NRK, men
1172 flere andre &quot;Broadcasting Company&quot;-oppføringer. Lurer på om det betyr
1173 at NRK ikke trenger avtale, eller noe helt annet?&lt;/p&gt;
1174 </description>
1175 </item>
1176
1177 <item>
1178 <title>Trenger en avtale med MPEG-LA for å publisere og kringkaste H.264-video?</title>
1179 <link>http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html</link>
1180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html</guid>
1181 <pubDate>Thu, 21 Jun 2012 13:40:00 +0200</pubDate>
1182 <description>&lt;p&gt;Trengs det avtale med MPEG-LA for å ha lovlig rett til å
1183 distribuere og kringkaste video i MPEG4 eller med videokodingen H.264?
1184 &lt;a href=&quot;http://webmink.com/essays/h-264/&quot;&gt;H.264 og MPEG4 er jo ikke en
1185 fri og åpen standard&lt;/a&gt; i henhold til
1186 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html&quot;&gt;definisjonen
1187 til Digistan&lt;/a&gt;, så i enkelte land er det ingen tvil om at du må ha
1188 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
1189 gjelder Norge. Det ser uansett ut til å være en juridisk interessant
1190 problemstilling. Men jeg tenkte her om dagen som så, at hvis det er
1191 nødvendig, så har store aktører som
1192 &lt;a href=&quot;http://www.nrk.no/&quot;&gt;NRK&lt;/a&gt; og
1193 &lt;a href=&quot;http://www.regjeringen.no/&quot;&gt;regjeringen&lt;/a&gt; skaffet seg en
1194 slik avtale. Jeg har derfor sendt forespørsel til begge (for
1195 regjeringen sin del er det Departementenes Servicesenter som gjør
1196 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
1197 og/eller H.264 med MPEG-LA eller andre aktører som opererer på vegne
1198 av MPEG-LA. Her er kopi av eposten jeg har sendt til
1199 &lt;a href=&quot;http://www.dss.dep.no/&quot;&gt;Departementenes Servicesenter&lt;/a&gt;.
1200 Forespørselen til NRK er veldig lik.&lt;/p&gt;
1201
1202 &lt;p&gt;&lt;blockquote&gt;
1203
1204 &lt;p&gt;Date: Tue, 19 Jun 2012 15:18:33 +0200
1205 &lt;br&gt;From: Petter Reinholdtsen
1206 &lt;br&gt;To: postmottak@dss.dep.no
1207 &lt;br&gt;Subject: Innsynsbegjæring om MPEG/H.264-relaterte avtaler
1208
1209 &lt;p&gt;Hei. Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
1210 til avtaler rundt bruk av videoformatene MPEG og H.264. Jeg er
1211 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
1212 eller noen som representerer MPEG-LA i Norge.&lt;/p&gt;
1213
1214 &lt;p&gt;MPEG og H.264 er videoformater som brukes både til kringkasting
1215 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
1216 via Adobe Flash. MPEG-LA, &amp;lt;URL:
1217 &lt;a href=&quot;http://www.mpeg-la.com/&quot;&gt;http://www.mpeg-la.com/&lt;/a&gt; &amp;gt;, er
1218 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
1219 av immaterielle rettigheter knyttet til MPEG og H.264, å selge
1220 bruksrett for MPEG og H.264.&lt;/p&gt;
1221
1222 &lt;p&gt;Via regjeringen.no kringkastes med MPEG og H.264-baserte
1223 videoformater, og dette ser ut til å være organisert av DSS. Jeg
1224 antar dermed at DSS har avtale med en eller annen aktør om dette.&lt;/p&gt;
1225
1226 &lt;p&gt;F.eks. har Adobe Premiere Pro har følgende klausul i følge &amp;lt;URL:
1227 &lt;a href=&quot;http://news.cnet.com/8301-30685_3-20000101-264.html&quot;&gt;http://news.cnet.com/8301-30685_3-20000101-264.html&lt;/a&gt;
1228 &amp;gt;:&lt;/p&gt;
1229
1230 &lt;p&gt;&lt;blockquote&gt;
1231
1232 &lt;p&gt;6.17. AVC DISTRIBUTION. The following notice applies to software
1233 containing AVC import and export functionality: THIS PRODUCT IS
1234 LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
1235 NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
1236 WITH THE AVC STANDARD (&quot;AVC VIDEO&quot;) AND/OR (b) DECODE AVC VIDEO THAT
1237 WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
1238 ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
1239 LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
1240 IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
1241 FROM MPEG LA L.L.C. SEE
1242 &lt;a href=&quot;http://www.mpegla.com&quot;&gt;http://www.mpegla.com&lt;/a&gt;.&lt;/p&gt;
1243
1244 &lt;/blockquote&gt;&lt;/p&gt;
1245
1246 &lt;p&gt;Her er det kun &quot;non-commercial&quot; og &quot;personal and non-commercial&quot;
1247 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.&lt;/p&gt;
1248
1249 &lt;p&gt;Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
1250 følgende klausul i følge &amp;lt;URL:
1251 &lt;a href=&quot;http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf&quot;&gt;http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf&lt;/a&gt;
1252 &amp;gt;:&lt;/p&gt;
1253
1254 &lt;p&gt;&lt;blockquote&gt;
1255
1256 &lt;p&gt;15. Merknad om H.264/AVC. Hvis Apple-programvaren inneholder
1257 funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
1258 kommersiell bruk ekstra lisensiering og følgende gjelder:
1259 AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
1260 FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
1261 KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN (&quot;AVC-VIDEO&quot;)
1262 OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
1263 PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
1264 FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
1265 AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
1266 FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.&lt;/p&gt;
1267 &lt;/blockquote&gt;&lt;/p&gt;
1268
1269 &lt;p&gt;Tilsvarende gjelder for andre programvarepakker, kamera, etc som
1270 bruker MPEG og H.264, at en må ha en avtale med MPEG-LA for å ha lov
1271 til å bruke programmet/utstyret hvis en skal lage noe annet enn
1272 private filmer og i ikke-kommersiell virksomhet.&lt;/p&gt;
1273
1274 &lt;p&gt;Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
1275 ikke er begrenset av de generelle bruksvilkårene som gjelder for
1276 utstyr som bruker MPEG og/eller H.264.&lt;/p&gt;
1277 &lt;/blockquote&gt;&lt;/p&gt;
1278
1279 &lt;p&gt;Nå venter jeg spent på svaret. Jeg planlegger å blogge om svaret
1280 her.&lt;/p&gt;
1281 </description>
1282 </item>
1283
1284 <item>
1285 <title>Veileder fra DIFI om publisering av offentlige data</title>
1286 <link>http://people.skolelinux.org/pere/blog/Veileder_fra_DIFI_om_publisering_av_offentlige_data.html</link>
1287 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Veileder_fra_DIFI_om_publisering_av_offentlige_data.html</guid>
1288 <pubDate>Fri, 1 Jun 2012 10:40:00 +0200</pubDate>
1289 <description>&lt;p&gt;På onsdag rakk jeg såvidt innom
1290 &lt;a href=&quot;http://www.meetup.com/osloopendata/&quot;&gt;Oslo Open Data Forums&lt;/a&gt;
1291 møte, og fikk lagt hendene mine på DIFIs helt nye veileder
1292 &quot;&lt;a href=&quot;http://veileder.data.norge.no/&quot;&gt;Åpne data. Del og skap
1293 verdier. Veileder i tilgjengeliggjøring av offentlig data&lt;/a&gt;&quot; (også
1294 &lt;a href=&quot;http://www.difi.no/filearchive/veileder-i-tilgjengeliggjoring-av-offentlig-data-web.pdf&quot;&gt;tilgjengelig
1295 som PDF&lt;/a&gt; fra DIFI).&lt;/p&gt;
1296
1297 &lt;p&gt;Veilederen er veldig bra, og nevner viktige problemstillinger og
1298 skisserer f.eks. både verdiskapningspotensialet og formatmulighetene
1299 som en bør ha i bakhodet når en publiserer offentlig informasjon på
1300 maskinlesbart format. Kildekoden til veilederen er
1301 &lt;a href=&quot;https://github.com/difi/veileder-opnedata&quot;&gt;tilgjengelig via
1302 github&lt;/a&gt;, og en kan rapportere tilbakemeldinger og forslag til
1303 forbedringer der (eller via epost og twitter for de som ønsker
1304 det).&lt;/p&gt;
1305
1306 &lt;p&gt;Det eneste jeg virkelig savnet i veilederen var omtale av
1307 &lt;a href=&quot;http://www.w3.org/DesignIssues/LinkedData.html&quot;&gt;w3cs
1308 stjerneklassifisering&lt;/a&gt; av åpne datakilder, som jeg tror ville være
1309 nyttige mentale knagger for de som vurderer å publisere sin
1310 informasjon på som åpne data. Jeg har
1311 &lt;a href=&quot;https://github.com/difi/veileder-opnedata/issues/1&quot;&gt;rapportert
1312 en github-bug&lt;/a&gt; om dette, så får vi se hvordan den blir behandlet.&lt;/p&gt;
1313
1314 &lt;p&gt;Det slo meg at det var veldig lite konkret i veilederen om valg av
1315 bruksvilkår ved publisering (aka lisens), men jeg er ikke sikker på om
1316 det hører hjemme der, da det er et vanskelig tema som kanskje heller
1317 hører hjemme i sin egen veileder. Uansett, anbefaler alle å ta en
1318 titt på veilederen og sikre at alle offentlige etater en har kontakt
1319 med får en kopi.&lt;/p&gt;
1320 </description>
1321 </item>
1322
1323 <item>
1324 <title>HTC One X - Your video? What do you mean?</title>
1325 <link>http://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html</link>
1326 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html</guid>
1327 <pubDate>Thu, 26 Apr 2012 13:20:00 +0200</pubDate>
1328 <description>&lt;p&gt;In &lt;a href=&quot;http://www.idg.no/computerworld/article243690.ece&quot;&gt;an
1329 article today&lt;/a&gt; published by Computerworld Norway, the photographer
1330 &lt;a href=&quot;http://www.urke.com/eirik/&quot;&gt;Eirik Helland Urke&lt;/a&gt; reports
1331 that the video editor application included with
1332 &lt;a href=&quot;http://www.htc.com/www/smartphones/htc-one-x/#specs&quot;&gt;HTC One
1333 X&lt;/a&gt; have some quite surprising terms of use. The article is mostly
1334 based on the twitter message from mister Urke, stating:
1335
1336 &lt;p&gt;&lt;blockquote&gt;
1337 &quot;&lt;a href=&quot;http://twitter.com/urke/status/194062269724897280&quot;&gt;Drøy
1338 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
1339 kan jeg KUN bruke dem privat.&lt;/a&gt;&quot;
1340 &lt;/blockquote&gt;&lt;/p&gt;
1341
1342 &lt;p&gt;I quickly translated it to this English message:&lt;/p&gt;
1343
1344 &lt;p&gt;&lt;blockquote&gt;
1345 &quot;Arrogant user agreement: HTC can use MY edited videos
1346 commercially. Although I can ONLY use them privately.&quot;
1347 &lt;/blockquote&gt;&lt;/p&gt;
1348
1349 &lt;p&gt;I&#39;ve been unable to find the text of the license term myself, but
1350 suspect it is a variation of the MPEG-LA terms I
1351 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html&quot;&gt;discovered
1352 with my Canon IXUS 130&lt;/a&gt;. The HTC One X specification specifies that
1353 the recording format of the phone is .amr for audio and .mp3 for
1354 video. AMR is
1355 &lt;a href=&quot;http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues&quot;&gt;Adaptive
1356 Multi-Rate audio codec&lt;/a&gt; with patents which according to the
1357 Wikipedia article require an license agreement with
1358 &lt;a href=&quot;http://www.voiceage.com/&quot;&gt;VoiceAge&lt;/a&gt;. MP4 is
1359 &lt;a href=&quot;http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Patent_licensing&quot;&gt;MPEG4 with
1360 H.264&lt;/a&gt;, which according to Wikipedia require a licence agreement
1361 with &lt;a href=&quot;http://www.mpegla.com/&quot;&gt;MPEG-LA&lt;/a&gt;.&lt;/p&gt;
1362
1363 &lt;p&gt;I know why I prefer
1364 &lt;a href=&quot;http://www.digistan.org/open-standard:definition&quot;&gt;free and open
1365 standards&lt;/a&gt; also for video.&lt;/p&gt;
1366 </description>
1367 </item>
1368
1369 <item>
1370 <title>Changing the default Iceweasel start page in Debian Edu/Squeeze</title>
1371 <link>http://people.skolelinux.org/pere/blog/Changing_the_default_Iceweasel_start_page_in_Debian_Edu_Squeeze.html</link>
1372 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Changing_the_default_Iceweasel_start_page_in_Debian_Edu_Squeeze.html</guid>
1373 <pubDate>Tue, 10 Jan 2012 15:30:00 +0100</pubDate>
1374 <description>&lt;p&gt;In the Squeeze version of
1375 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; soon
1376 to be released, users of the system will get their default browser
1377 start page set from LDAP, allowing the system administrator to point
1378 all users to the school web page by updating one setting in LDAP. In
1379 addition to setting the default start page when a machine boots, users
1380 are shown the same page as a welcome page when they log in for the
1381 first time.&lt;/p&gt;
1382
1383 &lt;p&gt;The LDAP object dc=skole,dc=skolelinux,dc=no have an attribute
1384 labeledURI with &quot;http://www/ LDAP for Debian Edu/Skolelinux&quot; as the
1385 default content. By changing this value to another URL, all users get
1386 to see the page behind this new URL.&lt;/p&gt;
1387
1388 &lt;p&gt;An easy way to update it is by using the ldapvi tool. It can be
1389 called as &quot;&lt;tt&gt;ldapvi -ZD &#39;(cn=admin)&#39;&lt;/tt&gt;&#39; to update LDAP with the
1390 new setting.&lt;/p&gt;
1391
1392 &lt;p&gt;We have written the code to adjust the default start page and show
1393 the welcome page, and I wonder if there is an easier way to do this
1394 from within Iceweasel instead.&lt;/p&gt;
1395 </description>
1396 </item>
1397
1398 <item>
1399 <title>Hvordan enkelt laste ned filmer fra NRK</title>
1400 <link>http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html</link>
1401 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html</guid>
1402 <pubDate>Sat, 5 Nov 2011 15:20:00 +0100</pubDate>
1403 <description>&lt;p&gt;Ofte har jeg lyst til å laste ned et innslag fra NRKs nettsted for
1404 å se det senere når jeg ikke er på nett, eller for å ha det
1405 tilgjengelig når jeg en gang i fremtiden ønsker å referere til
1406 innslaget selv om NRK har fjernet det fra sine nettsider. I dag fant
1407 jeg et lite script som fikser jobben.&lt;/p&gt;
1408
1409 &lt;p&gt;Scriptet er laget av Jan Henning Thorsen og tilgjengelig fra
1410 &lt;a href=&quot;http://jhthorsen.github.com/snippets/nrk-downloader/&quot;&gt;github&lt;/a&gt;,
1411 og gjør det veldig enkelt å laste ned. Kjør &lt;tt&gt;nrk-downloader.sh
1412 http://www1.nrk.no/nett-tv/klipp/582810&lt;/tt&gt; for å hente ned et enkelt
1413 innslag eller &lt;tt&gt;nrk-downloader.sh
1414 http://www1.nrk.no/nett-tv/kategori/3521&lt;/tt&gt; for å laste ned alle
1415 episodene i en serie.&lt;/p&gt;
1416
1417 &lt;p&gt;Det er ikke rakettforskning å laste ned NRK-&quot;strømmer&quot;, og
1418 tidligere gjorde jeg dette manuelt med mplayer. Scriptet til
1419 Hr. Thorsen gjør det raskere og enklere for meg, men jeg vil ikke si
1420 at det er en revolusjonerende løsning. Jeg mener jo fortsatt at
1421 påstanden fra NRKs ansatte om at det er
1422 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html&quot;&gt;vesensforskjellig
1423 å legge tilgjengelig for nedlasting og for streaming&lt;/a&gt; er
1424 meningsløs.&lt;/p&gt;
1425 </description>
1426 </item>
1427
1428 <item>
1429 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
1430 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
1431 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
1432 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
1433 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
1434 mentioned the issues I believe should be improved in Debian for its
1435 desktop to be useful for more people. The use case for this is my
1436 parents, which are currently running Kubuntu which solve the
1437 issues.&lt;/p&gt;
1438
1439 &lt;p&gt;I suspect these four missing features are not very hard to
1440 implement. After all, they are present in Ubuntu, so if we wanted to
1441 do this in Debian we would have a source.&lt;/p&gt;
1442
1443 &lt;ol&gt;
1444
1445 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
1446 are new packages available for upgrades, a icon in the KDE status bar
1447 indicate this, and clicking on it will activate the simple upgrade
1448 tool to handle it. I have no problem guiding both of my parents
1449 through the process over the phone. If a kernel reboot is required,
1450 this too is indicated by the status bars and the upgrade tool. Last
1451 time I checked, nothing with the same features was working in KDE in
1452 Debian.&lt;/li&gt;
1453
1454 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
1455 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
1456 currently have a handler for, it will ask the user if the system
1457 should search for a package that would add support for this MIME type,
1458 and if the user say yes, the APT sources will be searched for packages
1459 advertising the MIME type in their control file (visible in the
1460 Packages file in the APT archive). If one or more packages are found,
1461 it is a simple click of the mouse to add support for the missing mime
1462 type. If the package require the user to accept some non-free
1463 license, this is explained to the user. The entire process make it
1464 more clear to the user why something do not work in the browser, and
1465 make the chances higher for the user to blame the web page authors and
1466 not the browser for any missing features.&lt;/li&gt;
1467
1468 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
1469 handlers.&lt;/strong&gt; When the media players encounter a format or codec
1470 it is not supporting, a dialog pop up asking the user if the system
1471 should search for a package that would add support for it. This
1472 happen with things like MP3, Windows Media or H.264. The selection
1473 and installation procedure is very similar to the Firefox browser
1474 plugin handling. This is as far as I know implemented using a
1475 gstreamer hook. The end result is that the user easily get access to
1476 the codecs that are present from the APT archives available, while
1477 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
1478
1479 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
1480 displaying a text/plain file in my Debian browser, it will propose to
1481 start emacs to show it. If I remember correctly, when doing the same
1482 in Kunbutu it show the file as a text file in the browser. At least I
1483 know Opera will show text files within the browser. I much prefer the
1484 latter behaviour.&lt;/li&gt;
1485
1486 &lt;/ol&gt;
1487
1488 &lt;p&gt;There are other nice features as well, like the simplified suite
1489 upgrader, but given that I am the one mostly doing the dist-upgrade,
1490 it do not matter much.&lt;/p&gt;
1491
1492 &lt;p&gt;I really hope we could get these features in place for the next
1493 Debian release. It would require the coordinated effort of several
1494 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
1495 </description>
1496 </item>
1497
1498 <item>
1499 <title>Gnash enteres Google Summer of Code 2011</title>
1500 <link>http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html</link>
1501 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_enteres_Google_Summer_of_Code_2011.html</guid>
1502 <pubDate>Wed, 6 Apr 2011 09:00:00 +0200</pubDate>
1503 <description>&lt;p&gt;&lt;a href=&quot;http://www.getgnash.org/&quot;&gt;The Gnash project&lt;/a&gt; is still
1504 the most promising solution for a Free Software Flash implementation.
1505 A few days ago the project
1506 &lt;a href=&quot;http://lists.gnu.org/archive/html/gnash-dev/2011-04/msg00011.html&quot;&gt;announced&lt;/a&gt;
1507 that it will participate in Google Summer of Code. I hope many
1508 students apply, and that some of them succeed in getting AVM2 support
1509 into Gnash.&lt;/p&gt;
1510 </description>
1511 </item>
1512
1513 <item>
1514 <title>Why isn&#39;t Debian Edu using VLC?</title>
1515 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
1516 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
1517 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
1518 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
1519 presented, and the winner among the multimedia player were VLC.
1520 Personally, I like VLC, and it is my player of choice when I first try
1521 to play a video file or stream. Only if VLC fail will I drag out
1522 gmplayer to see if it can do better. The reason is mostly the failure
1523 model and trust. When VLC fail, it normally pop up a error message
1524 reporting the problem. When mplayer fail, it normally segfault or
1525 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
1526
1527 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
1528 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
1529 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
1530 plugin to play web videos seamlessly, and the VLC browser plugin is
1531 not very good. For example, it lack in-line control buttons, so there
1532 is no way for the user to pause the video. Also, when I
1533 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
1534 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
1535 failed on several video pages where mplayer based plugins worked. If
1536 the browser plugin for VLC was as good as the gecko-mediaplayer
1537 package (which uses mplayer), we would switch.&lt;/P&gt;
1538
1539 &lt;p&gt;While VLC is a good player, its user interface is slightly
1540 annoying. The most annoying feature is its inconsistent use of
1541 keyboard shortcuts. When the player is in full screen mode, its
1542 shortcuts are different from when it is playing the video in a window.
1543 For example, space only work as pause when in full screen mode. I
1544 wish it had consisten shortcuts and that space also would work when in
1545 window mode. Another nice shortcut in gmplayer is [enter] to restart
1546 the current video. It is very nice when playing short videos from the
1547 web and want to restart it when new people arrive to have a look at
1548 what is going on.&lt;/p&gt;
1549 </description>
1550 </item>
1551
1552 <item>
1553 <title>Norgeskartet på mange vis - via OpenStreetmap.org</title>
1554 <link>http://people.skolelinux.org/pere/blog/Norgeskartet_p__mange_vis___via_OpenStreetmap_org.html</link>
1555 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norgeskartet_p__mange_vis___via_OpenStreetmap_org.html</guid>
1556 <pubDate>Mon, 1 Nov 2010 11:15:00 +0100</pubDate>
1557 <description>&lt;p&gt;Har oppdaget at mange ikke er klar over at OpenStreetmap.org er
1558 tilgjengelig i en rekke forskjellige formater. Her er en liste med
1559 eksporter jeg kjenner til for Norge, for de som trenger et
1560 fribrukskart til sine tjenester:&lt;/p&gt;
1561
1562 &lt;p&gt;&lt;ul&gt;
1563
1564 &lt;li&gt;Cloudmade tilbyr OSM XML, Garmin Map Files, Osmosis country
1565 bounding polygon, Shapefile, Navit maps, GPX POI, TomTom POI og OSM
1566 XML feature extracts via
1567 &lt;a href=&quot;http://downloads.cloudmade.com/europe/norway&quot;&gt;sine
1568 nedlastingssider&lt;/a&gt;.&lt;/li&gt;
1569
1570 &lt;li&gt;Geofabric tilbyr
1571 &lt;a href=&quot;http://download.geofabrik.de/osm/europe/norway.osm.bz2&quot;&gt;OSM
1572 XML&lt;/a&gt;,
1573 &lt;a href=&quot;http://download.geofabrik.de/osm/europe/norway.osm.pbf&quot;&gt;OSM
1574 protobuf binærformat&lt;/a&gt; og
1575 &lt;a href=&quot;http://download.geofabrik.de/osm/europe/norway.shp.zip&quot;&gt;ESRI
1576 Shapefile (EPSG:4326)&lt;/a&gt; fra sine nedlastingssider.&lt;/li&gt;
1577
1578 &lt;li&gt;Frikart.no tilbyr
1579 &lt;a href=&quot;http://www.frikart.no/garmin/&quot;&gt;Garmin-kart&lt;/a&gt; i uike
1580 varianter for veibruk og turbruk sommer og vinter.&lt;/li&gt;
1581
1582 &lt;/ul&gt;&lt;/p&gt;
1583
1584 &lt;p&gt;Kartene oppdateres regelmessig, som oftest hver uke. Det skulle
1585 dermed være noe for enhver smak.&lt;/p&gt;
1586 </description>
1587 </item>
1588
1589 <item>
1590 <title>Best å ikke fortelle noen at streaming er nedlasting...</title>
1591 <link>http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html</link>
1592 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html</guid>
1593 <pubDate>Sat, 30 Oct 2010 11:20:00 +0200</pubDate>
1594 <description>&lt;p&gt;I dag la jeg inn en kommentar på en sak hos NRKBeta
1595 &lt;a href=&quot;http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/&quot;&gt;om
1596 hvordan TV-serien Blindpassasjer ble laget&lt;/a&gt; i forbindelse med at
1597 filmene NRK la ut ikke var tilgjengelig i et
1598 &lt;a href=&quot;http://www.digistan.org/open-standard:definition&quot;&gt;fritt og
1599 åpent format&lt;/a&gt;. Dette var det jeg skrev publiserte der 07:39.&lt;/p&gt;
1600
1601 &lt;p&gt;&lt;blockquote&gt;
1602 &lt;p&gt;&quot;Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
1603 nedlasting. Mange av oss som kan mer enn gjennomsnittet om systemer
1604 som dette, vet at det stort sett er mulig å lure ut ting med den
1605 nødvendige forkunnskapen.&quot;&lt;/p&gt;
1606
1607 &lt;p&gt;Haha. Å streame innhold er det samme som å laste ned innhold, så å
1608 beskytte en stream mot nedlasting er ikke mulig. Å skrive noe slikt
1609 er å forlede leseren.&lt;/p&gt;
1610
1611 &lt;p&gt;Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
1612 vil tillate streaming men ikke nedlasting meningsløs.&lt;/p&gt;
1613
1614 &lt;p&gt;Anbefaler forresten å lese
1615 &lt;a href=&quot;http://blogs.computerworlduk.com/simon-says/2010/10/drm-is-toxic-to-culture/index.htm&quot;&gt;http://blogs.computerworlduk.com/simon-says/2010/10/drm-is-toxic-to-culture/index.htm&lt;/a&gt;
1616 om hva som ville være konsekvensen hvis digitale avspillingssperrer
1617 (DRM) fungerte. Det gjør de naturligvis ikke teknisk - det er jo
1618 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
1619 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
1620 opp under.&lt;/p&gt;
1621 &lt;/blockquote&gt;&lt;/p&gt;
1622
1623 &lt;p&gt;Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
1624 NRKBeta:&lt;/p&gt;
1625
1626 &lt;p&gt;&lt;blockquote&gt;
1627 &lt;p&gt;From: Anders Hofseth &amp;lt;XXX@gmail.com&gt;
1628 &lt;br&gt;To: &quot;pere@hungry.com&quot; &amp;lt;pere@hungry.com&gt;
1629 &lt;br&gt;Cc: Eirik Solheim &amp;lt;XXX@gmail.com&gt;, Jon Ståle Carlsen &amp;lt;XXX@gmail.com&gt;, Henrik Lied &amp;lt;XXX@gmail.com&gt;
1630 &lt;br&gt;Subject: Re: [NRKbeta] Kommentar: &quot;Bakom Blindpassasjer: del 1&quot;
1631 &lt;br&gt;Date: Sat, 30 Oct 2010 07:58:44 +0200&lt;/p&gt;
1632
1633 &lt;p&gt;Hei Petter.
1634 &lt;br&gt;Det du forsøker dra igang er egentlig en interessant diskusjon,
1635 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
1636 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1637 særlig lett å klarere ut noe annet arkivmateriale på lang tid.&lt;/p&gt;
1638
1639 &lt;p&gt;Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
1640 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1641 konsekvensene vi beskriver ikke er noe du ønsker heller...&lt;/p&gt;
1642
1643 &lt;p&gt;Med hilsen,
1644 &lt;br&gt;-anders&lt;/p&gt;
1645
1646 &lt;p&gt;Ring meg om noe er uklart: 95XXXXXXX&lt;/p&gt;
1647 &lt;/blockquote&gt;&lt;/p&gt;
1648
1649 &lt;p&gt;Ble så fascinert over denne holdningen, at jeg forfattet og sendte
1650 over følgende svar. I og med at debatten er fjernet fra NRK Betas
1651 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
1652 Har fjernet epostadresser og telefonnummer til de involverte, for å
1653 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.&lt;/p&gt;
1654
1655 &lt;p&gt;&lt;blockquote&gt;
1656 &lt;p&gt;From: Petter Reinholdtsen &amp;lt;pere@hungry.com&gt;
1657 &lt;br&gt;To: Anders Hofseth &amp;lt;XXX@gmail.com&gt;
1658 &lt;br&gt;Cc: Eirik Solheim &amp;lt;XXX@gmail.com&gt;,
1659 &lt;br&gt; Jon Ståle Carlsen &amp;lt;XXX@gmail.com&gt;,
1660 &lt;br&gt; Henrik Lied &amp;lt;XXX@gmail.com&gt;
1661 &lt;br&gt;Subject: Re: [NRKbeta] Kommentar: &quot;Bakom Blindpassasjer: del 1&quot;
1662 &lt;br&gt;Date: Sat, 30 Oct 2010 08:24:34 +0200&lt;/p&gt;
1663
1664 &lt;p&gt;[Anders Hofseth]
1665 &lt;br&gt;&gt; Hei Petter.&lt;/p&gt;
1666
1667 &lt;p&gt;Hei.&lt;/p&gt;
1668
1669 &lt;p&gt;&gt; Det du forsøker dra igang er egentlig en interessant diskusjon, men
1670 &lt;br&gt;&gt; om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
1671 &lt;br&gt;&gt; å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1672 &lt;br&gt;&gt; særlig lett å klarere ut noe annet arkivmateriale på lang tid.&lt;/p&gt;
1673
1674 &lt;p&gt;Godt å se at du er enig i at dette er en interessant diskusjon. Den
1675 vil nok fortsette en stund til. :)&lt;/p&gt;
1676
1677 &lt;p&gt;Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
1678 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
1679 fortsette å legge ut arkivmateriale.&lt;/p&gt;
1680
1681 &lt;p&gt;Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
1682 faktum, som er at streaming er det samme som nedlasting, og at innhold
1683 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
1684 det.&lt;/p&gt;
1685
1686 &lt;p&gt;Det du sier er jo at klarering av arkivmateriale for publisering på
1687 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
1688 Det er ikke et argument som holder vann. :)&lt;/p&gt;
1689
1690 &lt;p&gt;&gt; Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
1691 &lt;br&gt;&gt; og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1692 &lt;br&gt;&gt; konsekvensene vi beskriver ikke er noe du ønsker heller...&lt;/p&gt;
1693
1694 &lt;p&gt;Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
1695 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
1696 mot de som vil låse kulturen inne. Jeg synes det er en skam at NRK
1697 godtar å forlede publikum. Ville heller at NRK krever at innhold som
1698 skal sendes skal være uten bruksbegresninger og kan publiseres i
1699 formater som heller ikke har bruksbegresninger (bruksbegresningene til
1700 H.264 burde få varselbjellene i NRK til å ringe).&lt;/p&gt;
1701
1702 &lt;p&gt;At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
1703 påstander om at &quot;streaming beskytter mot nedlasting&quot; som bare er egnet
1704 til å bygge opp om en myte som er skadelig for samfunnet som helhet.&lt;/p&gt;
1705
1706 &lt;p&gt;Anbefaler &amp;lt;URL:&lt;a href=&quot;http://webmink.com/2010/09/03/h-264-and-foss/&quot;&gt;http://webmink.com/2010/09/03/h-264-and-foss/&lt;/a&gt;&gt; og en
1707 titt på
1708 &amp;lt;URL: &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html&quot;&gt;http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html&lt;/a&gt; &gt;.
1709 for å se hva slags bruksbegresninger H.264 innebærer.&lt;/p&gt;
1710
1711 &lt;p&gt;Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
1712 kan brukes før rettighetshaverene også innser at de er med på å skade
1713 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
1714 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
1715 langt på overtid.&lt;/p&gt;
1716
1717 &lt;p&gt;&gt; Ring meg om noe er uklart: XXX&lt;/p&gt;
1718
1719 &lt;p&gt;Intet uklart, men ikke imponert over måten dere håndterer debatten på.
1720 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
1721 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
1722 for videre diskusjon hadde dere i mine øyne kommet fra det med
1723 ryggraden på plass.&lt;/p&gt;
1724
1725 &lt;p&gt;PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.&lt;/p&gt;
1726
1727 &lt;p&gt;Som en liten avslutning, her er noen litt morsomme innslag om temaet.
1728 &amp;lt;URL: &lt;a href=&quot;http://www.archive.org/details/CopyingIsNotTheft&quot;&gt;http://www.archive.org/details/CopyingIsNotTheft&lt;/a&gt; &gt; og
1729 &amp;lt;URL: &lt;a href=&quot;http://patentabsurdity.com/&quot;&gt;http://patentabsurdity.com/&lt;/a&gt; &gt; hadde vært noe å kringkaste på
1730 NRK1. :)&lt;/p&gt;
1731
1732 &lt;p&gt;Vennlig hilsen,
1733 &lt;br&gt;--
1734 &lt;br&gt;Petter Reinholdtsen&lt;/p&gt;
1735 </description>
1736 </item>
1737
1738 <item>
1739 <title>Pledge for funding to the Gnash project to get AVM2 support</title>
1740 <link>http://people.skolelinux.org/pere/blog/Pledge_for_funding_to_the_Gnash_project_to_get_AVM2_support.html</link>
1741 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Pledge_for_funding_to_the_Gnash_project_to_get_AVM2_support.html</guid>
1742 <pubDate>Tue, 19 Oct 2010 14:45:00 +0200</pubDate>
1743 <description>&lt;p&gt;&lt;a href=&quot;http://www.getgnash.org/&quot;&gt;The Gnash project&lt;/a&gt; is the
1744 most promising solution for a Free Software Flash implementation. It
1745 has done great so far, but there is still far to go, and recently its
1746 funding has dried up. I believe AVM2 support in Gnash is vital to the
1747 continued progress of the project, as more and more sites show up with
1748 AVM2 flash files.&lt;/p&gt;
1749
1750 &lt;p&gt;To try to get funding for developing such support, I have started
1751 &lt;a href=&quot;http://www.pledgebank.com/gnash-avm2&quot;&gt;a pledge&lt;/a&gt; with the
1752 following text:&lt;/P&gt;
1753
1754 &lt;p&gt;&lt;blockquote&gt;
1755
1756 &lt;p&gt;&quot;I will pay 100$ to the Gnash project to develop AVM2 support but
1757 only if 10 other people will do the same.&quot;&lt;/p&gt;
1758
1759 &lt;p&gt;- Petter Reinholdtsen, free software developer&lt;/p&gt;
1760
1761 &lt;p&gt;Deadline to sign up by: 24th December 2010&lt;/p&gt;
1762
1763 &lt;p&gt;The Gnash project need to get support for the new Flash file
1764 format AVM2 to work with a lot of sites using Flash on the
1765 web. Gnash already work with a lot of Flash sites using the old AVM1
1766 format, but more and more sites are using the AVM2 format these
1767 days. The project web page is available from
1768 http://www.getgnash.org/ . Gnash is a free software implementation
1769 of Adobe Flash, allowing those of us that do not accept the terms of
1770 the Adobe Flash license to get access to Flash sites.&lt;/p&gt;
1771
1772 &lt;p&gt;The project need funding to get developers to put aside enough
1773 time to develop the AVM2 support, and this pledge is my way to try
1774 to get this to happen.&lt;/p&gt;
1775
1776 &lt;p&gt;The project accept donations via the OpenMediaNow foundation,
1777 &lt;a href=&quot;http://www.openmedianow.org/?q=node/32&quot;&gt;http://www.openmedianow.org/?q=node/32&lt;/a&gt; .&lt;/p&gt;
1778
1779 &lt;/blockquote&gt;&lt;/p&gt;
1780
1781 &lt;p&gt;I hope you will support this effort too. I hope more than 10
1782 people will participate to make this happen. The more money the
1783 project gets, the more features it can develop using these funds.
1784 :)&lt;/p&gt;
1785 </description>
1786 </item>
1787
1788 <item>
1789 <title>Standardkrav inn i anbudstekster?</title>
1790 <link>http://people.skolelinux.org/pere/blog/Standardkrav_inn_i_anbudstekster_.html</link>
1791 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardkrav_inn_i_anbudstekster_.html</guid>
1792 <pubDate>Sun, 17 Oct 2010 19:30:00 +0200</pubDate>
1793 <description>&lt;p&gt;Hvis det å følge standarder skal ha noen effekt overfor
1794 leverandører, så må slike krav og ønsker komme inn i anbudstekster når
1795 systemer kjøpes inn. Har ikke sett noen slike formuleringer i anbud
1796 så langt, men har tenkt litt på hva som bør inn. Her er noen ideer og
1797 forslag. Min drøm er at en kan sette krav til slik støtte i
1798 anbudstekster, men så langt er det nok mer sannsynlig at en må nøye
1799 seg med å skrive at det er en fordel om slik støtte er tilstede i
1800 leveranser.&lt;/p&gt;
1801
1802 &lt;p&gt;Som systemadministrator på Universitetet er det typisk to områder
1803 som er problematiske for meg. Det ene er admin-grensesnittene på
1804 tjenermaskiner, som vi ønsker å bruke via ssh. Det andre er nettsider
1805 som vi ønsker å bruke via en nettleser. For begge deler er det viktig
1806 at protokollene og formatene som brukes følger standarder våre verktøy
1807 støtter.&lt;/p&gt;
1808
1809 &lt;p&gt;De fleste har nå støtte for SSH som overføringsprotkoll for
1810 admin-grensesnittet, men det er ikke tilstrekkelig for å kunne stille
1811 inn f.eks BIOS og RAID-kontroller via ssh-forbindelsen. Det er flere
1812 aktuelle protokoller for fremvisning av BIOS-oppsett og
1813 oppstartmeldinger, og min anbefaling ville være å kreve
1814 VT100-kompatibel protokoll, for å sikre at flest mulig
1815 terminalemulatorer kan forstå hva som kommer fra admin-grensesnittet
1816 via ssh. Andre aktuelle alternativer er ANSI-terminalemulering og
1817 VT220. Kanskje en formulering ala dette i anbudsutlysninger vil
1818 fungere:&lt;/p&gt;
1819
1820 &lt;p&gt;&lt;blockquote&gt;
1821 BIOS og oppstartmeldinger i administrasjonsgrensesnittet til maskinen
1822 bør/skal være tilgjengelig via SSH-protokollen som definert av IETF
1823 (RFC 4251 mfl.) og følge terminalfremvisningprotokollen VT100 (ref?)
1824 når en kobler seg til oppstart via ssh.
1825 &lt;/blockquote&gt;&lt;/p&gt;
1826
1827 &lt;p&gt;Har ikke lykkes med å finne en god referanse for
1828 VT100-spesifikasjonen.&lt;/p&gt;
1829
1830 &lt;p&gt;Når det gjelder nettsider, så er det det HTML, CSS og
1831 JavaScript-spesifikasjonen til W3C som gjelder.&lt;/p&gt;
1832
1833 &lt;p&gt;&lt;blockquote&gt;
1834 Alle systemets nettsider bør/skal være i henhold til statens
1835 standardkatalogs krav om nettsider og følge HTML-standarden som
1836 definert av W3C, og validere uten feil hos W3Cs HTML-validator
1837 (http://validator.w3.org). Hvis det brukes CSS så bør/skal denne
1838 validere uten feil hos W3Cs CSS-validator
1839 (http://jigsaw.w3.org/css-validator/). Eventuelle JavaScript skal
1840 være i henhold til EcmaScript-standarden. I tillegg til å følge de
1841 overnevnte standardene skal websidene fungere i nettleserne (fyll inn
1842 relevant liste for organisasjonen) Firefox 3.5, Internet Explorer 8,
1843 Opera 9, etc.
1844 &lt;/blockquote&gt;&lt;/p&gt;
1845
1846 &lt;p&gt;Vil et slikt avsnitt være konkret nok til å få leverandørene til å
1847 lage nettsider som følger standardene og fungerer i flere
1848 nettlesere?&lt;/p&gt;
1849
1850 &lt;p&gt;Tar svært gjerne imot innspill på dette temaet til aktive (at)
1851 nuug.no, og er spesielt interessert i hva andre skriver i sine anbud
1852 for å oppmuntre leverandører til å følge standardene. Kanskje NUUG
1853 burde lage et dokument med forslag til standardformuleringer å ta med
1854 i anbudsutlysninger?&lt;/p&gt;
1855
1856 &lt;p&gt;Oppdatering 2010-12-03: I følge Wikipedias oppføring om
1857 &lt;a href=&quot;http://en.wikipedia.org/wiki/ANSI_escape_code&quot;&gt;ANSI escape
1858 code&lt;/a&gt;, så bruker VT100-terminaler ECMA-48-spesifikasjonen som
1859 basis for sin oppførsel. Det kan dermed være et alternativ når en
1860 skal spesifisere hvordan seriell-konsoll skal fungere.&lt;/p&gt;
1861 </description>
1862 </item>
1863
1864 <item>
1865 <title>Terms of use for video produced by a Canon IXUS 130 digital camera</title>
1866 <link>http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html</link>
1867 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html</guid>
1868 <pubDate>Thu, 9 Sep 2010 23:55:00 +0200</pubDate>
1869 <description>&lt;p&gt;A few days ago I had the mixed pleasure of bying a new digital
1870 camera, a Canon IXUS 130. It was instructive and very disturbing to
1871 be able to verify that also this camera producer have the nerve to
1872 specify how I can or can not use the videos produced with the camera.
1873 Even thought I was aware of the issue, the options with new cameras
1874 are limited and I ended up bying the camera anyway. What is the
1875 problem, you might ask? It is software patents, MPEG-4, H.264 and the
1876 MPEG-LA that is the problem, and our right to record our experiences
1877 without asking for permissions that is at risk.
1878
1879 &lt;p&gt;On page 27 of the Danish instruction manual, this section is
1880 written:&lt;/p&gt;
1881
1882 &lt;blockquote&gt;
1883 &lt;p&gt;This product is licensed under AT&amp;T patents for the MPEG-4 standard
1884 and may be used for encoding MPEG-4 compliant video and/or decoding
1885 MPEG-4 compliant video that was encoded only (1) for a personal and
1886 non-commercial purpose or (2) by a video provider licensed under the
1887 AT&amp;T patents to provide MPEG-4 compliant video.&lt;/p&gt;
1888
1889 &lt;p&gt;No license is granted or implied for any other use for MPEG-4
1890 standard.&lt;/p&gt;
1891 &lt;/blockquote&gt;
1892
1893 &lt;p&gt;In short, the camera producer have chosen to use technology
1894 (MPEG-4/H.264) that is only provided if I used it for personal and
1895 non-commercial purposes, or ask for permission from the organisations
1896 holding the knowledge monopoly (patent) for technology used.&lt;/p&gt;
1897
1898 &lt;p&gt;This issue has been brewing for a while, and I recommend you to
1899 read
1900 &quot;&lt;a href=&quot;http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA&quot;&gt;Why
1901 Our Civilization&#39;s Video Art and Culture is Threatened by the
1902 MPEG-LA&lt;/a&gt;&quot; by Eugenia Loli-Queru and
1903 &quot;&lt;a href=&quot;http://webmink.com/2010/09/03/h-264-and-foss/&quot;&gt;H.264 Is Not
1904 The Sort Of Free That Matters&lt;/a&gt;&quot; by Simon Phipps to learn more about
1905 the issue. The solution is to support the
1906 &lt;a href=&quot;http://www.digistan.org/open-standard:definition&quot;&gt;free and
1907 open standards&lt;/a&gt; for video, like &lt;a href=&quot;http://www.theora.org/&quot;&gt;Ogg
1908 Theora&lt;/a&gt;, and avoid MPEG-4 and H.264 if you can.&lt;/p&gt;
1909 </description>
1910 </item>
1911
1912 <item>
1913 <title>Some notes on Flash in Debian and Debian Edu</title>
1914 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
1915 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
1916 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
1917 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
1918 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
1919 second most popular used package that is missing in Debian. The sixth
1920 most popular is flashplayer-mozilla. This is a clear indication that
1921 working flash is important for Debian users. Around 10 percent of the
1922 users submitting data to popcon.debian.org have this package
1923 installed.&lt;/p&gt;
1924
1925 &lt;p&gt;In the report written by Lars Risan in August 2008
1926&lt;a href=&quot;http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile&amp;do=view&amp;target=Skolelinux_i_bruk_rapport_1.0.pdf&quot;&gt;Skolelinux
1927 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
1928 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
1929 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
1930 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
1931 web sites require Flash to work, and lacking working Flash support in
1932 the web browser and the problems with installing it was perceived as a
1933 good reason to stay with Windows.&lt;/p&gt;
1934
1935 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
1936 said to be the retarded cousin that did not really understand
1937 everything you told him but could work fairly well. This was a
1938 comment regarding the problems Linux have with proprietary formats and
1939 non-standard web pages, and is sad because it exposes a fairly common
1940 understanding of whose fault it is if web pages that only work in for
1941 example Internet Explorer 6 fail to work on Firefox, and funny because
1942 it explain very well how annoying it is for users when Linux
1943 distributions do not work with the documents they receive or the web
1944 pages they want to visit.&lt;/p&gt;
1945
1946 &lt;p&gt;This is part of the reason why I believe it is important for Debian
1947 and Debian Edu to have a well working Flash implementation in the
1948 distribution, to get at least popular sites as Youtube and Google
1949 Video to working out of the box. For Squeeze, Debian have the chance
1950 to include the latest version of Gnash that will make this happen, as
1951 the new release 0.8.8 was published a few weeks ago and is resting in
1952 unstable. The new version work with more sites that version 0.8.7.
1953 The Gnash maintainers have asked for a freeze exception, but the
1954 release team have not had time to reply to it yet. I hope they agree
1955 with me that Flash is important for the Debian desktop users, and thus
1956 accept the new package into Squeeze.&lt;/p&gt;
1957 </description>
1958 </item>
1959
1960 <item>
1961 <title>OpenStreetmap one step closer to having routing on its front page</title>
1962 <link>http://people.skolelinux.org/pere/blog/OpenStreetmap_one_step_closer_to_having_routing_on_its_front_page.html</link>
1963 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenStreetmap_one_step_closer_to_having_routing_on_its_front_page.html</guid>
1964 <pubDate>Sun, 18 Jul 2010 16:45:00 +0200</pubDate>
1965 <description>&lt;p&gt;Thanks to
1966 &lt;a href=&quot;http://feedproxy.google.com/~r/Opengeodata/~3/wUTCzDZk3lc/project-of-the-week-which-way-home&quot;&gt;todays
1967 opengeodata blog entry&lt;/a&gt;, I just discovered that the
1968 OpenStreetmap.org site have gotten
1969 &lt;a href=&quot;http://nroets.dev.openstreetmap.org/demo/index.html?layers=B000FTFTT&quot;&gt;support
1970 for calculating routes&lt;/a&gt;. The support is still experimental and
1971 only available from the development server, until more experience is
1972 gathered on the user interface and any scalability issues.&lt;/p&gt;
1973
1974 &lt;p&gt;Earlier, the routing I knew about using the OpenStreetmap.org data
1975 was provided by &lt;a href=&quot;http://maps.cloudmade.com/&quot;&gt;Cloudmade&lt;/a&gt;,
1976 but having it on the main page is required to make everyone aware of
1977 the issue. I&#39;ve had people reject Openstreetmap.org as a viable
1978 alternative for them because the front page lacked routing support,
1979 and I hope their needs will be catered for when routing show up on the
1980 www.openstreetmap.org front page.&lt;/p&gt;
1981 </description>
1982 </item>
1983
1984 <item>
1985 <title>Great book: &quot;Content: Selected Essays on Technology, Creativity, Copyright, and the Future of the Future&quot;</title>
1986 <link>http://people.skolelinux.org/pere/blog/Great_book___Content__Selected_Essays_on_Technology__Creativity__Copyright__and_the_Future_of_the_Future_.html</link>
1987 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Great_book___Content__Selected_Essays_on_Technology__Creativity__Copyright__and_the_Future_of_the_Future_.html</guid>
1988 <pubDate>Mon, 19 Apr 2010 17:10:00 +0200</pubDate>
1989 <description>&lt;p&gt;The last few weeks i have had the pleasure of reading a
1990 thought-provoking collection of essays by Cory Doctorow, on topics
1991 touching copyright, virtual worlds, the future of man when the
1992 conscience mind can be duplicated into a computer and many more. The
1993 book titled &quot;Content: Selected Essays on Technology, Creativity,
1994 Copyright, and the Future of the Future&quot; is available with few
1995 restrictions on the web, for example from
1996 &lt;a href=&quot;http://craphound.com/content/&quot;&gt;his own site&lt;/a&gt;. I read the
1997 epub-version from
1998 &lt;a href=&quot;http://www.feedbooks.com/book/2883&quot;&gt;feedbooks&lt;/a&gt; using
1999 &lt;a href=&quot;http://www.fbreader.org/&quot;&gt;fbreader&lt;/a&gt; and my N810. I
2000 strongly recommend this book.&lt;/p&gt;
2001 </description>
2002 </item>
2003
2004 <item>
2005 <title>Relative popularity of document formats (MS Office vs. ODF)</title>
2006 <link>http://people.skolelinux.org/pere/blog/Relative_popularity_of_document_formats__MS_Office_vs__ODF_.html</link>
2007 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Relative_popularity_of_document_formats__MS_Office_vs__ODF_.html</guid>
2008 <pubDate>Wed, 12 Aug 2009 15:50:00 +0200</pubDate>
2009 <description>&lt;p&gt;Just for fun, I did a search right now on Google for a few file ODF
2010 and MS Office based formats (not to be mistaken for ISO or ECMA
2011 OOXML), to get an idea of their relative usage. I searched using
2012 &#39;filetype:odt&#39; and equvalent terms, and got these results:&lt;/P&gt;
2013
2014 &lt;table&gt;
2015 &lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;ODF&lt;/th&gt;&lt;th&gt;MS Office&lt;/th&gt;&lt;/tr&gt;
2016 &lt;tr&gt;&lt;td&gt;Tekst&lt;/td&gt; &lt;td&gt;odt:282000&lt;/td&gt; &lt;td&gt;docx:308000&lt;/td&gt;&lt;/tr&gt;
2017 &lt;tr&gt;&lt;td&gt;Presentasjon&lt;/td&gt; &lt;td&gt;odp:75600&lt;/td&gt; &lt;td&gt;pptx:183000&lt;/td&gt;&lt;/tr&gt;
2018 &lt;tr&gt;&lt;td&gt;Regneark&lt;/td&gt; &lt;td&gt;ods:26500 &lt;/td&gt; &lt;td&gt;xlsx:145000&lt;/td&gt;&lt;/tr&gt;
2019 &lt;/table&gt;
2020
2021 &lt;p&gt;Next, I added a &#39;site:no&#39; limit to get the numbers for Norway, and
2022 got these numbers:&lt;/p&gt;
2023
2024 &lt;table&gt;
2025 &lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;ODF&lt;/th&gt;&lt;th&gt;MS Office&lt;/th&gt;&lt;/tr&gt;
2026 &lt;tr&gt;&lt;td&gt;Tekst&lt;/td&gt; &lt;td&gt;odt:2480 &lt;/td&gt; &lt;td&gt;docx:4460&lt;/td&gt;&lt;/tr&gt;
2027 &lt;tr&gt;&lt;td&gt;Presentasjon&lt;/td&gt; &lt;td&gt;odp:299 &lt;/td&gt; &lt;td&gt;pptx:741&lt;/td&gt;&lt;/tr&gt;
2028 &lt;tr&gt;&lt;td&gt;Regneark&lt;/td&gt; &lt;td&gt;ods:187 &lt;/td&gt; &lt;td&gt;xlsx:372&lt;/td&gt;&lt;/tr&gt;
2029 &lt;/table&gt;
2030
2031 &lt;p&gt;I wonder how these numbers change over time.&lt;/p&gt;
2032
2033 &lt;p&gt;I am aware of Google returning different results and numbers based
2034 on where the search is done, so I guess these numbers will differ if
2035 they are conduced in another country. Because of this, I did the same
2036 search from a machine in California, USA, a few minutes after the
2037 search done from a machine here in Norway.&lt;/p&gt;
2038
2039
2040 &lt;table&gt;
2041 &lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;ODF&lt;/th&gt;&lt;th&gt;MS Office&lt;/th&gt;&lt;/tr&gt;
2042 &lt;tr&gt;&lt;td&gt;Tekst&lt;/td&gt; &lt;td&gt;odt:129000&lt;/td&gt; &lt;td&gt;docx:308000&lt;/td&gt;&lt;/tr&gt;
2043 &lt;tr&gt;&lt;td&gt;Presentasjon&lt;/td&gt; &lt;td&gt;odp:44200&lt;/td&gt; &lt;td&gt;pptx:93900&lt;/td&gt;&lt;/tr&gt;
2044 &lt;tr&gt;&lt;td&gt;Regneark&lt;/td&gt; &lt;td&gt;ods:26500 &lt;/td&gt; &lt;td&gt;xlsx:82400&lt;/td&gt;&lt;/tr&gt;
2045 &lt;/table&gt;
2046
2047 &lt;p&gt;And with &#39;site:no&#39;:
2048
2049 &lt;table&gt;
2050 &lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;ODF&lt;/th&gt;&lt;th&gt;MS Office&lt;/th&gt;&lt;/tr&gt;
2051 &lt;tr&gt;&lt;td&gt;Tekst&lt;/td&gt; &lt;td&gt;odt:2480&lt;/td&gt; &lt;td&gt;docx:3410&lt;/td&gt;&lt;/tr&gt;
2052 &lt;tr&gt;&lt;td&gt;Presentasjon&lt;/td&gt; &lt;td&gt;odp:175&lt;/td&gt; &lt;td&gt;pptx:604&lt;/td&gt;&lt;/tr&gt;
2053 &lt;tr&gt;&lt;td&gt;Regneark&lt;/td&gt; &lt;td&gt;ods:186 &lt;/td&gt; &lt;td&gt;xlsx:296&lt;/td&gt;&lt;/tr&gt;
2054 &lt;/table&gt;
2055
2056 &lt;p&gt;Interesting difference, not sure what to conclude from these
2057 numbers.&lt;/p&gt;
2058 </description>
2059 </item>
2060
2061 <item>
2062 <title>Nasjonalbiblioteket legger ut bøker på web</title>
2063 <link>http://people.skolelinux.org/pere/blog/Nasjonalbiblioteket_legger_ut_b_ker_p__web.html</link>
2064 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nasjonalbiblioteket_legger_ut_b_ker_p__web.html</guid>
2065 <pubDate>Thu, 23 Apr 2009 19:40:00 +0200</pubDate>
2066 <description>&lt;p&gt;&lt;a href=&quot;http://www.aftenposten.no/kul_und/litteratur/article3042382.ece&quot;&gt;Aftenposten
2067 melder&lt;/a&gt; at
2068 &lt;a href=&quot;http://www.nb.no/aktuelt/50_000_norske_boeker_gratis_tilgjengelig_paa_nett_helt_lovlig&quot;&gt;nasjonalbiblioteket
2069 og Kopinor har gjort en avtale&lt;/a&gt; som gjør at eldre bøker kan gjøres
2070 digitalt tilgjengelig fra nasjonalbiblioteket mot at Kopinor får 56
2071 øre for hver side som legges ut. Utvalget er litt merkelig: 1790-,
2072 1890- og 1990-tallet. Jeg synes det er absurd hvis det er slik at
2073 Kopinor skal ha betalt for utlegging av bøker som ikke lenger er
2074 beskyttet av opphavsretten. Jeg antar her at det er mer enn 90 år
2075 siden forfatterne av bøker som ble publisert 1790-1799 døde, slik at
2076 disse bøkene er falt i det fri og enhver kan kopiere så mye de vil fra
2077 dem uten å bryte opphavsrettsloven. Bruk av slike verk har ikke
2078 Kopinor noe med å gjøre. Jeg håper jeg har misforstått.
2079 &lt;a href=&quot;http://www.nb.no/aktuelt/no_er_vi_i_gang_med_aa_digitalisere_samlingane_vaare_og_formidle_digitalt&quot;&gt;En
2080 melding fra nasjonalbiblioteket i 2007&lt;/a&gt; tyder på at tekster i det
2081 fri ikke trenger avtale med Kopinor.&lt;/p&gt;
2082
2083 &lt;p&gt;Et annet problem er at bøkene kun legges ut som bildefiler, noe som
2084 vil gjøre at søketjenester ikke vil finne disse bøkene når en søker
2085 etter fragmenter i teksten. En risikerer dermed at de blir liggende
2086 på en slik måte at folk som bruker Google ikke finner dem.&lt;/p&gt;
2087
2088 &lt;p&gt;Da skulle jeg heller sett at nasjonalbiblioteket gjorde alvor av
2089 sin aprilspøk, og la ut bøkene som faller i det fri
2090 fortløpende.&lt;/p&gt;
2091
2092 </description>
2093 </item>
2094
2095 <item>
2096 <title>Fildeling er lovlig - ulovlig fildeling er ulovlig</title>
2097 <link>http://people.skolelinux.org/pere/blog/Fildeling_er_lovlig___ulovlig_fildeling_er_ulovlig.html</link>
2098 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fildeling_er_lovlig___ulovlig_fildeling_er_ulovlig.html</guid>
2099 <pubDate>Fri, 17 Apr 2009 20:00:00 +0200</pubDate>
2100 <description>&lt;p&gt;Jeg hadde glede av å overvære FADs lansering av
2101 &lt;a href=&quot;http://www.deltemeninger.no/&quot;&gt;Debattsentralen
2102 deltemeninger.no&lt;/a&gt; under Go Open 2009, og må si jeg ble skuffet over
2103 en kommentar fra podiet om ulovlig fildeling. Fikk ikke med meg hvem
2104 som holdt innlegget, men det startet med å snakke om ulovlig fildeling
2105 og gikk så over til å snakke om fildeling som om fildeling i seg er
2106 ulovlig. Intet er lengre fra sannheten. Fildeling er en nyttig
2107 teknologi som benyttes av NRK, Debian, Ubuntu, NUUG og andre for
2108 distribusjon av filer. Det er ingenting med denne fildelingen som
2109 gjør den ulovlig. Fildeling er i seg selv en fullt ut lovlig
2110 teknologisk anvendelse. Noe fildeling er ulovlig, og noe er lovlig.
2111 De som tror at fildeling er ulovlig har misforstått grovt. Hvorvidt
2112 den er ulovlig kommer jo an på hvem som har opphavsretten til filene
2113 som deles og hvilke bruksbegrensninger som gjelder for filene. En
2114 rekke filer er lagt ut av rettighetsinnehaver for deling på Internet,
2115 og fildeling av slike filer er fullt ut lovlig.&lt;/p&gt;
2116 </description>
2117 </item>
2118
2119 <item>
2120 <title>When web browser developers make a video player...</title>
2121 <link>http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html</link>
2122 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/When_web_browser_developers_make_a_video_player___.html</guid>
2123 <pubDate>Sat, 17 Jan 2009 18:50:00 +0100</pubDate>
2124 <description>&lt;p&gt;As part of the work we do in &lt;a href=&quot;http://www.nuug.no&quot;&gt;NUUG&lt;/a&gt;
2125 to publish video recordings of our monthly presentations, we provide a
2126 page with embedded video for easy access to the recording. Putting a
2127 good set of HTML tags together to get working embedded video in all
2128 browsers and across all operating systems is not easy. I hope this
2129 will become easier when the &amp;lt;video&amp;gt; tag is implemented in all
2130 browsers, but I am not sure. We provide the recordings in several
2131 formats, MPEG1, Ogg Theora, H.264 and Quicktime, and want the
2132 browser/media plugin to pick one it support and use it to play the
2133 recording, using whatever embed mechanism the browser understand.
2134 There is at least four different tags to use for this, the new HTML5
2135 &amp;lt;video&amp;gt; tag, the &amp;lt;object&amp;gt; tag, the &amp;lt;embed&amp;gt; tag and
2136 the &amp;lt;applet&amp;gt; tag. All of these take a lot of options, and
2137 finding the best options is a major challenge.&lt;/p&gt;
2138
2139 &lt;p&gt;I just tested the experimental Opera browser available from &lt;a
2140 href=&quot;http://labs.opera.com&quot;&gt;labs.opera.com&lt;/a&gt;, to see how it handled
2141 a &amp;lt;video&amp;gt; tag with a few video sources and no extra attributes.
2142 I was not very impressed. The browser start by fetching a picture
2143 from the video stream. Not sure if it is the first frame, but it is
2144 definitely very early in the recording. So far, so good. Next,
2145 instead of streaming the 76 MiB video file, it start to download all
2146 of it, but do not start to play the video. This mean I have to wait
2147 for several minutes for the downloading to finish. When the download
2148 is done, the playing of the video do not start! Waiting for the
2149 download, but I do not get to see the video? Some testing later, I
2150 discover that I have to add the controls=&quot;true&quot; attribute to be able
2151 to get a play button to pres to start the video. Adding
2152 autoplay=&quot;true&quot; did not help. I sure hope this is a misfeature of the
2153 test version of Opera, and that future implementations of the
2154 &amp;lt;video&amp;gt; tag will stream recordings by default, or at least start
2155 playing when the download is done.&lt;/p&gt;
2156
2157 &lt;p&gt;The test page I used (since changed to add more attributes) is
2158 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20090113-foredrag-om-foredrag/&quot;&gt;available
2159 from the nuug site&lt;/a&gt;. Will have to test it with the new Firefox
2160 too.&lt;/p&gt;
2161
2162 &lt;p&gt;In the test process, I discovered a missing feature. I was unable
2163 to find a way to get the URL of the playing video out of Opera, so I
2164 am not quite sure it picked the Ogg Theora version of the video. I
2165 sure hope it was using the announced Ogg Theora support. :)&lt;/p&gt;
2166 </description>
2167 </item>
2168
2169 <item>
2170 <title>The sorry state of multimedia browser plugins in Debian</title>
2171 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
2172 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
2173 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
2174 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
2175 plugins available in Debian Lenny, to see which one we should use by
2176 default in Debian Edu. We need an embedded video playing plugin with
2177 control buttons to pause or stop the video, and capable of streaming
2178 all the multimedia content available on the web. The test results and
2179 notes are available on
2180 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
2181 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
2182 fill this need. My personal video player favorite, VLC, has a really
2183 bad plugin which fail on a lot of the test pages. A lot of the MIME
2184 types I would expect to work with any free software player (like
2185 video/ogg), just do not work. And simple formats like the
2186 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
2187 totem and vlc plugins. I hope the situation will improve soon. No
2188 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
2189
2190 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
2191 be the only one fitting our needs. :/&lt;/p&gt;
2192 </description>
2193 </item>
2194
2195 </channel>
2196 </rss>