<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>Nikita version 0.6 released - free software archive API server</title>
+ <link>http://people.skolelinux.org/pere/blog/Nikita_version_0_6_released___free_software_archive_API_server.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nikita_version_0_6_released___free_software_archive_API_server.html</guid>
+ <pubDate>Thu, 10 Jun 2021 17:10:00 +0200</pubDate>
+ <description><p>I am very pleased to be able to share with you
+<a href="https://lists.nuug.no/pipermail/nikita-noark/2021-June/000576.html">the
+announcement of a new version of the archiving system Nikita</a>
+published by its lead developer Thomas Sødring:</p>
+
+<p><blockquote>
+
+<p>It is with great pleasure that we can announce a new release of
+nikita. Version 0.6
+(<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core">https://gitlab.com/OsloMet-ABI/nikita-noark5-core</a>). This
+release makes new record keeping functionality available. This really
+is a maturity release. Both in terms of functionality but also code.
+Considerable effort has gone into refactoring the codebase and
+simplifying the code. Notable changes for this release include:</p>
+
+<ul>
+
+ <li>Significantly improved OData parsing</li>
+ <li>Support for business specific metadata and national identifiers</li>
+ <li>Continued implementation of domain model and endpoints</li>
+ <li>Improved testing</li>
+ <li>Ability to export and import from arkivstruktur.xml</li>
+
+</ul>
+
+<p>We are currently in the process of reaching an agreement with an
+archive institution to publish their picture archive using nikita with
+business specific metadata and we hope that we can share this with you
+soon. This is an interesting project as it allows the organisation to
+bring an older picture archive back to life while using the original
+metadata values stored as business specific metadata. Combined with
+OData means the scope and use of the archive is significantly
+increased and will showcase both the flexibility and power of
+Noark.</p>
+
+<p>I really think we are approaching a version 1.0 of nikita, even
+though there is still a lot of work to be done. The notable work at
+the moment is to implement access-control and full text indexing of
+documents.</p>
+
+<p>My sincere thanks to everyone who has contributed to this
+release!</p>
+
+<p>- Thomas</p>
+
+<p><strong>Release 0.6 2021-06-10 (d1ba5fc7e8bad0cfdce45ac20354b19d10ebbc7b)</strong></p>
+
+<ul>
+
+ <li>Refactor metadata entity search</li>
+ <li>Remove redundant security configuration</li>
+ <li>Make OpenAPI documentation work</li>
+ <li>Change database structure / inheritance model to a more sensible approach</li>
+ <li>Make it possible to move entities around the fonds structure</li>
+ <li>Implemented a number of missing endpoints</li>
+ <li>Make sure yml files are in sync</li>
+ <li>Implemented/finalised storing and use of
+ <ul>
+ <li>Business Specific Metadata</li>
+ <li>Norwegian National Identifiers</li>
+ <li>Cross Reference</li>
+ <li>Keyword</li>
+ <li>StorageLocation</li>
+ <li>Author</li>
+ <li>Screening for relevant objects</li>
+ <li>ChangeLog</li>
+ <li>EventLog</li>
+ </ul></li>
+ <li>Make generation of updated docker image part of successful CI pipeline</li>
+ <li>Implement pagination for all list requests
+ <ul>
+ <li>Refactor code to support lists</li>
+ <li>Refactor code for readability</li>
+ <li>Standardise the controller/service code</li>
+ </ul></li>
+ <li>Finalise File->CaseFile expansion and Record->registryEntry/recordNote
+expansion</li>
+ <li>Improved Continuous Integration (CI) approach via gitlab</li>
+ <li>Changed conversion approach to generate tagged PDF documents</li>
+ <li>Updated dependencies
+ <ul>
+ <li>For security reasons</li>
+ <li>Brought codebase to spring-boot version 2.5.0</li>
+ <li>Remove import of necessary dependencies</li>
+ <li>Remove non-used metrics classes</li>
+ </ul></li>
+ <li>Added new analysis to CI including</li>
+ <li>Implemented storing of Keyword</li>
+ <li>Implemented storing of Screening and ScreeningMetadata</li>
+ <li>Improved OData support
+ <ul>
+ <li>Better support for inheritance in queries where applicable</li>
+ <li>Brought in more OData tests</li>
+ <li>Improved OData/hibernate understanding of queries</li>
+ <li>Implement $count, $orderby</li>
+ <li>Finalise $top and $skip</li>
+ <li>Make sure & is used between query parameters</li>
+ </ul></li>
+ <li>Improved Testing in codebase
+ <ul>
+ <li>A new approach for integration tests to make test more readable</li>
+ <li>Introduce tests in parallel with code development for TDD approach</li>
+ <li>Remove test that required particular access to storage</li>
+ </ul></li>
+ <li>Implement case-handling process from received email to case-handler
+ <ul>
+ <li>Develop required GUI elements (digital postroom from email)</li>
+ <li>Introduced leader, quality control and postroom roles</li>
+ </ul></li>
+ <li>Make PUT requests return 200 OK not 201 CREATED</li>
+ <li>Make DELETE requests return 204 NO CONTENT not 200 OK</li>
+ <li>Replaced 'oppdatert*' with 'endret*' everywhere to match latest spec</li>
+ <li>Upgrade Gitlab CI to use python > 3 for CI scripts</li>
+ <li>Bug fixes
+ <ul>
+ <li>Fix missing ALLOW</li>
+ <li>Fix reading of objects from jar file during start-up</li>
+ <li>Reduce the number of warnings in the codebase</li>
+ <li>Fix delete problems</li>
+ <li>Make better use of cascade for "leaf" objects</li>
+ <li>Add missing annotations where relevant</li>
+ <li>Remove the use of ETAG for delete</li>
+ <li>Fix missing/wrong/broken rels discovered by runtest</li>
+ <li>Drop unofficial convertFil (konverterFil) end point</li>
+ <li>Fix regex problem for dateTime</li>
+ <li>Fix multiple static analysis issues discovered by coverity</li>
+ <li>Fix proxy problem when looking for object class names</li>
+ <li>Add many missing translated Norwegian to English (internal)
+attribute/entity names</li>
+ <li>Change UUID generation approach to allow code also set a value</li>
+ <li>Fix problem with Part/PartParson</li>
+ <li>Fix problem with empty OData search results</li>
+ <li>Fix metadata entity domain problem</li>
+ </ul></li>
+ <li>General Improvements
+ <ul>
+ <li>Makes future refactoring easier as coupling is reduced</li>
+ <li>Allow some constant variables to be set from property file</li>
+ <li>Refactor code to make reflection work better across codebase</li>
+ <li>Reduce the number of @Service layer classes used in @Controller
+classes</li>
+ <li>Be more consistent on naming of similar variable types</li>
+ <li>Start printing rels/href if they are applicable</li>
+ <li>Cleaner / standardised approach to deleting objects</li>
+ <li>Avoid concatenation when using StringBuilder</li>
+ <li>Consolidate code to avoid duplication</li>
+ <li>Tidy formatting for a more consistent reading style across
+similar class files</li>
+ <li>Make throw a log.error message not an log.info message</li>
+ <li>Make throw print the log value rather than printing in multiple
+places</li>
+ <li>Add some missing pronom codes</li>
+ <li>Fix time formatting issue in Gitlab CI</li>
+ <li>Remove stale / unused code</li>
+ <li>Use only UUID datatype rather than combination String/UUID for systemID</li>
+ <li>Mark variables final and @NotNull where relevant to indicate
+intention</li>
+ </ul></li>
+ <li>Change Date values to DateTime to maintain compliance with Noark 5
+standard</li>
+ <li>Domain model improvements using Hypersistence Optimizer
+ <ul>
+ <li>Move @Transactional from class to methods to avoid borrowing the JDBC Connection unnecessarily</li>
+ <li>Fix OneToOne performance issues</li>
+ <li>Fix ManyToMany performance issues</li>
+ <li>Add missing bidirectional synchronization support</li>
+ <li>Fix ManyToMany performance issue</li>
+ </ul></li>
+ <li>Make List<> and Set<> use final-keyword to avoid potential problems
+during update operations</li>
+ <li>Changed internal URLs, replaced "hateoas-api" with "api".</li>
+ <li>Implemented storing of Precedence.</li>
+ <li>Corrected handling of screening.</li>
+ <li>Corrected _links collection returned for list of mixed entity types
+to match the specific entity.</li>
+ <li>Improved several internal structures.</li>
+</ul>
+
+</blockquote></p>
+
+<p>If free and open standardized archiving API sound interesting to
+you, please contact us on IRC
+(<a href="irc://irc.oftc.net/%23nikita">#nikita on
+irc.oftc.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
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+</description>
+ </item>
+
+ <item>
+ <title>VLC bittorrent plugin in Bullseye, saved by the bell?</title>
+ <link>http://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_in_Bullseye__saved_by_the_bell_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_in_Bullseye__saved_by_the_bell_.html</guid>
+ <pubDate>Sat, 1 May 2021 11:00:00 +0200</pubDate>
+ <description><p>Yesterday morning I got a warning call from the Debian quality
+control system that
+<a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">the VLC
+bittorrent plugin</a> was due to be removed because of a release
+critical bug in one of its dependencies. As you might remember, this
+plugin make VLC able to stream videos directly from a bittorrent
+source using both torrent files and magnet links, similar to using a
+HTTP source. I believe such protocol support is a vital feature in
+VLC, allowing efficient streaming from sources such at the almost 7
+million movies in <a href="https://archive.org/">the Internet
+Archive</a>.</p>
+
+<p>The dependency was the unmaintained
+<a href="https://tracker.debian.org/pkg/libtorrent-rasterbar">libtorrent-rasterbar</a>
+package, and <a href="https://bugs.debian.org/987306">the bug in
+question</a> blocked its python library from working properly. As I
+did not want Bullseye to release without bittorrent support in VLC, I
+set out to check out the status, and track down a fix for the problem.
+Luckily the issue had already been identified and fixed upstream,
+providing everything needed. All I needed to do was to fetch the
+Debian git repository, extract and trim the patch from upstream and
+apply it to the Debian package for upload.</p>
+
+<p>The fixed library was uploaded yesterday evening. But that is not
+enough to get it into Bullseye, as Debian is currently in package
+freeze to prepare for a new next stable release. Only non-critical
+packages with
+<a href="https://wiki.debian.org/ContinuousIntegration/autopkgtest">autopkgtest
+setup</a> included, in other words able to validate automatically that
+the package is working, are allowed to migrate automatically into the
+next release at this stage. And the unmaintained libtorrent-rasterbar
+lack such testing, and thus needed a manual override. I am happy to
+report that such manual override was approved a few minutes ago, thus
+increasing significantly the chance of VLC bittorrent streaming being
+available out of the box also for Debian/Buster users. A bit too
+close shave for my liking, as the Bullseye release is most likely just
+a few days away, and this did feel like the package was saved by the
+bell. I am so glad the warning email showed up in time for me to
+handle the issue, and a big thanks go to the Debian Release team for
+the quick feedback on
+<a href="irc://irc.debian.org/%23debian-release">#debian-release</a>
+and their <a href="https://bugs.debian.org/987865">swift
+unblocking</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
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Updated Valutakrambod, now also with information from NBX</title>
+ <link>http://people.skolelinux.org/pere/blog/Updated_Valutakrambod__now_also_with_information_from_NBX.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Updated_Valutakrambod__now_also_with_information_from_NBX.html</guid>
+ <pubDate>Sat, 27 Feb 2021 13:30:00 +0100</pubDate>
+ <description><p>I have neglected the Valutakrambod library for a while, but decided
+this weekend to give it a face lift. I fixed a few minor glitches in
+several of the service drivers, where the API had changed since I last
+looked at the code. I also added support for fetching the order book
+from the newcomer Norwegian Bitcoin Exchange.</p>
+
+<p>I also decided to migrate the project from github to gitlab in the
+process. If you want a python library for talking to various currency
+exchanges, check out
+<a href="https://gitlab.com/petterreinholdtsen/valutakrambod">code for
+valutakrambod</a>.</p>
+
+<p>This is what the output from '<tt>bin/btc-rates-curses -c</tt>'
+looked like a few minutes ago:</p>
+
+<p><blockquote><pre>
+ Name Pair Bid Ask Spread Ftcd Age Freq
+ Bitfinex BTCEUR 39229.0000 39246.0000 0.0% 44 44 nan
+ Bitmynt BTCEUR 39071.0000 41048.9000 4.8% 43 74 nan
+ Bitpay BTCEUR 39326.7000 nan nan% 39 nan nan
+ Bitstamp BTCEUR 39398.7900 39417.3200 0.0% 0 0 1
+ Bl3p BTCEUR 39158.7800 39581.9000 1.1% 0 nan 3
+ Coinbase BTCEUR 39197.3100 39621.9300 1.1% 38 nan nan
+ Kraken+BTCEUR 39432.9000 39433.0000 0.0% 0 0 0
+ Paymium BTCEUR 39437.2100 39499.9300 0.2% 0 2264 nan
+ Bitmynt BTCNOK 409750.9600 420516.8500 2.6% 43 74 nan
+ Bitpay BTCNOK 410332.4000 nan nan% 39 nan nan
+ Coinbase BTCNOK 408675.7300 412813.7900 1.0% 38 nan nan
+ MiraiEx BTCNOK 412174.1800 418396.1500 1.5% 34 nan nan
+ NBX BTCNOK 405835.9000 408921.4300 0.8% 33 nan nan
+ Bitfinex BTCUSD 47341.0000 47355.0000 0.0% 44 53 nan
+ Bitpay BTCUSD 47388.5100 nan nan% 39 nan nan
+ Coinbase BTCUSD 47153.6500 47651.3700 1.0% 37 nan nan
+ Gemini BTCUSD 47416.0900 47439.0500 0.0% 36 336 nan
+ Hitbtc BTCUSD 47429.9900 47386.7400 -0.1% 0 0 0
+ Kraken+BTCUSD 47401.7000 47401.8000 0.0% 0 0 0
+ Exchangerates EURNOK 10.4012 10.4012 0.0% 38 76236 nan
+ Norgesbank EURNOK 10.4012 10.4012 0.0% 31 76236 nan
+ Bitstamp EURUSD 1.2030 1.2045 0.1% 2 2 1
+ Exchangerates EURUSD 1.2121 1.2121 0.0% 38 76236 nan
+ Norgesbank USDNOK 8.5811 8.5811 0.0% 31 76236 nan
+</pre></blockquote></p>
+
+<p>Yes, I notice the negative spread on Hitbtc. Either I fail to
+understand their Websocket API or they are sending bogus data. I've
+seen the same with Kraken, and suspect there is something wrong with
+the data they send.</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>
+</description>
+ </item>
+
+ <item>
+ <title>Boken «Hvordan knuse overvåkningskapitalismen» lanseres på norsk</title>
+ <link>http://people.skolelinux.org/pere/blog/Boken__Hvordan_knuse_overv_kningskapitalismen__lanseres_p__norsk.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Boken__Hvordan_knuse_overv_kningskapitalismen__lanseres_p__norsk.html</guid>
+ <pubDate>Tue, 26 Jan 2021 19:10:00 +0100</pubDate>
+ <description><p>Etter intenst arbeid over mange måneder er endelig den norske
+utgaven av «Hvordan knuse overvåkningskapitalismen» av Cory Doctorow
+ferdig og klar til å glede millioner av lesere over hele verden.
+Følgende pressemelding ble nettopp sendt ut til norske redaksjoner:
+
+<blockquote>
+
+<p><strong>Hva gjør stordata med oss, og hvordan gjør algoritmene
+«fake news» til realiter?</strong></p>
+
+<p>Nå foreligger en viktig bok om temaet også på norsk. Boken klargjør
+og foreslår hvordan vi selv som enkeltpersoner, men også nasjonalt og
+internasjonalt kan bekjempe stordatakonsentrasjonene;
+«overvåkingskapitalismen». Boken er «Hvordan knuse
+overvåkingskapitalismen» av dr. Cory Doctorow. Den engelske
+bokutgivelsen kom for noen dager siden og lanseres med et Webinar
+torsdag 2021-01-28. Doctorow besøkte Norge og NUUG i desember med sin
+presentasjon Monopoly, Not Mind Control: What's Really Happening With
+"Surveillance Capitalism".</p>
+
+<p>I funn etter funn, eksempel etter eksempel, gjennomgår og
+analyserer dr. Doctorow de utfordringer vi møter i større og større
+omfang. Ikke bare i USA, men også her hjemme.</p>
+
+<p>Cory Doctorow er en britisk-kanadisk forfatter, journalist og
+aktivist, kjent for sine science fiction-romaner, for arbeidet for
+Creative Commons-bevegelsen, og for sine bidrag til reform av
+opphavsretten. Han er både æresdoktor og gjesteforeleser i
+datavitenskap ved Open University i UK, konsulent for Electronic
+Frontier Foundation, og godt kjent for innsiktsfullt å kommentere og
+skrive om digital utvikling.</p>
+
+<p>Boken lanseres nå på norsk, både som ebok og på papir, oversatt av
+en dugnadsgjeng ledet av Petter Reinholdtsen.</p>
+
+<p>Boken reiser noen helt grunnleggende og samfunnskritiske spørsmål:
+Hva fører det til når store deler av Internettet domineres av få store
+aktører og deres styringsverktøy og algoritmer?</p>
+
+<p>Som individer bør vi være opptatt at grenser blir satt og håndhevet
+- grenser for overvåkning av individet, for utøvelse av kommersiell
+og politisk påvirkning, og for monopoldannelser i
+dataverdenen. Slik grensesetting styrker personvernet.</p>
+
+<p>Konkurransetilsynet har ansvaret for at konkurranselovens § 11 skal
+forby «et dominerende foretak for utilbørlig å utnytte og misbruke
+sin dominerende stilling». Et tilsvarende forbud omfattes også av
+EØS-avtalens artikkel 54. Boken går i detalj om serien av
+innskrenkninger vi møter i valgfriheten, innskrenkninger som denne
+lovgivningen nettopp skal forhindre. Håndhevelse av en slik lovgivning
+er også til fordel for mindre næringsdrivende som uten dette får
+begrenset sine faktiske eller potensielle muligheter for vekst og
+etablering. «Slik atferd kan utgjøre et misbruk og kan ta ulike
+former», skriver Konkurransetilsynet.</p>
+
+<p>Cory Doctorow går i sin bok lengre enn det med sine mange eksempler
+på forhold det burde vært grepet inn mot.</p>
+
+<p>«Boken bør bidra til et sterkere engasjemen fra voktere av
+Internettet nasjonalt og internasjonalt - EU medregnet» sier
+oversetter Ole-Erik Yrvin og fortsetter: «Vi har derfor
+<a href="http://people.skolelinux.org/pere/blog/images/2021-01-26-knus-overvaakningskapitalismen-helleland.pdf">allerede
+tatt opp bokens forslag</a> direkte med Distrikts- og
+digitaliseringsminister Linda Hofstad Helleland (H) og
+Konkurransetilsynet slik at de kan følges opp.»</p>
+
+<p>«Også Norge bør innta en pådriverrolle i denne utviklingen», sier
+Petter Reinholdtsen. «Tiden er knapp, og tilsynsmyndighetene må få
+de verktøy og de ressurser de trenger for at vi her hjemme skal oppnå
+nødvendige resultater. Dette gjelder ikke bare vår egen generasjon;
+det gjelder alle generasjoner fremover», avslutter Petter
+Reinholdsen.</p>
+
+<p>Kontaktinformasjon:</p>
+
+<ul>
+
+<li>Ole-Erik Yrvin, oeyrvin (at) gmail.com, +47 46500450</li>
+
+<li>Petter Reinholdtsen, pere (at) hungry.com</li>
+
+</ul>
+
+<p>Relevante lenker:<p>
+
+<ul>
+
+<li>«Hvordan knuse overvåkingskapitalismen» kan bestilles på papir,
+som ebok eller leses på nett via
+<a href="http://www.hungry.com/~pere/publisher/">http://www.hungry.com/~pere/publisher/</a>.</li>
+
+<li>Opptak av NUUG-møtet Monopoly, Not Mind Control: What's Really
+Happening With "Surveillance Capitalism" med Cory Doctorow,
+<a href="https://www.nuug.no/aktiviteter/20201208-doctorow/">https://www.nuug.no/aktiviteter/20201208-doctorow/</a>.</li>
+
+<li>Påmelding til webinar som lanserer den engelske utgaven kan gjøres
+via
+<a href="https://craphound.com/category/destroy/">https://craphound.com/category/destroy/</a>.</li>
+
+<li>Cory Doctorows nettsted er
+<a href="https://craphound.com/">https://craphound.com/</a>.</li>
+
+</ul>
+
+</blockquote>
+
+<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>Latest Jami back in Debian Testing, and scriptable using dbus</title>
<link>http://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</link>
<p>I recommend you check out this simple and powerful approach to more
secure network connections. :)</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>
-</description>
- </item>
-
- <item>
- <title>Bompenge-Norge, med noen tall fra bompengekalkulator</title>
- <link>http://people.skolelinux.org/pere/blog/Bompenge_Norge__med_noen_tall_fra_bompengekalkulator.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bompenge_Norge__med_noen_tall_fra_bompengekalkulator.html</guid>
- <pubDate>Mon, 1 Jun 2020 14:50:00 +0200</pubDate>
- <description><p>Det er tett med sensorstasjoner langs veinettet i Norge, som
-registrerer hvilke kjøretøy som passerer eller tar bilde av de som
-drar forbi. I følge
-<a href="https://vegkart.atlas.vegvesen.no/">Vegvesenets nasjonale
-veidatabank (NVDB)</a>, er det 353 bomstasjoner langs det norske
-veinettet. 21 i nordnorge, 48 i trøndelagsområdet, 13 på
-nordvestlandet, 91 i bergenstraktene og 180 på østlandsområdet. I
-tillegg finnes det et utall overvåkningskamera og noen titalls
-RFID-avlesere for bompengebrikker som samler inn informasjon om hvilke
-biler som befinner seg hvor i landet. For ikke å glemme alle
-mobilbasestasjoner som registrerer hvor brukere av mobilnettverket
-befinner seg. De er ikke tema i dag.</p>
-
-<p>De som kjører mye har interesse av å vite hvor mye bompenger det vil
-koste å kjøre fra et sted til et annet, og dette behovet har aktørene
-bak <a href="https://bompengekalkulator.no/">Bompengekalkulatoren</a>
-tatt sikte på å tilby i markedet. Fornuftig nok har de også en
-gratistjeneste, slik at de får frivillige til å gi innspill om feil i
-datagrunnlaget. Jeg ble nylig nysgjerring på hvor mye det til koste å
-kjøre på kryss og tvers i Norge, og valgte meg ut en teststrekning fra
-Oslo til Tromsø for å se hvilke beløp som gjelder.</p>
-
-<p>Bompengekalkulatoren viser frem flere rutealternativer for et gitt
-reisesøk, og i dette tilfellet, for reise fra Oslo Sentralstasjon til
-Tromsø sentrum, viser den tre alternativ. Merk, disse tallene gjelder
-bensindrevet personbil. En kan velge takstkategori i
-webgrensesnittet. Det ene rutealternativet er E6 gjennom Norge, de to
-andre er E45 og E4 gjennom sverige. E45 er innlandsruten i Sverige,
-motorvei gjennom store skoger som i følge kalkulatoren skal ta 22
-timer og 26 minutter med norsk bompengebeløp på 164 kroner. Jeg har
-mine tvil til om datasettet til Bompengekalkulatoren har svenske
-bomstasjoner, så ta dette beløpet med en klype salt. E4 er veien
-langs Bottenviken og mer befolket område, og skal ta 22 timer og 50
-minutter til en norsk bompengebeløp på 71 kroner. Den norske ruten
-langs E6 skal derimot ta 23 timer og 16 minutter og beløpe seg til 664
-kroner. Beløpene er uten autopass-brikke, slik at en slipper å få
-bilens posisjon registrert i alle bompengebrikkeavleserne som ikke
-også er bomstasjoner. For trailere er bompengekostnaden 2-3 ganger så
-høy som for personbil. I tillegg til pengebeløpet, som faktureres
-etterskuddsvis og de siste årene har blitt umulig å gjøre opp kontant
-på stedet, så kommer kostnaden med å få sine personopplysninger samlet
-inn, lagret og gjort tilgjengelig for fremmede på ubestemt tid. Jeg
-ser på den kostnaden som mye høyere en pengebeløpet som
-faktureres.</p>
-
-<p>For en tilsvarende tur fra Oslo til Bergen, så forteller
-kalkulatoren at raskeste vei er riksvei 7 på 7 timer 4 minutter med
-bompengebeløp 409 kroner. Alternativene listet opp er E134 på 8 timer
-37 minutter med bompengebeløp 318 kroner og fylkesivei 40 på 7 timer
-30 minutter med beløp 331. Det kan kanskje være greit å sjekke ut før
-en setter seg i bilen hvor ens personopplysninger vil bli samlet inn
-og lagret 5 fem år, når en velger hvilken rute en går for.</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>More reliable vlc bittorrent plugin in Debian (version 2.9)</title>
- <link>http://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html</guid>
- <pubDate>Sun, 24 May 2020 17:00:00 +0200</pubDate>
- <description><p>I am very happy to report that a more reliable
-<a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">VLC
-bittorrent plugin</a> was just uploaded into debian. This fixes a
-couple of crash bugs in the plugin, hopefully making the VLC
-experience even better when streaming directly from a bittorrent
-source. The package is currently in Debian unstable, but should be
-available in Debian testing in two days. To test it, simply install
-it like this:</p>
-
-<p><pre>
-apt install vlc-plugin-bittorrent
-</pre></p>
-
-<p>After it is installed, you can try to use it to play a file
-downloaded live via bittorrent like this:
-
-<p><pre>
-vlc https://archive.org/download/Glass_201703/Glass_201703_archive.torrent
-</pre></p>
-
-<p>It also support magnet links and local .torrent files.</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>
-</description>
- </item>
-
- <item>
- <title>Debian Edu interview: Yvan Masson</title>
- <link>http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html</guid>
- <pubDate>Tue, 12 May 2020 06:30:00 +0200</pubDate>
- <description><p>It has been way too long since my last interview, but as the
-<a href="http://www.skolelinux.org/">Debian Edu / Skolelinux</a>
-community is still active, and new people keep showing up on the IRC
-channel <a href="irc://irc.debian.org/#debian-edu">#debian-edu</a> and
-<a href="https://lists.debian.org/debian-edu/">the debian-edu mailing
-list</a>, I decided to give it another go. I was hoping someone else
-might pick up the idea and run with it, but this has not happened as
-far as I can tell, so here we are… This time the announcement of a new
-free software tool to
-<a href="https://framagit.org/Yvan-Masson/WhosWho">create a school year
-book</a> triggered my interest, and I decided to learn more about its
-author.</p>
-
-<p><strong>Who are you, and how do you spend your days?</strong></p>
-
-<p>My name is Yvan MASSON, I live in France. I have my own one person
-business in computer services. The work consist of visiting my
-customers (person's home, local authority, small business) to give
-advise, install computers and software, fix issues, and provide
-computing usage training. I spend the rest of my time enjoying my
-family and promoting free software.</p>
-
-<p><strong>What is your approach for promoting free
-software?</strong></p>
-
-<p>When I think that free software could be suitable for someone, I
-explain what it is, with simple words, give a few known examples, and
-explain that while there is no fee it is a viable alternative in many
-situations. Most people are receptive when you explain how it is
-better (I simplify arguments here, I know that it is not so simple):
-Linux works on older hardware, there are no viruses, and the software
-can be audited to ensure user is not spied upon. I think the most
-important is to keep a clear but moderated speech: when you try to
-convince too much, people feel attacked and stop listening.</p>
-
-<p><strong>How did you get in contact with the Skolelinux / Debian Edu
-project?</strong></p>
-
-<p>I can not remember how I first heard of Skolelinux / Debian Edu,
-but probably on planet.debian.org. As I have been working for a
-school, I have interest in this type of project.
-
-<p>The school I am involved in is a school for "children" between 14
-and 18 years old. The French government has recommended free software
-since 2012, but they do not always use free software themselves. The
-school computers are still using the Windows operating system, but all
-of them have the classic set of free software: Firefox ESR,
-LibreOffice (with the excellent extension Grammalecte that indicates
-French grammatical errors), SumatraPDF, Audacity, 7zip, KeePass2, VLC,
-GIMP, Inkscape…
-
-<p><strong>What do you see as the advantages of Skolelinux / Debian
-Edu?</strong></p>
-
-<p>It is free software! Built on Debian, I am sure that users are not
-spied upon, and that it can run on low end hardware. This last point
-is very important, because we really need to improve "green IT". I do
-not know enough about Skolelinux / Debian Edu to tell how it is better
-than another free software solution, but what I like is the "all in
-one" solution: everything has been thought of and prepared to ease
-installation and usage.</p>
-
-<p>I like Free Software because I hate using something that I can not
-understand. I do not say that I can understand everything nor that I
-want to understand everything, but knowing that someone / some company
-intentionally prevents me from understanding how things work is really
-unacceptable to me.</p>
-
-<p>Secondly, and more importantly, free software is a requirement to
-prevent abuses regarding human rights and environmental care.
-Humanity can not rely on tools that are in the hands of small group of
-people.</p>
-
-<p><strong>What do you see as the disadvantages of Skolelinux / Debian
-Edu?</strong></p>
-
-<p>Again, I don't know this project enough. Maybe a dedicated website?
-Debian wiki works well for documentation, but is not very appealing to
-someone discovering the project. Also, as Skolelinux / Debian Edu uses
-OpenLDAP, it probably means that Windows workstations cannot use
-centralized authentication. Maybe the project could use Samba as an
-Active Directory domain controller instead, allowing Windows desktop
-usage when necessary.</p>
-
-<p>(Editors note: In fact Windows workstations can
-<a href="https://wiki.debian.org/DebianEdu/Documentation/Buster/HowTo/Samba">use
-the centralized authentication in a Debian Edu setup</a>, at least for
-some versions of Windows, but the fact that this is not well known can
-be seen as an indication of the need for better documentation and
-marketing. :)</p>
-
-<p><strong>Which free software do you use daily?</strong></p>
-
-<p>Nothing original: Debian testing/sid with Gnome desktop, Firefox,
-Thunderbird, LibreOffice…</p>
-
-<p><strong>Which strategy do you believe is the right one to use to
-get schools to use free software?</strong></p>
-
-<p>Every effort to spread free software into schools is important,
-whatever it is. But I think, at least where I live, that IT
-professionals maintaining schools networks are still very "Microsoft
-centric". Schools will use any working solution, but they need people
-to install and maintain it. How to make these professionals sensitive
-about free software and train them with solutions like Debian Edu /
-Skolelinux is a really good question :-)</p>
-</description>
- </item>
-
- <item>
- <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 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 here 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
<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
projects / homepage.git / blobdiff