Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 1196544ba249ccc69cb0f54156083a64e25f6193..8cb2c5d371237adbf5c7500b2e3054512eac784c 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,36 @@
                 <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>Artikkel om Noark 5 Tjenestegrensesnitt og Nikita i Arkivråd nummer 3 for 2019</title>
+               <link>http://people.skolelinux.org/pere/blog/Artikkel_om_Noark_5_Tjenestegrensesnitt_og_Nikita_i_Arkivr_d_nummer_3_for_2019.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Artikkel_om_Noark_5_Tjenestegrensesnitt_og_Nikita_i_Arkivr_d_nummer_3_for_2019.html</guid>
+                <pubDate>Thu, 26 Dec 2019 08:00:00 +0100</pubDate>
+               <description>&lt;p&gt;Like før julaften ble en artikkel jeg har skrevet om vedlikehold av
+&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard&quot;&gt;Noark
+5 Tjenestegrensesnitt&lt;/a&gt; og Nikita publisert i &lt;a
+href=&quot;https://www.arkivrad.no/arkivrad&quot;&gt;tidsskriftet Arkivråd&lt;/a&gt;.
+Det er basert på
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/_pen_og_gjennomsiktig_vedlikehold_av_spesifikasjonen_for_Noark_5_Tjenestegrensesnitt.html&quot;&gt;min bloggpost
+om samme tema&lt;/a&gt; som ble publisert 2019-03-11.  Jeg oppdaget nettopp
+at nettsiden til tidsskriftet Arkivråd er oppdatert med siste utgave,
+og artikkelen dermed er tilgjengelig for alle. Du finner den i
+&lt;a href=&quot;https://www.arkivrad.no/sites/arkivrad/files/arkivrad_03_2019_nett.pdf&quot;&gt;PDF-en
+til nummer 2019/3 på side 30-33&lt;/a&gt;.  Jeg håper leserne av
+tidsskriftet får lyst til å sjekke ut tjenestegrensesnittet og at
+artikkelen vil gjøre det enklere for flere å bidra til en enda bedre,
+klarere og mer entydig API-spesifikasjon.  Det kan gjøre at
+&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;arkivsystemet
+Nikita&lt;/a&gt; kan bli enda bedre når spesifikasjonen forbedres.&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>Meningsløst, men for hvem...</title>
                <link>http://people.skolelinux.org/pere/blog/Meningsl_st__men_for_hvem___.html</link>
        <item>
                <title>Meningsløst, men for hvem...</title>
                <link>http://people.skolelinux.org/pere/blog/Meningsl_st__men_for_hvem___.html</link>


@@ -690,73 +720,5 @@ til min adresse
 </description>
        </item>
        
 </description>
        </item>
        

-       <item>
-               <title>Jami/Ring, finally functioning peer to peer communication client</title>
-               <link>http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
-                <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
-               <description>&lt;p&gt;Some years ago, in 2016, I
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html&quot;&gt;wrote
-for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
-It would provide messaging without any central server coordinating the
-system and without requiring all users to register a phone number or
-own a mobile phone.  Back then, I could not get it to work, and put it
-aside until it had seen more development.  A few days ago I decided to
-give it another try, and am happy to report that this time I am able
-to not only send and receive messages, but also place audio and video
-calls.  But only if UDP is not blocked into your network.&lt;/p&gt;
-
-&lt;p&gt;The Ring system changed name earlier this year to
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;.  I
-tried doing web search for &#39;ring&#39; when I discovered it for the first
-time, and can only applaud this change as it is impossible to find
-something called Ring among the noise of other uses of that word.  Now
-you can search for &#39;jami&#39; and this client and
-&lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
-least on duckduckgo.&lt;/p&gt;
-
-&lt;p&gt;Jami will by default encrypt messages as well as audio and video
-calls, and try to send them directly between the communicating parties
-if possible.  If this proves impossible (for example if both ends are
-behind NAT), it will use a central SIP TURN server maintained by the
-Jami project.  Jami can also be a normal SIP client.  If the SIP
-server is unencrypted, the audio and video calls will also be
-unencrypted.  This is as far as I know the only case where Jami will
-do anything without encryption.&lt;/p&gt;
-
-&lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
-Android, iOS, and Android TV.  It is included in Debian already.  Jami
-also work for those using F-Droid without any Google connections,
-while Signal do not.
-&lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
-protocol&lt;/a&gt; is described in the Ring project wiki.  The system uses a
-distributed hash table (DHT) system (similar to BitTorrent) running
-over UDP.  On one of the networks I use, I discovered Jami failed to
-work.  I tracked this down to the fact that incoming UDP packages
-going to ports 1-49999 were blocked, and the DHT would pick a random
-port and end up in the low range most of the time.  After talking to
-the developers, I solved this by enabling the dhtproxy in the
-settings, thus using TCP to talk to a central DHT proxy instead of
-
-peering directly with others.  I&#39;ve been told the developers are
-working on allowing DHT to use TCP to avoid this problem.  I also ran
-into a problem when trying to talk to the version of Ring included in
-Debian Stable (Stretch).  Apparently the protocol changed between
-beta2 and the current version, making these clients incompatible.
-Hopefully the protocol will not be made incompatible in the
-future.&lt;/p&gt;
-
-&lt;p&gt;It is worth noting that while looking at Jami and its features, I
-came across another communication platform I have not tested yet.  The
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
-and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;.  It might
-become the topic of a future blog post.&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>
         </channel>
 </rss>