Generated.

[homepage.git] / blog / index.rss

<?xml version="1.0" encoding="utf-8"?>
<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
        <channel>
                <title>Petter Reinholdtsen</title>
                <description></description>
                <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>Learn to program with Minetest on Debian</title>
                <link>http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</guid>
                <pubDate>Sat, 15 Dec 2018 15:30:00 +0100</pubDate>
                <description>&lt;p&gt;A fun way to learn how to program
&lt;a href=&quot;https://www.python.org/&quot;&gt;Python&lt;/a&gt; is to follow the
instructions in the book
&quot;&lt;a href=&quot;https://nostarch.com/programwithminecraft&quot;&gt;Learn to program
with Minecraft&lt;/a&gt;&quot;, which introduces programming in Python to people
who like to play with Minecraft.  The book uses a Python library to
talk to a TCP/IP socket with an API accepting build instructions and
providing information about the current players in a Minecraft world.
The TCP/IP API was first created for the Minecraft implementation for
Raspberry Pi, and has since been ported to some server versions of
Minecraft.  The book contain recipes for those using Windows, MacOSX
and Raspian.  But a little known fact is that you can follow the same
recipes using the free software construction game
&lt;a href=&quot;https://minetest.net/&quot;&gt;Minetest&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;There is &lt;a href=&quot;https://github.com/sprintingkiwi/pycraft_mod&quot;&gt;a
Minetest module implementing the same API&lt;/a&gt;, making it possible to
use the Python programs coded to talk to Minecraft with Minetest too.
I
&lt;a href=&quot;https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html&quot;&gt;uploaded
this module&lt;/a&gt; to Debian two weeks ago, and as soon as it clears the
FTP masters NEW queue, learning to program Python with Minetest on
Debian will be a simple &#39;apt install&#39; away.  The Debian package is
maintained as part of the Debian Games team, and
&lt;a href=&quot;https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft&quot;&gt;the
packaging rules&lt;/a&gt; are currently located under &#39;unfinished&#39; on
Salsa.&lt;/p&gt;

&lt;p&gt;You will most likely need to install several of the Minetest
modules in Debian for the examples included with the library to work
well, as there are several blocks used by the example scripts that are
provided via modules in Minetest.  Without the required blocks, a
simple stone block is used instead.  My initial testing with a analog
clock did not get gold arms as instructed in the python library, but
instead used stone arms.&lt;/p&gt;

&lt;p&gt;I tried to find a way to add the API to the desktop version of
Minecraft, but were unable to find any working recipes.  The
&lt;a href=&quot;https://www.epiphanydigest.com/tag/minecraft-python-api/&quot;&gt;recipes&lt;/a&gt;
I &lt;a href=&quot;https://github.com/kbsriram/mcpiapi&quot;&gt;found&lt;/a&gt; are only
working with a standalone Minecraft server setup.  Are there any
options to use with the normal desktop version?&lt;/p&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Non-blocking bittorrent plugin for vlc</title>
                <link>http://people.skolelinux.org/pere/blog/Non_blocking_bittorrent_plugin_for_vlc.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Non_blocking_bittorrent_plugin_for_vlc.html</guid>
                <pubDate>Wed, 12 Dec 2018 07:20:00 +0100</pubDate>
                <description>&lt;p&gt;A few hours ago, a new and improved version (2.4) of
&lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;the VLC
bittorrent plugin&lt;/a&gt; was uploaded to Debian.  This new version
include a complete rewrite of the bittorrent related code, which seem
to make the plugin non-blocking.  This mean you can actually exit VLC
even when the plugin seem to be unable to get the bittorrent streaming
started.  The new version also include support for filtering playlist
by file extension using command line options, if you want to avoid
processing audio, video or images.  The package is currently in Debian
unstable, but should be available in Debian testing in two days.  To
test it, simply install it like this:&lt;/p&gt;

&lt;p&gt;&lt;pre&gt;
apt install vlc-plugin-bittorrent
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;After it is installed, you can try to use it to play a file
downloaded live via bittorrent like this:

&lt;p&gt;&lt;pre&gt;
vlc https://archive.org/download/Glass_201703/Glass_201703_archive.torrent
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Retten til kontant betaling er en rettighet som må brukes for å beholdes</title>
                <link>http://people.skolelinux.org/pere/blog/Retten_til_kontant_betaling_er_en_rettighet_som_m__brukes_for___beholdes.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Retten_til_kontant_betaling_er_en_rettighet_som_m__brukes_for___beholdes.html</guid>
                <pubDate>Tue, 11 Dec 2018 10:00:00 +0100</pubDate>
                <description>&lt;p&gt;&lt;a href=&quot;https://www.fn.no/Om-FN/Avtaler/Menneskerettigheter/FNs-verdenserklaering-om-menneskerettigheter&quot;&gt;FNs
menneskerettighetserklæring&lt;/a&gt; artikkel 13 første punkt lyder som
følger:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;
Enhver har rett til å bevege seg fritt og til fritt å velge
oppholdssted innenfor en stats grenser.
&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;Det er altså en menneskerett å kunne bevege seg fritt i landet.
For å bevege seg fritt i landet, så må en kunne bevege seg uten å bli
sporet.  Det vil i dagens samfunn innebære å bevege seg uten å legge
igjen digitale spor og uten å være radiomerket.  Hvis en vet at ens
bevegelser, hvor en befinner seg når, og hvem som befinner seg i
nærheten, blir samlet inn og gjort tilgjengelig for fremmede, det være
seg myndighetene eller private organisasjoner, så kan en ikke lenger
bevege seg fritt.  Dette gjør at det er en forutsetning for å ha glede
av retten til å bevege seg fritt i landet at en motstår fristelsen til
å legge igjen digitale spor når en betaler for seg.  Rettigheter som
ikke blir brukt, blir fjernet.  Den eneste måten i dag å unngå å legge
igjen digitale spor når en betaler for seg, er å betale med kontanter,
samt takke nei til å legge igjen navn og adresse (slik f.eks. Elkjøp
ber om &amp;mdash; jeg sier de kan legge inn «anonym anonym» når
datasystemet deres trenger et navn).  Personlig anbefaler jeg å
konsekvent bruke kontant betaling når man beveger seg rundt, for å
bidra til forsvaret av menneskerettighetene i Norge.  Kanskje noe også
for deg?  Merk at det ikke er tilstrekkelig for å unngå sporing å
betale med kontanter, men det er et lite steg i riktig retning.&lt;/p&gt;

&lt;p&gt;Det er flere andre argumenter i tillegg til
menneskerettighetsargumentet for å bruke kontanter.  I går hadde
Dagbladet en utmerket kommentar av sin journalist John Olav Egeland om
hvilket
&lt;a href=&quot;https://www.dagbladet.no/kultur/kontantlost-diktatur/70543434&quot;&gt;kontantløst
diktatur&lt;/a&gt; som venter oss hvis mange nok slutter å insistere på å
betale med kontanter.  Jeg anbefaler deg å lese den.&lt;/p&gt;

&lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
til min adresse
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Why is your site not using Content Security Policy / CSP?</title>
                <link>http://people.skolelinux.org/pere/blog/Why_is_your_site_not_using_Content_Security_Policy___CSP_.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_is_your_site_not_using_Content_Security_Policy___CSP_.html</guid>
                <pubDate>Sun, 9 Dec 2018 15:00:00 +0100</pubDate>
                <description>&lt;p&gt;Yesterday, I had the pleasure of watching on Frikanalen the OWASP
talk by Scott Helme titled
&quot;&lt;a href=&quot;https://frikanalen.no/video/626080/&quot;&gt;What We’ve Learned From
Billions of Security Reports&lt;/a&gt;&quot;.  I had not heard of the
&lt;a href=&quot;https://en.wikipedia.org/wiki/Content_Security_Policy&quot;&gt;Content
Security Policy standard&lt;/a&gt; nor its ability to &quot;call home&quot; when a
browser detect a policy breach (I do not follow web page design
development much these days), and found the talk very illuminating.&lt;/p&gt;

&lt;p&gt;The mechanism allow a web site owner to use HTTP headers to tell
visitors web browser which sources (internal and external) are allowed to
be used on the web site.  Thus it become possible to enforce a &quot;only
local content&quot; policy despite web designers urge to fetch programs
from random sites on the Internet, like the one
&lt;a href=&quot;https://securityaffairs.co/wordpress/68966/hacking/browsealoud-plugin-hack.html&quot;&gt;enabling
the attack&lt;/a&gt; reported by Scott Helme earlier this year.&lt;/p&gt;

&lt;p&gt;Using CSP seem like an obvious thing for a site admin to implement
to take some control over the information leak that occur when
external sources are used to render web pages, it is a mystery more
sites are not using CSP?  It is being
&lt;a href=&quot;https://www.w3.org/TR/CSP/&quot;&gt;standardized under W3C&lt;/a&gt; these
days, and is supposed by most web browsers&lt;/p&gt;

&lt;p&gt;I managed to find &lt;a href=&quot;https://github.com/mozilla/django-csp&quot;&gt;a
Django middleware for implementing CSP&lt;/a&gt; and was happy to discover
it was already in Debian.  I plan to use it to add CSP support to the
Frikanalen web site soon.&lt;/p&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>New and improved Frikanalen Kodi addon version 0.0.3</title>
                <link>http://people.skolelinux.org/pere/blog/New_and_improved_Frikanalen_Kodi_addon_version_0_0_3.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_and_improved_Frikanalen_Kodi_addon_version_0_0_3.html</guid>
                <pubDate>Thu, 8 Nov 2018 10:30:00 +0100</pubDate>
                <description>&lt;p&gt;If you read my blog regularly, you probably know I am involved in
running and developing the &lt;a href=&quot;https://frikanalen.no/&quot;&gt;Norwegian
TV channel Frikanalen&lt;/a&gt;.  It is an open channel, allowing everyone
in Norway to publish videos on a TV channel with national coverage.
You can think of it as Youtube for national television.
In addition to distribution on RiksTV and Uninett, Frikanalen is also
available as a Kodi addon.  The last few days I have updated the code
to add more features.  A
&lt;a href=&quot;https://kodi.tv/addon/plugins-video-add-ons/frikanalen-nett-tv&quot;&gt;new
and improved version 0.0.3 Frikanalen addon&lt;/a&gt; was just made
available via the Kodi repositories.  This new version include a
option to browse videos by category, as well as free text search
in the video archive.  It will now also show the video duration in the
video lists, which were missing earlier.  A new and experimental
link to the HD video stream currently being worked on is provided, for
those that want to see what the &lt;a href=&quot;https://casparcg.com/&quot;&gt;CasparCG&lt;/a&gt;
output look like.  The alternative is the SD video stream, generated
using MLT.  CasparCG is controlled by our
&lt;a href=&quot;https://github.com/Frikanalen/mltplayout/&quot;&gt;mltplayout
server&lt;/a&gt; which instead of talking to mlt is giving PLAY instructions
to the CasparCG server when it is time to start a new program.&lt;/p&gt;

&lt;p&gt;By now, you are probably wondering what kind of content is being
played on the channel.  These days, it is filled with technical
presentations like those from &lt;a href=&quot;https://www.nuug.no/&quot;&gt;NUUG&lt;/a&gt;,
&lt;a href=&quot;https://www.debconf.org/&quot;&gt;Debconf&lt;/a&gt;, Makercon, and TED,
but there are also some periods with
&lt;a href=&quot;https://www.empo.no/&quot;&gt;EMPT TV&lt;/a&gt; and
&lt;a href=&quot;https://www.p7.no/&quot;&gt;P7&lt;/a&gt;.

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Time for an official MIME type for patches?</title>
                <link>http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
                <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
                <description>&lt;p&gt;As part of my involvement in
&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
emails into a test instance of the archive to see how well this would
go.  I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
notmuch email database&lt;/a&gt;, all public emails sent to me via
@lists.debian.org, giving me a set of around 216 000 emails to import.
In the process, I had a look at the various attachments included in
these emails, to figure out what to do with attachments, and noticed
that one of the most common attachment formats do not have
&lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
official MIME type&lt;/a&gt; registered with IANA/IETF.  The output from
diff, ie the input for patch, is on the top 10 list of formats
included in these emails.  At the moment people seem to use either
text/x-patch or text/x-diff, but neither is officially registered.  It
would be better if one official MIME type were registered and used
everywhere.&lt;/p&gt;

&lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
up the topic on
&lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
media-types mailing list&lt;/a&gt;.  If you are interested in discussion
which MIME type to use as the official for patch files, or involved in
making software using a MIME type for patches, perhaps you would like
to join the discussion?&lt;/p&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Measuring the speaker frequency response using the AUDMES free software GUI - nice free software</title>
                <link>http://people.skolelinux.org/pere/blog/Measuring_the_speaker_frequency_response_using_the_AUDMES_free_software_GUI___nice_free_software.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Measuring_the_speaker_frequency_response_using_the_AUDMES_free_software_GUI___nice_free_software.html</guid>
                <pubDate>Mon, 22 Oct 2018 08:40:00 +0200</pubDate>
                <description>&lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2018-10-22-audmes-measure-speakers.png&quot; align=&quot;right&quot; width=&quot;40%&quot;/&gt;&lt;/p&gt;

&lt;p&gt;My current home stereo is a patchwork of various pieces I got on
flee markeds over the years.  It is amazing what kind of equipment
show up there.  I&#39;ve been wondering for a while if it was possible to
measure how well this equipment is working together, and decided to
see how far I could get using free software.  After trawling the web I
came across an article from DIY Audio and Video on
&lt;a href=&quot;https://www.diyaudioandvideo.com/Tutorial/SpeakerResponseTesting/&quot;&gt;Speaker
Testing and Analysis&lt;/a&gt; describing how to test speakers, and it listing
several software options, among them
&lt;a href=&quot;https://sourceforge.net/projects/audmes/&quot;&gt;AUDio MEasurement
System (AUDMES)&lt;/a&gt;.  It is the only free software system I could find
focusing on measuring speakers and audio frequency response.  In the
process I also found an interesting article from NOVO on
&lt;a href=&quot;http://novo.press/understanding-speaker-specifications-and-frequency-response/&quot;&gt;Understanding
Speaker Specifications and Frequency Response&lt;/a&gt; and an article from
ecoustics on
&lt;a href=&quot;https://www.ecoustics.com/articles/understanding-speaker-frequency-response/&quot;&gt;Understanding
Speaker Frequency Response&lt;/a&gt;, with a lot of information on what to
look for and how to interpret the graphs.  Armed with this knowledge,
I set out to measure the state of my speakers.&lt;/p&gt;

&lt;p&gt;The first hurdle was that AUDMES hadn&#39;t seen a commit for 10 years
and did not build with current compilers and libraries.  I got in
touch with its author, who no longer was spending time on the program
but gave me write access to the subversion repository on Sourceforge.
The end result is that now the code build on Linux and is capable of
saving and loading the collected frequency response data in CSV
format.  The application is quite nice and flexible, and I was able to
select the input and output audio interfaces independently.  This made
it possible to use a USB mixer as the input source, while sending
output via my laptop headphone connection.  I lacked the hardware and
cabling to figure out a different way to get independent cabling to
speakers and microphone.&lt;/p&gt;

&lt;p&gt;Using this setup I could see how a large range of high frequencies
apparently were not making it out of my speakers.  The picture show
the frequency response measurement of one of the speakers.  Note the
frequency lines seem to be slightly misaligned, compared to the CSV
output from the program.  I can not hear several of these are high
frequencies, according to measurement from
&lt;a href=&quot;http://freehearingtestsoftware.com&quot;&gt;Free Hearing Test
Software&lt;/a&gt;, an freeware system to measure your hearing (still
looking for a free software alternative), so I do not know if they are
coming out out the speakers.  I thus do not quite know how to figure
out if the missing frequencies is a problem with the microphone, the
amplifier or the speakers, but I managed to rule out the audio card in my
PC by measuring my Bose noise canceling headset using its own
microphone.  This setup was able to see the high frequency tones, so
the problem with my stereo had to be in the amplifier or speakers.&lt;/p&gt;

&lt;p&gt;Anyway, to try to role out one factor I ended up picking up a new
set of speakers at a flee marked, and these work a lot better than the
old speakers, so I guess the microphone and amplifier is OK.  If you
need to measure your own speakers, check out AUDMES.  If more people
get involved, perhaps the project could become good enough to
&lt;a href=&quot;https://bugs.debian.org/910876&quot;&gt;include in Debian&lt;/a&gt;?  And if
you know of some other free software to measure speakers and amplifier
performance, please let me know.  I am aware of the freeware option
&lt;a href=&quot;https://www.roomeqwizard.com/&quot;&gt;REW&lt;/a&gt;, but I want something
that can be developed also when the vendor looses interest.&lt;/p&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Web browser integration of VLC with Bittorrent support</title>
                <link>http://people.skolelinux.org/pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Web_browser_integration_of_VLC_with_Bittorrent_support.html</guid>
                <pubDate>Sun, 21 Oct 2018 09:50:00 +0200</pubDate>
                <description>&lt;p&gt;Bittorrent is as far as I know, currently the most efficient way to
distribute content on the Internet.  It is used all by all sorts of
content providers, from national TV stations like
&lt;a href=&quot;https://www.nrk.no/&quot;&gt;NRK&lt;/a&gt;, Linux distributors like
&lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; and
&lt;a href=&quot;https://www.ubuntu.com/&quot;&gt;Ubuntu&lt;/a&gt;, and of course the
&lt;a href=&quot;https://archive.org/&quot;&gt;Internet archive&lt;/A&gt;.

&lt;p&gt;Almost a month ago
&lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;a new
package adding Bittorrent support to VLC&lt;/a&gt; became available in
Debian testing and unstable.  To test it, simply install it like
this:&lt;/p&gt;

&lt;p&gt;&lt;pre&gt;
apt install vlc-plugin-bittorrent
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;Since the plugin was made available for the first time in Debian,
several improvements have been made to it.  In version 2.2-4, now
available in both testing and unstable, a desktop file is provided to
teach browsers to start VLC when the user click on torrent files or
magnet links.  The last part is thanks to me finally understanding
what the strange x-scheme-handler style MIME types in desktop files
are used for.  By adding x-scheme-handler/magnet to the MimeType entry
in the desktop file, at least the browsers Firefox and Chromium will
suggest to start VLC when selecting a magnet URI on a web page.  The
end result is that now, with the plugin installed in Buster and Sid,
one can visit any
&lt;a href=&quot;https://archive.org/details/CopyingIsNotTheft1080p&quot;&gt;Internet
Archive page with movies&lt;/a&gt; using a web browser and click on the
torrent link to start streaming the movie.&lt;/p&gt;

&lt;p&gt;Note, there is still some misfeatures in the plugin.  One is the
fact that it will hang and
&lt;a href=&quot;https://github.com/johang/vlc-bittorrent/issues/13&quot;&gt;block VLC
from exiting until the torrent streaming starts&lt;/a&gt;.  Another is the
fact that it
&lt;a href=&quot;https://github.com/johang/vlc-bittorrent/issues/9&quot;&gt;will pick
and play a random file in a multi file torrent&lt;/a&gt;.  This is not
always the video file you want.  Combined with the first it can be a
bit hard to get the video streaming going.  But when it work, it seem
to do a good job.&lt;/p&gt;

&lt;p&gt;For the Debian packaging, I would love to find a good way to test
if the plugin work with VLC using autopkgtest.  I tried, but do not
know enough of the inner workings of VLC to get it working.  For now
the autopkgtest script is only checking if the .so file was
successfully loaded by VLC.  If you have any suggestions, please
submit a patch to the Debian bug tracking system.&lt;/p&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Release 0.2 of free software archive system Nikita announced</title>
                <link>http://people.skolelinux.org/pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html</guid>
                <pubDate>Thu, 18 Oct 2018 14:40:00 +0200</pubDate>
                <description>&lt;p&gt;This morning, the new release of the
&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;Nikita
Noark 5 core project&lt;/a&gt; was
&lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2018-October/000406.html&quot;&gt;announced
on the project mailing list&lt;/a&gt;.  The free software solution is an
implementation of the Norwegian archive standard Noark 5 used by
government offices in Norway.  These were the changes in version 0.2
since version 0.1.1 (from NEWS.md):

&lt;ul&gt;
  &lt;li&gt;Fix typos in REL names&lt;/li&gt;
  &lt;li&gt;Tidy up error message reporting&lt;/li&gt;
  &lt;li&gt;Fix issue where we used Integer.valueOf(), not Integer.getInteger()&lt;/li&gt;
  &lt;li&gt;Change some String handling to StringBuffer&lt;/li&gt;
  &lt;li&gt;Fix error reporting&lt;/li&gt;
  &lt;li&gt;Code tidy-up&lt;/li&gt;
  &lt;li&gt;Fix issue using static non-synchronized SimpleDateFormat to avoid 
      race conditions&lt;/li&gt;
  &lt;li&gt;Fix problem where deserialisers were treating integers as strings&lt;/li&gt;
  &lt;li&gt;Update methods to make them null-safe&lt;/li&gt;
  &lt;li&gt;Fix many issues reported by coverity&lt;/li&gt;
  &lt;li&gt;Improve equals(), compareTo() and hash() in domain model&lt;/li&gt;
  &lt;li&gt;Improvements to the domain model for metadata classes&lt;/li&gt;
  &lt;li&gt;Fix CORS issues when downloading document&lt;/li&gt;
  &lt;li&gt;Implementation of case-handling with registryEntry and document upload&lt;/li&gt;
  &lt;li&gt;Better support in Javascript for OPTIONS&lt;/li&gt;
  &lt;li&gt;Adding concept description of mail integration&lt;/li&gt;
  &lt;li&gt;Improve setting of default values for GET on ny-journalpost&lt;/li&gt;
  &lt;li&gt;Better handling of required values during deserialisation &lt;/li&gt;
  &lt;li&gt;Changed tilknyttetDato (M620) from date to dateTime&lt;/li&gt;
  &lt;li&gt;Corrected some opprettetDato (M600) (de)serialisation errors.&lt;/li&gt;
  &lt;li&gt;Improve parse error reporting.&lt;/li&gt;
  &lt;li&gt;Started on OData search and filtering.&lt;/li&gt;
  &lt;li&gt;Added Contributor Covenant Code of Conduct to project.&lt;/li&gt;
  &lt;li&gt;Moved repository and project from Github to Gitlab.&lt;/li&gt;
  &lt;li&gt;Restructured repository, moved code into src/ and web/.&lt;/li&gt;
  &lt;li&gt;Updated code to use Spring Boot version 2.&lt;/li&gt;
  &lt;li&gt;Added support for OAuth2 authentication.&lt;/li&gt;
  &lt;li&gt;Fixed several bugs discovered by Coverity.&lt;/li&gt;
  &lt;li&gt;Corrected handling of date/datetime fields.&lt;/li&gt;
  &lt;li&gt;Improved error reporting when rejecting during deserializatoin.&lt;/li&gt;
  &lt;li&gt;Adjusted default values provided for ny-arkivdel, ny-mappe,
   ny-saksmappe, ny-journalpost and ny-dokumentbeskrivelse.&lt;/li&gt;
  &lt;li&gt;Several fixes for korrespondansepart*.&lt;/li&gt;
  &lt;li&gt;Updated web GUI:
     &lt;ul&gt;
       &lt;li&gt;Now handle both file upload and download.&lt;/li&gt;
       &lt;li&gt;Uses new OAuth2 authentication for login.&lt;/li&gt;
       &lt;li&gt;Forms now fetches default values from API using GET.&lt;/li&gt;
       &lt;li&gt;Added RFC 822 (email), TIFF and JPEG to list of possible file formats.&lt;/li&gt;
     &lt;/ul&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The changes and improvements are extensive.  Running diffstat on
the changes between git tab 0.1.1 and 0.2 show 1098 files changed,
108666 insertions(+), 54066 deletions(-).&lt;/p&gt;

&lt;p&gt;If free and open standardized archiving API sound interesting to
you, please contact us on IRC
(&lt;a href=&quot;irc://irc.freenode.net/%23nikita&quot;&gt;#nikita on
irc.freenode.net&lt;/a&gt;) or email
(&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
mailing list&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Fetching trusted timestamps using the rfc3161ng python module</title>
                <link>http://people.skolelinux.org/pere/blog/Fetching_trusted_timestamps_using_the_rfc3161ng_python_module.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fetching_trusted_timestamps_using_the_rfc3161ng_python_module.html</guid>
                <pubDate>Mon, 8 Oct 2018 12:30:00 +0200</pubDate>
                <description>&lt;p&gt;I have  earlier covered the basics of trusted timestamping using the
&#39;openssl ts&#39; client.  See blog post for
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Public_Trusted_Timestamping_services_for_everyone.html&quot;&gt;2014&lt;/a&gt;,
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/syslog_trusted_timestamp___chain_of_trusted_timestamps_for_your_syslog.html&quot;&gt;2016&lt;/a&gt;
and
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html&quot;&gt;2017&lt;/a&gt;
for those stories.  But some times I want to integrate the timestamping
in other code, and recently I needed to integrate it into Python.
After searching a bit, I found
&lt;a href=&quot;https://dev.entrouvert.org/projects/python-rfc3161&quot;&gt;the
rfc3161 library&lt;/a&gt; which seemed like a good fit, but I soon
discovered it only worked for python version 2, and I needed something
that work with python version 3.  Luckily I next came across
&lt;a href=&quot;https://github.com/trbs/rfc3161ng/&quot;&gt;the rfc3161ng library&lt;/a&gt;,
a fork of the original rfc3161 library.  Not only is it working with
python 3, it have fixed a few of the bugs in the original library, and
it has an active maintainer.  I decided to wrap it up and make it
&lt;a href=&quot;https://tracker.debian.org/pkg/python-rfc3161ng&quot;&gt;available in
Debian&lt;/a&gt;, and a few days ago it entered Debian unstable and testing.&lt;/p&gt;

&lt;p&gt;Using the library is fairly straight forward.  The only slightly
problematic step is to fetch the required certificates to verify the
timestamp.  For some services it is straight forward, while for others
I have not yet figured out how to do it.  Here is a small standalone
code example based on of the integration tests in the library code:&lt;/p&gt;

&lt;pre&gt;
#!/usr/bin/python3

&quot;&quot;&quot;

Python 3 script demonstrating how to use the rfc3161ng module to
get trusted timestamps.

The license of this code is the same as the license of the rfc3161ng
library, ie MIT/BSD.

&quot;&quot;&quot;

import os
import pyasn1.codec.der
import rfc3161ng
import subprocess
import tempfile
import urllib.request

def store(f, data):
    f.write(data)
    f.flush()
    f.seek(0)

def fetch(url, f=None):
    response = urllib.request.urlopen(url)
    data = response.read()
    if f:
        store(f, data)
    return data

def main():
    with tempfile.NamedTemporaryFile() as cert_f,\
         tempfile.NamedTemporaryFile() as ca_f,\
         tempfile.NamedTemporaryFile() as msg_f,\
         tempfile.NamedTemporaryFile() as tsr_f:

        # First fetch certificates used by service
        certificate_data = fetch(&#39;https://freetsa.org/files/tsa.crt&#39;, cert_f)
        ca_data_data = fetch(&#39;https://freetsa.org/files/cacert.pem&#39;, ca_f)

        # Then timestamp the message
        timestamper = \
            rfc3161ng.RemoteTimestamper(&#39;http://freetsa.org/tsr&#39;,
                                        certificate=certificate_data)
        data = b&quot;Python forever!\n&quot;
        tsr = timestamper(data=data, return_tsr=True)

        # Finally, convert message and response to something &#39;openssl ts&#39; can verify
        store(msg_f, data)
        store(tsr_f, pyasn1.codec.der.encoder.encode(tsr))
        args = [&quot;openssl&quot;, &quot;ts&quot;, &quot;-verify&quot;,
                &quot;-data&quot;, msg_f.name,
                &quot;-in&quot;, tsr_f.name,
                &quot;-CAfile&quot;, ca_f.name,
                &quot;-untrusted&quot;, cert_f.name]
        subprocess.check_call(args)

if &#39;__main__&#39; == __name__:
   main()
&lt;/pre&gt;

&lt;p&gt;The code fetches the required certificates, store them as temporary
files, timestamp a simple message, store the message and timestamp to
disk and ask &#39;openssl ts&#39; to verify the timestamp.  A timestamp is
around 1.5 kiB in size, and should be fairly easy to store for future
use.&lt;/p&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
</description>
        </item>
        
        </channel>
</rss>