1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/' xmlns:
atom=
"http://www.w3.org/2005/Atom">
4 <title>Petter Reinholdtsen
</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
7 <atom:link href=
"http://people.skolelinux.org/pere/blog/index.rss" rel=
"self" type=
"application/rss+xml" />
10 <title>More reliable vlc bittorrent plugin in Debian (version
2.9)
</title>
11 <link>http://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html
</guid>
13 <pubDate>Sun,
24 May
2020 17:
00:
00 +
0200</pubDate>
14 <description><p
>I am very happy to report that a more reliable vlc bittorrent
15 plugin was just uploaded into debian. This fixes a couple of crash
16 bugs in the plugin, hopefully making the VLC experience even better
17 when streaming directly from a bittorrent source. The package is
18 currently in Debian unstable, but should be available in Debian
19 testing in two days. To test it, simply install it like this:
</p
>
22 apt install vlc-plugin-bittorrent
23 </pre
></p
>
25 <p
>After it is installed, you can try to use it to play a file
26 downloaded live via bittorrent like this:
29 vlc https://archive.org/download/Glass_201703/Glass_201703_archive.torrent
30 </pre
></p
>
32 <p
>It also support magnet links and local .torrent files.
</p
>
34 <p
>As usual, if you use Bitcoin and want to show your support of my
35 activities, please send Bitcoin donations to my address
36 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
41 <title>Debian Edu interview: Yvan Masson
</title>
42 <link>http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html
</link>
43 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html
</guid>
44 <pubDate>Tue,
12 May
2020 06:
30:
00 +
0200</pubDate>
45 <description><p
>It has been way too long since my last interview, but as the
46 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
>
47 community is still active, and new people keep showing up on the IRC
48 channel
<a href=
"irc://irc.debian.org/#debian-edu
">#debian-edu
</a
> and
49 <a href=
"https://lists.debian.org/debian-edu/
">the debian-edu mailing
50 list
</a
>, I decided to give it another go. I was hoping someone else
51 might pick up the idea and run with it, but this has not happened as
52 far as I can tell, so here we are… This time the announcement of a new
54 <a href=
"https://framagit.org/Yvan-Masson/WhosWho
">create a school year
55 book
</a
> triggered my interest, and I decided to learn more about its
58 <p
><strong
>Who are you, and how do you spend your days?
</strong
></p
>
60 <p
>My name is Yvan MASSON, I live in France. I have my own one person
61 business in computer services. The work consist of visiting my
62 customers (person
's home, local authority, small business) to give
63 advise, install computers and software, fix issues, and provide
64 computing usage training. I spend the rest of my time enjoying my
65 family and promoting free software.
</p
>
67 <p
><strong
>What is your approach for promoting free
68 software?
</strong
></p
>
70 <p
>When I think that free software could be suitable for someone, I
71 explain what it is, with simple words, give a few known examples, and
72 explain that while there is no fee it is a viable alternative in many
73 situations. Most people are receptive when you explain how it is
74 better (I simplify arguments here, I know that it is not so simple):
75 Linux works on older hardware, there are no viruses, and the software
76 can be audited to ensure user is not spied upon. I think the most
77 important is to keep a clear but moderated speech: when you try to
78 convince too much, people feel attacked and stop listening.
</p
>
80 <p
><strong
>How did you get in contact with the Skolelinux / Debian Edu
81 project?
</strong
></p
>
83 <p
>I can not remember how I first heard of Skolelinux / Debian Edu,
84 but probably on planet.debian.org. As I have been working for a
85 school, I have interest in this type of project.
87 <p
>The school I am involved in is a school for
"children
" between
14
88 and
18 years old. The French government has recommended free software
89 since
2012, but they do not always use free software themselves. The
90 school computers are still using the Windows operating system, but all
91 of them have the classic set of free software: Firefox ESR,
92 LibreOffice (with the excellent extension Grammalecte that indicates
93 French grammatical errors), SumatraPDF, Audacity,
7zip, KeePass2, VLC,
96 <p
><strong
>What do you see as the advantages of Skolelinux / Debian
97 Edu?
</strong
></p
>
99 <p
>It is free software! Built on Debian, I am sure that users are not
100 spied upon, and that it can run on low end hardware. This last point
101 is very important, because we really need to improve
"green IT
". I do
102 not know enough about Skolelinux / Debian Edu to tell how it is better
103 than another free software solution, but what I like is the
"all in
104 one
" solution: everything has been thought of and prepared to ease
105 installation and usage.
</p
>
107 <p
>I like Free Software because I hate using something that I can not
108 understand. I do not say that I can understand everything nor that I
109 want to understand everything, but knowing that someone / some company
110 intentionally prevents me from understanding how things work is really
111 unacceptable to me.
</p
>
113 <p
>Secondly, and more importantly, free software is a requirement to
114 prevent abuses regarding human rights and environmental care.
115 Humanity can not rely on tools that are in the hands of small group of
118 <p
><strong
>What do you see as the disadvantages of Skolelinux / Debian
119 Edu?
</strong
></p
>
121 <p
>Again, I don
't know this project enough. Maybe a dedicated website?
122 Debian wiki works well for documentation, but is not very appealing to
123 someone discovering the project. Also, as Skolelinux / Debian Edu uses
124 OpenLDAP, it probably means that Windows workstations cannot use
125 centralized authentication. Maybe the project could use Samba as an
126 Active Directory domain controller instead, allowing Windows desktop
127 usage when necessary.
</p
>
129 <p
>(Editors note: In fact Windows workstations can
130 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Buster/HowTo/Samba
">use
131 the centralized authentication in a Debian Edu setup
</a
>, at least for
132 some versions of Windows, but the fact that this is not well known can
133 be seen as an indication of the need for better documentation and
134 marketing. :)
</p
>
136 <p
><strong
>Which free software do you use daily?
</strong
></p
>
138 <p
>Nothing original: Debian testing/sid with Gnome desktop, Firefox,
139 Thunderbird, LibreOffice…
</p
>
141 <p
><strong
>Which strategy do you believe is the right one to use to
142 get schools to use free software?
</strong
></p
>
144 <p
>Every effort to spread free software into schools is important,
145 whatever it is. But I think, at least where I live, that IT
146 professionals maintaining schools networks are still very
"Microsoft
147 centric
". Schools will use any working solution, but they need people
148 to install and maintain it. How to make these professionals sensitive
149 about free software and train them with solutions like Debian Edu /
150 Skolelinux is a really good question :-)
</p
>
155 <title>Jami as a Zoom client, a trick for password protected rooms...
</title>
156 <link>http://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</link>
157 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</guid>
158 <pubDate>Fri,
8 May
2020 13:
30:
00 +
0200</pubDate>
159 <description><p
>Half a year ago,
160 <a href=
"http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
">I
161 wrote
</a
> about
<a href=
"https://jami.net/
">the Jami communication
162 client
</a
>, capable of peer-to-peer encrypted communication. It
163 handle both messages, audio and video. It uses distributed hash
164 tables instead of central infrastructure to connect its users to each
165 other, which in my book is a plus. I mentioned briefly that it could
166 also work as a SIP client, which came in handy when the higher
167 educational sector in Norway started to promote Zoom as its video
168 conferencing solution. I am reluctant to use the official Zoom client
169 software, due to their
<a href=
"https://zoom.us/terms
">copyright
170 license clauses
</a
> prohibiting users to reverse engineer (for example
171 to check the security) and benchmark it, and thus prefer to connect to
172 Zoom meetings with free software clients.
</p
>
174 <p
>Jami worked OK as a SIP client to Zoom as long as there was no
175 password set on the room. The Jami daemon leak memory like crazy
176 (approximately
1 GiB a minute) when I am connected to the video
177 conference, so I had to restart the client every
7-
10 minutes, which
178 is not a great. I tried to get other SIP Linux clients to work
179 without success, so I decided I would have to live with this wart
180 until someone managed to fix the leak in the dring code base. But
181 another problem showed up once the rooms were password protected. I
182 could not get my dial tone signaling through from Jami to Zoom, and
183 dial tone signaling is used to enter the password when connecting to
184 Zoom. I tried a lot of different permutations with my Jami and
185 Asterisk setup to try to figure out why the signaling did not get
186 through, only to finally discover that the fundamental problem seem to
187 be that Zoom is simply not able to receive dial tone signaling when
188 connecting via SIP. There seem to be nothing wrong with the Jami and
189 Asterisk end, it is simply broken in the Zoom end. I got help from a
190 very skilled VoIP engineer figuring out this last part. And being a
191 very skilled engineer, he was also able to locate a solution for me.
192 Or to be exact, a workaround that solve my initial problem of
193 connecting to password protected Zoom rooms using Jami.
</p
>
195 <p
>So, how do you do this, I am sure you are wondering by now. The
197 <a href=
"https://support.zoom.us/hc/en-us/articles/
202405539-H-
323-SIP-Room-Connector-Dial-Strings#sip
">documented
198 from Zoom
</a
>, and it is to modify the SIP address to include the room
199 password. What is most surprising about this is that the
200 automatically generated email from Zoom with instructions on how to
201 connect via SIP do not mention this. The SIP address to use normally
202 consist of the room ID (a number), an @ character and the IP address
203 of the Zoom SIP gateway. But Zoom understand a lot more than just the
204 room ID in front of the at sign. The format is
"<tt
>[Meeting
205 ID].[Password].[Layout].[Host Key]
</tt
>", and you can hear see how you
206 can both enter password, control the layout (full screen, active
207 presence and gallery) and specify the host key to start the meeting.
208 The full SIP address entered into Jami to provide the password will
209 then look like this (all using made up numbers):
</p
>
211 <p
><blockquote
>
212 <tt
>sip:
657837644.522827@
192.168.169.170</tt
>
213 </blockquote
></p
>
215 <p
>Now if only jami would reduce its memory usage, I could even
216 recommend this setup to others. :)
</p
>
218 <p
>As usual, if you use Bitcoin and want to show your support of my
219 activities, please send Bitcoin donations to my address
220 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
225 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software
</title>
226 <link>http://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</link>
227 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</guid>
228 <pubDate>Wed,
29 Apr
2020 13:
10:
00 +
0200</pubDate>
229 <description><p
>The curiosity got the better of me when
230 <a href=
"https://developers.slashdot.org/story/
20/
04/
06/
1424246/new-jersey-desperately-needs-cobol-programmers
">Slashdot
231 reported
</a
> that New Jersey was desperately looking for
232 <a href=
"https://en.wikipedia.org/wiki/COBOL
">COBOL
</a
> programmers,
233 and a few days later it was reported that
234 <a href=
"https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce
">IBM
235 tried to locate COBOL programmers
</a
>.
</p
>
237 <p
>I thus decided to have a look at free software alternatives to
238 learn COBOL, and had the pleasure to find
239 <a href=
"https://sourceforge.net/projects/open-cobol/
">GnuCOBOL
</a
> was
240 already
<a href=
"https://tracker.debian.org/pkg/gnucobol
">in
241 Debian
</a
>. It used to be called Open Cobol, and is a
"compiler
"
242 transforming COBOL code to C or C++ before giving it to GCC or Visual
243 Studio to build binaries.
</p
>
245 <p
>I managed to get in touch with upstream, and was impressed with the
246 quick response, and also was happy to see a new Debian maintainer
247 taking over when the original one recently asked to be replaced. A
248 new Debian upload was done as recently as yesterday.
</p
>
250 <p
>Using the Debian package, I was able to follow a simple COBOL
251 introduction and make and run simple COBOL programs. It was fun to
252 learn a new programming language. If you want to test for yourself,
253 <a href=
"https://en.wikipedia.org/wiki/GnuCOBOL
">the GnuCOBOL Wikipedia
254 page
</a
> have a few simple examples to get you startet.
</p
>
256 <p
>As I do not have much experience with COBOL, I do not know how
257 standard compliant it is, but it claim to pass most tests from COBOL
258 test suite, which sound good to me. It is nice to know it is possible
259 to learn COBOL using software without any usage restrictions, and I am
260 very happy such nice free software project as this is available. If
261 you as me is curious about COBOL, check it out.
</p
>
263 <p
>As usual, if you use Bitcoin and want to show your support of my
264 activities, please send Bitcoin donations to my address
265 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
270 <title>Totalovervåkning av innbyggernes bevegelser - nei takk!
</title>
271 <link>http://people.skolelinux.org/pere/blog/Totaloverv_kning_av_innbyggernes_bevegelser___nei_takk_.html
</link>
272 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Totaloverv_kning_av_innbyggernes_bevegelser___nei_takk_.html
</guid>
273 <pubDate>Thu,
16 Apr
2020 20:
30:
00 +
0200</pubDate>
274 <description><p
>Jeg er blitt spurt hva jeg synes om lansering av smittestopp-appen,
275 overvåkningsløsningen lansert av Folkehelseinstituttet,
276 Simula-senteret og Regjeringen i dag, fulgt av klare trusler fra
277 regjeringen om konsekvenser hvis befolkningen ikke tar den i bruk.
278 Rekker ikke skrive noe fyldig om temaet, men det er klart for meg at
279 den utraderer retten til privatliv samt utgjør en personlig
280 sikkerhetsrisiko for alle som tar den i bruk. Bare det er nok til at
281 det fremstår som en svært dårlig ide å bli med på denne
"dugnaden
".
282 Det finnes andre og bedre tilnærminger enn den valgt av FHI. Har de
283 valgt sin tilnærming for å sikre seg nok et datasett i den fremtidige
284 ehelse-portalen? Potensialet for misbruk av informasjon samlet inn av
285 appen er for stort, effekten på neste krise for klar og gevinsten for
288 <p
>For å si det med forhenværende leder i Datatilsynet, Georg Apenes,
289 som skrev i en kronikk den gang Datatilsynet vernet
291 «
<a href=
"https://www.dagbladet.no/kultur/rent-mel-i-bilen/
66333882">SENTRALT
292 I en liberal forestillingsverden finner vi aksept av borgerens rett
293 til å kunne velge å være i fred; å være u-iakttatt, uregistrert og
294 anonym
</a
>». Det er ikke uten grunn han startet kronikken med
295 «Personvern et fremmedord i enkelte av de statsorganene som samler
296 inn, oppbevarer og bruker personopplysninger». Der har nok
297 statsorganene bare blitt dårligere på
13 år.
</p
>
299 <p
>Det er jo også verdt å merke seg at personvernrådet i EU (EDPB)
300 mener smittestopp-appen
301 <a href=
"https://nrkbeta.no/
2020/
04/
16/personvernrad-i-eu-mener-norsk-app-bryter-med-viktig-personvernprinsipp/
">opererer
302 i strid med prinsippet om dataminimering
</a
>. Også de ser at det
303 finnes mye bedre måter å gjøre dette på.
</p
>
306 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
307 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
309 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
310 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
315 <title>Ny URL til den frie norske stavekontrollen
</title>
316 <link>http://people.skolelinux.org/pere/blog/Ny_URL_til_den_frie_norske_stavekontrollen.html
</link>
317 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ny_URL_til_den_frie_norske_stavekontrollen.html
</guid>
318 <pubDate>Sat,
21 Mar
2020 08:
00:
00 +
0100</pubDate>
319 <description><p
>Det er lenge siden jeg har sett på den norske stavekontrollen, sist
320 jeg skrev om temaet var i
2016, og i mellomtiden har nettstedet
321 no.speling.org forsvunnet, og både git-depotet på Alioth og
322 mailman-tjenesten som hadde epostlistene for oversettelser blitt lagt
323 ned. Men bokmål og nynorsk trenger fortsatt stavekontroll, så etter
324 et par purringer fra en som har lyst til å forbedre stavekontrollen
325 har jeg endelig fått lagt ut ny offentlig kopi av git-depotet. Jeg
326 valgte gitlab foran github.. Siste utgave av stavekontrollen kan
328 <a href=
"https://gitlab.com/norwegian-language-tools/spell-norwegian
">https://gitlab.com/norwegian-language-tools/spell-norwegian
</a
>.
329 Ingen ny versjon i denne omgang altså, bare et nytt sted å samle
330 forbedringer til den frie norske stavekontrollen. :)
332 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
333 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
335 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
336 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
341 <title>Nikita version
0.5 released - updated free software archive API server
</title>
342 <link>http://people.skolelinux.org/pere/blog/Nikita_version_0_5_released___updated_free_software_archive_API_server.html
</link>
343 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Nikita_version_0_5_released___updated_free_software_archive_API_server.html
</guid>
344 <pubDate>Mon,
2 Mar
2020 19:
00:
00 +
0100</pubDate>
345 <description><p
>Today, after many months of development, a new release of
346 <ahref=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core/
">Nikita
347 Noark
5 core project
</a
> was finally
348 <ahref=
"https://lists.nuug.no/pipermail/nikita-noark/
2020-March/
000519.html
">announced
349 on the project mailing list
</a
>. The Nikita free software solution is
350 an implementation of the Norwegian archive standard Noark
5 used by
351 government offices in Norway. These were the changes in version
0.5
352 since version
0.4, see the email link above for links to a demo
357 <li
>Updated to Noark
5 versjon
5.0 API specification.
359 <li
>Changed formatting of _links from [] to {} to match IETF draft
360 on JSON HAL.
</li
>
361 <li
>Merged Registrering og Basisregistrering in version
4 to
362 combined Registrering.
</li
>
363 <li
>DokumentObjekt is now subtype of ArkivEnhet.
</li
>
364 <li
>Introducing new entity Arkivnotat.
</li
>
365 <li
>Changed all relation keys to use /v5/ instead of /v4/.
</li
>
366 <li
>Corrected to use new official relation keys when possible.
</li
>
367 <li
>Renamed Sakspart to Part and connect it to Mappe, Registrering
368 and Dokumentbeskrivelse instead of only Saksmappe.
</li
>
369 <li
>Moved Korrespondansepart connection from Journalpost to
370 Registrering.
</li
>
371 <li
>Moved Part and Korrespondansepart from package sakarkiv to
372 arkivstruktur.
</li
>
373 <li
>Renamed presedensstatus to presedensStatus.
</li
>
374 <li
>Use new JSON content-type
"application/vnd.noark5+json
".
</li
>
375 <li
>Updated prepopulated format list to use PRONOM codes.
</li
>
376 <li
>Implemented endpoint for system information.
</li
>
377 <li
>Implemented national identifiers for both file and record.
</li
>
378 <li
>Implemented comments.
</li
>
379 <li
>implemented sign off.
</li
>
380 <li
>implemented conversion.
</li
>
381 </ul
></li
>
382 <li
>Improved/implemented OData search and paging support for more entities.
</li
>
383 <li
>No longer exposes attribute Dokumentobjekt.referanseDokumentfil,
384 one should use the relation in _links instead.
</li
>
385 <li
>Corrected relation keys under
386 https://rel.arkivverket.no/noark5/v5/api/administrasjon/, replacing
387 'administrasjon
' with
'admin
'.
</li
>
388 <li
>Fixed several security and stability issues discovered by Coverity.
</li
>
389 <li
>Corrected handling ETag errors, now return code
409.
</li
>
390 <li
>Improved handling of Kryssreferanse.
</li
>
391 <li
>Changed internal database model to use UUID/SystemID as primary keys
392 in tables.
</li
>
393 <li
>Changed internal database table names to use package prefix.
</li
>
394 <li
>Changed time zone handling for date and datetime attributes, to be
395 more according to the new definition in the API specification.
</li
>
396 <li
>Change revoke-token to only drop token on POST requests, not GET.
</li
>
397 <li
>Updated to newer Spring version.
</li
>
398 <li
>Changed primary key and URL component for metadata code lists to
399 use the
'kode
' value instead of a SystemID.
</li
>
400 <li
>Corrected implementation of Part and Sakspart.
</li
>
401 <li
>Changed instance lists with subtypes (like .../registrering/ and
402 .../mappe/) to include the attributes and _links entries for the
403 subtype in the supertype lists.
</li
>
404 <li
>Adjusted _links relations to make it possible to figure out the
405 entity of an instance using the self-
>href-
>relation key lookup
407 <li
>Fixed several end points to make sure GET, PUT, POST and DELETE
408 match each other.
</li
>
409 <li
>Updated DELETE endpoints to work with UUID based entity
410 identifiers.
</li
>
411 <li
>Restructured code to use more common URL related constants in entry
412 point values and replace @RequestMapping with method specific
413 annotations.
</li
>
414 <li
>Added first unit test code.
</li
>
415 <li
>Updated web GUI to work with the updated API.
</li
>
416 <li
>Changed integer fields, enforce them as numeric.
</li
>
417 <li
>Rewrote and simplify metadata handling to use common service and
418 controller code instead of duplicating for each type.
</li
>
419 <li
>Implemented the remaining metadata types.
</li
>
420 <li
>Changed Country list source from Wikipedia to Debian iso-codes and
421 updated the list of Countries.
</li
>
422 <li
>Many many corrections and improvements.
</li
>
426 <p
>If free and open standardized archiving API sound interesting to
427 you, please contact us on IRC
428 (
<a href=
"irc://irc.freenode.net/%
23nikita
">#nikita on
429 irc.freenode.net
</a
>) or email
430 (
<a href=
"https://lists.nuug.no/mailman/listinfo/nikita-noark
">nikita-noark
431 mailing list
</a
>).
</p
>
433 <p
>As usual, if you use Bitcoin and want to show your support of my
434 activities, please send Bitcoin donations to my address
435 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
440 <title>Blockchain and IoT articles accepted into Records Management Journal
</title>
441 <link>http://people.skolelinux.org/pere/blog/Blockchain_and_IoT_articles_accepted_into_Records_Management_Journal.html
</link>
442 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Blockchain_and_IoT_articles_accepted_into_Records_Management_Journal.html
</guid>
443 <pubDate>Thu,
27 Feb
2020 09:
05:
00 +
0100</pubDate>
444 <description><p
>On Tuesday, two scietific articles we have been working on for a
445 while, was finally accepted for publication into
446 <a href=
"https://www.emerald.com/insight/publication/issn/
0956-
5698">Records
447 Management Journal
</a
>. Still waiting for the assigned DOI urls to
448 start working, but you can have a look at the LaTeX originals here.
</p
>
450 <p
>The first article is
451 "<a href=
"http://people.skolelinux.org/pere/blog/images/
2020-
02-
25-rmj-iot-record-keeping.pdf
">A
452 record-keeping approach to managing IoT-data for government
453 agencies
</a
>" (
<a href=
"https://doi.org/
10.1108/RMJ-
09-
2019-
0050">DOI
454 10.1108/RMJ-
09-
2019-
0050<a/
>) by Thomas Sødring, Petter Reinholdtsen
455 and David Massey, and sketches some approaches for storing measurement
456 data (aka Internet of Things sensor data) in a archive, thus providing
457 a well defined mechanism for screening and deletion of the information
</p
>
459 <p
>The second article is
460 "<a href=
"http://people.skolelinux.org/pere/blog/images/
2020-
02-
25-rmj-block-chain-record-keeping.pdf
">Publishing
461 and using record-keeping structural information in a blockchain
</a
>"
462 (
<a href=
"https://doi.org/
10.1108/RMJ-
09-
2019-
0056">DOI
463 10.1108/RMJ-
09-
2019-
0056</a
>) by Thomas Sødring, Petter Reinholdtsen
464 and Svein Ølnes, where we describe a way for third parties to validate
465 authenticity and thus improve trust in the records kept in a
468 <p
>As usual, if you use Bitcoin and want to show your support of my
469 activities, please send Bitcoin donations to my address
470 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
472 <p
><strong
>Update
2020-
04-
26</strong
>: Initially managed to swap the
473 DOI numbers. Fixed it.
</p
>
478 <title>Redaksjon på plass for Noark
5 tjenestegrensesnitt
</title>
479 <link>http://people.skolelinux.org/pere/blog/Redaksjon_p__plass_for_Noark_5_tjenestegrensesnitt.html
</link>
480 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Redaksjon_p__plass_for_Noark_5_tjenestegrensesnitt.html
</guid>
481 <pubDate>Wed,
5 Feb
2020 14:
45:
00 +
0100</pubDate>
482 <description><p
>Arbeidet med å lage et godt, fritt og åpent standardisert maskinelt
483 grensesnitt for arkivering, med tilhørende fri
484 programvareimplementasjon fortsetter. Jeg snakker om
485 <a href=
"https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard
">Noark
486 5 Tjenestegrensesnitt
</a
> og
487 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core/
">Nikita
</a
>.
489 <a href=
"https://www.nuug.no/aktiviteter/
20200127-noark-seminar/
">seminaret
490 for noen dager siden
</a
>, er vi i Nikita-prosjektet har fått beskjed
491 fra Arkivverket at det blir satt ned en redaksjon for å videreutvikle
492 spesifikasjonen. Redaksjonen består av Mona Danielsen og Anne Sofie
493 Knutsen ved arkivverket, Thomas Sødring ved OsloMet, og meg selv fra
494 NUUG. De to sistenevnte tar seg av de åpenbare forbedringene, mens
495 hele redaksjonen diskuterer tvilstilfeller. Jeg håper dette vil bidra
496 til at vi lykkes i å gjøre denne protokollspesifikasjonen så entydig
497 og klar at den vil bidra til et velfungerende marked for
498 arkivsystemer, og sikre at programmer som trenger å snakke med
499 arkivsystemet kan snakke med enhver implementasjon av
500 API-spesifikasjonen. Nikita er den første implementasjonen, men det
501 bør blir flere.
</p
>
503 <p
>Det gjenstår riktig nok endel før vi er i mål, selv om svært mye
504 allerede er på plass. Med innspill og forslag til forbedringer fra
505 alle som vil ha et leverandøruavhengig og fullstendig
506 datamaskinlesbart grensesnitt til arkivet, så tror jeg vi vil
509 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
510 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
512 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
513 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
518 <title>Artikkel om Noark
5 Tjenestegrensesnitt og Nikita i Arkivråd nummer
3 for
2019</title>
519 <link>http://people.skolelinux.org/pere/blog/Artikkel_om_Noark_5_Tjenestegrensesnitt_og_Nikita_i_Arkivr_d_nummer_3_for_2019.html
</link>
520 <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>
521 <pubDate>Thu,
26 Dec
2019 08:
00:
00 +
0100</pubDate>
522 <description><p
>Like før julaften ble en artikkel jeg har skrevet om vedlikehold av
523 <a href=
"https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard
">Noark
524 5 Tjenestegrensesnitt
</a
> og Nikita publisert i
<a
525 href=
"https://www.arkivrad.no/arkivrad
">tidsskriftet Arkivråd
</a
>.
527 <a href=
"http://people.skolelinux.org/pere/blog/_pen_og_gjennomsiktig_vedlikehold_av_spesifikasjonen_for_Noark_5_Tjenestegrensesnitt.html
">min bloggpost
528 om samme tema
</a
> som ble publisert
2019-
03-
11. Jeg oppdaget nettopp
529 at nettsiden til tidsskriftet Arkivråd er oppdatert med siste utgave,
530 og artikkelen dermed er tilgjengelig for alle. Du finner den i
531 <a href=
"https://www.arkivrad.no/sites/arkivrad/files/arkivrad_03_2019_nett.pdf
">PDF-en
532 til nummer
2019/
3 på side
30-
33</a
>. Jeg håper leserne av
533 tidsskriftet får lyst til å sjekke ut tjenestegrensesnittet og at
534 artikkelen vil gjøre det enklere for flere å bidra til en enda bedre,
535 klarere og mer entydig API-spesifikasjon. Det kan gjøre at
536 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core/
">arkivsystemet
537 Nikita
</a
> kan bli enda bedre når spesifikasjonen forbedres.
</p
>
539 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
540 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
542 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
543 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>