<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
<item>
- <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
- <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
- <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
- <description><p>A while back, I was asked by a friend how to stream the desktop to
-my projector connected to Kodi. I sadly had to admit that I had no
-idea, as it was a task I never had tried. Since then, I have been
-looking for a way to do so, preferable without much extra software to
-install on either side. Today I found a way that seem to kind of
-work. Not great, but it is a start.</p>
-
-<p>I had a look at several approaches, for example
-<a href="https://github.com/mfoetsch/dlna_live_streaming">using uPnP
-DLNA as described in 2011</a>, but it required a uPnP server, fuse and
-local storage enough to store the stream locally. This is not going
-to work well for me, lacking enough free space, and it would
-impossible for my friend to get working.</p>
-
-<p>Next, it occurred to me that perhaps I could use VLC to create a
-video stream that Kodi could play. Preferably using
-broadcast/multicast, to avoid having to change any setup on the Kodi
-side when starting such stream. Unfortunately, the only recipe I
-could find using multicast used the rtp protocol, and this protocol
-seem to not be supported by Kodi.</p>
-
-<p>On the other hand, the rtsp protocol is working! Unfortunately I
-have to specify the IP address of the streaming machine in both the
-sending command and the file on the Kodi server. But it is showing my
-desktop, and thus allow us to have a shared look on the big screen at
-the programs I work on.</p>
-
-<p>I did not spend much time investigating codeces. I combined the
-rtp and rtsp recipes from
-<a href="https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/">the
-VLC Streaming HowTo/Command Line Examples</a>, and was able to get
-this working on the desktop/streaming end.</p>
-
-<blockquote><pre>
-vlc screen:// --sout \
- '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{dst=projector.local,port=1234,sdp=rtsp://192.168.11.4:8080/test.sdp}'
-</pre></blockquote>
-
-<p>I ssh-ed into my Kodi box and created a file like this with the
-same IP address:</p>
-
-<blockquote><pre>
-echo rtsp://192.168.11.4:8080/test.sdp \
- > /storage/videos/screenstream.m3u
-</pre></blockquote>
-
-<p>Note the 192.168.11.4 IP address is my desktops IP address. As far
-as I can tell the IP must be hardcoded for this to work. In other
-words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
-recipe. To get started, locate the file in Kodi and select the m3u
-file while the VLC stream is running. The desktop then show up in my
-big screen. :)</p>
-
-<p>When using the same technique to stream a video file with audio,
-the audio quality is really bad. No idea if the problem is package
-loss or bad parameters for the transcode. I do not know VLC nor Kodi
-enough to tell.</p>
-
-<p><strong>Update 2018-07-12</strong>: Johannes Schauer send me a few
-succestions and reminded me about an important step. The "screen:"
-input source is only available once the vlc-plugin-access-extra
-package is installed on Debian. Without it, you will see this error
-message: "VLC is unable to open the MRL 'screen://'. Check the log
-for details." He further found that it is possible to drop some parts
-of the VLC command line to reduce the amount of hardcoded information.
-It is also useful to consider using cvlc to avoid having the VLC
-window in the desktop view. In sum, this give us this command line on
-the source end
-
-<blockquote><pre>
-cvlc screen:// --sout \
- '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}'
-</pre></blockquote>
-
-<p>and this on the Kodi end<p>
-
-<blockquote><pre>
-echo rtsp://192.168.11.4:8080/ \
- > /storage/videos/screenstream.m3u
-</pre></blockquote>
-
-<p>Still bad image quality, though. But I did discover that streaming
-a DVD using dvdsimple:///dev/dvd as the source had excellent video and
-audio quality, so I guess the issue is in the input or transcoding
-parts, not the rtsp part. I've tried to change the vb and ab
-parameters to use more bandwidth, but it did not make a
-difference.</p>
-
-<p>I further received a suggestion from Einar Haraldseid to try using
-gstreamer instead of VLC, and this proved to work great! He also
-provided me with the trick to get Kodi to use a multicast stream as
-its source. By using this monstrous oneliner, I can stream my desktop
-with good video quality in reasonable framerate to the 239.255.0.1
-multicast address on port 1234:
-
-<blockquote><pre>
-gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
- videoconvert ! queue2 ! \
- x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
- key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
- mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
- udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
- pulsesrc device=$(pactl list | grep -A2 'Source #' | \
- grep 'Name: .*\.monitor$' | cut -d" " -f2|head -1) ! \
- audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
-</pre></blockquote>
-
-<p>and this on the Kodi end<p>
-
-<blockquote><pre>
-echo udp://@239.255.0.1:1234 \
- > /storage/videos/screenstream.m3u
-</pre></blockquote>
-
-<p>Note the trick to pick a valid pulseaudio source. It might not
-pick the one you need. This approach will of course lead to trouble
-if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
-local network. If the value is increased, your screen will be
-broadcasted further, one network "hop" for each increase (read up on
-multicast to learn more. :)!</p>
-
-<p>Having cracked how to get Kodi to receive multicast streams, I
-could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.</p>
-
-<blockquote><pre>
-cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
-</pre></blockquote>
+ <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>
+ <pubDate>Fri, 8 May 2020 13:30:00 +0200</pubDate>
+ <description><p>Half a year ago,
+<a href="http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html">I
+wrote</a> about <a href="https://jami.net/">the Jami communication
+client</a>, capable of peer-to-peer encrypted communication. It
+handle both messages, audio and video. It uses distributed hash
+tables instead of central infrastructure to connect its users to each
+other, which in my book is a plus. I mentioned briefly that it could
+also work as a SIP client, which came in handy when the higher
+educational sector in Norway started to promote Zoom as its video
+conferencing solution. I am reluctant to use the official Zoom client
+software, due to their <a href="https://zoom.us/terms">copyright
+license clauses</a> prohibiting users to reverse engineer (for example
+to check the security) and benchmark it, and thus prefer to connect to
+Zoom meetings with free software clients.</p>
+
+<p>Jami worked OK as a SIP client to Zoom as long as there was no
+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
+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
+could not get my dial tone signaling through from Jami to Zoom, and
+dial tone signaling is used to enter the password when connecting to
+Zoom. I tried a lot of different permutations with my Jami and
+Asterisk setup to try to figure out why the signaling did not get
+through, only to finally discover that the fundamental problem seem to
+be that Zoom is simply not able to receive dial tone signaling when
+connecting via SIP. There seem to be nothing wrong with the Jami and
+Asterisk end, it is simply broken in the Zoom end. I got help from a
+very skilled VoIP engineer figuring out this last part. And being a
+very skilled engineer, he was also able to locate a solution for me.
+Or to be exact, a workaround that solve my initial problem of
+connecting to password protected Zoom rooms using Jami.</p>
+
+<p>So, how do you do this, I am sure you are wondering by now. The
+trick is already
+<a href="https://support.zoom.us/hc/en-us/articles/202405539-H-323-SIP-Room-Connector-Dial-Strings#sip">documented
+from Zoom</a>, and it is to modify the SIP address to include the room
+password. What is most surprising about this is that the
+automatically generated email from Zoom with instructions on how to
+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 "<tt>[Meeting
+ID].[Password].[Layout].[Host Key]</tt>", and you can hear 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
+then look like this (all using made up numbers):</p>
+
+<p><blockquote>
+<tt>sip:657837644.522827@192.168.169.170</tt>
+</blockquote></p>
+
+<p>Now if only jami would reduce its memory usage, I could even
+recommend this setup to others. :)</p>
<p>As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
</item>
<item>
- <title>What is the most supported MIME type in Debian in 2018?</title>
- <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
- <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
- <description><p>Five years ago,
-<a href="http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html">I
-measured what the most supported MIME type in Debian was</a>, by
-analysing the desktop files in all packages in the archive. Since
-then, the DEP-11 AppStream system has been put into production, making
-the task a lot easier. This made me want to repeat the measurement,
-to see how much things changed. Here are the new numbers, for
-unstable only this time:
-
-<p><strong>Debian Unstable:</strong></p>
-
-<pre>
- count MIME type
- ----- -----------------------
- 56 image/jpeg
- 55 image/png
- 49 image/tiff
- 48 image/gif
- 39 image/bmp
- 38 text/plain
- 37 audio/mpeg
- 34 application/ogg
- 33 audio/x-flac
- 32 audio/x-mp3
- 30 audio/x-wav
- 30 audio/x-vorbis+ogg
- 29 image/x-portable-pixmap
- 27 inode/directory
- 27 image/x-portable-bitmap
- 27 audio/x-mpeg
- 26 application/x-ogg
- 25 audio/x-mpegurl
- 25 audio/ogg
- 24 text/html
-</pre>
-
-<p>The list was created like this using a sid chroot: "cat
-/var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk '/^
-- \S+\/\S+$/ {print $2 }' | sort | uniq -c | sort -nr | head -20"</p>
-
-<p>It is interesting to see how image formats have passed text/plain
-as the most announced supported MIME type. These days, thanks to the
-AppStream system, if you run into a file format you do not know, and
-want to figure out which packages support the format, you can find the
-MIME type of the file using "file --mime &lt;filename&gt;", and then
-look up all packages announcing support for this format in their
-AppStream metadata (XML or .desktop file) using "appstreamcli
-what-provides mimetype &lt;mime-type&gt;. For example if you, like
-me, want to know which packages support inode/directory, you can get a
-list like this:</p>
-
-<p><blockquote><pre>
-% appstreamcli what-provides mimetype inode/directory | grep Package: | sort
-Package: anjuta
-Package: audacious
-Package: baobab
-Package: cervisia
-Package: chirp
-Package: dolphin
-Package: doublecmd-common
-Package: easytag
-Package: enlightenment
-Package: ephoto
-Package: filelight
-Package: gwenview
-Package: k4dirstat
-Package: kaffeine
-Package: kdesvn
-Package: kid3
-Package: kid3-qt
-Package: nautilus
-Package: nemo
-Package: pcmanfm
-Package: pcmanfm-qt
-Package: qweborf
-Package: ranger
-Package: sirikali
-Package: spacefm
-Package: spacefm
-Package: vifm
-%
-</pre></blockquote></p>
-
-<p>Using the same method, I can quickly discover that the Sketchup file
-format is not yet supported by any package in Debian:</p>
-
-<p><blockquote><pre>
-% appstreamcli what-provides mimetype application/vnd.sketchup.skp
-Could not find component providing 'mimetype::application/vnd.sketchup.skp'.
-%
-</pre></blockquote></p>
-
-<p>Yesterday I used it to figure out which packages support the STL 3D
-format:</p>
-
-<p><blockquote><pre>
-% appstreamcli what-provides mimetype application/sla|grep Package
-Package: cura
-Package: meshlab
-Package: printrun
-%
-</pre></blockquote></p>
-
-<p>PS: A new version of Cura was uploaded to Debian yesterday.</p>
+ <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software</title>
+ <link>http://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</guid>
+ <pubDate>Wed, 29 Apr 2020 13:10:00 +0200</pubDate>
+ <description><p>The curiosity got the better of me when
+<a href="https://developers.slashdot.org/story/20/04/06/1424246/new-jersey-desperately-needs-cobol-programmers">Slashdot
+reported</a> that New Jersey was desperately looking for
+<a href="https://en.wikipedia.org/wiki/COBOL">COBOL</a> programmers,
+and a few days later it was reported that
+<a href="https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce">IBM
+tried to locate COBOL programmers</a>.</p>
+
+<p>I thus decided to have a look at free software alternatives to
+learn COBOL, and had the pleasure to find
+<a href="https://sourceforge.net/projects/open-cobol/">GnuCOBOL</a> was
+already <a href="https://tracker.debian.org/pkg/gnucobol">in
+Debian</a>. It used to be called Open Cobol, and is a "compiler"
+transforming COBOL code to C or C++ before giving it to GCC or Visual
+Studio to build binaries.</p>
+
+<p>I managed to get in touch with upstream, and was impressed with the
+quick response, and also was happy to see a new Debian maintainer
+taking over when the original one recently asked to be replaced. A
+new Debian upload was done as recently as yesterday.</p>
+
+<p>Using the Debian package, I was able to follow a simple COBOL
+introduction and make and run simple COBOL programs. It was fun to
+learn a new programming language. If you want to test for yourself,
+<a href="https://en.wikipedia.org/wiki/GnuCOBOL">the GnuCOBOL Wikipedia
+page</a> have a few simple examples to get you startet.</p>
+
+<p>As I do not have much experience with COBOL, I do not know how
+standard compliant it is, but it claim to pass most tests from COBOL
+test suite, which sound good to me. It is nice to know it is possible
+to learn COBOL using software without any usage restrictions, and I am
+very happy such nice free software project as this is available. If
+you as me is curious about COBOL, check it out.</p>
<p>As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
</item>
<item>
- <title>Debian APT upgrade without enough free space on the disk...</title>
- <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
- <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
- <description><p>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
-for a while, and when I need to update it there is not enough free
-space on the disk for apt to do a normal 'apt upgrade'. I normally
-would resolve the issue by doing 'apt install &lt;somepackages&gt;' to
-upgrade only some of the packages in one batch, until the amount of
-packages to download fall below the amount of free space available.
-Today, I had about 500 packages to upgrade, and after a while I got
-tired of trying to install chunks of packages manually. I concluded
-that I did not have the spare hours required to complete the task, and
-decided to see if I could automate it. I came up with this small
-script which I call 'apt-in-chunks':</p>
-
-<p><blockquote><pre>
-#!/bin/sh
-#
-# Upgrade packages when the disk is too full to upgrade every
-# upgradable package in one lump. Fetching packages to upgrade using
-# apt, and then installing using dpkg, to avoid changing the package
-# flag for manual/automatic.
-
-set -e
-
-ignore() {
- if [ "$1" ]; then
- grep -v "$1"
- else
- cat
- fi
-}
-
-for p in $(apt list --upgradable | ignore "$@" |cut -d/ -f1 | grep -v '^Listing...'); do
- echo "Upgrading $p"
- apt clean
- apt install --download-only -y $p
- for f in /var/cache/apt/archives/*.deb; do
- if [ -e "$f" ]; then
- dpkg -i /var/cache/apt/archives/*.deb
- break
- fi
- done
-done
-</pre></blockquote></p>
-
-<p>The script will extract the list of packages to upgrade, try to
-download the packages needed to upgrade one package, install the
-downloaded packages using dpkg. The idea is to upgrade packages
-without changing the APT mark for the package (ie the one recording of
-the package was manually requested or pulled in as a dependency). To
-use it, simply run it as root from the command line. If it fail, try
-'apt install -f' to clean up the mess and run the script again. This
-might happen if the new packages conflict with one of the old
-packages. dpkg is unable to remove, while apt can do this.</p>
-
-<p>It take one option, a package to ignore in the list of packages to
-upgrade. The option to ignore a package is there to be able to skip
-the packages that are simply too large to unpack. Today this was
-'ghc', but I have run into other large packages causing similar
-problems earlier (like TeX).</p>
-
-<p>Update 2018-07-08: Thanks to Paul Wise, I am aware of two
-alternative ways to handle this. The "unattended-upgrades
---minimal-upgrade-steps" option will try to calculate upgrade sets for
-each package to upgrade, and then upgrade them in order, smallest set
-first. It might be a better option than my above mentioned script.
-Also, "aptutude upgrade" can upgrade single packages, thus avoiding
-the need for using "dpkg -i" in the script above.</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>
+ <title>Totalovervåkning av innbyggernes bevegelser - nei takk!</title>
+ <link>http://people.skolelinux.org/pere/blog/Totaloverv_kning_av_innbyggernes_bevegelser___nei_takk_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Totaloverv_kning_av_innbyggernes_bevegelser___nei_takk_.html</guid>
+ <pubDate>Thu, 16 Apr 2020 20:30:00 +0200</pubDate>
+ <description><p>Jeg er blitt spurt hva jeg synes om lansering av smittestopp-appen,
+overvåkningsløsningen lansert av Folkehelseinstituttet,
+Simula-senteret og Regjeringen i dag, fulgt av klare trusler fra
+regjeringen om konsekvenser hvis befolkningen ikke tar den i bruk.
+Rekker ikke skrive noe fyldig om temaet, men det er klart for meg at
+den utraderer retten til privatliv samt utgjør en personlig
+sikkerhetsrisiko for alle som tar den i bruk. Bare det er nok til at
+det fremstår som en svært dårlig ide å bli med på denne "dugnaden".
+Det finnes andre og bedre tilnærminger enn den valgt av FHI. Har de
+valgt sin tilnærming for å sikre seg nok et datasett i den fremtidige
+ehelse-portalen? Potensialet for misbruk av informasjon samlet inn av
+appen er for stort, effekten på neste krise for klar og gevinsten for
+liten.</p>
+
+<p>For å si det med forhenværende leder i Datatilsynet, Georg Apenes,
+som skrev i en kronikk den gang Datatilsynet vernet
+privatsfæren at
+«<a href="https://www.dagbladet.no/kultur/rent-mel-i-bilen/66333882">SENTRALT
+I en liberal forestillingsverden finner vi aksept av borgerens rett
+til å kunne velge å være i fred; å være u-iakttatt, uregistrert og
+anonym</a>». Det er ikke uten grunn han startet kronikken med
+«Personvern et fremmedord i enkelte av de statsorganene som samler
+inn, oppbevarer og bruker personopplysninger». Der har nok
+statsorganene bare blitt dårligere på 13 år.</p>
+
+<p>Det er jo også verdt å merke seg at personvernrådet i EU (EDPB)
+mener smittestopp-appen
+<a href="https://nrkbeta.no/2020/04/16/personvernrad-i-eu-mener-norsk-app-bryter-med-viktig-personvernprinsipp/">opererer
+i strid med prinsippet om dataminimering</a>. Også de ser at det
+finnes mye bedre måter å gjøre dette på.</p>
+
+
+<p>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
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
+Merk, betaling med bitcoin er ikke anonymt. :)</p>
</description>
</item>
<item>
- <title>The worlds only stone power plant?</title>
- <link>http://people.skolelinux.org/pere/blog/The_worlds_only_stone_power_plant_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_worlds_only_stone_power_plant_.html</guid>
- <pubDate>Sat, 30 Jun 2018 10:35:00 +0200</pubDate>
- <description><p>So far, at least hydro-electric power, coal power, wind power,
-solar power, and wood power are well known. Until a few days ago, I
-had never heard of stone power. Then I learn about a quarry in a
-mountain in
-<a href="https://en.wikipedia.org/wiki/Bremanger">Bremanger</a> i
-Norway, where
-<a href="https://www.bontrup.com/en/activities/raw-materials/bremanger-quarry/">the
-Bremanger Quarry</a> company is extracting stone and dumping the stone
-into a shaft leading to its shipping harbour. This downward movement
-in this shaft is used to produce electricity. In short, it is using
-falling rocks instead of falling water to produce electricity, and
-according to its own statements it is producing more power than it is
-using, and selling the surplus electricity to the Norwegian power
-grid. I find the concept truly amazing. Is this the worlds only
-stone power plant?</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>
+ <title>Ny URL til den frie norske stavekontrollen</title>
+ <link>http://people.skolelinux.org/pere/blog/Ny_URL_til_den_frie_norske_stavekontrollen.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ny_URL_til_den_frie_norske_stavekontrollen.html</guid>
+ <pubDate>Sat, 21 Mar 2020 08:00:00 +0100</pubDate>
+ <description><p>Det er lenge siden jeg har sett på den norske stavekontrollen, sist
+jeg skrev om temaet var i 2016, og i mellomtiden har nettstedet
+no.speling.org forsvunnet, og både git-depotet på Alioth og
+mailman-tjenesten som hadde epostlistene for oversettelser blitt lagt
+ned. Men bokmål og nynorsk trenger fortsatt stavekontroll, så etter
+et par purringer fra en som har lyst til å forbedre stavekontrollen
+har jeg endelig fått lagt ut ny offentlig kopi av git-depotet. Jeg
+valgte gitlab foran github.. Siste utgave av stavekontrollen kan
+hentes ned fra
+<a href="https://gitlab.com/norwegian-language-tools/spell-norwegian">https://gitlab.com/norwegian-language-tools/spell-norwegian</a>.
+Ingen ny versjon i denne omgang altså, bare et nytt sted å samle
+forbedringer til den frie norske stavekontrollen. :)
+
+<p>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
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
+Merk, betaling med bitcoin er ikke anonymt. :)</p>
</description>
</item>
<item>
- <title>Add-on to control the projector from within Kodi</title>
- <link>http://people.skolelinux.org/pere/blog/Add_on_to_control_the_projector_from_within_Kodi.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Add_on_to_control_the_projector_from_within_Kodi.html</guid>
- <pubDate>Tue, 26 Jun 2018 23:55:00 +0200</pubDate>
- <description><p>My movie playing setup involve <a href="https://kodi.tv/">Kodi</a>,
-<a href="https://openelec.tv">OpenELEC</a> (probably soon to be
-replaced with <a href="https://libreelec.tv/">LibreELEC</a>) and an
-Infocus IN76 video projector. My projector can be controlled via both
-a infrared remote controller, and a RS-232 serial line. The vendor of
-my projector, <a href="https://www.infocus.com/">InFocus</a>, had been
-sensible enough to document the serial protocol in its user manual, so
-it is easily available, and I used it some years ago to write
-<a href="https://github.com/petterreinholdtsen/infocus-projector-control">a
-small script to control the projector</a>. For a while now, I longed
-for a setup where the projector was controlled by Kodi, for example in
-such a way that when the screen saver went on, the projector was
-turned off, and when the screen saver exited, the projector was turned
-on again.</p>
-
-<p>A few days ago, with very good help from parts of my family, I
-managed to find a Kodi Add-on for controlling a Epson projector, and
-got in touch with its author to see if we could join forces and make a
-Add-on with support for several projectors. To my pleasure, he was
-positive to the idea, and we set out to add InFocus support to his
-add-on, and make the add-on suitable for the official Kodi add-on
-repository.</p>
-
-<p>The Add-on is now working (for me, at least), with a few minor
-adjustments. The most important change I do relative to the master
-branch in the github repository is embedding the
-<a href="https://github.com/pyserial/pyserial">pyserial module</a> in
-the add-on. The long term solution is to make a "script" type
-pyserial module for Kodi, that can be pulled in as a dependency in
-Kodi. But until that in place, I embed it.</p>
-
-<p>The add-on can be configured to turn on the projector when Kodi
-starts, off when Kodi stops as well as turn the projector off when the
-screensaver start and on when the screesaver stops. It can also be
-told to set the projector source when turning on the projector.
-
-<p>If this sound interesting to you, check out
-<a href="https://github.com/fredrik-eriksson/kodi_projcontrol">the
-project github repository</a>. Perhaps you can send patches to
-support your projector too? As soon as we find time to wrap up the
-latest changes, it should be available for easy installation using any
-Kodi instance.</p>
-
-<p>For future improvements, I would like to add projector model
-detection and the ability to adjust the brightness level of the
-projector from within Kodi. We also need to figure out how to handle
-the cooling period of the projector. My projector refuses to turn on
-for 60 seconds after it was turned off. This is not handled well by
-the add-on at the moment.</p>
+ <title>Nikita version 0.5 released - updated free software archive API server</title>
+ <link>http://people.skolelinux.org/pere/blog/Nikita_version_0_5_released___updated_free_software_archive_API_server.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nikita_version_0_5_released___updated_free_software_archive_API_server.html</guid>
+ <pubDate>Mon, 2 Mar 2020 19:00:00 +0100</pubDate>
+ <description><p>Today, after many months of development, a new release of
+<ahref="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita
+Noark 5 core project</a> was finally
+<ahref="https://lists.nuug.no/pipermail/nikita-noark/2020-March/000519.html">announced
+on the project mailing list</a>. The Nikita free software solution is
+an implementation of the Norwegian archive standard Noark 5 used by
+government offices in Norway. These were the changes in version 0.5
+since version 0.4, see the email link above for links to a demo
+site:</p>
+
+<ul>
+
+ <li>Updated to Noark 5 versjon 5.0 API specification.
+ <ul>
+ <li>Changed formatting of _links from [] to {} to match IETF draft
+ on JSON HAL.</li>
+ <li>Merged Registrering og Basisregistrering in version 4 to
+ combined Registrering.</li>
+ <li>DokumentObjekt is now subtype of ArkivEnhet.</li>
+ <li>Introducing new entity Arkivnotat.</li>
+ <li>Changed all relation keys to use /v5/ instead of /v4/.</li>
+ <li>Corrected to use new official relation keys when possible.</li>
+ <li>Renamed Sakspart to Part and connect it to Mappe, Registrering
+ and Dokumentbeskrivelse instead of only Saksmappe.</li>
+ <li>Moved Korrespondansepart connection from Journalpost to
+ Registrering.</li>
+ <li>Moved Part and Korrespondansepart from package sakarkiv to
+ arkivstruktur.</li>
+ <li>Renamed presedensstatus to presedensStatus.</li>
+ <li>Use new JSON content-type "application/vnd.noark5+json".</li>
+ <li>Updated prepopulated format list to use PRONOM codes.</li>
+ <li>Implemented endpoint for system information.</li>
+ <li>Implemented national identifiers for both file and record.</li>
+ <li>Implemented comments.</li>
+ <li>implemented sign off.</li>
+ <li>implemented conversion.</li>
+ </ul></li>
+ <li>Improved/implemented OData search and paging support for more entities.</li>
+ <li>No longer exposes attribute Dokumentobjekt.referanseDokumentfil,
+ one should use the relation in _links instead.</li>
+ <li>Corrected relation keys under
+ https://rel.arkivverket.no/noark5/v5/api/administrasjon/, replacing
+ 'administrasjon' with 'admin'.</li>
+ <li>Fixed several security and stability issues discovered by Coverity.</li>
+ <li>Corrected handling ETag errors, now return code 409.</li>
+ <li>Improved handling of Kryssreferanse.</li>
+ <li>Changed internal database model to use UUID/SystemID as primary keys
+ in tables.</li>
+ <li>Changed internal database table names to use package prefix.</li>
+ <li>Changed time zone handling for date and datetime attributes, to be
+ more according to the new definition in the API specification.</li>
+ <li>Change revoke-token to only drop token on POST requests, not GET.</li>
+ <li>Updated to newer Spring version.</li>
+ <li>Changed primary key and URL component for metadata code lists to
+ use the 'kode' value instead of a SystemID.</li>
+ <li>Corrected implementation of Part and Sakspart.</li>
+ <li>Changed instance lists with subtypes (like .../registrering/ and
+ .../mappe/) to include the attributes and _links entries for the
+ subtype in the supertype lists.</li>
+ <li>Adjusted _links relations to make it possible to figure out the
+ entity of an instance using the self->href->relation key lookup
+ method.</li>
+ <li>Fixed several end points to make sure GET, PUT, POST and DELETE
+ match each other.</li>
+ <li>Updated DELETE endpoints to work with UUID based entity
+ identifiers.</li>
+ <li>Restructured code to use more common URL related constants in entry
+ point values and replace @RequestMapping with method specific
+ annotations.</li>
+ <li>Added first unit test code.</li>
+ <li>Updated web GUI to work with the updated API.</li>
+ <li>Changed integer fields, enforce them as numeric.</li>
+ <li>Rewrote and simplify metadata handling to use common service and
+ controller code instead of duplicating for each type.</li>
+ <li>Implemented the remaining metadata types.</li>
+ <li>Changed Country list source from Wikipedia to Debian iso-codes and
+ updated the list of Countries.</li>
+ <li>Many many corrections and improvements.</li>
+
+</ul>
+
+<p>If free and open standardized archiving API sound interesting to
+you, please contact us on IRC
+(<a href="irc://irc.freenode.net/%23nikita">#nikita on
+irc.freenode.net</a>) or email
+(<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
+mailing list</a>).</p>
<p>As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
</item>
<item>
- <title>youtube-dl for nedlasting fra NRK med undertekster - nice free software</title>
- <link>http://people.skolelinux.org/pere/blog/youtube_dl_for_nedlasting_fra_NRK_med_undertekster___nice_free_software.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/youtube_dl_for_nedlasting_fra_NRK_med_undertekster___nice_free_software.html</guid>
- <pubDate>Sat, 28 Apr 2018 10:30:00 +0200</pubDate>
- <description><p>I <a href="https://no.wikipedia.org/wiki/VHS">VHS-kassettenes</a>
-tid var det rett frem å ta vare på et TV-program en ønsket å kunne se
-senere, uten å være avhengig av at programmet ble sendt på nytt.
-Kanskje ønsket en å se programmet på hytten der det ikke var
-TV-signal, eller av andre grunner ha det tilgjengelig for fremtidig
-fornøyelse. Dette er blitt vanskeligere med introduksjon av
-digital-TV og webstreaming, der opptak til harddisk er utenfor de
-flestes kontroll hvis de bruker ufri programvare og bokser kontrollert
-av andre. Men for NRK her i Norge, finnes det heldigvis flere fri
-programvare-alternativer, som jeg har
-<a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK.html">skrevet</a>
-<a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html">om</a>
-<a href="http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html">før</a>.
-Så lenge kilden for nedlastingen er lovlig lagt ut på nett (hvilket
-jeg antar NRK gjør), så er slik lagring til privat bruk også lovlig i
-Norge.</p>
-
-<p>Sist jeg så på saken, i 2016, nevnte jeg at
-<a href="https://rg3.github.com/youtube-dl/">youtube-dl</a> ikke kunne
-bake undertekster fra NRK inn i videofilene, og at jeg derfor
-foretrakk andre alternativer. Nylig oppdaget jeg at dette har endret
-seg. Fordelen med youtube-dl er at den er tilgjengelig direkte fra
-Linux-distribusjoner som <a href="https://www.debian.org/">Debian</a>
-og <a href="https://www.ubuntu.com/">Ubuntu</a>, slik at en slipper å
-finne ut selv hvordan en skal få dem til å virke.</p>
-
-<p>For å laste ned et NRK-innslag med undertekster, og få den norske
-underteksten pakket inn i videofilen, så kan følgende kommando
-brukes:</p>
-
-<p><pre>
-youtube-dl --write-sub --sub-format ttml \
- --convert-subtitles srt --embed-subs \
- https://tv.nrk.no/serie/ramm-ferdig-gaa/MUHU11000316/27-04-2018
-</pre></p>
-
-<p>URL-eksemplet er dagens toppsak på tv.nrk.no. Resultatet er en
-MP4-fil med filmen og undertekster som kan spilles av med VLC. Merk
-at VLC ikke viser frem undertekster før du aktiverer dem. For å gjøre
-det, høyreklikk med musa i fremviservinduet, velg menyvalget for
-undertekst og så norsk språk. Jeg testet også '--write-auto-sub',
-men det kommandolinjeargumentet ser ikke ut til å fungere, så jeg
-endte opp med settet med argumentlisten over, som jeg fant i en
-feilrapport i youtube-dl-prosjektets samling over feilrapporter.</p>
-
-<p>Denne støtten i youtube-dl gjør det svært enkelt å lagre
-NRK-innslag, det være seg nyheter, filmer, serier eller dokumentater,
-for å ha dem tilgjengelig for fremtidig referanse og bruk, uavhengig
-av hvor lenge innslagene ligger tilgjengelig hos NRK. Så får det ikke
-hjelpe at NRKs jurister mener at det er
-<a href="http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">vesensforskjellig
-å legge tilgjengelig for nedlasting og for streaming</a>, når det rent
-teknisk er samme sak.</p>
-
-<p>Programmet youtube-dl støtter også en rekke andre nettsteder, se
-prosjektoversikten for
-<a href="http://rg3.github.io/youtube-dl/supportedsites.html">en
-komplett liste</a>.</p>
+ <title>Blockchain and IoT articles accepted into Records Management Journal</title>
+ <link>http://people.skolelinux.org/pere/blog/Blockchain_and_IoT_articles_accepted_into_Records_Management_Journal.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Blockchain_and_IoT_articles_accepted_into_Records_Management_Journal.html</guid>
+ <pubDate>Thu, 27 Feb 2020 09:05:00 +0100</pubDate>
+ <description><p>On Tuesday, two scietific articles we have been working on for a
+while, was finally accepted for publication into
+<a href="https://www.emerald.com/insight/publication/issn/0956-5698">Records
+Management Journal</a>. Still waiting for the assigned DOI urls to
+start working, but you can have a look at the LaTeX originals here.</p>
+
+<p>The first article is
+"<a href="http://people.skolelinux.org/pere/blog/images/2020-02-25-rmj-iot-record-keeping.pdf">A
+record-keeping approach to managing IoT-data for government
+agencies</a>" (<a href="https://doi.org/10.1108/RMJ-09-2019-0050">DOI
+10.1108/RMJ-09-2019-0050<a/>) by Thomas Sødring, Petter Reinholdtsen
+and David Massey, and sketches some approaches for storing measurement
+data (aka Internet of Things sensor data) in a archive, thus providing
+a well defined mechanism for screening and deletion of the information </p>
+
+<p>The second article is
+"<a href="http://people.skolelinux.org/pere/blog/images/2020-02-25-rmj-block-chain-record-keeping.pdf">Publishing
+and using record-keeping structural information in a blockchain</a>"
+(<a href="https://doi.org/10.1108/RMJ-09-2019-0056">DOI
+10.1108/RMJ-09-2019-0056</a>) by Thomas Sødring, Petter Reinholdtsen
+and Svein Ølnes, where we describe a way for third parties to validate
+authenticity and thus improve trust in the records kept in a
+archive.</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>
+
+<p><strong>Update 2020-04-26</strong>: Initially managed to swap the
+DOI numbers. Fixed it.</p>
</description>
</item>
<item>
- <title>Stortingsflertallet går inn for ny IP-basert sensurinfrastruktur i Norge</title>
- <link>http://people.skolelinux.org/pere/blog/Stortingsflertallet_g_r_inn_for_ny_IP_basert_sensurinfrastruktur_i_Norge.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Stortingsflertallet_g_r_inn_for_ny_IP_basert_sensurinfrastruktur_i_Norge.html</guid>
- <pubDate>Tue, 24 Apr 2018 15:00:00 +0200</pubDate>
- <description><p><a href="https://www.vg.no/sport/i/J1g8zj/stortingsvedtak-snart-ip-blokkerer-utenlandske-spillselskaper">VG</a>,
-<a href="https://www.dagbladet.no/nyheter/stortinget-blokkerer-utenlandske-spillselskaper/69740219">Dagbladet</a>
-og
-<a href="https://www.nrk.no/ostfold/tar-opp-kampen-mot-utenlandske-spillselskap-1.14021381">NRK</a>
-melder i dag at flertallet i Familie- og kulturkomiteen på Stortinget
-har bestemt seg for å introdusere en ny sensurinfrastruktur i Norge.
-Fra før har Norge en «frivillig» sensurinfrastruktur basert på
-DNS-navn, der de største ISP-ene basert på en liste med DNS-navn
-forgifter DNS-svar og omdirigerer til et annet IP-nummer enn det som
-ligger i DNS. Nå kommer altså IP-basert omdirigering i tillegg. Når
-infrastrukturen er på plass, er sensur av IP-adresser redusert et
-spørsmål om hvilke IP-nummer som skal blokkeres. Listen over
-IP-adresser vil naturligvis endre seg etter hvert som myndighetene
-endrer seg. Det er ingen betryggende tanke.</p>
+ <title>Redaksjon på plass for Noark 5 tjenestegrensesnitt</title>
+ <link>http://people.skolelinux.org/pere/blog/Redaksjon_p__plass_for_Noark_5_tjenestegrensesnitt.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Redaksjon_p__plass_for_Noark_5_tjenestegrensesnitt.html</guid>
+ <pubDate>Wed, 5 Feb 2020 14:45:00 +0100</pubDate>
+ <description><p>Arbeidet med å lage et godt, fritt og åpent standardisert maskinelt
+grensesnitt for arkivering, med tilhørende fri
+programvareimplementasjon fortsetter. Jeg snakker om
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard">Noark
+5 Tjenestegrensesnitt</a> og
+<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita</a>.
+Siste nytt etter
+<a href="https://www.nuug.no/aktiviteter/20200127-noark-seminar/">seminaret
+for noen dager siden</a>, er vi i Nikita-prosjektet har fått beskjed
+fra Arkivverket at det blir satt ned en redaksjon for å videreutvikle
+spesifikasjonen. Redaksjonen består av Mona Danielsen og Anne Sofie
+Knutsen ved arkivverket, Thomas Sødring ved OsloMet, og meg selv fra
+NUUG. De to sistenevnte tar seg av de åpenbare forbedringene, mens
+hele redaksjonen diskuterer tvilstilfeller. Jeg håper dette vil bidra
+til at vi lykkes i å gjøre denne protokollspesifikasjonen så entydig
+og klar at den vil bidra til et velfungerende marked for
+arkivsystemer, og sikre at programmer som trenger å snakke med
+arkivsystemet kan snakke med enhver implementasjon av
+API-spesifikasjonen. Nikita er den første implementasjonen, men det
+bør blir flere.</p>
+
+<p>Det gjenstår riktig nok endel før vi er i mål, selv om svært mye
+allerede er på plass. Med innspill og forslag til forbedringer fra
+alle som vil ha et leverandøruavhengig og fullstendig
+datamaskinlesbart grensesnitt til arkivet, så tror jeg vi vil
+lykkes.</p>
+
+<p>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
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
+Merk, betaling med bitcoin er ikke anonymt. :)</p>
</description>
</item>
<item>
- <title>En grunn til å takke nei til usikker digital post</title>
- <link>http://people.skolelinux.org/pere/blog/En_grunn_til___takke_nei_til_usikker_digital_post.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/En_grunn_til___takke_nei_til_usikker_digital_post.html</guid>
- <pubDate>Mon, 2 Apr 2018 13:30:00 +0200</pubDate>
- <description><p>Brevpost er beskyttet av straffelovens bestemmelse som gjør det
-kriminelt å åpne andres brev. Dette følger av (ny) straffelovs
-<a href="https://lovdata.no/dokument/NL/lov/2005-05-20-28/§205">§ 205
-(Krenkelse av retten til privat kommunikasjon)</a>, som sier at «Med
-bot eller fengsel inntil 2 år straffes den som uberettiget ... c)
-åpner brev eller annen lukket skriftlig meddelelse som er adressert
-til en annen, eller på annen måte skaffer seg uberettiget tilgang til
-innholdet.» Dette gjelder såvel postbud som alle andre som har
-befatning med brevet etter at avsender har befatning med et lukket
-brev. Tilsvarende står også tidligere utgaver av den norske
-straffeloven.</p>
-
-<p>Når en registrerer seg på usikre digitale postkasseløsningene, som
-f.eks. Digipost og e-Boks, og slik tar disse i bruk, så gir en de som
-står bak løsningene tillatelse til å åpne sine brev. Dette er
-nødvendig for at innholdet i digital post skal kunne vises frem til
-mottaker via tjenestens websider. Dermed gjelder ikke straffelovens
-paragraf om forbud mot å åpne brev, da tilgangen ikke lenger er
-uberettiget. En gir altså fremmede tilgang til å lese sin
-korrespondanse. I tillegg vil bruk av slike usikre digitale
-postbokser føre til at det blir registrert når du leser brevene, hvor
-du befinner deg (vha. tilkoblingens IP-adresse), hvilket utstyr du
-bruker og en rekke annen personlig informasjon som ikke er
-tilgjengelig når papirpost brukes. Jeg foretrekker at det er
-lovmessig beskyttelse av min korrespondanse, som jo inneholder privat
-og personlig informasjon. Det bidrar til litt bedre vern av personlig
-integritet i dagens norske samfunn.</p>
+ <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><p>Like før julaften ble en artikkel jeg har skrevet om vedlikehold av
+<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard">Noark
+5 Tjenestegrensesnitt</a> og Nikita publisert i <a
+href="https://www.arkivrad.no/arkivrad">tidsskriftet Arkivråd</a>.
+Det er basert på
+<a href="http://people.skolelinux.org/pere/blog/_pen_og_gjennomsiktig_vedlikehold_av_spesifikasjonen_for_Noark_5_Tjenestegrensesnitt.html">min bloggpost
+om samme tema</a> 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
+<a href="https://www.arkivrad.no/sites/arkivrad/files/arkivrad_03_2019_nett.pdf">PDF-en
+til nummer 2019/3 på side 30-33</a>. 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
+<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">arkivsystemet
+Nikita</a> kan bli enda bedre når spesifikasjonen forbedres.</p>
+
+<p>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
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
+Merk, betaling med bitcoin er ikke anonymt. :)</p>
</description>
</item>
<item>
- <title>Self-appointed leaders of the Free World</title>
- <link>http://people.skolelinux.org/pere/blog/Self_appointed_leaders_of_the_Free_World.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Self_appointed_leaders_of_the_Free_World.html</guid>
- <pubDate>Thu, 22 Mar 2018 11:00:00 +0100</pubDate>
- <description><p>The leaders of the worlds have started to congratulate the
-re-elected Russian head of state, and this causes some criticism. I
-am though a little fascinated by a comment from USA senator John McCain,
-<a href="http://thehill.com/homenews/senate/379339-mccain-rips-trumps-congratulatory-call-to-putin-as-insult-to-russian-people">sited
-by The Hill and others</a>:
-
-<p><blockquote>
-<p>"An American president does not lead the Free World by
-congratulating dictators on winning sham elections."</p>
-</blockquote></p>
-
-<p>While I totally agree with the senator here, the way the quote is
-phrased make me suspect that he is unaware of the simple fact that USA
-have not lead the Free World since at least before its government
-<a href="https://en.wikipedia.org/wiki/Maher_Arar">kidnapped a
-completely innocent Canadian citizen in transit on his way home to
-Canada via John F. Kennedy International Airport in September 2002 and
-sent him to be tortured in Syria for a year</a>.</p>
-
-<p>USA might be running ahead, but the path they are taking is not the
-one taken by any Free World.</p>
+ <title>Meningsløst, men for hvem...</title>
+ <link>http://people.skolelinux.org/pere/blog/Meningsl_st__men_for_hvem___.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Meningsl_st__men_for_hvem___.html</guid>
+ <pubDate>Wed, 25 Dec 2019 10:35:00 +0100</pubDate>
+ <description><p>En historie som har betydd endel for meg, og som jeg av og til
+tenker på når hverdagen tynger, ble så vidt jeg har klart å finne ut,
+skrevet av <a href="https://en.wikipedia.org/wiki/Loren_Eiseley">Loren
+Eiseley</a> <a href="https://en.wikipedia.org/wiki/The_Star_Thrower">i
+flere ulike varianter</a>. På norsk tror jeg den går under navnet
+«Gutten og sjøstjernen», og jeg fant en oversettelse av en utgave av den
+hos
+<a href="https://no.quora.com/Hva-er-din-favoritthistorie">Quora</a>.
+Fant også <a href="https://www.youtube.com/watch?v=-qClChUdlfI">en
+filmatisering</a>, men den versjonen jeg liker best fant jeg
+<a href="https://www.goodreads.com/author/quotes/56782.Loren_Eiseley">hos
+Goodreads</a>. Jeg oversatte den utgaven til norsk i går, og har lyst
+til å dele den med deg:
+
+<blockquote><p>Mens jeg tok en pause fra skrivingen og vandret på en
+øde strand ved daggry, så jeg en gutt i det fjerne bøye seg ned og
+kaste noe mens han vandret mot meg over den endeløse stranden. Da han
+kom nærmere, kunne jeg se at han kastet sjøstjerner, som var etterlatt
+i sanden av tidevannet, tilbake i havet. Da han var nær nok spurte jeg
+ham hvorfor han jobbet så hardt på denne merkelige oppgaven. Han sa at
+solen snart ville stå opp og tørke sjøstjernene slik at de ville
+dø.</p>
+
+<p>Jeg sa til ham at dette var helt meningsløst. Det var kilometer på
+kilometer med strand, og det lå sjøstjerner hele veien. En person
+alene kunne ikke gjøre noen forskjell. Han smilte da han plukket opp
+neste sjøstjerne. Mens han kastet den så langt ut i havet som han
+klarte sa han, «for denne gjør det en forskjell». Jeg droppet
+skrivingen og tilbrakte resten av morgenen med å kaste
+sjøstjerner.</p>
+
+<p>- Loren Eiseley</p>
+</blockquote>
+
+<p>Kanskje noe du også kan ha glede av å tenke på når ting virker
+håpløst?</p>
+
+<p>Teksten er gjengitt og oversatt basert på utgaven på Good Read,
+uten tillatelse fra noen andre enn meg selv. Jeg håper på tilgivelse,
+hvis det er et problem for noen, da det er gjort i beste mening. Hvis
+eventuell rettighetshaver tar kontakt vil jeg fjerne teksten og i
+stedet legge ut henvendelsen der teksten kreves fjernet.</p>
+
+<p>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
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
+Merk, betaling med bitcoin er ikke anonymt. :)</p>
</description>
</item>
<item>
- <title>Facebooks ability to sell your personal information is the real Cambridge Analytica scandal</title>
- <link>http://people.skolelinux.org/pere/blog/Facebooks_ability_to_sell_your_personal_information_is_the_real_Cambridge_Analytica_scandal.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Facebooks_ability_to_sell_your_personal_information_is_the_real_Cambridge_Analytica_scandal.html</guid>
- <pubDate>Wed, 21 Mar 2018 16:30:00 +0100</pubDate>
- <description><p>So, Cambridge Analytica is getting some well deserved criticism for
-(mis)using information it got from Facebook about 50 million people,
-mostly in the USA. What I find a bit surprising, is how little
-criticism Facebook is getting for handing the information over to
-Cambridge Analytica and others in the first place. And what about the
-people handing their private and personal information to Facebook?
-And last, but not least, what about the government offices who are
-handing information about the visitors of their web pages to Facebook?
-No-one who looked at the terms of use of Facebook should be surprised
-that information about peoples interests, political views, personal
-lifes and whereabouts would be sold by Facebook.</p>
-
-<p>What I find to be the real scandal is the fact that Facebook is
-selling your personal information, not that one of the buyers used it
-in a way Facebook did not approve when exposed. It is well known that
-Facebook is selling out their users privacy, but a scandal
-nevertheless. Of course the information provided to them by Facebook
-would be misused by one of the parties given access to personal
-information about the millions of Facebook users. Collected
-information will be misused sooner or later. The only way to avoid
-such misuse, is to not collect the information in the first place. If
-you do not want Facebook to hand out information about yourself for
-the use and misuse of its customers, do not give Facebook the
-information.</p>
-
-<p>Personally, I would recommend to completely remove your Facebook
-account, and take back some control of your personal information.
-<a href="https://www.theguardian.com/technology/2018/mar/19/how-to-protect-your-facebook-privacy-or-delete-yourself-completely">According
-to The Guardian</a>, it is a bit hard to find out how to request
-account removal (and not just 'disabling'). You need to
-<a href="https://www.facebook.com/help/224562897555674?helpref=faq_content">visit
-a specific Facebook page</a> and click on 'let us know' on that page
-to get to <a href="https://www.facebook.com/help/delete_account">the
-real account deletion screen</a>. Perhaps something to consider? I
-would not trust the information to really be deleted (who knows,
-perhaps NSA, GCHQ and FRA already got a copy), but it might reduce the
-exposure a bit.</p>
-
-<p>If you want to learn more about the capabilities of Cambridge
-Analytica, I recommend to see the video recording of the one hour talk
-Paul-Olivier Dehaye gave to <a href="">NUUG</a> last april about
-<a href="https://www.nuug.no/aktiviteter/20170404-big-data-psychometric/">
-Data collection, psychometric profiling and their impact on
-politics</a>.</p>
-
-<p>And if you want to communicate with your friends and loved ones,
-use some end-to-end encrypted method like
-<a href="https://www.signal.org/">Signal</a> or
-<a href="https://ring.cx/">Ring</a>, and stop sharing your private
-messages with strangers like Facebook and Google.</p>
+ <title>Artikkel om Nikita i Arkheion nummer 2019/2</title>
+ <link>http://people.skolelinux.org/pere/blog/Artikkel_om_Nikita_i_Arkheion_nummer_2019_2.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Artikkel_om_Nikita_i_Arkheion_nummer_2019_2.html</guid>
+ <pubDate>Mon, 9 Dec 2019 15:05:00 +0100</pubDate>
+ <description><p>Jeg hadde i dag gleden av å oppdage at en artikkel om
+<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">arkivsystemet
+Nikita</a> som vi skrev i sommer, nå er publisert i
+<a href="http://www.arkheion.no/">Arkheion, fagtidsskrift for kommunial
+arkivsektor</a>. Du finner artikkelen på side 30-33 i nummer 2019/2,
+PDF kan lastes ned fra nettstedet til tidsskriftet. Kanskje
+publiseringen kan føre til at noen flere får øynene opp for verdien av
+et åpent standardisert API for arkivering og søk i arkivet.</p>
+
+<p>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
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
+Merk, betaling med bitcoin er ikke anonymt. :)</p>
</description>
</item>
projects / homepage.git / blobdiff