<link>http://people.skolelinux.org/pere/blog/</link>
+ <item>
+ <title>More reliable vlc bittorrent plugin in Debian (version 2.9)</title>
+ <link>http://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html</guid>
+ <pubDate>Sun, 24 May 2020 17:00:00 +0200</pubDate>
+ <description><p>I am very happy to report that a more reliable
+<a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">VLC
+bittorrent plugin</a> was just uploaded into debian. This fixes a
+couple of crash bugs in the plugin, hopefully making the VLC
+experience even better when streaming directly from a bittorrent
+source. 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:</p>
+
+<p><pre>
+apt install vlc-plugin-bittorrent
+</pre></p>
+
+<p>After it is installed, you can try to use it to play a file
+downloaded live via bittorrent like this:
+
+<p><pre>
+vlc https://archive.org/download/Glass_201703/Glass_201703_archive.torrent
+</pre></p>
+
+<p>It also support magnet links and local .torrent files.</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>
+</description>
+ </item>
+
<item>
<title>Debian Edu interview: Yvan Masson</title>
<link>http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html</link>
one" solution: everything has been thought of and prepared to ease
installation and usage.</p>
-I like Free Software because I hate using something that I can not
+<p>I like Free Software because I hate using something that I can not
understand. I do not say that I can understand everything nor that I
want to understand everything, but knowing that someone / some company
intentionally prevents me from understanding how things work is really
password set on the room. The Jami daemon leak memory like crazy
(approximately 1 GiB a minute) when I am connected to the video
conference, so I had to restart the client every 7-10 minutes, which
-is not a great. I tried to get other SIP Linux clients to work
+is not great. I tried to get other SIP Linux clients to work
without success, so I decided I would have to live with this wart
until someone managed to fix the leak in the dring code base. But
another problem showed up once the rooms were password protected. I
consist of the room ID (a number), an @ character and the IP address
of the Zoom SIP gateway. But Zoom understand a lot more than just the
room ID in front of the at sign. The format is "<tt>[Meeting
-ID].[Password].[Layout].[Host Key]</tt>", and you can hear see how you
+ID].[Password].[Layout].[Host Key]</tt>", and you can here see how you
can both enter password, control the layout (full screen, active
presence and gallery) and specify the host key to start the meeting.
The full SIP address entered into Jami to provide the password will