Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 9a5e61baa66b0780bdbe8860514ed1df228083d9..146620278af0e86763d5cf5406ce1b0a891e9248 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,94 @@
                 <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" />
        
                 <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>Appstream just learned how to map hardware to packages too!</title>
+               <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
+                <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
+               <description>&lt;p&gt;I received a very nice Christmas present today.  As my regular
+readers probably know, I have been working on the
+&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
+system&lt;/a&gt; for many years.  The goal of the Isenkram system is to make
+it easier for users to figure out what to install to get a given piece
+of hardware to work in Debian, and a key part of this system is a way
+to map hardware to packages.  Isenkram have its own mapping database,
+and also uses data provided by each package using the AppStream
+metadata format.  And today,
+&lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
+Debian learned to look up hardware the same way Isenkram is doing it,
+ie using fnmatch():&lt;/p&gt;
+
+&lt;p&gt;&lt;pre&gt;
+% appstreamcli what-provides modalias \
+  usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
+Identifier: pymissile [generic]
+Name: pymissile
+Summary: Control original Striker USB Missile Launcher
+Package: pymissile
+% appstreamcli what-provides modalias usb:v0694p0002d0000
+Identifier: libnxt [generic]
+Name: libnxt
+Summary: utility library for talking to the LEGO Mindstorms NXT brick
+Package: libnxt
+---
+Identifier: t2n [generic]
+Name: t2n
+Summary: Simple command-line tool for Lego NXT
+Package: t2n
+---
+Identifier: python-nxt [generic]
+Name: python-nxt
+Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
+Package: python-nxt
+---
+Identifier: nbc [generic]
+Name: nbc
+Summary: C compiler for LEGO Mindstorms NXT bricks
+Package: nbc
+%
+&lt;/pre&gt;&lt;/p&gt;
+
+&lt;p&gt;A similar query can be done using the combined AppStream and
+Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
+
+&lt;p&gt;&lt;pre&gt;
+% isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
+pymissile
+% isenkram-lookup usb:v0694p0002d0000
+libnxt
+nbc
+python-nxt
+t2n
+%
+&lt;/pre&gt;&lt;/p&gt;
+
+&lt;p&gt;If you want to make this system a success and help Debian users
+make the most of the hardware they have, please
+help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
+AppStream metadata for your package following the guidelines&lt;/a&gt;
+documented in the wiki.  So far only 11 packages provide such
+information, among the several hundred hardware specific packages in
+Debian. The Isenkram database on the other hand contain 101 packages,
+mostly related to USB dongles.  Most of the packages with hardware
+mapping in AppStream are LEGO Mindstorms related, because I have, as
+part of my involvement in
+&lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
+team&lt;/a&gt; given priority to making sure LEGO users get proposed the
+complete set of packages in Debian for that particular hardware.  The
+team also got a nice Christmas present today.  The
+&lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
+package&lt;/a&gt; made it into Debian.  With this package in place, it is
+not possible to use the LEGO Mindstorms NXT unit with only free
+software, as the nxt-firmware package contain the source and firmware
+binaries for the NXT brick.&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&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+</description>
+       </item>
+       

        <item>
                <title>Isenkram updated with a lot more hardware-package mappings</title>
                <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
        <item>
                <title>Isenkram updated with a lot more hardware-package mappings</title>
                <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>


@@ -1093,118 +1181,5 @@ working.&lt;/p&gt;
 </description>
        </item>
        
 </description>
        </item>
        

-       <item>
-               <title>How to talk with your loved ones in private</title>
-               <link>http://people.skolelinux.org/pere/blog/How_to_talk_with_your_loved_ones_in_private.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_talk_with_your_loved_ones_in_private.html</guid>
-                <pubDate>Mon, 7 Nov 2016 10:25:00 +0100</pubDate>
-               <description>&lt;p&gt;A few days ago I ran a very biased and informal survey to get an
-idea about what options are being used to communicate with end to end
-encryption with friends and family.  I explicitly asked people not to
-list options only used in a work setting.  The background is the
-uneasy feeling I get when using Signal, a feeling shared by others as
-a blog post from Sander Venima about
-&lt;a href=&quot;https://sandervenema.ch/2016/11/why-i-wont-recommend-signal-anymore/&quot;&gt;why
-he do not recommend Signal anymore&lt;/a&gt; (with
-&lt;a href=&quot;https://news.ycombinator.com/item?id=12883410&quot;&gt;feedback from
-the Signal author available from ycombinator&lt;/a&gt;).  I wanted an
-overview of the options being used, and hope to include those options
-in a less biased survey later on.  So far I have not taken the time to
-look into the individual proposed systems.  They range from text
-sharing web pages, via file sharing and email to instant messaging,
-VOIP and video conferencing.  For those considering which system to
-use, it is also useful to have a look at
-&lt;a href=&quot;https://www.eff.org/secure-messaging-scorecard&quot;&gt;the EFF Secure
-messaging scorecard&lt;/a&gt; which is slightly out of date but still
-provide valuable information.&lt;/p&gt;
-
-&lt;p&gt;So, on to the list.  There were some used by many, some used by a
-few, some rarely used ones and a few mentioned but without anyone
-claiming to use them.  Notice the grouping is in reality quite random
-given the biased self selected set of participants.  First the ones
-used by many:&lt;/p&gt;
-
-&lt;ul&gt;
-
-&lt;li&gt;&lt;a href=&quot;https://whispersystems.org/&quot;&gt;Signal&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;Email w/&lt;a href=&quot;http://openpgp.org/&quot;&gt;OpenPGP&lt;/a&gt; (Enigmail, GPGSuite,etc)&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://www.whatsapp.com/&quot;&gt;Whatsapp&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;IRC w/&lt;a href=&quot;https://otr.cypherpunks.ca/&quot;&gt;OTR&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;XMPP w/&lt;a href=&quot;https://otr.cypherpunks.ca/&quot;&gt;OTR&lt;/a&gt;&lt;/li&gt;
-
-&lt;/ul&gt;
-
-&lt;p&gt;Then the ones used by a few.&lt;/p&gt;
-
-&lt;ul&gt;
-
-&lt;li&gt;&lt;a href=&quot;https://wiki.mumble.info/wiki/Main_Page&quot;&gt;Mumble&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;iMessage (included in iOS from Apple)&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://telegram.org/&quot;&gt;Telegram&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://jitsi.org/&quot;&gt;Jitsi&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://keybase.io/download&quot;&gt;Keybase file&lt;/a&gt;&lt;/li&gt;
-
-&lt;/ul&gt;
-
-&lt;p&gt;Then the ones used by even fewer people&lt;/p&gt;
-
-&lt;ul&gt;
-
-&lt;li&gt;&lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://bitmessage.org/&quot;&gt;Bitmessage&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://wire.com/&quot;&gt;Wire&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;VoIP w/&lt;a href=&quot;https://en.wikipedia.org/wiki/ZRTP&quot;&gt;ZRTP&lt;/a&gt; or controlled &lt;a href=&quot;https://en.wikipedia.org/wiki/Secure_Real-time_Transport_Protocol&quot;&gt;SRTP&lt;/a&gt; (e.g using &lt;a href=&quot;https://en.wikipedia.org/wiki/CSipSimple&quot;&gt;CSipSimple&lt;/a&gt;, &lt;a href=&quot;https://en.wikipedia.org/wiki/Linphone&quot;&gt;Linphone&lt;/a&gt;)&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://matrix.org/&quot;&gt;Matrix&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://kontalk.org/&quot;&gt;Kontalk&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://0bin.net/&quot;&gt;0bin&lt;/a&gt; (encrypted pastebin)&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://appear.in&quot;&gt;Appear.in&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://riot.im/&quot;&gt;riot&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://www.wickr.com/&quot;&gt;Wickr Me&lt;/a&gt;&lt;/li&gt;
-
-&lt;/ul&gt;
-
-&lt;p&gt;And finally the ones mentioned by not marked as used by
-anyone. This might be a mistake, perhaps the person adding the entry
-forgot to flag it as used?&lt;/p&gt;
-
-&lt;ul&gt;
-
-&lt;li&gt;Email w/Certificates &lt;a href=&quot;https://en.wikipedia.org/wiki/S/MIME&quot;&gt;S/MIME&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://www.crypho.com/&quot;&gt;Crypho&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://cryptpad.fr/&quot;&gt;CryptPad&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&quot;https://github.com/ricochet-im/ricochet&quot;&gt;ricochet&lt;/a&gt;&lt;/li&gt;
-
-&lt;/ul&gt;
-
-&lt;p&gt;Given the network effect it seem obvious to me that we as a society
-have been divided and conquered by those interested in keeping
-encrypted and secure communication away from the masses.  The
-finishing remarks &lt;a href=&quot;https://vimeo.com/97505679&quot;&gt;from Aral Balkan
-in his talk &quot;Free is a lie&quot;&lt;/a&gt; about the usability of free software
-really come into effect when you want to communicate in private with
-your friends and family.  We can not expect them to allow the
-usability of communication tool to block their ability to talk to
-their loved ones.&lt;/p&gt;
-
-&lt;p&gt;Note for example the option IRC w/OTR.  Most IRC clients do not
-have OTR support, so in most cases OTR would not be an option, even if
-you wanted to.  In my personal experience, about 1 in 20 I talk to
-have a IRC client with OTR.  For private communication to really be
-available, most people to talk to must have the option in their
-currently used client.  I can not simply ask my family to install an
-IRC client.  I need to guide them through a technical multi-step
-process of adding extensions to the client to get them going.  This is
-a non-starter for most.&lt;/p&gt;
-
-&lt;p&gt;I would like to be able to do video phone calls, audio phone calls,
-exchange instant messages and share files with my loved ones, without
-being forced to share with people I do not know.  I do not want to
-share the content of the conversations, and I do not want to share who
-I communicate with or the fact that I communicate with someone.
-Without all these factors in place, my private life is being more or
-less invaded.&lt;/p&gt;
-</description>
-       </item>
-       

         </channel>
 </rss>
         </channel>
 </rss>