<link>http://people.skolelinux.org/pere/blog/</link>
<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
+ <item>
+ <title>NUUG contests Norwegian police DNS seizure of popcorn-time.no</title>
+ <link>http://people.skolelinux.org/pere/blog/NUUG_contests_Norwegian_police_DNS_seizure_of_popcorn_time_no.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/NUUG_contests_Norwegian_police_DNS_seizure_of_popcorn_time_no.html</guid>
+ <pubDate>Mon, 18 Apr 2016 10:00:00 +0200</pubDate>
+ <description><p>It is days like today I am really happy to be a member of
+<a href="http://www.nuug.no/">the Norwegian Unix User group</a>, a
+member association for those of us believing in free software, open
+standards and unix-like operating systems. NUUG announced today it
+will
+<a href="http://www.nuug.no/news/Pressemelding__NUUG_og_EFN_begj_rer_rettslig_pr_ving_for_DNS_domenebeslag_av_popcorn_time_no.shtml">try
+to bring the seizure of the DNS domain popcorn-time.no as
+unlawful</a>, to stand up for the principle that writing about a
+controversial topic is not infringing copyrights, and censuring web
+pages by hijacking DNS domain should be decided by the courts, not the
+police. The DNS domain was seized by the Norwegian National Authority
+for Investigation and Prosecution of Economic and Environmental Crime
+a month ago. I hope this bring more paying members to NUUG to give
+the association the financial muscle needed to bring this case as far
+as it must go to stop this kind of DNS hijacking.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Ny utgave (v2.2) av den frie norske stavekontrollen gitt ut</title>
+ <link>http://people.skolelinux.org/pere/blog/Ny_utgave__v2_2__av_den_frie_norske_stavekontrollen_gitt_ut.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ny_utgave__v2_2__av_den_frie_norske_stavekontrollen_gitt_ut.html</guid>
+ <pubDate>Fri, 15 Apr 2016 21:20:00 +0200</pubDate>
+ <description><p>I dag tok jeg mot til meg og pakket sammen en ny versjon av den
+frie norske stavekontrollen, ca. tre og et halvt år etter forrige
+gang. Resultatet kan lastes ned fra
+<a href="http://no.speling.org/">no.speling.org-prosjeksiden</a>, både
+som kildekodepakke og som "pack"-fil som kanskje fortsatt kan brukes
+av OpenOffice.org/LibreOffice. Byggesystemet trenger oppussing, men i
+denne omgang hadde jeg bare tid til å fikse byggefeil forårsaket av
+endringer i GNU grep. De øvrige endringene var gjort tidligere i
+påvente av en ny utgave.</p>
+
+<p><strong>Her er det som er nytt (fra NEWS-fila i
+kildekodepakken):</strong></p>
+
+<p>Release 2.2 (2016-04-15)</p>
+
+<ul>
+
+ <li>Rewrite how scripts/speling2words handle tripple consonants, to
+ avoid importing duplicate words from no.speling.org, and getting
+ rid of the existing duplicates in norsk.words.</li>
+ <li>Remove duplicate entries with tripple consonants from norsk.words.</li>
+ <li>Update frequency for entries in norsk.words based on
+ <URL:http://helmer.aksis.uib.no/nta/ordlistf.zip> (ran 'make
+ freq-update').</li>
+ <li>Correct nn ispell build, avoid crash in munchlist causing lots of
+ words to fall out of the database.</li>
+ <li>Use grep -a to convince grep it is working on text files, to work
+ with newer grep versions.</li>
+
+ <li>Remove some words disputed in the no.speling.org review process:
+ <ul>
+ <li>apparent (nb)</li>
+ <li>likke (nb)</li>
+ <li>ugjest, ugjesten, ugjestens (nb)</li>
+ </ul></li>
+
+</ul>
+</description>
+ </item>
+
+ <item>
+ <title>I.F. Stone - an inspiration for us all</title>
+ <link>http://people.skolelinux.org/pere/blog/I_F__Stone___an_inspiration_for_us_all.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/I_F__Stone___an_inspiration_for_us_all.html</guid>
+ <pubDate>Wed, 13 Apr 2016 21:20:00 +0200</pubDate>
+ <description><p>I first got to know I.F. Stone when I came across an article by Jon
+Schwarz on The Intercept
+<a href="https://theintercept.com/2015/05/07/new-documentary-legacy-f-stone/">about
+his extraordinary contribution to investigative journalism in
+USA</a>. The article is about a new documentary in two parts
+(<a href="https://vimeo.com/123974841">part one is 12 minutes</a> and
+<a href="https://vimeo.com/123974842">part two is 30 minutes</a>), and
+I found both truly fascinating. It is amazing what he was able to
+find by digging up public sources and government papers. He
+documented lots of government abuse and cover ups, and I find
+<a href="http://www.ifstone.org/weekly.php">his weekly news letters</a>
+inspiring to read even today.</p>
+
+<p><blockquote>
+All governments are run by liars and nothing they say should be believed.
+<br>- I. F. Stone
+</blockquote></p>
+
+<p>His starting point was that reporters should not assume governments
+and corporations are telling the truth, but verify all their claims as
+much as possible. I wonder how many Norwegian reporters can be said
+to follow the principles of I. F. Stone. They are definitely in short
+supply. If you, like me half a year ago, have never heard of him,
+check him out.</p>
+</description>
+ </item>
+
+ <item>
+ <title>A French paperback edition of the book Free Culture by Lawrence Lessig is now available</title>
+ <link>http://people.skolelinux.org/pere/blog/A_French_paperback_edition_of_the_book_Free_Culture_by_Lawrence_Lessig_is_now_available.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_French_paperback_edition_of_the_book_Free_Culture_by_Lawrence_Lessig_is_now_available.html</guid>
+ <pubDate>Tue, 12 Apr 2016 10:40:00 +0200</pubDate>
+ <description><p>I'm happy to report that
+<a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">the
+French paperback edition</a> of
+<a href="https://github.com/petterreinholdtsen/free-culture-lessig">my
+project to translate</a> the <a href="http://free-culture.cc/">Free
+Culture</a> book by Lawrence Lessig is now available for sale on
+Lulu.com. Once I have formally verified my proof reading copy, which
+should be in the mail, the paperback edition should be available in
+book stores like Amazon and Barnes & Noble too.</p>
+
+<p>This French edition, Culture Libre, is the work of the
+<a href="http://dblatex.sourceforge.net/">dblatex</a> developer Benoît
+Guillon, who created the PO file from the initial translation
+available from
+<a href="http://www.wikilivres.ca/wiki/Culture_libre">the Wikilivres
+wiki pages</a> and completed and corrected the translation to match
+the original docbook edition my project is using, as well as
+coordinated the proof reading of the final result. I believe the end
+result look great, but I am biased and do not read French. In
+addition to the paperback edition, the book is available in PDF, EPUB
+and Mobi format from the github project page linked to above.</p>
+
+<p>When enabling book store distribution on Lulu.com, I had to nearly
+triple the price to allow the book stores some profit. I also had to
+accept that I will get some revenue when a book is sold via Lulu.com.
+But because of the non-commercial clause in the book license
+(CC-BY-NC), this might be a problem. To bypass the problem I
+discussed how to handle the revenue with the author, and we agreed
+that the revenue for these editions go to the
+<a href="https://creativecommons.org/">Creative Commons non-profit
+Corporation</a> who handle donations to the Creative Commons project.
+So far they have earned around USD 70 on sales of the
+<a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">English</a>
+and
+<a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Norwegian
+Bokmål</a> editions, according to Lulu.com. They will get the revenue
+for the French edition too. Their revenue is higher if you buy the
+book directly from Lulu.com instead of via a book store, so I
+recommend you buy directly from Lulu.com.</p>
+
+<p>Perhaps you would like to get the book published in your language?
+The translation is done using a web based translator service, so the
+technical bar to enter is fairly low. Get in touch if you would like
+to make this happen.</p>
+</description>
+ </item>
+
<item>
<title>Lets make a Norwegian Bokmål edition of The Debian Administrator's Handbook</title>
<link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
</description>
</item>
- <item>
- <title>Making battery measurements a little easier in Debian</title>
- <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
- <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
- <description><p>Back in September, I blogged about
-<a href="http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html">the
-system I wrote to collect statistics about my laptop battery</a>, and
-how it showed the decay and death of this battery (now replaced). I
-created a simple deb package to handle the collection and graphing,
-but did not want to upload it to Debian as there were already
-<a href="https://tracker.debian.org/pkg/battery-stats">a battery-stats
-package in Debian</a> that should do the same thing, and I did not see
-a point of uploading a competing package when battery-stats could be
-fixed instead. I reported a few bugs about its non-function, and
-hoped someone would step in and fix it. But no-one did.</p>
-
-<p>I got tired of waiting a few days ago, and took matters in my own
-hands. The end result is that I am now the new upstream developer of
-battery stats (<a href="https://github.com/petterreinholdtsen/battery-stats">available from github</a>) and part of the team maintaining
-battery-stats in Debian, and the package in Debian unstable is finally
-able to collect battery status using the <tt>/sys/class/power_supply/</tt>
-information provided by the Linux kernel. If you install the
-battery-stats package from unstable now, you will be able to get a
-graph of the current battery fill level, to get some idea about the
-status of the battery. The source package build and work just fine in
-Debian testing and stable (and probably oldstable too, but I have not
-tested). The default graph you get for that system look like this:</p>
-
-<p align="center"><img src="http://people.skolelinux.org/pere/blog/images/2016-03-15-battery-stats-graph-example.png" width="70%" align="center"></p>
-
-<p>My plans for the future is to merge my old scripts into the
-battery-stats package, as my old scripts collected a lot more details
-about the battery. The scripts are merged into the upstream
-battery-stats git repository already, but I am not convinced they work
-yet, as I changed a lot of paths along the way. Will have to test a
-bit more before I make a new release.</p>
-
-<p>I will also consider changing the file format slightly, as I
-suspect the way I combine several values into one field might make it
-impossible to know the type of the value when using it for processing
-and graphing.</p>
-
-<p>If you would like I would like to keep an close eye on your laptop
-battery, check out the battery-stats package in
-<a href="https://tracker.debian.org/pkg/battery-stats">Debian</a> and
-on
-<a href="https://github.com/petterreinholdtsen/battery-stats">github</a>.
-I would love some help to improve the system further.</p>
-</description>
- </item>
-
- <item>
- <title>Creating, updating and checking debian/copyright semi-automatically</title>
- <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
- <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
- <description><p>Making packages for Debian requires quite a lot of attention to
-details. And one of the details is the content of the
-debian/copyright file, which should list all relevant licenses used by
-the code in the package in question, preferably in
-<a href="https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/">machine
-readable DEP5 format</a>.</p>
-
-<p>For large packages with lots of contributors it is hard to write
-and update this file manually, and if you get some detail wrong, the
-package is normally rejected by the ftpmasters. So getting it right
-the first time around get the package into Debian faster, and save
-both you and the ftpmasters some work.. Today, while trying to figure
-out what was wrong with
-<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447">the
-zfsonlinux copyright file</a>, I decided to spend some time on
-figuring out the options for doing this job automatically, or at least
-semi-automatically.</p>
-
-<p>Lucikly, there are at least two tools available for generating the
-file based on the code in the source package,
-<tt><a href="https://tracker.debian.org/pkg/debmake">debmake</a></tt>
-and <tt><a href="https://tracker.debian.org/pkg/cme">cme</a></tt>. I'm
-not sure which one of them came first, but both seem to be able to
-create a sensible draft file. As far as I can tell, none of them can
-be trusted to get the result just right, so the content need to be
-polished a bit before the file is OK to upload. I found the debmake
-option in
-<a href="http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html">a
-blog posts from 2014</a>.
-
-<p>To generate using debmake, use the -cc option:
-
-<p><pre>
-debmake -cc > debian/copyright
-</pre></p>
-
-<p>Note there are some problems with python and non-ASCII names, so
-this might not be the best option.</p>
-
-<p>The cme option is based on a config parsing library, and I found
-this approach in
-<a href="https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/">a
-blog post from 2015</a>. To generate using cme, use the 'update
-dpkg-copyright' option:
-
-<p><pre>
-cme update dpkg-copyright
-</pre></p>
-
-<p>This will create or update debian/copyright. The cme tool seem to
-handle UTF-8 names better than debmake.</p>
-
-<p>When the copyright file is created, I would also like some help to
-check if the file is correct. For this I found two good options,
-<tt>debmake -k</tt> and <tt>license-reconcile</tt>. The former seem
-to focus on license types and file matching, and is able to detect
-ineffective blocks in the copyright file. The latter reports missing
-copyright holders and years, but was confused by inconsistent license
-names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
-fix all issues reported by them before uploading. But I do not know
-if the tools and the ftpmasters agree on what is important to fix in a
-copyright file, so the package might still be rejected.</p>
-
-<p>The devscripts tool <tt>licensecheck</tt> deserve mentioning. It
-will read through the source and try to find all copyright statements.
-It is not comparing the result to the content of debian/copyright, but
-can be useful when verifying the content of the copyright file.</p>
-
-<p>Are you aware of better tools in Debian to create and update
-debian/copyright file. Please let me know, or blog about it on
-planet.debian.org.</p>
-
-<p>As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
-
-<p><strong>Update 2016-02-20</strong>: I got a tip from Mike Gabriel
-on how to use licensecheck and cdbs to create a draft copyright file
-
-<p><pre>
-licensecheck --copyright -r `find * -type f` | \
- /usr/lib/cdbs/licensecheck2dep5 > debian/copyright.auto
-</pre></p>
-
-<p>He mentioned that he normally check the generated file into the
-version control system to make it easier to discover license and
-copyright changes in the upstream source. I will try to do the same
-with my packages in the future.</p>
-
-<p><strong>Update 2016-02-21</strong>: The cme author recommended
-against using -quiet for new users, so I removed it from the proposed
-command line.</p>
-</description>
- </item>
-
- <item>
- <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
- <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
- <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
- <description><p>The <a href="https://wiki.debian.org/DEP-11">appstream system</a>
-is taking shape in Debian, and one provided feature is a very
-convenient way to tell you which package to install to make a given
-firmware file available when the kernel is looking for it. This can
-be done using apt-file too, but that is for someone else to blog
-about. :)</p>
-
-<p>Here is a small recipe to find the package with a given firmware
-file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
-picked from the set of firmware announced using appstream in Debian
-unstable. In general you would be looking for the firmware requested
-by the kernel during kernel module loading. To find the package
-providing the example file, do like this:</p>
-
-<blockquote><pre>
-% apt install appstream
-[...]
-% apt update
-[...]
-% appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
- awk '/Package:/ {print $2}'
-firmware-qlogic
-%
-</pre></blockquote>
-
-<p>See <a href="https://wiki.debian.org/AppStream/Guidelines">the
-appstream wiki</a> page to learn how to embed the package metadata in
-a way appstream can use.</p>
-
-<p>This same approach can be used to find any package supporting a
-given MIME type. This is very useful when you get a file you do not
-know how to handle. First find the mime type using <tt>file
---mime-type</tt>, and next look up the package providing support for
-it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
-and you can find all packages handling this type like this:</p>
-
-<blockquote><pre>
-% apt install appstream
-[...]
-% apt update
-[...]
-% appstreamcli what-provides mimetype image/svg+xml | \
- awk '/Package:/ {print $2}'
-bkchem
-phototonic
-inkscape
-shutter
-tetzle
-geeqie
-xia
-pinta
-gthumb
-karbon
-comix
-mirage
-viewnior
-postr
-ristretto
-kolourpaint4
-eog
-eom
-gimagereader
-midori
-%
-</pre></blockquote>
-
-<p>I believe the MIME types are fetched from the desktop file for
-packages providing appstream metadata.</p>
-</description>
- </item>
-
- <item>
- <title>Creepy, visualise geotagged social media information - nice free software</title>
- <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
- <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
- <description><p>Most people seem not to realise that every time they walk around
-with the computerised radio beacon known as a mobile phone their
-position is tracked by the phone company and often stored for a long
-time (like every time a SMS is received or sent). And if their
-computerised radio beacon is capable of running programs (often called
-mobile apps) downloaded from the Internet, these programs are often
-also capable of tracking their location (if the app requested access
-during installation). And when these programs send out information to
-central collection points, the location is often included, unless
-extra care is taken to not send the location. The provided
-information is used by several entities, for good and bad (what is
-good and bad, depend on your point of view). What is certain, is that
-the private sphere and the right to free movement is challenged and
-perhaps even eradicated for those announcing their location this way,
-when they share their whereabouts with private and public
-entities.</p>
-
-<p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png"></p>
-
-<p>The phone company logs provide a register of locations to check out
-when one want to figure out what the tracked person was doing. It is
-unavailable for most of us, but provided to selected government
-officials, company staff, those illegally buying information from
-unfaithful servants and crackers stealing the information. But the
-public information can be collected and analysed, and a free software
-tool to do so is called
-<a href="http://www.geocreepy.com/">Creepy or Cree.py</a>. I
-discovered it when I read
-<a href="http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html">an
-article about Creepy</a> in the Norwegian newspaper Aftenposten i
-November 2014, and decided to check if it was available in Debian.
-The python program was in Debian, but
-<a href="https://tracker.debian.org/pkg/creepy">the version in
-Debian</a> was completely broken and practically unmaintained. I
-uploaded a new version which did not work quite right, but did not
-have time to fix it then. This Christmas I decided to finally try to
-get Creepy operational in Debian. Now a fixed version is available in
-Debian unstable and testing, and almost all Debian specific patches
-are now included
-<a href="https://github.com/jkakavas/creepy">upstream</a>.</p>
-
-<p>The Creepy program visualises geolocation information fetched from
-Twitter, Instagram, Flickr and Google+, and allow one to get a
-complete picture of every social media message posted recently in a
-given area, or track the movement of a given individual across all
-these services. Earlier it was possible to use the search API of at
-least some of these services without identifying oneself, but these
-days it is impossible. This mean that to use Creepy, you need to
-configure it to log in as yourself on these services, and provide
-information to them about your search interests. This should be taken
-into account when using Creepy, as it will also share information
-about yourself with the services.</p>
-
-<p>The picture above show the twitter messages sent from (or at least
-geotagged with a position from) the city centre of Oslo, the capital
-of Norway. One useful way to use Creepy is to first look at
-information tagged with an area of interest, and next look at all the
-information provided by one or more individuals who was in the area.
-I tested it by checking out which celebrity provide their location in
-twitter messages by checkout out who sent twitter messages near a
-Norwegian TV station, and next could track their position over time,
-making it possible to locate their home and work place, among other
-things. A similar technique have been
-<a href="http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl">used
-to locate Russian soldiers in Ukraine</a>, and it is both a powerful
-tool to discover lying governments, and a useful tool to help people
-understand the value of the private information they provide to the
-public.</p>
-
-<p>The package is not trivial to backport to Debian Stable/Jessie, as
-it depend on several python modules currently missing in Jessie (at
-least python-instagram, python-flickrapi and
-python-requests-toolbelt).</p>
-
-<p>(I have uploaded
-<a href="https://screenshots.debian.net/package/creepy">the image to
-screenshots.debian.net</a> and licensed it under the same terms as the
-Creepy program in Debian.)</p>
-</description>
- </item>
-
</channel>
</rss>
projects / homepage.git / blobdiff