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>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
                <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
                <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
                <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
system&lt;/a&gt; provide a practical and easy way to figure out which
packages support the hardware in a given machine.  The command line
tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
convenient way to list and install packages relevant for the current
hardware during system installation, both user space packages and
firmware packages. The GUI background daemon on the other hand provide
a pop-up proposing to install packages when a new dongle is inserted
while using the computer.  For example, if you plug in a smart card
reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
that package isn&#39;t already installed, and if you plug in a USB video
camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
cheese is currently missing.  This already work just fine.&lt;/p&gt;

&lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
package names.  When I started no such database existed in Debian, so
I made my own data set and included it with the isenkram package and
made isenkram fetch the latest version of this database from git using
http.  This way the isenkram users would get updated package proposals
as soon as I learned more about hardware related packages.&lt;/p&gt;

&lt;p&gt;The hardware is identified using modalias strings.  The modalias
design is from the Linux kernel where most hardware descriptors are
made available as a strings that can be matched using filename style
globbing.  It handle USB, PCI, DMI and a lot of other hardware related
identifiers.&lt;/p&gt;

&lt;p&gt;The downside to the Isenkram specific database is that there is no
information about relevant distribution / Debian version, making
isenkram propose obsolete packages too.  But along came AppStream, a
cross distribution mechanism to store and collect metadata about
software packages.  When I heard about the proposal, I contacted the
people involved and suggested to add a hardware matching rule using
modalias strings in the specification, to be able to use AppStream for
mapping hardware to packages.  This idea was accepted and AppStream is
now a great way for a package to announce the hardware it support in a
distribution neutral way.  I wrote
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html&quot;&gt;a
recipe on how to add such meta-information&lt;/a&gt; in a blog post last
December.  If you have a hardware related package in Debian, please
announce the relevant hardware IDs using AppStream.&lt;/p&gt;

&lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
RCX or NXT unit, announce this support using AppStream.  The effect is
that when you insert such LEGO robot controller into your Debian
machine, Isenkram will propose to install the packages needed to get
it working.  The intention is that this should allow the local user to
start programming his robot controller right away without having to
guess what packages to use or which permissions to fix.&lt;/p&gt;

&lt;p&gt;But when I sat down with my son the other day to program our NXT
unit using his Debian Stretch computer, I discovered something
annoying.  The local console user (ie my son) did not get access to
the USB device for programming the unit.  This used to work, but no
longer in Jessie and Stretch.  After some investigation and asking
around on #debian-devel, I discovered that this was because udev had
changed the mechanism used to grant access to local devices.  The
ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
no longer applied, because LDAP users no longer was added to the
plugdev group during login.  Michael Biebl told me that this method
was obsolete and the new method used ACLs instead.  This was good
news, as the plugdev mechanism is a mess when using a remote user
directory like LDAP.  Using ACLs would make sure a user lost device
access when she logged out, even if the user left behind a background
process which would retain the plugdev membership with the ConsoleKit
setup.  Armed with this knowledge I moved on to fix the access problem
for the LEGO Mindstorms related packages.&lt;/p&gt;

&lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;.  It can either be
applied directly for a device, or is applied in
/lib/udev/rules.d/70-uaccess.rules for classes of devices.  As the
LEGO Mindstorms udev rules did not have a class, I decided to add the
tag directly in the udev rules files included in the packages.  Here
is one example.  For the nqc C compiler for the RCX, the
&lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:

&lt;p&gt;&lt;pre&gt;
SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
    SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;I suspect all packages using plugdev in their /lib/udev/rules.d/
files should be changed to use this tag (either directly or indirectly
via &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;).  Perhaps a lintian check should be
created to detect this?&lt;/p&gt;

&lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
It is unclear to me if the uaccess tag is an internal implementation
detail like the udev-acl tag used by
&lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;.  If it is, I guess the
indirect method is the preferred way.  Michael
&lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
documentation from the systemd project&lt;/a&gt; and I hope it will make
this clearer.  For now I use the generic classes when they exist and
is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
directly if no such class exist.&lt;/p&gt;

&lt;p&gt;To learn more about the isenkram system, please check out
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;To help out making life for LEGO constructors in Debian easier,
please join us on our IRC channel
&lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
LEGO team&lt;/a&gt; in the Alioth project we created yesterday.  A mailing
list is not yet created, but we are working on it. :)&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>Aftenposten-redaktøren med lua i hånda</title>
                <link>http://people.skolelinux.org/pere/blog/Aftenposten_redakt_ren_med_lua_i_h_nda.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Aftenposten_redakt_ren_med_lua_i_h_nda.html</guid>
                <pubDate>Fri, 9 Sep 2016 11:30:00 +0200</pubDate>
                <description>&lt;p&gt;En av dagens nyheter er at Aftenpostens redaktør Espen Egil Hansen
bruker
&lt;a href=&quot;https://www.nrk.no/kultur/aftenposten-brukar-heile-forsida-pa-facebook-kritikk-1.13126918&quot;&gt;forsiden
av papiravisen på et åpent brev til Facebooks sjef Mark Zuckerberg om
Facebooks fjerning av bilder, tekster og sider de ikke liker&lt;/a&gt;.  Det
må være uvant for redaktøren i avisen Aftenposten å stå med lua i
handa og håpe på å bli hørt.  Spesielt siden Aftenposten har vært med
på å gi Facebook makten de nå demonstrerer at de har.  Ved å melde seg
inn i Facebook-samfunnet har de sagt ja til bruksvilkårene og inngått
en antagelig bindende avtale.  Kanskje de skulle lest og vurdert
vilkårene litt nærmere før de sa ja, i stedet for å klage over at
reglende de har valgt å akseptere blir fulgt?  Personlig synes jeg
vilkårene er uakseptable og det ville ikke falle meg inn å gå inn på
en avtale med slike vilkår.  I tillegg til uakseptable vilkår er det
mange andre grunner til å unngå Facebook.  Du kan finne en solid
gjennomgang av flere slike argumenter hos
&lt;a href=&quot;https://stallman.org/facebook.html&quot;&gt;Richard Stallmans side om
Facebook&lt;/a&gt;.

&lt;p&gt;Jeg håper flere norske redaktører på samme vis må stå med lua i
hånden inntil de forstår at de selv er med på å føre samfunnet på
ville veier ved å omfavne Facebook slik de gjør når de omtaler og
løfter frem saker fra Facebook, og tar i bruk Facebook som
distribusjonskanal for sine nyheter.  De bidrar til
overvåkningssamfunnet og raderer ut lesernes privatsfære når de lenker
til Facebook på sine sider, og låser seg selv inne i en omgivelse der
det er Facebook, og ikke redaktøren, som sitter med makta.&lt;/p&gt;

&lt;p&gt;Men det vil nok ta tid, i et Norge der de fleste nettredaktører
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Snurpenot_overv_kning_av_sensitiv_personinformasjon.html&quot;&gt;deler
sine leseres personopplysinger med utenlands etterretning&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For øvrig burde varsleren Edward Snowden få politisk asyl i
Norge.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>E-tjenesten ber om innsyn i eposten til partiene på Stortinget</title>
                <link>http://people.skolelinux.org/pere/blog/E_tjenesten_ber_om_innsyn_i_eposten_til_partiene_p__Stortinget.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/E_tjenesten_ber_om_innsyn_i_eposten_til_partiene_p__Stortinget.html</guid>
                <pubDate>Tue, 6 Sep 2016 23:00:00 +0200</pubDate>
                <description>&lt;p&gt;I helga kom det et hårreisende forslag fra Lysne II-utvalget satt
ned av Forsvarsdepartementet.  Lysne II-utvalget var bedt om å vurdere
ønskelista til Forsvarets etterretningstjeneste (e-tjenesten), og har
kommet med
&lt;a href=&quot;http://www.aftenposten.no/norge/Utvalg-sier-ja-til-at-E-tjenesten-far-overvake-innholdet-i-all-internett--og-telefontrafikk-som-krysser-riksgrensen-603232b.html&quot;&gt;forslag
om at e-tjenesten skal få lov til a avlytte all Internett-trafikk&lt;/a&gt;
som passerer Norges grenser.  Få er klar over at dette innebærer at
e-tjenesten får tilgang til epost sendt til de fleste politiske
partiene på Stortinget.  Regjeringspartiet Høyre (@hoyre.no),
støttepartiene Venstre (@venstre.no) og Kristelig Folkeparti (@krf.no)
samt Sosialistisk Ventreparti (@sv.no) og Miljøpartiet de grønne
(@mdg.no) har nemlig alle valgt å ta imot eposten sin via utenlandske
tjenester.  Det betyr at hvis noen sender epost til noen med en slik
adresse vil innholdet i eposten, om dette forslaget blir vedtatt, gjøres
tilgjengelig for e-tjenesten.  Venstre, Sosialistisk Ventreparti og
Miljøpartiet De Grønne har valgt å motta sin epost hos Google,
Kristelig Folkeparti har valgt å motta sin epost hos Microsoft, og
Høyre har valgt å motta sin epost hos Comendo med mottak i Danmark og
Irland.  Kun Arbeiderpartiet og Fremskrittspartiet har valgt å motta
eposten sin i Norge, hos henholdsvis Intility AS og Telecomputing
AS.&lt;/p&gt;

&lt;p&gt;Konsekvensen er at epost inn og ut av de politiske organisasjonene,
til og fra partimedlemmer og partiets tillitsvalgte vil gjøres
tilgjengelig for e-tjenesten for analyse og sortering.  Jeg mistenker
at kunnskapen som slik blir tilgjengelig vil være nyttig hvis en
ønsker å vite hvilke argumenter som treffer publikum når en ønsker å
påvirke Stortingets representanter.&lt;/p

&lt;p&gt;Ved hjelp av MX-oppslag i DNS for epost-domene, tilhørende
whois-oppslag av IP-adressene og traceroute for å se hvorvidt
trafikken går via utlandet kan enhver få bekreftet at epost sendt til
de omtalte partiene vil gjøres tilgjengelig for forsvarets
etterretningstjeneste hvis forslaget blir vedtatt.  En kan også bruke
den kjekke nett-tjenesten &lt;a href=&quot;http://ipinfo.io/&quot;&gt;ipinfo.io&lt;/a&gt;
for å få en ide om hvor i verden en IP-adresse hører til.&lt;/p&gt;

&lt;p&gt;På den positive siden vil forslaget gjøre at enda flere blir
motivert til å ta grep for å bruke
&lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt; og krypterte
kommunikasjonsløsninger for å kommunisere med sine kjære, for å sikre
at privatsfæren vernes.  Selv bruker jeg blant annet
&lt;a href=&quot;https://www.freedomboxfoundation.org/&quot;&gt;FreedomBox&lt;/a&gt; og
&lt;a href=&quot;https://whispersystems.org/&quot;&gt;Signal&lt;/a&gt; til slikt.  Ingen av
dem er optimale, men de fungerer ganske bra allerede og øker kostnaden
for dem som ønsker å invadere mitt privatliv.&lt;/p&gt;

&lt;p&gt;For øvrig burde varsleren Edward Snowden få politisk asyl i
Norge.&lt;/p&gt;

&lt;!--

venstre.no
  venstre.no mail is handled by 10 aspmx.l.google.com.
  venstre.no mail is handled by 20 alt1.aspmx.l.google.com.
  venstre.no mail is handled by 20 alt2.aspmx.l.google.com.
  venstre.no mail is handled by 30 aspmx2.googlemail.com.
  venstre.no mail is handled by 30 aspmx3.googlemail.com.

traceroute to aspmx.l.google.com (173.194.222.27), 30 hops max, 60 byte packets
 1  uio-gw10.uio.no (129.240.6.1)  0.411 ms  0.438 ms  0.536 ms
 2  uio-gw8.uio.no (129.240.24.229)  0.375 ms  0.452 ms  0.548 ms
 3  oslo-gw1.uninett.no (128.39.65.17)  1.940 ms  1.950 ms  1.942 ms
 4  se-tug.nordu.net (109.105.102.108)  6.910 ms  6.949 ms  7.283 ms
 5  google-gw.nordu.net (109.105.98.6)  6.975 ms  6.967 ms  6.958 ms
 6  209.85.250.192 (209.85.250.192)  7.337 ms  7.286 ms  10.890 ms
 7  209.85.254.13 (209.85.254.13)  7.394 ms 209.85.254.31 (209.85.254.31)  7.586 ms 209.85.254.33 (209.85.254.33)  7.570 ms
 8  209.85.251.255 (209.85.251.255)  15.686 ms 209.85.249.229 (209.85.249.229)  16.118 ms 209.85.251.255 (209.85.251.255)  16.073 ms
 9  74.125.37.255 (74.125.37.255)  16.794 ms 216.239.40.248 (216.239.40.248)  16.113 ms 74.125.37.44 (74.125.37.44)  16.764 ms
10  * * *

mdg.no
  mdg.no mail is handled by 1 aspmx.l.google.com.
  mdg.no mail is handled by 5 alt2.aspmx.l.google.com.
  mdg.no mail is handled by 5 alt1.aspmx.l.google.com.
  mdg.no mail is handled by 10 aspmx2.googlemail.com.
  mdg.no mail is handled by 10 aspmx3.googlemail.com.
sv.no
  sv.no mail is handled by 1 aspmx.l.google.com.
  sv.no mail is handled by 5 alt1.aspmx.l.google.com.
  sv.no mail is handled by 5 alt2.aspmx.l.google.com.
  sv.no mail is handled by 10 aspmx3.googlemail.com.
  sv.no mail is handled by 10 aspmx2.googlemail.com.
hoyre.no
  hoyre.no mail is handled by 10 hoyre-no.mx1.comendosystems.com.
  hoyre.no mail is handled by 20 hoyre-no.mx2.comendosystems.net.

traceroute to hoyre-no.mx1.comendosystems.com (89.104.206.4), 30 hops max, 60 byte packets
 1  uio-gw10.uio.no (129.240.6.1)  0.450 ms  0.510 ms  0.591 ms
 2  uio-gw8.uio.no (129.240.24.229)  0.383 ms  0.508 ms  0.596 ms
 3  oslo-gw1.uninett.no (128.39.65.17)  0.311 ms  0.315 ms  0.300 ms
 4  se-tug.nordu.net (109.105.102.108)  6.837 ms  6.842 ms  6.834 ms
 5  dk-uni.nordu.net (109.105.97.10)  26.073 ms  26.085 ms  26.076 ms
 6  dix.1000m.soeborg.ip.comendo.dk (192.38.7.22)  15.372 ms  15.046 ms  15.123 ms
 7  89.104.192.65 (89.104.192.65)  15.875 ms  15.990 ms  16.239 ms
 8  89.104.192.179 (89.104.192.179)  15.676 ms  15.674 ms  15.664 ms
 9  03dm-com.mx1.staysecuregroup.com (89.104.206.4)  15.637 ms * *

krf.no
  krf.no mail is handled by 10 krf-no.mail.protection.outlook.com.

traceroute to krf-no.mail.protection.outlook.com (213.199.154.42), 30 hops max, 60 byte packets
 1  uio-gw10.uio.no (129.240.6.1)  0.401 ms  0.438 ms  0.536 ms
 2  uio-gw8.uio.no (129.240.24.229)  11.076 ms  11.120 ms  11.204 ms
 3  oslo-gw1.uninett.no (128.39.65.17)  0.232 ms  0.234 ms  0.271 ms
 4  se-tug.nordu.net (109.105.102.108)  6.811 ms  6.820 ms  6.815 ms
 5  netnod-ix-ge-a-sth-4470.microsoft.com (195.245.240.181)  7.074 ms  7.013 ms  7.061 ms
 6  ae1-0.sto-96cbe-1b.ntwk.msn.net (104.44.225.161)  7.227 ms  7.362 ms  7.293 ms
 7  be-8-0.ibr01.ams.ntwk.msn.net (104.44.5.7)  41.993 ms  43.334 ms  41.939 ms
 8  be-1-0.ibr02.ams.ntwk.msn.net (104.44.4.214)  43.153 ms  43.507 ms  43.404 ms
 9  ae3-0.fra-96cbe-1b.ntwk.msn.net (104.44.5.17)  29.897 ms  29.831 ms  29.794 ms
10  ae10-0.vie-96cbe-1a.ntwk.msn.net (198.206.164.1)  42.309 ms  42.130 ms  41.808 ms
11  * ae8-0.vie-96cbe-1b.ntwk.msn.net (104.44.227.29)  41.425 ms *
12  * * *

arbeiderpartiet.no
  arbeiderpartiet.no mail is handled by 10 mail.intility.com.
  arbeiderpartiet.no mail is handled by 20 mail2.intility.com.

traceroute to mail.intility.com (188.95.245.87), 30 hops max, 60 byte packets
 1  uio-gw10.uio.no (129.240.6.1)  0.486 ms  0.508 ms  0.649 ms
 2  uio-gw8.uio.no (129.240.24.229)  0.416 ms  0.508 ms  0.620 ms
 3  oslo-gw1.uninett.no (128.39.65.17)  0.276 ms  0.278 ms  0.275 ms
 4  te3-1-2.br1.fn3.as2116.net (193.156.90.3)  0.374 ms  0.371 ms  0.416 ms
 5  he16-1-1.cr1.san110.as2116.net (195.0.244.234)  3.132 ms he16-1-1.cr2.oslosda310.as2116.net (195.0.244.48)  10.079 ms he16-1-1.cr1.san110.as2116.net (195.0.244.234)  3.353 ms
 6  te1-2-0.ar2.ulv89.as2116.net (195.0.243.194)  0.569 ms te5-0-0.ar2.ulv89.as2116.net (195.0.243.192)  0.661 ms  0.653 ms
 7  cD2EC45C1.static.as2116.net (193.69.236.210)  0.654 ms  0.615 ms  0.590 ms
 8  185.7.132.38 (185.7.132.38)  1.661 ms  1.808 ms  1.695 ms
 9  185.7.132.100 (185.7.132.100)  1.793 ms  1.943 ms  1.546 ms
10  * * *

frp.no
  frp.no mail is handled by 10 mx03.telecomputing.no.
  frp.no mail is handled by 20 mx01.telecomputing.no.

traceroute to mx03.telecomputing.no (95.128.105.102), 30 hops max, 60 byte packets
 1  uio-gw10.uio.no (129.240.6.1)  0.378 ms  0.402 ms  0.479 ms
 2  uio-gw8.uio.no (129.240.24.229)  0.361 ms  0.458 ms  0.548 ms
 3  oslo-gw1.uninett.no (128.39.65.17)  0.361 ms  0.352 ms  0.336 ms
 4  xe-2-2-0-0.san-peer2.osl.no.ip.tdc.net (193.156.90.16)  0.375 ms  0.366 ms  0.346 ms
 5  xe-2-0-2-0.ost-pe1.osl.no.ip.tdc.net (85.19.121.97)  0.780 ms xe-2-0-0-0.ost-pe1.osl.no.ip.tdc.net (85.19.121.101)  0.713 ms xe-2-0-2-0.ost-pe1.osl.no.ip.tdc.net (85.19.121.97)  0.759 ms
 6  cpe.xe-0-2-0-100.ost-pe1.osl.no.customer.tdc.net (85.19.26.46)  0.837 ms  0.755 ms  0.759 ms
 7  95.128.105.3 (95.128.105.3)  1.050 ms  1.288 ms  1.182 ms
 8  mx03.telecomputing.no (95.128.105.102)  0.717 ms  0.703 ms  0.692 ms

--&gt;
</description>
        </item>
        
        <item>
                <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
                <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</guid>
                <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
                <description>&lt;p&gt;In April we
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html&quot;&gt;started
to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
how to set up and administrate a Debian system.  Today I am happy to
report that the first draft is now publicly available.  You can find
it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages).  The first
eight chapters have a first draft translation, and we are working on
proofreading the content.  If you want to help out, please start
contributing using
&lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
hosted weblate project page&lt;/a&gt;, and get in touch using
&lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
translators mailing list&lt;/a&gt;.  Please also check out
&lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
contributors&lt;/a&gt;.  A good way to contribute is to proofread the text
and update weblate if you find errors.&lt;/p&gt;

&lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
electronic form.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
                <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
                <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
                <description>&lt;p&gt;This summer, I read a great article
&quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
how to profile multi-threaded programs.  It presented a system for
profiling software by running experiences in the running program,
testing how run time performance is affected by &quot;speeding up&quot; parts of
the code to various degrees compared to a normal run.  It does this by
slowing down parallel threads while the &quot;faster up&quot; code is running
and measure how this affect processing time.  The processing time is
measured using probes inserted into the code, either using progress
counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END).  It
can also measure unmodified code by measuring complete the program
runtime and running the program several times instead.&lt;/p&gt;

&lt;p&gt;The project and presentation was so inspiring that I would like to
get the system into Debian.  I
&lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
system ready for Debian by sending patches.  The build process need to
be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
to include the JavaScript web page used to visualize the collected
profiling information included in the source package.
But I expect that should work out fairly soon.&lt;/p&gt;

&lt;p&gt;The way the system work is fairly simple.  To run an coz experiment
on a binary with debug symbols available, start the program like this:

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
coz run --- program-to-run
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;This will create a text file profile.coz with the instrumentation
information.  To show what part of the code affect the performance
most, use a web browser and either point it to
&lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
or use the copy from git (in the gh-pages branch).  Check out this web
site to have a look at several example profiling runs and get an idea what the end result from the profile runs look like.  To make the
profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
code, rebuild and run the profiler.  This allow coz to do more
targeted experiments.&lt;/p&gt;

&lt;p&gt;A video published by ACM
&lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
Coz profiler&lt;/a&gt; is available from Youtube.  There is also a paper
from the 25th Symposium on Operating Systems Principles available
titled
&lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
for Coz is available from github.  It will only build with clang
because it uses a
&lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
&lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;

&lt;p&gt;Please get in touch if you, like me, would like to see this piece
of software in Debian.  I would very much like some help with the
packaging effort, as I lack the in depth knowledge on how to package
C++ libraries.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Sales number for the Free Culture translation, first half of 2016</title>
                <link>http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html</guid>
                <pubDate>Fri, 5 Aug 2016 22:45:00 +0200</pubDate>
                <description>&lt;p&gt;As my regular readers probably remember, the last year I published
a French and Norwegian translation of the classic
&lt;a href=&quot;http://www.free-culture.cc/&quot;&gt;Free Culture book&lt;/a&gt; by the
founder of the Creative Commons movement, Lawrence Lessig.  A bit less
known is the fact that due to the way I created the translations,
using docbook and po4a, I also recreated the English original.  And
because I already had created a new the PDF edition, I published it
too.  The revenue from the books are sent to the Creative Commons
Corporation.  In other words, I do not earn any money from this
project, I just earn the warm fuzzy feeling that the text is available
for a wider audience and more people can learn why the Creative
Commons is needed.&lt;/p&gt;

&lt;p&gt;Today, just for fun, I had a look at the sales number over at
Lulu.com, which take care of payment, printing and shipping.  Much to
my surprise, the English edition is selling better than both the
French and Norwegian edition, despite the fact that it has been
available in English since it was first published.  In total, 24 paper
books was sold for USD $19.99 between 2016-01-01 and 2016-07-31:&lt;/p&gt;

&lt;table border=&quot;0&quot;&gt;
&lt;tr&gt;&lt;th&gt;Title / language&lt;/th&gt;&lt;th&gt;Quantity&lt;/th&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;Culture Libre / French&lt;/a&gt;&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Fri kultur / Norwegian&lt;/a&gt;&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;Free Culture / English&lt;/a&gt;&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;14&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;

&lt;p&gt;The books are available both from Lulu.com and from large book
stores like Amazon and Barnes&amp;Noble.  Most revenue, around $10 per
book, is sent to the Creative Commons project when the book is sold
directly by Lulu.com.  The other channels give less revenue.  The
summary from Lulu tell me 10 books was sold via the Amazon channel, 10
via Ingram (what is this?) and 4 directly by Lulu.  And Lulu.com tells
me that the revenue sent so far this year is USD $101.42.  No idea
what kind of sales numbers to expect, so I do not know if that is a
good amount of sales for a 10 year old book or not.  But it make me
happy that the buyers find the book, and I hope they enjoy reading it
as much as I did.&lt;/p&gt;

&lt;p&gt;The ebook edition is available for free from
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;Github&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you would like to translate and publish the book in your native
language, I would be happy to help make it happen.  Please get in
touch.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Vitenskapen tar som vanlig feil igjen - relativt feil</title>
                <link>http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html</guid>
                <pubDate>Mon, 1 Aug 2016 16:00:00 +0200</pubDate>
                <description>&lt;p&gt;For mange år siden leste jeg en klassisk tekst som gjorde såpass
inntrykk på meg at jeg husker den fortsatt, flere år senere, og bruker
argumentene fra den stadig vekk.  Teksten var «The Relativity of
Wrong» som Isaac Asimov publiserte i Skeptical Inquirer i 1989.  Den
gir litt perspektiv rundt formidlingen av vitenskapelige resultater.
Jeg har hatt lyst til å kunne dele den også med folk som ikke
behersker engelsk så godt, som barn og noen av mine eldre slektninger,
og har savnet å ha den tilgjengelig på norsk.  For to uker siden tok
jeg meg sammen og kontaktet Asbjørn Dyrendal i foreningen Skepsis om
de var interessert i å publisere en norsk utgave på bloggen sin, og da
han var positiv tok jeg kontakt med Skeptical Inquirer og spurte om
det var greit for dem.  I løpet av noen dager fikk vi tilbakemelding
fra Barry Karr hos The Skeptical Inquirer som hadde sjekket og fått OK
fra Robyn Asimov som representerte arvingene i Asmiov-familien og gikk
igang med oversettingen.&lt;/p&gt;

&lt;p&gt;Resultatet, &lt;a href=&quot;http://www.skepsis.no/?p=1617&quot;&gt;«Relativt
feil»&lt;/a&gt;, ble publisert på skepsis-bloggen for noen minutter siden.
Jeg anbefaler deg på det varmeste å lese denne teksten og dele den med
dine venner.&lt;/p&gt;

&lt;p&gt;For å håndtere oversettelsen og sikre at original og oversettelse
var i sync brukte vi git, po4a, GNU make og Transifex.  Det hele
fungerte utmerket og gjorde det enkelt å dele tekstene og jobbe sammen
om finpuss på formuleringene.  Hadde hosted.weblate.org latt meg
opprette nye prosjekter selv i stedet for å måtte kontakte
administratoren der, så hadde jeg brukt weblate i stedet.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Techno TV broadcasting live across Norway and the Internet (#debconf16, #nuug) on @frikanalen</title>
                <link>http://people.skolelinux.org/pere/blog/Techno_TV_broadcasting_live_across_Norway_and_the_Internet___debconf16___nuug__on__frikanalen.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Techno_TV_broadcasting_live_across_Norway_and_the_Internet___debconf16___nuug__on__frikanalen.html</guid>
                <pubDate>Mon, 1 Aug 2016 10:30:00 +0200</pubDate>
                <description>&lt;p&gt;Did you know there is a TV channel broadcasting talks from DebConf
16 across an entire country?  Or that there is a TV channel
broadcasting talks by or about
&lt;a href=&quot;http://beta.frikanalen.no/video/625529/&quot;&gt;Linus Torvalds&lt;/a&gt;,
&lt;a href=&quot;http://beta.frikanalen.no/video/625599/&quot;&gt;Tor&lt;/a&gt;,
&lt;a href=&quot;http://beta.frikanalen.no/video/624019/&quot;&gt;OpenID&lt;/A&gt;,
&lt;a href=&quot;http://beta.frikanalen.no/video/625624/&quot;&gt;Common Lisp&lt;/a&gt;,
&lt;a href=&quot;http://beta.frikanalen.no/video/625446/&quot;&gt;Civic Tech&lt;/a&gt;,
&lt;a href=&quot;http://beta.frikanalen.no/video/625090/&quot;&gt;EFF founder John Barlow&lt;/a&gt;,
&lt;a href=&quot;http://beta.frikanalen.no/video/625432/&quot;&gt;how to make 3D
printer electronics&lt;/a&gt; and many more fascinating topics?  It works
using only free software (all of it
&lt;a href=&quot;http://github.com/Frikanalen&quot;&gt;available from Github&lt;/a&gt;), and
is administrated using a web browser and a web API.&lt;/p&gt;

&lt;p&gt;The TV channel is the Norwegian open channel
&lt;a href=&quot;http://www.frikanalen.no/&quot;&gt;Frikanalen&lt;/a&gt;, and I am involved
via &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG member association&lt;/a&gt; in
running and developing the software for the channel.  The channel is
organised as a member organisation where its members can upload and
broadcast what they want (think of it as Youtube for national
broadcasting television).  Individuals can broadcast too.  The time
slots are handled on a first come, first serve basis.  Because the
channel have almost no viewers and very few active members, we can
experiment with TV technology without too much flack when we make
mistakes.  And thanks to the few active members, most of the slots on
the schedule are free.  I see this as an opportunity to spread
knowledge about technology and free software, and have a script I run
regularly to fill up all the open slots the next few days with
technology related video.  The end result is a channel I like to
describe as Techno TV - filled with interesting talks and
presentations.&lt;/p&gt;

&lt;p&gt;It is available on channel 50 on the Norwegian national digital TV
network (RiksTV).  It is also available as a multicast stream on
Uninett.  And finally, it is available as
&lt;a href=&quot;http://beta.frikanalen.no/&quot;&gt;a WebM unicast stream&lt;/a&gt; from
Frikanalen and NUUG.  Check it out. :)&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
                <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
                <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
                <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
to be a slight challenge.  Here is the recipe if I ever need to do it
again.  It all started by me wanting to try the recipe to set up
&lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
hardened Android installation&lt;/a&gt; from the Tor project blog on a
device I had access to.  It is a old mobile phone with a broken
microphone The initial idea had been to just
&lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
until a few days ago.&lt;/p&gt;

&lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
loader (press volume down and power at the same time), (2) select
&#39;fastboot&#39; before (3) connecting the device via USB to a Linux
machine, (4) request the device identifier token by running &#39;fastboot
oem get_identifier_token&#39;, (5) request the device unlocking key using
the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;

&lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
or newer, and the device I was working on had 2.00.0027.  This
apparently can be easily fixed by downloading a Windows program and
running it on your Windows machine, if you accept the terms Microsoft
require you to accept to use Windows - which I do not.  So I had to
come up with a different approach.  I got a lot of help from AndyCap
on #nuug, and would not have been able to get this working without
him.&lt;/p&gt;

&lt;p&gt;First I needed to extract the hboot firmware from
&lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
project named unruu&lt;/a&gt; using libunshield.  The unshield tool did not
recognise the file format, but unruu worked and extracted rom.zip,
containing the new hboot firmware and a text file describing which
devices it would work for.&lt;/p&gt;

&lt;p&gt;Next, I needed to get the new firmware into the device.  For this I
followed some instructions
&lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
machine with Debian testing:&lt;/p&gt;

&lt;p&gt;&lt;pre&gt;
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;The flash command apparently need to be done twice to take effect,
as the first is just preparations and the second one do the flashing.
The adb command is just to get to the boot loader menu, so turning the
device on while holding volume down and the power button should work
too.&lt;/p&gt;

&lt;p&gt;With the new hboot version in place I could start following the
instructions on the HTC developer web site.  I got the device token
like this:&lt;/p&gt;

&lt;p&gt;&lt;pre&gt;
fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
&lt;/pre&gt;

&lt;p&gt;And once I got the unlock code via email, I could use it like
this:&lt;/p&gt;

&lt;p&gt;&lt;pre&gt;
fastboot flash unlocktoken Unlock_code.bin
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;And with that final step in place, the phone was unlocked and I
could start stuffing the software of my own choosing into the device.
So far I only inserted a replacement recovery image to wipe the phone
before I start.  We will see what happen next.  Perhaps I should
install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
                <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</guid>
                <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
                <description>&lt;p&gt;For a while now, I have wanted to test
&lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
said to provide end to end encrypted communication and several of my
friends and family are already using it.  As I by choice do not own a
mobile phone, this proved to be harder than expected.  And I wanted to
have the source of the client and know that it was the code used on my
machine.  But yesterday I managed to get it working.  I used the
Github source, compared it to the source in
&lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
patches to use the production Signal servers, started the app and
asked for the hidden &quot;register without a smart phone&quot; form.  Here is
the recipe how I did it.&lt;/p&gt;

&lt;p&gt;First, I fetched the Signal desktop source from Github, using

&lt;pre&gt;
git clone https://github.com/WhisperSystems/Signal-Desktop.git
&lt;/pre&gt;

&lt;p&gt;Next, I patched the source to use the production servers, to be
able to talk to other Signal users:&lt;/p&gt;

&lt;pre&gt;
cat &amp;lt;&amp;lt;EOF | patch -p0
diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
--- ./js/background.js  2016-06-29 13:43:15.630344628 +0200
+++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js    2016-06-29 14:06:29.530300934 +0200
@@ -47,8 +47,8 @@
         });
     });
 
-    var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
-    var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
+    var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
+    var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
     var messageReceiver;
     window.getSocketStatus = function() {
         if (messageReceiver) {
diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
--- ./js/expire.js      2016-06-29 13:43:15.630344628 +0200
+++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
@@ -1,6 +1,6 @@
 ;(function() {
     &#39;use strict&#39;;
-    var BUILD_EXPIRATION = 0;
+    var BUILD_EXPIRATION = 1474492690000;
 
     window.extension = window.extension || {};
 
EOF
&lt;/pre&gt;

&lt;p&gt;The first part is changing the servers, and the second is updating
an expiration timestamp.  This timestamp need to be updated regularly.
It is set 90 days in the future by the build process (Gruntfile.js).
The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;

&lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
script to launch Signal in Chromium.&lt;/p&gt;

&lt;pre&gt;
#!/bin/sh
cd $(dirname $0)
mkdir -p userdata
exec chromium \
  --proxy-server=&quot;socks://localhost:9050&quot; \
  --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
&lt;/pre&gt;

&lt;p&gt; The script start the app and configure Chromium to use the Tor
SOCKS5 proxy to make sure those controlling the Signal servers (today
Amazon and Whisper Systems) as well as those listening on the lines
will have a harder time location my laptop based on the Signal
connections if they use source IP address.&lt;/p&gt;

&lt;p&gt;When the script starts, one need to follow the instructions under
&quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
repository.  I right clicked on the Signal window to get up the
Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
&#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
registration form.  Then I entered by land line phone number and
pressed &#39;Call&#39;.  5 seconds later the phone rang and a robot voice
repeated the verification code three times.  After entering the number
into the verification code field in the form, I could start using
Signal from my laptop.

&lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
whom and thus who know who to those controlling the central server,
but such leakage is hard to avoid with a centrally controlled server
setup.  It is something to keep in mind when using Signal - the
content of your chats are harder to intercept, but the meta data
exposing your contact network is available to people you do not know.
So better than many options, but not great.  And sadly the usage is
connected to my land line, thus allowing those controlling the server
to associate it to my home and person.  I would prefer it if only
those I knew could tell who I was on Signal.  There are options
avoiding such information leakage, but most of my friends are not
using them, so I am stuck with Signal for now.&lt;/p&gt;
</description>
        </item>
        
        </channel>
</rss>