<channel>
<title>Petter Reinholdtsen</title>
<description></description>
- <link>http://people.skolelinux.org/pere/blog/</link>
- <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
+ <link>https://people.skolelinux.org/pere/blog/</link>
+ <atom:link href="https://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
<item>
- <title>A Brazilian Portuguese translation of the book Made with Creative Commons</title>
- <link>http://people.skolelinux.org/pere/blog/A_Brazilian_Portuguese_translation_of_the_book_Made_with_Creative_Commons.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Brazilian_Portuguese_translation_of_the_book_Made_with_Creative_Commons.html</guid>
- <pubDate>Fri, 3 Dec 2021 09:30:00 +0100</pubDate>
- <description><p>A few days ago, a productive translator started working on a new
-translation of <a href="https://madewith.cc">the Made with Creative
-Commons book</a> for Brailian Portuguese. The translation take place on
-<a href="https://hosted.weblate.org/projects/madewithcc/translation/">the
-Weblate web based translation system</a>. Once the translation is
-complete and proof read, we can publish it on paper as well as in PDF,
-ePub and HTML format. The translation is already 16% complete, and if
-more people get involved I am conviced it can very quickly reach 100%.
-If you are interested in helping out with this or other translations
-of the Made with Creative Commons book, start translating on
-Weblate. There are partial translations available in Azerbaijani,
-Bengali, Brazillian Portuguese, Dutch, French, German, Greek, Polish,
-Simplified Chinese, Swedish, Thai and Ukrainian.</p>
+ <title>«Virkninger av angrefristloven», hovedfagsoppgaven som fikk endret en lov</title>
+ <link>https://people.skolelinux.org/pere/blog/_Virkninger_av_angrefristloven___hovedfagsoppgaven_som_fikk_endret_en_lov.html</link>
+ <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/_Virkninger_av_angrefristloven___hovedfagsoppgaven_som_fikk_endret_en_lov.html</guid>
+ <pubDate>Sun, 29 Oct 2023 22:00:00 +0100</pubDate>
+ <description><img src="http://people.skolelinux.org/pere/blog/images/2023-10-29-bok-angrefrist.svg" width="20%" align="center"></a>
+
+<p>I 1979 leverte Ole-Erik Yrvin en hovedfagsoppgave for Cand. Scient.
+ ved Institutt for sosiologi på Universitetet i Oslo på oppdrag fra
+ Forbruker- og administrasjonsdepartementet. Oppgaven evaluerte
+ Angrefristloven fra 1972, og det han oppdaget førte til at loven ble
+ endret fire år senere.</p>
+
+<p>Jeg har kjent Ole-Erik en stund, og synes det var trist at hans
+ oppgave ikke lenger er tilgjengelig, hverken fra oppdragsgiver
+ eller fra universitetet. Hans forsøk på å få den avbildet og lagt
+ ut på Internett har vist seg fånyttes, så derfor tilbød jeg meg for
+ en stund tilbake å publisere den og gjøre den tilgjengelig med
+ fribruksvilkår på Internett. Det er nå klart, og hovedfagsoppgaven
+ er tilgjengelig blant annet via <a
+ href="http://www.hungry.com/~pere/publisher/">min liste over
+ publiserte bøker</a>, både som nettside,
+ <a href="https://www.lulu.com/search?contributor=Ole-Erik+Yrvin">digital
+ bok i ePub-format og på papir fra lulu.com</a>. Jeg regner med at
+ den også vil dukke opp på nettbokhandlere i løpet av en måned eller
+ to.</p>
+
+<p>Alle tabeller og figurer er gjenskapt for bedre lesbarhet, noen
+ skrivefeil rettet opp og mange referanser har fått flere detaljer
+ som ISBN-nummer og DOI-referanse. Selv om jeg ikke regner med at
+ dette blir en kioskvelter, så håper jeg denne nye utgaven kan komme
+ fremtiden til glede.</p>
-<p>The <a href="https://gitlab.com/gunnarwolf/madewithcc-es.git">git
-repository for the book</a> contain all source files needed to build
-the book for yourself.
-<ahref="https://gunnarwolf.gitlab.io/madewithcc-es/">HTML editions</a>
-to help with proof reading is also available.</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>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>Debian still an excellent choice for Lego builders</title>
- <link>http://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</guid>
- <pubDate>Sun, 24 Oct 2021 07:10:00 +0200</pubDate>
- <description><p>The Debian Lego team saw a lot of activity the last few weeks. All
-the packages under the team umbrella has been updated to fix
-packaging, lintian issues and BTS reports. In addition, a new and
-inspiring team member appeared on both the
-<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team">debian-lego-team
-Team mailing list</a> and
-<a href="irc://irc.debian.org/%23debian-lego">IRC channel
-#debian-lego</a>. If you are interested in Lego CAD design and LEGO
-Mindstorms programming, check out the
-<a href="http://wiki.debian.org/LegoDesigners">team wiki page</a> to
-see what Debian can offer the Lego enthusiast.</p>
+ <title>«underordnet tjenestemann blir inhabil fordi en overordnet er inhabil».</title>
+ <link>https://people.skolelinux.org/pere/blog/_underordnet_tjenestemann_blir_inhabil_fordi_en_overordnet_er_inhabil__.html</link>
+ <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/_underordnet_tjenestemann_blir_inhabil_fordi_en_overordnet_er_inhabil__.html</guid>
+ <pubDate>Thu, 7 Sep 2023 09:10:00 +0200</pubDate>
+ <description><p>Medlemmene av Norges regjering har demonstert de siste månedene at
+habilitetsvureringer ikke er deres sterke side og det gjelder både
+Arbeiderpartiets og Senterpartiers representater. Det er heldigvis
+enklere i det private, da inhabilitetsreglene kun gjelder de som
+jobber for folket, ikke seg selv. Sist ut er utenriksminister
+Huitfeldt. I går kom nyheten om at
+<a href="https://www.nrk.no/nyheter/riksadvokaten_-okokrim-nestsjef-kan-behandle-huitfeldt-saken-1.16545162">Riksadvokaten
+har konkludert med at nestsjefen i Økokrim kan behandle sak om
+habilitet og innsidekunnskap</a> for Huitfeldt, på tross av at hans
+overordnede, sjefen for Økokrim, har meldt seg inhabil i saken. Dette
+er litt rart. I veilednigen
+«<a href="https://www.regjeringen.no/globalassets/upload/krd/vedlegg/komm/veiledere/habilitet_i_kommuner_og_fylkeskommuner.pdf">Habilitet
+i kommuner og fylkeskommuner</a>» av Kommunal- og regionaldepartementet
+forteller de hva som gjelder, riktig nok gjelder veiledningen ikke for
+Økokrim som jo ikke er kommune eller fylkeskommune, men jeg får ikke
+inntrykk av at dette er regler som kun gjelder for kommune og
+fylkeskommune:
-<p>Patches has been sent upstream, causing new upstream releases, one
-even the first one in more than ten years, and old upstreams was
-released with new ones. There are still a lot of work left, and the
-team welcome more members to help us make sure Debian is the Linux
-distribution of choice for Lego builders. If you want to contribute,
-join us in the IRC channel and become part of
-<a href="https://salsa.debian.org/debian-lego-team/">the team on
-Salsa</a>.</p>
+<blockquote>
+<p>«<strong>2.1 Oversikt over inhabilitetsgrunnlagene</strong>
+
+<p>De alminnelige reglene om inhabilitet for den offentlige
+forvaltningen er gitt i
+<a href="https://lovdata.no/dokument/NL/lov/1967-02-10/KAPITTEL_2#KAPITTEL_2">forvaltningsloven
+§§ 6 til 10</a>. Forvaltningslovens hovedregel om inhabilitet framgår
+av § 6. Her er det gitt tre ulike grunnlag som kan føre til at en
+tjenestemann eller folkevalgt blir inhabil. I § 6 første ledd
+bokstavene a til e er det oppstilt konkrete tilknytningsforhold mellom
+tjenestemannen og saken eller sakens parter som automatisk fører til
+inhabilitet. Annet ledd oppstiller en skjønnsmessig regel om at
+tjenestemannen også kan bli inhabil etter en konkret vurdering av
+inhabilitetsspørsmålet, der en lang rekke momenter kan være
+relevante. I tredje ledd er det regler om såkalt avledet
+inhabilitet. Det vil si at en underordnet tjenestemann blir inhabil
+fordi en overordnet er inhabil.»</p>
+</blockquote>
-<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>Loven sier ganske enkelt «Er den overordnede tjenestemann ugild,
+kan avgjørelse i saken heller ikke treffes av en direkte underordnet
+tjenestemann i samme forvaltningsorgan.» Jeg antar tanken er at en
+underordnet vil stå i fare for å tilpasse sine konklusjoner til det
+overordnet vil ha fordel av, for å fortsatt ha et godt forhold til sin
+overordnede. Men jeg er ikke jurist og forstår nok ikke kompliserte
+juridiske vurderinger. For å sitere «Kamerat Napoleon» av George
+Orwell: «Alle dyr er like, men noen dyr er likere enn andre».
</description>
</item>
<item>
- <title>Hvilke partier støttet datalagringsdirektivet 2 og 3?</title>
- <link>http://people.skolelinux.org/pere/blog/Hvilke_partier_st_ttet_datalagringsdirektivet_2_og_3_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvilke_partier_st_ttet_datalagringsdirektivet_2_og_3_.html</guid>
- <pubDate>Fri, 10 Sep 2021 08:35:00 +0200</pubDate>
- <description><p>Relativt stille har Stortinget den siste perioden vedtatt
-<a href="https://no.wikipedia.org/wiki/Datalagringsdirektivet">datalagringsdirektivet</a> versjon to og tre, og slik økt
-overvåkningstrykket på Internett i Norge betraktelig. Det blir mer og
-mer viktig å <a href="https://www.torproject.org/">bruke Tor</a> og
-god kryptering for å sikre sin privatsfære på Internett.</p>
-
-<p>Først ut var
-<a href="https://www.stortinget.no/no/Saker-og-publikasjoner/Saker/Sak/?p=79451">ny
-etterretningstjenestelov</a> vedtatt 2020-06-11, der samtlige partier
-på stortinget (Arbeiderpartiet, Fremskrittspartiet, Høyre, Kristelig
-Folkeparti, Miljøpartiet De Grønne, Senterpartiet, Sosialistisk
-Venstreparti, Venstre og et forhenværende Fremskrittspartimedlem)
-unntatt Rødt støttet loven i sin helhet da den ble vedtatt.
-
-<p>Dernest kom
-<a href="https://www.stortinget.no/no/Saker-og-publikasjoner/Saker/Sak/?p=84446">ny
-ekomlov</a> vedtatt 2021-06-08 med støtte fra Arbeiderpartiet,
-Fremskrittspartiet, Høyre, Kristelig Folkeparti, Senterpartiet,
-Venstre og et forhenværende Fremskrittspartimedlem mot stemmene fra
-Sosialistisk Venstreparti, Miljøpartiet De Grønne og Rødt.</p>
-
-<p>Intet parti som støtter slike inngrep i privatsfæren får min støtte
-i valg. Heldigvis er det mange parter også utenfor Stortinget som kan
-ha nytte av den økonomiske støtten som følger av hver stemme de får i
-stortingsvalget i år, selv om de ikke kommer inn på Stortinget i denne
-omgang.</p>
-
-<p>Som et annet målepunkt på hvor mye vern av privatsfæren betyr for
-stortingspartiene kan jeg fortelle at ikke et eneste av partiene på
-Stortinget har besvart
-<a href="http://people.skolelinux.org/pere/blog/Hva_mener_partiene_om_vern_av_privatsf_ren_og_sporing_av_befolkningen_.html">brevet
-med spørsmål rundt vern av privatsfæren</a> som de fikk i sommer.</p>
-
-<p>Hvis du lurer på hva som er problemet med datalagringsdirektivet,
-anbefaler jeg å lese <a href="http://www.uhuru.biz/?cat=84">artiklene
-fra Jon Wessel-Aas</a> om temaet.</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>
+ <title>Invidious add-on for Kodi 20</title>
+ <link>https://people.skolelinux.org/pere/blog/Invidious_add_on_for_Kodi_20.html</link>
+ <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Invidious_add_on_for_Kodi_20.html</guid>
+ <pubDate>Thu, 10 Aug 2023 19:50:00 +0200</pubDate>
+ <description><p>I still enjoy <a href="https://kodi.tv/">Kodi</a> and
+<a href="https://libreelec.tv/">LibreELEC</a> as my multimedia center
+at home. Sadly two of the services I really would like to use from
+within Kodi are not easily available. The most wanted add-on would be
+one making <a href="https://archive.org/">The Internet Archive</a>
+available, and it has
+<a href="https://kodi.wiki/view/Add-on:Internet_Archive">not been
+working</a> for many years. The second most wanted add-on is one
+using <a href="https://invidious.io/">the Invidious privacy enhanced
+Youtube frontent</a>. A plugin for this has been partly working, but
+not been kept up to date in the Kodi add-on repository, and its
+upstream seem to have given it up in April this year, when the git
+repository was closed. A few days ago I got tired of this sad state
+of affairs and decided to
+<a href="https://github.com/petterreinholdtsen/kodi-invidious-plugin">have
+a go at improving the Invidious add-on</a>. As
+<a href="https://github.com/iv-org/invidious/issues/3872">Google has
+already attacked</a> the Invidious concept, so it need all the support
+if can get. My small contribution here is to improve the service
+status on Kodi.</p>
+
+<p>I added support to the Invidious add-on for automatically picking a
+working Invidious instance, instead of requiring the user to specify
+the URL to a specific instance after installation. I also had a look
+at the set of patches floating around in the various forks on github,
+and decided to clean up at least some of the features I liked and
+integrate them into my new release branch. Now the plugin can handle
+channel and short video items in search results. Earlier it could
+only handle single video instances in the search response. I also
+brushed up the set of metadata displayed a bit, but hope I can figure
+out how to get more relevant metadata displayed.</p>
+
+<p>Because I only use Kodi 20 myself, I only test on version 20 and am
+only motivated to ensure version 20 is working. Because of API changes
+between version 19 and 20, I suspect it will fail with earlier Kodi
+versions.</p>
+
+<p>I already
+<a href="https://github.com/xbmc/repo-plugins/pull/4363">asked to have
+the add-on added</a> to the official Kodi 20 repository, and is
+waiting to heard back from the repo maintainers.</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>Mechanic's words in five languages, English, Norwegian and Northern Sámi editions</title>
- <link>http://people.skolelinux.org/pere/blog/Mechanic_s_words_in_five_languages__English__Norwegian_and_Northern_S_mi_editions.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Mechanic_s_words_in_five_languages__English__Norwegian_and_Northern_S_mi_editions.html</guid>
- <pubDate>Wed, 4 Aug 2021 15:30:00 +0200</pubDate>
- <description><p>Almost thirty years ago, some forward looking teachers at Samisk
-videregående skole og reindriftsskole teaching metal work and Northern
-Sámi, decided to create a list of words used in Northern Sámi metal
-work. After almost ten years this resulted in a dictionary database,
-published as the book
-"<a href="https://ovttas.no/nb/girji_mekanikerord">Mekanihkkársánit :
-Mekanikerord = Mekaanisen alan sanasto = Mechanic's words</a>" in
-1999. The
-<a href="http://www.skuvla.info/skolehist/sveinl-n.htm">story of this
-work</a> is available from the pen of Svein Lund, one of the leading
-actors behind this effort. They even got the dictionary approved by
-the Sámi Language Council as the recommended metal work words to use.</p>
-
-<p>Fast forward twenty years, I came across this work when I recently
-became interested in metal work, and started watching educational and
-funny videos on the topic, like the ones from
-<a href="https://yewtu.be/channel/UCKLIIdKEpjAnn8E76KP7sQg">mrpete222</a>
-and <a href="https://yewtu.be/channel/UC5NO8MgTQKHAWXp6z8Xl7yQ">This
-Old Tony</a>. But they all talk English, but I wanted to know what
-the tools and techniques they used were called in Norwegian. Trying
-to track down a good dictionary from English to Norwegian, after much
-searching, I came across the database of words created
-almost thirty years ago, with translations into English, Norwegian,
-Northern Sámi, Swedish and Finnish. This gave me a lot of the
-Norwegian phrases I had been looking for. To make it easier for the
-next person trying to track down a good Norwegian dictionary for the
-metal worker, and because I knew the person behind the database from
-my Skolelinux / Debian Edu days, I decided to ask if the database
-could be released to the public without any usage limitations, in
-other words as a Creative Commons licensed data set. And happily,
-after consulting with the Sámi Parliament of Norway, the database is
-now available with the Creative Commons Attribution 4.0 International
-license from
-<a href="https://gitlab.com/petterreinholdtsen/mekanikerord">my gitlab
-repository</a>.</p>
-
-<p>The dictionary entries look slightly different, depending on the
-language in focus. This is the same entry in the different editions.
-
-<p><em>English</em></p>
-
-<blockquote>
-<dl>
- <dt><strong>lathe</strong></dt>
-
- <dd><p>dreiebenk (nb) várve, várvenbea&#331;ka, jorahanbea&#331;ka, vátnanbea&#331;ka (se) svarv (sv) sorvi (fi) </p></dd>
-
-</dl>
-</blockquote>
-
-<p><em>Norwegian</em></p>
-
-<blockquote>
-<dl>
- <dt><strong>dreiebenk</strong></dt>
-
- <dd><p>lathe (en) várve, várvenbea&#331;ka, jorahanbea&#331;ka,
- vátnanbea&#331;ka (se) svarv (sv) sorvi (fi) </p></dd>
-
- <dd><p>(nb): sponskjærande bearbeidingsmaskin der ein med
- skjæreverktøy lausgjør spon frå eit roterande
- arbetsstykke</p></dd>
-
-</dl>
-</blockquote>
-
-<p><em>Northern Sámi</em></p>
-
-<blockquote>
-<dl>
- <dt><strong>várve, várvenbea&#331;ka, jorahanbea&#331;ka, vátnanbea&#331;ka</strong></dt>
-
- <dd><p>dreiebenk (nb) lathe (en) svarv (sv) sorvi (fi) </p></dd>
-
- <dd><p>(se): ma&#353;iidna mainna &#269;uohppá vuolahasaid jorri
- bargoávdnasis</p></dd>
-
- <dd><p>(nb): sponskjærande bearbeidingsmaskin der ein med
- skjæreverktøy lausgjør spon frå eit roterande
- arbetsstykke</p></dd>
-
-<dl>
-</blockquote>
-
-<p>The database included term description in both Norwegian and
-Northern Sámi, but not English. Because of this, the Northern Sámi
-edition include both descriptions, the Norwegian edition include the
-Norwegian description and the English edition lack a descripiton.</p>
-
-<p>Once the database was available without any usage restrictions, and
-armed with my experience in publishing books, I decided to publish a
-Norwegian/English dictionary as a book using the database, to make the
-data set available also on paper and as an ebook. Further into the
-project, it occurred to me that I could just as easily make an English
-dictionary, and talking to Svein and concluding that it was within
-reach, I decided to make a Northern Sámi dictionary too.</p>
-
-<p>Thus I suddenly find myself publishing a Northern Sámi dictionary,
-even though I do not understand the language myself. I hope it will
-be well received, and can help revive the impressive work done almost
-thirty years ago to document the vocabulary of metal workers. If I
-get some help, I might even extend it with some of the words I find
-missing, like collet, rotary broach, carbide, knurler, arbor press and
-others. But the first edition build from a lightly edited version of
-the original database, with no new entries added. If you would like
-to check it out, visit
-<a href="http://www.hungry.com/~pere/publisher/">my list of published
-books</a> and consider
-<a href="https://www.lulu.com/search?contributor=Petter+Reinholdtsen">buying
-a paper or ebook copy from lulu.com</a>. The paper edition is only
-available in hardcover to increase its durability in the workshop.</p>
-
-<p>I am very happy to report that in the process, and thanks to help
-from both Svein Lund and Børre Gaup who understand the language, the
-docbook tools I use to create books, dblatex and docbook-xsl, now
-include support for Northern Sámi. Before I started, these lacked the
-needed locale settings for this language, but now the patches are
-included upstream.</p>
+ <title>What did I learn from OpenSnitch this summer?</title>
+ <link>https://people.skolelinux.org/pere/blog/What_did_I_learn_from_OpenSnitch_this_summer_.html</link>
+ <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_did_I_learn_from_OpenSnitch_this_summer_.html</guid>
+ <pubDate>Sun, 11 Jun 2023 08:30:00 +0200</pubDate>
+ <description><p>With yesterdays
+<a href="https://www.debian.org/News/2023/20230610">release of Debian
+12 Bookworm</a>, I am happy to know the
+<a href="https://tracker.debian.org/pkg/opensnitch">the interactive
+application firewall OpenSnitch</a> is available for a wider audience.
+I have been running it for a few weeks now, and have been surprised
+about some of the programs connecting to the Internet. Some programs
+are obviously calling out from my machine, like the NTP network based
+clock adjusting system and Tor to reach other Tor clients, but others
+were more dubious. For example, the KDE Window manager try to look up
+the host name in DNS, for no apparent reason, but if this lookup is
+blocked the KDE desktop get periodically stuck when I use it. Another
+surprise was how much Firefox call home directly to mozilla.com,
+mozilla.net and googleapis.com, to mention a few, when I visit other
+web pages. This direct connection happen even if I told Firefox to
+always use a proxy, and the proxy setting is ignored for this traffic.
+Other surprising connections come from audacity and dirmngr (I do not
+use Gnome). It took some trial and error to get a good default set of
+permissions. Without it, I would get popups asking for permissions at
+any time, also the most inconvenient ones where I am in the middle of
+a time sensitive gaming session.</p>
+
+<p>I suspect some application developers should rethink when then need
+to use network connections or DNS lookups, and recommend testing
+OpenSnitch (only <tt>apt install opensnitch</tt> away in Debian
+Bookworm) to locate and report any surprising Internet connections on
+your desktop machine.</p>
+
+<p>At the moment the upstream developer and Debian package maintainer
+is working on making the system more reliable in Debian, by enabling
+the eBPF kernel module to track processes and connections instead of
+depending in content in /proc/. This should enter unstable fairly
+soon.</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 2023-06-12</strong>: I got a tip about
+<a href="https://wiki.debian.org/PrivacyIssues">a list of privacy
+issues in Free Software</a> and the
+<a href="irc://irc.debian.org/%23debian-privacy">#debian-privacy IRC
+channel</a> discussing these topics.</p>
+
</description>
</item>
<item>
- <title>Hva mener partiene om vern av privatsfæren og sporing av befolkningen?</title>
- <link>http://people.skolelinux.org/pere/blog/Hva_mener_partiene_om_vern_av_privatsf_ren_og_sporing_av_befolkningen_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hva_mener_partiene_om_vern_av_privatsf_ren_og_sporing_av_befolkningen_.html</guid>
- <pubDate>Sat, 31 Jul 2021 13:30:00 +0200</pubDate>
- <description><p>Årsaken til at vi på dugnad oversatte og ga ut boken
-«<a href="http://www.hungry.com/~pere/publisher/">Hvordan knuse
-overvåkningskapitalismen</a>» av Cory Doctorow er at vi mener den tar
-opp et viktig tema og bør leses av så mange som mulig. Temaene boken
-tok opp, og det kommende valget, inspirerte nylig oss som sto bak
-utgivelsen til å sende inn spørsmål til partiene sammen med et
-eksemplar av boken. Vi er veldig spent på hva de ulike partiene
-kommer til å svare. Spørsmålene er sendt til samtlige partier som er
-representert på stortinget, men vi tar naturligvis imot svar også fra
-andre partier. Det er for mange partier i Norge til å ta kostnaden
-med å sende til alle, så vi begrenset oss til de som er representert
-på Stortinget.</p>
-
-<p>Her er brevet som ble postlagt til partiene tidligere i uka:</p>
-
-<p><strong>OM DIGITALE PLATTFORMER OG STORDATA – MED SEKS KONKRETE
-FORSLAG</strong></p>
-
-<p>Det er en økende grad av mistillit til digitale plattformer fordi
-den delen av vårt samfunn mangler helt grunnleggende demokratiske
-kjøreregler. Begrepet «privatlivets fred» er i ferd med å dø som et
-resultat av digitaliseringen. Som brukere har vi ikke kontroll over
-våre personlige data og er helt frarøvet et digitalt privatliv. Dette
-dels fordi samfunnet rundt oss samler inn data om oss og våre
-bevegelser, samtidig som noen globale aktører samler data om
-alle. Denne utviklingen er preget av kaos og manglende regulering.</p>
-
-<p>Disse digitale utfordringene kan være vanskelig å formulere enkelt
-inn i et partiprogram og enda vanskeligere å dekke helhetlig. Vi har
-derfor valgt å sette søkelys på noen utvalgte områder som vi mener
-partiene burde ta klare standpunkt til.</p>
-
-<p><strong>Personvern</strong></p>
-
-<p>I følge tekologirådets direktør Tore Tennøe kan det, når offentlige
-virksomheter som Sivilombudsmannen, Likestillings- og
-diskrimineringsombudet og Medietilsynet alle deler brukerdata med
-Google-tjenestene Analytics, remarketing audiences og annonsebørsen
-Doubleclick, fort komme i veien for samfunnsoppdraget
-deres. Uttalelsen kommer i forbindelse med en rapport fra
-Teknologirådet som viser at en stor andel av offentlige virksomheter
-deler personinformasjon om de som besøker virksomhetenes nettsider med
-kommersielle
-aktører.<a href="#fn1" class="footnote-ref" id="fnref1"><sup>1</sup></a>
-Stortinget er i følge rapporten en av disse.</p>
-
-<p>I forbindelse med Covid 19 har bruken av videokonferanseløsninger
-økt dramatisk. Løsninger som Microsoft Teams og Zoom har
-åndsverksbruksvilkår som hindrer brukerne å undersøke sikkerheten i
-systemene ved å forby omvent utvikling. Fri programvareløsninger som
-Jitsi og Big Blue Button, har ikke slike begrensinger, kan tas i bruk
-uavhengig av utenlandske leverandører og gir brukerne slik bedre
-sikkerhet.</p>
-
-<p><strong>Facebook er ikke offentlig digital infrastruktur</strong></p>
-
-<p>Leder for det tyske datatilsynet BfDI, Ulrich Kelber, anbefalte sterkt
-i et brev til tyske myndigheter nylig at de stengte sine
-Facebook-sider og avslutter kobling mellom egne sider og Facebook.<a href="#fn2" class="footnote-ref" id="fnref2"><sup>2</sup></a> <a href="#fn3" class="footnote-ref" id="fnref3"><sup>3</sup></a>
-Bakgrunnen er at bruken av Facebook ikke er i tråd med EU- og
-EØS-lovgivingen om vern av privatsfæren, personvernforordningen
-GDPR.</p>
-
-<p><strong>Massiv overvåkning av digitale brukere</strong></p>
-
-<p>De store globale plattformene samler inn data om oss alle gjennom sine
-tjenester. Data akkumuleres og videreselges, med påstand om at
-informasjonen er anonymisert. Data om geoposisjon er også noe
-teleselskapene samler inn om alle brukere, selv de som har helt enkle
-mobiltelefoner.<a href="#fn4" class="footnote-ref" id="fnref4"><sup>4</sup></a> <a href="#fn5" class="footnote-ref" id="fnref5"><sup>5</sup></a>
-EUs personvernmyndighet, har i sitt arbeid med GDPR, presisert at
-anonymisering ikke må forveksles med pseudoanonymisering<a href="#fn6" class="footnote-ref" id="fnref6"><sup>6</sup></a>, som fortsatt er
-underlagt personvernlovgivningen, og at mobilers geografiske
-plassering (lokasjonsdata) ikke kan anonymiseres.</p>
-
-<p>En av mange saker som dokumenterer disse utfordringene er NRK som
-kjøpte «anonymiserte» lokasjonsdata<a href="#fn7" class="footnote-ref" id="fnref7"><sup>7</sup></a>, og ved hjelp av enkel analyse kunne
-identifisere enkeltindivider.</p>
-
-<p>Grunnskolen i Norge har i stor grad tatt i bruk Internett-baserte
-løsninger, og de fleste av disse samler inn personopplysninger om
-elever og lærere som lagres på datamaskiner utenfor både Norge og
-EU. I tillegg til å rapportere bruk til for eksempel Google
-Analytics, så bruker mange av tjenestene datamaskiner eid av Amazon
-og Microsoft. Dette fører totalt til en massiv spredning og innsamling
-av personopplysninger utenfor skolene om elever i norske skoler.</p>
-<p>Spørsmålene vi stiller til de politiske partiene er som følger:</p>
-
-<ol type="1">
-
-<li>Er dere enige med det tyske datatilsynet om at offentlige
-instanser ikke bør dele informasjon om sine ansatte og lesere med
-selskaper i strid med GDPR, og derfor bør stenge sine
-Facebook-sider?</li>
-
-<li>Er dere enig med Teknologirådet i at offentlig sektor bør velge
-løsninger og verktøy som følger personvernprinsippene, og samler inn
-minimalt med data til helt spesifikke formål?</li>
-
-<li>Bør det være mulig å bevege seg i Norge med mobiltelefon uten at
-ens posisjon samles inn og selges videre av teleselskapene?</li>
-
-<li>Bør det offentlige velge videoløsninger som sikrer
-brukernes rettigheter når det gjelder sikkerhet, personvern og
-innsyn?</li>
-
-<li>Hva tenker deres parti man burde gjøre for å forhindre
-massiv overvåkning av brukere i Norge?</li>
-
-<li>Er deling av elevenes personopplysninger til aktører utenfor
-skolen, potensielt i strid med GDPR, en akseptabel kostnad for å
-forenkle kommunenes drift av skoler?<a href="#fn8" class="footnote-ref" id="fnref8"><sup>8</sup></a></li>
-
-</ol>
-
-<p><em>Om det er behov for ytterligere avklaringer og
-bakgrunnsinformasjon, ta gjerne kontakt! Epostadressen vår er til
-Petter Reinholdtsen: pere-valg2021 (at) hungry.com. Spørsmålene samt
-svarene vi mottar vil bli publisert.</em></p>
-
-<p><strong>Den internasjonale bakgrunnen</strong></p>
-
-<p>Internasjonalt pågår det en stadig bredere faglig og politisk
-drøfting av de viktige bakenforliggende problemstillingene. Ett
-eksempel er vedlagte bok der dr. Cory nettopp drøfter definerende
-problemstillinger fom følger den nasjonale og internasjonale
-utviklingen av «stordata». Boken peker også på helt konkrete
-innsatsområder.</p>
-
-<p>Når for eksempel Rand Worldwide viser til at Facebook
-«radikaliseres», og når Facebook i sin tur sprer feilinformasjon om
-coronaviruset med en forklaring om sine algoritmer, blir det
-implisitte budskapet at maskinlæring og overvåkning kan endre vår
-oppfattelse av hva som er sant. Begrepet «overvåkingskapitalisme» er
-nå blitt det vanlig brukte ordet for å kjennetegne både beskivelsene
-og debatten på dette vide stordata-området. Begrepet ble popularisert
-i 2018-boken «Overvåkingskapitalismens tidsalder» av Shoshana Zuboff,
-som igjen ledet Cory Doctorow til å skrive sin bok.</p>
-
-<p><em>Legger ved boken fordi en gjennomgang er ment å være til hjelp
-som nyttig bakgrunnsmateriale i det generelle politiske arbeidet på
-dette stadig viktigere samfunnsområdet.</em></p>
-
-<p>Boken ble oversatt til bokmål <em>på dugnad</em> og utgitt
-<em>samtidig</em> med den engelske utgaven. Den kan fritt lastes ned
-og også bestilles i trykt format på bokmål direkte fra trykkeriet<a href="#fn9" class="footnote-ref" id="fnref9"><sup>9</sup></a>. Nærmere
-informasjon om utgivelsen fremgår av kolofon-siden.</p>
-
-<p>Med vennlig hilsen</p>
-<p>For Oversettergruppen</p>
-
-<p>Petter Reinholdtsen (prosjektleder) og Ole-Erik Yrvin (gruppekontakt)</p>
-
-
-<section class="footnotes">
-<hr />
-<ol>
-
-<li id="fn1"><p>Offentlige nettsteder sporer oss. Teknologirådet 2021-03-26. <a href="https://teknologiradet.no/offentlige-nettsteder-sporer-oss/" class="uri">https://teknologiradet.no/offentlige-nettsteder-sporer-oss/</a> <a href="#fnref1" class="footnote-back">↩</a></p></li>
+ <title>wmbusmeters, parse data from your utility meter - nice free software</title>
+ <link>https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html</link>
+ <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html</guid>
+ <pubDate>Fri, 19 May 2023 21:50:00 +0200</pubDate>
+ <description><p>There is a European standard for reading utility meters like water,
+gas, electricity or heat distribution meters. The
+<a href="https://en.wikipedia.org/wiki/Meter-Bus">Meter-Bus standard
+(EN 13757-2, EN 13757-3 and EN 13757–4)</a> provide a cross vendor way
+to talk to and collect meter data. I ran into this standard when I
+wanted to monitor some heat distribution meters, and managed to find
+free software that could do the job. The meters in question broadcast
+encrypted messages with meter information via radio, and the hardest
+part was to track down the encryption keys from the vendor. With this
+in place I could set up a MQTT gateway to submit the meter data for
+graphing.</p>
+
+<p>The free software systems in question,
+<a href="https://tracker.debian.org/pkg/rtl-wmbus">rtl-wmbus</a> to
+read the messages from a software defined radio, and
+<a href="https://tracker.debian.org/pkg/wmbusmeters">wmbusmeters</a> to
+decrypt and decode the content of the messages, is working very well
+and allowe me to get frequent updates from my meters. I got in touch
+with upstream last year to see if there was any interest in publishing
+the packages via Debian. I was very happy to learn that Fredrik
+Öhrström volunteered to maintain the packages, and I have since
+assisted him in getting Debian package build rules in place as well as
+sponsoring the packages into the Debian archive. Sadly we completed
+it too late for them to become part of the next stable Debian release
+(Bookworm). The wmbusmeters package just cleared the NEW queue. It
+will need some work to fix a built problem, but I expect Fredrik will
+find a solution soon.</p>
+
+<p>If you got a infrastructure meter supporting the Meter Bus
+standard, I strongly recommend having a look at these nice
+packages.</p>
-<li id="fn2"><p>Brombach, Harald. Tyske myndigheter må trolig slette Facebook-sidene sine innen nyttår. digi.no 2021-07-02. <a href="https://www.digi.no/artikler/tyske-myndigheter-ma-trolig-slette-facebook-sidene-sine-innen-nyttar/511719" class="uri">https://www.digi.no/artikler/tyske-myndigheter-ma-trolig-slette-facebook-sidene-sine-innen-nyttar/511719</a> <a href="#fnref2" class="footnote-back">↩</a></p></li>
-
-<li id="fn3"><p>Lomas, Natasha. German government bodies urged to remove their Facebook Pages before next year. TechCrunch 2021-07-01. <a href="https://techcrunch.com/2021/07/01/german-government-bodies-urged-to-remove-their-facebook-pages-before-next-year/" class="uri">https://techcrunch.com/2021/07/01/german-government-bodies-urged-to-remove-their-facebook-pages-before-next-year/</a> <a href="#fnref3" class="footnote-back">↩</a></p></li>
-
-<li id="fn4"><p>Gundersen, Martin. Telia og Telenor selger analyser av hvor kundene befinner seg. NRK Beta 2019-10-11. <a href="https://nrkbeta.no/2019/10/11/telia-og-telenor-selger-analyser-av-hvor-mobilbrukere-befinner-seg/" class="uri">https://nrkbeta.no/2019/10/11/telia-og-telenor-selger-analyser-av-hvor-mobilbrukere-befinner-seg/</a> <a href="#fnref4" class="footnote-back">↩</a></p></li>
-
-<li id="fn5"><p>de Montjoye, YA., Gambs, S., Blondel, V. med flere<em>.</em> On the privacy-conscientious use of mobile phone data. <em>Sci Data</em> <strong>5, </strong>180286 (2018). <a href="https://doi.org/10.1038/sdata.2018.286" class="uri">https://doi.org/10.1038/sdata.2018.286</a> <a href="#fnref5" class="footnote-back">↩</a></p></li>
-
-<li id="fn6"><p>Guidelines 04/2020 on the use of location data and contact tracing tools in the context of the COVID-19 outbreak. The European Data Protection Board 2020-04-21. <a href="https://edpb.europa.eu/sites/default/files/files/file1/edpb_guidelines_20200420_contact_tracing_covid_with_annex_en.pdf" class="uri">https://edpb.europa.eu/sites/default/files/files/file1/edpb_guidelines_20200420_contact_tracing_covid_with_annex_en.pdf</a> <a href="#fnref6" class="footnote-back">↩</a></p></li>
-
-<li id="fn7"><p>Lied, Henrik med flere. 8300 mobiler sporet på sykehus og krisesentre. NRK 2020-05-11. <a href="https://www.nrk.no/norge/mobilsporing_-8300-mobiler-sporet-pa-sykehus-og-krisesentre-1.15008085" class="uri">https://www.nrk.no/norge/mobilsporing_-8300-mobiler-sporet-pa-sykehus-og-krisesentre-1.15008085</a> <a href="#fnref7" class="footnote-back">↩</a></p></li>
-
-<li id="fn8"><p>Barn, unge og skole. Datatilsynet 2021-07-01. <a href="https://www.datatilsynet.no/personvern-pa-ulike-omrader/skole-barn-unge/" class="uri">https://www.datatilsynet.no/personvern-pa-ulike-omrader/skole-barn-unge/</a> <a href="#fnref8" class="footnote-back">↩</a></p></li>
-
-<li id="fn9"><p>Boken kan leses via <a href="http://www.hungry.com/~pere/publisher/" class="uri">http://www.hungry.com/~pere/publisher/</a>. I tillegg er den tilgjengelig som papirbok fra
-<a href="https://www.lulu.com/en/en/shop/cory-doctorow/hvordan-knuse-overvåkningskapitalismen/ebook/product-yk8neg.html" class="uri">https://www.lulu.com/en/en/shop/cory-doctorow/hvordan-knuse-overvåkningskapitalismen/ebook/product-yk8neg.html</a> <a href="#fnref9" class="footnote-back">↩</a></p></li>
-</ol>
-</section>
-
-<hr />
-
-<h2 id="hvordan-knuse-overvåkningskapitalismen-2021">Hvordan knuse overvåkningskapitalismen (2021)</h2>
-<p>av Cory Doctorow, se også
-<a href="https://craphound.com/category/destroy/" class="uri">https://craphound.com/category/destroy/</a>
-og
-<a href="http://www.hungry.com/~pere/publisher/" class="uri">http://www.hungry.com/~pere/publisher/</a>.</p>
-
-<p>I dag er det en utbredt tro at maskinlæring og kommersiell
-overvåkning kan gjøre selv en konspirasjonsteoretiker uten talegaver
-til en magisk manipulator med evne til å finne de sårbare blant oss og
-ved hjelp av argumenter skapt med kunstig intelligens, sette vettet
-deres ut av spill og gjøre dem til flat-jord-tilhengere,
-vaksineskeptikere eller til og med nynazister. Når RAND beskylder
-Facebook for «radikalisering», og når Facebook i sin tur sprer
-feilinformasjon om coronaviruset og bortforklarer det ved å henvise
-til algoritmene sine, er det implisitte budskapet at maskinlæring og
-overvåkning kan endre vår oppfattelse av hva som er sant.</p>
-
-<p>Men hva om det finnes en annen forklaring? Hva om det er de
-materielle forutsetningene som har endret seg til fordel for disse
-manipulatorene? Hva om det er opplevelsen av å leve i en verden full
-av ekte konspirasjoner, slik de viser seg i samhandlingen mellom rike
-mennesker, lobbyistene deres og lovgiverne, der de enes om å begrave
-ubehagelige sannheter og bevis på ugjerninger, slikt som gjerne kalles
-korrupsjon — hva om det er denne opplevelsen som gjør folk sårbare for
-de tåpelige konspirasjonsteoriene?</p>
-
-<hr/>
-
-<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>
+<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>Six complete translations of The Debian Administrator's Handbook for Buster</title>
- <link>http://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</guid>
- <pubDate>Mon, 5 Jul 2021 19:20:00 +0200</pubDate>
- <description><p>I am happy observe that the <a href="https://debian-handbook.info/">The
-Debian Administrator's Handbook</a> is available in six languages now.
-I am not sure which one of these are completely proof read, but the
-complete book is available in these languages:
-
-<ul>
-
-<li>English</li>
-<li>Norwegian Bokmål</li>
-<li>German</li>
-<li>Indonesian</li>
-<li>Brazil Portuguese</li>
-<li>Spanish</li>
+ <title>The 2023 LinuxCNC Norwegian developer gathering</title>
+ <link>https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html</link>
+ <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html</guid>
+ <pubDate>Sun, 14 May 2023 20:30:00 +0200</pubDate>
+ <description><p>The LinuxCNC project is making headway these days. A lot of
+patches and issues have seen activity on
+<a href="https://github.com/LinuxCNC/linuxcnc/">the project github
+pages</a> recently. A few weeks ago there was a developer gathering
+over at the <a href="https://tormach.com/">Tormach</a> headquarter in
+Wisconsin, and now we are planning a new gathering in Norway. If you
+wonder what LinuxCNC is, lets quote Wikipedia:</p>
-</ul>
-
-<p>This is the list of languages more than 70% complete, in other
-words with not too much left to do:</p>
-
-<ul>
-
-<li>Chinese (Simplified) - 90%</li>
-<li>French - 79%</li>
-<li>Italian - 79%</li>
-<li>Japanese - 77%</li>
-<li>Arabic (Morocco) - 75%</li>
-<li>Persian - 71%</li>
-
-</ul>
-
-<p>I wonder how long it will take to bring these to 100%.</p>
-
-<p>Then there is the list of languages about halfway done:</p>
-
-<ul>
-
-<li>Russian - 63%</li>
-<li>Swedish - 53%</li>
-<li>Chinese (Traditional) - 46%</li>
-<li>Catalan - 45%</li>
-
-</ul>
-
-<p>Several are on to a good start:</p>
-
-<ul>
-
-<li>Dutch - 26%</li>
-<li>Vietnamese - 25%</li>
-<li>Polish - 23%</li>
-<li>Czech - 22%</li>
-<li>Turkish - 18%</li>
-
-</ul>
-
-<p>Finally, there are the ones just getting started:</p>
-
-<ul>
-
-<li>Korean - 4%</li>
-<li>Croatian - 2%</li>
-<li>Greek - 2%</li>
-<li>Danish - 1%</li>
-<li>Romanian - 1%</li>
-
-</ul>
-
-<p>If you want to help provide a Debian instruction book in your own
-language, visit
-<a href="https://hosted.weblate.org/projects/debian-handbook/#languages">Weblate</a>
-to contribute to the translations.</p>
+<blockquote>
+"LinuxCNC is a software system for numerical control of
+machines such as milling machines, lathes, plasma cutters, routers,
+cutting machines, robots and hexapods. It can control up to 9 axes or
+joints of a CNC machine using G-code (RS-274NGC) as input. It has
+several GUIs suited to specific kinds of usage (touch screen,
+interactive development)."
+</blockquote>
+<p>The Norwegian developer gathering take place the weekend June 16th
+to 18th this year, and is open for everyone interested in contributing
+to LinuxCNC. Up to date information about the gathering can be found
+in
+<a href="https://sourceforge.net/p/emc/mailman/emc-developers/thread/sa64jp06nob.fsf%40hjemme.reinholdtsen.name/#msg37837251">the
+developer mailing list thread</a> where the gathering was announced.
+Thanks to the good people at
+<a href="https://www.debian.org/">Debian</a>,
+<a href="https://www.redpill-linpro.com/">Redpill-Linpro</a> and
+<a href="https://www.nuugfoundation.no/no/">NUUG Foundation</a>, we
+have enough sponsor funds to pay for food, and shelter for the people
+traveling from afar to join us. If you would like to join the
+gathering, get in touch.</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>
</item>
<item>
- <title>Kart over Oslo Kommunes eiendomsoversikt fra 2017-06</title>
- <link>http://people.skolelinux.org/pere/blog/Kart_over_Oslo_Kommunes_eiendomsoversikt_fra_2017_06.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kart_over_Oslo_Kommunes_eiendomsoversikt_fra_2017_06.html</guid>
- <pubDate>Sun, 4 Jul 2021 13:15:00 +0200</pubDate>
- <description><a href="http://people.skolelinux.org/~pere/blog/images/2021-07-04-kart-oslos-kommunale-eiendommer.kmz"><img src="http://people.skolelinux.org/~pere/blog/images/2021-07-04-kart-oslos-kommunale-eiendommer.png" align="right"></a>
+ <title>OpenSnitch in Debian ready for prime time</title>
+ <link>https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html</link>
+ <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html</guid>
+ <pubDate>Sat, 13 May 2023 12:10:00 +0200</pubDate>
+ <description><p>A bit delayed,
+<a href="https://tracker.debian.org/pkg/opensnitch">the interactive
+application firewall OpenSnitch</a> package in Debian now got the
+latest fixes ready for Debian Bookworm. Because it depend on a
+package missing on some architectures, the autopkgtest check of the
+testing migration script did not understand that the tests were
+actually working, so the migration was delayed. A bug in the package
+dependencies is also fixed, so those installing the firewall package
+(opensnitch) now also get the GUI admin tool (python3-opensnitch-ui)
+installed by default. I am very grateful to Gustavo Iñiguez Goya for
+his work on getting the package ready for Debian Bookworm.</p>
+
+<p>Armed with this package I have discovered some surprising
+connections from programs I believed were able to work completly
+offline, and it has already proven its worth, at least to me. If you
+too want to get more familiar with the kind of programs using
+Internett connections on your machine, I recommend testing <tt>apt
+install opensnitch</tt> in Bookworm and see what you think.</p>
+
+<p>The package is still not able to build its eBPF module within
+Debian. Not sure how much work it would be to get it working, but
+suspect some kernel related packages need to be extended with more
+header files to get it working.</p>
-<p><a href="https://www.ivarjohansen.no/temaer/annet/3651-eiendomsregister.html">I
-følge Ivar Johansen</a> er det ca ti år siden Finanskomiteen i Oslo
-kommune vedtok "Byrådet bes legge til rette for at en elektronisk
-oversikt over alle kommunale eiendommer er tilgjengelig for oppslag på
-kommunens nettsider." Har ikke klart å finne vedtaket i offisielle
-nettsider fra kommunen, men i og med at kommunen har
-<a href="https://www.oslo.kommune.no/plan-bygg-og-eiendom/kart-og-eiendomsinformasjon/kommunal-eiendom/eiendomsoversikt/">publisert
-oversikt over eiendommer de eier</a> selv, desverre sist oppdatert for
-fire år siden (juni 2017), så kan det virke som vedtaket i hvert fall
-for en periode tok effekt.</p>
-
-<p>Oversikten fra kommunen er et regneark med tomter og bygg, med
-tilhørende metainformasjon om adresse, areal etc. Det er jo et greit
-datagrunnlag, men ikke spesielt egnet for å få oversikt. Det
-inspirerte meg til å lage
-<a href="https://en.wikipedia.org/wiki/Kml">en KML-fil</a> der
-informasjon fra kommunens liste kombineres med geografisk posisjon og
-utstrekning fra Matrikkelen slik den vises frem på Kartverkets tjeneste
-<a href="https://seeiendom.kartverket.no/">Se Eiendom</a>, og slik få
-et interaktivt kart som viser komunens eiendommer. I første omgang
-viser den de 6824 tomtene i listen over eiendommer i Oslo kommune (og
-ikke utenbys tomter), unntatt de 268 gårds- og bruksnummerene uten
-informasjon om geografisk posisjon i Matrikkelen og de 346 gårds- og
-bruksnummerene som mangler helt i Matrikkelen. Det er vanskelig å
-vite hvilke av de sistenevnte som er feil i datagrunnlaget fra
-kommunen og hvilke som er et resultat av utdatert informasjon i et
-fire år gammelt datasett. Mer om det senere.</p>
-
-<p>Hvis du vil se på KML-datasettet, så kan du enten gjøre som meg,
-bruke <a href="https://marble.kde.org/">Marble<a/> på Linux, eller du
-kan laste ned et av de mange andre verktøyene som leser KML-filer, som
-<a href="https://en.wikipedia.org/wiki/Google_Earth">Google Earth</a>,
-<a href="https://wiki.openstreetmap.org/wiki/JOSM">JOSM</a> og
-<a href="https://en.wikipedia.org/wiki/QGIS">QGis</a>. Har desverre
-ikke funnet en nettjeneste som kan vise frem filen i en nettleser, på
-grunn av filstørrelsen. Fant en
-<a href="https://www.openstreetmap.org/">OpenstreetMap</a>-basert
-nettside som håndterte mindre filer, men den ga opp da hele kommunens
-areal var inkludert i filen.</p>
-
-<p>KML-datasettet
-<a href="http://people.skolelinux.org/~pere/blog/images/2021-07-04-kart-oslos-kommunale-eiendommer.kmz">kan lastes ned her fra min blogg</a>. Tomter med bygninger i følge
-matrikkelen er markert i rødt, mens tomter uten bygninger er markert i
-blått. De få tomtene med posisjon men uten utstrekning (tror alle er
-under bakken) har kun fått posisjonsmarkører. Jeg har i denne omgang
-begrenset meg til tomter og ikke tegnet inn hus, da jeg ikke fant noen
-enkel måte å hente ut geografisk utstrekning for husene basert på
-informasjonen i kommunens datasett. Konkret mangler jeg sikker måte å
-identifisere enkeltbygninger basert på kommunens oversikt. Vedlagt er et
-skjermbilde fra Marble som viser hvordan det kan se ut.</p>
-
-<p>På grunn av oppløsningen viser ikke bildet alle gatene og mindre
-eiendommer i sentrum som er eid av kommunen. Dette vises når en
-dykker ned i materialet med en KML-fremviser. Jeg har ikke regnet på
-det, men visuelt ser det ut som om kommunen eier 25-30% av alt arealet
-i kommunen, hvilket jeg fant overraskende. Lurer på hvor stor del av
-arealet i Oslo totalt som er eid av ulike offentlige aktører. Vet jo
-at ulike departementer, direktorater, fylkeskommuner, kommunale
-pensjonskasser, og offentlig majoritetseide selskaper også eier en god
-del av eiendommene i Oslo. Det hadde vært interessant å vise frem,
-men mistenker innsynsforespørslene for å få tak i det datasettet
-kommer til å være en kamp i motbakke, både hvis en forsøker hver
-enkelt offentlig instans eller Matrikkelen.</p>
-
-<p>Fra kartet kan en se at endel tomtearealer er markert flere ganger.
-Det skjer hvis kommunens oversikt henviser til matrikkel-tomter med
-overlappende areal. Hvis det finnes to ulike arealer med og uten
-bygninger så blir fargen lilla, ellers blir fargen sterkere enn hvis
-det bare et gårds- og bruksnummer for et gitt areal. Jeg antar dette
-kommer av utdatert informasjon i oversikten fra kommunen kombinert med
-tilgang på geografisk informasjon om ikke lenger gjeldende tomter i
-Matrikkelen, for eksempel ved at en eiendom er delt i flere biter, og
-kommunens oversikt inneholder oppføring av gårds- og bruksnummer før
-og etter oppdeling. Hver av disse bør undersøkes og korrigeres
-individuelt, men i og med at jeg ikke har mulighet til å fikse feil
-hos hverken kommunen eller kartverket har jeg ikke brukt tid på
-dette.</p>
-
-<p>Det norske eiendomsregisteret, Matrikkelen, endres hele tiden. Det
-skjer blant annet ved ved fradeling og sammenslåing. Fire år er lang
-tid i så måte. Jeg antar det kan forklare noen av eiendommene
-kommunen hevder å eie som mangler informasjon i Matrikkelen, men neppe
-alle. Noen av dem er nok også feil i kommunens datasett.
-Utfordringen er å finne hvilke det gjelder. Hvis du har lyst til å se
-på detaljene, så er lenker til aktuelle gårds- og bruksnummer for de
-to problematiske kategoriene samlet under.</p>
-
-<p>Et eksempel i så måte er
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/11/0/0">0301-999/11</a>,
-som kommunens oversikt forteller er "GULLKROKEN 4M IKKE TINGLYST VEI"
-med Bymiljøetaten som ansvarlig etat, og kartverket sier er 0
-kvadratmeter og uten registrerte teiger. Mitt gjett her er at
-kommunen ikke har registrert det jeg mistenker kan være veien til
-husene i lokalområdet i Matrikkelen, det vil si veien er fradelt fra
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/244/0/0">0301-31/244</a>,
-og at kommunen så langt ikke har registrert teigen i Matrikkelen, men
-kan ikke vite sikkert. Det virker litt rart at det ikke er gjort på de fire årene som har gått siden oversikten fra kommunen ble publisert.</p>
-
-<p>Dette er de 268 gårds- og bruksnummerene uten informasjon om
-geografisk posisjon i Matrikkelen:
-<a href="https://seeiendom.kartverket.no/eiendom/0301/2/173/0/0">2/173</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/2/174/0/0">2/174</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/2/384/0/0">2/384</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/2/58/0/0">2/58</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/3/133/0/0">3/133</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/3/164/0/0">3/164</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/3/346/0/0">3/346</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/3/347/0/0">3/347</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/3/348/0/0">3/348</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/3/349/0/0">3/349</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/3/368/0/0">3/368</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/3/635/0/0">3/635</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/5/14/0/0">5/14</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/5/64/0/0">5/64</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/5/78/0/0">5/78</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/6/187/0/0">6/187</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/6/219/0/0">6/219</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/6/25/0/0">6/25</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/6/56/0/0">6/56</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/6/59/0/0">6/59</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/9/147/0/0">9/147</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/9/149/0/0">9/149</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/9/155/0/0">9/155</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/9/156/0/0">9/156</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/9/158/0/0">9/158</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/9/159/0/0">9/159</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/10/385/0/0">10/385</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/10/445/0/0">10/445</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/27/2382/0/0">27/2382</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/27/677/0/0">27/677</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/27/716/0/0">27/716</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/27/75/0/0">27/75</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/430/0/0">28/430</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/30/47/0/0">30/47</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/194/0/0">31/194</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/195/0/0">31/195</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1083/0/0">33/1083</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/11/0/0">33/11</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1194/0/0">33/1194</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1195/0/0">33/1195</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1196/0/0">33/1196</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1197/0/0">33/1197</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1198/0/0">33/1198</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1199/0/0">33/1199</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1239/0/0">33/1239</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/330/0/0">33/330</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/345/0/0">33/345</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/346/0/0">33/346</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/347/0/0">33/347</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/348/0/0">33/348</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/458/0/0">33/458</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/512/0/0">33/512</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/34/3/0/0">34/3</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/35/435/0/0">35/435</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/35/675/0/0">35/675</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/36/185/0/0">36/185</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/36/38/0/0">36/38</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/37/101/0/0">37/101</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/37/25/0/0">37/25</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/38/203/0/0">38/203</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/38/234/0/0">38/234</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/38/235/0/0">38/235</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/41/193/0/0">41/193</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/41/381/0/0">41/381</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/41/406/0/0">41/406</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/47/19/0/0">47/19</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/47/2/0/0">47/2</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/47/75/0/0">47/75</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/47/76/0/0">47/76</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/49/3/0/0">49/3</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/50/10/0/0">50/10</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/50/11/0/0">50/11</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/50/12/0/0">50/12</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/50/13/0/0">50/13</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/50/233/0/0">50/233</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/50/9/0/0">50/9</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/52/1143/0/0">52/1143</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/53/253/0/0">53/253</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/53/35/0/0">53/35</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/54/264/0/0">54/264</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/54/265/0/0">54/265</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/57/279/0/0">57/279</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/57/297/0/0">57/297</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/58/173/0/0">58/173</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/58/196/0/0">58/196</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/58/197/0/0">58/197</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/59/239/0/0">59/239</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/59/66/0/0">59/66</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/64/9/0/0">64/9</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/65/20/0/0">65/20</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/66/15/0/0">66/15</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/66/22/0/0">66/22</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/69/15/0/0">69/15</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/69/20/0/0">69/20</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/69/38/0/0">69/38</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/69/39/0/0">69/39</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/69/40/0/0">69/40</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/69/41/0/0">69/41</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/69/42/0/0">69/42</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/69/43/0/0">69/43</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/70/3/0/0">70/3</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/70/4/0/0">70/4</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/70/6/0/0">70/6</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/72/182/0/0">72/182</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/72/25/0/0">72/25</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/72/26/0/0">72/26</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/72/27/0/0">72/27</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/313/0/0">73/313</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/638/0/0">73/638</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/673/0/0">73/673</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/719/0/0">73/719</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/74/8/0/0">74/8</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/77/153/0/0">77/153</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/77/154/0/0">77/154</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/77/155/0/0">77/155</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/77/156/0/0">77/156</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/77/157/0/0">77/157</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/77/22/0/0">77/22</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/79/25/0/0">79/25</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/79/74/0/0">79/74</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/86/50/0/0">86/50</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/86/513/0/0">86/513</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/86/515/0/0">86/515</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/88/209/0/0">88/209</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/88/210/0/0">88/210</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/88/211/0/0">88/211</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/90/536/0/0">90/536</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/158/0/0">93/158</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/200/0/0">93/200</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/204/0/0">93/204</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/205/0/0">93/205</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/207/0/0">93/207</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/208/0/0">93/208</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/217/0/0">93/217</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/218/0/0">93/218</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/351/0/0">93/351</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/5/0/0">93/5</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/603/0/0">93/603</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/94/531/0/0">94/531</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/94/81/0/0">94/81</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/95/16/0/0">95/16</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/96/180/0/0">96/180</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/97/44/0/0">97/44</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/98/12/0/0">98/12</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/98/13/0/0">98/13</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/98/14/0/0">98/14</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/98/19/0/0">98/19</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/102/424/0/0">102/424</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/102/447/0/0">102/447</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/104/6/0/0">104/6</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/105/188/0/0">105/188</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/105/189/0/0">105/189</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/107/167/0/0">107/167</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/109/3/0/0">109/3</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/112/24/0/0">112/24</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/112/27/0/0">112/27</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/114/23/0/0">114/23</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/120/13/0/0">120/13</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/122/19/0/0">122/19</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/122/25/0/0">122/25</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/122/369/0/0">122/369</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/126/95/0/0">126/95</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/126/96/0/0">126/96</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/126/97/0/0">126/97</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/127/11/0/0">127/11</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/127/67/0/0">127/67</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/131/31/0/0">131/31</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/137/121/0/0">137/121</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/138/16/0/0">138/16</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/140/120/0/0">140/120</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/141/26/0/0">141/26</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/692/0/0">144/692</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/200/0/0">146/200</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/201/0/0">146/201</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/202/0/0">146/202</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/203/0/0">146/203</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/204/0/0">146/204</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/205/0/0">146/205</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/206/0/0">146/206</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/207/0/0">146/207</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/208/0/0">146/208</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/209/0/0">146/209</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/210/0/0">146/210</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/211/0/0">146/211</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/557/0/0">146/557</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/147/54/0/0">147/54</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/148/503/0/0">148/503</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/149/429/0/0">149/429</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/149/958/0/0">149/958</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/150/107/0/0">150/107</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/281/0/0">151/281</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/6/0/0">151/6</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/152/162/0/0">152/162</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/152/20/0/0">152/20</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/154/24/0/0">154/24</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/157/214/0/0">157/214</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/162/286/0/0">162/286</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/166/3/0/0">166/3</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/168/31/0/0">168/31</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/168/5/0/0">168/5</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/171/31/0/0">171/31</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/171/6/0/0">171/6</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/174/4/0/0">174/4</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/177/5/0/0">177/5</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/109/0/0">182/109</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/114/0/0">182/114</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/147/0/0">182/147</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/344/0/0">182/344</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/652/0/0">182/652</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/725/0/0">182/725</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/727/0/0">182/727</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/728/0/0">182/728</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/729/0/0">182/729</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/744/0/0">182/744</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/182/936/0/0">182/936</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/191/171/0/0">191/171</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/194/49/0/0">194/49</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/196/66/0/0">196/66</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/216/0/0">197/216</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/218/0/0">197/218</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/305/0/0">197/305</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/358/0/0">197/358</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/198/16/0/0">198/16</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/208/439/0/0">208/439</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/209/321/0/0">209/321</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/209/322/0/0">209/322</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/209/377/0/0">209/377</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/212/21/0/0">212/21</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/213/33/0/0">213/33</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/213/74/0/0">213/74</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/214/468/0/0">214/468</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/215/248/0/0">215/248</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/215/44/0/0">215/44</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/216/166/0/0">216/166</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/216/82/0/0">216/82</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/219/200/0/0">219/200</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/219/300/0/0">219/300</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/221/276/0/0">221/276</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/221/58/0/0">221/58</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/222/124/0/0">222/124</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/222/6/0/0">222/6</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/224/185/0/0">224/185</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/224/346/0/0">224/346</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/224/93/0/0">224/93</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/225/231/0/0">225/231</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/225/306/0/0">225/306</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/225/32/0/0">225/32</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/225/400/0/0">225/400</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/225/414/0/0">225/414</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/228/22/0/0">228/22</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/228/47/0/0">228/47</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/310/0/0">230/310</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/231/142/0/0">231/142</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/231/144/0/0">231/144</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/231/23/0/0">231/23</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/231/521/0/0">231/521</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/233/169/0/0">233/169</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/233/176/0/0">233/176</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/233/178/0/0">233/178</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/233/301/0/0">233/301</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/234/52/0/0">234/52</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/234/53/0/0">234/53</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/236/76/0/0">236/76</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/236/9/0/0">236/9</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/441/1/0/0">441/1</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/480/1/0/0">480/1</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/11/0/0">999/11</a> og
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/134/0/0">999/134</a></p>
-
-<p>Dette er de 346 gårds- og bruksnummerene som mangler i Matrikkelen
-(Matrikkelen sier "eiendommen er utgått"):
-<a href="https://seeiendom.kartverket.no/eiendom/0301/2/559/0/0">2/559</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/2/563/0/0">2/563</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/2/641/0/0">2/641</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/2/642/0/0">2/642</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/3/555/0/0">3/555</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/5/111/0/0">5/111</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/11/598/0/0">11/598</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/11/608/0/0">11/608</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/27/2113/0/0">27/2113</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/27/2261/0/0">27/2261</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/27/326/0/0">27/326</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/27/405/0/0">27/405</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/27/644/0/0">27/644</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/363/0/0">28/363</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/446/0/0">28/446</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/447/0/0">28/447</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/491/0/0">28/491</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/492/0/0">28/492</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/493/0/0">28/493</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/494/0/0">28/494</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/495/0/0">28/495</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/496/0/0">28/496</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/28/497/0/0">28/497</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/218/0/0">31/218</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/352/0/0">31/352</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/353/0/0">31/353</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/356/0/0">31/356</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/359/0/0">31/359</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/383/0/0">31/383</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/384/0/0">31/384</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/420/0/0">31/420</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/425/0/0">31/425</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/427/0/0">31/427</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/434/0/0">31/434</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/31/437/0/0">31/437</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/32/433/0/0">32/433</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/32/434/0/0">32/434</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/32/435/0/0">32/435</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/32/436/0/0">32/436</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/32/815/0/0">32/815</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1088/0/0">33/1088</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1224/0/0">33/1224</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1237/0/0">33/1237</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1238/0/0">33/1238</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1258/0/0">33/1258</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1339/0/0">33/1339</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1340/0/0">33/1340</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1341/0/0">33/1341</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/1342/0/0">33/1342</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/203/0/0">33/203</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/302/0/0">33/302</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/4/0/0">33/4</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/7/0/0">33/7</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/8/0/0">33/8</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/809/0/0">33/809</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/810/0/0">33/810</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/813/0/0">33/813</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/33/870/0/0">33/870</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/34/7/0/0">34/7</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/35/469/0/0">35/469</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/35/470/0/0">35/470</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/36/189/0/0">36/189</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/36/191/0/0">36/191</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/36/192/0/0">36/192</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/36/193/0/0">36/193</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/36/194/0/0">36/194</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/44/0/0/0">44/0</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/52/1109/0/0">52/1109</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/52/1197/0/0">52/1197</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/53/484/0/0">53/484</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/54/181/0/0">54/181</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/54/185/0/0">54/185</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/54/200/0/0">54/200</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/54/201/0/0">54/201</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/54/202/0/0">54/202</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/54/203/0/0">54/203</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/135/0/0">73/135</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/159/0/0">73/159</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/466/0/0">73/466</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/614/0/0">73/614</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/615/0/0">73/615</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/616/0/0">73/616</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/617/0/0">73/617</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/618/0/0">73/618</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/619/0/0">73/619</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/620/0/0">73/620</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/621/0/0">73/621</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/633/0/0">73/633</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/672/0/0">73/672</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/674/0/0">73/674</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/675/0/0">73/675</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/676/0/0">73/676</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/678/0/0">73/678</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/679/0/0">73/679</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/687/0/0">73/687</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/73/794/0/0">73/794</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/598/0/0">75/598</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/599/0/0">75/599</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/600/0/0">75/600</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/601/0/0">75/601</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/602/0/0">75/602</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/603/0/0">75/603</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/604/0/0">75/604</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/605/0/0">75/605</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/607/0/0">75/607</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/608/0/0">75/608</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/610/0/0">75/610</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/611/0/0">75/611</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/613/0/0">75/613</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/616/0/0">75/616</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/617/0/0">75/617</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/618/0/0">75/618</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/619/0/0">75/619</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/620/0/0">75/620</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/622/0/0">75/622</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/734/0/0">75/734</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/763/0/0">75/763</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/764/0/0">75/764</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/765/0/0">75/765</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/766/0/0">75/766</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/767/0/0">75/767</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/768/0/0">75/768</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/769/0/0">75/769</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/770/0/0">75/770</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/771/0/0">75/771</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/772/0/0">75/772</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/773/0/0">75/773</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/774/0/0">75/774</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/775/0/0">75/775</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/776/0/0">75/776</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/777/0/0">75/777</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/778/0/0">75/778</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/779/0/0">75/779</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/780/0/0">75/780</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/781/0/0">75/781</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/782/0/0">75/782</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/75/783/0/0">75/783</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/145/0/0">76/145</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/146/0/0">76/146</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/147/0/0">76/147</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/148/0/0">76/148</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/149/0/0">76/149</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/150/0/0">76/150</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/151/0/0">76/151</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/152/0/0">76/152</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/153/0/0">76/153</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/154/0/0">76/154</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/155/0/0">76/155</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/156/0/0">76/156</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/157/0/0">76/157</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/76/158/0/0">76/158</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/85/23/0/0">85/23</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/86/541/0/0">86/541</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/86/922/0/0">86/922</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/88/222/0/0">88/222</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/91/143/0/0">91/143</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/92/121/0/0">92/121</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/92/171/0/0">92/171</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/92/90/0/0">92/90</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/283/0/0">93/283</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/284/0/0">93/284</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/93/285/0/0">93/285</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/94/11/0/0">94/11</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/94/436/0/0">94/436</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/94/503/0/0">94/503</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/94/504/0/0">94/504</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/94/6/0/0">94/6</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/95/307/0/0">95/307</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/95/50/0/0">95/50</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/105/380/0/0">105/380</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/105/476/0/0">105/476</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/106/263/0/0">106/263</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/122/103/0/0">122/103</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/122/110/0/0">122/110</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/122/111/0/0">122/111</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/122/309/0/0">122/309</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/122/337/0/0">122/337</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/123/778/0/0">123/778</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/128/116/0/0">128/116</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/129/87/0/0">129/87</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/130/172/0/0">130/172</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/130/192/0/0">130/192</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/132/59/0/0">132/59</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/132/60/0/0">132/60</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/132/61/0/0">132/61</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/132/62/0/0">132/62</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/132/63/0/0">132/63</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/132/64/0/0">132/64</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/132/65/0/0">132/65</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/132/66/0/0">132/66</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/132/67/0/0">132/67</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/133/11/0/0">133/11</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/138/97/0/0">138/97</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/140/154/0/0">140/154</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/141/47/0/0">141/47</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/143/604/0/0">143/604</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/1064/0/0">144/1064</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/1357/0/0">144/1357</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/150/0/0">144/150</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/1895/0/0">144/1895</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/314/0/0">144/314</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/814/0/0">144/814</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/870/0/0">144/870</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/871/0/0">144/871</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/872/0/0">144/872</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/873/0/0">144/873</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/874/0/0">144/874</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/875/0/0">144/875</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/876/0/0">144/876</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/877/0/0">144/877</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/878/0/0">144/878</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/144/969/0/0">144/969</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/146/349/0/0">146/349</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/148/179/0/0">148/179</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/148/180/0/0">148/180</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/148/181/0/0">148/181</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/148/528/0/0">148/528</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/149/986/0/0">149/986</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/150/103/0/0">150/103</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/237/0/0">151/237</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/240/0/0">151/240</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/255/0/0">151/255</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/256/0/0">151/256</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/268/0/0">151/268</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/269/0/0">151/269</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/270/0/0">151/270</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/273/0/0">151/273</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/274/0/0">151/274</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/275/0/0">151/275</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/277/0/0">151/277</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/280/0/0">151/280</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/291/0/0">151/291</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/293/0/0">151/293</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/299/0/0">151/299</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/304/0/0">151/304</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/151/338/0/0">151/338</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/157/35/0/0">157/35</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/159/245/0/0">159/245</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/159/323/0/0">159/323</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/159/338/0/0">159/338</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/160/163/0/0">160/163</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/164/247/0/0">164/247</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/164/249/0/0">164/249</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/167/313/0/0">167/313</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/175/6/0/0">175/6</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/176/25/0/0">176/25</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/176/31/0/0">176/31</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/177/7/0/0">177/7</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/180/7/0/0">180/7</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/190/222/0/0">190/222</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/190/223/0/0">190/223</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/190/225/0/0">190/225</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/190/226/0/0">190/226</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/190/227/0/0">190/227</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/190/228/0/0">190/228</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/190/229/0/0">190/229</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/190/230/0/0">190/230</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/190/231/0/0">190/231</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/190/232/0/0">190/232</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/191/69/0/0">191/69</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/101/0/0">197/101</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/117/0/0">197/117</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/138/0/0">197/138</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/145/0/0">197/145</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/158/0/0">197/158</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/159/0/0">197/159</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/160/0/0">197/160</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/167/0/0">197/167</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/183/0/0">197/183</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/22/0/0">197/22</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/318/0/0">197/318</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/197/68/0/0">197/68</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/207/462/0/0">207/462</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/207/75/0/0">207/75</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/212/0/0/0">212/0</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/223/38/0/0">223/38</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/224/376/0/0">224/376</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/225/178/0/0">225/178</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/225/424/0/0">225/424</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/225/425/0/0">225/425</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/225/47/0/0">225/47</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/229/152/0/0">229/152</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/280/0/0">230/280</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/282/0/0">230/282</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/475/0/0">230/475</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/476/0/0">230/476</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/477/0/0">230/477</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/478/0/0">230/478</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/479/0/0">230/479</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/94/0/0">230/94</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/95/0/0">230/95</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/96/0/0">230/96</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/230/98/0/0">230/98</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/232/62/0/0">232/62</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/233/272/0/0">233/272</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/233/273/0/0">233/273</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/233/274/0/0">233/274</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/233/502/0/0">233/502</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/234/48/0/0">234/48</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/235/53/0/0">235/53</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/236/195/0/0">236/195</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/250/41/0/0">250/41</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/385/0/0/0">385/0</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/485/0/0/0">485/0</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/507/0/0/0">507/0</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/509/0/0/0">509/0</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/516/0/0/0">516/0</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/517/0/0/0">517/0</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/518/0/0/0">518/0</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/109/0/0">999/109</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/170/0/0">999/170</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/221/0/0">999/221</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/245/0/0">999/245</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/25/0/0">999/25</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/273/0/0">999/273</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/283/0/0">999/283</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/317/0/0">999/317</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/338/0/0">999/338</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/339/0/0">999/339</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/349/0/0">999/349</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/38/0/0">999/38</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/394/0/0">999/394</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/417/0/0">999/417</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/471/0/0">999/471</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/492/0/0">999/492</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/58/0/0">999/58</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/581/0/0">999/581</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/601/0/0">999/601</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/612/0/0">999/612</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/636/0/0">999/636</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/643/0/0">999/643</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/646/0/0">999/646</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/654/0/0">999/654</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/655/0/0">999/655</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/676/0/0">999/676</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/76/0/0">999/76</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/786/0/0">999/786</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/788/0/0">999/788</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/819/0/0">999/819</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/822/0/0">999/822</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/825/0/0">999/825</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/849/0/0">999/849</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/857/0/0">999/857</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/862/0/0">999/862</a>,
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/866/0/0">999/866</a> og
-<a href="https://seeiendom.kartverket.no/eiendom/0301/999/884/0/0">999/884</a></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>
-
-<p><strong>Oppdatering 2020-07-05</strong>: Ble tipset om offisielle
-kilder fra kommunens behandling. Vedtaket var del av sak 133 i
-<a href="https://www.oslo.kommune.no/dok/Finanskomiteen/2011_10/964872_11_1.PDF">protokoll
-fra finanskomiteens møte onsdag 19. oktober 2011 kl. 16:30</a>, og kom
-som resultat av følgende utveksling med
-<a href="https://www.oslo.kommune.no/dok/Vedlegg/2011_09/962186_1_1.PDF">spørsmål</a>
-og
-<a href="https://www.oslo.kommune.no/dok/Vedlegg/2011_10/963909_1_1.PDF">svar</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>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>
-
+ <title>Speech to text, she APTly whispered, how hard can it be?</title>
+ <link>https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html</link>
+ <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html</guid>
+ <pubDate>Sun, 23 Apr 2023 09:40:00 +0200</pubDate>
+ <description><p>While visiting a convention during Easter, it occurred to me that
+it would be great if I could have a digital Dictaphone with
+transcribing capabilities, providing me with texts to cut-n-paste into
+stuff I need to write. The background is that long drives often bring
+up the urge to write on texts I am working on, which of course is out
+of the question while driving. With the release of
+<a href="https://github.com/openai/whisper/">OpenAI Whisper</a>, this
+seem to be within reach with Free Software, so I decided to give it a
+go. OpenAI Whisper is a Linux based neural network system to read in
+audio files and provide text representation of the speech in that
+audio recording. It handle multiple languages and according to its
+creators even can translate into a different language than the spoken
+one. I have not tested the latter feature. It can either use the CPU
+or a GPU with CUDA support. As far as I can tell, CUDA in practice
+limit that feature to NVidia graphics cards. I have few of those, as
+they do not work great with free software drivers, and have not tested
+the GPU option. While looking into the matter, I did discover some
+work to provide CUDA support on non-NVidia GPUs, and some work with
+the library used by Whisper to port it to other GPUs, but have not
+spent much time looking into GPU support yet. I've so far used an old
+X220 laptop as my test machine, and only transcribed using its
+CPU.</p>
+
+<p>As it from a privacy standpoint is unthinkable to use computers
+under control of someone else (aka a "cloud" service) to transcribe
+ones thoughts and personal notes, I want to run the transcribing
+system locally on my own computers. The only sensible approach to me
+is to make the effort I put into this available for any Linux user and
+to upload the needed packages into Debian. Looking at Debian Bookworm, I
+discovered that only three packages were missing,
+<a href="https://bugs.debian.org/1034307">tiktoken</a>,
+<a href="https://bugs.debian.org/1034144">triton</a>, and
+<a href="https://bugs.debian.org/1034091">openai-whisper</a>. For a while
+I also believed
+<a href="https://bugs.debian.org/1034286">ffmpeg-python</a> was
+needed, but as its
+<a href="https://github.com/kkroening/ffmpeg-python/issues/760">upstream
+seem to have vanished</a> I found it safer
+<a href="https://github.com/openai/whisper/pull/1242">to rewrite
+whisper</a> to stop depending on in than to introduce ffmpeg-python
+into Debian. I decided to place these packages under the umbrella of
+<a href="https://salsa.debian.org/deeplearning-team">the Debian Deep
+Learning Team</a>, which seem like the best team to look after such
+packages. Discussing the topic within the group also made me aware
+that the triton package was already a future dependency of newer
+versions of the torch package being planned, and would be needed after
+Bookworm is released.</p>
+
+<p>All required code packages have been now waiting in
+<a href="https://ftp-master.debian.org/new.html">the Debian NEW
+queue</a> since Wednesday, heading for Debian Experimental until
+Bookworm is released. An unsolved issue is how to handle the neural
+network models used by Whisper. The default behaviour of Whisper is
+to require Internet connectivity and download the model requested to
+<tt>~/.cache/whisper/</tt> on first invocation. This obviously would
+fail <a href="https://people.debian.org/~bap/dfsg-faq.html">the
+deserted island test of free software</a> as the Debian packages would
+be unusable for someone stranded with only the Debian archive and solar
+powered computer on a deserted island.</p>
+
+<p>Because of this, I would love to include the models in the Debian
+mirror system. This is problematic, as the models are very large
+files, which would put a heavy strain on the Debian mirror
+infrastructure around the globe. The strain would be even higher if
+the models change often, which luckily as far as I can tell they do
+not. The small model, which according to its creator is most useful
+for English and in my experience is not doing a great job there
+either, is 462 MiB (deb is 414 MiB). The medium model, which to me
+seem to handle English speech fairly well is 1.5 GiB (deb is 1.3 GiB)
+and the large model is 2.9 GiB (deb is 2.6 GiB). I would assume
+everyone with enough resources would prefer to use the large model for
+highest quality. I believe the models themselves would have to go
+into the non-free part of the Debian archive, as they are not really
+including any useful source code for updating the models. The
+"source", aka the model training set, according to the creators
+consist of "680,000 hours of multilingual and multitask supervised
+data collected from the web", which to me reads material with both
+unknown copyright terms, unavailable to the general public. In other
+words, the source is not available according to the Debian Free
+Software Guidelines and the model should be considered non-free.</p>
+
+<p>I asked the Debian FTP masters for advice regarding uploading a
+model package on their IRC channel, and based on the feedback there it
+is still unclear to me if such package would be accepted into the
+archive. In any case I wrote build rules for a
+<a href="https://salsa.debian.org/deeplearning-team/openai-whisper-model">OpenAI
+Whisper model package</a> and
+<a href="https://github.com/openai/whisper/pull/1257">modified the
+Whisper code base</a> to prefer shared files under <tt>/usr/</tt> and
+<tt>/var/</tt> over user specific files in <tt>~/.cache/whisper/</tt>
+to be able to use these model packages, to prepare for such
+possibility. One solution might be to include only one of the models
+(small or medium, I guess) in the Debian archive, and ask people to
+download the others from the Internet. Not quite sure what to do
+here, and advice is most welcome (use the debian-ai mailing list).</p>
+
+<p>To make it easier to test the new packages while I wait for them to
+clear the NEW queue, I created an APT source targeting bookworm. I
+selected Bookworm instead of Bullseye, even though I know the latter
+would reach more users, is that some of the required dependencies are
+missing from Bullseye and I during this phase of testing did not want
+to backport a lot of packages just to get up and running.</p>
+
+<p>Here is a recipe to run as user root if you want to test OpenAI
+Whisper using Debian packages on your Debian Bookworm installation,
+first adding the APT repository GPG key to the list of trusted keys,
+then setting up the APT repository and finally installing the packages
+and one of the models:</p>
+
+<p><pre>
+curl https://geekbay.nuug.no/~pere/openai-whisper/D78F5C4796F353D211B119E28200D9B589641240.asc \
+ -o /etc/apt/trusted.gpg.d/pere-whisper.asc
+mkdir -p /etc/apt/sources.list.d
+cat > /etc/apt/sources.list.d/pere-whisper.list &lt;&lt;EOF
+deb https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
+deb-src https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
+EOF
+apt update
+apt install openai-whisper
+</pre></p>
+
+<p>The package work for me, but have not yet been tested on any other
+computer than my own. With it, I have been able to (badly) transcribe
+a 2 minute 40 second Norwegian audio clip to test using the small
+model. This took 11 minutes and around 2.2 GiB of RAM. Transcribing
+the same file with the medium model gave a accurate text in 77 minutes
+using around 5.2 GiB of RAM. My test machine had too little memory to
+test the large model, which I believe require 11 GiB of RAM. In
+short, this now work for me using Debian packages, and I hope it will
+for you and everyone else once the packages enter Debian.</p>
+
+<p>Now I can start on the audio recording part of this project.</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>
</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>
+ <title>rtlsdr-scanner, software defined radio frequency scanner for Linux - nice free software</title>
+ <link>https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html</link>
+ <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html</guid>
+ <pubDate>Fri, 7 Apr 2023 23:10:00 +0200</pubDate>
+ <description><p>Today I finally found time to track down a useful radio frequency
+scanner for my software defined radio. Just for fun I tried to locate
+the radios used in the areas, and a good start would be to scan all
+the frequencies to see what is in use. I've tried to find a useful
+program earlier, but ran out of time before I managed to find a useful
+tool. This time I was more successful, and after a few false leads I
+found a description of
+<a href="https://www.kali.org/tools/rtlsdr-scanner/">rtlsdr-scanner
+over at the Kali site</a>, and was able to track down
+<a href="https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git">the
+Kali package git repository</a> to build a deb package for the
+scanner. Sadly the package is missing from the Debian project itself,
+at least in Debian Bullseye. Two runtime dependencies,
+<a href="https://gitlab.com/kalilinux/packages/python-visvis.git">python-visvis</a>
+and
+<a href="https://gitlab.com/kalilinux/packages/python-rtlsdr.git">python-rtlsdr</a>
+had to be built and installed separately. Luckily '<tt>gbp
+buildpackage</tt>' handled them just fine and no further packages had
+to be manually built. The end result worked out of the box after
+installation.</p>
+
+<p>My initial scans for FM channels worked just fine, so I knew the
+scanner was functioning. But when I tried to scan every frequency
+from 100 to 1000 MHz, the program stopped unexpectedly near the
+completion. After some debugging I discovered USB software radio I
+used rejected frequencies above 948 MHz, triggering a unreported
+exception breaking the scan. Changing the scan to end at 957 worked
+better. I similarly found the lower limit to be around 15, and ended
+up with the following full scan:</p>
+
+<p><a href="https://people.skolelinux.org/pere/blog/images/2023-04-07-radio-freq-scanning.png"><img src="https://people.skolelinux.org/pere/blog/images/2023-04-07-radio-freq-scanning.png" width="100%"></a></p>
+
+<p>Saving the scan did not work, but exporting it as a CSV file worked
+just fine. I ended up with around 477k CVS lines with dB level for
+the given frequency.</p>
+
+<p>The save failure seem to be a missing UTF-8 encoding issue in the
+python code. Will see if I can find time to send a patch
+<a href="https://github.com/CdeMills/RTLSDR-Scanner/">upstream</a>
+later to fix this exception:</p>
+
+<pre>
+Traceback (most recent call last):
+ File "/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py", line 485, in __on_save
+ save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
+ File "/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py", line 408, in save_plot
+ handle.write(json.dumps(data, indent=4))
+TypeError: a bytes-like object is required, not 'str'
+Traceback (most recent call last):
+ File "/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py", line 485, in __on_save
+ save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
+ File "/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py", line 408, in save_plot
+ handle.write(json.dumps(data, indent=4))
+TypeError: a bytes-like object is required, not 'str'
+</pre>
<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>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>
-
+ <title>OpenSnitch available in Debian Sid and Bookworm</title>
+ <link>https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html</link>
+ <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html</guid>
+ <pubDate>Sat, 25 Feb 2023 20:30:00 +0100</pubDate>
+ <description><p>Thanks to the efforts of the OpenSnitch lead developer Gustavo
+Iñiguez Goya allowing me to sponsor the upload,
+<a href="https://tracker.debian.org/pkg/opensnitch">the interactive
+application firewall OpenSnitch</a> is now available in Debian
+Testing, soon to become the next stable release of Debian.</p>
+
+<p>This is a package which set up a network firewall on one or more
+machines, which is controlled by a graphical user interface that will
+ask the user if a program should be allowed to connect to the local
+network or the Internet. If some background daemon is trying to dial
+home, it can be blocked from doing so with a simple mouse click, or by
+default simply by not doing anything when the GUI question dialog pop
+up. A list of all programs discovered using the network is provided
+in the GUI, giving the user an overview of how the machine(s) programs
+use the network.</p>
+
+<p>OpenSnitch was uploaded for NEW processing about a month ago, and I
+had little hope of it getting accepted and shaping up in time for the
+package freeze, but the Debian ftpmasters proved to be amazingly quick
+at checking out the package and it was accepted into the archive about
+week after the first upload. It is now team maintained under the Go
+language team umbrella. A few fixes to the default setup is only in
+Sid, and should migrate to Testing/Bookworm in a week.</p>
+
+<p>During testing I ran into an
+<a href="https://github.com/evilsocket/opensnitch/issues/813">issue
+with Minecraft server broadcasts disappearing</a>, which was quickly
+resolved by the developer with a patch and a proposed configuration
+change. I've been told this was caused by the Debian packages default
+use if /proc/ information to track down kernel status, instead of the
+newer eBPF module that can be used. The reason is simply that
+upstream and I have failed to find a way to build the eBPF modules for
+OpenSnitch without a complete configured Linux kernel source tree,
+which as far as we can tell is unavailable as a build dependency in
+Debian. We tried unsuccessfully so far to use the kernel-headers
+package. It would be great if someone could provide some clues how to
+build eBPF modules on build daemons in Debian, possibly without the full
+kernel source.</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