X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/9da9f491746b957621e4452c19460a6168499733..34756d69147cd313c33c2953926f11bd4f799f6f:/blog/archive/2020/05/05.rss

diff --git a/blog/archive/2020/05/05.rss b/blog/archive/2020/05/05.rss
index dfb70e3d10..fbda7c7820 100644
--- a/blog/archive/2020/05/05.rss
+++ b/blog/archive/2020/05/05.rss
@@ -3,13 +3,46 @@
 	<channel>
 		<title>Petter Reinholdtsen - Entries from May 2020</title>
 		<description>Entries from May 2020</description>
-                <link>http://people.skolelinux.org/pere/blog/</link>
+                <link>https://people.skolelinux.org/pere/blog/</link>
 
 	
+	<item>
+		<title>More reliable vlc bittorrent plugin in Debian (version 2.9)</title>
+		<link>https://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html</link>        
+		<guid isPermaLink="true">https://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>&lt;p&gt;I am very happy to report that a more reliable
+&lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;VLC
+bittorrent plugin&lt;/a&gt; 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:&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;It also support magnet links and local .torrent files.&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>Debian Edu interview: Yvan Masson</title>
-		<link>http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html</link>        
-		<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html</guid>
+		<link>https://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html</link>        
+		<guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html</guid>
                 <pubDate>Tue, 12 May 2020 06:30:00 +0200</pubDate>
 		<description>&lt;p&gt;It has been way too long since my last interview, but as the
 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt;
@@ -122,8 +155,8 @@ Skolelinux is a really good question :-)&lt;/p&gt;
 	
 	<item>
 		<title>Jami as a Zoom client, a trick for password protected rooms...</title>
-		<link>http://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</link>        
-		<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</guid>
+		<link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</link>        
+		<guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</guid>
                 <pubDate>Fri, 8 May 2020 13:30:00 +0200</pubDate>
 		<description>&lt;p&gt;Half a year ago,
 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html&quot;&gt;I
@@ -144,7 +177,7 @@ Zoom meetings with free software clients.&lt;/p&gt;
 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
@@ -171,7 +204,7 @@ connect via SIP do not mention this.  The SIP address to use normally
 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 &quot;&lt;tt&gt;[Meeting
-ID].[Password].[Layout].[Host Key]&lt;/tt&gt;&quot;, and you can hear see how you
+ID].[Password].[Layout].[Host Key]&lt;/tt&gt;&quot;, 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