blog/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="https://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="https://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="https://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="https://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21
  22     <div class="entry">
  23       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html">Time to move orphaned Debian packages to git</a></div>
  24       <div class="date">14th April 2024</div>
  25       <div class="body"><p>There are several packages in Debian without a associated git
  26 repository with the packaging history.  This is unfortunate and it
  27 would be nice if more of these would do so.  Quote a lot of these are
  28 without a maintainer, ie listed as maintained by the
  29 '<a href="https://qa.debian.org/developer.php?email=packages%40qa.debian.org">Debian
  30 QA Group</a>' place holder.  In fact, 438 packages have this property
  31 according to UDD (<tt>SELECT source FROM sources WHERE release = 'sid'
  32 AND (vcs_url ilike '%anonscm.debian.org%' OR vcs_browser ilike
  33 '%anonscm.debian.org%' or vcs_url IS NULL OR vcs_browser IS NULL) AND
  34 maintainer ilike '%packages@qa.debian.org%';</tt>).  Such packages can
  35 be updated without much coordination by any Debian developer, as they
  36 are considered orphaned.</p>
  37
  38 <p>To try to improve the situation and reduce the number of packages
  39 without associated git repository, I started a few days ago to search
  40 out candiates and provide them with a git repository under the
  41 'debian' collaborative Salsa project.  I started with the packages
  42 pointing to obsolete Alioth git repositories, and am now working my
  43 way across the ones completely without git references.  In addition to
  44 updating the Vcs-* debian/control fields, I try to update
  45 Standards-Version, debhelper compat level, simplify d/rules, switch to
  46 Rules-Requires-Root: no and fix lintian issues reported.  I only
  47 implement those that are trivial to fix, to avoid spending too much
  48 time on each orphaned package.  So far my experience is that it take
  49 aproximately 20 minutes to convert a package without any git
  50 references, and a lot more for packages with existing git repositories
  51 incompatible with git-buildpackages.</p>
  52
  53 <p>So far I have converted 10 packages, and I will keep going until I
  54 run out of steam.  As should be clear from the numbers, there is
  55 enough packages remaining for more people to do the same without
  56 stepping on each others toes.  I find it useful to start by searching
  57 for a git repo already on salsa, as I find that some times a git repo
  58 has already been created, but no new version is uploaded to Debian
  59 yet.  In those cases I start with the existing git repository.  I
  60 convert to the git-buildpackage+pristine-tar workflow, and ensure a
  61 debian/gbp.conf file with "pristine-tar=True" is added early, to avoid
  62 uploading a orig.tar.gz with the wrong checksum by mistake.  Did that
  63 three times in the begin before I remembered my mistake.</p>
  64
  65 <p>So, if you are a Debian Developer and got some spare time, perhaps
  66 considering migrating some orphaned packages to git?</p>
  67
  68 <p>As usual, if you use Bitcoin and want to show your support of my
  69 activities, please send Bitcoin donations to my address
  70 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
  71 </div>
  72       <div class="tags">
  73
  74
  75         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
  76
  77
  78       </div>
  79     </div>
  80     <div class="padding"></div>
  81
  82     <div class="entry">
  83       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Plain_text_accounting_file_from_your_bitcoin_transactions.html">Plain text accounting file from your bitcoin transactions</a></div>
  84       <div class="date"> 7th March 2024</div>
  85       <div class="body"><p>A while back I wrote a small script to extract the Bitcoin
  86 transactions in a wallet in the
  87 <ahref="https://plaintextaccounting.org/">ledger plain text accounting
  88 format</a>.  The last few days I spent some time to get it working
  89 better with more special cases.  In case it can be useful for others,
  90 here is a copy:</p>
  91
  92 <p><blockquote><pre>
  93 #!/usr/bin/python3
  94 #  -*- coding: utf-8 -*-
  95 #  Copyright (c) 2023-2024 Petter Reinholdtsen
  96
  97 from decimal import Decimal
  98 import json
  99 import subprocess
 100 import time
 101
 102 import numpy
 103
 104 def format_float(num):
 105     return numpy.format_float_positional(num, trim='-')
 106
 107 accounts = {
 108     u'amount' : 'Assets:BTC:main',
 109 }
 110
 111 addresses = {
 112     '<some address>' : 'Assets:bankkonto',
 113     '<some address>' : 'Assets:bankkonto',
 114 }
 115
 116 def exec_json(cmd):
 117     proc = subprocess.Popen(cmd,stdout=subprocess.PIPE)
 118     j = json.loads(proc.communicate()[0], parse_float=Decimal)
 119     return j
 120
 121 def list_txs():
 122     # get all transactions for all accounts / addresses
 123     c = 0
 124     txs = []
 125     txidfee = {}
 126     limit=100000
 127     cmd = ['bitcoin-cli', 'listtransactions', '*', str(limit)]
 128     if True:
 129         txs.extend(exec_json(cmd))
 130     else:
 131         # Useful for debugging
 132         with open('transactions.json') as f:
 133             txs.extend(json.load(f, parse_float=Decimal))
 134     #print txs
 135     for tx in sorted(txs, key=lambda a: a['time']):
 136 #        print tx['category']
 137         if 'abandoned' in tx and tx['abandoned']:
 138             continue
 139         if 'confirmations' in tx and 0 >= tx['confirmations']:
 140             continue
 141         when = time.strftime('%Y-%m-%d %H:%M', time.localtime(tx['time']))
 142         if 'message' in tx:
 143             desc = tx['message']
 144         elif 'comment' in tx:
 145             desc = tx['comment']
 146         elif 'label' in tx:
 147             desc = tx['label']
 148         else:
 149             desc = 'n/a'
 150         print("%s %s" % (when, desc))
 151         if 'address' in tx:
 152             print("  ; to bitcoin address %s" % tx['address'])
 153         else:
 154             print("  ; missing address in transaction, txid=%s" % tx['txid'])
 155         print(f"  ; amount={tx['amount']}")
 156         if 'fee'in tx:
 157             print(f"  ; fee={tx['fee']}")
 158         for f in accounts.keys():
 159             if f in tx and Decimal(0) != tx[f]:
 160                 amount = tx[f]
 161                 print("  %-20s   %s BTC" % (accounts[f], format_float(amount)))
 162         if 'fee' in tx and Decimal(0) != tx['fee']:
 163             # Make sure to list fee used in several transactions only once.
 164             if 'fee' in tx and tx['txid'] in txidfee \
 165                and tx['fee'] == txidfee[tx['txid']]:
 166                 True
 167             else:
 168                 fee = tx['fee']
 169                 print("  %-20s   %s BTC" % (accounts['amount'], format_float(fee)))
 170                 print("  %-20s   %s BTC" % ('Expences:BTC-fee', format_float(-fee)))
 171                 txidfee[tx['txid']] = tx['fee']
 172
 173         if 'address' in tx and tx['address'] in addresses:
 174             print("  %s" % addresses[tx['address']])
 175         else:
 176             if 'generate' == tx['category']:
 177                 print("  Income:BTC-mining")
 178             else:
 179                 if amount < Decimal(0):
 180                     print(f"  Assets:unknown:sent:update-script-addr-{tx['address']}")
 181                 else:
 182                     print(f"  Assets:unknown:received:update-script-addr-{tx['address']}")
 183
 184         print()
 185         c = c + 1
 186     print("# Found %d transactions" % c)
 187     if limit == c:
 188         print(f"# Warning: Limit {limit} reached, consider increasing limit.")
 189
 190 def main():
 191     list_txs()
 192
 193 main()
 194 </pre></blockquote></p>
 195
 196 <p>It is more of a proof of concept, and I do not expect it to handle
 197 all edge cases, but it worked for me, and perhaps you can find it
 198 useful too.</p>
 199
 200 <p>To get a more interesting result, it is useful to map accounts sent
 201 to or received from to accounting accounts, using the
 202 <tt>addresses</tt> hash.  As these will be very context dependent, I
 203 leave out my list to allow each user to fill out their own list of
 204 accounts.  Out of the box, 'ledger reg BTC:main' should be able to
 205 show the amount of BTCs present in the wallet at any given time in the
 206 past.  For other and more valuable analysis, a account plan need to be
 207 set up in the <tt>addresses</tt> hash.  Here is an example
 208 transaction:</p>
 209
 210 <p><blockquote><pre>
 211 2024-03-07 17:00 Donated to good cause
 212     Assets:BTC:main                           -0.1 BTC
 213     Assets:BTC:main                       -0.00001 BTC
 214     Expences:BTC-fee                       0.00001 BTC
 215     Expences:donations                         0.1 BTC
 216 </pre></blockquote></p>
 217
 218 <p>It need a running Bitcoin Core daemon running, as it connect to it
 219 using <tt>bitcoin-cli listtransactions * 100000</tt> to extract the
 220 transactions listed in the Wallet.</p>
 221
 222 <p>As usual, if you use Bitcoin and want to show your support of my
 223 activities, please send Bitcoin donations to my address
 224 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 225 </div>
 226       <div class="tags">
 227
 228
 229         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
 230
 231
 232       </div>
 233     </div>
 234     <div class="padding"></div>
 235
 236     <div class="entry">
 237       <div class="title"><a href="https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_using_free_software.html">RAID status from LSI Megaraid controllers using free software</a></div>
 238       <div class="date"> 3rd March 2024</div>
 239       <div class="body"><p>The last few days I have revisited RAID setup using the LSI
 240 Megaraid controller.  These are a family of controllers called PERC by
 241 Dell, and is present in several old PowerEdge servers, and I recently
 242 got my hands on one of these.  I had forgotten how to handle this RAID
 243 controller in Debian, so I had to take a peek in the
 244 <a href="https://wiki.debian.org/LinuxRaidForAdmins">Debian wiki page
 245 "Linux and Hardware RAID: an administrator's summary"</a> to remember
 246 what kind of software is available to configure and monitor the disks
 247 and controller.  I prefer Free Software alternatives to proprietary
 248 tools, as the later tend to fall into disarray once the manufacturer
 249 loose interest, and often do not work with newer Linux Distributions.
 250 Sadly there is no free software tool to configure the RAID setup, only
 251 to monitor it. RAID can provide improved reliability and resilience in
 252 a storage solution, but only if it is being regularly checked and any
 253 broken disks are being replaced in time.  I thus want to ensure some
 254 automatic monitoring is available.</p>
 255
 256 <p>In the discovery process, I came across a old free software tool to
 257 monitor PERC2, PERC3, PERC4 and PERC5 controllers, which to my
 258 surprise is not present in debian.  To help change that I created a
 259 <a href="https://bugs.debian.org/1065322">request for packaging of the
 260 megactl package</a>, and tried to track down a usable version.
 261 <a href="https://sourceforge.net/p/megactl/">The original project
 262 site</a> is on Sourceforge, but as far as I can tell that project has
 263 been dead for more than 15 years.  I managed to find a
 264 <a href="https://github.com/hmage/megactl">more recent fork on
 265 github</a> from user hmage, but it is unclear to me if this is still
 266 being maintained.  It has not seen much improvements since 2016.  A
 267 <a href="https://github.com/namiltd/megactl">more up to date
 268 edition</a> is a git fork from the original github fork by user
 269 namiltd, and this newer fork seem a lot more promising.  The owner of
 270 this github repository has replied to change proposals within hours,
 271 and had already added some improvements and support for more hardware.
 272 Sadly he is reluctant to commit to maintaining the tool and stated in
 273 <a href="https://github.com/namiltd/megactl/pull/1">my first pull
 274 request</A> that he think a new release should be made based on the
 275 git repository owned by hmage.  I perfectly understand this
 276 reluctance, as I feel the same about maintaining yet another package
 277 in Debian when I barely have time to take care of the ones I already
 278 maintain, but do not really have high hopes that hmage will have time
 279 to spend on it and hope namiltd will change his mind.</p>
 280
 281 <p>In any case, I created
 282 <a href="https://salsa.debian.org/debian/megactl">a draft package</a>
 283 based on the namiltd edition and put it under the debian group on
 284 salsa.debian.org.  If you own a Dell PowerEdge server with one of the
 285 PERC controllers, or any other RAID controller using the megaraid or
 286 megaraid_sas Linux kernel modules, you might want to check it out.  If
 287 enough people are interested, perhaps the package will make it into
 288 the Debian archive.</p>
 289
 290 <p>There are two tools provided, megactl for the megaraid Linux kernel
 291 module, and megasasctl for the megaraid_sas Linux kernel module. The
 292 simple output from the command on one of my machines look like this
 293 (yes, I know some of the disks have problems. :).</p>
 294
 295 <pre>
 296 # megasasctl
 297 a0       PERC H730 Mini           encl:1 ldrv:2  batt:good
 298 a0d0       558GiB RAID 1   1x2  optimal
 299 a0d1      3067GiB RAID 0   1x11 optimal
 300 a0e32s0     558GiB  a0d0  online   errs: media:0  other:19
 301 a0e32s1     279GiB  a0d1  online
 302 a0e32s2     279GiB  a0d1  online
 303 a0e32s3     279GiB  a0d1  online
 304 a0e32s4     279GiB  a0d1  online
 305 a0e32s5     279GiB  a0d1  online
 306 a0e32s6     279GiB  a0d1  online
 307 a0e32s8     558GiB  a0d0  online   errs: media:0  other:17
 308 a0e32s9     279GiB  a0d1  online
 309 a0e32s10    279GiB  a0d1  online
 310 a0e32s11    279GiB  a0d1  online
 311 a0e32s12    279GiB  a0d1  online
 312 a0e32s13    279GiB  a0d1  online
 313
 314 #
 315 </pre>
 316
 317 <p>In addition to displaying a simple status report, it can also test
 318 individual drives and print the various event logs.  Perhaps you too
 319 find it useful?</p>
 320
 321 <p>In the packaging process I provided some patches upstream to
 322 improve installation and ensure
 323 <ahref="https://github.com/namiltd/megactl/pull/2">a Appstream
 324 metainfo file is provided</a> to list all supported HW, to allow
 325 <a href="https://tracker.debian.org/isenkram">isenkram</a> to propose
 326 the package on all servers with a relevant PCI card.</p>
 327
 328 <p>As usual, if you use Bitcoin and want to show your support of my
 329 activities, please send Bitcoin donations to my address
 330 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 331
 332 </div>
 333       <div class="tags">
 334
 335
 336         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>, <a href="https://people.skolelinux.org/pere/blog/tags/raid">raid</a>.
 337
 338
 339       </div>
 340     </div>
 341     <div class="padding"></div>
 342
 343     <div class="entry">
 344       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Frokostseminar_om_Noark_5_i_Oslo_tirsdag_2024_03_12.html">Frokostseminar om Noark 5 i Oslo tirsdag 2024-03-12</a></div>
 345       <div class="date">27th February 2024</div>
 346       <div class="body"><p>Nikita-prosjektet, der jeg er involvert, inviterer i samarbeid med
 347 Oslo Byarkiv, forskningsgruppen METAINFO og foreningen NUUG, til et
 348 frokostseminar om Noark 5 og Noark 5 Tjenestegrensesnitt tirsdag
 349 2024-03-12.  Seminaret finner sted ved Oslo byarkiv.  Vi håper å få
 350 til videostrømming via Internett av presentasjoner og paneldiskusjon.
 351 Oppdatert program og lenker til påmeldingsskjema er
 352 <a href="https://noark.codeberg.page/noark5-seminars/2023-03-12-noark-workshop.html">tilgjengelig
 353 fra Nikita-prosjektet</a>.  Arrangementet er gratis.
 354
 355 <p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
 356 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
 357 til min adresse
 358 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. Merk,
 359 betaling med bitcoin er ikke anonymt. :)</p>
 360 </div>
 361       <div class="tags">
 362
 363
 364         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 365
 366
 367       </div>
 368     </div>
 369     <div class="padding"></div>
 370
 371     <div class="entry">
 372       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Welcome_out_of_prison__Mickey__hope_you_find_some_freedom_.html">Welcome out of prison, Mickey, hope you find some freedom!</a></div>
 373       <div class="date"> 1st January 2024</div>
 374       <div class="body"><p align="center"><img src="https://people.skolelinux.org/pere/blog/images/2024-01-01-mikke-verk-i-det-fri.jpeg"/></p>
 375
 376 <p>Today, the animation figure Mickey Mouse finally was released from
 377 the corporate copyright prison, as the 1928 movie
 378 <a href="https://en.wikipedia.org/wiki/Steamboat_Willie">Steamboat
 379 Willie</a> entered the public domain in USA.  This movie was the first
 380 public appearance of Mickey Mouse.  Sadly the figure is still on
 381 probation, thanks to trademark laws and a the Disney corporations
 382 powerful pack of lawyers, as described in the 2017 article
 383 in <a href="https://priceonomics.com/how-mickey-mouse-evades-the-public-domain/">"How
 384 Mickey Mouse Evades the Public Domain"</a> from Priceonomics.  On the
 385 positive side, the primary driver for repeated extentions of the
 386 duration of copyright has been Disney thanks to Mickey Mouse and the
 387 2028 movie, and as it now in the public domain I hope it will cause
 388 less urge to extend the already unreasonable long copyright
 389 duration.</p>
 390
 391 <p>The first book I published, the 2004 book <a
 392 href="https://free-culture.cc/">"Free Culture" by Lawrence Lessig</a>,
 393 published 2015 in
 394 <a href="https://people.skolelinux.org/pere/publisher/#frikultur">English,
 395 French and Norwegian Bokmål</a>, touch on the story of Disney pushed
 396 for extending the copyright duration in USA.  It is a great book
 397 explaining problems with the current copyright regime and why we need
 398 Creative Commons movement, and I strongly recommend everyone to read
 399 it.</p>
 400
 401 <p>This movie (with
 402 <a href="https://www.imdb.com/title/tt0019422/">IMDB ID tt0019422</a>)
 403 is now available from the Internet Archive.  Two copies have been
 404 uploaded so far, one uploaded
 405 <a href="https://archive.org/details/SteamboatWillie">2015-11-04</a>
 406 (<a href="https://archive.org/download/SteamboatWillie/SteamboatWillie_archive.torrent">torrent</a>)
 407 and the other
 408 <a href="https://archive.org/details/steamboat-willie-mickey">2023-01-01</a>
 409 (<a href="https://archive.org/download/steamboat-willie-mickey/steamboat-willie-mickey_archive.torrent">torrent</a>) - see
 410 <a href="https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html">VLC
 411 bittorrent plugin</a> for streaming the video using the torrent link.
 412 I am very happy to see
 413 <a href="https://people.skolelinux.org/pere/blog/Legal_to_share_more_than_16_000_movies_listed_on_IMDB_.html">the
 414 number of public domain movies</a> increasing.  I look forward to
 415 when those are the majority.  Perhaps it will reduce the urge of the
 416 copyright industry to control its customers.</p>
 417
 418 <p>A more
 419 <a href="https://publicdomainreview.org/features/entering-the-public-domain/2024/">comprehensive
 420 list of works entering the public domain in 2024</a> is available from
 421 the Public Domain Review.</p>
 422
 423 <p>As usual, if you use Bitcoin and want to show your support of my
 424 activities, please send Bitcoin donations to my address
 425 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 426 </div>
 427       <div class="tags">
 428
 429
 430         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>.
 431
 432
 433       </div>
 434     </div>
 435     <div class="padding"></div>
 436
 437     <div class="entry">
 438       <div class="title"><a href="https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html">VLC bittorrent plugin still going strong, new upload 2.14-4</a></div>
 439       <div class="date">31st December 2023</div>
 440       <div class="body"><p>The other day I uploaded a new version of
 441 <a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">the VLC
 442 bittorrent plugin</a> to Debian, version 2.14-4, to fix a few
 443 packaging issues.  This plugin extend VLC allowing it to stream videos
 444 directly from a bittorrent source using both torrent files and magnet
 445 links, as easy as using a HTTP or local file source.  I believe such
 446 protocol support is a vital feature in VLC, allowing efficient
 447 streaming from sources such at the 11 million movies in
 448 <a href="https://archive.org/">the Internet Archive</a>.  Bittorrent is
 449 one of the most efficient content distribution protocols on the
 450 Internet, without centralised control, and should be used more.</p>
 451
 452 <p>The new version is now both in Debian Unstable and Testing, as well
 453 as Ubuntu.  While looking after the package, I decided to ask the VLC
 454 upstream community if there was any hope to get Bittorrent support
 455 into the official VLC program, and was very happy to learn that
 456 someone is already working on it.  I hope we can see some fruits of
 457 that labour next year, but do not hold my breath.  In the mean time we
 458 can use the plugin, which is already
 459 <a href="https://qa.debian.org/popcon.php?package=vlc-plugin-bittorrent">installed
 460 by 0.23 percent of the Debian population</a> according to
 461 popularity-contest.  It could use a new upstream release, and I hope
 462 the upstream developer soon find time to polish it even more.</p>
 463
 464 <p>It is worth noting that the plugin store the downloaded files in
 465 <tt>~/Downloads/vlc-bittorrent/</tt>, which can quickly fill up the
 466 user home directory during use.  Users of the plugin should keep an
 467 eye with disk usage when streaming a bittorrent source.</p>
 468
 469 <p>As usual, if you use Bitcoin and want to show your support of my
 470 activities, please send Bitcoin donations to my address
 471 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 472 </div>
 473       <div class="tags">
 474
 475
 476         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 477
 478
 479       </div>
 480     </div>
 481     <div class="padding"></div>
 482
 483     <div class="entry">
 484       <div class="title"><a href="https://people.skolelinux.org/pere/blog/_N_r__p___blir__p_____Et_reservoar_av_tegn_sett_fra_depotet__i_tidsskriftet_Aksess.html">«Når «på» blir «pÃ¥»: Et reservoar av tegn sett fra depotet» i tidsskriftet Aksess</a></div>
 485       <div class="date">15th November 2023</div>
 486       <div class="body"><p>For noen uker siden skrev en kamerat og meg
 487 <a href="https://www.aksess-tidsskrift.no/fordypning/175530">en
 488 artikkel om tegnsett</a> i
 489 <a href="https://www.aksess-tidsskrift.no/">arkivtidsskriftet
 490 Aksess</a> både på web og i papirutgave nr. 3 2023.  Her er det som
 491 nettopp ble publisert.</p>
 492
 493 <blockquote>
 494
 495 <p><strong>Når «på» blir «pÃ¥»: Et reservoar av tegn sett fra
 496 depotet</strong></p>
 497
 498 <p>av Thomas Sødring og Petter Reinholdtsen</p>
 499
 500 <p>De færreste av oss tenker over hva som skjer dypere i datamaskinen
 501 mens vi sitter der og skriver noe på tastaturet. Når du trykker på
 502 tasten «Å», så vises bokstaven Å. Men noen ganger blir det
 503 feil. Hvorfor det – og hva er viktig å være klar over i
 504 arkivsammenheng?</p>
 505
 506 <p>Dersom bokstaver tolkes forskjellig mellom systemer, blir det fort
 507 rot, dette kalles mojibake blant kjennere, etter det japanske
 508 uttrykket for tegnomforming. Det er en lang historie her som tidvis
 509 har vært preget av rot.  Noen husker kanskje tilbake til en tid der
 510 bokstavene æ, ø og å ofte var ødelagt i e-poster – et klassisk
 511 eksempel på tegnsettproblemstilling.</p>
 512
 513 <p id="tegnsett_access_nå_og_før"><strong>«Nå» og «før»</strong></p>
 514
 515 <p>Tid er et skjult problem for depot fordi vi danner dokumentasjon i
 516 en kontekst som er preget av å være «nå».  Vår forståelse av verden og
 517 bruken av teknologi er utgangspunktet for denne konteksten. Tenk selv
 518 hvordan verden har utviklet seg de siste 20 årene, hva samfunnet er
 519 opptatt av, og hvordan vi bruker teknologi i hverdagen. Tid er et
 520 skjult problem fordi når vi trekker dokumentasjon ut av systemer og
 521 deponerer for langtidsbevaring, er konteksten til materialet «nå», men
 522 verden går videre. Ettersom teknologien og måten vi bruker den på,
 523 utvikler seg, blir «nå» til «før», og dokumentasjonen befinner seg
 524 snart i en «før»-kontekst.</p>
 525
 526 <p>Dette med «før» og «nå» i forhold til dokumentasjonens kontekst er
 527 noe vi er veldig lite bevisste på, men det er en problemstilling
 528 depotarkivene eier og forvalter.  En av disse utfordringene er hvorfor
 529 «Ø» ikke nødvendigvis er det samme som «Ø», og hvorfor det i det hele
 530 tatt gir mening å si noe sånt. Vi snakker her om noe som heter
 531 tegnsett, som er en avtalt måte å representere bokstaver, tall og
 532 andre symboler på slik at vi på en feilfri måte kan utveksle tekst
 533 mellom datasystemer.</p>
 534
 535 <p>Tegnsettproblemstillingen er satt sammen av fire fasetter;
 536 repertoar, representasjon, koding og uttegning.</p>
 537
 538 <p id="tegnsett_access_repertoarer"><strong>Repertoarer</strong></p>
 539
 540 <p>Repertoar er en samling med tegn og symboler som kan
 541 representeres. Tenk norsk alfabet eller japanske piktogrammer, men
 542 også matematiske og elektroniske symboler. Bokstaven «stor a» kan være
 543 en oppføring i et slikt repertoar. For å kunne brukes i en datamaskin
 544 trenger hver oppføring i et slikt repertoar en representasjon, hvilket
 545 i datamaskinsammenheng betyr at det tilordnes et tall. Tallet kan
 546 lagres på ulike vis i en eller flere kodingsformater. For eksempel kan
 547 en skrive tallet ti som både 10, X og A, i henholdsvis
 548 titallssystemet, romertallssystemet og sekstentallssystemet.</p>
 549
 550 <p>Hvis en skal kunne lese inn filer og vite hvilket tall og hvilken
 551 representasjon og instans i et repertoar det er snakk om, så må en
 552 vite hvordan tallet er kodet. Sist, men ikke minst, for å kunne bruke
 553 symbolet til noe må det kunne være kjent hvordan det skal se ut eller
 554 tegnes på ark. Det finnes utallige skrifttyper med norske bokstaver,
 555 alle litt forskjellige, og skal en kunne tegne en stor A på skjermen,
 556 så må datamaskinen vite hva den skal tegne. Skrifttyper inneholder
 557 informasjon om hvordan ulike tall skal tegnes. De inneholder ikke
 558 alltid alle symbolene som er brukt i en tekst, hvilket gjør at ikke
 559 alle forståtte tegn vil kunne vises på skjerm eller ark.</p>
 560
 561 <p>Hver av disse fasettene må være avklart for å kunne ta vare på og vise
 562 frem tekst med en datamaskin. Kombinasjon av repertoar, representasjon
 563 og koding er det en kaller et tegnsett. Kombinasjonen av
 564 representasjon og uttegning kalles en skrifttype. De fleste
 565 skrifttyper har også informasjon om repertoar, men det finnes
 566 skrifttyper som kun kobler mellom tallkode og uttegning, uten å
 567 fortelle noe om hvordan tallkodene egentlig skal tolkes.</p>
 568
 569 <p id="tegnsett_access_fra_ascii_til_iso_8859"><strong>Fra ASCII til ISO-8859</strong></p>
 570
 571 <p>Vi begynner historien med ASCII (American Standard Code for
 572 Information Interchange) som har en historie som spores tilbake til
 573 1963. Utgangspunktet til ASCII var at det kunne kode opp til 128
 574 forskjellige symboler i vanlig bruk i USA. De visuelle symbolene i
 575 ASCII er de små og store bokstavene (a til z og A til Z), tall (0 til
 576 9) og tegnsettingssymboler (for eksempel semikolon, komma og
 577 punktum). ASCII har også noen usynlige symboler som ble brukt for
 578 bl.a. kommunikasjon. Før ASCII var det for eksempel teleks-tegnsett
 579 med plass til bare 32 tegn og EBCDIC med plass til 256 tegn, alle med
 580 en helt annen rekkefølge på symbolene enn ASCII, men de har vært lite
 581 brukt de siste femti årene. Et eksempel på noen utvalgte symboler i
 582 repertoaret til ASCII vises i tabell 1.</p>
 583
 584 <table align="center" width="50%">
 585
 586 <caption>Tabell 1. Eksempel på utvalgte symboler hentet fra
 587 ASCII-tegnsettet. Kolonnen «Binær» viser symbolets verdi i
 588 totallssystemet (1 og 0 tall), mens kolonnen «Desimal» viser symbolets
 589 verdi i titallssystemet.</caption>
 590
 591 <tbody>
 592 <tr>
 593 <th>Grafisk</th>
 594 <th>Binær</th>
 595 <th>Desimal</th>
 596 </tr>
 597 <tr>
 598 <td>A</td>
 599 <td>1000001</td>
 600 <td align="right">65</td>
 601 </tr>
 602 <tr>
 603 <td>M</td>
 604 <td>1001101</td>
 605 <td align="right">77</td>
 606 </tr>
 607 <tr>
 608 <td>Z</td>
 609 <td>1011010</td>
 610 <td align="right">90</td>
 611 </tr>
 612 <tr>
 613 <td>a</td>
 614 <td>1100001</td>
 615 <td align="right">97</td>
 616 </tr>
 617 <tr>
 618 <td>m</td>
 619 <td>1101101</td>
 620 <td align="right">109</td>
 621 </tr>
 622 <tr>
 623 <td>z</td>
 624 <td>1111010</td>
 625 <td align="right">122</td>
 626 </tr>
 627 <tr>
 628 <td>0</td>
 629 <td>0110000</td>
 630 <td align="right">48</td>
 631 </tr>
 632 <tr>
 633 <td>9</td>
 634 <td>0111001</td>
 635 <td align="right">58</td>
 636 </tr>
 637 <tr>
 638 <td>;</td>
 639 <td>0111011</td>
 640 <td align="right">59</td>
 641 </tr>
 642 </tbody>
 643 </table>
 644
 645 <p>Det opprinnelige ASCII-tegnsettet ble også omtalt som ASCII-7 og
 646 brukte 7 bits (0 og 1) for å representere symboler. Datamaskiner er
 647 ofte konfigurert til å jobbe med enheter der bits er gruppert som 4
 648 eller 8 bits . Det lå en mulighet i å ta i bruk bit åtte. En slik
 649 endring ville gjøre det mulig for datamaskiner å øke antall symboler
 650 de kunne representere, noe som ga en økning fra 128 forskjellige
 651 symboler til 256 forskjellige symboler. Det ble åpnet for å innlemme
 652 de nordiske bokstavene sammen med ASCII, og dette ble etter hvert
 653 standardisert som ISO-8859-1. Tabell 2 viser deler av ISO-8859-1 som
 654 støtter de norske bokstavene.</p>
 655
 656 <p>Det sier seg selv at muligheten til å representere inntil 256 symboler
 657 ikke holder når vi snakker om en global verden, og det ble gjort et
 658 standardiseringsløp som tok utgangspunkt i ASCII-7 med en utvidelse
 659 til å bruke den åttende biten for ulike språkgrupper. Denne standarden
 660 heter ISO-8859 og er inndelt i opptil 16 varianter, altså fra
 661 ISO-8859-1 til ISO-8859-16.</p>
 662
 663 <table align="center" width="50%">
 664
 665 <caption>Tabell 2. Koding av de norske symbolene slik de er definert i
 666 ISO-8859-1 tegnsettet.</caption>
 667
 668 <tbody>
 669 <tr>
 670 <th>Grafisk</th>
 671 <th>Binær</th>
 672 <th>Desimal</th>
 673 </tr>
 674 <tr>
 675 <td>Æ</td>
 676 <td>11000110</td>
 677 <td align="right">198</td>
 678 </tr>
 679 <tr>
 680 <td>Ø</td>
 681 <td>11011000</td>
 682 <td align="right">216</td>
 683 </tr>
 684 <tr>
 685 <td>Å</td>
 686 <td>11000101</td>
 687 <td align="right">197</td>
 688 </tr>
 689 <tr>
 690 <td>æ</td>
 691 <td>11100110</td>
 692 <td align="right">230</td>
 693 </tr>
 694 <tr>
 695 <td>ø</td>
 696 <td>11111000</td>
 697 <td align="right">248</td>
 698 </tr>
 699 <tr>
 700 <td>å</td>
 701 <td>11100101</td>
 702 <td align="right">229</td>
 703 </tr>
 704 </tbody>
 705 </table>
 706
 707 <p>Norske tegn er definert i ISO-8859-1, som også omtales som Latin 1, de
 708 fleste samiske tegn er definert i ISO-8859-4 (Latin 4) mens tilgang
 709 til €-symbolet kom med ISO-8859-15 (Latin 9). ISO-8859-15 er en
 710 revisjon av ISO-8859-1 som fjerner noen lite brukte symboler og
 711 erstatter bokstaver som er mer brukt, og introduserer €-symbolet.  Det
 712 er viktig å merke at alle ISO-8859-variantene har overlapp med
 713 ASCII-7, noe som ga samvirke med de engelskspråklige landene som ikke
 714 trengte å gjøre noe. Det innebærer også at de første 128 verdiene i
 715 ISO-8859-variantene representerer de samme symbolene. Det er først når
 716 du kommer til tolkningen av de resterende 128 verdiene med nummer 128
 717 til 255, at det oppsto tolkningsutfordringer mellom
 718 ISO-8859-variantene.</p>
 719
 720 <p>ISO-8859-verdenen fungerte godt så lenge tegnsettet som ble brukt når
 721 innhold ble skapt, også ble brukt når innhold ble gjengitt og du ikke
 722 trengte å kombinere innhold fra forskjellige tegnsett i samme
 723 dokument.  Utfordringen med bruken av ISO-8859-variantene ble raskt
 724 tydelig i en mer globalisert verden med utveksling av tekst på tvers
 725 av landegrenser der tekstlig innhold i dokumenter, e-poster og
 726 websider kunne bli skrevet med ett tegnsett og gjengitt med et annet
 727 tegnsett.</p>
 728
 729 <table align="center" width="60%">
 730
 731 <caption>Tabell 3. Viser tolkning av verdiene som er tilegnet de
 732 norske symbolene i ISO-8859-1 i de andre ISO 8859-variatene. Merk
 733 ISO-8859-12 ikke finnes da arbeidet ble avsluttet.<sup>[<a id="tegnsett_access_footnoteref_1" href="#tegnsett_access_footnotedef_1" title="View footnote.">1</a>]</sup></caption>
 734
 735 <tbody>
 736 <tr>
 737 <th>Binærverdi</th>
 738 <th>1</th>
 739 <th>2</th>
 740 <th>3</th>
 741 <th>4</th>
 742 <th>5</th>
 743 <th>6</th>
 744 <th>7</th>
 745 <th>8</th>
 746 <th>9</th>
 747 <th>10</th>
 748 <th>11</th>
 749 <th>13</th>
 750 <th>14</th>
 751 <th>15</th>
 752 <th>16</th>
 753 </tr>
 754 <tr>
 755 <td>11000110</td>
 756 <td>Æ</td>
 757 <td>Ć</td>
 758 <td>Ĉ</td>
 759 <td>Æ</td>
 760 <td>Ц</td>
 761 <td>ئ</td>
 762 <td>Ζ</td>
 763 <td></td>
 764 <td>Æ</td>
 765 <td>Æ</td>
 766 <td>ฦ</td>
 767 <td>Ę</td>
 768 <td>Æ</td>
 769 <td>Æ</td>
 770 <td>Æ</td>
 771 </tr>
 772 <tr>
 773 <td>11011000</td>
 774 <td>Ø</td>
 775 <td>Ř</td>
 776 <td>Ĝ</td>
 777 <td>Ø</td>
 778 <td>и</td>
 779 <td>ظ</td>
 780 <td>Ψ</td>
 781 <td></td>
 782 <td>Ø</td>
 783 <td>Ø</td>
 784 <td>ุ</td>
 785 <td>Ų</td>
 786 <td>Ø</td>
 787 <td>Ø</td>
 788 <td>Ű</td>
 789 </tr>
 790 <tr>
 791 <td>11000101</td>
 792 <td>Å</td>
 793 <td>Ĺ</td>
 794 <td>Ċ</td>
 795 <td>Å</td>
 796 <td>Х</td>
 797 <td>إ</td>
 798 <td>Ε</td>
 799 <td></td>
 800 <td>Å</td>
 801 <td>Å</td>
 802 <td>ล</td>
 803 <td>Å</td>
 804 <td>Å</td>
 805 <td>Å</td>
 806 <td>Ć</td>
 807 </tr>
 808 <tr>
 809 <td>11100110</td>
 810 <td>æ</td>
 811 <td>ć</td>
 812 <td>ĉ</td>
 813 <td>æ</td>
 814 <td>ц</td>
 815 <td>ن</td>
 816 <td>ζ</td>
 817 <td>ז</td>
 818 <td>æ</td>
 819 <td>æ</td>
 820 <td>ๆ</td>
 821 <td>ę</td>
 822 <td>æ</td>
 823 <td>æ</td>
 824 <td>v</td>
 825 </tr>
 826 <tr>
 827 <td>11111000</td>
 828 <td>ø</td>
 829 <td>ř</td>
 830 <td>ĝ</td>
 831 <td>ø</td>
 832 <td>ј</td>
 833 <td></td>
 834 <td>ψ</td>
 835 <td>ר</td>
 836 <td>ø</td>
 837 <td>ø</td>
 838 <td>๘</td>
 839 <td>ų</td>
 840 <td>ø</td>
 841 <td>ø</td>
 842 <td>ű</td>
 843 </tr>
 844 <tr>
 845 <td>11100101</td>
 846 <td>å</td>
 847 <td>ĺ</td>
 848 <td>ċ</td>
 849 <td>å</td>
 850 <td>х</td>
 851 <td>م</td>
 852 <td>ε</td>
 853 <td>ו</td>
 854 <td>å</td>
 855 <td>å</td>
 856 <td>ๅ</td>
 857 <td>å</td>
 858 <td>å</td>
 859 <td>å</td>
 860 <td>ć</td>
 861 </tr>
 862 </tbody>
 863 </table>
 864
 865 <p>Denne problemstillingen er illustrert i tabell 3, der vi ser verdiene
 866 tilegnet de norske symbolene i ISO-8859-1 i kolonne «1». I de øvrige
 867 kolonnene ser vi hvilket symbol verdien får i de andre
 868 ISO-8859-variantene. Tar vi utgangspunkt i tabell 3, kan vi se at
 869 ordet lærlingspørsmål gjengitt med ISO-8859-2 (kolonne 2) blir
 870 lćrlingspřrsmĺl, mens det blir lζrlingspψrsmεl med ISO- 8859-7
 871 (kolonne 7). Med ISO-8859-2 blir «æ» til «ć», «ø» til «ř» og «å» til
 872  «ĺ». I ISO-8859-7 blir «æ» til «ζ», «ø» til «ψ», mens «å» blir «ε».</p>
 873
 874 <p>Det er egentlig ingen utfordring med dette så lenge du vet hvilket
 875 tegnsett innholdet ditt er representert med, og det ikke har skjedd
 876 omforminger som du ikke er klar over. Det er det siste som er
 877 problematisk, spesielt de datasystemene som har vært i bruk de siste
 878 20 årene, som ikke har noe innebygd funksjonalitet for å forvalte
 879 tegnsettproblematikken. Et godt eksempel på dette er
 880 Microsoft-tegnsettet Windows-1252, som ble forvekslet som 100 %
 881 kompatibel med ISO-8859-1, men hadde byttet ut plassene fra 127 til
 882 159. Historisk vil det finnes en del variasjon i hvilket tegnsett som
 883 har vært i bruk, og hvor vellykket konvertering mellom tegnsett har
 884 vært.</p>
 885
 886 <p id="tegnsett_access_unicode_som_løsning"><strong>Unicode som løsning</strong></p>
 887
 888 <p>Tegnsettforvirring ble etter hvert et irritasjonsmoment og
 889 samvirkeproblem. Ofte fikk man en e-post der æøå var erstattet av rare
 890 symboler fordi e-posten hadde vært innom et eller annet datasystem som
 891 ikke brukte samme tegnsett.</p>
 892
 893 <p>For å løse dette samvirkeproblemet for tegnsett ble det startet et
 894 arbeid og en ny standard så dagens lys etter hvert. Denne standarden
 895 fikk navnet Unicode (ISO/ IEC 10646) og skulle resultere i et tegnsett
 896 som alle skulle være enige om. Unicode er et repertoar og en
 897 representasjon, dvs. navngivning og tilordning av tallverdi til alle
 898 symboler i bruk i verden i dag.  Oppføringer i Unicode skrives gjerne
 899 U+XXXX der XXXX er tallkoden i sekstentallssystemet som oppføringen
 900 har i Unicode-katalogen. Her finner vi tegn brukt av både levende og
 901 døde språk, konstruerte språk, tekniske symboler, morsomme tegninger
 902 (såkalte emojier) og tegn ingen vet hva betyr eller skal brukes
 903 til. Et morsomt eksempel er i nettartikkelen: U+237C ⍼ RIGHT ANGLE
 904 WITH DOWNWARDS ZIGZAG ARROW, av Jonathan Chan.<sup>[<a id="tegnsett_access_footnoteref_2" href="#tegnsett_access_footnotedef_2" title="View footnote.">2</a>]</sup></p>
 905
 906 <p>Sammen med Unicode kom det tre måter å kode disse tallene på; UTF-8,
 907 UTF-16 og UTF-32. Av datatekniske årsaker er UTF-8 mye brukt, spesielt
 908 når det gjelder utveksling av tekst over Internett, mens UTF-16 er
 909 brukt en del til tekstfiler lagret på Windows. En utfordring med
 910 Unicode og UTF-variantene er at disse gir flere måter å kode samme
 911 symbol på med en kombinasjonsmekanisme. Dette kan gi utfordringer ved
 912 søk, hvis en skal søke etter et ord som har ett eller flere symboler
 913 som kan skrives på ulikt vis, så er det ikke sikkert at søkesystemet
 914 vil finne alle forekomster. For eksempel kan bokstaven U+00F8 «Latin
 915 Small Letter O with Stroke» kodes som den tradisjonelle norske tegnet
 916 ø, men også som o kombinert med skråstrek U+0338. Begge deler er
 917 gyldig bruk av Unicode, selv om det er tradisjon for å foretrekke å
 918 «normalisere» kombinasjoner som enkelttegn der det er mulig, nettopp
 919 for å forenkle søk.</p>
 920
 921 <p id="tegnsett_access_bare_unicode_fremover"><strong>Bare Unicode fremover</strong></p>
 922
 923 <p>Forvaltningens bruk av tegnsett er regulert i Forskrift om
 924 IT-standarder i offentlig forvaltning<sup>[<a id="tegnsett_access_footnoteref_3" href="#tegnsett_access_footnotedef_3" title="View footnote.">3</a>]</sup>. Her står det: «Ved all
 925 utveksling av informasjon mellom forvaltningsorganer og fra
 926 forvaltningsorgan til innbyggere og næringsliv skal tegnsettstandarden
 927 ISO/IEC 10646 representert ved UTF8 benyttes.»  Det er forskjellige
 928 bruksområder til UTF-8, UTF-16 og UTF-32, men UTF-8 er kodingen vi
 929 kjenner mest til.  Det er flere grunner at UTF-8 «vant» konkurransen
 930 til å bli den utvalgte. Den kanskje viktigste er at UTF-8 er fullt
 931 samvirkende med ASCII-7, slik at den engelskspråklige delen av verden
 932 kunne rulle ut UTF-8 uten å merke noe forskjell. En tekstfil med kun
 933 ASCII-tekst vil være identisk på disken hvis den lagres som UTF-8 og
 934 ASCII. UTF-16 og UTF-32 byr på noen optimaliseringer som gjør dem
 935 relevant for spesifikke problemområder, men for det meste vil vi aldri
 936 oppleve disse standardene på nært hold i hverdagen. Det er uansett kun
 937 bruken av UTF-8 som er lovregulert i Norge.</p>
 938
 939 <p>Det er ikke slik at hele verden bruker ISO/IEC 10646 og UTF-8. Kina
 940 har egne standarder for tegnsett, mye brukt er GB 18030, som er
 941 Unicode med en annen koding enn UTF-8, mens Taiwan og andre asiatiske
 942 land gjerne bruker Big5 eller andre tegnsett.</p>
 943
 944 <p>UTF-8 er dominerende i Norge, men det er tidsperioder der forskjellige
 945 datasystemer utvekslet data i henhold til ISO-8859-1, ISO-8859-15,
 946 Windows-1252, Codepage 865 og ISO-646-60 / Codepage 1016 mens
 947 overgangen til UTF-8 pågikk. Det er ikke slik at et datasystem enkelt
 948 kan tvinges til å bruke et tegnsett, da det er flere lag i et
 949 datasystem som må settes opp til å bruke riktig tegnsett, og
 950 tegnsettproblemet fort oppstår når det er et eller annet i
 951 datasystemet som bruker feil tegnsett.</p>
 952
 953 <p>Et klassisk eksempel på problemet er en utveksling av tekst mellom to
 954 systemer der teksten i utgangspunktet er kodet i UTF-8, men går
 955 gjennom noe som er ISO-8859-1 underveis. Dette kan vises med at ordet
 956 «på» i et slik scenario ender opp som «pÃ¥». Det er mulig å spore
 957 dette tilbake til verdiene symbolene er tilordnet i tegnsettene. «på»
 958 blir til «pÃ¥» fordi «å» i UTF-8 er representert med U+C3AF, og dersom
 959 vi ser på hva disse verdiene representerer, ser vi at
 960 sekstentallssystemverdien C3 er 1100 0011 i totallssystemet og
 961 symbolet med dette tallet i ISO-8859-1 er Ã.</p>
 962
 963 <p>Vi ser det samme med sekstentallssystemverdien A5, som er 1010 0101 i
 964 totallssystemet, og tilsvarende symbol i ISO-8859-1 er ¥. Slik
 965 mojibake kan lett skje hvis «på» i utgangspunktet var representert med
 966 UTF-8, men ble behandlet med et system som bruker ISO-8859-1. Det er
 967 ingen automatikk i å fange opp slike ødeleggelser mens tekstlig
 968 innhold utveksles mellom datasystemer.</p>
 969
 970 <p>En utfordring for depotarkivene er at bruken av tegnsett ikke alltid
 971 har vært regulert, og at det kan finnes flere dokumentasjonssamlinger
 972 som er opprettet med varierende tegnsett før gjeldende forskrift
 973 inntraff – uten at det er mulig å avlede fra filene hvilket tegnsett
 974 som ble brukt. Et eksempel på dette er €-symbolet, som kom først etter
 975 at ISO-8859-1 var tatt i bruk. Det kan bli en utfordring for et
 976 depotarkiv, men så lenge det er kjent hvilket tegnsett var i bruk, så
 977 bør det gå bra.  Riksarkivarens
 978 forskrift<sup>[<a id="tegnsett_access_footnoteref_4" href="#tegnsett_access_footnotedef_4" title="View footnote.">4</a>]</sup>
 979 formaliserer dette ved å kreve følgende:</p>
 980
 981 <blockquote>
 982 <p>§ 5-11. Tegnsett i arkivuttrekk</p>
 983
 984 <ol>
 985   <li>Arkivuttrekk og medfølgende struktur- og innholdsbeskrivelser skal
 986       overføres som ren tekst i ukryptert form, og benytte godkjent
 987       tegnsett.</li>
 988
 989   <li>Godkjente tegnsett er:
 990     <ol>
 991       <li>Unicode UTF-8<br>
 992           (ISO/IEC 10646-1:2000 Annex D)</li>
 993       <li>ISO 8859-1:1998, Latin 1</li>
 994       <li>ISO 8859-4:1998, Latin 4 for samiske tegn.</li>
 995     </ol></li>
 996
 997   <li>Andre tegnsett aksepteres bare etter avtale med Arkivverket.</li>
 998 </ol>
 999 </blockquote>
1000
1001 <p id="tegnsett_access_ditt_ansvar"><strong>Ditt ansvar</strong></p>
1002
1003 <p>På mange måter burde ikke tegnsett være et problem i 2023, men sånn er
1004 det nok ikke. Land som har oppgradert til UTF-8 som primærtegnsett for
1005 utveksling av tekstlig innhold, begrenser problematikken betraktelig,
1006 men globalt sett så er tegnsettutfordringen ikke løst fordi ikke alle
1007 er enige om å bruke samme tegnsett.  Det kan være geopolitiske eller
1008 kulturelle hensyn som ligger til grunn for dette.</p>
1009
1010 <p>Det er uansett verdt å merke at selv om bruken av UTF-8 skulle bli
1011 100% utbredt, så er det et historisk perspektiv (ASCII-7,
1012 ISO-8859-variantene, UTF-8) her som gjør tegnsett til et problemområde
1013 arkivarene må forstå og håndtere.  Som danningsarkivar har du et
1014 ansvar for å vite hvilket tegnsett systemene og databasene dere
1015 forvalter, er i samsvar med. Det er noe IT-avdelingen din eller
1016 programvareleverandørene enkelt skal kunne svare på, og svaret skal
1017 være UTF-8 for alle nye systemer.</p>
1018
1019 <hr>
1020
1021 <p id="tegnsett_access_footnotedef_1"><a href="#tegnsett_access_footnoteref_1">1</a>. Tegnsettkilde <a href="https://en.wikipedia.org/wiki/ISO/IEC_8859">https://en.wikipedia.org/wiki/ISO/IEC_8859</a></p>
1022
1023 <p id="tegnsett_access_footnotedef_2"><a href="#tegnsett_access_footnoteref_2">2</a>. <a href="https://ionathan.ch/2022/04/09/angzarr.html">https://ionathan.ch/2022/04/09/angzarr.html</a></p>
1024
1025 <p id="tegnsett_access_footnotedef_3"><a href="#tegnsett_access_footnoteref_3">3</a>. <a href="https://lovdata.no/dokument/SF/forskrift/2013-04-05-959/%C2%A78#%C2%A78">https://lovdata.no/dokument/SF/forskrift/2013-04-05-959/%C2%A78#%C2%A78</a></p>
1026
1027 <p id="tegnsett_access_footnotedef_4"><a href="#tegnsett_access_footnoteref_4">4</a>. <a href="https://lovdata.no/forskrift/2017-12-19-2286/§5-11">https://lovdata.no/forskrift/2017-12-19-2286/§5-11</a></p>
1028
1029 </blockquote>
1030
1031 <p>For øvrig burde varsleren Edward Snowden få politisk asyl i Norge.</p>
1032
1033 <p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1034 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1035 til min adresse
1036 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. Merk,
1037 betaling med bitcoin er ikke anonymt. :)</p>
1038 </div>
1039       <div class="tags">
1040
1041
1042         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1043
1044
1045       </div>
1046     </div>
1047     <div class="padding"></div>
1048
1049     <div class="entry">
1050       <div class="title"><a href="https://people.skolelinux.org/pere/blog/New_and_improved_sqlcipher_in_Debian_for_accessing_Signal_database.html">New and improved sqlcipher in Debian for accessing Signal database</a></div>
1051       <div class="date">12th November 2023</div>
1052       <div class="body"><p>For a while now I wanted to have direct access to the
1053 <a href="https://signal.org/">Signal</a> database of messages and
1054 channels of my Desktop edition of Signal.  I prefer the enforced end
1055 to end encryption of Signal these days for my communication with
1056 friends and family, to increase the level of safety and privacy as
1057 well as raising the cost of the mass surveillance government and
1058 non-government entities practice these days.  In August I came across
1059 a nice
1060 <a href="https://www.yoranbrondsema.com/post/the-guide-to-extracting-statistics-from-your-signal-conversations/">recipe
1061 on how to use sqlcipher to extract statistics from the Signal
1062 database</a> explaining how to do this.  Unfortunately this did not
1063 work with the version of sqlcipher in Debian.  The
1064 <a href="http://tracker.debian.org/sqlcipher/">sqlcipher</a>
1065 package is a "fork" of the sqlite package with added support for
1066 encrypted databases.  Sadly the current Debian maintainer
1067 <a href="https://bugs.debian.org/961598">announced more than three
1068 years ago that he did not have time to maintain sqlcipher</a>, so it
1069 seemed unlikely to be upgraded by the maintainer.  I was reluctant to
1070 take on the job myself, as I have very limited experience maintaining
1071 shared libraries in Debian.  After waiting and hoping for a few
1072 months, I gave up the last  week, and set out to update the package.  In
1073 the process I orphaned it to make it more obvious for the next person
1074 looking at it that the package need proper maintenance.</p>
1075
1076 <p>The version in Debian was around five years old, and quite a lot of
1077 changes had taken place upstream into the Debian maintenance git
1078 repository.  After spending a few days importing the new upstream
1079 versions, realising that upstream did not care much for SONAME
1080 versioning as I saw library symbols being both added and removed with
1081 minor version number changes to the project, I concluded that I had to
1082 do a SONAME bump of the library package to avoid surprising the
1083 reverse dependencies.  I even added a simple
1084 autopkgtest script to ensure the package work as intended.  Dug deep
1085 into the hole of learning shared library maintenance, I set out a few
1086 days ago to upload the new version to Debian experimental to see what
1087 the quality assurance framework in Debian had to say about the result.
1088 The feedback told me the pacakge was not too shabby, and yesterday I
1089 uploaded the latest version to Debian unstable.  It should enter
1090 testing today or tomorrow, perhaps delayed by
1091 <a href="https://bugs.debian.org/1055812">a small library
1092 transition</a>.</p>
1093
1094 <p>Armed with a new version of sqlcipher, I can now have a look at the
1095 SQL database in ~/.config/Signal/sql/db.sqlite.  First, one need to
1096 fetch the encryption key from the Signal configuration using this
1097 simple JSON extraction command:</p>
1098
1099 <pre>/usr/bin/jq -r '."key"' ~/.config/Signal/config.json</pre>
1100
1101 <p>Assuming the result from that command is 'secretkey', which is a
1102 hexadecimal number representing the key used to encrypt the database.
1103 Next, one can now connect to the database and inject the encryption
1104 key for access via SQL to fetch information from the database.  Here
1105 is an example dumping the database structure:</p>
1106
1107 <pre>
1108 % sqlcipher ~/.config/Signal/sql/db.sqlite
1109 sqlite> PRAGMA key = "x'secretkey'";
1110 sqlite> .schema
1111 CREATE TABLE sqlite_stat1(tbl,idx,stat);
1112 CREATE TABLE conversations(
1113       id STRING PRIMARY KEY ASC,
1114       json TEXT,
1115
1116       active_at INTEGER,
1117       type STRING,
1118       members TEXT,
1119       name TEXT,
1120       profileName TEXT
1121     , profileFamilyName TEXT, profileFullName TEXT, e164 TEXT, serviceId TEXT, groupId TEXT, profileLastFetchedAt INTEGER);
1122 CREATE TABLE identityKeys(
1123       id STRING PRIMARY KEY ASC,
1124       json TEXT
1125     );
1126 CREATE TABLE items(
1127       id STRING PRIMARY KEY ASC,
1128       json TEXT
1129     );
1130 CREATE TABLE sessions(
1131       id TEXT PRIMARY KEY,
1132       conversationId TEXT,
1133       json TEXT
1134     , ourServiceId STRING, serviceId STRING);
1135 CREATE TABLE attachment_downloads(
1136     id STRING primary key,
1137     timestamp INTEGER,
1138     pending INTEGER,
1139     json TEXT
1140   );
1141 CREATE TABLE sticker_packs(
1142     id TEXT PRIMARY KEY,
1143     key TEXT NOT NULL,
1144
1145     author STRING,
1146     coverStickerId INTEGER,
1147     createdAt INTEGER,
1148     downloadAttempts INTEGER,
1149     installedAt INTEGER,
1150     lastUsed INTEGER,
1151     status STRING,
1152     stickerCount INTEGER,
1153     title STRING
1154   , attemptedStatus STRING, position INTEGER DEFAULT 0 NOT NULL, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync
1155       INTEGER DEFAULT 0 NOT NULL);
1156 CREATE TABLE stickers(
1157     id INTEGER NOT NULL,
1158     packId TEXT NOT NULL,
1159
1160     emoji STRING,
1161     height INTEGER,
1162     isCoverOnly INTEGER,
1163     lastUsed INTEGER,
1164     path STRING,
1165     width INTEGER,
1166
1167     PRIMARY KEY (id, packId),
1168     CONSTRAINT stickers_fk
1169       FOREIGN KEY (packId)
1170       REFERENCES sticker_packs(id)
1171       ON DELETE CASCADE
1172   );
1173 CREATE TABLE sticker_references(
1174     messageId STRING,
1175     packId TEXT,
1176     CONSTRAINT sticker_references_fk
1177       FOREIGN KEY(packId)
1178       REFERENCES sticker_packs(id)
1179       ON DELETE CASCADE
1180   );
1181 CREATE TABLE emojis(
1182     shortName TEXT PRIMARY KEY,
1183     lastUsage INTEGER
1184   );
1185 CREATE TABLE messages(
1186         rowid INTEGER PRIMARY KEY ASC,
1187         id STRING UNIQUE,
1188         json TEXT,
1189         readStatus INTEGER,
1190         expires_at INTEGER,
1191         sent_at INTEGER,
1192         schemaVersion INTEGER,
1193         conversationId STRING,
1194         received_at INTEGER,
1195         source STRING,
1196         hasAttachments INTEGER,
1197         hasFileAttachments INTEGER,
1198         hasVisualMediaAttachments INTEGER,
1199         expireTimer INTEGER,
1200         expirationStartTimestamp INTEGER,
1201         type STRING,
1202         body TEXT,
1203         messageTimer INTEGER,
1204         messageTimerStart INTEGER,
1205         messageTimerExpiresAt INTEGER,
1206         isErased INTEGER,
1207         isViewOnce INTEGER,
1208         sourceServiceId TEXT, serverGuid STRING NULL, sourceDevice INTEGER, storyId STRING, isStory INTEGER
1209         GENERATED ALWAYS AS (type IS 'story'), isChangeCreatedByUs INTEGER NOT NULL DEFAULT 0, isTimerChangeFromSync INTEGER
1210         GENERATED ALWAYS AS (
1211           json_extract(json, '$.expirationTimerUpdate.fromSync') IS 1
1212         ), seenStatus NUMBER default 0, storyDistributionListId STRING, expiresAt INT
1213         GENERATED ALWAYS
1214         AS (ifnull(
1215           expirationStartTimestamp + (expireTimer * 1000),
1216           9007199254740991
1217         )), shouldAffectActivity INTEGER
1218         GENERATED ALWAYS AS (
1219           type IS NULL
1220           OR
1221           type NOT IN (
1222             'change-number-notification',
1223             'contact-removed-notification',
1224             'conversation-merge',
1225             'group-v1-migration',
1226             'keychange',
1227             'message-history-unsynced',
1228             'profile-change',
1229             'story',
1230             'universal-timer-notification',
1231             'verified-change'
1232           )
1233         ), shouldAffectPreview INTEGER
1234         GENERATED ALWAYS AS (
1235           type IS NULL
1236           OR
1237           type NOT IN (
1238             'change-number-notification',
1239             'contact-removed-notification',
1240             'conversation-merge',
1241             'group-v1-migration',
1242             'keychange',
1243             'message-history-unsynced',
1244             'profile-change',
1245             'story',
1246             'universal-timer-notification',
1247             'verified-change'
1248           )
1249         ), isUserInitiatedMessage INTEGER
1250         GENERATED ALWAYS AS (
1251           type IS NULL
1252           OR
1253           type NOT IN (
1254             'change-number-notification',
1255             'contact-removed-notification',
1256             'conversation-merge',
1257             'group-v1-migration',
1258             'group-v2-change',
1259             'keychange',
1260             'message-history-unsynced',
1261             'profile-change',
1262             'story',
1263             'universal-timer-notification',
1264             'verified-change'
1265           )
1266         ), mentionsMe INTEGER NOT NULL DEFAULT 0, isGroupLeaveEvent INTEGER
1267         GENERATED ALWAYS AS (
1268           type IS 'group-v2-change' AND
1269           json_array_length(json_extract(json, '$.groupV2Change.details')) IS 1 AND
1270           json_extract(json, '$.groupV2Change.details[0].type') IS 'member-remove' AND
1271           json_extract(json, '$.groupV2Change.from') IS NOT NULL AND
1272           json_extract(json, '$.groupV2Change.from') IS json_extract(json, '$.groupV2Change.details[0].aci')
1273         ), isGroupLeaveEventFromOther INTEGER
1274         GENERATED ALWAYS AS (
1275           isGroupLeaveEvent IS 1
1276           AND
1277           isChangeCreatedByUs IS 0
1278         ), callId TEXT
1279         GENERATED ALWAYS AS (
1280           json_extract(json, '$.callId')
1281         ));
1282 CREATE TABLE sqlite_stat4(tbl,idx,neq,nlt,ndlt,sample);
1283 CREATE TABLE jobs(
1284         id TEXT PRIMARY KEY,
1285         queueType TEXT STRING NOT NULL,
1286         timestamp INTEGER NOT NULL,
1287         data STRING TEXT
1288       );
1289 CREATE TABLE reactions(
1290         conversationId STRING,
1291         emoji STRING,
1292         fromId STRING,
1293         messageReceivedAt INTEGER,
1294         targetAuthorAci STRING,
1295         targetTimestamp INTEGER,
1296         unread INTEGER
1297       , messageId STRING);
1298 CREATE TABLE senderKeys(
1299         id TEXT PRIMARY KEY NOT NULL,
1300         senderId TEXT NOT NULL,
1301         distributionId TEXT NOT NULL,
1302         data BLOB NOT NULL,
1303         lastUpdatedDate NUMBER NOT NULL
1304       );
1305 CREATE TABLE unprocessed(
1306         id STRING PRIMARY KEY ASC,
1307         timestamp INTEGER,
1308         version INTEGER,
1309         attempts INTEGER,
1310         envelope TEXT,
1311         decrypted TEXT,
1312         source TEXT,
1313         serverTimestamp INTEGER,
1314         sourceServiceId STRING
1315       , serverGuid STRING NULL, sourceDevice INTEGER, receivedAtCounter INTEGER, urgent INTEGER, story INTEGER);
1316 CREATE TABLE sendLogPayloads(
1317         id INTEGER PRIMARY KEY ASC,
1318
1319         timestamp INTEGER NOT NULL,
1320         contentHint INTEGER NOT NULL,
1321         proto BLOB NOT NULL
1322       , urgent INTEGER, hasPniSignatureMessage INTEGER DEFAULT 0 NOT NULL);
1323 CREATE TABLE sendLogRecipients(
1324         payloadId INTEGER NOT NULL,
1325
1326         recipientServiceId STRING NOT NULL,
1327         deviceId INTEGER NOT NULL,
1328
1329         PRIMARY KEY (payloadId, recipientServiceId, deviceId),
1330
1331         CONSTRAINT sendLogRecipientsForeignKey
1332           FOREIGN KEY (payloadId)
1333           REFERENCES sendLogPayloads(id)
1334           ON DELETE CASCADE
1335       );
1336 CREATE TABLE sendLogMessageIds(
1337         payloadId INTEGER NOT NULL,
1338
1339         messageId STRING NOT NULL,
1340
1341         PRIMARY KEY (payloadId, messageId),
1342
1343         CONSTRAINT sendLogMessageIdsForeignKey
1344           FOREIGN KEY (payloadId)
1345           REFERENCES sendLogPayloads(id)
1346           ON DELETE CASCADE
1347       );
1348 CREATE TABLE preKeys(
1349         id STRING PRIMARY KEY ASC,
1350         json TEXT
1351       , ourServiceId NUMBER
1352         GENERATED ALWAYS AS (json_extract(json, '$.ourServiceId')));
1353 CREATE TABLE signedPreKeys(
1354         id STRING PRIMARY KEY ASC,
1355         json TEXT
1356       , ourServiceId NUMBER
1357         GENERATED ALWAYS AS (json_extract(json, '$.ourServiceId')));
1358 CREATE TABLE badges(
1359         id TEXT PRIMARY KEY,
1360         category TEXT NOT NULL,
1361         name TEXT NOT NULL,
1362         descriptionTemplate TEXT NOT NULL
1363       );
1364 CREATE TABLE badgeImageFiles(
1365         badgeId TEXT REFERENCES badges(id)
1366           ON DELETE CASCADE
1367           ON UPDATE CASCADE,
1368         'order' INTEGER NOT NULL,
1369         url TEXT NOT NULL,
1370         localPath TEXT,
1371         theme TEXT NOT NULL
1372       );
1373 CREATE TABLE storyReads (
1374         authorId STRING NOT NULL,
1375         conversationId STRING NOT NULL,
1376         storyId STRING NOT NULL,
1377         storyReadDate NUMBER NOT NULL,
1378
1379         PRIMARY KEY (authorId, storyId)
1380       );
1381 CREATE TABLE storyDistributions(
1382         id STRING PRIMARY KEY NOT NULL,
1383         name TEXT,
1384
1385         senderKeyInfoJson STRING
1386       , deletedAtTimestamp INTEGER, allowsReplies INTEGER, isBlockList INTEGER, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync INTEGER);
1387 CREATE TABLE storyDistributionMembers(
1388         listId STRING NOT NULL REFERENCES storyDistributions(id)
1389           ON DELETE CASCADE
1390           ON UPDATE CASCADE,
1391         serviceId STRING NOT NULL,
1392
1393         PRIMARY KEY (listId, serviceId)
1394       );
1395 CREATE TABLE uninstalled_sticker_packs (
1396         id STRING NOT NULL PRIMARY KEY,
1397         uninstalledAt NUMBER NOT NULL,
1398         storageID STRING,
1399         storageVersion NUMBER,
1400         storageUnknownFields BLOB,
1401         storageNeedsSync INTEGER NOT NULL
1402       );
1403 CREATE TABLE groupCallRingCancellations(
1404         ringId INTEGER PRIMARY KEY,
1405         createdAt INTEGER NOT NULL
1406       );
1407 CREATE TABLE IF NOT EXISTS 'messages_fts_data'(id INTEGER PRIMARY KEY, block BLOB);
1408 CREATE TABLE IF NOT EXISTS 'messages_fts_idx'(segid, term, pgno, PRIMARY KEY(segid, term)) WITHOUT ROWID;
1409 CREATE TABLE IF NOT EXISTS 'messages_fts_content'(id INTEGER PRIMARY KEY, c0);
1410 CREATE TABLE IF NOT EXISTS 'messages_fts_docsize'(id INTEGER PRIMARY KEY, sz BLOB);
1411 CREATE TABLE IF NOT EXISTS 'messages_fts_config'(k PRIMARY KEY, v) WITHOUT ROWID;
1412 CREATE TABLE edited_messages(
1413         messageId STRING REFERENCES messages(id)
1414           ON DELETE CASCADE,
1415         sentAt INTEGER,
1416         readStatus INTEGER
1417       , conversationId STRING);
1418 CREATE TABLE mentions (
1419         messageId REFERENCES messages(id) ON DELETE CASCADE,
1420         mentionAci STRING,
1421         start INTEGER,
1422         length INTEGER
1423       );
1424 CREATE TABLE kyberPreKeys(
1425         id STRING PRIMARY KEY NOT NULL,
1426         json TEXT NOT NULL, ourServiceId NUMBER
1427         GENERATED ALWAYS AS (json_extract(json, '$.ourServiceId')));
1428 CREATE TABLE callsHistory (
1429         callId TEXT PRIMARY KEY,
1430         peerId TEXT NOT NULL, -- conversation id (legacy) | uuid | groupId | roomId
1431         ringerId TEXT DEFAULT NULL, -- ringer uuid
1432         mode TEXT NOT NULL, -- enum "Direct" | "Group"
1433         type TEXT NOT NULL, -- enum "Audio" | "Video" | "Group"
1434         direction TEXT NOT NULL, -- enum "Incoming" | "Outgoing
1435         -- Direct: enum "Pending" | "Missed" | "Accepted" | "Deleted"
1436         -- Group: enum "GenericGroupCall" | "OutgoingRing" | "Ringing" | "Joined" | "Missed" | "Declined" | "Accepted" | "Deleted"
1437         status TEXT NOT NULL,
1438         timestamp INTEGER NOT NULL,
1439         UNIQUE (callId, peerId) ON CONFLICT FAIL
1440       );
1441 [ dropped all indexes to save space in this blog post ]
1442 CREATE TRIGGER messages_on_view_once_update AFTER UPDATE ON messages
1443       WHEN
1444         new.body IS NOT NULL AND new.isViewOnce = 1
1445       BEGIN
1446         DELETE FROM messages_fts WHERE rowid = old.rowid;
1447       END;
1448 CREATE TRIGGER messages_on_insert AFTER INSERT ON messages
1449       WHEN new.isViewOnce IS NOT 1 AND new.storyId IS NULL
1450       BEGIN
1451         INSERT INTO messages_fts
1452           (rowid, body)
1453         VALUES
1454           (new.rowid, new.body);
1455       END;
1456 CREATE TRIGGER messages_on_delete AFTER DELETE ON messages BEGIN
1457         DELETE FROM messages_fts WHERE rowid = old.rowid;
1458         DELETE FROM sendLogPayloads WHERE id IN (
1459           SELECT payloadId FROM sendLogMessageIds
1460           WHERE messageId = old.id
1461         );
1462         DELETE FROM reactions WHERE rowid IN (
1463           SELECT rowid FROM reactions
1464           WHERE messageId = old.id
1465         );
1466         DELETE FROM storyReads WHERE storyId = old.storyId;
1467       END;
1468 CREATE VIRTUAL TABLE messages_fts USING fts5(
1469         body,
1470         tokenize = 'signal_tokenizer'
1471       );
1472 CREATE TRIGGER messages_on_update AFTER UPDATE ON messages
1473       WHEN
1474         (new.body IS NULL OR old.body IS NOT new.body) AND
1475          new.isViewOnce IS NOT 1 AND new.storyId IS NULL
1476       BEGIN
1477         DELETE FROM messages_fts WHERE rowid = old.rowid;
1478         INSERT INTO messages_fts
1479           (rowid, body)
1480         VALUES
1481           (new.rowid, new.body);
1482       END;
1483 CREATE TRIGGER messages_on_insert_insert_mentions AFTER INSERT ON messages
1484       BEGIN
1485         INSERT INTO mentions (messageId, mentionAci, start, length)
1486
1487     SELECT messages.id, bodyRanges.value ->> 'mentionAci' as mentionAci,
1488       bodyRanges.value ->> 'start' as start,
1489       bodyRanges.value ->> 'length' as length
1490     FROM messages, json_each(messages.json ->> 'bodyRanges') as bodyRanges
1491     WHERE bodyRanges.value ->> 'mentionAci' IS NOT NULL
1492
1493         AND messages.id = new.id;
1494       END;
1495 CREATE TRIGGER messages_on_update_update_mentions AFTER UPDATE ON messages
1496       BEGIN
1497         DELETE FROM mentions WHERE messageId = new.id;
1498         INSERT INTO mentions (messageId, mentionAci, start, length)
1499
1500     SELECT messages.id, bodyRanges.value ->> 'mentionAci' as mentionAci,
1501       bodyRanges.value ->> 'start' as start,
1502       bodyRanges.value ->> 'length' as length
1503     FROM messages, json_each(messages.json ->> 'bodyRanges') as bodyRanges
1504     WHERE bodyRanges.value ->> 'mentionAci' IS NOT NULL
1505
1506         AND messages.id = new.id;
1507       END;
1508 sqlite>
1509 </pre>
1510
1511 <p>Finally I have the tool needed to inspect and process Signal
1512 messages that I need, without using the vendor provided client.  Now
1513 on to transforming it to a more useful format.</p>
1514
1515 <p>As usual, if you use Bitcoin and want to show your support of my
1516 activities, please send Bitcoin donations to my address
1517 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
1518 </div>
1519       <div class="tags">
1520
1521
1522         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
1523
1524
1525       </div>
1526     </div>
1527     <div class="padding"></div>
1528
1529     <div class="entry">
1530       <div class="title"><a href="https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html">New chrpath release 0.17</a></div>
1531       <div class="date">10th November 2023</div>
1532       <div class="body"><p>The chrpath package provide a simple command line tool to remove or
1533 modify the rpath or runpath of compiled ELF program.  It is almost 10
1534 years since I updated the code base, but I stumbled over the tool
1535 today, and decided it was time to move the code base from Subversion
1536 to git and find a new home for it, as the previous one (Debian Alioth)
1537 has been shut down.  I decided to go with
1538 <a href="https://codeberg.org/">Codeberg</a> this time, as it is my git
1539 service of choice these days, did a quick and dirty migration to git
1540 and updated the code with a few patches I found in the Debian bug
1541 tracker.  These are the release notes:</p>
1542
1543 <p>New in 0.17 released 2023-11-10:</p>
1544
1545 <ul>
1546 <li>Moved project to Codeberg, as Alioth is shut down.</li>
1547 <li>Add Solaris support (use &lt;sys/byteorder.h> instead of &lt;byteswap.h>).
1548    Patch from Rainer Orth.</li>
1549 <li>Added missing newline from printf() line.  Patch from Frank Dana.</li>
1550 <li>Corrected handling of multiple ELF sections. Patch from Frank Dana.</li>
1551 <li>Updated build rules for .deb.  Partly based on patch from djcj.</li>
1552 </ul>
1553
1554 <p>The latest edition is tagged and available from
1555 <a href="https://codeberg.org/pere/chrpath">https://codeberg.org/pere/chrpath</a>.
1556
1557 <p>As usual, if you use Bitcoin and want to show your support of my
1558 activities, please send Bitcoin donations to my address
1559 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
1560 </div>
1561       <div class="tags">
1562
1563
1564         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/chrpath">chrpath</a>, <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
1565
1566
1567       </div>
1568     </div>
1569     <div class="padding"></div>
1570
1571     <div class="entry">
1572       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Test_framework_for_DocBook_processors___formatters.html">Test framework for DocBook processors / formatters</a></div>
1573       <div class="date"> 5th November 2023</div>
1574       <div class="body"><p>All the books I have published so far has been using
1575 <a href="https://docbook.org/">DocBook</a> somewhere in the process.
1576 For the first book, the source format was DocBook, while for every
1577 later book it was an intermediate format used as the stepping stone to
1578 be able to present the same manuscript in several formats, on paper,
1579 as ebook in ePub format, as a HTML page and as a PDF file either for
1580 paper production or for Internet consumption.  This is made possible
1581 with a wide variety of free software tools with DocBook support in
1582 Debian.  The source format of later books have been docx via rst,
1583 Markdown, Filemaker and Asciidoc, and for all of these I was able to
1584 generate a suitable DocBook file for further processing using
1585 <a href="https://tracker.debian.org/pkg/pandoc">pandoc</a>,
1586 <a href="https://tracker.debian.org/pkg/asciidoc">a2x</a> and
1587 <a href="https://tracker.debian.org/pkg/asciidoctor">asciidoctor</a>,
1588 as well as rendering using
1589 <a href="https://tracker.debian.org/pkg/xmlto">xmlto</a>,
1590 <a href="https://tracker.debian.org/pkg/dbtoepub">dbtoepub</a>,
1591 <a href="https://tracker.debian.org/pkg/dblatex">dblatex</a>,
1592 <a href="https://tracker.debian.org/pkg/docbook-xsl">docbook-xsl</a> and
1593 <a href="https://tracker.debian.org/pkg/fop">fop</a>.</p>
1594
1595 <p>Most of the <a href="http://www.hungry.com/~pere/publisher/">books I
1596 have published</a> are translated books, with English as the source
1597 language.  The use of
1598 <a href="https://tracker.debian.org/pkg/po4a">po4a</a> to
1599 handle translations using the gettext PO format has been a blessing,
1600 but publishing translated books had triggered the need to ensure the
1601 DocBook tools handle relevant languages correctly.  For every new
1602 language I have published, I had to submit patches dblatex, dbtoepub
1603 and docbook-xsl fixing incorrect language and country specific issues
1604 in the framework themselves.  Typically this has been missing keywords
1605 like 'figure' or sort ordering of index entries.  After a while it
1606 became tiresome to only discover issues like this by accident, and I
1607 decided to write a DocBook "test framework" exercising various
1608 features of DocBook and allowing me to see all features exercised for
1609 a given language.  It consist of a set of DocBook files, a version 4
1610 book, a version 5 book, a v4 book set, a v4 selection of problematic
1611 tables, one v4 testing sidefloat and finally one v4 testing a book of
1612 articles.  The DocBook files are accompanied with a set of build rules
1613 for building PDF using dblatex and docbook-xsl/fop, HTML using xmlto
1614 or docbook-xsl and epub using dbtoepub.  The result is a set of files
1615 visualizing footnotes, indexes, table of content list, figures,
1616 formulas and other DocBook features, allowing for a quick review on
1617 the completeness of the given locale settings.  To build with a
1618 different language setting, all one need to do is edit the lang= value
1619 in the .xml file to pick a different ISO 639 code value and run
1620 'make'.</p>
1621
1622 <p>The <a href="https://codeberg.org/pere/docbook-example/">test framework
1623 source code</a> is available from Codeberg, and a generated set of
1624 presentations of the various examples is available as Codeberg static
1625 web pages at
1626 <a href="https://pere.codeberg.page/docbook-example/">https://pere.codeberg.page/docbook-example/</a>.
1627 Using this test framework I have been able to discover and report
1628 several bugs and missing features in various tools, and got a lot of
1629 them fixed.  For example I got Northern Sami keywords added to both
1630 docbook-xsl and dblatex, fixed several typos in Norwegian bokmål and
1631 Norwegian Nynorsk, support for non-ascii title IDs added to pandoc,
1632 Norwegian index sorting support fixed in xindy and initial Norwegian
1633 Bokmål support added to dblatex.  Some issues still remains, though.
1634 Default index sorting rules are still broken in several tools, so the
1635 Norwegian letters æ, ø and å are more often than not sorted properly
1636 in the book index.</p>
1637
1638 <p>The test framework recently received some more polish, as part of
1639 publishing my latest book.  This book contained a lot of fairly
1640 complex tables, which exposed bugs in some of the tools.  This made me
1641 add a new test file with various tables, as well as spend some time to
1642 brush up the build rules.  My goal is for the test framework to
1643 exercise all DocBook features to make it easier to see which features
1644 work with different processors, and hopefully get them all to support
1645 the full set of DocBook features.  Feel free to send patches to extend
1646 the test set, and test it with your favorite DocBook processor.
1647 Please visit these two URLs to learn more:</p>
1648
1649 <ul>
1650 <li><a href="https://codeberg.org/pere/docbook-example/">https://codeberg.org/pere/docbook-example/</a></li>
1651 <li><a href="https://pere.codeberg.page/docbook-example/">https://pere.codeberg.page/docbook-example/</a></li>
1652 </ul>
1653
1654 <p>If you want to learn more on Docbook and translations, I recommend
1655 having a look at the <a href="https://docbook.org/">the DocBook
1656 web site</a>,
1657 <a href="https://doccookbook.sourceforge.net/html/en/">the DoCookBook
1658 site<a/> and my earlier blog post on
1659 <a href="https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html">how
1660 the Skolelinux project process and translate documentation</a>,  a talk I gave earlier this year on
1661 <a href="https://www.nuug.no/aktiviteter/20230314-oversetting-og-publisering-av-b%c3%b8ker-med-fri-programvare/">how
1662 to translate and publish books using free software</a> (Norwegian
1663 only).</p>
1664
1665 <!--
1666
1667 https://github.com/docbook/xslt10-stylesheets/issues/205 (docbook-xsl: sme support)
1668 https://bugs.debian.org/968437 (xindy: index sorting rules for nb/nn)
1669 https://bugs.debian.org/856123 (pandoc: markdown to docbook with non-english titles)
1670 https://bugs.debian.org/864813 (dblatex: missing nb words)
1671 https://bugs.debian.org/756386 (dblatex: index sorting rules for nb/nn)
1672 https://bugs.debian.org/796871 (dbtoepub: index sorting rules for nb/nn)
1673 https://bugs.debian.org/792616 (dblatex: PDF metadata)
1674 https://bugs.debian.org/686908 (docbook-xsl: index sorting rules for nb/nn)
1675 https://sourceforge.net/tracker/?func=detail&atid=373747&aid=3556630&group_id=21935 (docbook-xsl: nb/nn support)
1676 https://bugs.debian.org/684391 (dblatex: initial nb support)
1677
1678 -->
1679
1680 <p>As usual, if you use Bitcoin and want to show your support of my
1681 activities, please send Bitcoin donations to my address
1682 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
1683 </div>
1684       <div class="tags">
1685
1686
1687         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
1688
1689
1690       </div>
1691     </div>
1692     <div class="padding"></div>
1693
1694     <p style="text-align: right;"><a href="index.rss"><img src="https://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14" /></a></p>
1695     <div id="sidebar">
1696
1697
1698
1699 <h2>Archive</h2>
1700 <ul>
1701
1702 <li>2024
1703 <ul>
1704
1705 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/01/">January (1)</a></li>
1706
1707 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/02/">February (1)</a></li>
1708
1709 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/03/">March (2)</a></li>
1710
1711 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/04/">April (1)</a></li>
1712
1713 </ul></li>
1714
1715 <li>2023
1716 <ul>
1717
1718 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/01/">January (3)</a></li>
1719
1720 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/02/">February (1)</a></li>
1721
1722 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/04/">April (2)</a></li>
1723
1724 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/05/">May (3)</a></li>
1725
1726 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/06/">June (1)</a></li>
1727
1728 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/08/">August (1)</a></li>
1729
1730 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/09/">September (1)</a></li>
1731
1732 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/10/">October (1)</a></li>
1733
1734 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/11/">November (4)</a></li>
1735
1736 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/12/">December (1)</a></li>
1737
1738 </ul></li>
1739
1740 <li>2022
1741 <ul>
1742
1743 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/02/">February (1)</a></li>
1744
1745 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/03/">March (3)</a></li>
1746
1747 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/04/">April (2)</a></li>
1748
1749 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/06/">June (2)</a></li>
1750
1751 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/07/">July (1)</a></li>
1752
1753 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/09/">September (1)</a></li>
1754
1755 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/10/">October (1)</a></li>
1756
1757 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/12/">December (1)</a></li>
1758
1759 </ul></li>
1760
1761 <li>2021
1762 <ul>
1763
1764 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/01/">January (2)</a></li>
1765
1766 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/02/">February (1)</a></li>
1767
1768 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/05/">May (1)</a></li>
1769
1770 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/06/">June (1)</a></li>
1771
1772 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/07/">July (3)</a></li>
1773
1774 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/08/">August (1)</a></li>
1775
1776 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/09/">September (1)</a></li>
1777
1778 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/10/">October (1)</a></li>
1779
1780 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/12/">December (1)</a></li>
1781
1782 </ul></li>
1783
1784 <li>2020
1785 <ul>
1786
1787 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/02/">February (2)</a></li>
1788
1789 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/03/">March (2)</a></li>
1790
1791 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/04/">April (2)</a></li>
1792
1793 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/05/">May (3)</a></li>
1794
1795 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/06/">June (2)</a></li>
1796
1797 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/07/">July (1)</a></li>
1798
1799 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/09/">September (1)</a></li>
1800
1801 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/10/">October (1)</a></li>
1802
1803 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/11/">November (1)</a></li>
1804
1805 </ul></li>
1806
1807 <li>2019
1808 <ul>
1809
1810 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/01/">January (4)</a></li>
1811
1812 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/02/">February (3)</a></li>
1813
1814 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/03/">March (3)</a></li>
1815
1816 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/05/">May (2)</a></li>
1817
1818 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/06/">June (5)</a></li>
1819
1820 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/07/">July (2)</a></li>
1821
1822 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/08/">August (1)</a></li>
1823
1824 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/09/">September (1)</a></li>
1825
1826 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/11/">November (1)</a></li>
1827
1828 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/12/">December (4)</a></li>
1829
1830 </ul></li>
1831
1832 <li>2018
1833 <ul>
1834
1835 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/01/">January (1)</a></li>
1836
1837 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/02/">February (5)</a></li>
1838
1839 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/03/">March (5)</a></li>
1840
1841 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/04/">April (3)</a></li>
1842
1843 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/06/">June (2)</a></li>
1844
1845 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/07/">July (5)</a></li>
1846
1847 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/08/">August (3)</a></li>
1848
1849 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/09/">September (3)</a></li>
1850
1851 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/10/">October (5)</a></li>
1852
1853 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/11/">November (2)</a></li>
1854
1855 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/12/">December (4)</a></li>
1856
1857 </ul></li>
1858
1859 <li>2017
1860 <ul>
1861
1862 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
1863
1864 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
1865
1866 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
1867
1868 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
1869
1870 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
1871
1872 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
1873
1874 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/08/">August (1)</a></li>
1875
1876 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/09/">September (3)</a></li>
1877
1878 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/10/">October (5)</a></li>
1879
1880 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/11/">November (3)</a></li>
1881
1882 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/12/">December (4)</a></li>
1883
1884 </ul></li>
1885
1886 <li>2016
1887 <ul>
1888
1889 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
1890
1891 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
1892
1893 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
1894
1895 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
1896
1897 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
1898
1899 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
1900
1901 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
1902
1903 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
1904
1905 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
1906
1907 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
1908
1909 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
1910
1911 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
1912
1913 </ul></li>
1914
1915 <li>2015
1916 <ul>
1917
1918 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
1919
1920 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
1921
1922 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
1923
1924 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
1925
1926 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
1927
1928 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
1929
1930 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
1931
1932 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
1933
1934 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
1935
1936 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
1937
1938 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
1939
1940 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
1941
1942 </ul></li>
1943
1944 <li>2014
1945 <ul>
1946
1947 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
1948
1949 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
1950
1951 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
1952
1953 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
1954
1955 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
1956
1957 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
1958
1959 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
1960
1961 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
1962
1963 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
1964
1965 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
1966
1967 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
1968
1969 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
1970
1971 </ul></li>
1972
1973 <li>2013
1974 <ul>
1975
1976 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1977
1978 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1979
1980 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1981
1982 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1983
1984 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1985
1986 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1987
1988 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1989
1990 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1991
1992 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1993
1994 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1995
1996 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1997
1998 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1999
2000 </ul></li>
2001
2002 <li>2012
2003 <ul>
2004
2005 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
2006
2007 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
2008
2009 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
2010
2011 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
2012
2013 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
2014
2015 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
2016
2017 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
2018
2019 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
2020
2021 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
2022
2023 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
2024
2025 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
2026
2027 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
2028
2029 </ul></li>
2030
2031 <li>2011
2032 <ul>
2033
2034 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
2035
2036 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
2037
2038 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
2039
2040 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
2041
2042 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
2043
2044 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
2045
2046 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
2047
2048 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
2049
2050 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
2051
2052 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
2053
2054 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
2055
2056 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
2057
2058 </ul></li>
2059
2060 <li>2010
2061 <ul>
2062
2063 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
2064
2065 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
2066
2067 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
2068
2069 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
2070
2071 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
2072
2073 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
2074
2075 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
2076
2077 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
2078
2079 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
2080
2081 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
2082
2083 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
2084
2085 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
2086
2087 </ul></li>
2088
2089 <li>2009
2090 <ul>
2091
2092 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
2093
2094 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
2095
2096 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
2097
2098 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
2099
2100 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
2101
2102 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
2103
2104 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
2105
2106 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
2107
2108 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
2109
2110 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
2111
2112 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
2113
2114 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
2115
2116 </ul></li>
2117
2118 <li>2008
2119 <ul>
2120
2121 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
2122
2123 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
2124
2125 </ul></li>
2126
2127 </ul>
2128
2129
2130
2131 <h2>Tags</h2>
2132 <ul>
2133
2134  <li><a href="https://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (19)</a></li>
2135
2136  <li><a href="https://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
2137
2138  <li><a href="https://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
2139
2140  <li><a href="https://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
2141
2142  <li><a href="https://people.skolelinux.org/pere/blog/tags/betalkontant">betalkontant (9)</a></li>
2143
2144  <li><a href="https://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (13)</a></li>
2145
2146  <li><a href="https://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (17)</a></li>
2147
2148  <li><a href="https://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
2149
2150  <li><a href="https://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (3)</a></li>
2151
2152  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian">debian (198)</a></li>
2153
2154  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (159)</a></li>
2155
2156  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (9)</a></li>
2157
2158  <li><a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan (11)</a></li>
2159
2160  <li><a href="https://people.skolelinux.org/pere/blog/tags/dld">dld (18)</a></li>
2161
2162  <li><a href="https://people.skolelinux.org/pere/blog/tags/docbook">docbook (32)</a></li>
2163
2164  <li><a href="https://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
2165
2166  <li><a href="https://people.skolelinux.org/pere/blog/tags/english">english (459)</a></li>
2167
2168  <li><a href="https://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
2169
2170  <li><a href="https://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (14)</a></li>
2171
2172  <li><a href="https://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (34)</a></li>
2173
2174  <li><a href="https://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
2175
2176  <li><a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (20)</a></li>
2177
2178  <li><a href="https://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
2179
2180  <li><a href="https://people.skolelinux.org/pere/blog/tags/intervju">intervju (43)</a></li>
2181
2182  <li><a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (17)</a></li>
2183
2184  <li><a href="https://people.skolelinux.org/pere/blog/tags/kart">kart (23)</a></li>
2185
2186  <li><a href="https://people.skolelinux.org/pere/blog/tags/kodi">kodi (6)</a></li>
2187
2188  <li><a href="https://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
2189
2190  <li><a href="https://people.skolelinux.org/pere/blog/tags/lego">lego (5)</a></li>
2191
2192  <li><a href="https://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
2193
2194  <li><a href="https://people.skolelinux.org/pere/blog/tags/linuxcnc">linuxcnc (5)</a></li>
2195
2196  <li><a href="https://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
2197
2198  <li><a href="https://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
2199
2200  <li><a href="https://people.skolelinux.org/pere/blog/tags/madewithcc">madewithcc (3)</a></li>
2201
2202  <li><a href="https://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
2203
2204  <li><a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (46)</a></li>
2205
2206  <li><a href="https://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (15)</a></li>
2207
2208  <li><a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5 (25)</a></li>
2209
2210  <li><a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk (324)</a></li>
2211
2212  <li><a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug (199)</a></li>
2213
2214  <li><a href="https://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (41)</a></li>
2215
2216  <li><a href="https://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
2217
2218  <li><a href="https://people.skolelinux.org/pere/blog/tags/opensnitch">opensnitch (4)</a></li>
2219
2220  <li><a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (76)</a></li>
2221
2222  <li><a href="https://people.skolelinux.org/pere/blog/tags/personvern">personvern (114)</a></li>
2223
2224  <li><a href="https://people.skolelinux.org/pere/blog/tags/raid">raid (3)</a></li>
2225
2226  <li><a href="https://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
2227
2228  <li><a href="https://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
2229
2230  <li><a href="https://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
2231
2232  <li><a href="https://people.skolelinux.org/pere/blog/tags/robot">robot (17)</a></li>
2233
2234  <li><a href="https://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
2235
2236  <li><a href="https://people.skolelinux.org/pere/blog/tags/ruter">ruter (7)</a></li>
2237
2238  <li><a href="https://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
2239
2240  <li><a href="https://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (60)</a></li>
2241
2242  <li><a href="https://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
2243
2244  <li><a href="https://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
2245
2246  <li><a href="https://people.skolelinux.org/pere/blog/tags/standard">standard (76)</a></li>
2247
2248  <li><a href="https://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (7)</a></li>
2249
2250  <li><a href="https://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (14)</a></li>
2251
2252  <li><a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (65)</a></li>
2253
2254  <li><a href="https://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (5)</a></li>
2255
2256  <li><a href="https://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
2257
2258  <li><a href="https://people.skolelinux.org/pere/blog/tags/valg">valg (9)</a></li>
2259
2260  <li><a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri (22)</a></li>
2261
2262  <li><a href="https://people.skolelinux.org/pere/blog/tags/video">video (80)</a></li>
2263
2264  <li><a href="https://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
2265
2266  <li><a href="https://people.skolelinux.org/pere/blog/tags/web">web (42)</a></li>
2267
2268 </ul>
2269
2270
2271     </div>
2272     <p style="text-align: right">
2273  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
2274 </p>
2275
2276   </body>
2277 </html>