]> pere.pagekite.me Git - homepage.git/blob - blog/index.rss
New post on orphaned packages.
[homepage.git] / blog / index.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
3 <channel>
4 <title>Petter Reinholdtsen</title>
5 <description></description>
6 <link>https://people.skolelinux.org/pere/blog/</link>
7 <atom:link href="https://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
8
9 <item>
10 <title>RAID status from LSI Megaraid controllers in Debian</title>
11 <link>https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_in_Debian.html</link>
12 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_in_Debian.html</guid>
13 <pubDate>Wed, 17 Apr 2024 17:00:00 +0200</pubDate>
14 <description>&lt;p&gt;I am happy to report that
15 &lt;a href=&quot;https://github.com/namiltd/megactl&quot;&gt;the megactl package&lt;/a&gt;,
16 useful to fetch RAID status when using the LSI Megaraid controller,
17 now is available in Debian. It passed NEW a few days ago, and is now
18 &lt;a href=&quot;https://tracker.debian.org/pkg/megactl&quot;&gt;available in
19 unstable&lt;/a&gt;, and probably showing up in testing in a weeks time. The
20 new version should provide Appstream hardware mapping and should
21 integrate nicely with isenkram.&lt;/p&gt;
22
23 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
24 activities, please send Bitcoin donations to my address
25 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
26
27 </description>
28 </item>
29
30 <item>
31 <title>Time to move orphaned Debian packages to git</title>
32 <link>https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html</link>
33 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html</guid>
34 <pubDate>Sun, 14 Apr 2024 09:30:00 +0200</pubDate>
35 <description>&lt;p&gt;There are several packages in Debian without a associated git
36 repository with the packaging history. This is unfortunate and it
37 would be nice if more of these would do so. Quote a lot of these are
38 without a maintainer, ie listed as maintained by the
39 &#39;&lt;a href=&quot;https://qa.debian.org/developer.php?email=packages%40qa.debian.org&quot;&gt;Debian
40 QA Group&lt;/a&gt;&#39; place holder. In fact, 438 packages have this property
41 according to UDD (&lt;tt&gt;SELECT source FROM sources WHERE release = &#39;sid&#39;
42 AND (vcs_url ilike &#39;%anonscm.debian.org%&#39; OR vcs_browser ilike
43 &#39;%anonscm.debian.org%&#39; or vcs_url IS NULL OR vcs_browser IS NULL) AND
44 maintainer ilike &#39;%packages@qa.debian.org%&#39;;&lt;/tt&gt;). Such packages can
45 be updated without much coordination by any Debian developer, as they
46 are considered orphaned.&lt;/p&gt;
47
48 &lt;p&gt;To try to improve the situation and reduce the number of packages
49 without associated git repository, I started a few days ago to search
50 out candiates and provide them with a git repository under the
51 &#39;debian&#39; collaborative Salsa project. I started with the packages
52 pointing to obsolete Alioth git repositories, and am now working my
53 way across the ones completely without git references. In addition to
54 updating the Vcs-* debian/control fields, I try to update
55 Standards-Version, debhelper compat level, simplify d/rules, switch to
56 Rules-Requires-Root: no and fix lintian issues reported. I only
57 implement those that are trivial to fix, to avoid spending too much
58 time on each orphaned package. So far my experience is that it take
59 aproximately 20 minutes to convert a package without any git
60 references, and a lot more for packages with existing git repositories
61 incompatible with git-buildpackages.&lt;/p&gt;
62
63 &lt;p&gt;So far I have converted 10 packages, and I will keep going until I
64 run out of steam. As should be clear from the numbers, there is
65 enough packages remaining for more people to do the same without
66 stepping on each others toes. I find it useful to start by searching
67 for a git repo already on salsa, as I find that some times a git repo
68 has already been created, but no new version is uploaded to Debian
69 yet. In those cases I start with the existing git repository. I
70 convert to the git-buildpackage+pristine-tar workflow, and ensure a
71 debian/gbp.conf file with &quot;pristine-tar=True&quot; is added early, to avoid
72 uploading a orig.tar.gz with the wrong checksum by mistake. Did that
73 three times in the begin before I remembered my mistake.&lt;/p&gt;
74
75 &lt;p&gt;So, if you are a Debian Developer and got some spare time, perhaps
76 considering migrating some orphaned packages to git?&lt;/p&gt;
77
78 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
79 activities, please send Bitcoin donations to my address
80 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
81 </description>
82 </item>
83
84 <item>
85 <title>Plain text accounting file from your bitcoin transactions</title>
86 <link>https://people.skolelinux.org/pere/blog/Plain_text_accounting_file_from_your_bitcoin_transactions.html</link>
87 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Plain_text_accounting_file_from_your_bitcoin_transactions.html</guid>
88 <pubDate>Thu, 7 Mar 2024 18:00:00 +0100</pubDate>
89 <description>&lt;p&gt;A while back I wrote a small script to extract the Bitcoin
90 transactions in a wallet in the
91 &lt;ahref=&quot;https://plaintextaccounting.org/&quot;&gt;ledger plain text accounting
92 format&lt;/a&gt;. The last few days I spent some time to get it working
93 better with more special cases. In case it can be useful for others,
94 here is a copy:&lt;/p&gt;
95
96 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
97 #!/usr/bin/python3
98 # -*- coding: utf-8 -*-
99 # Copyright (c) 2023-2024 Petter Reinholdtsen
100
101 from decimal import Decimal
102 import json
103 import subprocess
104 import time
105
106 import numpy
107
108 def format_float(num):
109 return numpy.format_float_positional(num, trim=&#39;-&#39;)
110
111 accounts = {
112 u&#39;amount&#39; : &#39;Assets:BTC:main&#39;,
113 }
114
115 addresses = {
116 &#39;&lt;some address&gt;&#39; : &#39;Assets:bankkonto&#39;,
117 &#39;&lt;some address&gt;&#39; : &#39;Assets:bankkonto&#39;,
118 }
119
120 def exec_json(cmd):
121 proc = subprocess.Popen(cmd,stdout=subprocess.PIPE)
122 j = json.loads(proc.communicate()[0], parse_float=Decimal)
123 return j
124
125 def list_txs():
126 # get all transactions for all accounts / addresses
127 c = 0
128 txs = []
129 txidfee = {}
130 limit=100000
131 cmd = [&#39;bitcoin-cli&#39;, &#39;listtransactions&#39;, &#39;*&#39;, str(limit)]
132 if True:
133 txs.extend(exec_json(cmd))
134 else:
135 # Useful for debugging
136 with open(&#39;transactions.json&#39;) as f:
137 txs.extend(json.load(f, parse_float=Decimal))
138 #print txs
139 for tx in sorted(txs, key=lambda a: a[&#39;time&#39;]):
140 # print tx[&#39;category&#39;]
141 if &#39;abandoned&#39; in tx and tx[&#39;abandoned&#39;]:
142 continue
143 if &#39;confirmations&#39; in tx and 0 &gt;= tx[&#39;confirmations&#39;]:
144 continue
145 when = time.strftime(&#39;%Y-%m-%d %H:%M&#39;, time.localtime(tx[&#39;time&#39;]))
146 if &#39;message&#39; in tx:
147 desc = tx[&#39;message&#39;]
148 elif &#39;comment&#39; in tx:
149 desc = tx[&#39;comment&#39;]
150 elif &#39;label&#39; in tx:
151 desc = tx[&#39;label&#39;]
152 else:
153 desc = &#39;n/a&#39;
154 print(&quot;%s %s&quot; % (when, desc))
155 if &#39;address&#39; in tx:
156 print(&quot; ; to bitcoin address %s&quot; % tx[&#39;address&#39;])
157 else:
158 print(&quot; ; missing address in transaction, txid=%s&quot; % tx[&#39;txid&#39;])
159 print(f&quot; ; amount={tx[&#39;amount&#39;]}&quot;)
160 if &#39;fee&#39;in tx:
161 print(f&quot; ; fee={tx[&#39;fee&#39;]}&quot;)
162 for f in accounts.keys():
163 if f in tx and Decimal(0) != tx[f]:
164 amount = tx[f]
165 print(&quot; %-20s %s BTC&quot; % (accounts[f], format_float(amount)))
166 if &#39;fee&#39; in tx and Decimal(0) != tx[&#39;fee&#39;]:
167 # Make sure to list fee used in several transactions only once.
168 if &#39;fee&#39; in tx and tx[&#39;txid&#39;] in txidfee \
169 and tx[&#39;fee&#39;] == txidfee[tx[&#39;txid&#39;]]:
170 True
171 else:
172 fee = tx[&#39;fee&#39;]
173 print(&quot; %-20s %s BTC&quot; % (accounts[&#39;amount&#39;], format_float(fee)))
174 print(&quot; %-20s %s BTC&quot; % (&#39;Expences:BTC-fee&#39;, format_float(-fee)))
175 txidfee[tx[&#39;txid&#39;]] = tx[&#39;fee&#39;]
176
177 if &#39;address&#39; in tx and tx[&#39;address&#39;] in addresses:
178 print(&quot; %s&quot; % addresses[tx[&#39;address&#39;]])
179 else:
180 if &#39;generate&#39; == tx[&#39;category&#39;]:
181 print(&quot; Income:BTC-mining&quot;)
182 else:
183 if amount &lt; Decimal(0):
184 print(f&quot; Assets:unknown:sent:update-script-addr-{tx[&#39;address&#39;]}&quot;)
185 else:
186 print(f&quot; Assets:unknown:received:update-script-addr-{tx[&#39;address&#39;]}&quot;)
187
188 print()
189 c = c + 1
190 print(&quot;# Found %d transactions&quot; % c)
191 if limit == c:
192 print(f&quot;# Warning: Limit {limit} reached, consider increasing limit.&quot;)
193
194 def main():
195 list_txs()
196
197 main()
198 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
199
200 &lt;p&gt;It is more of a proof of concept, and I do not expect it to handle
201 all edge cases, but it worked for me, and perhaps you can find it
202 useful too.&lt;/p&gt;
203
204 &lt;p&gt;To get a more interesting result, it is useful to map accounts sent
205 to or received from to accounting accounts, using the
206 &lt;tt&gt;addresses&lt;/tt&gt; hash. As these will be very context dependent, I
207 leave out my list to allow each user to fill out their own list of
208 accounts. Out of the box, &#39;ledger reg BTC:main&#39; should be able to
209 show the amount of BTCs present in the wallet at any given time in the
210 past. For other and more valuable analysis, a account plan need to be
211 set up in the &lt;tt&gt;addresses&lt;/tt&gt; hash. Here is an example
212 transaction:&lt;/p&gt;
213
214 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
215 2024-03-07 17:00 Donated to good cause
216 Assets:BTC:main -0.1 BTC
217 Assets:BTC:main -0.00001 BTC
218 Expences:BTC-fee 0.00001 BTC
219 Expences:donations 0.1 BTC
220 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
221
222 &lt;p&gt;It need a running Bitcoin Core daemon running, as it connect to it
223 using &lt;tt&gt;bitcoin-cli listtransactions * 100000&lt;/tt&gt; to extract the
224 transactions listed in the Wallet.&lt;/p&gt;
225
226 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
227 activities, please send Bitcoin donations to my address
228 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
229 </description>
230 </item>
231
232 <item>
233 <title>RAID status from LSI Megaraid controllers using free software</title>
234 <link>https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_using_free_software.html</link>
235 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_using_free_software.html</guid>
236 <pubDate>Sun, 3 Mar 2024 22:40:00 +0100</pubDate>
237 <description>&lt;p&gt;The last few days I have revisited RAID setup using the LSI
238 Megaraid controller. These are a family of controllers called PERC by
239 Dell, and is present in several old PowerEdge servers, and I recently
240 got my hands on one of these. I had forgotten how to handle this RAID
241 controller in Debian, so I had to take a peek in the
242 &lt;a href=&quot;https://wiki.debian.org/LinuxRaidForAdmins&quot;&gt;Debian wiki page
243 &quot;Linux and Hardware RAID: an administrator&#39;s summary&quot;&lt;/a&gt; to remember
244 what kind of software is available to configure and monitor the disks
245 and controller. I prefer Free Software alternatives to proprietary
246 tools, as the later tend to fall into disarray once the manufacturer
247 loose interest, and often do not work with newer Linux Distributions.
248 Sadly there is no free software tool to configure the RAID setup, only
249 to monitor it. RAID can provide improved reliability and resilience in
250 a storage solution, but only if it is being regularly checked and any
251 broken disks are being replaced in time. I thus want to ensure some
252 automatic monitoring is available.&lt;/p&gt;
253
254 &lt;p&gt;In the discovery process, I came across a old free software tool to
255 monitor PERC2, PERC3, PERC4 and PERC5 controllers, which to my
256 surprise is not present in debian. To help change that I created a
257 &lt;a href=&quot;https://bugs.debian.org/1065322&quot;&gt;request for packaging of the
258 megactl package&lt;/a&gt;, and tried to track down a usable version.
259 &lt;a href=&quot;https://sourceforge.net/p/megactl/&quot;&gt;The original project
260 site&lt;/a&gt; is on Sourceforge, but as far as I can tell that project has
261 been dead for more than 15 years. I managed to find a
262 &lt;a href=&quot;https://github.com/hmage/megactl&quot;&gt;more recent fork on
263 github&lt;/a&gt; from user hmage, but it is unclear to me if this is still
264 being maintained. It has not seen much improvements since 2016. A
265 &lt;a href=&quot;https://github.com/namiltd/megactl&quot;&gt;more up to date
266 edition&lt;/a&gt; is a git fork from the original github fork by user
267 namiltd, and this newer fork seem a lot more promising. The owner of
268 this github repository has replied to change proposals within hours,
269 and had already added some improvements and support for more hardware.
270 Sadly he is reluctant to commit to maintaining the tool and stated in
271 &lt;a href=&quot;https://github.com/namiltd/megactl/pull/1&quot;&gt;my first pull
272 request&lt;/A&gt; that he think a new release should be made based on the
273 git repository owned by hmage. I perfectly understand this
274 reluctance, as I feel the same about maintaining yet another package
275 in Debian when I barely have time to take care of the ones I already
276 maintain, but do not really have high hopes that hmage will have time
277 to spend on it and hope namiltd will change his mind.&lt;/p&gt;
278
279 &lt;p&gt;In any case, I created
280 &lt;a href=&quot;https://salsa.debian.org/debian/megactl&quot;&gt;a draft package&lt;/a&gt;
281 based on the namiltd edition and put it under the debian group on
282 salsa.debian.org. If you own a Dell PowerEdge server with one of the
283 PERC controllers, or any other RAID controller using the megaraid or
284 megaraid_sas Linux kernel modules, you might want to check it out. If
285 enough people are interested, perhaps the package will make it into
286 the Debian archive.&lt;/p&gt;
287
288 &lt;p&gt;There are two tools provided, megactl for the megaraid Linux kernel
289 module, and megasasctl for the megaraid_sas Linux kernel module. The
290 simple output from the command on one of my machines look like this
291 (yes, I know some of the disks have problems. :).&lt;/p&gt;
292
293 &lt;pre&gt;
294 # megasasctl
295 a0 PERC H730 Mini encl:1 ldrv:2 batt:good
296 a0d0 558GiB RAID 1 1x2 optimal
297 a0d1 3067GiB RAID 0 1x11 optimal
298 a0e32s0 558GiB a0d0 online errs: media:0 other:19
299 a0e32s1 279GiB a0d1 online
300 a0e32s2 279GiB a0d1 online
301 a0e32s3 279GiB a0d1 online
302 a0e32s4 279GiB a0d1 online
303 a0e32s5 279GiB a0d1 online
304 a0e32s6 279GiB a0d1 online
305 a0e32s8 558GiB a0d0 online errs: media:0 other:17
306 a0e32s9 279GiB a0d1 online
307 a0e32s10 279GiB a0d1 online
308 a0e32s11 279GiB a0d1 online
309 a0e32s12 279GiB a0d1 online
310 a0e32s13 279GiB a0d1 online
311
312 #
313 &lt;/pre&gt;
314
315 &lt;p&gt;In addition to displaying a simple status report, it can also test
316 individual drives and print the various event logs. Perhaps you too
317 find it useful?&lt;/p&gt;
318
319 &lt;p&gt;In the packaging process I provided some patches upstream to
320 improve installation and ensure
321 &lt;ahref=&quot;https://github.com/namiltd/megactl/pull/2&quot;&gt;a Appstream
322 metainfo file is provided&lt;/a&gt; to list all supported HW, to allow
323 &lt;a href=&quot;https://tracker.debian.org/isenkram&quot;&gt;isenkram&lt;/a&gt; to propose
324 the package on all servers with a relevant PCI card.&lt;/p&gt;
325
326 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
327 activities, please send Bitcoin donations to my address
328 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
329
330 </description>
331 </item>
332
333 <item>
334 <title>Frokostseminar om Noark 5 i Oslo tirsdag 2024-03-12</title>
335 <link>https://people.skolelinux.org/pere/blog/Frokostseminar_om_Noark_5_i_Oslo_tirsdag_2024_03_12.html</link>
336 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Frokostseminar_om_Noark_5_i_Oslo_tirsdag_2024_03_12.html</guid>
337 <pubDate>Tue, 27 Feb 2024 15:15:00 +0100</pubDate>
338 <description>&lt;p&gt;Nikita-prosjektet, der jeg er involvert, inviterer i samarbeid med
339 Oslo Byarkiv, forskningsgruppen METAINFO og foreningen NUUG, til et
340 frokostseminar om Noark 5 og Noark 5 Tjenestegrensesnitt tirsdag
341 2024-03-12. Seminaret finner sted ved Oslo byarkiv. Vi håper å få
342 til videostrømming via Internett av presentasjoner og paneldiskusjon.
343 Oppdatert program og lenker til påmeldingsskjema er
344 &lt;a href=&quot;https://noark.codeberg.page/noark5-seminars/2023-03-12-noark-workshop.html&quot;&gt;tilgjengelig
345 fra Nikita-prosjektet&lt;/a&gt;. Arrangementet er gratis.
346
347 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
348 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
349 til min adresse
350 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;. Merk,
351 betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
352 </description>
353 </item>
354
355 <item>
356 <title>Welcome out of prison, Mickey, hope you find some freedom!</title>
357 <link>https://people.skolelinux.org/pere/blog/Welcome_out_of_prison__Mickey__hope_you_find_some_freedom_.html</link>
358 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Welcome_out_of_prison__Mickey__hope_you_find_some_freedom_.html</guid>
359 <pubDate>Mon, 1 Jan 2024 21:00:00 +0100</pubDate>
360 <description>&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;https://people.skolelinux.org/pere/blog/images/2024-01-01-mikke-verk-i-det-fri.jpeg&quot;/&gt;&lt;/p&gt;
361
362 &lt;p&gt;Today, the animation figure Mickey Mouse finally was released from
363 the corporate copyright prison, as the 1928 movie
364 &lt;a href=&quot;https://en.wikipedia.org/wiki/Steamboat_Willie&quot;&gt;Steamboat
365 Willie&lt;/a&gt; entered the public domain in USA. This movie was the first
366 public appearance of Mickey Mouse. Sadly the figure is still on
367 probation, thanks to trademark laws and a the Disney corporations
368 powerful pack of lawyers, as described in the 2017 article
369 in &lt;a href=&quot;https://priceonomics.com/how-mickey-mouse-evades-the-public-domain/&quot;&gt;&quot;How
370 Mickey Mouse Evades the Public Domain&quot;&lt;/a&gt; from Priceonomics. On the
371 positive side, the primary driver for repeated extentions of the
372 duration of copyright has been Disney thanks to Mickey Mouse and the
373 2028 movie, and as it now in the public domain I hope it will cause
374 less urge to extend the already unreasonable long copyright
375 duration.&lt;/p&gt;
376
377 &lt;p&gt;The first book I published, the 2004 book &lt;a
378 href=&quot;https://free-culture.cc/&quot;&gt;&quot;Free Culture&quot; by Lawrence Lessig&lt;/a&gt;,
379 published 2015 in
380 &lt;a href=&quot;https://people.skolelinux.org/pere/publisher/#frikultur&quot;&gt;English,
381 French and Norwegian Bokmål&lt;/a&gt;, touch on the story of Disney pushed
382 for extending the copyright duration in USA. It is a great book
383 explaining problems with the current copyright regime and why we need
384 Creative Commons movement, and I strongly recommend everyone to read
385 it.&lt;/p&gt;
386
387 &lt;p&gt;This movie (with
388 &lt;a href=&quot;https://www.imdb.com/title/tt0019422/&quot;&gt;IMDB ID tt0019422&lt;/a&gt;)
389 is now available from the Internet Archive. Two copies have been
390 uploaded so far, one uploaded
391 &lt;a href=&quot;https://archive.org/details/SteamboatWillie&quot;&gt;2015-11-04&lt;/a&gt;
392 (&lt;a href=&quot;https://archive.org/download/SteamboatWillie/SteamboatWillie_archive.torrent&quot;&gt;torrent&lt;/a&gt;)
393 and the other
394 &lt;a href=&quot;https://archive.org/details/steamboat-willie-mickey&quot;&gt;2023-01-01&lt;/a&gt;
395 (&lt;a href=&quot;https://archive.org/download/steamboat-willie-mickey/steamboat-willie-mickey_archive.torrent&quot;&gt;torrent&lt;/a&gt;) - see
396 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html&quot;&gt;VLC
397 bittorrent plugin&lt;/a&gt; for streaming the video using the torrent link.
398 I am very happy to see
399 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/Legal_to_share_more_than_16_000_movies_listed_on_IMDB_.html&quot;&gt;the
400 number of public domain movies&lt;/a&gt; increasing. I look forward to
401 when those are the majority. Perhaps it will reduce the urge of the
402 copyright industry to control its customers.&lt;/p&gt;
403
404 &lt;p&gt;A more
405 &lt;a href=&quot;https://publicdomainreview.org/features/entering-the-public-domain/2024/&quot;&gt;comprehensive
406 list of works entering the public domain in 2024&lt;/a&gt; is available from
407 the Public Domain Review.&lt;/p&gt;
408
409 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
410 activities, please send Bitcoin donations to my address
411 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
412 </description>
413 </item>
414
415 <item>
416 <title>VLC bittorrent plugin still going strong, new upload 2.14-4</title>
417 <link>https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html</link>
418 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html</guid>
419 <pubDate>Sun, 31 Dec 2023 10:45:00 +0100</pubDate>
420 <description>&lt;p&gt;The other day I uploaded a new version of
421 &lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;the VLC
422 bittorrent plugin&lt;/a&gt; to Debian, version 2.14-4, to fix a few
423 packaging issues. This plugin extend VLC allowing it to stream videos
424 directly from a bittorrent source using both torrent files and magnet
425 links, as easy as using a HTTP or local file source. I believe such
426 protocol support is a vital feature in VLC, allowing efficient
427 streaming from sources such at the 11 million movies in
428 &lt;a href=&quot;https://archive.org/&quot;&gt;the Internet Archive&lt;/a&gt;. Bittorrent is
429 one of the most efficient content distribution protocols on the
430 Internet, without centralised control, and should be used more.&lt;/p&gt;
431
432 &lt;p&gt;The new version is now both in Debian Unstable and Testing, as well
433 as Ubuntu. While looking after the package, I decided to ask the VLC
434 upstream community if there was any hope to get Bittorrent support
435 into the official VLC program, and was very happy to learn that
436 someone is already working on it. I hope we can see some fruits of
437 that labour next year, but do not hold my breath. In the mean time we
438 can use the plugin, which is already
439 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=vlc-plugin-bittorrent&quot;&gt;installed
440 by 0.23 percent of the Debian population&lt;/a&gt; according to
441 popularity-contest. It could use a new upstream release, and I hope
442 the upstream developer soon find time to polish it even more.&lt;/p&gt;
443
444 &lt;p&gt;It is worth noting that the plugin store the downloaded files in
445 &lt;tt&gt;~/Downloads/vlc-bittorrent/&lt;/tt&gt;, which can quickly fill up the
446 user home directory during use. Users of the plugin should keep an
447 eye with disk usage when streaming a bittorrent source.&lt;/p&gt;
448
449 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
450 activities, please send Bitcoin donations to my address
451 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
452 </description>
453 </item>
454
455 <item>
456 <title>«Når «på» blir «pÃ¥»: Et reservoar av tegn sett fra depotet» i tidsskriftet Aksess</title>
457 <link>https://people.skolelinux.org/pere/blog/_N_r__p___blir__p_____Et_reservoar_av_tegn_sett_fra_depotet__i_tidsskriftet_Aksess.html</link>
458 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/_N_r__p___blir__p_____Et_reservoar_av_tegn_sett_fra_depotet__i_tidsskriftet_Aksess.html</guid>
459 <pubDate>Wed, 15 Nov 2023 09:20:00 +0100</pubDate>
460 <description>&lt;p&gt;For noen uker siden skrev en kamerat og meg
461 &lt;a href=&quot;https://www.aksess-tidsskrift.no/fordypning/175530&quot;&gt;en
462 artikkel om tegnsett&lt;/a&gt; i
463 &lt;a href=&quot;https://www.aksess-tidsskrift.no/&quot;&gt;arkivtidsskriftet
464 Aksess&lt;/a&gt; både på web og i papirutgave nr. 3 2023. Her er det som
465 nettopp ble publisert.&lt;/p&gt;
466
467 &lt;blockquote&gt;
468
469 &lt;p&gt;&lt;strong&gt;Når «på» blir «pÃ¥»: Et reservoar av tegn sett fra
470 depotet&lt;/strong&gt;&lt;/p&gt;
471
472 &lt;p&gt;av Thomas Sødring og Petter Reinholdtsen&lt;/p&gt;
473
474 &lt;p&gt;De færreste av oss tenker over hva som skjer dypere i datamaskinen
475 mens vi sitter der og skriver noe på tastaturet. Når du trykker på
476 tasten «Å», så vises bokstaven Å. Men noen ganger blir det
477 feil. Hvorfor det – og hva er viktig å være klar over i
478 arkivsammenheng?&lt;/p&gt;
479
480 &lt;p&gt;Dersom bokstaver tolkes forskjellig mellom systemer, blir det fort
481 rot, dette kalles mojibake blant kjennere, etter det japanske
482 uttrykket for tegnomforming. Det er en lang historie her som tidvis
483 har vært preget av rot. Noen husker kanskje tilbake til en tid der
484 bokstavene æ, ø og å ofte var ødelagt i e-poster – et klassisk
485 eksempel på tegnsettproblemstilling.&lt;/p&gt;
486
487 &lt;p id=&quot;tegnsett_access_nå_og_før&quot;&gt;&lt;strong&gt;«Nå» og «før»&lt;/strong&gt;&lt;/p&gt;
488
489 &lt;p&gt;Tid er et skjult problem for depot fordi vi danner dokumentasjon i
490 en kontekst som er preget av å være «nå». Vår forståelse av verden og
491 bruken av teknologi er utgangspunktet for denne konteksten. Tenk selv
492 hvordan verden har utviklet seg de siste 20 årene, hva samfunnet er
493 opptatt av, og hvordan vi bruker teknologi i hverdagen. Tid er et
494 skjult problem fordi når vi trekker dokumentasjon ut av systemer og
495 deponerer for langtidsbevaring, er konteksten til materialet «nå», men
496 verden går videre. Ettersom teknologien og måten vi bruker den på,
497 utvikler seg, blir «nå» til «før», og dokumentasjonen befinner seg
498 snart i en «før»-kontekst.&lt;/p&gt;
499
500 &lt;p&gt;Dette med «før» og «nå» i forhold til dokumentasjonens kontekst er
501 noe vi er veldig lite bevisste på, men det er en problemstilling
502 depotarkivene eier og forvalter. En av disse utfordringene er hvorfor
503 «Ø» ikke nødvendigvis er det samme som «Ø», og hvorfor det i det hele
504 tatt gir mening å si noe sånt. Vi snakker her om noe som heter
505 tegnsett, som er en avtalt måte å representere bokstaver, tall og
506 andre symboler på slik at vi på en feilfri måte kan utveksle tekst
507 mellom datasystemer.&lt;/p&gt;
508
509 &lt;p&gt;Tegnsettproblemstillingen er satt sammen av fire fasetter;
510 repertoar, representasjon, koding og uttegning.&lt;/p&gt;
511
512 &lt;p id=&quot;tegnsett_access_repertoarer&quot;&gt;&lt;strong&gt;Repertoarer&lt;/strong&gt;&lt;/p&gt;
513
514 &lt;p&gt;Repertoar er en samling med tegn og symboler som kan
515 representeres. Tenk norsk alfabet eller japanske piktogrammer, men
516 også matematiske og elektroniske symboler. Bokstaven «stor a» kan være
517 en oppføring i et slikt repertoar. For å kunne brukes i en datamaskin
518 trenger hver oppføring i et slikt repertoar en representasjon, hvilket
519 i datamaskinsammenheng betyr at det tilordnes et tall. Tallet kan
520 lagres på ulike vis i en eller flere kodingsformater. For eksempel kan
521 en skrive tallet ti som både 10, X og A, i henholdsvis
522 titallssystemet, romertallssystemet og sekstentallssystemet.&lt;/p&gt;
523
524 &lt;p&gt;Hvis en skal kunne lese inn filer og vite hvilket tall og hvilken
525 representasjon og instans i et repertoar det er snakk om, så må en
526 vite hvordan tallet er kodet. Sist, men ikke minst, for å kunne bruke
527 symbolet til noe må det kunne være kjent hvordan det skal se ut eller
528 tegnes på ark. Det finnes utallige skrifttyper med norske bokstaver,
529 alle litt forskjellige, og skal en kunne tegne en stor A på skjermen,
530 så må datamaskinen vite hva den skal tegne. Skrifttyper inneholder
531 informasjon om hvordan ulike tall skal tegnes. De inneholder ikke
532 alltid alle symbolene som er brukt i en tekst, hvilket gjør at ikke
533 alle forståtte tegn vil kunne vises på skjerm eller ark.&lt;/p&gt;
534
535 &lt;p&gt;Hver av disse fasettene må være avklart for å kunne ta vare på og vise
536 frem tekst med en datamaskin. Kombinasjon av repertoar, representasjon
537 og koding er det en kaller et tegnsett. Kombinasjonen av
538 representasjon og uttegning kalles en skrifttype. De fleste
539 skrifttyper har også informasjon om repertoar, men det finnes
540 skrifttyper som kun kobler mellom tallkode og uttegning, uten å
541 fortelle noe om hvordan tallkodene egentlig skal tolkes.&lt;/p&gt;
542
543 &lt;p id=&quot;tegnsett_access_fra_ascii_til_iso_8859&quot;&gt;&lt;strong&gt;Fra ASCII til ISO-8859&lt;/strong&gt;&lt;/p&gt;
544
545 &lt;p&gt;Vi begynner historien med ASCII (American Standard Code for
546 Information Interchange) som har en historie som spores tilbake til
547 1963. Utgangspunktet til ASCII var at det kunne kode opp til 128
548 forskjellige symboler i vanlig bruk i USA. De visuelle symbolene i
549 ASCII er de små og store bokstavene (a til z og A til Z), tall (0 til
550 9) og tegnsettingssymboler (for eksempel semikolon, komma og
551 punktum). ASCII har også noen usynlige symboler som ble brukt for
552 bl.a. kommunikasjon. Før ASCII var det for eksempel teleks-tegnsett
553 med plass til bare 32 tegn og EBCDIC med plass til 256 tegn, alle med
554 en helt annen rekkefølge på symbolene enn ASCII, men de har vært lite
555 brukt de siste femti årene. Et eksempel på noen utvalgte symboler i
556 repertoaret til ASCII vises i tabell 1.&lt;/p&gt;
557
558 &lt;table align=&quot;center&quot; width=&quot;50%&quot;&gt;
559
560 &lt;caption&gt;Tabell 1. Eksempel på utvalgte symboler hentet fra
561 ASCII-tegnsettet. Kolonnen «Binær» viser symbolets verdi i
562 totallssystemet (1 og 0 tall), mens kolonnen «Desimal» viser symbolets
563 verdi i titallssystemet.&lt;/caption&gt;
564
565 &lt;tbody&gt;
566 &lt;tr&gt;
567 &lt;th&gt;Grafisk&lt;/th&gt;
568 &lt;th&gt;Binær&lt;/th&gt;
569 &lt;th&gt;Desimal&lt;/th&gt;
570 &lt;/tr&gt;
571 &lt;tr&gt;
572 &lt;td&gt;A&lt;/td&gt;
573 &lt;td&gt;1000001&lt;/td&gt;
574 &lt;td align=&quot;right&quot;&gt;65&lt;/td&gt;
575 &lt;/tr&gt;
576 &lt;tr&gt;
577 &lt;td&gt;M&lt;/td&gt;
578 &lt;td&gt;1001101&lt;/td&gt;
579 &lt;td align=&quot;right&quot;&gt;77&lt;/td&gt;
580 &lt;/tr&gt;
581 &lt;tr&gt;
582 &lt;td&gt;Z&lt;/td&gt;
583 &lt;td&gt;1011010&lt;/td&gt;
584 &lt;td align=&quot;right&quot;&gt;90&lt;/td&gt;
585 &lt;/tr&gt;
586 &lt;tr&gt;
587 &lt;td&gt;a&lt;/td&gt;
588 &lt;td&gt;1100001&lt;/td&gt;
589 &lt;td align=&quot;right&quot;&gt;97&lt;/td&gt;
590 &lt;/tr&gt;
591 &lt;tr&gt;
592 &lt;td&gt;m&lt;/td&gt;
593 &lt;td&gt;1101101&lt;/td&gt;
594 &lt;td align=&quot;right&quot;&gt;109&lt;/td&gt;
595 &lt;/tr&gt;
596 &lt;tr&gt;
597 &lt;td&gt;z&lt;/td&gt;
598 &lt;td&gt;1111010&lt;/td&gt;
599 &lt;td align=&quot;right&quot;&gt;122&lt;/td&gt;
600 &lt;/tr&gt;
601 &lt;tr&gt;
602 &lt;td&gt;0&lt;/td&gt;
603 &lt;td&gt;0110000&lt;/td&gt;
604 &lt;td align=&quot;right&quot;&gt;48&lt;/td&gt;
605 &lt;/tr&gt;
606 &lt;tr&gt;
607 &lt;td&gt;9&lt;/td&gt;
608 &lt;td&gt;0111001&lt;/td&gt;
609 &lt;td align=&quot;right&quot;&gt;58&lt;/td&gt;
610 &lt;/tr&gt;
611 &lt;tr&gt;
612 &lt;td&gt;;&lt;/td&gt;
613 &lt;td&gt;0111011&lt;/td&gt;
614 &lt;td align=&quot;right&quot;&gt;59&lt;/td&gt;
615 &lt;/tr&gt;
616 &lt;/tbody&gt;
617 &lt;/table&gt;
618
619 &lt;p&gt;Det opprinnelige ASCII-tegnsettet ble også omtalt som ASCII-7 og
620 brukte 7 bits (0 og 1) for å representere symboler. Datamaskiner er
621 ofte konfigurert til å jobbe med enheter der bits er gruppert som 4
622 eller 8 bits . Det lå en mulighet i å ta i bruk bit åtte. En slik
623 endring ville gjøre det mulig for datamaskiner å øke antall symboler
624 de kunne representere, noe som ga en økning fra 128 forskjellige
625 symboler til 256 forskjellige symboler. Det ble åpnet for å innlemme
626 de nordiske bokstavene sammen med ASCII, og dette ble etter hvert
627 standardisert som ISO-8859-1. Tabell 2 viser deler av ISO-8859-1 som
628 støtter de norske bokstavene.&lt;/p&gt;
629
630 &lt;p&gt;Det sier seg selv at muligheten til å representere inntil 256 symboler
631 ikke holder når vi snakker om en global verden, og det ble gjort et
632 standardiseringsløp som tok utgangspunkt i ASCII-7 med en utvidelse
633 til å bruke den åttende biten for ulike språkgrupper. Denne standarden
634 heter ISO-8859 og er inndelt i opptil 16 varianter, altså fra
635 ISO-8859-1 til ISO-8859-16.&lt;/p&gt;
636
637 &lt;table align=&quot;center&quot; width=&quot;50%&quot;&gt;
638
639 &lt;caption&gt;Tabell 2. Koding av de norske symbolene slik de er definert i
640 ISO-8859-1 tegnsettet.&lt;/caption&gt;
641
642 &lt;tbody&gt;
643 &lt;tr&gt;
644 &lt;th&gt;Grafisk&lt;/th&gt;
645 &lt;th&gt;Binær&lt;/th&gt;
646 &lt;th&gt;Desimal&lt;/th&gt;
647 &lt;/tr&gt;
648 &lt;tr&gt;
649 &lt;td&gt;Æ&lt;/td&gt;
650 &lt;td&gt;11000110&lt;/td&gt;
651 &lt;td align=&quot;right&quot;&gt;198&lt;/td&gt;
652 &lt;/tr&gt;
653 &lt;tr&gt;
654 &lt;td&gt;Ø&lt;/td&gt;
655 &lt;td&gt;11011000&lt;/td&gt;
656 &lt;td align=&quot;right&quot;&gt;216&lt;/td&gt;
657 &lt;/tr&gt;
658 &lt;tr&gt;
659 &lt;td&gt;Å&lt;/td&gt;
660 &lt;td&gt;11000101&lt;/td&gt;
661 &lt;td align=&quot;right&quot;&gt;197&lt;/td&gt;
662 &lt;/tr&gt;
663 &lt;tr&gt;
664 &lt;td&gt;æ&lt;/td&gt;
665 &lt;td&gt;11100110&lt;/td&gt;
666 &lt;td align=&quot;right&quot;&gt;230&lt;/td&gt;
667 &lt;/tr&gt;
668 &lt;tr&gt;
669 &lt;td&gt;ø&lt;/td&gt;
670 &lt;td&gt;11111000&lt;/td&gt;
671 &lt;td align=&quot;right&quot;&gt;248&lt;/td&gt;
672 &lt;/tr&gt;
673 &lt;tr&gt;
674 &lt;td&gt;å&lt;/td&gt;
675 &lt;td&gt;11100101&lt;/td&gt;
676 &lt;td align=&quot;right&quot;&gt;229&lt;/td&gt;
677 &lt;/tr&gt;
678 &lt;/tbody&gt;
679 &lt;/table&gt;
680
681 &lt;p&gt;Norske tegn er definert i ISO-8859-1, som også omtales som Latin 1, de
682 fleste samiske tegn er definert i ISO-8859-4 (Latin 4) mens tilgang
683 til €-symbolet kom med ISO-8859-15 (Latin 9). ISO-8859-15 er en
684 revisjon av ISO-8859-1 som fjerner noen lite brukte symboler og
685 erstatter bokstaver som er mer brukt, og introduserer €-symbolet. Det
686 er viktig å merke at alle ISO-8859-variantene har overlapp med
687 ASCII-7, noe som ga samvirke med de engelskspråklige landene som ikke
688 trengte å gjøre noe. Det innebærer også at de første 128 verdiene i
689 ISO-8859-variantene representerer de samme symbolene. Det er først når
690 du kommer til tolkningen av de resterende 128 verdiene med nummer 128
691 til 255, at det oppsto tolkningsutfordringer mellom
692 ISO-8859-variantene.&lt;/p&gt;
693
694 &lt;p&gt;ISO-8859-verdenen fungerte godt så lenge tegnsettet som ble brukt når
695 innhold ble skapt, også ble brukt når innhold ble gjengitt og du ikke
696 trengte å kombinere innhold fra forskjellige tegnsett i samme
697 dokument. Utfordringen med bruken av ISO-8859-variantene ble raskt
698 tydelig i en mer globalisert verden med utveksling av tekst på tvers
699 av landegrenser der tekstlig innhold i dokumenter, e-poster og
700 websider kunne bli skrevet med ett tegnsett og gjengitt med et annet
701 tegnsett.&lt;/p&gt;
702
703 &lt;table align=&quot;center&quot; width=&quot;60%&quot;&gt;
704
705 &lt;caption&gt;Tabell 3. Viser tolkning av verdiene som er tilegnet de
706 norske symbolene i ISO-8859-1 i de andre ISO 8859-variatene. Merk
707 ISO-8859-12 ikke finnes da arbeidet ble avsluttet.&lt;sup&gt;[&lt;a id=&quot;tegnsett_access_footnoteref_1&quot; href=&quot;#tegnsett_access_footnotedef_1&quot; title=&quot;View footnote.&quot;&gt;1&lt;/a&gt;]&lt;/sup&gt;&lt;/caption&gt;
708
709 &lt;tbody&gt;
710 &lt;tr&gt;
711 &lt;th&gt;Binærverdi&lt;/th&gt;
712 &lt;th&gt;1&lt;/th&gt;
713 &lt;th&gt;2&lt;/th&gt;
714 &lt;th&gt;3&lt;/th&gt;
715 &lt;th&gt;4&lt;/th&gt;
716 &lt;th&gt;5&lt;/th&gt;
717 &lt;th&gt;6&lt;/th&gt;
718 &lt;th&gt;7&lt;/th&gt;
719 &lt;th&gt;8&lt;/th&gt;
720 &lt;th&gt;9&lt;/th&gt;
721 &lt;th&gt;10&lt;/th&gt;
722 &lt;th&gt;11&lt;/th&gt;
723 &lt;th&gt;13&lt;/th&gt;
724 &lt;th&gt;14&lt;/th&gt;
725 &lt;th&gt;15&lt;/th&gt;
726 &lt;th&gt;16&lt;/th&gt;
727 &lt;/tr&gt;
728 &lt;tr&gt;
729 &lt;td&gt;11000110&lt;/td&gt;
730 &lt;td&gt;Æ&lt;/td&gt;
731 &lt;td&gt;Ć&lt;/td&gt;
732 &lt;td&gt;Ĉ&lt;/td&gt;
733 &lt;td&gt;Æ&lt;/td&gt;
734 &lt;td&gt;Ц&lt;/td&gt;
735 &lt;td&gt;ئ&lt;/td&gt;
736 &lt;td&gt;Ζ&lt;/td&gt;
737 &lt;td&gt;&lt;/td&gt;
738 &lt;td&gt;Æ&lt;/td&gt;
739 &lt;td&gt;Æ&lt;/td&gt;
740 &lt;td&gt;&lt;/td&gt;
741 &lt;td&gt;Ę&lt;/td&gt;
742 &lt;td&gt;Æ&lt;/td&gt;
743 &lt;td&gt;Æ&lt;/td&gt;
744 &lt;td&gt;Æ&lt;/td&gt;
745 &lt;/tr&gt;
746 &lt;tr&gt;
747 &lt;td&gt;11011000&lt;/td&gt;
748 &lt;td&gt;Ø&lt;/td&gt;
749 &lt;td&gt;Ř&lt;/td&gt;
750 &lt;td&gt;Ĝ&lt;/td&gt;
751 &lt;td&gt;Ø&lt;/td&gt;
752 &lt;td&gt;и&lt;/td&gt;
753 &lt;td&gt;ظ&lt;/td&gt;
754 &lt;td&gt;Ψ&lt;/td&gt;
755 &lt;td&gt;&lt;/td&gt;
756 &lt;td&gt;Ø&lt;/td&gt;
757 &lt;td&gt;Ø&lt;/td&gt;
758 &lt;td&gt;&lt;/td&gt;
759 &lt;td&gt;Ų&lt;/td&gt;
760 &lt;td&gt;Ø&lt;/td&gt;
761 &lt;td&gt;Ø&lt;/td&gt;
762 &lt;td&gt;Ű&lt;/td&gt;
763 &lt;/tr&gt;
764 &lt;tr&gt;
765 &lt;td&gt;11000101&lt;/td&gt;
766 &lt;td&gt;Å&lt;/td&gt;
767 &lt;td&gt;Ĺ&lt;/td&gt;
768 &lt;td&gt;Ċ&lt;/td&gt;
769 &lt;td&gt;Å&lt;/td&gt;
770 &lt;td&gt;Х&lt;/td&gt;
771 &lt;td&gt;إ&lt;/td&gt;
772 &lt;td&gt;Ε&lt;/td&gt;
773 &lt;td&gt;&lt;/td&gt;
774 &lt;td&gt;Å&lt;/td&gt;
775 &lt;td&gt;Å&lt;/td&gt;
776 &lt;td&gt;&lt;/td&gt;
777 &lt;td&gt;Å&lt;/td&gt;
778 &lt;td&gt;Å&lt;/td&gt;
779 &lt;td&gt;Å&lt;/td&gt;
780 &lt;td&gt;Ć&lt;/td&gt;
781 &lt;/tr&gt;
782 &lt;tr&gt;
783 &lt;td&gt;11100110&lt;/td&gt;
784 &lt;td&gt;æ&lt;/td&gt;
785 &lt;td&gt;ć&lt;/td&gt;
786 &lt;td&gt;ĉ&lt;/td&gt;
787 &lt;td&gt;æ&lt;/td&gt;
788 &lt;td&gt;ц&lt;/td&gt;
789 &lt;td&gt;ن&lt;/td&gt;
790 &lt;td&gt;ζ&lt;/td&gt;
791 &lt;td&gt;ז&lt;/td&gt;
792 &lt;td&gt;æ&lt;/td&gt;
793 &lt;td&gt;æ&lt;/td&gt;
794 &lt;td&gt;&lt;/td&gt;
795 &lt;td&gt;ę&lt;/td&gt;
796 &lt;td&gt;æ&lt;/td&gt;
797 &lt;td&gt;æ&lt;/td&gt;
798 &lt;td&gt;v&lt;/td&gt;
799 &lt;/tr&gt;
800 &lt;tr&gt;
801 &lt;td&gt;11111000&lt;/td&gt;
802 &lt;td&gt;ø&lt;/td&gt;
803 &lt;td&gt;ř&lt;/td&gt;
804 &lt;td&gt;ĝ&lt;/td&gt;
805 &lt;td&gt;ø&lt;/td&gt;
806 &lt;td&gt;ј&lt;/td&gt;
807 &lt;td&gt;&lt;/td&gt;
808 &lt;td&gt;ψ&lt;/td&gt;
809 &lt;td&gt;ר&lt;/td&gt;
810 &lt;td&gt;ø&lt;/td&gt;
811 &lt;td&gt;ø&lt;/td&gt;
812 &lt;td&gt;&lt;/td&gt;
813 &lt;td&gt;ų&lt;/td&gt;
814 &lt;td&gt;ø&lt;/td&gt;
815 &lt;td&gt;ø&lt;/td&gt;
816 &lt;td&gt;ű&lt;/td&gt;
817 &lt;/tr&gt;
818 &lt;tr&gt;
819 &lt;td&gt;11100101&lt;/td&gt;
820 &lt;td&gt;å&lt;/td&gt;
821 &lt;td&gt;ĺ&lt;/td&gt;
822 &lt;td&gt;ċ&lt;/td&gt;
823 &lt;td&gt;å&lt;/td&gt;
824 &lt;td&gt;х&lt;/td&gt;
825 &lt;td&gt;م&lt;/td&gt;
826 &lt;td&gt;ε&lt;/td&gt;
827 &lt;td&gt;ו&lt;/td&gt;
828 &lt;td&gt;å&lt;/td&gt;
829 &lt;td&gt;å&lt;/td&gt;
830 &lt;td&gt;&lt;/td&gt;
831 &lt;td&gt;å&lt;/td&gt;
832 &lt;td&gt;å&lt;/td&gt;
833 &lt;td&gt;å&lt;/td&gt;
834 &lt;td&gt;ć&lt;/td&gt;
835 &lt;/tr&gt;
836 &lt;/tbody&gt;
837 &lt;/table&gt;
838
839 &lt;p&gt;Denne problemstillingen er illustrert i tabell 3, der vi ser verdiene
840 tilegnet de norske symbolene i ISO-8859-1 i kolonne «1». I de øvrige
841 kolonnene ser vi hvilket symbol verdien får i de andre
842 ISO-8859-variantene. Tar vi utgangspunkt i tabell 3, kan vi se at
843 ordet lærlingspørsmål gjengitt med ISO-8859-2 (kolonne 2) blir
844 lćrlingspřrsmĺl, mens det blir lζrlingspψrsmεl med ISO- 8859-7
845 (kolonne 7). Med ISO-8859-2 blir «æ» til «ć», «ø» til «ř» og «å» til
846 «ĺ». I ISO-8859-7 blir «æ» til «ζ», «ø» til «ψ», mens «å» blir «ε».&lt;/p&gt;
847
848 &lt;p&gt;Det er egentlig ingen utfordring med dette så lenge du vet hvilket
849 tegnsett innholdet ditt er representert med, og det ikke har skjedd
850 omforminger som du ikke er klar over. Det er det siste som er
851 problematisk, spesielt de datasystemene som har vært i bruk de siste
852 20 årene, som ikke har noe innebygd funksjonalitet for å forvalte
853 tegnsettproblematikken. Et godt eksempel på dette er
854 Microsoft-tegnsettet Windows-1252, som ble forvekslet som 100 %
855 kompatibel med ISO-8859-1, men hadde byttet ut plassene fra 127 til
856 159. Historisk vil det finnes en del variasjon i hvilket tegnsett som
857 har vært i bruk, og hvor vellykket konvertering mellom tegnsett har
858 vært.&lt;/p&gt;
859
860 &lt;p id=&quot;tegnsett_access_unicode_som_løsning&quot;&gt;&lt;strong&gt;Unicode som løsning&lt;/strong&gt;&lt;/p&gt;
861
862 &lt;p&gt;Tegnsettforvirring ble etter hvert et irritasjonsmoment og
863 samvirkeproblem. Ofte fikk man en e-post der æøå var erstattet av rare
864 symboler fordi e-posten hadde vært innom et eller annet datasystem som
865 ikke brukte samme tegnsett.&lt;/p&gt;
866
867 &lt;p&gt;For å løse dette samvirkeproblemet for tegnsett ble det startet et
868 arbeid og en ny standard så dagens lys etter hvert. Denne standarden
869 fikk navnet Unicode (ISO/ IEC 10646) og skulle resultere i et tegnsett
870 som alle skulle være enige om. Unicode er et repertoar og en
871 representasjon, dvs. navngivning og tilordning av tallverdi til alle
872 symboler i bruk i verden i dag. Oppføringer i Unicode skrives gjerne
873 U+XXXX der XXXX er tallkoden i sekstentallssystemet som oppføringen
874 har i Unicode-katalogen. Her finner vi tegn brukt av både levende og
875 døde språk, konstruerte språk, tekniske symboler, morsomme tegninger
876 (såkalte emojier) og tegn ingen vet hva betyr eller skal brukes
877 til. Et morsomt eksempel er i nettartikkelen: U+237C ⍼ RIGHT ANGLE
878 WITH DOWNWARDS ZIGZAG ARROW, av Jonathan Chan.&lt;sup&gt;[&lt;a id=&quot;tegnsett_access_footnoteref_2&quot; href=&quot;#tegnsett_access_footnotedef_2&quot; title=&quot;View footnote.&quot;&gt;2&lt;/a&gt;]&lt;/sup&gt;&lt;/p&gt;
879
880 &lt;p&gt;Sammen med Unicode kom det tre måter å kode disse tallene på; UTF-8,
881 UTF-16 og UTF-32. Av datatekniske årsaker er UTF-8 mye brukt, spesielt
882 når det gjelder utveksling av tekst over Internett, mens UTF-16 er
883 brukt en del til tekstfiler lagret på Windows. En utfordring med
884 Unicode og UTF-variantene er at disse gir flere måter å kode samme
885 symbol på med en kombinasjonsmekanisme. Dette kan gi utfordringer ved
886 søk, hvis en skal søke etter et ord som har ett eller flere symboler
887 som kan skrives på ulikt vis, så er det ikke sikkert at søkesystemet
888 vil finne alle forekomster. For eksempel kan bokstaven U+00F8 «Latin
889 Small Letter O with Stroke» kodes som den tradisjonelle norske tegnet
890 ø, men også som o kombinert med skråstrek U+0338. Begge deler er
891 gyldig bruk av Unicode, selv om det er tradisjon for å foretrekke å
892 «normalisere» kombinasjoner som enkelttegn der det er mulig, nettopp
893 for å forenkle søk.&lt;/p&gt;
894
895 &lt;p id=&quot;tegnsett_access_bare_unicode_fremover&quot;&gt;&lt;strong&gt;Bare Unicode fremover&lt;/strong&gt;&lt;/p&gt;
896
897 &lt;p&gt;Forvaltningens bruk av tegnsett er regulert i Forskrift om
898 IT-standarder i offentlig forvaltning&lt;sup&gt;[&lt;a id=&quot;tegnsett_access_footnoteref_3&quot; href=&quot;#tegnsett_access_footnotedef_3&quot; title=&quot;View footnote.&quot;&gt;3&lt;/a&gt;]&lt;/sup&gt;. Her står det: «Ved all
899 utveksling av informasjon mellom forvaltningsorganer og fra
900 forvaltningsorgan til innbyggere og næringsliv skal tegnsettstandarden
901 ISO/IEC 10646 representert ved UTF8 benyttes.» Det er forskjellige
902 bruksområder til UTF-8, UTF-16 og UTF-32, men UTF-8 er kodingen vi
903 kjenner mest til. Det er flere grunner at UTF-8 «vant» konkurransen
904 til å bli den utvalgte. Den kanskje viktigste er at UTF-8 er fullt
905 samvirkende med ASCII-7, slik at den engelskspråklige delen av verden
906 kunne rulle ut UTF-8 uten å merke noe forskjell. En tekstfil med kun
907 ASCII-tekst vil være identisk på disken hvis den lagres som UTF-8 og
908 ASCII. UTF-16 og UTF-32 byr på noen optimaliseringer som gjør dem
909 relevant for spesifikke problemområder, men for det meste vil vi aldri
910 oppleve disse standardene på nært hold i hverdagen. Det er uansett kun
911 bruken av UTF-8 som er lovregulert i Norge.&lt;/p&gt;
912
913 &lt;p&gt;Det er ikke slik at hele verden bruker ISO/IEC 10646 og UTF-8. Kina
914 har egne standarder for tegnsett, mye brukt er GB 18030, som er
915 Unicode med en annen koding enn UTF-8, mens Taiwan og andre asiatiske
916 land gjerne bruker Big5 eller andre tegnsett.&lt;/p&gt;
917
918 &lt;p&gt;UTF-8 er dominerende i Norge, men det er tidsperioder der forskjellige
919 datasystemer utvekslet data i henhold til ISO-8859-1, ISO-8859-15,
920 Windows-1252, Codepage 865 og ISO-646-60 / Codepage 1016 mens
921 overgangen til UTF-8 pågikk. Det er ikke slik at et datasystem enkelt
922 kan tvinges til å bruke et tegnsett, da det er flere lag i et
923 datasystem som må settes opp til å bruke riktig tegnsett, og
924 tegnsettproblemet fort oppstår når det er et eller annet i
925 datasystemet som bruker feil tegnsett.&lt;/p&gt;
926
927 &lt;p&gt;Et klassisk eksempel på problemet er en utveksling av tekst mellom to
928 systemer der teksten i utgangspunktet er kodet i UTF-8, men går
929 gjennom noe som er ISO-8859-1 underveis. Dette kan vises med at ordet
930 «på» i et slik scenario ender opp som «pÃ¥». Det er mulig å spore
931 dette tilbake til verdiene symbolene er tilordnet i tegnsettene. «på»
932 blir til «pÃ¥» fordi «å» i UTF-8 er representert med U+C3AF, og dersom
933 vi ser på hva disse verdiene representerer, ser vi at
934 sekstentallssystemverdien C3 er 1100 0011 i totallssystemet og
935 symbolet med dette tallet i ISO-8859-1 er Ã.&lt;/p&gt;
936
937 &lt;p&gt;Vi ser det samme med sekstentallssystemverdien A5, som er 1010 0101 i
938 totallssystemet, og tilsvarende symbol i ISO-8859-1 er ¥. Slik
939 mojibake kan lett skje hvis «på» i utgangspunktet var representert med
940 UTF-8, men ble behandlet med et system som bruker ISO-8859-1. Det er
941 ingen automatikk i å fange opp slike ødeleggelser mens tekstlig
942 innhold utveksles mellom datasystemer.&lt;/p&gt;
943
944 &lt;p&gt;En utfordring for depotarkivene er at bruken av tegnsett ikke alltid
945 har vært regulert, og at det kan finnes flere dokumentasjonssamlinger
946 som er opprettet med varierende tegnsett før gjeldende forskrift
947 inntraff – uten at det er mulig å avlede fra filene hvilket tegnsett
948 som ble brukt. Et eksempel på dette er €-symbolet, som kom først etter
949 at ISO-8859-1 var tatt i bruk. Det kan bli en utfordring for et
950 depotarkiv, men så lenge det er kjent hvilket tegnsett var i bruk, så
951 bør det gå bra. Riksarkivarens
952 forskrift&lt;sup&gt;[&lt;a id=&quot;tegnsett_access_footnoteref_4&quot; href=&quot;#tegnsett_access_footnotedef_4&quot; title=&quot;View footnote.&quot;&gt;4&lt;/a&gt;]&lt;/sup&gt;
953 formaliserer dette ved å kreve følgende:&lt;/p&gt;
954
955 &lt;blockquote&gt;
956 &lt;p&gt;§ 5-11. Tegnsett i arkivuttrekk&lt;/p&gt;
957
958 &lt;ol&gt;
959 &lt;li&gt;Arkivuttrekk og medfølgende struktur- og innholdsbeskrivelser skal
960 overføres som ren tekst i ukryptert form, og benytte godkjent
961 tegnsett.&lt;/li&gt;
962
963 &lt;li&gt;Godkjente tegnsett er:
964 &lt;ol&gt;
965 &lt;li&gt;Unicode UTF-8&lt;br&gt;
966 (ISO/IEC 10646-1:2000 Annex D)&lt;/li&gt;
967 &lt;li&gt;ISO 8859-1:1998, Latin 1&lt;/li&gt;
968 &lt;li&gt;ISO 8859-4:1998, Latin 4 for samiske tegn.&lt;/li&gt;
969 &lt;/ol&gt;&lt;/li&gt;
970
971 &lt;li&gt;Andre tegnsett aksepteres bare etter avtale med Arkivverket.&lt;/li&gt;
972 &lt;/ol&gt;
973 &lt;/blockquote&gt;
974
975 &lt;p id=&quot;tegnsett_access_ditt_ansvar&quot;&gt;&lt;strong&gt;Ditt ansvar&lt;/strong&gt;&lt;/p&gt;
976
977 &lt;p&gt;På mange måter burde ikke tegnsett være et problem i 2023, men sånn er
978 det nok ikke. Land som har oppgradert til UTF-8 som primærtegnsett for
979 utveksling av tekstlig innhold, begrenser problematikken betraktelig,
980 men globalt sett så er tegnsettutfordringen ikke løst fordi ikke alle
981 er enige om å bruke samme tegnsett. Det kan være geopolitiske eller
982 kulturelle hensyn som ligger til grunn for dette.&lt;/p&gt;
983
984 &lt;p&gt;Det er uansett verdt å merke at selv om bruken av UTF-8 skulle bli
985 100% utbredt, så er det et historisk perspektiv (ASCII-7,
986 ISO-8859-variantene, UTF-8) her som gjør tegnsett til et problemområde
987 arkivarene må forstå og håndtere. Som danningsarkivar har du et
988 ansvar for å vite hvilket tegnsett systemene og databasene dere
989 forvalter, er i samsvar med. Det er noe IT-avdelingen din eller
990 programvareleverandørene enkelt skal kunne svare på, og svaret skal
991 være UTF-8 for alle nye systemer.&lt;/p&gt;
992
993 &lt;hr&gt;
994
995 &lt;p id=&quot;tegnsett_access_footnotedef_1&quot;&gt;&lt;a href=&quot;#tegnsett_access_footnoteref_1&quot;&gt;1&lt;/a&gt;. Tegnsettkilde &lt;a href=&quot;https://en.wikipedia.org/wiki/ISO/IEC_8859&quot;&gt;https://en.wikipedia.org/wiki/ISO/IEC_8859&lt;/a&gt;&lt;/p&gt;
996
997 &lt;p id=&quot;tegnsett_access_footnotedef_2&quot;&gt;&lt;a href=&quot;#tegnsett_access_footnoteref_2&quot;&gt;2&lt;/a&gt;. &lt;a href=&quot;https://ionathan.ch/2022/04/09/angzarr.html&quot;&gt;https://ionathan.ch/2022/04/09/angzarr.html&lt;/a&gt;&lt;/p&gt;
998
999 &lt;p id=&quot;tegnsett_access_footnotedef_3&quot;&gt;&lt;a href=&quot;#tegnsett_access_footnoteref_3&quot;&gt;3&lt;/a&gt;. &lt;a href=&quot;https://lovdata.no/dokument/SF/forskrift/2013-04-05-959/%C2%A78#%C2%A78&quot;&gt;https://lovdata.no/dokument/SF/forskrift/2013-04-05-959/%C2%A78#%C2%A78&lt;/a&gt;&lt;/p&gt;
1000
1001 &lt;p id=&quot;tegnsett_access_footnotedef_4&quot;&gt;&lt;a href=&quot;#tegnsett_access_footnoteref_4&quot;&gt;4&lt;/a&gt;. &lt;a href=&quot;https://lovdata.no/forskrift/2017-12-19-22865-11&quot;&gt;https://lovdata.no/forskrift/2017-12-19-22865-11&lt;/a&gt;&lt;/p&gt;
1002
1003 &lt;/blockquote&gt;
1004
1005 &lt;p&gt;For øvrig burde varsleren Edward Snowden få politisk asyl i Norge.&lt;/p&gt;
1006
1007 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1008 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1009 til min adresse
1010 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;. Merk,
1011 betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
1012 </description>
1013 </item>
1014
1015 <item>
1016 <title>New and improved sqlcipher in Debian for accessing Signal database</title>
1017 <link>https://people.skolelinux.org/pere/blog/New_and_improved_sqlcipher_in_Debian_for_accessing_Signal_database.html</link>
1018 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_and_improved_sqlcipher_in_Debian_for_accessing_Signal_database.html</guid>
1019 <pubDate>Sun, 12 Nov 2023 12:00:00 +0100</pubDate>
1020 <description>&lt;p&gt;For a while now I wanted to have direct access to the
1021 &lt;a href=&quot;https://signal.org/&quot;&gt;Signal&lt;/a&gt; database of messages and
1022 channels of my Desktop edition of Signal. I prefer the enforced end
1023 to end encryption of Signal these days for my communication with
1024 friends and family, to increase the level of safety and privacy as
1025 well as raising the cost of the mass surveillance government and
1026 non-government entities practice these days. In August I came across
1027 a nice
1028 &lt;a href=&quot;https://www.yoranbrondsema.com/post/the-guide-to-extracting-statistics-from-your-signal-conversations/&quot;&gt;recipe
1029 on how to use sqlcipher to extract statistics from the Signal
1030 database&lt;/a&gt; explaining how to do this. Unfortunately this did not
1031 work with the version of sqlcipher in Debian. The
1032 &lt;a href=&quot;http://tracker.debian.org/sqlcipher/&quot;&gt;sqlcipher&lt;/a&gt;
1033 package is a &quot;fork&quot; of the sqlite package with added support for
1034 encrypted databases. Sadly the current Debian maintainer
1035 &lt;a href=&quot;https://bugs.debian.org/961598&quot;&gt;announced more than three
1036 years ago that he did not have time to maintain sqlcipher&lt;/a&gt;, so it
1037 seemed unlikely to be upgraded by the maintainer. I was reluctant to
1038 take on the job myself, as I have very limited experience maintaining
1039 shared libraries in Debian. After waiting and hoping for a few
1040 months, I gave up the last week, and set out to update the package. In
1041 the process I orphaned it to make it more obvious for the next person
1042 looking at it that the package need proper maintenance.&lt;/p&gt;
1043
1044 &lt;p&gt;The version in Debian was around five years old, and quite a lot of
1045 changes had taken place upstream into the Debian maintenance git
1046 repository. After spending a few days importing the new upstream
1047 versions, realising that upstream did not care much for SONAME
1048 versioning as I saw library symbols being both added and removed with
1049 minor version number changes to the project, I concluded that I had to
1050 do a SONAME bump of the library package to avoid surprising the
1051 reverse dependencies. I even added a simple
1052 autopkgtest script to ensure the package work as intended. Dug deep
1053 into the hole of learning shared library maintenance, I set out a few
1054 days ago to upload the new version to Debian experimental to see what
1055 the quality assurance framework in Debian had to say about the result.
1056 The feedback told me the pacakge was not too shabby, and yesterday I
1057 uploaded the latest version to Debian unstable. It should enter
1058 testing today or tomorrow, perhaps delayed by
1059 &lt;a href=&quot;https://bugs.debian.org/1055812&quot;&gt;a small library
1060 transition&lt;/a&gt;.&lt;/p&gt;
1061
1062 &lt;p&gt;Armed with a new version of sqlcipher, I can now have a look at the
1063 SQL database in ~/.config/Signal/sql/db.sqlite. First, one need to
1064 fetch the encryption key from the Signal configuration using this
1065 simple JSON extraction command:&lt;/p&gt;
1066
1067 &lt;pre&gt;/usr/bin/jq -r &#39;.&quot;key&quot;&#39; ~/.config/Signal/config.json&lt;/pre&gt;
1068
1069 &lt;p&gt;Assuming the result from that command is &#39;secretkey&#39;, which is a
1070 hexadecimal number representing the key used to encrypt the database.
1071 Next, one can now connect to the database and inject the encryption
1072 key for access via SQL to fetch information from the database. Here
1073 is an example dumping the database structure:&lt;/p&gt;
1074
1075 &lt;pre&gt;
1076 % sqlcipher ~/.config/Signal/sql/db.sqlite
1077 sqlite&gt; PRAGMA key = &quot;x&#39;secretkey&#39;&quot;;
1078 sqlite&gt; .schema
1079 CREATE TABLE sqlite_stat1(tbl,idx,stat);
1080 CREATE TABLE conversations(
1081 id STRING PRIMARY KEY ASC,
1082 json TEXT,
1083
1084 active_at INTEGER,
1085 type STRING,
1086 members TEXT,
1087 name TEXT,
1088 profileName TEXT
1089 , profileFamilyName TEXT, profileFullName TEXT, e164 TEXT, serviceId TEXT, groupId TEXT, profileLastFetchedAt INTEGER);
1090 CREATE TABLE identityKeys(
1091 id STRING PRIMARY KEY ASC,
1092 json TEXT
1093 );
1094 CREATE TABLE items(
1095 id STRING PRIMARY KEY ASC,
1096 json TEXT
1097 );
1098 CREATE TABLE sessions(
1099 id TEXT PRIMARY KEY,
1100 conversationId TEXT,
1101 json TEXT
1102 , ourServiceId STRING, serviceId STRING);
1103 CREATE TABLE attachment_downloads(
1104 id STRING primary key,
1105 timestamp INTEGER,
1106 pending INTEGER,
1107 json TEXT
1108 );
1109 CREATE TABLE sticker_packs(
1110 id TEXT PRIMARY KEY,
1111 key TEXT NOT NULL,
1112
1113 author STRING,
1114 coverStickerId INTEGER,
1115 createdAt INTEGER,
1116 downloadAttempts INTEGER,
1117 installedAt INTEGER,
1118 lastUsed INTEGER,
1119 status STRING,
1120 stickerCount INTEGER,
1121 title STRING
1122 , attemptedStatus STRING, position INTEGER DEFAULT 0 NOT NULL, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync
1123 INTEGER DEFAULT 0 NOT NULL);
1124 CREATE TABLE stickers(
1125 id INTEGER NOT NULL,
1126 packId TEXT NOT NULL,
1127
1128 emoji STRING,
1129 height INTEGER,
1130 isCoverOnly INTEGER,
1131 lastUsed INTEGER,
1132 path STRING,
1133 width INTEGER,
1134
1135 PRIMARY KEY (id, packId),
1136 CONSTRAINT stickers_fk
1137 FOREIGN KEY (packId)
1138 REFERENCES sticker_packs(id)
1139 ON DELETE CASCADE
1140 );
1141 CREATE TABLE sticker_references(
1142 messageId STRING,
1143 packId TEXT,
1144 CONSTRAINT sticker_references_fk
1145 FOREIGN KEY(packId)
1146 REFERENCES sticker_packs(id)
1147 ON DELETE CASCADE
1148 );
1149 CREATE TABLE emojis(
1150 shortName TEXT PRIMARY KEY,
1151 lastUsage INTEGER
1152 );
1153 CREATE TABLE messages(
1154 rowid INTEGER PRIMARY KEY ASC,
1155 id STRING UNIQUE,
1156 json TEXT,
1157 readStatus INTEGER,
1158 expires_at INTEGER,
1159 sent_at INTEGER,
1160 schemaVersion INTEGER,
1161 conversationId STRING,
1162 received_at INTEGER,
1163 source STRING,
1164 hasAttachments INTEGER,
1165 hasFileAttachments INTEGER,
1166 hasVisualMediaAttachments INTEGER,
1167 expireTimer INTEGER,
1168 expirationStartTimestamp INTEGER,
1169 type STRING,
1170 body TEXT,
1171 messageTimer INTEGER,
1172 messageTimerStart INTEGER,
1173 messageTimerExpiresAt INTEGER,
1174 isErased INTEGER,
1175 isViewOnce INTEGER,
1176 sourceServiceId TEXT, serverGuid STRING NULL, sourceDevice INTEGER, storyId STRING, isStory INTEGER
1177 GENERATED ALWAYS AS (type IS &#39;story&#39;), isChangeCreatedByUs INTEGER NOT NULL DEFAULT 0, isTimerChangeFromSync INTEGER
1178 GENERATED ALWAYS AS (
1179 json_extract(json, &#39;$.expirationTimerUpdate.fromSync&#39;) IS 1
1180 ), seenStatus NUMBER default 0, storyDistributionListId STRING, expiresAt INT
1181 GENERATED ALWAYS
1182 AS (ifnull(
1183 expirationStartTimestamp + (expireTimer * 1000),
1184 9007199254740991
1185 )), shouldAffectActivity INTEGER
1186 GENERATED ALWAYS AS (
1187 type IS NULL
1188 OR
1189 type NOT IN (
1190 &#39;change-number-notification&#39;,
1191 &#39;contact-removed-notification&#39;,
1192 &#39;conversation-merge&#39;,
1193 &#39;group-v1-migration&#39;,
1194 &#39;keychange&#39;,
1195 &#39;message-history-unsynced&#39;,
1196 &#39;profile-change&#39;,
1197 &#39;story&#39;,
1198 &#39;universal-timer-notification&#39;,
1199 &#39;verified-change&#39;
1200 )
1201 ), shouldAffectPreview INTEGER
1202 GENERATED ALWAYS AS (
1203 type IS NULL
1204 OR
1205 type NOT IN (
1206 &#39;change-number-notification&#39;,
1207 &#39;contact-removed-notification&#39;,
1208 &#39;conversation-merge&#39;,
1209 &#39;group-v1-migration&#39;,
1210 &#39;keychange&#39;,
1211 &#39;message-history-unsynced&#39;,
1212 &#39;profile-change&#39;,
1213 &#39;story&#39;,
1214 &#39;universal-timer-notification&#39;,
1215 &#39;verified-change&#39;
1216 )
1217 ), isUserInitiatedMessage INTEGER
1218 GENERATED ALWAYS AS (
1219 type IS NULL
1220 OR
1221 type NOT IN (
1222 &#39;change-number-notification&#39;,
1223 &#39;contact-removed-notification&#39;,
1224 &#39;conversation-merge&#39;,
1225 &#39;group-v1-migration&#39;,
1226 &#39;group-v2-change&#39;,
1227 &#39;keychange&#39;,
1228 &#39;message-history-unsynced&#39;,
1229 &#39;profile-change&#39;,
1230 &#39;story&#39;,
1231 &#39;universal-timer-notification&#39;,
1232 &#39;verified-change&#39;
1233 )
1234 ), mentionsMe INTEGER NOT NULL DEFAULT 0, isGroupLeaveEvent INTEGER
1235 GENERATED ALWAYS AS (
1236 type IS &#39;group-v2-change&#39; AND
1237 json_array_length(json_extract(json, &#39;$.groupV2Change.details&#39;)) IS 1 AND
1238 json_extract(json, &#39;$.groupV2Change.details[0].type&#39;) IS &#39;member-remove&#39; AND
1239 json_extract(json, &#39;$.groupV2Change.from&#39;) IS NOT NULL AND
1240 json_extract(json, &#39;$.groupV2Change.from&#39;) IS json_extract(json, &#39;$.groupV2Change.details[0].aci&#39;)
1241 ), isGroupLeaveEventFromOther INTEGER
1242 GENERATED ALWAYS AS (
1243 isGroupLeaveEvent IS 1
1244 AND
1245 isChangeCreatedByUs IS 0
1246 ), callId TEXT
1247 GENERATED ALWAYS AS (
1248 json_extract(json, &#39;$.callId&#39;)
1249 ));
1250 CREATE TABLE sqlite_stat4(tbl,idx,neq,nlt,ndlt,sample);
1251 CREATE TABLE jobs(
1252 id TEXT PRIMARY KEY,
1253 queueType TEXT STRING NOT NULL,
1254 timestamp INTEGER NOT NULL,
1255 data STRING TEXT
1256 );
1257 CREATE TABLE reactions(
1258 conversationId STRING,
1259 emoji STRING,
1260 fromId STRING,
1261 messageReceivedAt INTEGER,
1262 targetAuthorAci STRING,
1263 targetTimestamp INTEGER,
1264 unread INTEGER
1265 , messageId STRING);
1266 CREATE TABLE senderKeys(
1267 id TEXT PRIMARY KEY NOT NULL,
1268 senderId TEXT NOT NULL,
1269 distributionId TEXT NOT NULL,
1270 data BLOB NOT NULL,
1271 lastUpdatedDate NUMBER NOT NULL
1272 );
1273 CREATE TABLE unprocessed(
1274 id STRING PRIMARY KEY ASC,
1275 timestamp INTEGER,
1276 version INTEGER,
1277 attempts INTEGER,
1278 envelope TEXT,
1279 decrypted TEXT,
1280 source TEXT,
1281 serverTimestamp INTEGER,
1282 sourceServiceId STRING
1283 , serverGuid STRING NULL, sourceDevice INTEGER, receivedAtCounter INTEGER, urgent INTEGER, story INTEGER);
1284 CREATE TABLE sendLogPayloads(
1285 id INTEGER PRIMARY KEY ASC,
1286
1287 timestamp INTEGER NOT NULL,
1288 contentHint INTEGER NOT NULL,
1289 proto BLOB NOT NULL
1290 , urgent INTEGER, hasPniSignatureMessage INTEGER DEFAULT 0 NOT NULL);
1291 CREATE TABLE sendLogRecipients(
1292 payloadId INTEGER NOT NULL,
1293
1294 recipientServiceId STRING NOT NULL,
1295 deviceId INTEGER NOT NULL,
1296
1297 PRIMARY KEY (payloadId, recipientServiceId, deviceId),
1298
1299 CONSTRAINT sendLogRecipientsForeignKey
1300 FOREIGN KEY (payloadId)
1301 REFERENCES sendLogPayloads(id)
1302 ON DELETE CASCADE
1303 );
1304 CREATE TABLE sendLogMessageIds(
1305 payloadId INTEGER NOT NULL,
1306
1307 messageId STRING NOT NULL,
1308
1309 PRIMARY KEY (payloadId, messageId),
1310
1311 CONSTRAINT sendLogMessageIdsForeignKey
1312 FOREIGN KEY (payloadId)
1313 REFERENCES sendLogPayloads(id)
1314 ON DELETE CASCADE
1315 );
1316 CREATE TABLE preKeys(
1317 id STRING PRIMARY KEY ASC,
1318 json TEXT
1319 , ourServiceId NUMBER
1320 GENERATED ALWAYS AS (json_extract(json, &#39;$.ourServiceId&#39;)));
1321 CREATE TABLE signedPreKeys(
1322 id STRING PRIMARY KEY ASC,
1323 json TEXT
1324 , ourServiceId NUMBER
1325 GENERATED ALWAYS AS (json_extract(json, &#39;$.ourServiceId&#39;)));
1326 CREATE TABLE badges(
1327 id TEXT PRIMARY KEY,
1328 category TEXT NOT NULL,
1329 name TEXT NOT NULL,
1330 descriptionTemplate TEXT NOT NULL
1331 );
1332 CREATE TABLE badgeImageFiles(
1333 badgeId TEXT REFERENCES badges(id)
1334 ON DELETE CASCADE
1335 ON UPDATE CASCADE,
1336 &#39;order&#39; INTEGER NOT NULL,
1337 url TEXT NOT NULL,
1338 localPath TEXT,
1339 theme TEXT NOT NULL
1340 );
1341 CREATE TABLE storyReads (
1342 authorId STRING NOT NULL,
1343 conversationId STRING NOT NULL,
1344 storyId STRING NOT NULL,
1345 storyReadDate NUMBER NOT NULL,
1346
1347 PRIMARY KEY (authorId, storyId)
1348 );
1349 CREATE TABLE storyDistributions(
1350 id STRING PRIMARY KEY NOT NULL,
1351 name TEXT,
1352
1353 senderKeyInfoJson STRING
1354 , deletedAtTimestamp INTEGER, allowsReplies INTEGER, isBlockList INTEGER, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync INTEGER);
1355 CREATE TABLE storyDistributionMembers(
1356 listId STRING NOT NULL REFERENCES storyDistributions(id)
1357 ON DELETE CASCADE
1358 ON UPDATE CASCADE,
1359 serviceId STRING NOT NULL,
1360
1361 PRIMARY KEY (listId, serviceId)
1362 );
1363 CREATE TABLE uninstalled_sticker_packs (
1364 id STRING NOT NULL PRIMARY KEY,
1365 uninstalledAt NUMBER NOT NULL,
1366 storageID STRING,
1367 storageVersion NUMBER,
1368 storageUnknownFields BLOB,
1369 storageNeedsSync INTEGER NOT NULL
1370 );
1371 CREATE TABLE groupCallRingCancellations(
1372 ringId INTEGER PRIMARY KEY,
1373 createdAt INTEGER NOT NULL
1374 );
1375 CREATE TABLE IF NOT EXISTS &#39;messages_fts_data&#39;(id INTEGER PRIMARY KEY, block BLOB);
1376 CREATE TABLE IF NOT EXISTS &#39;messages_fts_idx&#39;(segid, term, pgno, PRIMARY KEY(segid, term)) WITHOUT ROWID;
1377 CREATE TABLE IF NOT EXISTS &#39;messages_fts_content&#39;(id INTEGER PRIMARY KEY, c0);
1378 CREATE TABLE IF NOT EXISTS &#39;messages_fts_docsize&#39;(id INTEGER PRIMARY KEY, sz BLOB);
1379 CREATE TABLE IF NOT EXISTS &#39;messages_fts_config&#39;(k PRIMARY KEY, v) WITHOUT ROWID;
1380 CREATE TABLE edited_messages(
1381 messageId STRING REFERENCES messages(id)
1382 ON DELETE CASCADE,
1383 sentAt INTEGER,
1384 readStatus INTEGER
1385 , conversationId STRING);
1386 CREATE TABLE mentions (
1387 messageId REFERENCES messages(id) ON DELETE CASCADE,
1388 mentionAci STRING,
1389 start INTEGER,
1390 length INTEGER
1391 );
1392 CREATE TABLE kyberPreKeys(
1393 id STRING PRIMARY KEY NOT NULL,
1394 json TEXT NOT NULL, ourServiceId NUMBER
1395 GENERATED ALWAYS AS (json_extract(json, &#39;$.ourServiceId&#39;)));
1396 CREATE TABLE callsHistory (
1397 callId TEXT PRIMARY KEY,
1398 peerId TEXT NOT NULL, -- conversation id (legacy) | uuid | groupId | roomId
1399 ringerId TEXT DEFAULT NULL, -- ringer uuid
1400 mode TEXT NOT NULL, -- enum &quot;Direct&quot; | &quot;Group&quot;
1401 type TEXT NOT NULL, -- enum &quot;Audio&quot; | &quot;Video&quot; | &quot;Group&quot;
1402 direction TEXT NOT NULL, -- enum &quot;Incoming&quot; | &quot;Outgoing
1403 -- Direct: enum &quot;Pending&quot; | &quot;Missed&quot; | &quot;Accepted&quot; | &quot;Deleted&quot;
1404 -- Group: enum &quot;GenericGroupCall&quot; | &quot;OutgoingRing&quot; | &quot;Ringing&quot; | &quot;Joined&quot; | &quot;Missed&quot; | &quot;Declined&quot; | &quot;Accepted&quot; | &quot;Deleted&quot;
1405 status TEXT NOT NULL,
1406 timestamp INTEGER NOT NULL,
1407 UNIQUE (callId, peerId) ON CONFLICT FAIL
1408 );
1409 [ dropped all indexes to save space in this blog post ]
1410 CREATE TRIGGER messages_on_view_once_update AFTER UPDATE ON messages
1411 WHEN
1412 new.body IS NOT NULL AND new.isViewOnce = 1
1413 BEGIN
1414 DELETE FROM messages_fts WHERE rowid = old.rowid;
1415 END;
1416 CREATE TRIGGER messages_on_insert AFTER INSERT ON messages
1417 WHEN new.isViewOnce IS NOT 1 AND new.storyId IS NULL
1418 BEGIN
1419 INSERT INTO messages_fts
1420 (rowid, body)
1421 VALUES
1422 (new.rowid, new.body);
1423 END;
1424 CREATE TRIGGER messages_on_delete AFTER DELETE ON messages BEGIN
1425 DELETE FROM messages_fts WHERE rowid = old.rowid;
1426 DELETE FROM sendLogPayloads WHERE id IN (
1427 SELECT payloadId FROM sendLogMessageIds
1428 WHERE messageId = old.id
1429 );
1430 DELETE FROM reactions WHERE rowid IN (
1431 SELECT rowid FROM reactions
1432 WHERE messageId = old.id
1433 );
1434 DELETE FROM storyReads WHERE storyId = old.storyId;
1435 END;
1436 CREATE VIRTUAL TABLE messages_fts USING fts5(
1437 body,
1438 tokenize = &#39;signal_tokenizer&#39;
1439 );
1440 CREATE TRIGGER messages_on_update AFTER UPDATE ON messages
1441 WHEN
1442 (new.body IS NULL OR old.body IS NOT new.body) AND
1443 new.isViewOnce IS NOT 1 AND new.storyId IS NULL
1444 BEGIN
1445 DELETE FROM messages_fts WHERE rowid = old.rowid;
1446 INSERT INTO messages_fts
1447 (rowid, body)
1448 VALUES
1449 (new.rowid, new.body);
1450 END;
1451 CREATE TRIGGER messages_on_insert_insert_mentions AFTER INSERT ON messages
1452 BEGIN
1453 INSERT INTO mentions (messageId, mentionAci, start, length)
1454
1455 SELECT messages.id, bodyRanges.value -&gt;&gt; &#39;mentionAci&#39; as mentionAci,
1456 bodyRanges.value -&gt;&gt; &#39;start&#39; as start,
1457 bodyRanges.value -&gt;&gt; &#39;length&#39; as length
1458 FROM messages, json_each(messages.json -&gt;&gt; &#39;bodyRanges&#39;) as bodyRanges
1459 WHERE bodyRanges.value -&gt;&gt; &#39;mentionAci&#39; IS NOT NULL
1460
1461 AND messages.id = new.id;
1462 END;
1463 CREATE TRIGGER messages_on_update_update_mentions AFTER UPDATE ON messages
1464 BEGIN
1465 DELETE FROM mentions WHERE messageId = new.id;
1466 INSERT INTO mentions (messageId, mentionAci, start, length)
1467
1468 SELECT messages.id, bodyRanges.value -&gt;&gt; &#39;mentionAci&#39; as mentionAci,
1469 bodyRanges.value -&gt;&gt; &#39;start&#39; as start,
1470 bodyRanges.value -&gt;&gt; &#39;length&#39; as length
1471 FROM messages, json_each(messages.json -&gt;&gt; &#39;bodyRanges&#39;) as bodyRanges
1472 WHERE bodyRanges.value -&gt;&gt; &#39;mentionAci&#39; IS NOT NULL
1473
1474 AND messages.id = new.id;
1475 END;
1476 sqlite&gt;
1477 &lt;/pre&gt;
1478
1479 &lt;p&gt;Finally I have the tool needed to inspect and process Signal
1480 messages that I need, without using the vendor provided client. Now
1481 on to transforming it to a more useful format.&lt;/p&gt;
1482
1483 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1484 activities, please send Bitcoin donations to my address
1485 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1486 </description>
1487 </item>
1488
1489 <item>
1490 <title>New chrpath release 0.17</title>
1491 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html</link>
1492 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html</guid>
1493 <pubDate>Fri, 10 Nov 2023 07:30:00 +0100</pubDate>
1494 <description>&lt;p&gt;The chrpath package provide a simple command line tool to remove or
1495 modify the rpath or runpath of compiled ELF program. It is almost 10
1496 years since I updated the code base, but I stumbled over the tool
1497 today, and decided it was time to move the code base from Subversion
1498 to git and find a new home for it, as the previous one (Debian Alioth)
1499 has been shut down. I decided to go with
1500 &lt;a href=&quot;https://codeberg.org/&quot;&gt;Codeberg&lt;/a&gt; this time, as it is my git
1501 service of choice these days, did a quick and dirty migration to git
1502 and updated the code with a few patches I found in the Debian bug
1503 tracker. These are the release notes:&lt;/p&gt;
1504
1505 &lt;p&gt;New in 0.17 released 2023-11-10:&lt;/p&gt;
1506
1507 &lt;ul&gt;
1508 &lt;li&gt;Moved project to Codeberg, as Alioth is shut down.&lt;/li&gt;
1509 &lt;li&gt;Add Solaris support (use &amp;lt;sys/byteorder.h&gt; instead of &amp;lt;byteswap.h&gt;).
1510 Patch from Rainer Orth.&lt;/li&gt;
1511 &lt;li&gt;Added missing newline from printf() line. Patch from Frank Dana.&lt;/li&gt;
1512 &lt;li&gt;Corrected handling of multiple ELF sections. Patch from Frank Dana.&lt;/li&gt;
1513 &lt;li&gt;Updated build rules for .deb. Partly based on patch from djcj.&lt;/li&gt;
1514 &lt;/ul&gt;
1515
1516 &lt;p&gt;The latest edition is tagged and available from
1517 &lt;a href=&quot;https://codeberg.org/pere/chrpath&quot;&gt;https://codeberg.org/pere/chrpath&lt;/a&gt;.
1518
1519 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1520 activities, please send Bitcoin donations to my address
1521 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1522 </description>
1523 </item>
1524
1525 </channel>
1526 </rss>