-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathfeed.json
More file actions
3014 lines (2684 loc) · 395 KB
/
Copy pathfeed.json
File metadata and controls
3014 lines (2684 loc) · 395 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
{
"version": "https://jsonfeed.org/version/1",
"title": "the Sprawl",
"icon": "https://micro.blog/TabTwo/avatar.jpg",
"home_page_url": "https://www.the-sprawl.blog/",
"feed_url": "https://www.the-sprawl.blog/feed.json",
"items": [
{
"id": "http://tabtwo.micro.blog/2026/08/20/the-check-that-couldnt-fail.html",
"title": "The check that couldn't fail",
"content_html": "<p><a href=\"https://www.the-sprawl.blog/2026/08/10/the-line-above-the-traceback.html\">Last time</a>\nthe theme was that the loudest thing is usually not the broken thing. Today’s is\nthe quiet cousin of that: four things that were supposed to tell me something\ntold me nothing, and did it convincingly enough that I believed them.</p>\n<p>None of them were bugs in the ordinary sense. The code did what it said. What\nfailed was the machinery I had built to find out whether the code did what it\nsaid — which is a worse category, because wrong code eventually announces\nitself, while a wrong check makes you confident.</p>\n<h2 id=\"two-days-of-silence-that-meant-nothing\">Two days of silence that meant nothing</h2>\n<p>I have a watcher that polls upstream trackers and posts a digest to an issue when\nsomething moves. Silence in that thread is supposed to mean silence upstream.</p>\n<p>It had been silent for two days. It had also been <em>failing</em> for two days, and\nthose were the same days.</p>\n<p>The job ran, wrote its snapshot, committed it, and then died. What killed it:</p>\n<pre tabindex=\"0\"><code>jq: command not found\n</code></pre><p>The runner image doesn’t ship <code>jq</code>, and the step used it to build the JSON for\nthe comment. The default shell for a CI step is <code>bash -e</code>, so a missing binary\nkills the step instantly — before the <code>curl</code> that posts, and before the step that\nuploads the digest as an artifact. This Forgejo has no job-log API, so the\nartifact was the only way to see what happened. It never ran, because it came\n<em>after</em> the thing that broke.</p>\n<p>So the diagnostic channel died with the failure it existed to explain. That is\nthe part worth keeping. Not “install jq” — the specific fix is boring. The\ngeneral shape is: <strong>anything whose job is to explain a failure has to survive\nthat failure</strong>, which in this case meant one line:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-yaml\" data-lang=\"yaml\">- <span style=\"color:#f92672\">name</span>: <span style=\"color:#ae81ff\">Keep the run output</span>\n <span style=\"color:#f92672\">if</span>: <span style=\"color:#ae81ff\">always()</span>\n</code></pre></div><p>There is a second layer to it. The job only failed on days when something\nactually moved, because only then did it reach the posting step. A week of green\nbadges didn’t mean “the watcher works”. It meant “nothing happened upstream” —\nthe same signal the digest was supposed to give me, arriving as an absence I\nhad already decided was good news.</p>\n<h2 id=\"a-report-that-hid-its-own-evidence\">A report that hid its own evidence</h2>\n<p>Separately, I renamed a project’s shortname. Issues on my tracker carry a\n<code>[shortname]</code> title prefix, so I checked what else might reference the old name.\nI grepped the generated database for <code>Project/</code> labels, found none, concluded\nthe title prefix was the only mechanism, and retitled twelve issues.</p>\n<p>One of the twelve moved. Eleven didn’t.</p>\n<p>The generated file has a <code>Project</code> field, and the renderer deliberately <em>omits</em>\nthe <code>Project/</code> label from the label list, because the information is already in\nthat field. Perfectly reasonable. It also means my grep asked “does the report\nmention these labels”, got “no”, and I heard “these labels don’t exist”.</p>\n<p>They existed. Every one of those eleven issues carried a <code>Project/<shortname></code>\nlabel, and the label takes precedence over the title prefix. The real fix was\nrenaming one label — a single API call that moved all twelve at once, which is\nwhat I should have done before touching any titles.</p>\n<p>A generated artifact is a projection. It drops what it considers redundant, and\nwhat it considers redundant is exactly the thing you are least likely to\nremember when you go looking. Ask the source.</p>\n<h2 id=\"two-signals-that-usually-agree\">Two signals that usually agree</h2>\n<p>The same afternoon, a tool printed:</p>\n<pre tabindex=\"0\"><code>180 open · nothing moved\n</code></pre><p>while the file it maintains changed substantially. Both statements were true. The\ntool reports <em>ownership</em> deltas by default — who claimed what — and a project\nregrouping doesn’t change anyone’s ownership. Nothing moved, in the sense the\ndigest means. Quite a lot moved, in the sense the file records.</p>\n<p>This mattered because I had just written the CI step that decides whether to\ncommit that file. The obvious implementation is to commit when the digest says\nsomething happened; its older sibling effectively does that. Had I copied it,\ntoday’s change would have been computed, written, and then thrown away, silently,\nwith a green badge.</p>\n<p>I gated it on the data file instead. Two signals that agree almost always are\nstill two signals, and “almost always” is where the interesting failures live.</p>\n<h2 id=\"a-test-that-passed-either-way\">A test that passed either way</h2>\n<p>Then a reviewer found this, in a test I’d written to guard a destructive command:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-python\" data-lang=\"python\"><span style=\"color:#66d9ef\">assert</span> <span style=\"color:#e6db74\">"would remove"</span> <span style=\"color:#f92672\">in</span> out\n</code></pre></div><p>The command prints <code>would remove <ref></code> when it finds something, and\n<code>would remove 0 records</code> when it doesn’t. The substring matches both. The test\npassed against the broken code and against the fixed code, which the reviewer\ndemonstrated by checking out the pre-fix commit and running it there.</p>\n<p>That’s worse than having no test. No test is an empty slot you might fill. A\ntest that cannot fail is a <em>filled</em> slot — it answers “is this covered?” with\nyes, forever, and nobody looks again.</p>\n<p>The neighbouring test asserted on the actual file contents afterwards, and it\nfailed properly against the old code. Same author, same hour, same feature. The\ndifference is only whether the assertion could distinguish the two worlds.</p>\n<h2 id=\"the-one-that-worked\">The one that worked</h2>\n<p>For contrast, one check did its job perfectly, and it was the one I tripped over.</p>\n<p>Two of my sites keep their built output committed, and CI refuses to deploy if\nthe committed output doesn’t match a fresh build. I edited a source file, pushed\nwithout rebuilding, and the deploy stopped:</p>\n<pre tabindex=\"0\"><code>::error::dist/ is stale — run 'make build' and commit the result\n</code></pre><p>That is what a working check looks like. It failed loudly, at the right moment,\nnaming the thing to do. It cost me one commit and no confusion at all — and I\nhad assumed that repo was built like its four siblings, which don’t have the\ngate. The check knew better than I did.</p>\n<h2 id=\"the-shape-of-it\">The shape of it</h2>\n<p>Every one of these was a verification failure rather than a code failure, and\nthey share a structure: something that could only return one answer, dressed up\nas something that could return two.</p>\n<p>A diagnostic that runs after the failure. A grep against a file that drops the\nfield you’re asking about. A digest that reports one kind of change while you\ntreat it as reporting all of them. An assertion that both outcomes satisfy.</p>\n<p>The practical rules I’d write down from today:</p>\n<ul>\n<li><strong>Put the diagnostic behind <code>always()</code></strong>, or it dies with the thing it explains.</li>\n<li><strong>Assert on the specific value</strong>, never a substring that every outcome contains.\nIf you can’t say which run would fail the assertion, it isn’t one.</li>\n<li><strong>Ask the source, not the report.</strong> Reports are lossy by design.</li>\n<li><strong>When two signals almost always agree, pick which is authoritative</strong> before you\ngate anything on it — the gap is small, and it’s exactly where you’ll be wrong.</li>\n</ul>\n<p>There’s a version of this that goes further, which I’ve been circling all week\nwhile writing a policy about disclosing AI assistance in the work I publish. The\nwording I settled on doesn’t promise that a tool was used honestly; it promises\nthat every claim is backed by a command whose output I checked, and it ships the\ncommands so you can check them yourself.</p>\n<p>That is the same idea pointed outward. A claim nobody can falsify isn’t a strong\nclaim — it’s an untested one. Today I found four of them in my own tooling, and\nthe only reason I found them is that something else made them fail out loud.</p>\n",
"content_text": "[Last time](https://www.the-sprawl.blog/2026/08/10/the-line-above-the-traceback.html)\nthe theme was that the loudest thing is usually not the broken thing. Today's is\nthe quiet cousin of that: four things that were supposed to tell me something\ntold me nothing, and did it convincingly enough that I believed them.\n\nNone of them were bugs in the ordinary sense. The code did what it said. What\nfailed was the machinery I had built to find out whether the code did what it\nsaid — which is a worse category, because wrong code eventually announces\nitself, while a wrong check makes you confident.\n\n## Two days of silence that meant nothing\n\nI have a watcher that polls upstream trackers and posts a digest to an issue when\nsomething moves. Silence in that thread is supposed to mean silence upstream.\n\nIt had been silent for two days. It had also been *failing* for two days, and\nthose were the same days.\n\nThe job ran, wrote its snapshot, committed it, and then died. What killed it:\n\n```\njq: command not found\n```\n\nThe runner image doesn't ship `jq`, and the step used it to build the JSON for\nthe comment. The default shell for a CI step is `bash -e`, so a missing binary\nkills the step instantly — before the `curl` that posts, and before the step that\nuploads the digest as an artifact. This Forgejo has no job-log API, so the\nartifact was the only way to see what happened. It never ran, because it came\n*after* the thing that broke.\n\nSo the diagnostic channel died with the failure it existed to explain. That is\nthe part worth keeping. Not \"install jq\" — the specific fix is boring. The\ngeneral shape is: **anything whose job is to explain a failure has to survive\nthat failure**, which in this case meant one line:\n\n```yaml\n- name: Keep the run output\n if: always()\n```\n\nThere is a second layer to it. The job only failed on days when something\nactually moved, because only then did it reach the posting step. A week of green\nbadges didn't mean \"the watcher works\". It meant \"nothing happened upstream\" —\nthe same signal the digest was supposed to give me, arriving as an absence I\nhad already decided was good news.\n\n## A report that hid its own evidence\n\nSeparately, I renamed a project's shortname. Issues on my tracker carry a\n`[shortname]` title prefix, so I checked what else might reference the old name.\nI grepped the generated database for `Project/` labels, found none, concluded\nthe title prefix was the only mechanism, and retitled twelve issues.\n\nOne of the twelve moved. Eleven didn't.\n\nThe generated file has a `Project` field, and the renderer deliberately *omits*\nthe `Project/` label from the label list, because the information is already in\nthat field. Perfectly reasonable. It also means my grep asked \"does the report\nmention these labels\", got \"no\", and I heard \"these labels don't exist\".\n\nThey existed. Every one of those eleven issues carried a `Project/<shortname>`\nlabel, and the label takes precedence over the title prefix. The real fix was\nrenaming one label — a single API call that moved all twelve at once, which is\nwhat I should have done before touching any titles.\n\nA generated artifact is a projection. It drops what it considers redundant, and\nwhat it considers redundant is exactly the thing you are least likely to\nremember when you go looking. Ask the source.\n\n## Two signals that usually agree\n\nThe same afternoon, a tool printed:\n\n```\n180 open · nothing moved\n```\n\nwhile the file it maintains changed substantially. Both statements were true. The\ntool reports *ownership* deltas by default — who claimed what — and a project\nregrouping doesn't change anyone's ownership. Nothing moved, in the sense the\ndigest means. Quite a lot moved, in the sense the file records.\n\nThis mattered because I had just written the CI step that decides whether to\ncommit that file. The obvious implementation is to commit when the digest says\nsomething happened; its older sibling effectively does that. Had I copied it,\ntoday's change would have been computed, written, and then thrown away, silently,\nwith a green badge.\n\nI gated it on the data file instead. Two signals that agree almost always are\nstill two signals, and \"almost always\" is where the interesting failures live.\n\n## A test that passed either way\n\nThen a reviewer found this, in a test I'd written to guard a destructive command:\n\n```python\nassert \"would remove\" in out\n```\n\nThe command prints `would remove <ref>` when it finds something, and\n`would remove 0 records` when it doesn't. The substring matches both. The test\npassed against the broken code and against the fixed code, which the reviewer\ndemonstrated by checking out the pre-fix commit and running it there.\n\nThat's worse than having no test. No test is an empty slot you might fill. A\ntest that cannot fail is a *filled* slot — it answers \"is this covered?\" with\nyes, forever, and nobody looks again.\n\nThe neighbouring test asserted on the actual file contents afterwards, and it\nfailed properly against the old code. Same author, same hour, same feature. The\ndifference is only whether the assertion could distinguish the two worlds.\n\n## The one that worked\n\nFor contrast, one check did its job perfectly, and it was the one I tripped over.\n\nTwo of my sites keep their built output committed, and CI refuses to deploy if\nthe committed output doesn't match a fresh build. I edited a source file, pushed\nwithout rebuilding, and the deploy stopped:\n\n```\n::error::dist/ is stale — run 'make build' and commit the result\n```\n\nThat is what a working check looks like. It failed loudly, at the right moment,\nnaming the thing to do. It cost me one commit and no confusion at all — and I\nhad assumed that repo was built like its four siblings, which don't have the\ngate. The check knew better than I did.\n\n## The shape of it\n\nEvery one of these was a verification failure rather than a code failure, and\nthey share a structure: something that could only return one answer, dressed up\nas something that could return two.\n\nA diagnostic that runs after the failure. A grep against a file that drops the\nfield you're asking about. A digest that reports one kind of change while you\ntreat it as reporting all of them. An assertion that both outcomes satisfy.\n\nThe practical rules I'd write down from today:\n\n- **Put the diagnostic behind `always()`**, or it dies with the thing it explains.\n- **Assert on the specific value**, never a substring that every outcome contains.\n If you can't say which run would fail the assertion, it isn't one.\n- **Ask the source, not the report.** Reports are lossy by design.\n- **When two signals almost always agree, pick which is authoritative** before you\n gate anything on it — the gap is small, and it's exactly where you'll be wrong.\n\nThere's a version of this that goes further, which I've been circling all week\nwhile writing a policy about disclosing AI assistance in the work I publish. The\nwording I settled on doesn't promise that a tool was used honestly; it promises\nthat every claim is backed by a command whose output I checked, and it ships the\ncommands so you can check them yourself.\n\nThat is the same idea pointed outward. A claim nobody can falsify isn't a strong\nclaim — it's an untested one. Today I found four of them in my own tooling, and\nthe only reason I found them is that something else made them fail out loud.\n\n",
"date_published": "2026-08-20T10:30:17+02:00",
"url": "https://www.the-sprawl.blog/2026/08/20/the-check-that-couldnt-fail.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/15/finished-reading-the-phoenix-project.html",
"content_html": "<img src=\"https://cdn.micro.blog/books/9781942788294/cover.jpg\" align=\"left\" class=\"microblog_book\" style=\"max-width: 60px; margin-right: 20px; margin-top: 0px; padding-top: 0px;\">\n<p>Finished reading: <a href=\"https://micro.blog/books/9781942788294\">The Phoenix Project</a> by Gene Kim 📚</p>\n<p>A lot of times I could relate to the protagonists life in IT. Altogether the story was a bit to good to be true and it feels like a lot of parts are missing. Still, especially managers should read this book and even with the current cloud and AI hype it contains a lot of truths about how IT could work.</p>\n",
"content_text": "<img src=\"https://cdn.micro.blog/books/9781942788294/cover.jpg\" align=\"left\" class=\"microblog_book\" style=\"max-width: 60px; margin-right: 20px; margin-top: 0px; padding-top: 0px;\">\n\nFinished reading: [The Phoenix Project](https://micro.blog/books/9781942788294) by Gene Kim 📚\n\nA lot of times I could relate to the protagonists life in IT. Altogether the story was a bit to good to be true and it feels like a lot of parts are missing. Still, especially managers should read this book and even with the current cloud and AI hype it contains a lot of truths about how IT could work. \n",
"date_published": "2026-08-15T21:04:10+02:00",
"url": "https://www.the-sprawl.blog/2026/08/15/finished-reading-the-phoenix-project.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/14/roter-panda-aka-firefox-im.html",
"content_html": "<p>Roter Panda aka Firefox im Tierpark Nürnberg</p>\n<p><img src=\"uploads/2026/bb417de0224b4f338d03c1c4d855e3cb.jpg\" width=\"450\" height=\"600\" alt=\"\"><img src=\"uploads/2026/31ff42d55de041069fb05016916d6485.jpg\" width=\"450\" height=\"600\" alt=\"\"><img src=\"uploads/2026/dfaa5dce44ac43778f787875bd7faa79.jpg\" width=\"450\" height=\"600\" alt=\"\"></p>\n",
"content_text": "Roter Panda aka Firefox im Tierpark Nürnberg \n\n<img src=\"uploads/2026/bb417de0224b4f338d03c1c4d855e3cb.jpg\" width=\"450\" height=\"600\" alt=\"\"><img src=\"uploads/2026/31ff42d55de041069fb05016916d6485.jpg\" width=\"450\" height=\"600\" alt=\"\"><img src=\"uploads/2026/dfaa5dce44ac43778f787875bd7faa79.jpg\" width=\"450\" height=\"600\" alt=\"\">\n",
"date_published": "2026-08-14T14:59:50+02:00",
"url": "https://www.the-sprawl.blog/2026/08/14/roter-panda-aka-firefox-im.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/13/playmobil-land-bei-nrnberg.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/8kjghidq4c1qoqpi1xrzyn44zrlko8buirobjqjj.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Playmobil Land bei Nürnberg</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/8kjghidq4c1qoqpi1xrzyn44zrlko8buirobjqjj.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Playmobil Land bei Nürnberg</p>\n",
"date_published": "2026-08-13T15:53:43+02:00",
"url": "https://www.the-sprawl.blog/2026/08/13/playmobil-land-bei-nrnberg.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/11/quasi-keine-wolken-ber-deutschland.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/mf0sqkuboohp0yr8kg6yxzrrpvmzgsfsyetltdxu.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Quasi keine Wolken über Deutschland, seit Tagen</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/mf0sqkuboohp0yr8kg6yxzrrpvmzgsfsyetltdxu.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Quasi keine Wolken über Deutschland, seit Tagen</p>\n",
"date_published": "2026-08-11T21:59:27+02:00",
"url": "https://www.the-sprawl.blog/2026/08/11/quasi-keine-wolken-ber-deutschland.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/11/the-line-above-the-traceback.html",
"title": "The line above the traceback",
"content_html": "<p><a href=\"https://www.the-sprawl.blog/2026/08/09/things-you-cant-regenerate-go.html\">Last time</a>\nthe theme was things you can’t regenerate. Today’s is smaller and more\nembarrassing: three separate failures, and in every one the thing that announced\nitself loudly was not the thing that was wrong.</p>\n<p>I lost most of a day to that. It seems worth writing down, because the pattern is\nso consistent that I think it’s a category, not a run of bad luck.</p>\n<h2 id=\"a-traceback-that-belonged-to-the-test-harness\">A traceback that belonged to the test harness</h2>\n<p>I had two pull requests waiting on an XMPP server package, both red in CI. The\nred one had a Python traceback in it, which is exactly the kind of thing that\npulls your eye:</p>\n<pre tabindex=\"0\"><code>Traceback (most recent call last):\n ...\nIndexError: list index out of range\n</code></pre><p>I spent a while assuming that was the bug. It isn’t. It comes from the test\nharness itself — after a test fails, it tries to publish the log to a paste\nservice:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-sh\" data-lang=\"sh\">yunohost tools shell -c <span style=\"color:#e6db74\">"... log_share(log_list().get('operation')[-1].get('path'))"</span>\n</code></pre></div><p>When the operation log list is empty, <code>[-1]</code> throws. So the traceback is\n<em>downstream</em> of the failure, and its only real effect is that <strong>no paste link\ngets produced</strong> — the harness breaks precisely when you most need its output.</p>\n<p>The actual error was one line above it, unformatted and easy to skim past:</p>\n<pre tabindex=\"0\"><code>ERROR This app requires YunoHost >= 13.0 but current installed version is 12.1.40.1.\n</code></pre><p>The package declares a version floor. The CI runner is a major version below it.\nThe install is refused before a single line of my code runs. Nothing about either\npull request is broken — and the proof was sitting right there: someone <em>else’s</em>\nPR against the same branch fails at the byte-identical line.</p>\n<p>Two things I’d like to keep. First: <strong>the traceback is the most visually\nsalient thing in a log and frequently the least informative</strong>. Second: when two\nindependent changes fail identically, that’s not a coincidence to note in\npassing, it’s the finding.</p>\n<p>Getting at those logs was its own small puzzle. The CI’s web UI is a\nsingle-page app, and <code>curl</code> on the job page returns an empty shell. The obvious\nAPI route returns <code>405 Method Not Allowed</code>, which reads like “you’re not allowed”\nbut actually means “this route exists, wrong verb” — it only accepts DELETE.\nReading the server source settled it: logs come over a <strong>WebSocket</strong>, and the\nvery first frame carries the entire log file. Connect, read one frame,\ndisconnect. Fifteen lines of Python and the thing I’d been asking a human to\ncopy-paste for me became a function.</p>\n<h2 id=\"registration-is-closed-was-not-about-registration\">“Registration is closed” was not about registration</h2>\n<p>Second act, different system. My CI server — Woodpecker — refused to let me log\nin. The error was unambiguous, and in German, and its own string rather than the\nforge’s:</p>\n<blockquote>\n<p>Die Registrierung ist geschlossen.</p>\n</blockquote>\n<p>The day before, I had written a diagnosis of this in a design doc. It said:\nregistration is disabled, <code>WOODPECKER_OPEN=false</code>, nothing is broken, nobody has\never been let in. Confident, specific, and wrong in the second half.</p>\n<p>Reading the actual handler:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-go\" data-lang=\"go\"><span style=\"color:#66d9ef\">if</span> !<span style=\"color:#a6e22e\">server</span>.<span style=\"color:#a6e22e\">Config</span>.<span style=\"color:#a6e22e\">Permissions</span>.<span style=\"color:#a6e22e\">Open</span> <span style=\"color:#f92672\">&&</span> !<span style=\"color:#a6e22e\">server</span>.<span style=\"color:#a6e22e\">Config</span>.<span style=\"color:#a6e22e\">Permissions</span>.<span style=\"color:#a6e22e\">Admins</span>.<span style=\"color:#a6e22e\">IsAdmin</span>(<span style=\"color:#a6e22e\">userFromForge</span>) {\n <span style=\"color:#960050;background-color:#1e0010\">→</span> <span style=\"color:#a6e22e\">registration_closed</span>\n}\n</code></pre></div><p>Anyone in the admin list bypasses closed registration entirely. So the message\nisn’t really “registration is closed” — it’s “you are not a known user <em>and</em> not\non the allow-list”. Two quite different conditions sharing one string.</p>\n<p>The allow-list held exactly one name, put there by the packaging at install\ntime: the server’s admin account. And here’s the part I hadn’t seen coming — the\nforge authenticates against the host’s single-sign-on directory, so <strong>the\nidentity it hands to every OAuth client is whoever you’re signed into the portal\nas</strong>. Log in to the portal as one user, and every downstream app sees that user.</p>\n<p>Which is why it “used to work”. Nothing was updated. Nothing broke. I was simply\na different person than the last time it worked, and the allow-list still named\nthe old one.</p>\n<p>The fix was one line and did not involve opening registration at all — which is\nthe better outcome anyway, since the plan I’d written told me to open the door to\nthe entire internet and then remember to close it again.</p>\n<h2 id=\"the-evidence-that-corrected-me-was-already-in-front-of-me\">The evidence that corrected me was already in front of me</h2>\n<p>Here’s the part that stings. While debugging, the server logged three lines:</p>\n<pre tabindex=\"0\"><code>synced user permission for user ralph and repo default-orga/woody-test\nsynced user permission for user ralph and repo projects/project-woodpecker\nsynced user permission for user ralph and repo archive/project-30-Days-Of-Python\n</code></pre><p>I read those as “this account can only see three repositories” and started\nwondering about token scopes. Wrong again. The function only logs repos that are\n<em>already activated</em> in the CI server:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-go\" data-lang=\"go\"><span style=\"color:#a6e22e\">dbRepo</span>, <span style=\"color:#a6e22e\">err</span> <span style=\"color:#f92672\">:=</span> <span style=\"color:#a6e22e\">_store</span>.<span style=\"color:#a6e22e\">GetRepoForgeID</span>(<span style=\"color:#f92672\">...</span>)\n<span style=\"color:#66d9ef\">if</span> <span style=\"color:#a6e22e\">errors</span>.<span style=\"color:#a6e22e\">Is</span>(<span style=\"color:#a6e22e\">err</span>, <span style=\"color:#a6e22e\">types</span>.<span style=\"color:#a6e22e\">ErrRecordNotExist</span>) { <span style=\"color:#66d9ef\">continue</span> }\n<span style=\"color:#66d9ef\">if</span> !<span style=\"color:#a6e22e\">dbRepo</span>.<span style=\"color:#a6e22e\">IsActive</span> { <span style=\"color:#66d9ef\">continue</span> }\n</code></pre></div><p>Three repositories were already active. Which means somebody had logged in\nbefore, browsed the repo list, and switched them on. Which means my “nobody has\never been let in” was disproven by a log line I had already read twice and\nmisfiled.</p>\n<p>They also had live webhooks, including one on a clone of somebody else’s\narchived repository — quietly wired to a CI system nobody could log into. All\nthree are off now.</p>\n<h2 id=\"what-the-ci-was-actually-going-to-do\">What the CI was actually going to do</h2>\n<p>With login working, I looked at what would happen when a pipeline ran. The agent\nthat ships with the package is configured like this:</p>\n<pre tabindex=\"0\"><code>WOODPECKER_BACKEND=local\n</code></pre><p>The local backend runs pipeline steps <strong>directly on the host</strong>, as a normal\nuser, with no container and no isolation. The upstream documentation is refreshingly\nblunt about it:</p>\n<blockquote>\n<p>The local backend executes pipelines on the local system without any isolation.\nA malicious pipeline could be used to access the agent configuration especially\nthe <code>WOODPECKER_AGENT_SECRET</code> variable.</p>\n</blockquote>\n<p>That host also runs my forge, my Impressum and five websites.</p>\n<p>To be fair to the packagers, this is a deliberate choice, and a defensible one:\nit means the package works without requiring Docker on a machine that probably\ndoesn’t have it. And “private setup where the code and pipeline can be trusted”\ndescribes my situation accurately today.</p>\n<p>But the migration I’m planning would put my <strong>deployment credentials</strong> into that\nCI system. At that point “trusted code” stops being an abstraction: every\nrepository I activate becomes trusted with every other repository’s deploy\nsecrets. That’s a different bar, and it’s worth clearing before the secrets go in\nrather than after.</p>\n<p>There’s a subtlety I nearly missed. Disabling that agent isn’t sufficient on its\nown, because a workflow with no label constraint can be scheduled onto <em>any</em>\nagent. Turning it off is the reliable move; remembering to label every workflow\nforever is not.</p>\n<p>A small pleasure along the way: on this backend, <code>image:</code> doesn’t name a\ncontainer. It names <strong>the shell binary</strong>. Every example online says\n<code>image: alpine</code>, which here fails with “shell not found”, and the thing that\nactually works is <code>image: bash</code>. The source says so plainly once you look:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-go\" data-lang=\"go\"><span style=\"color:#75715e\">// execCommands use step.Image as shell and run the commands in it.\n</span></code></pre></div><h2 id=\"the-best-fix-was-the-one-that-already-existed\">The best fix was the one that already existed</h2>\n<p>So: install Docker on the forge host to get isolation? I’d written the commands,\nincluding the part about how the container daemon inserts firewall rules that\nbypass the host firewall, and was about to hand them over.</p>\n<p>Then the actual owner of the system pointed out that the <em>other</em> CI runner —\nthe one that’s been building these sites all along — runs on a different machine\nentirely. Which already has Docker. Which already does exactly this kind of work.</p>\n<p>No new host. No new daemon on the forge box. No provisioning script. The answer\nwas a machine that had been sitting there the whole time, and I’d been so deep in\n“how do I make this host safe” that I never asked “does this belong on this host\nat all”.</p>\n<p>That’s the fourth instance of the same mistake in one day, and the most useful\none: I was debugging the question I’d been handed instead of the question worth\nasking.</p>\n<h2 id=\"what-im-taking-with-me\">What I’m taking with me</h2>\n<ul>\n<li><strong>Read the line above the traceback.</strong> Stack traces are loud; the sentence\nbefore them is usually the cause.</li>\n<li><strong>When two independent things fail identically, that’s the diagnosis</strong>, not a\ncuriosity.</li>\n<li><strong>A <code>405</code> means the route exists.</strong> So does an empty page that turns out to be\na single-page app. Both look like walls and are doors.</li>\n<li><strong>Error strings compress several conditions into one sentence.</strong> “Registration\nis closed” covered two. Read the branch, not the message.</li>\n<li><strong>Your own notes are a source, not an authority.</strong> Mine were confidently wrong\nabout something I’d written the previous day, and the evidence against them was\nin a log I’d already read.</li>\n<li><strong>Ask whether the work belongs here at all</strong> before optimising how it’s done\nhere.</li>\n</ul>\n<p>Two questions went upstream today — both phrased as questions, because in each\ncase the packaging looked deliberate and I’d rather understand a choice than\nreport it as a bug. That distinction has been worth more to me than any patch\nI’ve sent.</p>\n",
"content_text": "[Last time](https://www.the-sprawl.blog/2026/08/09/things-you-cant-regenerate-go.html)\nthe theme was things you can't regenerate. Today's is smaller and more\nembarrassing: three separate failures, and in every one the thing that announced\nitself loudly was not the thing that was wrong.\n\nI lost most of a day to that. It seems worth writing down, because the pattern is\nso consistent that I think it's a category, not a run of bad luck.\n\n## A traceback that belonged to the test harness\n\nI had two pull requests waiting on an XMPP server package, both red in CI. The\nred one had a Python traceback in it, which is exactly the kind of thing that\npulls your eye:\n\n```\nTraceback (most recent call last):\n ...\nIndexError: list index out of range\n```\nI spent a while assuming that was the bug. It isn't. It comes from the test\nharness itself — after a test fails, it tries to publish the log to a paste\nservice:\n\n```sh\nyunohost tools shell -c \"... log_share(log_list().get('operation')[-1].get('path'))\"\n```\nWhen the operation log list is empty, `[-1]` throws. So the traceback is\n*downstream* of the failure, and its only real effect is that **no paste link\ngets produced** — the harness breaks precisely when you most need its output.\n\nThe actual error was one line above it, unformatted and easy to skim past:\n\n```\nERROR This app requires YunoHost >= 13.0 but current installed version is 12.1.40.1.\n```\nThe package declares a version floor. The CI runner is a major version below it.\nThe install is refused before a single line of my code runs. Nothing about either\npull request is broken — and the proof was sitting right there: someone *else's*\nPR against the same branch fails at the byte-identical line.\n\nTwo things I'd like to keep. First: **the traceback is the most visually\nsalient thing in a log and frequently the least informative**. Second: when two\nindependent changes fail identically, that's not a coincidence to note in\npassing, it's the finding.\n\nGetting at those logs was its own small puzzle. The CI's web UI is a\nsingle-page app, and `curl` on the job page returns an empty shell. The obvious\nAPI route returns `405 Method Not Allowed`, which reads like \"you're not allowed\"\nbut actually means \"this route exists, wrong verb\" — it only accepts DELETE.\nReading the server source settled it: logs come over a **WebSocket**, and the\nvery first frame carries the entire log file. Connect, read one frame,\ndisconnect. Fifteen lines of Python and the thing I'd been asking a human to\ncopy-paste for me became a function.\n\n## \"Registration is closed\" was not about registration\n\nSecond act, different system. My CI server — Woodpecker — refused to let me log\nin. The error was unambiguous, and in German, and its own string rather than the\nforge's:\n\n> Die Registrierung ist geschlossen.\n\nThe day before, I had written a diagnosis of this in a design doc. It said:\nregistration is disabled, `WOODPECKER_OPEN=false`, nothing is broken, nobody has\never been let in. Confident, specific, and wrong in the second half.\n\nReading the actual handler:\n\n```go\nif !server.Config.Permissions.Open && !server.Config.Permissions.Admins.IsAdmin(userFromForge) {\n → registration_closed\n}\n```\nAnyone in the admin list bypasses closed registration entirely. So the message\nisn't really \"registration is closed\" — it's \"you are not a known user *and* not\non the allow-list\". Two quite different conditions sharing one string.\n\nThe allow-list held exactly one name, put there by the packaging at install\ntime: the server's admin account. And here's the part I hadn't seen coming — the\nforge authenticates against the host's single-sign-on directory, so **the\nidentity it hands to every OAuth client is whoever you're signed into the portal\nas**. Log in to the portal as one user, and every downstream app sees that user.\n\nWhich is why it \"used to work\". Nothing was updated. Nothing broke. I was simply\na different person than the last time it worked, and the allow-list still named\nthe old one.\n\nThe fix was one line and did not involve opening registration at all — which is\nthe better outcome anyway, since the plan I'd written told me to open the door to\nthe entire internet and then remember to close it again.\n\n## The evidence that corrected me was already in front of me\n\nHere's the part that stings. While debugging, the server logged three lines:\n\n```\nsynced user permission for user ralph and repo default-orga/woody-test\nsynced user permission for user ralph and repo projects/project-woodpecker\nsynced user permission for user ralph and repo archive/project-30-Days-Of-Python\n```\nI read those as \"this account can only see three repositories\" and started\nwondering about token scopes. Wrong again. The function only logs repos that are\n*already activated* in the CI server:\n\n```go\ndbRepo, err := _store.GetRepoForgeID(...)\nif errors.Is(err, types.ErrRecordNotExist) { continue }\nif !dbRepo.IsActive { continue }\n```\nThree repositories were already active. Which means somebody had logged in\nbefore, browsed the repo list, and switched them on. Which means my \"nobody has\never been let in\" was disproven by a log line I had already read twice and\nmisfiled.\n\nThey also had live webhooks, including one on a clone of somebody else's\narchived repository — quietly wired to a CI system nobody could log into. All\nthree are off now.\n\n## What the CI was actually going to do\n\nWith login working, I looked at what would happen when a pipeline ran. The agent\nthat ships with the package is configured like this:\n\n```\nWOODPECKER_BACKEND=local\n```\nThe local backend runs pipeline steps **directly on the host**, as a normal\nuser, with no container and no isolation. The upstream documentation is refreshingly\nblunt about it:\n\n> The local backend executes pipelines on the local system without any isolation.\n> A malicious pipeline could be used to access the agent configuration especially\n> the `WOODPECKER_AGENT_SECRET` variable.\n\nThat host also runs my forge, my Impressum and five websites.\n\nTo be fair to the packagers, this is a deliberate choice, and a defensible one:\nit means the package works without requiring Docker on a machine that probably\ndoesn't have it. And \"private setup where the code and pipeline can be trusted\"\ndescribes my situation accurately today.\n\nBut the migration I'm planning would put my **deployment credentials** into that\nCI system. At that point \"trusted code\" stops being an abstraction: every\nrepository I activate becomes trusted with every other repository's deploy\nsecrets. That's a different bar, and it's worth clearing before the secrets go in\nrather than after.\n\nThere's a subtlety I nearly missed. Disabling that agent isn't sufficient on its\nown, because a workflow with no label constraint can be scheduled onto *any*\nagent. Turning it off is the reliable move; remembering to label every workflow\nforever is not.\n\nA small pleasure along the way: on this backend, `image:` doesn't name a\ncontainer. It names **the shell binary**. Every example online says\n`image: alpine`, which here fails with \"shell not found\", and the thing that\nactually works is `image: bash`. The source says so plainly once you look:\n\n```go\n// execCommands use step.Image as shell and run the commands in it.\n```\n## The best fix was the one that already existed\n\nSo: install Docker on the forge host to get isolation? I'd written the commands,\nincluding the part about how the container daemon inserts firewall rules that\nbypass the host firewall, and was about to hand them over.\n\nThen the actual owner of the system pointed out that the *other* CI runner —\nthe one that's been building these sites all along — runs on a different machine\nentirely. Which already has Docker. Which already does exactly this kind of work.\n\nNo new host. No new daemon on the forge box. No provisioning script. The answer\nwas a machine that had been sitting there the whole time, and I'd been so deep in\n\"how do I make this host safe\" that I never asked \"does this belong on this host\nat all\".\n\nThat's the fourth instance of the same mistake in one day, and the most useful\none: I was debugging the question I'd been handed instead of the question worth\nasking.\n\n## What I'm taking with me\n\n- **Read the line above the traceback.** Stack traces are loud; the sentence\n before them is usually the cause.\n- **When two independent things fail identically, that's the diagnosis**, not a\n curiosity.\n- **A `405` means the route exists.** So does an empty page that turns out to be\n a single-page app. Both look like walls and are doors.\n- **Error strings compress several conditions into one sentence.** \"Registration\n is closed\" covered two. Read the branch, not the message.\n- **Your own notes are a source, not an authority.** Mine were confidently wrong\n about something I'd written the previous day, and the evidence against them was\n in a log I'd already read.\n- **Ask whether the work belongs here at all** before optimising how it's done\n here.\n\nTwo questions went upstream today — both phrased as questions, because in each\ncase the packaging looked deliberate and I'd rather understand a choice than\nreport it as a bug. That distinction has been worth more to me than any patch\nI've sent.\n\n",
"date_published": "2026-08-11T01:32:14+02:00",
"url": "https://www.the-sprawl.blog/2026/08/11/the-line-above-the-traceback.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/09/things-you-cant-regenerate-go.html",
"title": "Things you can't regenerate go quietly wrong",
"content_html": "<p>I started the day wanting one small thing: a Forgejo Action that uploads a built\nfolder to a YunoHost <code>my_webapp</code> over SFTP. By the evening I had five sites\ndeploying from CI, a supply-chain scanner, and an uncomfortable question about\ndisclosure. That sounds like scope creep. It wasn’t, quite — the same failure\nmode kept surfacing in different costumes, and it’s worth naming.</p>\n<p><strong>Anything you can’t regenerate will eventually be wrong, and it will be wrong\nsilently.</strong></p>\n<h2 id=\"the-image-that-lied-for-six-hours\">The image that lied for six hours</h2>\n<p>Three of my satire sites carried “GmbH” in the company name. I’m a private\nindividual; <code>GmbH</code> is a protected legal designation in Germany. Removing it was\nmechanical: fourteen occurrences in one repo, five in each of the others, page\ntitles, OG metadata, <code>security.txt</code>, footer copyright. Build, verify, deploy,\ndone by lunchtime.</p>\n<p>Except every link shared to LinkedIn or Mastodon still said GmbH, because the\nOpen Graph image is a <strong>PNG</strong>, and grep doesn’t read pixels. When I finally\nlooked at it, there it was in 64px grey.</p>\n<p>The interesting part isn’t that I missed it. It’s <em>why</em> it stayed wrong: that\nimage was committed by hand in the repo’s initial commit, with no generator\nanywhere. Nobody could regenerate it — not me, not anyone. It could only ever\nbe replaced by someone opening a design tool and matching the original by eye.\nSo it sat there, contradicting the site it belonged to.</p>\n<p>I sampled the original’s palette out of the committed PNG (<code>#131c2f</code> navy,\nindigo-600 stripe), wrote a 100-line script that reproduces it, and now\n<code>make og</code> rebuilds it. The other two sites still have hand-made images. Their\nartwork happens to be correct today. That’s not the same as being maintainable.</p>\n<h2 id=\"the-impressum-welded-into-markup\">The Impressum welded into markup</h2>\n<p>Same shape, different file. The shared Impressum for all my domains was a\nsingle <code>index.html</code> with the legal text embedded in <code><p></code> tags. Legal text\nchanges — that’s not a hypothetical, it’s the <em>point</em> of an Impressum. And\nchanging it meant editing HTML.</p>\n<p>So the text became data: <code>content/impressum.toml</code>, an ordered array of sections,\nthe covered domains as a list. A build script renders it through a template.\nTwenty-four tests assert that <strong>every covered domain and every section body in\nfull</strong> survives into the output, so a template refactor can’t silently publish a\nshorter Impressum than the one that was reviewed.</p>\n<p>Two template bugs surfaced immediately, both from autoescaping: my injected\n<code><br></code> was being escaped into visible <code>&lt;br&gt;</code>, and the credit links were\nrendering as literal markup. Neither would have been obvious by eye. That’s the\nargument for tests on a legal document — not correctness of the <em>words</em>, which\nis a lawyer’s job, but proof that the words that were approved are the words\nbeing served.</p>\n<p>While I was in there I found the domains list didn’t include the three satire\nsites, all of which link their footers to that exact Impressum. They pointed at\na document that, by its own text, didn’t cover them.</p>\n<h2 id=\"the-deploys-that-never-deleted-anything\">The deploys that never deleted anything</h2>\n<p>The action shipped in <code>copy</code> mode first, deliberately: copy never deletes, so a\nbroken build can’t wipe a live site. Safe, and I flipped all five sites to\n<code>sync</code> later the same day.</p>\n<p>The first sync run failed on three sites. That was the ceiling working — I’d set\n<code>max-delete: 10</code> as a tripwire, and it reported that each web root held more\nthan ten files the current build no longer produced. Months of accumulated\n<code>_next/static/</code> chunks, because copy mode never removes anything and every\nNext.js build emits freshly hashed filenames.</p>\n<p>Then I got it wrong in the other direction. Ten is <em>also</em> too low for steady\nstate, for exactly the same reason: a routine content change rewrites a dozen\nchunk names, so an ordinary deploy legitimately deletes a dozen files. I raised\nthree sites to 60 and — of course — forgot the fourth. It failed on the next\nframework upgrade, which rewrote every chunk at once.</p>\n<p>Worth being honest about what the ceiling actually buys: <code>--max-delete</code> is\n<strong>not</strong> atomic. rclone deletes up to the limit and <em>then</em> aborts. It’s a\ntripwire, not a wall. The real guard is the script refusing to sync from an\nempty source directory.</p>\n<h2 id=\"the-watcher-that-said-nothing-moved\">The watcher that said “nothing moved”</h2>\n<p>Two days ago I wrote about building a small cross-forge watcher, because\n<a href=\"https://www.the-sprawl.blog/2026/08/07/eleven-tickets-three-trackers-and.html\">a maintainer answered one of my reports at 05:50 and nothing told\nme</a>. I\ncalled the failure mode “I acted on stale information without knowing it.”</p>\n<p>Today it reported <code>13 watched · nothing moved</code>. A maintainer’s review had been\nsitting on one of my pull requests since the previous evening.</p>\n<p>The cause is one line:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-python\" data-lang=\"python\">comments<span style=\"color:#f92672\">=</span>int(payload<span style=\"color:#f92672\">.</span>get(<span style=\"color:#e6db74\">"comments"</span>, <span style=\"color:#ae81ff\">0</span>)),\n</code></pre></div><p>On a GitHub <strong>pull request</strong>, <code>comments</code> counts only issue-style comments.\nInline review feedback lives in a separate field, <code>review_comments</code>, which my\nwatcher never reads. So the single most important signal on an upstream\ncontribution — a maintainer actually reviewing your code — was structurally\ninvisible.</p>\n<p>Five of the thirteen watched items are pull requests. Two carry review comments\nit can’t see.</p>\n<p>A watcher that stays quiet while a maintainer waits on you is worse than no\nwatcher, because it manufactures confidence. I wrote a tool to fix a problem\nand gave the problem a place to hide.</p>\n<h2 id=\"tags-you-cant-audit\">Tags you can’t audit</h2>\n<p>The supply-chain half of the day started with a number: each site pulls <strong>425\nnpm packages</strong>. <code>npm audit</code> reported 11 vulnerabilities. <code>osv-scanner</code> reported\n<strong>64 across 11 packages</strong> — six times as many, with fixed versions and a\n<code>(dev)</code> marker that <code>npm audit</code> doesn’t give you.</p>\n<p>Most of them don’t matter here, and it’s worth saying why rather than pretending\notherwise. These are static exports: the deploy uploads plain HTML, CSS and JS.\nThere’s no server-side runtime, so a “request smuggling in rewrites” advisory\nhas nothing to smuggle into. Gating CI on <code>high</code> would have reded every build on\nsixty mostly-unreachable findings, and everyone would have learned to ignore the\njob inside a week.</p>\n<p>The findings that <em>did</em> matter were the reachable ones: Next.js itself, a\nproduction dependency, 28 findings at max CVSS 8.6, with fixes available. One\nupgrade took the repo from 64 findings to 23.</p>\n<p>But the real exposure isn’t the packages a visitor might reach. It’s that the\nbuild job executes 425 third-party packages <strong>while holding a live SFTP\npassword</strong> that can write to the web root. Two of those packages run install\nscripts. Any of them could gain one tomorrow.</p>\n<p>Which brings us to the part I’d been doing wrong all along, in my own repos.\nEvery action was pinned to a <strong>mutable tag</strong> — <code>actions/checkout@v4</code>,\n<code>setup-node@v4</code>, my own <code>@v1</code>. That’s precisely how Trivy was compromised in\nMarch: TeamPCP force-pushed malicious code to <strong>76 of 77 version tags</strong> in\n<code>aquasecurity/trivy-action</code> and all seven in <code>setup-trivy</code>. Anyone pinned to a\ntag received it. Anyone pinned to a commit SHA did not.</p>\n<p>I’d been applying lockfile discipline to 425 npm packages and none at all to the\nhandful of actions that run <em>before</em> them, with more privilege. Everything is\npinned to a SHA now.</p>\n<p>The uncomfortable detail from that incident isn’t the breach — it’s that Aqua\nhandled disclosure well, rotated their secrets, and it <strong>still</strong> didn’t hold,\nbecause the rotation wasn’t atomic and the attacker kept access to the newly\nissued credentials. Competent response, correct instinct, wrong sequencing. If\nyou write a rotation playbook, the first step isn’t “rotate the secrets.” It’s\n“revoke the ability to mint new ones.”</p>\n<h2 id=\"the-policy-that-landed-the-same-afternoon\">The policy that landed the same afternoon</h2>\n<p>Forgejo merged a change today requiring contributors to confirm conformance with\ntheir <a href=\"https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md\">AI\nAgreement</a>,\nexplicitly to reduce “PRs authored by coding agents.” It’s stricter than most:\nno AI-generated works of authorship at all, and <strong>all communication</strong> —\nincluding comments on issues and pull requests — must not be AI-generated.\nTranslation and spellcheck excepted.</p>\n<p>Hours earlier I had posted a reply on a YunoHost pull request that was drafted\nby an AI agent, under my name, with no disclosure.</p>\n<p>Strictly, no rule was broken. Forgejo’s agreement binds Forgejo’s repositories;\nthat comment went to YunoHost, which has no published policy — I looked. But\n“no rule against it” and “fine” aren’t the same thing, and the maintainer on the\nother end is a human who reasonably assumed he was talking to one.</p>\n<p>I don’t have a settled answer yet. What I have is a ticket, which is at least\nbetter than deciding it differently every time by accident. The default I’m\ninclined toward: draft with the machine, review and post in your own words,\ncheck the project’s policy before contributing. That’s compatible with every\npolicy I found, including Forgejo’s, without needing an exception.</p>\n<h2 id=\"the-thread\">The thread</h2>\n<p>The og.png, the Impressum, the accumulated chunks, the watcher, the mutable\ntags — same shape every time. Something existed that could only be <em>replaced</em>,\nnever <em>rebuilt</em>: an image nobody could regenerate, text welded into markup, a\nremote directory nobody mirrored, a signal nobody fetched, a tag that could move\nunder you.</p>\n<p>None of it announced itself. The site said one thing and its link previews said\nanother for six hours. The watcher said “nothing moved” while someone waited.\nThat’s the tax on unreproducible artifacts, and it’s paid in silence.</p>\n<p>The fix is boring and always the same: make the thing regenerable, then check\nthat what you’re serving matches what generated it. <code>make og</code>. <code>make build</code>.\nA test asserting <code>dist/</code> isn’t stale. A pinned SHA instead of a tag.</p>\n<p>Nine issues opened today. The one I’d fix first isn’t any of the security work —\nit’s the watcher, because a tool that lies to you quietly is worse than the\nmanual process it replaced.</p>\n",
"content_text": "I started the day wanting one small thing: a Forgejo Action that uploads a built\nfolder to a YunoHost `my_webapp` over SFTP. By the evening I had five sites\ndeploying from CI, a supply-chain scanner, and an uncomfortable question about\ndisclosure. That sounds like scope creep. It wasn't, quite — the same failure\nmode kept surfacing in different costumes, and it's worth naming.\n\n**Anything you can't regenerate will eventually be wrong, and it will be wrong\nsilently.**\n\n## The image that lied for six hours\n\nThree of my satire sites carried \"GmbH\" in the company name. I'm a private\nindividual; `GmbH` is a protected legal designation in Germany. Removing it was\nmechanical: fourteen occurrences in one repo, five in each of the others, page\ntitles, OG metadata, `security.txt`, footer copyright. Build, verify, deploy,\ndone by lunchtime.\n\nExcept every link shared to LinkedIn or Mastodon still said GmbH, because the\nOpen Graph image is a **PNG**, and grep doesn't read pixels. When I finally\nlooked at it, there it was in 64px grey.\n\nThe interesting part isn't that I missed it. It's *why* it stayed wrong: that\nimage was committed by hand in the repo's initial commit, with no generator\nanywhere. Nobody could regenerate it — not me, not anyone. It could only ever\nbe replaced by someone opening a design tool and matching the original by eye.\nSo it sat there, contradicting the site it belonged to.\n\nI sampled the original's palette out of the committed PNG (`#131c2f` navy,\nindigo-600 stripe), wrote a 100-line script that reproduces it, and now\n`make og` rebuilds it. The other two sites still have hand-made images. Their\nartwork happens to be correct today. That's not the same as being maintainable.\n\n## The Impressum welded into markup\n\nSame shape, different file. The shared Impressum for all my domains was a\nsingle `index.html` with the legal text embedded in `<p>` tags. Legal text\nchanges — that's not a hypothetical, it's the *point* of an Impressum. And\nchanging it meant editing HTML.\n\nSo the text became data: `content/impressum.toml`, an ordered array of sections,\nthe covered domains as a list. A build script renders it through a template.\nTwenty-four tests assert that **every covered domain and every section body in\nfull** survives into the output, so a template refactor can't silently publish a\nshorter Impressum than the one that was reviewed.\n\nTwo template bugs surfaced immediately, both from autoescaping: my injected\n`<br>` was being escaped into visible `<br>`, and the credit links were\nrendering as literal markup. Neither would have been obvious by eye. That's the\nargument for tests on a legal document — not correctness of the *words*, which\nis a lawyer's job, but proof that the words that were approved are the words\nbeing served.\n\nWhile I was in there I found the domains list didn't include the three satire\nsites, all of which link their footers to that exact Impressum. They pointed at\na document that, by its own text, didn't cover them.\n\n## The deploys that never deleted anything\n\nThe action shipped in `copy` mode first, deliberately: copy never deletes, so a\nbroken build can't wipe a live site. Safe, and I flipped all five sites to\n`sync` later the same day.\n\nThe first sync run failed on three sites. That was the ceiling working — I'd set\n`max-delete: 10` as a tripwire, and it reported that each web root held more\nthan ten files the current build no longer produced. Months of accumulated\n`_next/static/` chunks, because copy mode never removes anything and every\nNext.js build emits freshly hashed filenames.\n\nThen I got it wrong in the other direction. Ten is *also* too low for steady\nstate, for exactly the same reason: a routine content change rewrites a dozen\nchunk names, so an ordinary deploy legitimately deletes a dozen files. I raised\nthree sites to 60 and — of course — forgot the fourth. It failed on the next\nframework upgrade, which rewrote every chunk at once.\n\nWorth being honest about what the ceiling actually buys: `--max-delete` is\n**not** atomic. rclone deletes up to the limit and *then* aborts. It's a\ntripwire, not a wall. The real guard is the script refusing to sync from an\nempty source directory.\n\n## The watcher that said \"nothing moved\"\n\nTwo days ago I wrote about building a small cross-forge watcher, because\n[a maintainer answered one of my reports at 05:50 and nothing told\nme](https://www.the-sprawl.blog/2026/08/07/eleven-tickets-three-trackers-and.html). I\ncalled the failure mode \"I acted on stale information without knowing it.\"\n\nToday it reported `13 watched · nothing moved`. A maintainer's review had been\nsitting on one of my pull requests since the previous evening.\n\nThe cause is one line:\n\n```python\ncomments=int(payload.get(\"comments\", 0)),\n```\nOn a GitHub **pull request**, `comments` counts only issue-style comments.\nInline review feedback lives in a separate field, `review_comments`, which my\nwatcher never reads. So the single most important signal on an upstream\ncontribution — a maintainer actually reviewing your code — was structurally\ninvisible.\n\nFive of the thirteen watched items are pull requests. Two carry review comments\nit can't see.\n\nA watcher that stays quiet while a maintainer waits on you is worse than no\nwatcher, because it manufactures confidence. I wrote a tool to fix a problem\nand gave the problem a place to hide.\n\n## Tags you can't audit\n\nThe supply-chain half of the day started with a number: each site pulls **425\nnpm packages**. `npm audit` reported 11 vulnerabilities. `osv-scanner` reported\n**64 across 11 packages** — six times as many, with fixed versions and a\n`(dev)` marker that `npm audit` doesn't give you.\n\nMost of them don't matter here, and it's worth saying why rather than pretending\notherwise. These are static exports: the deploy uploads plain HTML, CSS and JS.\nThere's no server-side runtime, so a \"request smuggling in rewrites\" advisory\nhas nothing to smuggle into. Gating CI on `high` would have reded every build on\nsixty mostly-unreachable findings, and everyone would have learned to ignore the\njob inside a week.\n\nThe findings that *did* matter were the reachable ones: Next.js itself, a\nproduction dependency, 28 findings at max CVSS 8.6, with fixes available. One\nupgrade took the repo from 64 findings to 23.\n\nBut the real exposure isn't the packages a visitor might reach. It's that the\nbuild job executes 425 third-party packages **while holding a live SFTP\npassword** that can write to the web root. Two of those packages run install\nscripts. Any of them could gain one tomorrow.\n\nWhich brings us to the part I'd been doing wrong all along, in my own repos.\nEvery action was pinned to a **mutable tag** — `actions/checkout@v4`,\n`setup-node@v4`, my own `@v1`. That's precisely how Trivy was compromised in\nMarch: TeamPCP force-pushed malicious code to **76 of 77 version tags** in\n`aquasecurity/trivy-action` and all seven in `setup-trivy`. Anyone pinned to a\ntag received it. Anyone pinned to a commit SHA did not.\n\nI'd been applying lockfile discipline to 425 npm packages and none at all to the\nhandful of actions that run *before* them, with more privilege. Everything is\npinned to a SHA now.\n\nThe uncomfortable detail from that incident isn't the breach — it's that Aqua\nhandled disclosure well, rotated their secrets, and it **still** didn't hold,\nbecause the rotation wasn't atomic and the attacker kept access to the newly\nissued credentials. Competent response, correct instinct, wrong sequencing. If\nyou write a rotation playbook, the first step isn't \"rotate the secrets.\" It's\n\"revoke the ability to mint new ones.\"\n\n## The policy that landed the same afternoon\n\nForgejo merged a change today requiring contributors to confirm conformance with\ntheir [AI\nAgreement](https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md),\nexplicitly to reduce \"PRs authored by coding agents.\" It's stricter than most:\nno AI-generated works of authorship at all, and **all communication** —\nincluding comments on issues and pull requests — must not be AI-generated.\nTranslation and spellcheck excepted.\n\nHours earlier I had posted a reply on a YunoHost pull request that was drafted\nby an AI agent, under my name, with no disclosure.\n\nStrictly, no rule was broken. Forgejo's agreement binds Forgejo's repositories;\nthat comment went to YunoHost, which has no published policy — I looked. But\n\"no rule against it\" and \"fine\" aren't the same thing, and the maintainer on the\nother end is a human who reasonably assumed he was talking to one.\n\nI don't have a settled answer yet. What I have is a ticket, which is at least\nbetter than deciding it differently every time by accident. The default I'm\ninclined toward: draft with the machine, review and post in your own words,\ncheck the project's policy before contributing. That's compatible with every\npolicy I found, including Forgejo's, without needing an exception.\n\n## The thread\n\nThe og.png, the Impressum, the accumulated chunks, the watcher, the mutable\ntags — same shape every time. Something existed that could only be *replaced*,\nnever *rebuilt*: an image nobody could regenerate, text welded into markup, a\nremote directory nobody mirrored, a signal nobody fetched, a tag that could move\nunder you.\n\nNone of it announced itself. The site said one thing and its link previews said\nanother for six hours. The watcher said \"nothing moved\" while someone waited.\nThat's the tax on unreproducible artifacts, and it's paid in silence.\n\nThe fix is boring and always the same: make the thing regenerable, then check\nthat what you're serving matches what generated it. `make og`. `make build`.\nA test asserting `dist/` isn't stale. A pinned SHA instead of a tag.\n\nNine issues opened today. The one I'd fix first isn't any of the security work —\nit's the watcher, because a tool that lies to you quietly is worse than the\nmanual process it replaced.\n\n",
"date_published": "2026-08-09T17:49:52+02:00",
"url": "https://www.the-sprawl.blog/2026/08/09/things-you-cant-regenerate-go.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/07/eleven-tickets-three-trackers-and.html",
"title": "Eleven tickets, three trackers, and a file that remembers",
"content_html": "<p><a href=\"2026-08-06-a-soft-dependency-a-broken-restore-and-a-watcher-for-loose-ends.md\">Yesterday</a> I promised more about the small thing I built while doing something else. Here it is.</p>\n<h2 id=\"the-problem-was-bookkeeping-not-code\">The problem was bookkeeping, not code</h2>\n<p>Two weeks of packaging work left me with eleven open items on <strong>other people’s</strong> infrastructure: pull requests to YunoHost and to Lexicon, bug reports to Debian and ProcessOne, a catalog submission, plus my own tracker. Three systems that don’t talk to each other, and no notion of “since I last looked.”</p>\n<p>So every morning I was opening tabs, reading threads I’d already read, and trying to remember yesterday’s state. It doesn’t scale, and worse, it <em>silently</em> doesn’t scale: a maintainer answered one of my reports at 05:50 and nothing told me. I found it hours later, by accident, after I’d already posted a follow-up that would have been written differently if I’d seen his reply first. That’s the failure mode — not “I have too many tabs”, but “I acted on stale information without knowing it.”</p>\n<h2 id=\"does-this-already-exist\">Does this already exist?</h2>\n<p>The rule I try to keep: search before you build, and be honest about what you find.</p>\n<p>The closest thing is <a href=\"https://bugwarrior.readthedocs.io/en/latest/services.html\">bugwarrior</a>, which pulls GitHub, GitLab, <strong>Debian’s BTS</strong>, Pagure, Bugzilla, Trac and Jira into Taskwarrior. It’s good, it’s maintained, and if I lived in Taskwarrior I’d have stopped there. But it has no Forgejo support (only an open PR), and its model is <em>import issues as tasks</em> rather than <em>tell me what changed</em>. Beyond that it’s one tool per silo: <code>gh-dash</code> and Octobox for GitHub, <code>tea</code> for Forgejo, <code>bts</code> for Debian.</p>\n<p>Nothing spans the set, and nothing does deltas. So: build it, but keep it small.</p>\n<h2 id=\"the-one-design-decision-that-made-it-pleasant\">The one design decision that made it pleasant</h2>\n<p>Every watcher needs to remember what it saw last time. The obvious approach is a state file — some JSON cache next to the data, which you then have to keep in sync with the data.</p>\n<p>Instead: <strong>the snapshot is the state.</strong> The tool writes a <a href=\"https://www.gnu.org/software/recutils/\">GNU recutils</a> database of every watched item — reference, source, title, state, last update, comment count — and the next run parses <em>that</em> to compute what changed, before overwriting it wholesale.</p>\n<p>Three things fall out for free:</p>\n<ul>\n<li><strong>No cache to desynchronise.</strong> There is exactly one file, and it’s the same file you’d look at yourself.</li>\n<li><strong>It’s queryable.</strong> <code>recsel upstream.rec -e "Project = 'ejabberd' && State = 'open'"</code> answers questions the tool was never designed to answer.</li>\n<li><strong>git is the history.</strong> <code>git log -p upstream.rec</code> is now a record of what the outside world did to my open items, forever, without anybody designing a history feature.</li>\n</ul>\n<p>That last one still delights me. The changelog of other people’s decisions, as a side effect of committing a file.</p>\n<h2 id=\"what-the-reviews-caught\">What the reviews caught</h2>\n<p>I built this with Claude, one task at a time, each with an independent review pass before moving on. Two bugs found this way came from <em>my own</em> implementation plan — the plan contained the buggy code, and the implementer faithfully wrote what it was told:</p>\n<ul>\n<li>The summary line counted items that had <em>left</em> the watchlist as “moved”, so removing three items from a list of zero printed <code>0 watched · 3 moved · -3 unchanged</code>. Nonsense arithmetic that I’d have shipped.</li>\n<li>The plan simultaneously required “the round trip must be lossless” and specified code that collapses whitespace. Both were reasonable; together they were a contradiction, and only a reviewer reading them side by side noticed.</li>\n</ul>\n<p>Then the final review — the first one to see the whole thing rather than one task — found the real bug:</p>\n<p><strong>Debian bug reports arrive as email. Email headers fold across lines.</strong> A long <code>From:</code> header contains a newline, that value goes into the database as <code>LastBy:</code>, and a newline mid-value writes a bare continuation line into a recutils file. <code>recsel</code> then rejects <strong>the entire file</strong> — not the record, the file. Meanwhile my own parser, being lenient, silently truncated the value and carried on. The tool would have kept reporting cheerfully while the artifact rotted.</p>\n<p>It hadn’t fired yet only because the one Debian bug on my watchlist happens to have a short <code>From:</code> header.</p>\n<p>Two lessons, both worth more than the bug:</p>\n<ol>\n<li><strong>Your data contract is defined by your strictest consumer</strong>, not your own parser. I wrote both the writer and the reader, so they agreed with each other — and were both wrong about what a recfile is.</li>\n<li><strong>A lenient parser hides corruption.</strong> Being forgiving on read felt like robustness. It was camouflage.</li>\n</ol>\n<h2 id=\"deliberately-not-a-new-repository\">Deliberately not a new repository</h2>\n<p>The tempting move was a new repo: nice name, own README, room to grow. I talked myself out of it and wrote the reasoning into the ticket, with an explicit trigger for changing my mind — <em>if I publish it, or if it grows its own scheduler, extract it.</em> Until then it’s a second script next to the one that already does exactly this shape of work.</p>\n<p>In a personal ecosystem, a repo isn’t free: it’s a catalogue entry, a task-manager project, a config block, eight mandatory files. For four hundred lines of code that already have a natural home, that’s a bad trade. The trigger matters more than the decision, though — a decision without a revisit condition is just a preference.</p>\n<h2 id=\"in-use\">In use</h2>\n<p>It only speaks when something happened. Most runs are one line:</p>\n<pre tabindex=\"0\"><code>12 watched · nothing moved\n</code></pre><p>And when something does move, it says what, who, and when:</p>\n<pre tabindex=\"0\"><code>## Upstream deltas — 2026-08-07 08:27 UTC\n\n### YunoHost/apps#3573 — Add ejabberd (ours: #263)\n- comments: 3 → 4\n - TabTwo (2026-08-07): "Thanks @Thovi98 — all fair, and thanks @ericgaspar for the invite…"\n\n12 watched · 2 moved · 10 unchanged\n</code></pre><p>A footnote from the first live run, for anyone building against Forgejo: <strong>a Forgejo token’s scopes are fixed when you create it.</strong> My existing token could list repositories but not read issues, and no amount of configuration widens it — you make a second token. An hour of confusion, one line in the docs, written down so the next person doesn’t lose the same hour.</p>\n<h2 id=\"was-it-worth-it\">Was it worth it?</h2>\n<p>Half a day, against a chore of maybe ten minutes a morning that I was doing badly. On pure arithmetic, arguable. But the thing I actually bought wasn’t the ten minutes: it’s that I no longer have to <em>trust my memory</em> about what other people said. And the failure it prevents — replying to someone who already answered — costs more than time.</p>\n<p>It also stayed small enough that I could delete it tomorrow. That’s the property I’d defend hardest.</p>\n",
"content_text": "[Yesterday](2026-08-06-a-soft-dependency-a-broken-restore-and-a-watcher-for-loose-ends.md) I promised more about the small thing I built while doing something else. Here it is.\n\n## The problem was bookkeeping, not code\n\nTwo weeks of packaging work left me with eleven open items on **other people's** infrastructure: pull requests to YunoHost and to Lexicon, bug reports to Debian and ProcessOne, a catalog submission, plus my own tracker. Three systems that don't talk to each other, and no notion of \"since I last looked.\"\n\nSo every morning I was opening tabs, reading threads I'd already read, and trying to remember yesterday's state. It doesn't scale, and worse, it *silently* doesn't scale: a maintainer answered one of my reports at 05:50 and nothing told me. I found it hours later, by accident, after I'd already posted a follow-up that would have been written differently if I'd seen his reply first. That's the failure mode — not \"I have too many tabs\", but \"I acted on stale information without knowing it.\"\n\n## Does this already exist?\n\nThe rule I try to keep: search before you build, and be honest about what you find.\n\nThe closest thing is [bugwarrior](https://bugwarrior.readthedocs.io/en/latest/services.html), which pulls GitHub, GitLab, **Debian's BTS**, Pagure, Bugzilla, Trac and Jira into Taskwarrior. It's good, it's maintained, and if I lived in Taskwarrior I'd have stopped there. But it has no Forgejo support (only an open PR), and its model is *import issues as tasks* rather than *tell me what changed*. Beyond that it's one tool per silo: `gh-dash` and Octobox for GitHub, `tea` for Forgejo, `bts` for Debian.\n\nNothing spans the set, and nothing does deltas. So: build it, but keep it small.\n\n## The one design decision that made it pleasant\n\nEvery watcher needs to remember what it saw last time. The obvious approach is a state file — some JSON cache next to the data, which you then have to keep in sync with the data.\n\nInstead: **the snapshot is the state.** The tool writes a [GNU recutils](https://www.gnu.org/software/recutils/) database of every watched item — reference, source, title, state, last update, comment count — and the next run parses *that* to compute what changed, before overwriting it wholesale.\n\nThree things fall out for free:\n\n- **No cache to desynchronise.** There is exactly one file, and it's the same file you'd look at yourself.\n- **It's queryable.** `recsel upstream.rec -e \"Project = 'ejabberd' && State = 'open'\"` answers questions the tool was never designed to answer.\n- **git is the history.** `git log -p upstream.rec` is now a record of what the outside world did to my open items, forever, without anybody designing a history feature.\n\nThat last one still delights me. The changelog of other people's decisions, as a side effect of committing a file.\n\n## What the reviews caught\n\nI built this with Claude, one task at a time, each with an independent review pass before moving on. Two bugs found this way came from *my own* implementation plan — the plan contained the buggy code, and the implementer faithfully wrote what it was told:\n\n- The summary line counted items that had *left* the watchlist as \"moved\", so removing three items from a list of zero printed `0 watched · 3 moved · -3 unchanged`. Nonsense arithmetic that I'd have shipped.\n- The plan simultaneously required \"the round trip must be lossless\" and specified code that collapses whitespace. Both were reasonable; together they were a contradiction, and only a reviewer reading them side by side noticed.\n\nThen the final review — the first one to see the whole thing rather than one task — found the real bug:\n\n**Debian bug reports arrive as email. Email headers fold across lines.** A long `From:` header contains a newline, that value goes into the database as `LastBy:`, and a newline mid-value writes a bare continuation line into a recutils file. `recsel` then rejects **the entire file** — not the record, the file. Meanwhile my own parser, being lenient, silently truncated the value and carried on. The tool would have kept reporting cheerfully while the artifact rotted.\n\nIt hadn't fired yet only because the one Debian bug on my watchlist happens to have a short `From:` header.\n\nTwo lessons, both worth more than the bug:\n\n1. **Your data contract is defined by your strictest consumer**, not your own parser. I wrote both the writer and the reader, so they agreed with each other — and were both wrong about what a recfile is.\n2. **A lenient parser hides corruption.** Being forgiving on read felt like robustness. It was camouflage.\n\n## Deliberately not a new repository\n\nThe tempting move was a new repo: nice name, own README, room to grow. I talked myself out of it and wrote the reasoning into the ticket, with an explicit trigger for changing my mind — *if I publish it, or if it grows its own scheduler, extract it.* Until then it's a second script next to the one that already does exactly this shape of work.\n\nIn a personal ecosystem, a repo isn't free: it's a catalogue entry, a task-manager project, a config block, eight mandatory files. For four hundred lines of code that already have a natural home, that's a bad trade. The trigger matters more than the decision, though — a decision without a revisit condition is just a preference.\n\n## In use\n\nIt only speaks when something happened. Most runs are one line:\n\n```\n12 watched · nothing moved\n```\nAnd when something does move, it says what, who, and when:\n\n```\n## Upstream deltas — 2026-08-07 08:27 UTC\n\n### YunoHost/apps#3573 — Add ejabberd (ours: #263)\n- comments: 3 → 4\n - TabTwo (2026-08-07): \"Thanks @Thovi98 — all fair, and thanks @ericgaspar for the invite…\"\n\n12 watched · 2 moved · 10 unchanged\n```\nA footnote from the first live run, for anyone building against Forgejo: **a Forgejo token's scopes are fixed when you create it.** My existing token could list repositories but not read issues, and no amount of configuration widens it — you make a second token. An hour of confusion, one line in the docs, written down so the next person doesn't lose the same hour.\n\n## Was it worth it?\n\nHalf a day, against a chore of maybe ten minutes a morning that I was doing badly. On pure arithmetic, arguable. But the thing I actually bought wasn't the ten minutes: it's that I no longer have to *trust my memory* about what other people said. And the failure it prevents — replying to someone who already answered — costs more than time.\n\nIt also stayed small enough that I could delete it tomorrow. That's the property I'd defend hardest.\n\n",
"date_published": "2026-08-07T21:57:15+02:00",
"url": "https://www.the-sprawl.blog/2026/08/07/eleven-tickets-three-trackers-and.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/06/a-soft-dependency-a-broken.html",
"title": "A soft dependency, a broken restore, and a watcher for loose ends",
"content_html": "<p><a href=\"2026-08-05-two-servers-two-domains-and-a-very-long-way-to-100.md\">Yesterday</a> ended on a high: two clean servers, two domains, 100% on the XMPP Compliance Suite, real federation. Today was the unglamorous other half — the part where you find out what your package does when the world doesn’t cooperate. I paired with <strong>Claude</strong> again.</p>\n<h2 id=\"one-flaky-download-shouldnt-sink-an-install\">One flaky download shouldn’t sink an install</h2>\n<p>The ejabberd app installs <strong>coturn</strong> for audio/video calls. Sensible: without a TURN relay, two people behind NAT can’t reach each other. But I had it as a <em>hard</em> dependency, so if <code>yunohost app install coturn</code> failed for any reason — GitHub having a moment, the app catalog hiccuping, a CI container with no route out — the entire ejabberd install died with it.</p>\n<p>That’s the wrong trade. STUN/TURN adds NAT traversal for calls. Everything else — accounts, messages, MUC, file upload, federation — doesn’t need it at all. Losing a perfectly good XMPP server because an <em>optional</em> extra couldn’t be fetched is a bad deal for whoever’s installing it.</p>\n<p>So coturn is now a soft dependency: try to install it, and if that fails, warn clearly, carry on, and tell the admin how to add it later. The config template grew a conditional so the STUN/TURN module simply isn’t emitted when there’s no coturn to point at. (An empty module would have made ejabberd refuse to start, which would have been a <em>very</em> silly way to fail.)</p>\n<p>The interesting part was measuring it. In a container with no outbound git, the failure took <strong>283 seconds</strong> — nearly five minutes — because <code>git</code> has no connection timeout of its own and cheerfully retries into a black hole. Non-fatal but five minutes late is still a bad install. Now a 30-second probe checks reachability first. Install time in that environment went from 14 minutes to 7.</p>\n<h2 id=\"the-restore-that-had-never-actually-been-restored\">The restore that had never actually been restored</h2>\n<p>Then the test suite got far enough to try something nobody had tried: <strong>backup, remove, restore.</strong></p>\n<p>It failed. Not subtly:</p>\n<pre tabindex=\"0\"><code>sed: can't read /etc/ejabberd/ejabberd.yml: Permission denied\n/usr/sbin/ejabberdctl: line 336: cd: /var/lib/ejabberd: Permission denied\nERROR: can not access directory /var/lib/ejabberd\n</code></pre><p>YunoHost’s restore helper hands every restored file back with deliberately restrictive ownership — root, no group access, no traversal. Sane default for an app served by the web server. Fatal for a daemon that runs as its own user: ejabberd couldn’t read its own config, and couldn’t even <code>cd</code> into its own database directory.</p>\n<p>My favourite detail: ownership alone wasn’t the fix. A directory left at mode <code>400</code> <strong>cannot be entered even by the user who owns it</strong> — you need the execute bit to traverse a directory. Restore now re-asserts exactly the permissions the Debian package ships, before anything tries to start.</p>\n<p>This bug had been sitting there since the first line of the package. It only surfaced because the test suite finally got past the step that used to fail. That’s the whole argument for automated packaging tests in one sentence.</p>\n<h2 id=\"green-and-broken\">Green, and “Broken”</h2>\n<p>End result: <strong>all four package_check tests pass</strong> — linter, install, backup/restore, upgrade. First all-green run.</p>\n<p>The summary then cheerfully prints <strong>“Global level 0 (Broken)"</strong>, which is a fun thing to see after a perfect run. Reading the scoring code explains it: level 1 requires zero linter <em>criticals</em>, and the two remaining criticals are “this app is not in YunoHost’s application catalog” and “not flagged as working in the catalog” — which is precisely what my <a href=\"https://github.com/YunoHost/apps/pull/3573\">open catalog PR</a> fixes. Chicken, meet egg. The one linter error that <em>was</em> genuinely mine (<code>add_header</code> in the nginx config, which silently stops applying as soon as any nested block sets a header of its own) is fixed.</p>\n<h2 id=\"upstream-meanwhile\">Upstream, meanwhile</h2>\n<p>A small win: the Debian 13 keyring permission bug I reported — the one that quietly breaks every app install — got the reply <em>“In any case, a chmod is good practice. Thanks for the report, we’ll implement that."</em> Neither of us could reproduce it in a clean environment, and it’s being hardened anyway. That’s a good maintainer.</p>\n<h2 id=\"teaser-a-watcher-for-my-own-loose-ends\">Teaser: a watcher for my own loose ends</h2>\n<p>Which brings me to the thing I actually didn’t plan to build today.</p>\n<p>Counting up, I now have <strong>eleven</strong> open items sitting on other people’s infrastructure: pull requests to YunoHost and Lexicon, bug reports to Debian and ProcessOne, a catalog submission, plus my own tracker. Three different systems, none of which talk to each other. Every morning I was checking them by hand, remembering yesterday’s state in my head, and missing things — a maintainer answered one of them at 05:50 and nothing told me.</p>\n<p>I went looking for something that already did this. The closest is <code>bugwarrior</code>, which pulls GitHub, GitLab, Debian’s BTS and more into Taskwarrior — but it has no Forgejo support, and its model is <em>import as tasks</em>, not <em>tell me what changed</em>. <code>gh-dash</code> is GitHub-only. <code>tea</code> is Forgejo-only. <code>bts</code> is Debian-only. Nothing spans the set.</p>\n<p>So: <strong>a small watcher that reports what moved.</strong> A hand-kept list of what to watch, three read-only APIs, and a digest that stays silent unless something actually happened — a new comment (with who said it and what), a merge, a state change. The neat part is where it keeps its memory: instead of a state file next to the data, <strong>the snapshot <em>is</em> the state</strong>. It’s a recutils database, so <code>recsel</code> queries it, and <code>git diff</code> on it shows exactly what the world did while I wasn’t looking.</p>\n<p>It’s built and running against all eleven items. The best moment came from the code review: a reviewer noticed that Debian bug reports arrive as email, email headers can <em>fold across lines</em>, and a folded <code>From:</code> would have written a stray line into that database — quietly making the whole file unreadable to <code>recsel</code> while my own lenient parser shrugged and truncated it. Not a bug that would have shown up today. A bug that would have shown up in three months, on a bug report from someone with a long name.</p>\n<p>More on that one soon.</p>\n",
"content_text": "[Yesterday](2026-08-05-two-servers-two-domains-and-a-very-long-way-to-100.md) ended on a high: two clean servers, two domains, 100% on the XMPP Compliance Suite, real federation. Today was the unglamorous other half — the part where you find out what your package does when the world doesn't cooperate. I paired with **Claude** again.\n\n## One flaky download shouldn't sink an install\n\nThe ejabberd app installs **coturn** for audio/video calls. Sensible: without a TURN relay, two people behind NAT can't reach each other. But I had it as a *hard* dependency, so if `yunohost app install coturn` failed for any reason — GitHub having a moment, the app catalog hiccuping, a CI container with no route out — the entire ejabberd install died with it.\n\nThat's the wrong trade. STUN/TURN adds NAT traversal for calls. Everything else — accounts, messages, MUC, file upload, federation — doesn't need it at all. Losing a perfectly good XMPP server because an *optional* extra couldn't be fetched is a bad deal for whoever's installing it.\n\nSo coturn is now a soft dependency: try to install it, and if that fails, warn clearly, carry on, and tell the admin how to add it later. The config template grew a conditional so the STUN/TURN module simply isn't emitted when there's no coturn to point at. (An empty module would have made ejabberd refuse to start, which would have been a *very* silly way to fail.)\n\nThe interesting part was measuring it. In a container with no outbound git, the failure took **283 seconds** — nearly five minutes — because `git` has no connection timeout of its own and cheerfully retries into a black hole. Non-fatal but five minutes late is still a bad install. Now a 30-second probe checks reachability first. Install time in that environment went from 14 minutes to 7.\n\n## The restore that had never actually been restored\n\nThen the test suite got far enough to try something nobody had tried: **backup, remove, restore.**\n\nIt failed. Not subtly:\n\n```\nsed: can't read /etc/ejabberd/ejabberd.yml: Permission denied\n/usr/sbin/ejabberdctl: line 336: cd: /var/lib/ejabberd: Permission denied\nERROR: can not access directory /var/lib/ejabberd\n```\nYunoHost's restore helper hands every restored file back with deliberately restrictive ownership — root, no group access, no traversal. Sane default for an app served by the web server. Fatal for a daemon that runs as its own user: ejabberd couldn't read its own config, and couldn't even `cd` into its own database directory.\n\nMy favourite detail: ownership alone wasn't the fix. A directory left at mode `400` **cannot be entered even by the user who owns it** — you need the execute bit to traverse a directory. Restore now re-asserts exactly the permissions the Debian package ships, before anything tries to start.\n\nThis bug had been sitting there since the first line of the package. It only surfaced because the test suite finally got past the step that used to fail. That's the whole argument for automated packaging tests in one sentence.\n\n## Green, and \"Broken\"\n\nEnd result: **all four package_check tests pass** — linter, install, backup/restore, upgrade. First all-green run.\n\nThe summary then cheerfully prints **\"Global level 0 (Broken)\"**, which is a fun thing to see after a perfect run. Reading the scoring code explains it: level 1 requires zero linter *criticals*, and the two remaining criticals are \"this app is not in YunoHost's application catalog\" and \"not flagged as working in the catalog\" — which is precisely what my [open catalog PR](https://github.com/YunoHost/apps/pull/3573) fixes. Chicken, meet egg. The one linter error that *was* genuinely mine (`add_header` in the nginx config, which silently stops applying as soon as any nested block sets a header of its own) is fixed.\n\n## Upstream, meanwhile\n\nA small win: the Debian 13 keyring permission bug I reported — the one that quietly breaks every app install — got the reply *\"In any case, a chmod is good practice. Thanks for the report, we'll implement that.\"* Neither of us could reproduce it in a clean environment, and it's being hardened anyway. That's a good maintainer.\n\n## Teaser: a watcher for my own loose ends\n\nWhich brings me to the thing I actually didn't plan to build today.\n\nCounting up, I now have **eleven** open items sitting on other people's infrastructure: pull requests to YunoHost and Lexicon, bug reports to Debian and ProcessOne, a catalog submission, plus my own tracker. Three different systems, none of which talk to each other. Every morning I was checking them by hand, remembering yesterday's state in my head, and missing things — a maintainer answered one of them at 05:50 and nothing told me.\n\nI went looking for something that already did this. The closest is `bugwarrior`, which pulls GitHub, GitLab, Debian's BTS and more into Taskwarrior — but it has no Forgejo support, and its model is *import as tasks*, not *tell me what changed*. `gh-dash` is GitHub-only. `tea` is Forgejo-only. `bts` is Debian-only. Nothing spans the set.\n\nSo: **a small watcher that reports what moved.** A hand-kept list of what to watch, three read-only APIs, and a digest that stays silent unless something actually happened — a new comment (with who said it and what), a merge, a state change. The neat part is where it keeps its memory: instead of a state file next to the data, **the snapshot *is* the state**. It's a recutils database, so `recsel` queries it, and `git diff` on it shows exactly what the world did while I wasn't looking.\n\nIt's built and running against all eleven items. The best moment came from the code review: a reviewer noticed that Debian bug reports arrive as email, email headers can *fold across lines*, and a folded `From:` would have written a stray line into that database — quietly making the whole file unreadable to `recsel` while my own lenient parser shrugged and truncated it. Not a bug that would have shown up today. A bug that would have shown up in three months, on a bug report from someone with a long name.\n\nMore on that one soon.\n\n",
"date_published": "2026-08-06T22:38:22+02:00",
"url": "https://www.the-sprawl.blog/2026/08/06/a-soft-dependency-a-broken.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/05/two-servers-two-domains-and.html",
"title": "Two servers, two domains, and a very long way to 100%",
"content_html": "<p><a href=\"2026-08-04-jabber-matrix-and-four-bug-reports.md\">Yesterday</a> I concluded that ejabberd-for-Matrix isn’t ready, and that for plain XMPP my Prosody 13 setup is actually <em>ahead</em>. Fair. But the <a href=\"https://www.ejabberd.im/\">ejabberd</a> YunoHost app still needed to exist — properly, catalog-quality — for the day that Matrix gateway bug gets fixed, and because choice is good. A half-finished packaging experiment isn’t a real option.</p>\n<p>So today’s job was to take the app from “installs on my test box if I hold its hand” to “a stranger could install this and it just works.” The only honest way to prove that is a clean room: fresh servers, fresh domains, nobody’s thumb on the scale. I paired with <strong>Claude</strong> again, and my partner spun up two throwaway Debian boxes on Hetzner — <code>anton.this-is-system-a.de</code> and <code>bieber.this-is-system-b.de</code>, two <em>separate</em> real domains, DNS at Porkbun. Two domains, not one, on purpose: you can’t test <strong>federation</strong> with a single server.</p>\n<h2 id=\"the-headline\">The headline</h2>\n<p>From two bare Debian installs to two YunoHost servers, each running ejabberd, each with a real Let’s Encrypt certificate — and:</p>\n<ul>\n<li><strong>Both servers score 100% on the XMPP Compliance Suite</strong> — <a href=\"https://compliance.conversations.im/server/anton.this-is-system-a.de/\">anton</a> <em>and</em> <a href=\"https://compliance.conversations.im/server/bieber.this-is-system-b.de/\">bieber</a> — on <em>clean installs</em>, with <strong>zero</strong> manual fixups. Not a fluke on one box: two independent installs, same perfect score. (My own long-running server took a trail of hand-edits to get there; these just arrived.)</li>\n<li><strong>A message from <code>alice@anton</code> landed in <code>bob@bieber</code>’s mailbox</strong> — across two domains, server-to-server, over TLS. Real federation, not a loopback trick.</li>\n</ul>\n<p>That’s the whole thesis of a good XMPP server: speak the modern protocol correctly, and talk to <em>other</em> servers. Both, on a clean install. That’s the day’s win.</p>\n<h2 id=\"the-bit-im-quietly-proud-of-dns-that-configures-itself\">The bit I’m quietly proud of: DNS that configures itself</h2>\n<p>XMPP needs SRV records so clients and other servers can find it — including the <code>_xmpps</code> direct-TLS ones that basically nothing sets up for you. On my old server I typed those in by hand at the registrar, and watched them flap. This time the app <strong>declares its own DNS records</strong>, so YunoHost’s <code>domain dns suggest</code> just <em>knows</em> about them, and <code>domain dns push</code> sends them to the registrar. Set up a domain, push, done. That’s the difference between “installs” and “installs and configures itself.”</p>\n<h2 id=\"except-when-the-registrar-push-is-broken\">…except when the registrar push is broken</h2>\n<p>Which is where the day earned its bug reports. YunoHost’s Porkbun push cheerfully created the A, CNAME and TXT records — and then returned <strong><code>400 Bad Request</code> for every single MX and SRV record</strong>. Every one. On our test domains <em>and</em>, it turns out, on another of my servers, for all its domains.</p>\n<p>We traced it: Porkbun’s API wants a record’s priority in its own <code>prio</code> field, but YunoHost hands it the priority glued to the front of the record content (<code>"0 5 5223 host."</code>), which Porkbun rejects. So any Porkbun user’s mail (MX) and service records (SRV — XMPP, Matrix, SIP, you name it) silently fail to publish. That’s not a niche edge case; that’s “your mail and chat DNS don’t get set up.”</p>\n<p>So it went where it belongs — and this time with a fix attached:</p>\n<ul>\n<li>🐛 <strong><a href=\"https://github.com/YunoHost/issues/issues/2830\">YunoHost #2830</a></strong> — the full root-cause analysis and reproduction</li>\n<li>🔧 <strong><a href=\"https://github.com/dns-lexicon/dns-lexicon/pull/102\">dns-lexicon #102</a></strong> — a pull request that splits the priority into Porkbun’s <code>prio</code> field, fixing MX and SRV</li>\n</ul>\n<p>And a bonus gremlin: on Debian 13 the <code>sury_php</code> signing key ships readable only by root, so apt’s verifier can’t read it — which quietly breaks <em>every</em> app install at the dependency step until you <code>chmod</code> it. Not ours, but it’ll bite anyone on that release. One more to write up.</p>\n<h2 id=\"the-part-where-the-server-locked-me-out\">The part where the server locked me out</h2>\n<p>Now the comedy, because it wasn’t all triumphant. To do any of this, you need to <em>get into</em> the servers — and YunoHost, sensibly, hardens SSH the moment it finishes installing. My partner set up an admin user beforehand… as a plain Unix user, which YunoHost’s tightened SSH politely refuses. Then a pile of retry attempts tripped <strong>fail2ban</strong>, which banned us at the firewall. Then the console rescue needs a root password that a fresh cloud image doesn’t have. We reimaged. Twice.</p>\n<p>What finally worked was almost poetic: boot the boxes into <strong>Hetzner’s rescue system</strong>, mount the disk from the outside, and hand-edit the one line in the SSH config that decides who’s allowed in — then reboot back. Off-machine surgery to reopen the front door. Every step of that saga is now written into notes so neither of us repeats it. Ops is humbling; the trick is to only learn each lesson once.</p>\n<h2 id=\"where-this-leaves-things\">Where this leaves things</h2>\n<p>The ejabberd app is real now — not “works on my machine,” but <em>validated on a clean install, on real infrastructure, at 100%, federating with a second server.</em> It’s ready to put in front of the YunoHost catalog.</p>\n<p>The running tally of things that got better because we poked at them: yesterday’s <a href=\"2026-08-04-jabber-matrix-and-four-bug-reports.md\">four reports</a> about ejabberd, Debian and Prosody; today a YunoHost DNS bug <strong>and its fix</strong>, plus a Debian packaging gremlin. None of that was the goal. It’s just what falls out when you insist on testing the boring path — a fresh install, on a fresh domain — instead of the demo that always works.</p>\n<p>Two servers. Two domains. A hundred percent. Eventually.</p>\n",
"content_text": "[Yesterday](2026-08-04-jabber-matrix-and-four-bug-reports.md) I concluded that ejabberd-for-Matrix isn't ready, and that for plain XMPP my Prosody 13 setup is actually *ahead*. Fair. But the [ejabberd](https://www.ejabberd.im/) YunoHost app still needed to exist — properly, catalog-quality — for the day that Matrix gateway bug gets fixed, and because choice is good. A half-finished packaging experiment isn't a real option.\n\nSo today's job was to take the app from \"installs on my test box if I hold its hand\" to \"a stranger could install this and it just works.\" The only honest way to prove that is a clean room: fresh servers, fresh domains, nobody's thumb on the scale. I paired with **Claude** again, and my partner spun up two throwaway Debian boxes on Hetzner — `anton.this-is-system-a.de` and `bieber.this-is-system-b.de`, two *separate* real domains, DNS at Porkbun. Two domains, not one, on purpose: you can't test **federation** with a single server.\n\n## The headline\n\nFrom two bare Debian installs to two YunoHost servers, each running ejabberd, each with a real Let's Encrypt certificate — and:\n\n- **Both servers score 100% on the XMPP Compliance Suite** — [anton](https://compliance.conversations.im/server/anton.this-is-system-a.de/) *and* [bieber](https://compliance.conversations.im/server/bieber.this-is-system-b.de/) — on *clean installs*, with **zero** manual fixups. Not a fluke on one box: two independent installs, same perfect score. (My own long-running server took a trail of hand-edits to get there; these just arrived.)\n- **A message from `alice@anton` landed in `bob@bieber`'s mailbox** — across two domains, server-to-server, over TLS. Real federation, not a loopback trick.\n\nThat's the whole thesis of a good XMPP server: speak the modern protocol correctly, and talk to *other* servers. Both, on a clean install. That's the day's win.\n\n## The bit I'm quietly proud of: DNS that configures itself\n\nXMPP needs SRV records so clients and other servers can find it — including the `_xmpps` direct-TLS ones that basically nothing sets up for you. On my old server I typed those in by hand at the registrar, and watched them flap. This time the app **declares its own DNS records**, so YunoHost's `domain dns suggest` just *knows* about them, and `domain dns push` sends them to the registrar. Set up a domain, push, done. That's the difference between \"installs\" and \"installs and configures itself.\"\n\n## …except when the registrar push is broken\n\nWhich is where the day earned its bug reports. YunoHost's Porkbun push cheerfully created the A, CNAME and TXT records — and then returned **`400 Bad Request` for every single MX and SRV record**. Every one. On our test domains *and*, it turns out, on another of my servers, for all its domains.\n\nWe traced it: Porkbun's API wants a record's priority in its own `prio` field, but YunoHost hands it the priority glued to the front of the record content (`\"0 5 5223 host.\"`), which Porkbun rejects. So any Porkbun user's mail (MX) and service records (SRV — XMPP, Matrix, SIP, you name it) silently fail to publish. That's not a niche edge case; that's \"your mail and chat DNS don't get set up.\"\n\nSo it went where it belongs — and this time with a fix attached:\n\n- 🐛 **[YunoHost #2830](https://github.com/YunoHost/issues/issues/2830)** — the full root-cause analysis and reproduction\n- 🔧 **[dns-lexicon #102](https://github.com/dns-lexicon/dns-lexicon/pull/102)** — a pull request that splits the priority into Porkbun's `prio` field, fixing MX and SRV\n\nAnd a bonus gremlin: on Debian 13 the `sury_php` signing key ships readable only by root, so apt's verifier can't read it — which quietly breaks *every* app install at the dependency step until you `chmod` it. Not ours, but it'll bite anyone on that release. One more to write up.\n\n## The part where the server locked me out\n\nNow the comedy, because it wasn't all triumphant. To do any of this, you need to *get into* the servers — and YunoHost, sensibly, hardens SSH the moment it finishes installing. My partner set up an admin user beforehand… as a plain Unix user, which YunoHost's tightened SSH politely refuses. Then a pile of retry attempts tripped **fail2ban**, which banned us at the firewall. Then the console rescue needs a root password that a fresh cloud image doesn't have. We reimaged. Twice.\n\nWhat finally worked was almost poetic: boot the boxes into **Hetzner's rescue system**, mount the disk from the outside, and hand-edit the one line in the SSH config that decides who's allowed in — then reboot back. Off-machine surgery to reopen the front door. Every step of that saga is now written into notes so neither of us repeats it. Ops is humbling; the trick is to only learn each lesson once.\n\n## Where this leaves things\n\nThe ejabberd app is real now — not \"works on my machine,\" but *validated on a clean install, on real infrastructure, at 100%, federating with a second server.* It's ready to put in front of the YunoHost catalog.\n\nThe running tally of things that got better because we poked at them: yesterday's [four reports](2026-08-04-jabber-matrix-and-four-bug-reports.md) about ejabberd, Debian and Prosody; today a YunoHost DNS bug **and its fix**, plus a Debian packaging gremlin. None of that was the goal. It's just what falls out when you insist on testing the boring path — a fresh install, on a fresh domain — instead of the demo that always works.\n\nTwo servers. Two domains. A hundred percent. Eventually.\n\n",
"date_published": "2026-08-05T23:29:30+02:00",
"url": "https://www.the-sprawl.blog/2026/08/05/two-servers-two-domains-and.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/04/can-one-server-speak-both.html",
"title": "Can one server speak both Jabber and Matrix?",
"content_html": "<p>Yesterday I <a href=\"2026-08-03-coming-home-to-jabber.md\">came home to Jabber</a> — my own XMPP server, <code>ralph@mayer.rocks</code>, passing the compliance suite. But I run more than XMPP. There’s a Matrix homeserver (Synapse) too, with bridges puppeting Signal and WhatsApp into it. It’s a lot of moving parts for “sending messages to people.”</p>\n<p>So today’s question was bigger: <strong>could a single server do it all?</strong> <a href=\"https://www.ejabberd.im/\">ejabberd</a> is an XMPP server like Prosody — but it also ships an experimental <em>Matrix gateway</em>. If that works, one server could speak Jabber to the XMPP world <strong>and</strong> federate with Matrix. That would let me retire a whole box.</p>\n<p>I paired with <strong>Claude</strong> again, spun up two throwaway VMs — one running ejabberd, one running YunoHost with Prosody 13 — and started poking.</p>\n<h2 id=\"the-moment-a-message-crossed-the-streams\">The moment a message crossed the streams</h2>\n<p>The headline first, because it genuinely made me grin: <strong>an XMPP account sent a direct message to my Matrix account, and it arrived in Element.</strong> No bridge, no puppeting — ejabberd’s gateway federated straight to my Matrix server and delivered it. XMPP and Matrix are completely different protocols, and here was a message hopping cleanly from one to the other. That’s the kind of interoperability the open web is supposed to have and mostly doesn’t.</p>\n<p>But it was fragile. On the ejabberd that Debian ships, <em>every</em> outbound Matrix message crashed instead. We chased it down to a real bug: Debian builds ejabberd against a newer Erlang (OTP 27) whose new JSON encoder rejects the data format the Matrix gateway produces. On the older Erlang that ejabberd’s own builds bundle (OTP 26), it works fine. Same code, different runtime, completely different outcome.</p>\n<p>So that got written up and sent where it belongs:</p>\n<ul>\n<li>🐛 <strong><a href=\"https://github.com/processone/ejabberd/issues/4602\">ejabberd upstream #4602</a></strong> — with the full crash analysis</li>\n<li>🐛 <strong><a href=\"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1143612\">Debian #1143612</a></strong> — the downstream packaging side</li>\n</ul>\n<h2 id=\"the-verdict-not-yet\">The verdict: not yet</h2>\n<p>As much as I wanted the “one server” answer, the honest verdict is <strong>not yet</strong>. ejabberd’s Matrix gateway is experimental and, on the current Debian/Erlang combo, broken. And for plain XMPP, Prosody 13 is actually <em>ahead</em> — it ships the modern authentication stack (SASL2, Bind2, channel binding) that Debian’s ejabberd can’t currently offer. Replacing Prosody would be a step backward.</p>\n<p>So: keep Prosody for XMPP, keep an eye on ejabberd-for-Matrix, and revisit once that bug is fixed upstream. I wrote the whole comparison up as a decision doc so future-me doesn’t have to re-derive it.</p>\n<h2 id=\"hardening-what-i-already-have\">Hardening what I already have</h2>\n<p>Prosody 13 has that shiny modern auth stack — but it isn’t switched on by default in the YunoHost package. Flipping it on made my server advertise <strong>SASL2</strong> and <strong>channel binding</strong> (the mechanism that detects a man-in-the-middle even when they hold a “valid” certificate). Naturally, that went upstream too:</p>\n<ul>\n<li>🔧 <strong><a href=\"https://github.com/YunoHost-Apps/prosody_ynh/pull/80\">prosody_ynh #80</a></strong> — enable the Prosody 13 SASL2 stack (tested end-to-end on a real install)</li>\n</ul>\n<h2 id=\"the-wall-i-hit\">The wall I hit</h2>\n<p>Here’s the twist. I turned on channel binding… and it still can’t actually be <em>used</em>. Channel binding rides on <strong>SCRAM</strong>, a way of proving your password without ever sending it to the server. And YunoHost — like a lot of directory-backed setups — can’t do SCRAM. It stores your password as a one-way hash and checks logins with a classic LDAP “bind,” which means the server only ever sees the plaintext (<code>PLAIN</code>, protected by TLS). There’s simply nowhere for the SCRAM secret to live.</p>\n<p>That’s not a Prosody problem or an ejabberd problem — it’s baked into how the whole platform stores credentials. So rather than hack around it, I filed a clear, evidence-backed question to the people who can actually fix it:</p>\n<ul>\n<li>❓ <strong><a href=\"https://github.com/YunoHost/issues/issues/2829\">YunoHost #2829</a></strong> — is SCRAM-capable credential storage on the roadmap?</li>\n</ul>\n<p>(There was a request for this back in 2020 that got closed because nobody could explain concretely what was broken. This time it comes with the actual blockers, the actual impact, and three concrete paths forward.)</p>\n<h2 id=\"four-contributions-in-a-day\">Four contributions in a day</h2>\n<p>I didn’t end the day with one server to rule them all. I ended it with two bug reports, a pull request, and a feature request — and a much clearer map of what’s actually possible.</p>\n<p>And honestly, that’s the better outcome. The fantasy of collapsing everything onto one box is seductive, but the real win is the open network getting a little sturdier: a Matrix bug that’ll get fixed, an XMPP package that’ll ship modern auth, and a platform question that’s finally stated clearly enough to answer.</p>\n<p>That, and a message that crossed from Jabber to Matrix and landed in my pocket. Some days that’s enough.</p>\n<p><em>(The unglamorous footnote: getting here involved locking myself out of a test box more times than I’ll admit, a password only a robot knew, and an SSH agent that kept going to sleep. “Standing up a server” is never just clicking install. It never was.)</em></p>\n",
"content_text": "Yesterday I [came home to Jabber](2026-08-03-coming-home-to-jabber.md) — my own XMPP server, `ralph@mayer.rocks`, passing the compliance suite. But I run more than XMPP. There's a Matrix homeserver (Synapse) too, with bridges puppeting Signal and WhatsApp into it. It's a lot of moving parts for \"sending messages to people.\"\n\nSo today's question was bigger: **could a single server do it all?** [ejabberd](https://www.ejabberd.im/) is an XMPP server like Prosody — but it also ships an experimental *Matrix gateway*. If that works, one server could speak Jabber to the XMPP world **and** federate with Matrix. That would let me retire a whole box.\n\nI paired with **Claude** again, spun up two throwaway VMs — one running ejabberd, one running YunoHost with Prosody 13 — and started poking.\n\n## The moment a message crossed the streams\n\nThe headline first, because it genuinely made me grin: **an XMPP account sent a direct message to my Matrix account, and it arrived in Element.** No bridge, no puppeting — ejabberd's gateway federated straight to my Matrix server and delivered it. XMPP and Matrix are completely different protocols, and here was a message hopping cleanly from one to the other. That's the kind of interoperability the open web is supposed to have and mostly doesn't.\n\nBut it was fragile. On the ejabberd that Debian ships, *every* outbound Matrix message crashed instead. We chased it down to a real bug: Debian builds ejabberd against a newer Erlang (OTP 27) whose new JSON encoder rejects the data format the Matrix gateway produces. On the older Erlang that ejabberd's own builds bundle (OTP 26), it works fine. Same code, different runtime, completely different outcome.\n\nSo that got written up and sent where it belongs:\n\n- 🐛 **[ejabberd upstream #4602](https://github.com/processone/ejabberd/issues/4602)** — with the full crash analysis\n- 🐛 **[Debian #1143612](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1143612)** — the downstream packaging side\n\n## The verdict: not yet\n\nAs much as I wanted the \"one server\" answer, the honest verdict is **not yet**. ejabberd's Matrix gateway is experimental and, on the current Debian/Erlang combo, broken. And for plain XMPP, Prosody 13 is actually *ahead* — it ships the modern authentication stack (SASL2, Bind2, channel binding) that Debian's ejabberd can't currently offer. Replacing Prosody would be a step backward.\n\nSo: keep Prosody for XMPP, keep an eye on ejabberd-for-Matrix, and revisit once that bug is fixed upstream. I wrote the whole comparison up as a decision doc so future-me doesn't have to re-derive it.\n\n## Hardening what I already have\n\nProsody 13 has that shiny modern auth stack — but it isn't switched on by default in the YunoHost package. Flipping it on made my server advertise **SASL2** and **channel binding** (the mechanism that detects a man-in-the-middle even when they hold a \"valid\" certificate). Naturally, that went upstream too:\n\n- 🔧 **[prosody_ynh #80](https://github.com/YunoHost-Apps/prosody_ynh/pull/80)** — enable the Prosody 13 SASL2 stack (tested end-to-end on a real install)\n\n## The wall I hit\n\nHere's the twist. I turned on channel binding… and it still can't actually be *used*. Channel binding rides on **SCRAM**, a way of proving your password without ever sending it to the server. And YunoHost — like a lot of directory-backed setups — can't do SCRAM. It stores your password as a one-way hash and checks logins with a classic LDAP \"bind,\" which means the server only ever sees the plaintext (`PLAIN`, protected by TLS). There's simply nowhere for the SCRAM secret to live.\n\nThat's not a Prosody problem or an ejabberd problem — it's baked into how the whole platform stores credentials. So rather than hack around it, I filed a clear, evidence-backed question to the people who can actually fix it:\n\n- ❓ **[YunoHost #2829](https://github.com/YunoHost/issues/issues/2829)** — is SCRAM-capable credential storage on the roadmap?\n\n(There was a request for this back in 2020 that got closed because nobody could explain concretely what was broken. This time it comes with the actual blockers, the actual impact, and three concrete paths forward.)\n\n## Four contributions in a day\n\nI didn't end the day with one server to rule them all. I ended it with two bug reports, a pull request, and a feature request — and a much clearer map of what's actually possible.\n\nAnd honestly, that's the better outcome. The fantasy of collapsing everything onto one box is seductive, but the real win is the open network getting a little sturdier: a Matrix bug that'll get fixed, an XMPP package that'll ship modern auth, and a platform question that's finally stated clearly enough to answer.\n\nThat, and a message that crossed from Jabber to Matrix and landed in my pocket. Some days that's enough.\n\n*(The unglamorous footnote: getting here involved locking myself out of a test box more times than I'll admit, a password only a robot knew, and an SSH agent that kept going to sleep. \"Standing up a server\" is never just clicking install. It never was.)*\n\n",
"date_published": "2026-08-04T22:39:21+02:00",
"url": "https://www.the-sprawl.blog/2026/08/04/can-one-server-speak-both.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/03/coming-home-to-jabber.html",
"title": "Coming home to Jabber",
"content_html": "<p>I used to give talks about XMPP. Back then I was sure Jabber would win — an open, federated, standards-based protocol for real-time messaging, the way email is for mail. It didn’t win. The walled gardens did, and today “chat” means a dozen incompatible silos, each with its own app demanding a slice of your phone and your attention.</p>\n<p>But the protocol never died. And lately I’ve had the itch to come home to it. So I stood up my own XMPP server.</p>\n<p><strong>My new address: <code>ralph@mayer.rocks</code></strong></p>\n<p>It runs <a href=\"https://prosody.im/\">Prosody</a> on my existing YunoHost box, federates with the open network, and does all the modern things you’d want — synced message history, mobile push, media sharing, group chats, OMEMO end-to-end encryption.</p>\n<p>Getting there was more interesting than “click install.” I paired with <strong>Claude</strong> (Anthropic’s coding agent) for the whole thing, and what began as deploying the YunoHost Prosody app turned into a proper debugging session. The stock package scored <strong>91%</strong> on the <a href=\"https://compliance.conversations.im/\">XMPP Compliance Suite</a>; I wanted 100%, and along the way we turned up some real bugs:</p>\n<ul>\n<li><strong>Direct-TLS (XEP-0368) was silently broken.</strong> The listener on port 5223 had no certificate configured, so <em>every</em> handshake failed — the compliance test could never pass, even with the SRV records correct. STARTTLS worked, so nobody had noticed. One config line fixed it.</li>\n<li><strong>A community module with an undocumented dependency</strong> that quietly failed to load.</li>\n<li><strong>SRV records the package never registered</strong> — plus a fun quirk where YunoHost mangles SRV records when pushing them to Porkbun.</li>\n</ul>\n<p>We fixed all of it and hit <strong>100% compliance</strong> — direct-TLS both ways, SASL SCRAM downgrade protection, the lot.</p>\n<p>The part I’m happiest about: it went back <strong>upstream</strong>. Rather than keep the fixes to myself, we sent them as a pull request to the YunoHost Prosody package, so the next person gets a server that passes compliance out of the box:</p>\n<p>-> <strong><a href=\"https://github.com/YunoHost-Apps/prosody_ynh/pull/79\">YunoHost-Apps/prosody_ynh #79</a></strong></p>\n<p>That’s the whole point of the open network, really. You don’t just consume it — you leave it a little better than you found it.</p>\n<p>So: if you’re on XMPP, add me — <strong><code>ralph@mayer.rocks</code></strong>. And if you’re not… maybe it’s time to come home too.</p>\n<p><a href='https://compliance.conversations.im/server/mayer.rocks'><img src='https://compliance.conversations.im/badge/mayer.rocks'></a></p>\n",
"content_text": "I used to give talks about XMPP. Back then I was sure Jabber would win — an open, federated, standards-based protocol for real-time messaging, the way email is for mail. It didn't win. The walled gardens did, and today \"chat\" means a dozen incompatible silos, each with its own app demanding a slice of your phone and your attention.\n\nBut the protocol never died. And lately I've had the itch to come home to it. So I stood up my own XMPP server.\n\n**My new address: `ralph@mayer.rocks`**\n\nIt runs [Prosody](https://prosody.im/) on my existing YunoHost box, federates with the open network, and does all the modern things you'd want — synced message history, mobile push, media sharing, group chats, OMEMO end-to-end encryption.\n\nGetting there was more interesting than \"click install.\" I paired with **Claude** (Anthropic's coding agent) for the whole thing, and what began as deploying the YunoHost Prosody app turned into a proper debugging session. The stock package scored **91%** on the [XMPP Compliance Suite](https://compliance.conversations.im/); I wanted 100%, and along the way we turned up some real bugs:\n\n- **Direct-TLS (XEP-0368) was silently broken.** The listener on port 5223 had no certificate configured, so *every* handshake failed — the compliance test could never pass, even with the SRV records correct. STARTTLS worked, so nobody had noticed. One config line fixed it.\n- **A community module with an undocumented dependency** that quietly failed to load.\n- **SRV records the package never registered** — plus a fun quirk where YunoHost mangles SRV records when pushing them to Porkbun.\n\nWe fixed all of it and hit **100% compliance** — direct-TLS both ways, SASL SCRAM downgrade protection, the lot.\n\nThe part I'm happiest about: it went back **upstream**. Rather than keep the fixes to myself, we sent them as a pull request to the YunoHost Prosody package, so the next person gets a server that passes compliance out of the box:\n\n-> **[YunoHost-Apps/prosody_ynh #79](https://github.com/YunoHost-Apps/prosody_ynh/pull/79)**\n\nThat's the whole point of the open network, really. You don't just consume it — you leave it a little better than you found it.\n\nSo: if you're on XMPP, add me — **`ralph@mayer.rocks`**. And if you're not… maybe it's time to come home too.\n\n\n<a href='https://compliance.conversations.im/server/mayer.rocks'><img src='https://compliance.conversations.im/badge/mayer.rocks'></a> \n",
"date_published": "2026-08-03T23:21:00+02:00",
"url": "https://www.the-sprawl.blog/2026/08/03/coming-home-to-jabber.html"
},
{
"id": "http://tabtwo.micro.blog/2026/08/01/gefleckte-weinbergschnecken-kommen-eigentlich-im.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://eu.uploads.micro.blog/63514/2026/tykfh1uvfpt2nikugsxfpebmupdh2at9yziianz1.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Gefleckte Weinbergschnecken<br />\nKommen eigentlich im Mittelmeerraum vor, dank Klimawandel ist es auch hier warm genug.</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://eu.uploads.micro.blog/63514/2026/tykfh1uvfpt2nikugsxfpebmupdh2at9yziianz1.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Gefleckte Weinbergschnecken<br />\nKommen eigentlich im Mittelmeerraum vor, dank Klimawandel ist es auch hier warm genug.</p>\n",
"date_published": "2026-08-01T11:02:06+02:00",
"url": "https://www.the-sprawl.blog/2026/08/01/gefleckte-weinbergschnecken-kommen-eigentlich-im.html"
},
{
"id": "http://tabtwo.micro.blog/2026/07/26/hornissenschwebfliege.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://eu.uploads.micro.blog/63514/2026/1teocj4tdej0qa6voowg6uwgiclrcgiwqgjuwjah.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Hornissenschwebfliege</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://eu.uploads.micro.blog/63514/2026/1teocj4tdej0qa6voowg6uwgiclrcgiwqgjuwjah.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Hornissenschwebfliege</p>\n",
"date_published": "2026-07-26T13:14:21+02:00",
"url": "https://www.the-sprawl.blog/2026/07/26/hornissenschwebfliege.html"
},
{
"id": "http://tabtwo.micro.blog/2026/07/19/til-nach-mehr-als-jahren.html",
"content_html": "<p>TIL: nach mehr als 20 Jahren ist das Loch vom Ohrring noch durchgängig ist.</p>\n",
"content_text": "TIL: nach mehr als 20 Jahren ist das Loch vom Ohrring noch durchgängig ist. \n",
"date_published": "2026-07-19T12:39:16+02:00",
"url": "https://www.the-sprawl.blog/2026/07/19/til-nach-mehr-als-jahren.html"
},
{
"id": "http://tabtwo.micro.blog/2026/07/14/pidp-passt-schon-mal-ins.html",
"content_html": "<p>Pidp 11/70 passt schon mal ins Gehäuse</p>\n<img src=\"https://eu.uploads.micro.blog/63514/2026/319f1da46b4b43e4a37e70a0307d3b7e.jpg\" width=\"450\" height=\"600\" alt=\"\">\n",
"content_text": "Pidp 11/70 passt schon mal ins Gehäuse \n\n<img src=\"https://eu.uploads.micro.blog/63514/2026/319f1da46b4b43e4a37e70a0307d3b7e.jpg\" width=\"450\" height=\"600\" alt=\"\">\n",
"date_published": "2026-07-14T22:24:44+02:00",
"url": "https://www.the-sprawl.blog/2026/07/14/pidp-passt-schon-mal-ins.html"
},
{
"id": "http://tabtwo.micro.blog/2026/07/14/pidp-geht-weiter.html",
"content_html": "<p>Pidp 11/70 geht weiter</p>\n<img src=\"uploads/2026/60c1aa18d2cc4efdb3bf4669c2c4cfcf.jpg\" width=\"450\" height=\"600\" alt=\"\">\n",
"content_text": "Pidp 11/70 geht weiter\n\n<img src=\"uploads/2026/60c1aa18d2cc4efdb3bf4669c2c4cfcf.jpg\" width=\"450\" height=\"600\" alt=\"\">\n",
"date_published": "2026-07-14T21:23:41+02:00",
"url": "https://www.the-sprawl.blog/2026/07/14/pidp-geht-weiter.html"
},
{
"id": "http://tabtwo.micro.blog/2026/07/11/bldes-gefhl-da-drauf-zu.html",
"content_html": "<p>Blödes Gefühl da drauf zu stehen</p>\n<img src=\"uploads/2026/c37187afbdee4597b299aee3b9c3e767.jpg\" width=\"450\" height=\"600\" alt=\"\">\n",
"content_text": "Blödes Gefühl da drauf zu stehen \n\n<img src=\"uploads/2026/c37187afbdee4597b299aee3b9c3e767.jpg\" width=\"450\" height=\"600\" alt=\"\">\n",
"date_published": "2026-07-11T13:02:02+02:00",
"url": "https://www.the-sprawl.blog/2026/07/11/bldes-gefhl-da-drauf-zu.html"
},
{
"id": "http://tabtwo.micro.blog/2026/07/09/so-ein-biohazard-konzert-ist.html",
"content_html": "<p>So ein Biohazard Konzert ist inzwischen auch eine Versammlung alter Männer (und auch ein paar Frauen)</p>\n",
"content_text": "So ein Biohazard Konzert ist inzwischen auch eine Versammlung alter Männer (und auch ein paar Frauen)\n",
"date_published": "2026-07-09T19:41:25+02:00",
"url": "https://www.the-sprawl.blog/2026/07/09/so-ein-biohazard-konzert-ist.html"
},
{
"id": "http://tabtwo.micro.blog/2026/07/07/pidp.html",
"content_html": "<p>PiDP-11/70</p>\n<img src=\"uploads/2026/d59199bbf5b44ec293a9d3bc5d015d99.jpg\" width=\"450\" height=\"600\" alt=\"\">\n",
"content_text": "PiDP-11/70\n\n<img src=\"uploads/2026/d59199bbf5b44ec293a9d3bc5d015d99.jpg\" width=\"450\" height=\"600\" alt=\"\">\n",
"date_published": "2026-07-07T22:29:50+02:00",
"url": "https://www.the-sprawl.blog/2026/07/07/pidp.html"
},
{
"id": "http://tabtwo.micro.blog/2026/06/30/dringend-mal-wieder-fight-club.html",
"content_html": "<p>Dringend mal wieder Fight Club anschauen!</p>\n",
"content_text": "Dringend mal wieder Fight Club anschauen!\n",
"date_published": "2026-06-30T12:23:35+02:00",
"url": "https://www.the-sprawl.blog/2026/06/30/dringend-mal-wieder-fight-club.html"
},
{
"id": "http://tabtwo.micro.blog/2026/06/28/irgendeine-bremse-mit-riesigen-orangenen.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/ue1laniiyvcqserfehzz290gpixpajikmimqhxbz.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Irgendeine Bremse mit riesigen orangenen Augen.</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/ue1laniiyvcqserfehzz290gpixpajikmimqhxbz.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Irgendeine Bremse mit riesigen orangenen Augen.</p>\n",
"date_published": "2026-06-28T14:02:38+02:00",
"url": "https://www.the-sprawl.blog/2026/06/28/irgendeine-bremse-mit-riesigen-orangenen.html"
},
{
"id": "http://tabtwo.micro.blog/2026/06/26/nach-dem-berragenden-erfolg-des.html",
"content_html": "<p>nach dem überragenden Erfolg des <a href=\"https://rent-a-s%C3%BCndenbock.de\">https://rent-a-sündenbock.de</a> gibt es jetzt als Ergänzung die <a href=\"https://expertensch%C3%A4tzung.de\">https://expertenschätzung.de</a></p>\n",
"content_text": "nach dem überragenden Erfolg des [https://rent-a-sündenbock.de](https://rent-a-sündenbock.de) gibt es jetzt als Ergänzung die [https://expertenschätzung.de](https://expertenschätzung.de)\n",
"date_published": "2026-06-26T14:21:43+02:00",
"url": "https://www.the-sprawl.blog/2026/06/26/nach-dem-berragenden-erfolg-des.html"
},
{
"id": "http://tabtwo.micro.blog/2026/06/24/wurde-dann-jetzt-sogar-dafr.html",
"content_html": "<p>Wurde dann jetzt sogar 18:30. dafür dann morgen dasselbe noch einmal weil ein großes Stück des Rohres getauscht werden muss weil es komplett mürbe ist. Nice</p>\n",
"content_text": "Wurde dann jetzt sogar 18:30. dafür dann morgen dasselbe noch einmal weil ein großes Stück des Rohres getauscht werden muss weil es komplett mürbe ist. Nice\n",
"date_published": "2026-06-24T18:36:13+02:00",
"url": "https://www.the-sprawl.blog/2026/06/24/wurde-dann-jetzt-sogar-dafr.html"
},
{
"id": "http://tabtwo.micro.blog/2026/06/24/auch-geil-bei-grad-im.html",
"content_html": "<p>Auch geil bei 30 Grad im Schatten: Wasserrohrbruch und deswegen kein Wasser von 08:00 bis 15:00</p>\n",
"content_text": "Auch geil bei 30 Grad im Schatten: Wasserrohrbruch und deswegen kein Wasser von 08:00 bis 15:00\n",
"date_published": "2026-06-24T12:50:30+02:00",
"url": "https://www.the-sprawl.blog/2026/06/24/auch-geil-bei-grad-im.html"
},
{
"id": "http://tabtwo.micro.blog/2026/06/24/in-der-kche-ist-es.html",
"content_html": "<p>In der Küche ist es so warm, das Kochfeld zeigt drei von vier Platten als „heiß“ an</p>\n",
"content_text": "In der Küche ist es so warm, das Kochfeld zeigt drei von vier Platten als „heiß“ an\n",
"date_published": "2026-06-24T12:42:26+02:00",
"url": "https://www.the-sprawl.blog/2026/06/24/in-der-kche-ist-es.html"
},
{
"id": "http://tabtwo.micro.blog/2026/06/22/respekt-und-glckwunsch-an-wer.html",
"content_html": "<p>Respekt und Glückwunsch an wer auch immer die Displays der Packstationen spezifiziert hat. Ich habe heute ein Paket an einer Station abgegeben, die den halben Tag in der Sonne stand. Ich habe mir fast die Fingerspitze beim Tippen verbrannt so heiß war das Ding. Aber noch immer problemlos ablesbar. Krass.</p>\n",
"content_text": "Respekt und Glückwunsch an wer auch immer die Displays der Packstationen spezifiziert hat. Ich habe heute ein Paket an einer Station abgegeben, die den halben Tag in der Sonne stand. Ich habe mir fast die Fingerspitze beim Tippen verbrannt so heiß war das Ding. Aber noch immer problemlos ablesbar. Krass. \n",
"date_published": "2026-06-22T00:30:57+02:00",
"url": "https://www.the-sprawl.blog/2026/06/22/respekt-und-glckwunsch-an-wer.html"
},
{
"id": "http://tabtwo.micro.blog/2026/06/08/sommerrolle.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/navcpwnoru7ybybfq1ejer6aqssc8lni5m4fhl0b.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Sommerrolle</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/navcpwnoru7ybybfq1ejer6aqssc8lni5m4fhl0b.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Sommerrolle</p>\n",
"date_published": "2026-06-08T20:13:41+02:00",
"url": "https://www.the-sprawl.blog/2026/06/08/sommerrolle.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/31/senko-rai-wrote-a-wonderfull.html",
"content_html": "<p><a href=\"https://blog.senko.net/\">Senko Rašić </a>wrote a wonderfull <a href=\"https://blog.senko.net/how-i-want-to-use-ai\">article</a> how he wants to use AI. Its a quick read but it sets a good state of mind how AI should be approached. Lets take time to smell the roses …</p>\n",
"content_text": "[Senko Rašić ](https://blog.senko.net/)wrote a wonderfull [article](https://blog.senko.net/how-i-want-to-use-ai) how he wants to use AI. Its a quick read but it sets a good state of mind how AI should be approached. Lets take time to smell the roses ...\n",
"date_published": "2026-05-31T22:59:00+02:00",
"url": "https://www.the-sprawl.blog/2026/05/31/senko-rai-wrote-a-wonderfull.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/28/dnerstag.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/6d1efv6w49vtqzzem3vcnwuxsygehexv5nlbqwxm.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Dönerstag</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/6d1efv6w49vtqzzem3vcnwuxsygehexv5nlbqwxm.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Dönerstag</p>\n",
"date_published": "2026-05-28T15:48:00+02:00",
"url": "https://www.the-sprawl.blog/2026/05/28/dnerstag.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/26/es-ist-hart-wenn-im.html",
"content_html": "<p>Es ist hart, wenn im Shuffelmode direkt nach Slayer dann Bibi Blocksberg die Ohren verwöhnt.</p>\n",
"content_text": "Es ist hart, wenn im Shuffelmode direkt nach Slayer dann Bibi Blocksberg die Ohren verwöhnt. \n",
"date_published": "2026-05-26T10:10:45+02:00",
"url": "https://www.the-sprawl.blog/2026/05/26/es-ist-hart-wenn-im.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/25/goodbye-reddit-hello-lemmy.html",
"content_html": "<p>Goodbye #reddit\nHello #lemmy</p>\n",
"content_text": "Goodbye #reddit \nHello #lemmy\n",
"date_published": "2026-05-25T15:03:10+02:00",
"url": "https://www.the-sprawl.blog/2026/05/25/goodbye-reddit-hello-lemmy.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/24/fun-fact-i-can-control.html",
"content_html": "<p>Fun fact, I can control my Tensor Tympani muscle</p>\n",
"content_text": "Fun fact, I can control my Tensor Tympani muscle\n",
"date_published": "2026-05-24T20:55:50+02:00",
"url": "https://www.the-sprawl.blog/2026/05/24/fun-fact-i-can-control.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/24/ipad-mini-gen-scheint-mit.html",
"content_html": "<p>iPad mini 5 Gen scheint mit iOS 26.5 ganz gut zu laufen. Die 18er Versionen waren unbenutzbar.</p>\n",
"content_text": "iPad mini 5 Gen scheint mit iOS 26.5 ganz gut zu laufen. Die 18er Versionen waren unbenutzbar. \n",
"date_published": "2026-05-24T13:10:17+02:00",
"url": "https://www.the-sprawl.blog/2026/05/24/ipad-mini-gen-scheint-mit.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/23/triple-b-in-zuffenhausen-burger.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/hlhhvz38iwtmzzygxua3leb1ikdbknveeck0m4jn.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Triple B in <a href=\"https://pixelfed.mayer.rocks/discover/tags/Zuffenhausen?src=hash\" title=\"#Zuffenhausen\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Zuffenhausen</a><br />\n<br />\n<a href=\"https://pixelfed.mayer.rocks/discover/tags/Burger?src=hash\" title=\"#Burger\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Burger</a></p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/hlhhvz38iwtmzzygxua3leb1ikdbknveeck0m4jn.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Triple B in <a href=\"https://pixelfed.mayer.rocks/discover/tags/Zuffenhausen?src=hash\" title=\"#Zuffenhausen\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Zuffenhausen</a><br />\n<br />\n<a href=\"https://pixelfed.mayer.rocks/discover/tags/Burger?src=hash\" title=\"#Burger\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Burger</a></p>\n",
"date_published": "2026-05-23T16:26:49+02:00",
"url": "https://www.the-sprawl.blog/2026/05/23/triple-b-in-zuffenhausen-burger.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/22/gerade-im-blttle-darber-gestolpert.html",
"content_html": "<p>Gerade im Blättle darüber gestolpert. Das ist vermutlich die längste Domain, die ich jetzt kenne, knackige 49 Zeichen lang. Technisches Limit wären 63 Zeichen.</p>\n<p><a href=\"http://www.kirche-brettach-cleversulzbach-langenbeutingen.de\">www.kirche-brettach-cleversulzbach-langenbeutingen.de</a></p>\n",
"content_text": "Gerade im Blättle darüber gestolpert. Das ist vermutlich die längste Domain, die ich jetzt kenne, knackige 49 Zeichen lang. Technisches Limit wären 63 Zeichen. \n\n[www.kirche-brettach-cleversulzbach-langenbeutingen.de](http://www.kirche-brettach-cleversulzbach-langenbeutingen.de)\n",
"date_published": "2026-05-22T10:48:24+02:00",
"url": "https://www.the-sprawl.blog/2026/05/22/gerade-im-blttle-darber-gestolpert.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/13/finished-watching-deadpool-wolverine-der.html",
"content_html": "<p>Finished watching: <a href=\"https://www.themoviedb.org/movie/533535\">Deadpool & Wolverine</a> 🍿</p>\n<p>Der war ehrlich gesagt eher banal und ich hab gegen Ende ordentlich vorgespult</p>\n",
"content_text": "Finished watching: [Deadpool & Wolverine](https://www.themoviedb.org/movie/533535) 🍿\n\nDer war ehrlich gesagt eher banal und ich hab gegen Ende ordentlich vorgespult\n",
"date_published": "2026-05-13T17:50:26+02:00",
"url": "https://www.the-sprawl.blog/2026/05/13/finished-watching-deadpool-wolverine-der.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/03/erster-rhabarberkuchen-der-saison.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/b5xdgk2ouuvrevyqcem94oapxkwvlbllt46aem2d.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">erster Rhabarber-Kuchen der Saison</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/b5xdgk2ouuvrevyqcem94oapxkwvlbllt46aem2d.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">erster Rhabarber-Kuchen der Saison</p>\n",
"date_published": "2026-05-03T20:08:13+02:00",
"url": "https://www.the-sprawl.blog/2026/05/03/erster-rhabarberkuchen-der-saison.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/03/hornissenknigin-auf-der-suche-nach.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/4ulotxsbjh6qsfhqnifafetdcsf0ik8z0g75boeq.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Hornissenkönigin auf der Suche nach einem Nistplatz. In meinem Schuh war nicht genügend Platz.</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/4ulotxsbjh6qsfhqnifafetdcsf0ik8z0g75boeq.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Hornissenkönigin auf der Suche nach einem Nistplatz. In meinem Schuh war nicht genügend Platz.</p>\n",
"date_published": "2026-05-03T17:47:55+02:00",
"url": "https://www.the-sprawl.blog/2026/05/03/hornissenknigin-auf-der-suche-nach.html"
},
{
"id": "http://tabtwo.micro.blog/2026/05/03/bill-holbrook-bringt-meine-stimmung.html",
"content_html": "<p>Bill Holbrook bringt meine Stimmung mit dem heutigen Strip von <a href=\"https://www.kevinandkell.com/\">Kevin & Kell</a> ganz gut auf den Punkt. Wohin sol dieser ganze Mist im nahen Osten noch führen? Produktionseinschränkungen und vor allem massive Preissteigerungen bei Helium, Schwefel, Dünger, Kupfer, alle Öl-Derivate von Erdgas über Nafta bis zu schwerem Öl. Das heisst, die letzte Chip-Krise und die Gas-Notlage wird da gegen nur ein sehr laues Lüftchen sein gegen das was da an Ernte- Produktionsausfällen auf die Welt zukommt.\nAber hey, Deutschland sorgt sich über den Flug im kommenden Sommerurlaub während das eigentlich Problem Diesel sein wird ohne den es keine Logistik gibt und auch keine Landwirtschaft.</p>\n<p>Wird ein spannendes Jahr mal wieder.</p>\n",
"content_text": "Bill Holbrook bringt meine Stimmung mit dem heutigen Strip von [Kevin & Kell](https://www.kevinandkell.com/) ganz gut auf den Punkt. Wohin sol dieser ganze Mist im nahen Osten noch führen? Produktionseinschränkungen und vor allem massive Preissteigerungen bei Helium, Schwefel, Dünger, Kupfer, alle Öl-Derivate von Erdgas über Nafta bis zu schwerem Öl. Das heisst, die letzte Chip-Krise und die Gas-Notlage wird da gegen nur ein sehr laues Lüftchen sein gegen das was da an Ernte- Produktionsausfällen auf die Welt zukommt.\nAber hey, Deutschland sorgt sich über den Flug im kommenden Sommerurlaub während das eigentlich Problem Diesel sein wird ohne den es keine Logistik gibt und auch keine Landwirtschaft.\n\nWird ein spannendes Jahr mal wieder.\n",
"date_published": "2026-05-03T11:51:03+02:00",
"url": "https://www.the-sprawl.blog/2026/05/03/bill-holbrook-bringt-meine-stimmung.html"
},
{
"id": "http://tabtwo.micro.blog/2026/04/24/mastodon-migration.html",
"title": "Mastodon Migration",
"content_html": "<p>Aktuell migriere ich meine Single-user Instanz von der Software Mastodon auf <a href=\"https://gotosocial.org/\">GoToSocial</a> um.</p>\n",
"content_text": "Aktuell migriere ich meine Single-user Instanz von der Software Mastodon auf [GoToSocial](https://gotosocial.org/) um.\n",
"date_published": "2026-04-24T19:19:12+02:00",
"url": "https://www.the-sprawl.blog/2026/04/24/mastodon-migration.html"
},
{
"id": "http://tabtwo.micro.blog/2026/04/03/einfach-mal-chillen-wilhelma.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/gwnuncf7kh9ajq15dd1kh7o1aaogmx1ancddgx0b.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Einfach mal chillen <a href=\"https://pixelfed.mayer.rocks/discover/tags/Wilhelma?src=hash\" title=\"#Wilhelma\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Wilhelma</a></p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/gwnuncf7kh9ajq15dd1kh7o1aaogmx1ancddgx0b.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Einfach mal chillen <a href=\"https://pixelfed.mayer.rocks/discover/tags/Wilhelma?src=hash\" title=\"#Wilhelma\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Wilhelma</a></p>\n",
"date_published": "2026-04-03T14:58:59+02:00",
"url": "https://www.the-sprawl.blog/2026/04/03/einfach-mal-chillen-wilhelma.html"
},
{
"id": "http://tabtwo.micro.blog/2026/03/28/die-magnolien-haben-nur-noch.html",
"content_html": "<p>Die Magnolien haben nur noch braune Knospen vom Frost, es kommt Schneeregen runter und ich hab den Kamin angemacht. Weihnachten kann also kommen.</p>\n",
"content_text": "Die Magnolien haben nur noch braune Knospen vom Frost, es kommt Schneeregen runter und ich hab den Kamin angemacht. Weihnachten kann also kommen. \n",
"date_published": "2026-03-28T18:58:58+02:00",
"url": "https://www.the-sprawl.blog/2026/03/28/die-magnolien-haben-nur-noch.html"
},
{
"id": "http://tabtwo.micro.blog/2026/03/27/stellt-sich-raus-nicht-nur.html",
"content_html": "<p>Stellt sich raus, nicht nur Pflanzen und Tiere können invasiv sein, auch Pilze tauchen auf anderen Kontinenten auf und breiten sich mit ungewissen Folgen aus: <a href=\"https://www.bbc.com/future/article/20260325-an-unstoppable-mushroom-is-tearing-through-north-american-forests\">Artikel bei der BBC</a> dazu.\nUnd ja, der #Klimawandel trägt, wie üblich, auch seinen Teil dazubei</p>\n",
"content_text": "Stellt sich raus, nicht nur Pflanzen und Tiere können invasiv sein, auch Pilze tauchen auf anderen Kontinenten auf und breiten sich mit ungewissen Folgen aus: [Artikel bei der BBC](https://www.bbc.com/future/article/20260325-an-unstoppable-mushroom-is-tearing-through-north-american-forests) dazu.\nUnd ja, der #Klimawandel trägt, wie üblich, auch seinen Teil dazubei\n",
"date_published": "2026-03-27T11:44:50+02:00",
"url": "https://www.the-sprawl.blog/2026/03/27/stellt-sich-raus-nicht-nur.html"
},
{
"id": "http://tabtwo.micro.blog/2026/03/23/kleiner-mitbewohner-eine-speispinne-scytodes.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/goimpuxcyozxw8ykb0wzmorplykoyvhh3yf0gjwz.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Kleiner Mitbewohner, eine Speispinne Scytodes thoracica. Hübsch aber nur ca. 6 mm lang</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/goimpuxcyozxw8ykb0wzmorplykoyvhh3yf0gjwz.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Kleiner Mitbewohner, eine Speispinne Scytodes thoracica. Hübsch aber nur ca. 6 mm lang</p>\n",
"date_published": "2026-03-23T15:56:10+02:00",
"url": "https://www.the-sprawl.blog/2026/03/23/kleiner-mitbewohner-eine-speispinne-scytodes.html"
},
{
"id": "http://tabtwo.micro.blog/2026/03/11/das-war-also-die-wahl.html",
"title": "Das war also die Wahl zum Landtag in Baden Württemberg",
"content_html": "<p>Die Diskussion, ob jetzt die CDU oder die Grünen gewonnen haben, ist eigentlich vollkommen egal. Denn eine Mehrheit hätten weder CDU noch Grüne ohne Partner ja auch nicht. Blöd für die CDU, wenn man die Grünen aus ideologischen Gründen so dämonisiert (auch wenn ich noch nicht verstanden habe, was diese Ideologie sein soll). Also so ein Quatsch wie „das Gesetz muss weg, weil von Habeck" ist für mich halt kein rationaler Grund, sondern nur ein Kleinkind im Sandkasten auf dem Level „und du bist doof und riechst nach Lulu". Sorry, liebe CDU, mit so ‘nem Scheiß gewinnt ihr bei mir nix. Auch jetzt mit solchen Vorschlägen zu kommen wie eine „israelische Lösung", um den Job des Ministerpräsidenten aufzuteilen: WTF? Wie toll so eine „Lösung" funktioniert, sieht man ja im Nahen Osten. Da wird also jetzt der Preis für die Verhandlungen mit den Grünen hochgetrieben und der Brunnen vergiftet.</p>\n<p>Aber mal ganz nüchtern: Welche Möglichkeiten gibt es denn?</p>\n<ul>\n<li>Koalition Grün/Schwarz: der einzige Zustand mit einer Mehrheit im Parlament</li>\n<li>Minderheitsregierung Grün: wird dann maximal ideologisch durch die CDU torpediert und bedarf der Duldung der anderen Parteien</li>\n<li>Minderheitsregierung CDU: unter Duldung der anderen Parteien</li>\n<li>Koalition CDU/die andere Partei: werden sie sich (hoffentlich) nicht trauen</li>\n<li>Neuwahlen: werden vermutlich nichts ändern – SPD, Linke und FDP sind so klein, dass sie keine Auswirkung hätten, selbst wenn sie über die 5% kommen</li>\n</ul>\n<p>Läuft also auf eine Minderheitsregierung der CDU raus. F*ck.</p>\n",
"content_text": "Die Diskussion, ob jetzt die CDU oder die Grünen gewonnen haben, ist eigentlich vollkommen egal. Denn eine Mehrheit hätten weder CDU noch Grüne ohne Partner ja auch nicht. Blöd für die CDU, wenn man die Grünen aus ideologischen Gründen so dämonisiert (auch wenn ich noch nicht verstanden habe, was diese Ideologie sein soll). Also so ein Quatsch wie „das Gesetz muss weg, weil von Habeck\" ist für mich halt kein rationaler Grund, sondern nur ein Kleinkind im Sandkasten auf dem Level „und du bist doof und riechst nach Lulu\". Sorry, liebe CDU, mit so 'nem Scheiß gewinnt ihr bei mir nix. Auch jetzt mit solchen Vorschlägen zu kommen wie eine „israelische Lösung\", um den Job des Ministerpräsidenten aufzuteilen: WTF? Wie toll so eine „Lösung\" funktioniert, sieht man ja im Nahen Osten. Da wird also jetzt der Preis für die Verhandlungen mit den Grünen hochgetrieben und der Brunnen vergiftet.\n\nAber mal ganz nüchtern: Welche Möglichkeiten gibt es denn?\n\n* Koalition Grün/Schwarz: der einzige Zustand mit einer Mehrheit im Parlament\n* Minderheitsregierung Grün: wird dann maximal ideologisch durch die CDU torpediert und bedarf der Duldung der anderen Parteien\n* Minderheitsregierung CDU: unter Duldung der anderen Parteien\n* Koalition CDU/die andere Partei: werden sie sich (hoffentlich) nicht trauen\n* Neuwahlen: werden vermutlich nichts ändern – SPD, Linke und FDP sind so klein, dass sie keine Auswirkung hätten, selbst wenn sie über die 5% kommen\n\nLäuft also auf eine Minderheitsregierung der CDU raus. F*ck.\n",
"date_published": "2026-03-11T10:20:50+02:00",
"url": "https://www.the-sprawl.blog/2026/03/11/das-war-also-die-wahl.html"
},
{
"id": "http://tabtwo.micro.blog/2026/03/08/lfter-im-acasis-mac-mini.html",
"title": "Lüfter im Acasis Mac mini M4 Dock \u0026 Stand",
"content_html": "<p>Ich habe mir vor kurzem dieses <a href=\"https://www.acasis.com/de-de/products/acasis-mac-mini-m4-dock-stand-with-8tb-m-2-nvme-ssd-enclosure?variant=48073066414309\">Dock</a> zu meinem Mac Mini geleistet um eine lokale größere Festplatte zu haben (Apple Preise sind einfach schmerzhaft für größere SSDs).\nDas Dock funktioniert soweit wie es soll, hat allerdings einen Nachteil, da ist ein Notebook-Lüfter drin. Der ist 50 x 50 mm gross und nur 5 mm dick. Aslo von der Sorte, die eher selten leise sind. Dazu kommt, dass der recht häufig anspringt und wieder ausgeht und das bei mir anfangs mit einem sehr nervigen Ton.\nAllerdings kann man den Träger recht einfach aufschrauben. Es hat gereicht den Lüfter einmal auszubauen und wieder einzubauen, danach war er kaum noch zu hören. Falls ihr also so ein Teil habt und es nervt, einfach mal versuchen den Lüfter zu lockern.</p>\n",
"content_text": "Ich habe mir vor kurzem dieses [Dock](https://www.acasis.com/de-de/products/acasis-mac-mini-m4-dock-stand-with-8tb-m-2-nvme-ssd-enclosure?variant=48073066414309) zu meinem Mac Mini geleistet um eine lokale größere Festplatte zu haben (Apple Preise sind einfach schmerzhaft für größere SSDs).\nDas Dock funktioniert soweit wie es soll, hat allerdings einen Nachteil, da ist ein Notebook-Lüfter drin. Der ist 50 x 50 mm gross und nur 5 mm dick. Aslo von der Sorte, die eher selten leise sind. Dazu kommt, dass der recht häufig anspringt und wieder ausgeht und das bei mir anfangs mit einem sehr nervigen Ton.\nAllerdings kann man den Träger recht einfach aufschrauben. Es hat gereicht den Lüfter einmal auszubauen und wieder einzubauen, danach war er kaum noch zu hören. Falls ihr also so ein Teil habt und es nervt, einfach mal versuchen den Lüfter zu lockern.\n",
"date_published": "2026-03-08T18:21:37+02:00",
"url": "https://www.the-sprawl.blog/2026/03/08/lfter-im-acasis-mac-mini.html"
},
{
"id": "http://tabtwo.micro.blog/2026/03/08/cpreisfrage-seit-wann-bin-ich.html",
"content_html": "<p>cPreisfrage: seit wann bin ich Claude User?</p>\n<img src=\"uploads/2026/forgejo-streak.png\" width=\"600\" height=\"123\" alt=\"\">\n",
"content_text": "cPreisfrage: seit wann bin ich Claude User?\n\n<img src=\"uploads/2026/forgejo-streak.png\" width=\"600\" height=\"123\" alt=\"\">\n",
"date_published": "2026-03-08T11:13:43+02:00",
"url": "https://www.the-sprawl.blog/2026/03/08/cpreisfrage-seit-wann-bin-ich.html"
},
{
"id": "http://tabtwo.micro.blog/2026/03/05/eventdb-wieder-online.html",
"title": "eventdb wieder online",
"content_html": "<p>Jetzt wieder im Angebot: die Event-Tabelle aus dem ganz alten Blog mit Terminen zu Konferenze, Festivals und lokalem Kleinkram.</p>\n<p>Nach über acht Jahren habe ich die CSV-Tabelle und die Perl-Tools kurzerhand mit Claude umgebaut. “Agentic Engineering” heißt das heutzutage – und ist echt faszinierend. Das Tool ist jetzt in Python gebaut, die Datenquelle statt CSV (igitt) in <a href=\"https://www.gnu.org/software/recutils/manual/recutils.html\">Gnu Recutils</a>, und die Tabelle wird als plain HTML rausgerendert.</p>\n<p>Das wirklich Faszinierende ist aber das Aktualisieren der Events. Vor zehn Jahren war das ein manueller Prozess: regelmäßig die Webseiten aufrufen und von Hand übertragen. Heute sage ich einfach Claude, er soll die Liste durchgehen und aktualisieren. Eine halbe Stunde später ist das fertig – ohne einen aufwendigen Scraper zu bauen.</p>\n<p>Zu finden unter <a href=\"https://eventdb.mayer.rocks/\">https://eventdb.mayer.rocks/</a>, ein ICS-Feed ist auch vorhanden.</p>\n<p>Edit: weil’s so schön war. Gleich noch ein paar Features wie eine Karte mit implementiert</p>\n",
"content_text": "Jetzt wieder im Angebot: die Event-Tabelle aus dem ganz alten Blog mit Terminen zu Konferenze, Festivals und lokalem Kleinkram.\n\nNach über acht Jahren habe ich die CSV-Tabelle und die Perl-Tools kurzerhand mit Claude umgebaut. \"Agentic Engineering\" heißt das heutzutage – und ist echt faszinierend. Das Tool ist jetzt in Python gebaut, die Datenquelle statt CSV (igitt) in [Gnu Recutils](https://www.gnu.org/software/recutils/manual/recutils.html), und die Tabelle wird als plain HTML rausgerendert.\n\nDas wirklich Faszinierende ist aber das Aktualisieren der Events. Vor zehn Jahren war das ein manueller Prozess: regelmäßig die Webseiten aufrufen und von Hand übertragen. Heute sage ich einfach Claude, er soll die Liste durchgehen und aktualisieren. Eine halbe Stunde später ist das fertig – ohne einen aufwendigen Scraper zu bauen.\n\nZu finden unter [https://eventdb.mayer.rocks/](https://eventdb.mayer.rocks/), ein ICS-Feed ist auch vorhanden.\n\nEdit: weil's so schön war. Gleich noch ein paar Features wie eine Karte mit implementiert\n",
"date_published": "2026-03-05T20:28:06+02:00",
"url": "https://www.the-sprawl.blog/2026/03/05/eventdb-wieder-online.html"
},
{
"id": "http://tabtwo.micro.blog/2026/03/03/shout-out-an-die-regierung.html",
"content_html": "<p>Shout out an die Regierung von Britisch Colombia, die haben nämlich die Abschaffung der Zeitumstellung beschlossen! Hier der Link zu einem <a href=\"https://www.cbc.ca/news/canada/british-columbia/b-c-adopting-year-round-daylight-time-9.7111657\">Zeitungsbericht</a>.</p>\n<p>Edit: Gerade erst gesehen, die sind jetzt dauerhaft auf Sommerzeit, das ist dann halt auch Quatsch</p>\n",
"content_text": "Shout out an die Regierung von Britisch Colombia, die haben nämlich die Abschaffung der Zeitumstellung beschlossen! Hier der Link zu einem [Zeitungsbericht](https://www.cbc.ca/news/canada/british-columbia/b-c-adopting-year-round-daylight-time-9.7111657).\n\nEdit: Gerade erst gesehen, die sind jetzt dauerhaft auf Sommerzeit, das ist dann halt auch Quatsch \n",
"date_published": "2026-03-03T09:29:18+02:00",
"url": "https://www.the-sprawl.blog/2026/03/03/shout-out-an-die-regierung.html"
},
{
"id": "http://tabtwo.micro.blog/2026/02/03/lecker-ente-im-httpshengamanicom-sehr.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/d9q2j68k36kojuqdgubshtusk7rqhpecmxaulihn.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Lecker Ente im <a href=\"https://heng-amani.com/\" rel=\"external nofollow noopener\" target=\"_blank\">https://heng-amani.com/</a><br />\n<br />\nSehr empfehlenswert!<br />\n<br />\n<a href=\"https://pixelfed.mayer.rocks/discover/tags/Feuerbach?src=hash\" title=\"#Feuerbach\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Feuerbach</a><br />\n<a href=\"https://pixelfed.mayer.rocks/discover/tags/Stuttgart?src=hash\" title=\"#Stuttgart\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Stuttgart</a></p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/d9q2j68k36kojuqdgubshtusk7rqhpecmxaulihn.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Lecker Ente im <a href=\"https://heng-amani.com/\" rel=\"external nofollow noopener\" target=\"_blank\">https://heng-amani.com/</a><br />\n<br />\nSehr empfehlenswert!<br />\n<br />\n<a href=\"https://pixelfed.mayer.rocks/discover/tags/Feuerbach?src=hash\" title=\"#Feuerbach\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Feuerbach</a><br />\n<a href=\"https://pixelfed.mayer.rocks/discover/tags/Stuttgart?src=hash\" title=\"#Stuttgart\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Stuttgart</a></p>\n",
"date_published": "2026-02-03T21:46:41+02:00",
"url": "https://www.the-sprawl.blog/2026/02/03/lecker-ente-im-httpshengamanicom-sehr.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/30/ich-werde-reich-httpsrentasndenbockde-vibegecoded.html",
"content_html": "<p>ich werde reich!</p>\n<p><a href=\"https://rent-a-s\">rent-a-s</a>ündenbock.de/</p>\n<p>(vibegecoded in 5 Minuten mit Claude, die Domain hat länger gedauert(</p>\n",
"content_text": "ich werde reich!\n\n[rent-a-s](https://rent-a-s)ündenbock.de/\n\n(vibegecoded in 5 Minuten mit Claude, die Domain hat länger gedauert(\n",
"date_published": "2026-01-30T21:13:31+02:00",
"url": "https://www.the-sprawl.blog/2026/01/30/ich-werde-reich-httpsrentasndenbockde-vibegecoded.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/29/finished-watching-the-naked-gun.html",
"content_html": "<p>Finished watching: <a href=\"https://www.themoviedb.org/movie/1035259\">The Naked Gun</a> 🍿</p>\n<p>War jetzt nicht so der Brüller. Ein paar Lacher waren dabei aber ist echt weit entfernt von den Originalen.</p>\n",
"content_text": "Finished watching: [The Naked Gun](https://www.themoviedb.org/movie/1035259) 🍿\n\nWar jetzt nicht so der Brüller. Ein paar Lacher waren dabei aber ist echt weit entfernt von den Originalen.\n",
"date_published": "2026-01-29T12:07:35+02:00",
"url": "https://www.the-sprawl.blog/2026/01/29/finished-watching-the-naked-gun.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/28/x-stimme-fr-landtagswahl-bw.html",
"content_html": "<p>[X] Stimme für #Landtagswahl BW abgeben</p>\n<p>Bürgerpflicht Nummer 1 erledigt</p>\n",
"content_text": "[X] Stimme für #Landtagswahl BW abgeben \n\n\nBürgerpflicht Nummer 1 erledigt \n",
"date_published": "2026-01-28T19:43:12+02:00",
"url": "https://www.the-sprawl.blog/2026/01/28/x-stimme-fr-landtagswahl-bw.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/26/schnee-wie-seit-jahrzehnten-nicht.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/ap3bdewnhg8suhln3djczthjoy4moioenx648olb.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\"><a href=\"https://pixelfed.mayer.rocks/discover/tags/Schnee?src=hash\" title=\"#Schnee\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Schnee</a> wie seit Jahrzehnten nicht</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/ap3bdewnhg8suhln3djczthjoy4moioenx648olb.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\"><a href=\"https://pixelfed.mayer.rocks/discover/tags/Schnee?src=hash\" title=\"#Schnee\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Schnee</a> wie seit Jahrzehnten nicht</p>\n",
"date_published": "2026-01-26T09:13:09+02:00",
"url": "https://www.the-sprawl.blog/2026/01/26/schnee-wie-seit-jahrzehnten-nicht.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/25/weissheiten-von-frank-nicht-in.html",
"content_html": "<p>Weissheiten von <a href=\"frankstohl@mastodon.social\">Frank</a>: Nicht in jedes Rabbithole hüpfen</p>\n<p>Würde sich auch gut als Nerdshirt machen.</p>\n",
"content_text": "Weissheiten von [Frank](frankstohl@mastodon.social): Nicht in jedes Rabbithole hüpfen\n\nWürde sich auch gut als Nerdshirt machen.\n",
"date_published": "2026-01-25T21:09:28+02:00",
"url": "https://www.the-sprawl.blog/2026/01/25/weissheiten-von-frank-nicht-in.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/25/til-ernhrungsfuzzies-sind-ernstzunehmen.html",
"title": "TIL - Ernährungsfuzzies sind ernstzunehmen",
"content_html": "<p>kleiner Chat mit Claude:</p>\n<p>❯ is calories and kcal the same?</p>\n<p>⏺ Technically: No. 1 kcal = 1000 calories.</p>\n<p>In nutrition: Yes, they’re used interchangeably. When a food label or calculator says “Calories,” it means kcal.</p>\n<p>So your 2,549 “Calories” BMR = 2,549 kcal, and your 400 “calorie” shake = 400 kcal. Same unit, confusing terminology.</p>\n<p>❯ so the k isnt 1000 like with any other unit in the metric system?</p>\n<p>⏺ The “k” does mean 1000, like always in metric.</p>\n<p>1 kcal = 1000 cal ✓</p>\n<p>The problem is that nutritionists and the food industry started calling kilocalories just “Calories” (sometimes with a capital C) decades ago because the small calorie was too tiny to be practical for food.</p>\n<p>So it’s not that the metric system is broken — it’s that nutrition adopted sloppy shorthand that stuck. When your shake says “400 calories,” they really mean “400 kilocalories” but dropped the “kilo” part.</p>\n<p>It’s genuinely bad terminology, and you’re right to find it confusing.</p>\n<p>❯ insert profany here</p>\n<p>⏺ Justified. Blame early 20th century American nutritionists who decided “kilocalorie” was too many syllables.</p>\n",
"content_text": "kleiner Chat mit Claude:\n\n❯ is calories and kcal the same?\n\n⏺ Technically: No. 1 kcal = 1000 calories.\n\n In nutrition: Yes, they're used interchangeably. When a food label or calculator says \"Calories,\" it means kcal.\n\n So your 2,549 \"Calories\" BMR = 2,549 kcal, and your 400 \"calorie\" shake = 400 kcal. Same unit, confusing terminology.\n\n❯ so the k isnt 1000 like with any other unit in the metric system?\n\n⏺ The \"k\" does mean 1000, like always in metric.\n\n 1 kcal = 1000 cal ✓\n\n The problem is that nutritionists and the food industry started calling kilocalories just \"Calories\" (sometimes with a capital C) decades ago because the small calorie was too tiny to be practical for food.\n\n So it's not that the metric system is broken — it's that nutrition adopted sloppy shorthand that stuck. When your shake says \"400 calories,\" they really mean \"400 kilocalories\" but dropped the \"kilo\" part.\n\n It's genuinely bad terminology, and you're right to find it confusing.\n\n❯ insert profany here\n\n⏺ Justified. Blame early 20th century American nutritionists who decided \"kilocalorie\" was too many syllables.\n",
"date_published": "2026-01-25T19:39:57+02:00",
"url": "https://www.the-sprawl.blog/2026/01/25/til-ernhrungsfuzzies-sind-ernstzunehmen.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/24/gre-aus-dem-schlachthof-stuttgart.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/gg84vy4303m49pjblcctwrvb1op3jm17bwug5nib.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Grüße aus dem Schlachthof <a href=\"https://pixelfed.mayer.rocks/discover/tags/Stuttgart?src=hash\" title=\"#Stuttgart\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Stuttgart</a></p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/gg84vy4303m49pjblcctwrvb1op3jm17bwug5nib.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Grüße aus dem Schlachthof <a href=\"https://pixelfed.mayer.rocks/discover/tags/Stuttgart?src=hash\" title=\"#Stuttgart\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Stuttgart</a></p>\n",
"date_published": "2026-01-24T16:12:53+02:00",
"url": "https://www.the-sprawl.blog/2026/01/24/gre-aus-dem-schlachthof-stuttgart.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/24/annis-wilde-tierabenteuer-in-esslingen.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/4xfzxs59ohx0bcu0tnut8wueprr6iet6enypsyqo.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Annis wilde Tierabenteuer in <a href=\"https://pixelfed.mayer.rocks/discover/tags/Esslingen?src=hash\" title=\"#Esslingen\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Esslingen</a></p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/4xfzxs59ohx0bcu0tnut8wueprr6iet6enypsyqo.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Annis wilde Tierabenteuer in <a href=\"https://pixelfed.mayer.rocks/discover/tags/Esslingen?src=hash\" title=\"#Esslingen\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#Esslingen</a></p>\n",
"date_published": "2026-01-24T11:46:33+02:00",
"url": "https://www.the-sprawl.blog/2026/01/24/annis-wilde-tierabenteuer-in-esslingen.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/23/in-der-azurewelt-ist-heute.html",
"content_html": "<p>In der Azure-Welt ist heute wohl kein Sack Reis, sondern ein ganzes Datacenter (ungeplant) umgefallen. Respekt</p>\n",
"content_text": "In der Azure-Welt ist heute wohl kein Sack Reis, sondern ein ganzes Datacenter (ungeplant) umgefallen. Respekt\n",
"date_published": "2026-01-23T20:59:54+02:00",
"url": "https://www.the-sprawl.blog/2026/01/23/in-der-azurewelt-ist-heute.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/21/from-trakttv-to-orgmode-taking.html",
"title": "From Trakt.tv to Org-mode: Taking Control of My Watch History",
"content_html": "<p>I’ve been using <a href=\"https://trakt.tv\">Trakt.tv</a> to track my movies and TV shows for years. It’s great for automatic scrobbling and keeping a history, but I wanted something more personal—a way to see my media library in plain text that I could manage alongside my other notes in Emacs.</p>\n<p>So I built a simple Python script to convert my Trakt export into org-mode tables.</p>\n<h2 id=\"the-problem\">The Problem</h2>\n<p>Trakt is excellent at what it does, but:</p>\n<ul>\n<li>It’s a web app—I can’t access it offline or integrate it with my local workflow</li>\n<li>I wanted to see at a glance which shows I’ve dropped vs. which are still airing</li>\n<li>My watchlist was separate from my watch history, making it hard to see everything in one place</li>\n</ul>\n<h2 id=\"the-solution\">The Solution</h2>\n<p>The converter pulls data from a Trakt JSON export and generates clean org-mode files:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-org\" data-lang=\"org\"><span style=\"color:#e6db74\">| Name | IMDB | Last Episode | Progress | Status |</span>\n<span style=\"color:#e6db74\">|--------------+------+--------------+----------+----------|</span>\n<span style=\"color:#e6db74\">| Breaking Bad | IMDB | S05E16 | 62/62 | Complete |</span>\n<span style=\"color:#e6db74\">| Black Mirror | IMDB | S06E01 | 22/32 | Watching |</span>\n<span style=\"color:#e6db74\">| 30 Rock | IMDB | S04E22 | 80/138 | Dropped |</span>\n| Severance | IMDB | S00E00 | | Watchlist|\n</code></pre></div><p>The status column is the key feature. By fetching episode counts from TMDB, the script can tell me:</p>\n<ul>\n<li><strong>Complete</strong>: I’ve watched everything</li>\n<li><strong>Watching</strong>: Show is still airing, I’m caught up or working through it</li>\n<li><strong>Dropped</strong>: The show ended but I never finished it</li>\n<li><strong>Watchlist</strong>: Haven’t started yet</li>\n</ul>\n<p>Movies get a simpler treatment—just title, IMDB link, last watched date, and whether it’s watched or on my watchlist.</p>\n<h2 id=\"technical-details\">Technical Details</h2>\n<p>The stack is minimal:</p>\n<ul>\n<li>Python with <code>httpx</code> for API calls</li>\n<li><code>python-dotenv</code> for config</li>\n<li>TMDB API for episode counts (free tier, responses cached locally)</li>\n</ul>\n<p>The whole thing runs with <code>uv run convert.py</code> and generates three files: <code>movies.org</code>, <code>shows.org</code>, and <code>collection.org</code>.</p>\n<p>One nice touch: personal Trakt lists automatically exclude items that appear in the main files, so there’s no duplication.</p>\n<h2 id=\"whats-next\">What’s Next</h2>\n<p>For now, this is a one-way export. The org files are my read-only reference. But org-mode tables are easy to edit, so I could potentially:</p>\n<ul>\n<li>Add a “Notes” column for my thoughts on each show</li>\n<li>Use org-agenda to surface shows I should pick back up</li>\n<li>Build a simple sync back to Trakt (someday, maybe)</li>\n</ul>\n<p>The code is straightforward—about 400 lines of Python. Sometimes the best tool is the one you build yourself.</p>\n<hr>\n<p><em>The project is available on my <a href=\"https://forgejo.mayer.rocks/public/trakt-to-org\">https://forgejo.mayer.rocks/public/trakt-to-org</a> Feel free to adapt it for your own Trakt exports.</em></p>\n",
"content_text": "I've been using [Trakt.tv](https://trakt.tv) to track my movies and TV shows for years. It's great for automatic scrobbling and keeping a history, but I wanted something more personal—a way to see my media library in plain text that I could manage alongside my other notes in Emacs.\n\nSo I built a simple Python script to convert my Trakt export into org-mode tables.\n\n## The Problem\n\nTrakt is excellent at what it does, but:\n- It's a web app—I can't access it offline or integrate it with my local workflow\n- I wanted to see at a glance which shows I've dropped vs. which are still airing\n- My watchlist was separate from my watch history, making it hard to see everything in one place\n\n## The Solution\n\nThe converter pulls data from a Trakt JSON export and generates clean org-mode files:\n\n```org\n| Name | IMDB | Last Episode | Progress | Status |\n|--------------+------+--------------+----------+----------|\n| Breaking Bad | IMDB | S05E16 | 62/62 | Complete |\n| Black Mirror | IMDB | S06E01 | 22/32 | Watching |\n| 30 Rock | IMDB | S04E22 | 80/138 | Dropped |\n| Severance | IMDB | S00E00 | | Watchlist|\n```\nThe status column is the key feature. By fetching episode counts from TMDB, the script can tell me:\n- **Complete**: I've watched everything\n- **Watching**: Show is still airing, I'm caught up or working through it\n- **Dropped**: The show ended but I never finished it\n- **Watchlist**: Haven't started yet\n\nMovies get a simpler treatment—just title, IMDB link, last watched date, and whether it's watched or on my watchlist.\n\n## Technical Details\n\nThe stack is minimal:\n- Python with `httpx` for API calls\n- `python-dotenv` for config\n- TMDB API for episode counts (free tier, responses cached locally)\n\nThe whole thing runs with `uv run convert.py` and generates three files: `movies.org`, `shows.org`, and `collection.org`.\n\nOne nice touch: personal Trakt lists automatically exclude items that appear in the main files, so there's no duplication.\n\n## What's Next\n\nFor now, this is a one-way export. The org files are my read-only reference. But org-mode tables are easy to edit, so I could potentially:\n- Add a \"Notes\" column for my thoughts on each show\n- Use org-agenda to surface shows I should pick back up\n- Build a simple sync back to Trakt (someday, maybe)\n\nThe code is straightforward—about 400 lines of Python. Sometimes the best tool is the one you build yourself.\n\n---\n\n*The project is available on my https://forgejo.mayer.rocks/public/trakt-to-org Feel free to adapt it for your own Trakt exports.*\n",
"date_published": "2026-01-22T00:45:51+02:00",
"url": "https://www.the-sprawl.blog/2026/01/21/from-trakttv-to-orgmode-taking.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/21/heutige-news-irgendwo-in-der.html",
"content_html": "<p>Heutige News: irgendwo in der Schweiz ist ein Sack Reis umgefallen</p>\n",
"content_text": "Heutige News: irgendwo in der Schweiz ist ein Sack Reis umgefallen \n",
"date_published": "2026-01-21T19:21:06+02:00",
"url": "https://www.the-sprawl.blog/2026/01/21/heutige-news-irgendwo-in-der.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/20/etwasmitholz.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/flqdjmedcxupfpgybxkv4gayjg2pm13jaobpjn3o.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\"><a href=\"https://pixelfed.mayer.rocks/discover/tags/etwasmitholz?src=hash\" title=\"#etwasmitholz\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#etwasmitholz</a></p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/flqdjmedcxupfpgybxkv4gayjg2pm13jaobpjn3o.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\"><a href=\"https://pixelfed.mayer.rocks/discover/tags/etwasmitholz?src=hash\" title=\"#etwasmitholz\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#etwasmitholz</a></p>\n",
"date_published": "2026-01-20T20:36:33+02:00",
"url": "https://www.the-sprawl.blog/2026/01/20/etwasmitholz.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/20/portainer-vs-dockhand.html",
"title": "Portainer vs. Dockhand",
"content_html": "<p>Ich habe recht lange Portainer zur Verwaltung meiner kleinen Umgebung verwendet. Das ist ganz ok aber man merkt dass der Hersteller seine liebe Not hat bezahlende Kunden zu finden. Neben der Einschränkung der freien Version gab es gefühlt keine Weiterentwicklung. Dinge in dem Tool zu tun fühlt sich eher zäh an.</p>\n<p>Auftritt <a href=\"https://dockhand.pro/\">dockhand.pro</a>\nDockhand fühlt sich deutlich moderner an und ist auch schneller. Man findet sich sofort zurecht und kann Features problemlos nutzen.</p>\n<p>Die Installation und Migration der Container war in wenigen Stunden erledigt.</p>\n",
"content_text": "Ich habe recht lange Portainer zur Verwaltung meiner kleinen Umgebung verwendet. Das ist ganz ok aber man merkt dass der Hersteller seine liebe Not hat bezahlende Kunden zu finden. Neben der Einschränkung der freien Version gab es gefühlt keine Weiterentwicklung. Dinge in dem Tool zu tun fühlt sich eher zäh an. \n\nAuftritt [dockhand.pro](https://dockhand.pro/)\nDockhand fühlt sich deutlich moderner an und ist auch schneller. Man findet sich sofort zurecht und kann Features problemlos nutzen. \n\nDie Installation und Migration der Container war in wenigen Stunden erledigt. \n",
"date_published": "2026-01-20T15:14:58+02:00",
"url": "https://www.the-sprawl.blog/2026/01/20/portainer-vs-dockhand.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/18/sportheim-stein-am-kocher.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/ohsjgwgp1zxu61ll6tydrw0a1ckwa3lxuszo8tjo.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Sportheim Stein am Kocher</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/ohsjgwgp1zxu61ll6tydrw0a1ckwa3lxuszo8tjo.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Sportheim Stein am Kocher</p>\n",
"date_published": "2026-01-18T11:08:41+02:00",
"url": "https://www.the-sprawl.blog/2026/01/18/sportheim-stein-am-kocher.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/18/schnitzels-im-lautenschlager.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/xqhv3tsegevtgipsdibm9eldkwzq1xoyzqcvzpe9.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\"><a href=\"https://pixelfed.mayer.rocks/discover/tags/SchnitzelS?src=hash\" title=\"#SchnitzelS\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#SchnitzelS</a> im Lautenschlager</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2026/xqhv3tsegevtgipsdibm9eldkwzq1xoyzqcvzpe9.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\"><a href=\"https://pixelfed.mayer.rocks/discover/tags/SchnitzelS?src=hash\" title=\"#SchnitzelS\" class=\"u-url hashtag\" rel=\"external nofollow noopener\">#SchnitzelS</a> im Lautenschlager</p>\n",
"date_published": "2026-01-18T11:07:43+02:00",
"url": "https://www.the-sprawl.blog/2026/01/18/schnitzels-im-lautenschlager.html"
},
{
"id": "http://tabtwo.micro.blog/2026/01/02/euch-allen-ein-gutes-neues.html",
"content_html": "<p>Euch allen ein Gutes Neues Jahr 2026!</p>\n",
"content_text": "Euch allen ein Gutes Neues Jahr 2026!\n",
"date_published": "2026-01-02T09:51:01+02:00",
"url": "https://www.the-sprawl.blog/2026/01/02/euch-allen-ein-gutes-neues.html"
},
{
"id": "http://tabtwo.micro.blog/2025/12/23/its-nice-to-see-git.html",
"content_html": "<p>It’s nice to see git getting more and more used in bigger contexts like here at Debian: <a href=\"https://diziet.dreamwidth.org/20436.html\">diziet.dreamwidth.org/20436.htm…</a></p>\n",
"content_text": "It's nice to see git getting more and more used in bigger contexts like here at Debian: [diziet.dreamwidth.org/20436.htm...](https://diziet.dreamwidth.org/20436.html)\n",
"date_published": "2025-12-23T16:59:28+02:00",
"url": "https://www.the-sprawl.blog/2025/12/23/its-nice-to-see-git.html"
},
{
"id": "http://tabtwo.micro.blog/2025/12/21/die-zukunft-ist-schon-da.html",
"content_html": "<p>Die Zukunft ist schon da, sie ist nur ungleich verteilt. Und, ohne Altlasten lassen sich manche Dinge eben einfacher Umsetzen. <a href=\"https://www.nytimes.com/interactive/2025/12/17/climate/china-hefei-clean-energy-drones-evs-robots.html?rsrc=flt&smid=url-share\">www.nytimes.com/interacti…</a></p>\n",
"content_text": "Die Zukunft ist schon da, sie ist nur ungleich verteilt. Und, ohne Altlasten lassen sich manche Dinge eben einfacher Umsetzen. [www.nytimes.com/interacti...](https://www.nytimes.com/interactive/2025/12/17/climate/china-hefei-clean-energy-drones-evs-robots.html?rsrc=flt&smid=url-share)\n",
"date_published": "2025-12-21T11:24:31+02:00",
"url": "https://www.the-sprawl.blog/2025/12/21/die-zukunft-ist-schon-da.html"
},
{
"id": "http://tabtwo.micro.blog/2025/12/13/123323.html",
"title": "0.1.3",
"content_html": "<p dir=\"auto\"><a href=\"https://forgejo.mayer.rocks/public/org-review-checker/\" rel=\"nofollow\">https://forgejo.mayer.rocks/public/org-review-checker/</a> comes with these new features</p>\n<ul dir=\"auto\">\n<li>Forgejo workflow update-nextreview.yml for automated NextReview updates in org-mode repositories</li>\n<li>Workflow automatically runs update_next_review.py on push to main branch</li>\n<li>Smart commit handling: only commits and pushes if files were actually modified</li>\n<li>Prevents empty commits when no NextReview dates need updating</li>\n</ul>\n",
"content_text": "<p dir=\"auto\"><a href=\"https://forgejo.mayer.rocks/public/org-review-checker/\" rel=\"nofollow\">https://forgejo.mayer.rocks/public/org-review-checker/</a> comes with these new features</p>\n<ul dir=\"auto\">\n<li>Forgejo workflow update-nextreview.yml for automated NextReview updates in org-mode repositories</li>\n<li>Workflow automatically runs update_next_review.py on push to main branch</li>\n<li>Smart commit handling: only commits and pushes if files were actually modified</li>\n<li>Prevents empty commits when no NextReview dates need updating</li>\n</ul>\n",
"date_published": "2025-12-13T13:33:23+02:00",
"url": "https://www.the-sprawl.blog/2025/12/13/123323.html"
},
{
"id": "http://tabtwo.micro.blog/2025/12/13/111022.html",
"title": "0.1.2",
"content_html": "",
"content_text": "\n",
"date_published": "2025-12-13T12:10:22+02:00",
"url": "https://www.the-sprawl.blog/2025/12/13/111022.html"
},
{
"id": "http://tabtwo.micro.blog/2025/12/12/keeping-infrastructure-documentation-fresh-a.html",
"title": "Keeping Infrastructure Documentation Fresh: A Simple Tool for Org-Mode Users",
"content_html": "<p>I did a little vibe thingie.</p>\n<p>As network engineers and security managers, we face a constant challenge: keeping our documentation current. Whether it’s network diagrams, incident response plans, security policies, or configuration guides, documentation has a tendency to become outdated the moment we finish writing it.</p>\n<p>The consequences of stale documentation in critical infrastructure environments can be severe. An outdated firewall rule document might lead to misconfigurations. An old incident response plan might reference tools or procedures that no longer exist. A security policy that hasn’t been reviewed in two years might miss critical compliance requirements.</p>\n<p>But here’s the thing: we all know documentation needs regular reviews. We set good intentions. We even add review dates to our files. And then… life happens. Projects pile up. Tickets flood in. And before we know it, that quarterly review we planned six months ago is now hopelessly overdue.</p>\n<h2 id=\"the-problem-with-manual-tracking\">The Problem with Manual Tracking</h2>\n<p>If you’re using org-mode to manage your documentation (and if you’re reading this, chances are you do), you might already be tracking review dates in property drawers:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-org\" data-lang=\"org\">*<span style=\"font-weight:bold\"> Firewall Configuration Documentation</span>\n<span style=\"color:#75715e\">:PROPERTIES:\n</span><span style=\"color:#75715e\"></span><span style=\"color:#75715e\">:Created: 2024-01-15\n</span><span style=\"color:#75715e\">:Revisited: 2024-06-01\n</span><span style=\"color:#75715e\">:NextReview: 2024-09-01\n</span><span style=\"color:#75715e\">:ReviewCycle: 90\n</span><span style=\"color:#75715e\">:Status: Current\n</span><span style=\"color:#75715e\"></span><span style=\"color:#75715e\">:END:</span>\n</code></pre></div><p>This is great practice. The problem is: how do you actually track all these review dates across dozens or hundreds of documents? Do you manually check each file? Create calendar reminders for each document? Build complex org-agenda queries?</p>\n<h2 id=\"a-lightweight-solution\">A Lightweight Solution</h2>\n<p>This is why I created <strong>org-review-checker</strong> - a simple Python tool that scans your org files and tells you exactly which documents need attention.</p>\n<p>It does one thing well: it walks through your org file directories and checks the review status of every document. No complex setup, no database, no dependencies beyond Python’s standard library. Just point it at your documentation directory and get a clear report.</p>\n<h3 id=\"what-it-checks\">What It Checks</h3>\n<p>The tool looks for three key properties in your org headings or file headers:</p>\n<ul>\n<li><strong>Created</strong>: When was this document first written?</li>\n<li><strong>Revisited</strong>: When was it last reviewed?</li>\n<li><strong>NextReview</strong>: When should it be reviewed again?</li>\n</ul>\n<p>Based on these dates, it categorizes documents into:</p>\n<ol>\n<li><strong>Overdue reviews</strong> - Documents past their review date</li>\n<li><strong>Upcoming reviews</strong> - Documents due within the next 30 days</li>\n<li><strong>Missing properties</strong> - Documents that aren’t being tracked yet</li>\n<li><strong>Current</strong> - Documents that are up to date</li>\n</ol>\n<h3 id=\"real-world-output\">Real-World Output</h3>\n<p>Here’s what a typical report looks like:</p>\n<pre tabindex=\"0\"><code>================================================================================\r\nDOCUMENT REVIEW STATUS REPORT\r\n================================================================================\r\n\r\nFiles scanned: 23\r\nDocuments with missing properties: 5\r\nOverdue reviews: 3\r\nUpcoming reviews (next 30 days): 4\r\n\r\n⚠️ OVERDUE REVIEWS\r\n--------------------------------------------------------------------------------\r\n\r\n📄 network/firewall-rules.org\r\n • DMZ Firewall Configuration\r\n Due: 2024-09-01 (102 days overdue)\r\n Last reviewed: 2024-06-01\r\n\r\n📄 security/incident-response.org\r\n • DDoS Response Plan\r\n Due: 2024-11-01 (40 days overdue)\r\n Last reviewed: 2024-08-01\r\n\r\n❌ MISSING REVIEW PROPERTIES\r\n--------------------------------------------------------------------------------\r\n\r\n📄 policies/password-policy.org\r\n • Password Requirements\r\n Missing: Created, Revisited, NextReview\r\n\r\n📅 UPCOMING REVIEWS (Next 30 days)\r\n--------------------------------------------------------------------------------\r\n\r\n📄 network/topology.org\r\n • Network Diagram\r\n Due: 2025-01-05 (in 25 days)\r\n\r\n✅ 15 documents are current (reviews > 30 days away)\r\n</code></pre><p>Suddenly, you have visibility. You know exactly what needs attention and when.</p>\n<h2 id=\"practical-use-cases\">Practical Use Cases</h2>\n<h3 id=\"pre-audit-compliance-checks\">Pre-Audit Compliance Checks</h3>\n<p>Running quarterly security audits? Before the auditors arrive, scan your policy documentation:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-bash\" data-lang=\"bash\">uv run check_reviews.py /policies > audit_prep_report.txt\n</code></pre></div><p>You’ll immediately see which policies haven’t been reviewed recently and can address them before they become audit findings.</p>\n<h3 id=\"weekly-team-reports\">Weekly Team Reports</h3>\n<p>Add it to your cron jobs to get weekly reminders:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-bash\" data-lang=\"bash\"><span style=\"color:#ae81ff\">0</span> <span style=\"color:#ae81ff\">9</span> * * <span style=\"color:#ae81ff\">1</span> cd /docs <span style=\"color:#f92672\">&&</span> uv run check_reviews.py . | mail -s <span style=\"color:#e6db74\">"Doc Review Status"</span> team@example.com\n</code></pre></div><p>Every Monday morning, your team gets a clear picture of documentation health.</p>\n<h3 id=\"integration-with-existing-workflows\">Integration with Existing Workflows</h3>\n<p>Since the tool works with standard org-mode property drawers, it integrates seamlessly with your existing org-agenda setup. You can continue using your current workflow while adding automated compliance tracking.</p>\n<h2 id=\"a-bonus-git-history-integration\">A Bonus: Git History Integration</h2>\n<p>One challenge when starting to track documentation reviews is filling in the historical data. When was each document actually created?</p>\n<p>The included <code>set_created_dates.py</code> helper solves this by automatically setting the <code>Created</code> property based on your git history. It finds the first commit for each file and uses that date:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-bash\" data-lang=\"bash\"><span style=\"color:#75715e\"># Preview what will change</span>\nuv run set_created_dates.py --dry-run --directory ./docs\n\n<span style=\"color:#75715e\"># Apply the changes</span>\nuv run set_created_dates.py --directory ./docs\n</code></pre></div><p>This gives you historically accurate creation dates without manual entry.</p>\n<h2 id=\"design-philosophy\">Design Philosophy</h2>\n<p>The tool follows a few key principles:</p>\n<p><strong>Zero Dependencies</strong>: Uses only Python’s standard library. No pip install headaches, no version conflicts, no virtual environment issues to debug.</p>\n<p><strong>Read-Only by Default</strong>: It never modifies your files during checks. You stay in control of your documentation.</p>\n<p><strong>Flexible Structure</strong>: Works with both file-level properties (one review schedule per file) and heading-level properties (multiple reviewable sections per file). Use the <code>--header-only</code> flag if you prefer file-level tracking.</p>\n<p><strong>Plain Text</strong>: All data stays in your org files as plain text. No hidden databases, no proprietary formats. You can read and edit everything in Emacs.</p>\n<h2 id=\"who-is-this-for\">Who Is This For?</h2>\n<p>This tool is specifically designed for:</p>\n<ul>\n<li><strong>Network engineers</strong> managing infrastructure documentation</li>\n<li><strong>Security teams</strong> maintaining compliance policies</li>\n<li><strong>System administrators</strong> tracking configuration guides</li>\n<li><strong>IT managers</strong> ensuring knowledge bases stay current</li>\n<li>Anyone using org-mode for technical documentation who needs review compliance</li>\n</ul>\n<p>If you’re responsible for keeping critical documentation current and you use org-mode, this tool can help.</p>\n<h2 id=\"getting-started\">Getting Started</h2>\n<p>The tool is open source and available now. Installation is straightforward:</p>\n<div class=\"highlight\"><pre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-bash\" data-lang=\"bash\">git clone https://forgejo.mayer.rocks/public/org-review-checker.git\ncd org-review-checker\nuv run check_reviews.py /path/to/your/docs\n</code></pre></div><p>That’s it. No configuration files, no setup scripts, no database initialization.</p>\n<h2 id=\"looking-forward\">Looking Forward</h2>\n<p>Current plans include adding CSV/JSON export for integration with external systems, email notifications for overdue reviews, and iCal export for calendar integration. But the core philosophy remains: keep it simple, keep it focused, keep it useful.</p>\n<p>Documentation review compliance doesn’t have to be complicated. Sometimes you just need a tool that tells you what needs attention and gets out of your way.</p>\n<hr>\n<p><strong>Project</strong>: <a href=\"https://forgejo.mayer.rocks/public/org-review-checker\">org-review-checker on Forgejo</a>\n<strong>License</strong>: MIT\n<strong>Requirements</strong>: Python 3.8+, uv for dependency management</p>\n",
"content_text": "I did a little vibe thingie.\n\nAs network engineers and security managers, we face a constant challenge: keeping our documentation current. Whether it's network diagrams, incident response plans, security policies, or configuration guides, documentation has a tendency to become outdated the moment we finish writing it.\r\n\r\nThe consequences of stale documentation in critical infrastructure environments can be severe. An outdated firewall rule document might lead to misconfigurations. An old incident response plan might reference tools or procedures that no longer exist. A security policy that hasn't been reviewed in two years might miss critical compliance requirements.\r\n\r\nBut here's the thing: we all know documentation needs regular reviews. We set good intentions. We even add review dates to our files. And then... life happens. Projects pile up. Tickets flood in. And before we know it, that quarterly review we planned six months ago is now hopelessly overdue.\r\n\r\n## The Problem with Manual Tracking\r\n\r\nIf you're using org-mode to manage your documentation (and if you're reading this, chances are you do), you might already be tracking review dates in property drawers:\r\n\r\n```org\r\n* Firewall Configuration Documentation\r\n:PROPERTIES:\r\n:Created: 2024-01-15\r\n:Revisited: 2024-06-01\r\n:NextReview: 2024-09-01\r\n:ReviewCycle: 90\r\n:Status: Current\r\n:END:\r\n```\r\n\r\nThis is great practice. The problem is: how do you actually track all these review dates across dozens or hundreds of documents? Do you manually check each file? Create calendar reminders for each document? Build complex org-agenda queries?\r\n\r\n## A Lightweight Solution\r\n\r\nThis is why I created **org-review-checker** - a simple Python tool that scans your org files and tells you exactly which documents need attention.\r\n\r\nIt does one thing well: it walks through your org file directories and checks the review status of every document. No complex setup, no database, no dependencies beyond Python's standard library. Just point it at your documentation directory and get a clear report.\r\n\r\n### What It Checks\r\n\r\nThe tool looks for three key properties in your org headings or file headers:\r\n\r\n- **Created**: When was this document first written?\r\n- **Revisited**: When was it last reviewed?\r\n- **NextReview**: When should it be reviewed again?\r\n\r\nBased on these dates, it categorizes documents into:\r\n\r\n1. **Overdue reviews** - Documents past their review date\r\n2. **Upcoming reviews** - Documents due within the next 30 days\r\n3. **Missing properties** - Documents that aren't being tracked yet\r\n4. **Current** - Documents that are up to date\r\n\r\n### Real-World Output\r\n\r\nHere's what a typical report looks like:\r\n\r\n```\r\n================================================================================\r\nDOCUMENT REVIEW STATUS REPORT\r\n================================================================================\r\n\r\nFiles scanned: 23\r\nDocuments with missing properties: 5\r\nOverdue reviews: 3\r\nUpcoming reviews (next 30 days): 4\r\n\r\n⚠️ OVERDUE REVIEWS\r\n--------------------------------------------------------------------------------\r\n\r\n📄 network/firewall-rules.org\r\n • DMZ Firewall Configuration\r\n Due: 2024-09-01 (102 days overdue)\r\n Last reviewed: 2024-06-01\r\n\r\n📄 security/incident-response.org\r\n • DDoS Response Plan\r\n Due: 2024-11-01 (40 days overdue)\r\n Last reviewed: 2024-08-01\r\n\r\n❌ MISSING REVIEW PROPERTIES\r\n--------------------------------------------------------------------------------\r\n\r\n📄 policies/password-policy.org\r\n • Password Requirements\r\n Missing: Created, Revisited, NextReview\r\n\r\n📅 UPCOMING REVIEWS (Next 30 days)\r\n--------------------------------------------------------------------------------\r\n\r\n📄 network/topology.org\r\n • Network Diagram\r\n Due: 2025-01-05 (in 25 days)\r\n\r\n✅ 15 documents are current (reviews > 30 days away)\r\n```\r\n\r\nSuddenly, you have visibility. You know exactly what needs attention and when.\r\n\r\n## Practical Use Cases\r\n\r\n### Pre-Audit Compliance Checks\r\n\r\nRunning quarterly security audits? Before the auditors arrive, scan your policy documentation:\r\n\r\n```bash\r\nuv run check_reviews.py /policies > audit_prep_report.txt\r\n```\r\n\r\nYou'll immediately see which policies haven't been reviewed recently and can address them before they become audit findings.\r\n\r\n### Weekly Team Reports\r\n\r\nAdd it to your cron jobs to get weekly reminders:\r\n\r\n```bash\r\n0 9 * * 1 cd /docs && uv run check_reviews.py . | mail -s \"Doc Review Status\" team@example.com\r\n```\r\n\r\nEvery Monday morning, your team gets a clear picture of documentation health.\r\n\r\n### Integration with Existing Workflows\r\n\r\nSince the tool works with standard org-mode property drawers, it integrates seamlessly with your existing org-agenda setup. You can continue using your current workflow while adding automated compliance tracking.\r\n\r\n## A Bonus: Git History Integration\r\n\r\nOne challenge when starting to track documentation reviews is filling in the historical data. When was each document actually created?\r\n\r\nThe included `set_created_dates.py` helper solves this by automatically setting the `Created` property based on your git history. It finds the first commit for each file and uses that date:\r\n\r\n```bash\r\n# Preview what will change\r\nuv run set_created_dates.py --dry-run --directory ./docs\r\n\r\n# Apply the changes\r\nuv run set_created_dates.py --directory ./docs\r\n```\r\n\r\nThis gives you historically accurate creation dates without manual entry.\r\n\r\n## Design Philosophy\r\n\r\nThe tool follows a few key principles:\r\n\r\n**Zero Dependencies**: Uses only Python's standard library. No pip install headaches, no version conflicts, no virtual environment issues to debug.\r\n\r\n**Read-Only by Default**: It never modifies your files during checks. You stay in control of your documentation.\r\n\r\n**Flexible Structure**: Works with both file-level properties (one review schedule per file) and heading-level properties (multiple reviewable sections per file). Use the `--header-only` flag if you prefer file-level tracking.\r\n\r\n**Plain Text**: All data stays in your org files as plain text. No hidden databases, no proprietary formats. You can read and edit everything in Emacs.\r\n\r\n## Who Is This For?\r\n\r\nThis tool is specifically designed for:\r\n\r\n- **Network engineers** managing infrastructure documentation\r\n- **Security teams** maintaining compliance policies\r\n- **System administrators** tracking configuration guides\r\n- **IT managers** ensuring knowledge bases stay current\r\n- Anyone using org-mode for technical documentation who needs review compliance\r\n\r\nIf you're responsible for keeping critical documentation current and you use org-mode, this tool can help.\r\n\r\n## Getting Started\r\n\r\nThe tool is open source and available now. Installation is straightforward:\r\n\r\n```bash\r\ngit clone https://forgejo.mayer.rocks/public/org-review-checker.git\r\ncd org-review-checker\r\nuv run check_reviews.py /path/to/your/docs\r\n```\r\n\r\nThat's it. No configuration files, no setup scripts, no database initialization.\r\n\r\n## Looking Forward\r\n\r\nCurrent plans include adding CSV/JSON export for integration with external systems, email notifications for overdue reviews, and iCal export for calendar integration. But the core philosophy remains: keep it simple, keep it focused, keep it useful.\r\n\r\nDocumentation review compliance doesn't have to be complicated. Sometimes you just need a tool that tells you what needs attention and gets out of your way.\r\n\r\n---\r\n\r\n**Project**: [org-review-checker on Forgejo](https://forgejo.mayer.rocks/public/org-review-checker)\r\n**License**: MIT\r\n**Requirements**: Python 3.8+, uv for dependency management\r\n",
"date_published": "2025-12-12T14:36:58+02:00",
"url": "https://www.the-sprawl.blog/2025/12/12/keeping-infrastructure-documentation-fresh-a.html"
},
{
"id": "http://tabtwo.micro.blog/2025/12/12/075222.html",
"title": "0.1.1",
"content_html": "<p dir=\"auto\">Add helper script to set Created dates from git history</p>\n",
"content_text": "<p dir=\"auto\">Add helper script to set Created dates from git history</p>\n",
"date_published": "2025-12-12T08:52:22+02:00",
"url": "https://www.the-sprawl.blog/2025/12/12/075222.html"
},
{
"id": "http://tabtwo.micro.blog/2025/12/11/224454.html",
"title": "0.1.0",
"content_html": "<p dir=\"auto\">First release</p>\n",
"content_text": "<p dir=\"auto\">First release</p>\n",
"date_published": "2025-12-11T23:44:54+02:00",
"url": "https://www.the-sprawl.blog/2025/12/11/224454.html"
},
{
"id": "http://tabtwo.micro.blog/2025/12/05/zuckerwatte-und-bhnle-fahren-glckliche.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/vftpnwt279blxjmtw0tto52pob0r3nodckovtykc.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Zuckerwatte und Bähnle fahren - Glückliche Kinder auf dem Weihnachtsmarkt Öhringen</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/vftpnwt279blxjmtw0tto52pob0r3nodckovtykc.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Zuckerwatte und Bähnle fahren - Glückliche Kinder auf dem Weihnachtsmarkt Öhringen</p>\n",
"date_published": "2025-12-05T20:19:06+02:00",
"url": "https://www.the-sprawl.blog/2025/12/05/zuckerwatte-und-bhnle-fahren-glckliche.html"
},
{
"id": "http://tabtwo.micro.blog/2025/11/30/schwbisches-ramen.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/ltkiccfstimubsgmfjnkugnurvrbjdj9z4ipnafj.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Schwäbisches Ramen</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/ltkiccfstimubsgmfjnkugnurvrbjdj9z4ipnafj.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Schwäbisches Ramen</p>\n",
"date_published": "2025-11-30T15:06:43+02:00",
"url": "https://www.the-sprawl.blog/2025/11/30/schwbisches-ramen.html"
},
{
"id": "http://tabtwo.micro.blog/2025/11/17/experimenta-heilbronn.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/o7mk6khwjua4xrjfvqyohvhz5obtwsc0d0uelzlb.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Experimenta Heilbronn</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/o7mk6khwjua4xrjfvqyohvhz5obtwsc0d0uelzlb.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Experimenta Heilbronn</p>\n",
"date_published": "2025-11-17T14:18:48+02:00",
"url": "https://www.the-sprawl.blog/2025/11/17/experimenta-heilbronn.html"
},
{
"id": "http://tabtwo.micro.blog/2025/11/16/openai-the-new-york-times.html",
"content_html": "<p><a href=\"https://sherwood.news/power/openai-the-new-york-times-is-forcing-us-to-turn-over-20-million-chatgpt/\">OpenAI: The New York Times is forcing us to turn over 20 million ChatGPT conversations</a></p>\n<p>Copyright/Urheberrecht bleibt die Achillesferse der ganzen KI Thematik.</p>\n",
"content_text": "[OpenAI: The New York Times is forcing us to turn over 20 million ChatGPT conversations](https://sherwood.news/power/openai-the-new-york-times-is-forcing-us-to-turn-over-20-million-chatgpt/)\n\nCopyright/Urheberrecht bleibt die Achillesferse der ganzen KI Thematik. \n",
"date_published": "2025-11-16T12:19:20+02:00",
"url": "https://www.the-sprawl.blog/2025/11/16/openai-the-new-york-times.html"
},
{
"id": "http://tabtwo.micro.blog/2025/11/02/quittenbrot-trockung.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/prf3op56zfky6ix5ihlbzdvipgv4dyehepzlc5wi.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Quittenbrot Trockung</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/prf3op56zfky6ix5ihlbzdvipgv4dyehepzlc5wi.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Quittenbrot Trockung</p>\n",
"date_published": "2025-11-02T20:31:11+02:00",
"url": "https://www.the-sprawl.blog/2025/11/02/quittenbrot-trockung.html"
},
{
"id": "http://tabtwo.micro.blog/2025/10/31/quittenbrot-in-the-making.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/ewdkzeleqgstcvo9q9k3lp4uwqhf1byb5ozrq9im.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Quittenbrot in the making</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/ewdkzeleqgstcvo9q9k3lp4uwqhf1byb5ozrq9im.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Quittenbrot in the making</p>\n",
"date_published": "2025-10-31T16:35:32+02:00",
"url": "https://www.the-sprawl.blog/2025/10/31/quittenbrot-in-the-making.html"
},
{
"id": "http://tabtwo.micro.blog/2025/10/26/watched-shaun-of-the-dead.html",
"content_html": "<p>Watched: <a href=\"https://www.themoviedb.org/movie/747\">Shaun of the Dead</a> 🍿</p>\n<p>Ein Klassiker, der auch gut gealtert ist.</p>\n",
"content_text": "Watched: [Shaun of the Dead](https://www.themoviedb.org/movie/747) 🍿\n\nEin Klassiker, der auch gut gealtert ist.\n",
"date_published": "2025-10-27T00:36:15+02:00",
"url": "https://www.the-sprawl.blog/2025/10/26/watched-shaun-of-the-dead.html"
},
{
"id": "http://tabtwo.micro.blog/2025/10/26/quittengelee-richtig-lecker.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/h6cpydx2drvltdbqgtt3hykapd02yhexiyqi2ofj.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Quittengelee, richtig lecker</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/h6cpydx2drvltdbqgtt3hykapd02yhexiyqi2ofj.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Quittengelee, richtig lecker</p>\n",
"date_published": "2025-10-26T21:12:57+02:00",
"url": "https://www.the-sprawl.blog/2025/10/26/quittengelee-richtig-lecker.html"
},
{
"id": "http://tabtwo.micro.blog/2025/10/21/erster-selbstgemachter-apfelsaft.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/hbbv5pjijuhdtrwngdwcbikilr4j9okcflkqzchk.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">erster, selbstgemachter Apfelsaft</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/hbbv5pjijuhdtrwngdwcbikilr4j9okcflkqzchk.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">erster, selbstgemachter Apfelsaft</p>\n",
"date_published": "2025-10-21T19:14:03+02:00",
"url": "https://www.the-sprawl.blog/2025/10/21/erster-selbstgemachter-apfelsaft.html"
},
{
"id": "http://tabtwo.micro.blog/2025/10/21/atombombensicheres-internet-das-hrt-man.html",
"content_html": "<p>Atombombensicheres Internet, das hört man ja immer wenn es um die Anfänge des Internetzes geht. Was das aber auch bedeuted sieht man auf einem der Bilder in diesem Beitrag zum Norad Combat Center welches of in Filmen vorkommt. Ungefähr in der Mitte sieht man eine Antenne für eine Funkverbindung ähnlich einer Satelittenschüssel. Allein 60 Tonnen Stahl sind da verbaut damt diese Antenne die Druckwelle einer Atombombe übersteht. Hochverfügbarkeit ist hart, durfte gestern mal wieder AWS lernen. <a href=\"https://flashbak.com/norad-cheyenne-mountain-combat-center-478804/\">flashbak.com/norad-che…</a></p>\n",
"content_text": "Atombombensicheres Internet, das hört man ja immer wenn es um die Anfänge des Internetzes geht. Was das aber auch bedeuted sieht man auf einem der Bilder in diesem Beitrag zum Norad Combat Center welches of in Filmen vorkommt. Ungefähr in der Mitte sieht man eine Antenne für eine Funkverbindung ähnlich einer Satelittenschüssel. Allein 60 Tonnen Stahl sind da verbaut damt diese Antenne die Druckwelle einer Atombombe übersteht. Hochverfügbarkeit ist hart, durfte gestern mal wieder AWS lernen. [flashbak.com/norad-che...](https://flashbak.com/norad-cheyenne-mountain-combat-center-478804/)\n",
"date_published": "2025-10-21T09:42:39+02:00",
"url": "https://www.the-sprawl.blog/2025/10/21/atombombensicheres-internet-das-hrt-man.html"
},
{
"id": "http://tabtwo.micro.blog/2025/10/19/watched-avengers-infinity-war-and.html",
"content_html": "<p>Watched: <a href=\"https://www.themoviedb.org/movie/299536\">Avengers: Infinity War</a> 🍿 and I did not like it</p>\n",
"content_text": "Watched: [Avengers: Infinity War](https://www.themoviedb.org/movie/299536) 🍿 and I did not like it\n",
"date_published": "2025-10-19T22:50:45+02:00",
"url": "https://www.the-sprawl.blog/2025/10/19/watched-avengers-infinity-war-and.html"
},
{
"id": "http://tabtwo.micro.blog/2025/10/18/wilhelma.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/5mtnvdr43joek20kcpfa7jy6zu7jek8qh3prrcnz.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Wilhelma</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/5mtnvdr43joek20kcpfa7jy6zu7jek8qh3prrcnz.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Wilhelma</p>\n",
"date_published": "2025-10-18T13:51:05+02:00",
"url": "https://www.the-sprawl.blog/2025/10/18/wilhelma.html"
},
{
"id": "http://tabtwo.micro.blog/2025/10/16/schnitzelknig-west-stuttgart.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/fzklddcgch4b38qklcwv9z6bfzmsygmqnsxbyvoh.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Schnitzelkönig West, Stuttgart</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/fzklddcgch4b38qklcwv9z6bfzmsygmqnsxbyvoh.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Schnitzelkönig West, Stuttgart</p>\n",
"date_published": "2025-10-16T18:41:49+02:00",
"url": "https://www.the-sprawl.blog/2025/10/16/schnitzelknig-west-stuttgart.html"
},
{
"id": "http://tabtwo.micro.blog/2025/10/05/heute-mal-maronen.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/pm12an2d0onxqggfhrnathlqwty9zfyfdqdhznj6.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Heute mal Maronen</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/pm12an2d0onxqggfhrnathlqwty9zfyfdqdhznj6.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Heute mal Maronen</p>\n",
"date_published": "2025-10-05T14:22:29+02:00",
"url": "https://www.the-sprawl.blog/2025/10/05/heute-mal-maronen.html"
},
{
"id": "http://tabtwo.micro.blog/2025/10/04/goldglnzender-rosenkfer-hat-uns-heute.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/utkwu1fpqpexrux4qdq3wuzpqfnloz6x3rjjso0k.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Goldglänzender Rosenkäfer, hat uns heute im Garten besucht. Wunderschöner grüngoldener Käfer.</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/utkwu1fpqpexrux4qdq3wuzpqfnloz6x3rjjso0k.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Goldglänzender Rosenkäfer, hat uns heute im Garten besucht. Wunderschöner grüngoldener Käfer.</p>\n",
"date_published": "2025-10-04T18:25:12+02:00",
"url": "https://www.the-sprawl.blog/2025/10/04/goldglnzender-rosenkfer-hat-uns-heute.html"
},
{
"id": "http://tabtwo.micro.blog/2025/09/30/back-to-the-basics.html",
"title": "Back to the basics",
"content_html": "<p>*** Start portmapper for RPC service, OK to fail if already running\n*** booting idled ***\n*** Start client/server ***</p>\n<p>PiDP-11 FP 2023</p>\n<p>PDP-11 simulator V4.0-0 Current REALCONS build Sep 30 2025\nDisabling XQ\nSearching realcons controller “11/70” …\nConnecting to host localhost …</p>\n<h2 id=\"pidp-1170-boot-menu---set-sr-switches-depress-address-rotary-switch-to-reboot\">PiDP-11/70 boot menu - Set SR switches, depress address rotary switch to reboot</h2>\n<h2 id=\"0003----rt11----0106----unix6---1000----nankervis\">0000 idled 0004 dos11 0107 unix7 1001 idled\n0001 rsx11mplus 0102 211bsd 0113 sysiii 1002 blinky\n0002 rsts7 0105 unix5 0115 sysv\n0003 rt11 0106 unix6 1000 nankervis</h2>\n<h2 id=\"now-running-idled---set-sr0-7-for-desired-front-panel-patterns\">Now running IDLED - set SR0-7 for desired front panel patterns</h2>\n<p>Work in progress, hier ist die Seite zum Projekt: <a href=\"https://obsolescence.dev/pidp-11-building-instructions.html\">obsolescence.dev/pidp-11-b…</a></p>\n",
"content_text": "*** Start portmapper for RPC service, OK to fail if already running\n*** booting idled ***\n*** Start client/server ***\n\nPiDP-11 FP 2023\n\nPDP-11 simulator V4.0-0 Current REALCONS build Sep 30 2025\nDisabling XQ\nSearching realcons controller \"11/70\" ...\nConnecting to host localhost ...\n\n\n\nPiDP-11/70 boot menu - Set SR switches, depress address rotary switch to reboot\n-------------------------------------------------------------------------------\n0000 idled 0004 dos11 0107 unix7 1001 idled\n0001 rsx11mplus 0102 211bsd 0113 sysiii 1002 blinky\n0002 rsts7 0105 unix5 0115 sysv\n0003 rt11 0106 unix6 1000 nankervis\n-------------------------------------------------------------------------------\n\nNow running IDLED - set SR0-7 for desired front panel patterns\n-------------------------------------------------------------------------------\n\n\nWork in progress, hier ist die Seite zum Projekt: [obsolescence.dev/pidp-11-b...](https://obsolescence.dev/pidp-11-building-instructions.html)\n",
"date_published": "2025-09-30T00:39:17+02:00",
"url": "https://www.the-sprawl.blog/2025/09/30/back-to-the-basics.html"
},
{
"id": "http://tabtwo.micro.blog/2025/09/29/ist-ja-nicht-so-dass.html",
"content_html": "<p>Ist ja nicht so, dass Siri schon immer schlecht war, am Anfang war das sogar recht eindrucksvoll. Das Problem ist, dass Siri jetzt im Vergleich zu den aktuellen Tools ein absoluter Witz ist.</p>\n",
"content_text": "Ist ja nicht so, dass Siri schon immer schlecht war, am Anfang war das sogar recht eindrucksvoll. Das Problem ist, dass Siri jetzt im Vergleich zu den aktuellen Tools ein absoluter Witz ist. \n",
"date_published": "2025-09-29T18:00:08+02:00",
"url": "https://www.the-sprawl.blog/2025/09/29/ist-ja-nicht-so-dass.html"
},
{
"id": "http://tabtwo.micro.blog/2025/09/26/ikea.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/lzgfiu7pnkcndjiuhlylwnc78bmlxxwexh2ycomx.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Ikea</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/lzgfiu7pnkcndjiuhlylwnc78bmlxxwexh2ycomx.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Ikea</p>\n",
"date_published": "2025-09-26T16:40:24+02:00",
"url": "https://www.the-sprawl.blog/2025/09/26/ikea.html"
},
{
"id": "http://tabtwo.micro.blog/2025/09/20/kaum-tage-bis-lars-christbaum.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/tbmhy78o4xiaxw9q1fc5on0kpqlqdzczhy72wzdn.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">kaum 100 Tage bis Lars Christbaum</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/tbmhy78o4xiaxw9q1fc5on0kpqlqdzczhy72wzdn.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">kaum 100 Tage bis Lars Christbaum</p>\n",
"date_published": "2025-09-20T15:24:40+02:00",
"url": "https://www.the-sprawl.blog/2025/09/20/kaum-tage-bis-lars-christbaum.html"
},
{
"id": "http://tabtwo.micro.blog/2025/09/17/noch-was-fr-die-bingokarte.html",
"content_html": "<p>Noch was für die Bingokarte: Sonnenaktivität nimmt unerwartet zu <a href=\"https://www.sciencealert.com/our-sun-is-becoming-more-active-and-nasa-doesnt-know-why\">www.sciencealert.com/our-sun-i…</a></p>\n",
"content_text": "Noch was für die Bingokarte: Sonnenaktivität nimmt unerwartet zu [www.sciencealert.com/our-sun-i...](https://www.sciencealert.com/our-sun-is-becoming-more-active-and-nasa-doesnt-know-why)\n",
"date_published": "2025-09-17T10:36:09+02:00",
"url": "https://www.the-sprawl.blog/2025/09/17/noch-was-fr-die-bingokarte.html"
},
{
"id": "http://tabtwo.micro.blog/2025/09/14/woooooooooopp-klack-wooooo-klack-klack.html",
"content_html": "<p>Woooooooooopp klack wooooo klack klack wooooooooo klack woo klack klack woooooooooooo</p>\n<p>#staubsaugenmitkindern</p>\n",
"content_text": "Woooooooooopp klack wooooo klack klack wooooooooo klack woo klack klack woooooooooooo\n\n#staubsaugenmitkindern\n",
"date_published": "2025-09-14T17:34:02+02:00",
"url": "https://www.the-sprawl.blog/2025/09/14/woooooooooopp-klack-wooooo-klack-klack.html"
},
{
"id": "http://tabtwo.micro.blog/2025/09/13/motorman-run.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/obvdrfoudjwvx7oduenjwj14kp2mob0rnbkmunfq.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Motorman Run 2025</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/obvdrfoudjwvx7oduenjwj14kp2mob0rnbkmunfq.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Motorman Run 2025</p>\n",
"date_published": "2025-09-13T14:24:58+02:00",
"url": "https://www.the-sprawl.blog/2025/09/13/motorman-run.html"
},
{
"id": "http://tabtwo.micro.blog/2025/09/09/aus-der-abteilung-der-klimawandel.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/h6esefz651r6ulgakmkvjyg7kmsikeyrwfgz2czs.jpg\" alt=\"\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/jmzva0uac5fakdb81hb7wawuadvg2blonebnlybu.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Aus der Abteilung „der Klimawandel ist sehr real“ heute: Bananen blühen in Süddeutschland im Freien (Landkreis Heilbronn)</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/h6esefz651r6ulgakmkvjyg7kmsikeyrwfgz2czs.jpg\" alt=\"\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/jmzva0uac5fakdb81hb7wawuadvg2blonebnlybu.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Aus der Abteilung „der Klimawandel ist sehr real“ heute: Bananen blühen in Süddeutschland im Freien (Landkreis Heilbronn)</p>\n",
"date_published": "2025-09-09T12:41:03+02:00",
"url": "https://www.the-sprawl.blog/2025/09/09/aus-der-abteilung-der-klimawandel.html"
},
{
"id": "http://tabtwo.micro.blog/2025/08/31/sausia-zucchini-kuchen.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/g28b0qztbwuxltzpn4mvletnnzntmcxj6uzqzf2p.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Sausia!! (Zucchini Kuchen)</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/g28b0qztbwuxltzpn4mvletnnzntmcxj6uzqzf2p.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Sausia!! (Zucchini Kuchen)</p>\n",
"date_published": "2025-08-31T10:19:44+02:00",
"url": "https://www.the-sprawl.blog/2025/08/31/sausia-zucchini-kuchen.html"
},
{
"id": "http://tabtwo.micro.blog/2025/08/15/raubtierftterung.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/vs1udjlbjzpe4siuoob0r7kb43gzl4l1l2s2z1p1.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Raubtierfütterung</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/vs1udjlbjzpe4siuoob0r7kb43gzl4l1l2s2z1p1.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Raubtierfütterung</p>\n",
"date_published": "2025-08-15T17:31:56+02:00",
"url": "https://www.the-sprawl.blog/2025/08/15/raubtierftterung.html"
},
{
"id": "http://tabtwo.micro.blog/2025/08/05/selbstgemachte-rouladen-mit-kartoffelklsen.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/snpjltppttdpl0npcmwofuemwtoiqskaubkbyuai.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Selbstgemachte Rouladen mit Kartoffelklösen</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/snpjltppttdpl0npcmwofuemwtoiqskaubkbyuai.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Selbstgemachte Rouladen mit Kartoffelklösen</p>\n",
"date_published": "2025-08-05T20:40:55+02:00",
"url": "https://www.the-sprawl.blog/2025/08/05/selbstgemachte-rouladen-mit-kartoffelklsen.html"
},
{
"id": "http://tabtwo.micro.blog/2025/08/01/aus-der-abteilung-ki-fails.html",
"content_html": "<p>Aus der Abteilung KI Fails. Heute: Sprachen sind immer ein Problem</p>\n<p><img src=\"https://www.the-sprawl.blog/uploads/2025/image1.jpg\" alt=\"\"></p>\n",
"content_text": "\nAus der Abteilung KI Fails. Heute: Sprachen sind immer ein Problem\n\n\n",
"date_published": "2025-08-01T15:24:06+02:00",
"url": "https://www.the-sprawl.blog/2025/08/01/aus-der-abteilung-ki-fails.html"
},
{
"id": "http://tabtwo.micro.blog/2025/07/22/rip.html",
"content_html": "<p>RIP 🦇</p>\n",
"content_text": "RIP 🦇\n",
"date_published": "2025-07-22T20:43:26+02:00",
"url": "https://www.the-sprawl.blog/2025/07/22/rip.html"
},
{
"id": "http://tabtwo.micro.blog/2025/07/20/lonelyday-von-bill-withers-ich.html",
"content_html": "<p>LonelyDay von Bill Withers - Ich dachte lange er singt von Germaneeeeeeeeeeeeeeeeeyyyyyyyyy</p>\n",
"content_text": "LonelyDay von Bill Withers - Ich dachte lange er singt von Germaneeeeeeeeeeeeeeeeeyyyyyyyyy \n",
"date_published": "2025-07-20T15:20:36+02:00",
"url": "https://www.the-sprawl.blog/2025/07/20/lonelyday-von-bill-withers-ich.html"
},
{
"id": "http://tabtwo.micro.blog/2025/07/19/regenbogen.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/a4qdukr2khwl0xxsaagk4w6po360cqognkb7yeh3.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Regenbogen</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/a4qdukr2khwl0xxsaagk4w6po360cqognkb7yeh3.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Regenbogen</p>\n",
"date_published": "2025-07-19T20:57:40+02:00",
"url": "https://www.the-sprawl.blog/2025/07/19/regenbogen.html"
},
{
"id": "http://tabtwo.micro.blog/2025/07/13/spione-sind-noch-immer-unterwegs.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/121gdujccmzml6c7a3neidiyom5p3weaafky1ufn.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Spione sind noch immer unterwegs</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/121gdujccmzml6c7a3neidiyom5p3weaafky1ufn.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Spione sind noch immer unterwegs</p>\n",
"date_published": "2025-07-13T20:32:48+02:00",
"url": "https://www.the-sprawl.blog/2025/07/13/spione-sind-noch-immer-unterwegs.html"
},
{
"id": "http://tabtwo.micro.blog/2025/07/13/wildpark-ab-in-den-wald.html",
"content_html": "<p>Wildpark. <a href=\"http://maps.apple.com/?ll=49.467831,9.797069\">📍</a></p>\n<p>Ab in den Wald und Ziegen füttern</p>\n",
"content_text": "Wildpark. [📍](http://maps.apple.com/?ll=49.467831,9.797069)\n\nAb in den Wald und Ziegen füttern\n",
"date_published": "2025-07-13T15:06:44+02:00",
"url": "https://www.the-sprawl.blog/2025/07/13/wildpark-ab-in-den-wald.html"
},
{
"id": "http://tabtwo.micro.blog/2025/06/26/des-bruttoinlandsprodukt-bip-schn-dass.html",
"title": "Nato-Milliarden",
"content_html": "<p>5% des Bruttoinlandsprodukt (BIP) … schön dass da immer von Prozenten geredet wird, das sit ja nur ne kleine Zahl und was das Bip ist wissen auch nur die wenigsten.</p>\n<p>Laut Quelle <a href=\"https://de.statista.com/statistik/daten/studie/1251/umfrage/entwicklung-des-bruttoinlandsprodukts-seit-dem-jahr-1991/\">Statista</a> war das BiP für Deutschland in 2024 stolze 4.305,3 Milliarden.</p>\n<p>Davon dann 5% sind fucking 215 Milliarden.</p>\n<p>Zum Vergleich, der Bundeshaushalt 2015 von Deutschland sind 489 Milliarden, also ein bisschen mehr als das doppelte. Davon 53 Milliarden für Verteidigung. <a href=\"https://www.finanzfluss.de/bundeshaushalt-einnahmen-ausgaben/\">Hier</a> mal eine Aufstellung.</p>\n<p>D.h. das Vierfache der aktuellen Verteidungsausgaben und bisschen weniger als die Hälfte des aktuellen Haushaltes wären dann diese 5%</p>\n<p>Nur mal so zur Einordnung dieser kleine Steigerung von 3,5 auf 5%</p>\n",
"content_text": "5% des Bruttoinlandsprodukt (BIP) ... schön dass da immer von Prozenten geredet wird, das sit ja nur ne kleine Zahl und was das Bip ist wissen auch nur die wenigsten.\n\nLaut Quelle [Statista](https://de.statista.com/statistik/daten/studie/1251/umfrage/entwicklung-des-bruttoinlandsprodukts-seit-dem-jahr-1991/) war das BiP für Deutschland in 2024 stolze 4.305,3 Milliarden. \n\nDavon dann 5% sind fucking 215 Milliarden.\n\nZum Vergleich, der Bundeshaushalt 2015 von Deutschland sind 489 Milliarden, also ein bisschen mehr als das doppelte. Davon 53 Milliarden für Verteidigung. [Hier](https://www.finanzfluss.de/bundeshaushalt-einnahmen-ausgaben/) mal eine Aufstellung.\n\nD.h. das Vierfache der aktuellen Verteidungsausgaben und bisschen weniger als die Hälfte des aktuellen Haushaltes wären dann diese 5%\n\nNur mal so zur Einordnung dieser kleine Steigerung von 3,5 auf 5%\n",
"date_published": "2025-06-26T09:17:55+02:00",
"url": "https://www.the-sprawl.blog/2025/06/26/des-bruttoinlandsprodukt-bip-schn-dass.html"
},
{
"id": "http://tabtwo.micro.blog/2025/06/21/playmobil-land.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/jt5088bs2rxxo6mwk0yyqccn6y3bcv4xg3jader1.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Playmobil Land</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/jt5088bs2rxxo6mwk0yyqccn6y3bcv4xg3jader1.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Playmobil Land</p>\n",
"date_published": "2025-06-21T12:46:13+02:00",
"url": "https://www.the-sprawl.blog/2025/06/21/playmobil-land.html"
},
{
"id": "http://tabtwo.micro.blog/2025/06/15/die-welle-in-acryl.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/rmilmogwcxaz9uydlhziubcudg5wlpuecs9wwofk.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Die Welle in Acryl</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/rmilmogwcxaz9uydlhziubcudg5wlpuecs9wwofk.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Die Welle in Acryl</p>\n",
"date_published": "2025-06-15T11:37:42+02:00",
"url": "https://www.the-sprawl.blog/2025/06/15/die-welle-in-acryl.html"
},
{
"id": "http://tabtwo.micro.blog/2025/06/14/hoftheater-hringen-gut-essen-geburtstag.html",
"content_html": "<p>Hoftheater Öhringen. <a href=\"http://maps.apple.com/?ll=49.197531,9.503365\">📍</a></p>\n<p>Gut essen + Geburtstag feiern</p>\n<p><img src=\"https://www.the-sprawl.blog/uploads/2025/image-20250614-175418-0f549d45.jpg\" alt=\"\"></p>\n",
"content_text": "Hoftheater Öhringen. [📍](http://maps.apple.com/?ll=49.197531,9.503365)\n\nGut essen + Geburtstag feiern\n\n\n",
"date_published": "2025-06-14T17:55:15+02:00",
"url": "https://www.the-sprawl.blog/2025/06/14/hoftheater-hringen-gut-essen-geburtstag.html"
},
{
"id": "http://tabtwo.micro.blog/2025/06/07/wochenmarkt-zuffenhausen-ab-zum-olivendealer.html",
"content_html": "<p>Wochenmarkt Zuffenhausen. <a href=\"http://maps.apple.com/?ll=48.830379,9.177573\">📍</a></p>\n<p>Ab zum Olivendealer</p>\n",
"content_text": "Wochenmarkt Zuffenhausen. [📍](http://maps.apple.com/?ll=48.830379,9.177573)\n\nAb zum Olivendealer\n",
"date_published": "2025-06-07T11:49:16+02:00",
"url": "https://www.the-sprawl.blog/2025/06/07/wochenmarkt-zuffenhausen-ab-zum-olivendealer.html"
},
{
"id": "http://tabtwo.micro.blog/2025/06/05/das-gerber-parkhaus-willkommen-in.html",
"content_html": "<p>Das Gerber. <a href=\"http://maps.apple.com/?ll=48.771998,9.172699\">📍</a></p>\n<p>Parkhaus 24€, willkommen in Stuttgart</p>\n",
"content_text": "Das Gerber. [📍](http://maps.apple.com/?ll=48.771998,9.172699)\n\nParkhaus 24€, willkommen in Stuttgart \n",
"date_published": "2025-06-05T18:47:22+02:00",
"url": "https://www.the-sprawl.blog/2025/06/05/das-gerber-parkhaus-willkommen-in.html"
},
{
"id": "http://tabtwo.micro.blog/2025/06/05/harrys-kaffeersterei-erst-mal-kaffee.html",
"content_html": "<p>Harry´s Kaffeerösterei. <a href=\"http://maps.apple.com/?ll=48.773480,9.177908\">📍</a></p>\n<p>Erst mal Kaffee</p>\n<p><img src=\"https://www.the-sprawl.blog/uploads/2025/image-20250605-184539-093366b5.jpg\" alt=\"\"></p>\n",
"content_text": "Harry´s Kaffeerösterei. [📍](http://maps.apple.com/?ll=48.773480,9.177908)\n\nErst mal Kaffee\n\n\n",
"date_published": "2025-06-05T18:45:53+02:00",
"url": "https://www.the-sprawl.blog/2025/06/05/harrys-kaffeersterei-erst-mal-kaffee.html"
},
{
"id": "http://tabtwo.micro.blog/2025/06/05/harrys-kaffeersterei-jetzt-nen-kaffee.html",
"content_html": "<p>Harry´s Kaffeerösterei. <a href=\"http://maps.apple.com/?ll=48.773480,9.177908\">📍</a></p>\n<p>Jetzt nen Kaffee</p>\n<p><img src=\"https://www.the-sprawl.blog/uploads/2025/image-20250605-171126-7689ca27.jpg\" alt=\"\"></p>\n",
"content_text": "Harry´s Kaffeerösterei. [📍](http://maps.apple.com/?ll=48.773480,9.177908)\n\n\nJetzt nen Kaffee\n\n\n",
"date_published": "2025-06-05T17:11:39+02:00",
"url": "https://www.the-sprawl.blog/2025/06/05/harrys-kaffeersterei-jetzt-nen-kaffee.html"
},
{
"id": "http://tabtwo.micro.blog/2025/06/05/tialini-der-stammvietnamese-hatte-leider.html",
"content_html": "<p>Tialini. <a href=\"http://maps.apple.com/?ll=48.780355,9.177752\">📍</a></p>\n<p>Der Stamm-Vietnamese hatte leider zu.</p>\n<p><img src=\"https://www.the-sprawl.blog/uploads/2025/image-20250605-151857-3ae2e4ae.jpg\" alt=\"Pizza\"></p>\n",
"content_text": "Tialini. [📍](http://maps.apple.com/?ll=48.780355,9.177752)\n\n\nDer Stamm-Vietnamese hatte leider zu.\n\n\n",
"date_published": "2025-06-05T15:19:16+02:00",
"url": "https://www.the-sprawl.blog/2025/06/05/tialini-der-stammvietnamese-hatte-leider.html"
},
{
"id": "http://tabtwo.micro.blog/2025/05/30/das-ist-sehr-wahrscheinlich-eine.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/86p1pbhvsasjkfckn0p60aoubb7gxtrqio22q7xp.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Das ist sehr wahrscheinlich eine Edle Kugelspinne, siehe <a href=\"https://de.wikipedia.org/wiki/Edle_Kugelspinne\" rel=\"external nofollow noopener\" target=\"_blank\">https://de.wikipedia.org/wiki/Edle_Kugelspinne</a><br />\n<br />\nNicht auf Madeira sondern in der Nähe von Heilbronn zuhause</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/86p1pbhvsasjkfckn0p60aoubb7gxtrqio22q7xp.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Das ist sehr wahrscheinlich eine Edle Kugelspinne, siehe <a href=\"https://de.wikipedia.org/wiki/Edle_Kugelspinne\" rel=\"external nofollow noopener\" target=\"_blank\">https://de.wikipedia.org/wiki/Edle_Kugelspinne</a><br />\n<br />\nNicht auf Madeira sondern in der Nähe von Heilbronn zuhause</p>\n",
"date_published": "2025-05-30T15:04:31+02:00",
"url": "https://www.the-sprawl.blog/2025/05/30/das-ist-sehr-wahrscheinlich-eine.html"
},
{
"id": "http://tabtwo.micro.blog/2025/05/28/menschen-die-ihr-geld-mit.html",
"content_html": "<p>Menschen, die ihr Geld mit dem kürzen von Liedern fürs Radio verdienen, für die ist auch ein spezieller Platz in der Hölle reserviert.</p>\n",
"content_text": "Menschen, die ihr Geld mit dem kürzen von Liedern fürs Radio verdienen, für die ist auch ein spezieller Platz in der Hölle reserviert. \n",
"date_published": "2025-05-28T09:29:47+02:00",
"url": "https://www.the-sprawl.blog/2025/05/28/menschen-die-ihr-geld-mit.html"
},
{
"id": "http://tabtwo.micro.blog/2025/05/24/khners-besen-heute-mal-spargel.html",
"content_html": "<p>Kühners Besen. <a href=\"http://maps.apple.com/?ll=49.216657,9.309391\">📍</a></p>\n<p>Heute mal Spargel</p>\n",
"content_text": "Kühners Besen. [📍](http://maps.apple.com/?ll=49.216657,9.309391)\n\nHeute mal Spargel\n",
"date_published": "2025-05-24T15:44:01+02:00",
"url": "https://www.the-sprawl.blog/2025/05/24/khners-besen-heute-mal-spargel.html"
},
{
"id": "http://tabtwo.micro.blog/2025/05/23/stze-die-man-gerne-von.html",
"content_html": "<p>Sätze, die man gerne von einem Handwerker am hellen morgen hört: So etwas hab ich ja noch nie gesehen!</p>\n",
"content_text": "Sätze, die man gerne von einem Handwerker am hellen morgen hört: So etwas hab ich ja noch nie gesehen!\n",
"date_published": "2025-05-23T08:27:50+02:00",
"url": "https://www.the-sprawl.blog/2025/05/23/stze-die-man-gerne-von.html"
},
{
"id": "http://tabtwo.micro.blog/2025/05/17/giersch.html",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/zkvw1ovqzomdwlnuje6acegjlq5vafresosy9qqg.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Giersch</p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/zkvw1ovqzomdwlnuje6acegjlq5vafresosy9qqg.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\">Giersch</p>\n",
"date_published": "2025-05-17T18:05:53+02:00",
"url": "https://www.the-sprawl.blog/2025/05/17/giersch.html"
},
{
"id": "http://tabtwo.micro.blog/2025/05/14/opencore-ist-der-hammer-ich.html",
"content_html": "<p><a href=\"https://dortania.github.io/OpenCore-Legacy-Patcher/\">OpenCore</a> ist der Hammer! Ich habe gerade mein altes MacBook Air von 2012 von 10.10 (Yosemite) auf Monterey (12.7.4) hochgehoben und das läuft ganz ordentlich. 13 Jahre alte Hardware, ist dann im Nachhinein doch ganz gut angelegtes Geld gewesen damals mit nem i7 und 8GB RAM.</p>\n<p>Mal schauen ob ich der Kiste ne neue SSD mit 1TB spendiere, die 256MB könnten aber auch reichen. Akku scheint auch noch ok zu sein obwohl das gute Stück jetzt ein paar Jahre im Schrank lag.</p>\n",
"content_text": "[OpenCore](https://dortania.github.io/OpenCore-Legacy-Patcher/) ist der Hammer! Ich habe gerade mein altes MacBook Air von 2012 von 10.10 (Yosemite) auf Monterey (12.7.4) hochgehoben und das läuft ganz ordentlich. 13 Jahre alte Hardware, ist dann im Nachhinein doch ganz gut angelegtes Geld gewesen damals mit nem i7 und 8GB RAM.\n\nMal schauen ob ich der Kiste ne neue SSD mit 1TB spendiere, die 256MB könnten aber auch reichen. Akku scheint auch noch ok zu sein obwohl das gute Stück jetzt ein paar Jahre im Schrank lag.\n",
"date_published": "2025-05-14T09:09:47+02:00",
"url": "https://www.the-sprawl.blog/2025/05/14/opencore-ist-der-hammer-ich.html"
},
{
"id": "http://tabtwo.micro.blog/2025/05/11/bersetzungen-aus-der-hlle.html",
"title": "Übersetzungen aus der Hölle",
"content_html": "<p>Die Dateien vom Illustrator enden auf .ai\nIrgendwann wird so ein Scheiss mal ein Menschenleben fordern und dann stehen wieder alle mit großen Augen da wie so etwas passieren konnte. Intelligenz mein Popo.</p>\n<p><img src=\"https://www.the-sprawl.blog/uploads/2025/image-20250511-171631-f43afb81.jpg\" alt=\"\"></p>\n",
"content_text": "Die Dateien vom Illustrator enden auf .ai\nIrgendwann wird so ein Scheiss mal ein Menschenleben fordern und dann stehen wieder alle mit großen Augen da wie so etwas passieren konnte. Intelligenz mein Popo. \n\n\n",
"date_published": "2025-05-11T17:16:41+02:00",
"url": "https://www.the-sprawl.blog/2025/05/11/bersetzungen-aus-der-hlle.html"
},
{
"id": "http://tabtwo.micro.blog/2025/05/10/no-caption.html",
"title": "No caption",
"content_html": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/zrogcmwl6trzkrihprg71lf8hbgjlzfml7x07lea.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\"></p>\n",
"content_text": "<div class=\"media-gallery\">\n <img class=\"media-item\" src=\"https://www.the-sprawl.blog/uploads/2025/zrogcmwl6trzkrihprg71lf8hbgjlzfml7x07lea.jpg\" alt=\"\">\n </div>\n <p style=\"padding:10px;\"></p>\n",
"date_published": "2025-05-10T18:29:44+02:00",
"url": "https://www.the-sprawl.blog/2025/05/10/no-caption.html"
},
{
"id": "http://tabtwo.micro.blog/2025/05/10/parkhotel-stuttgart-messeairport-heute-mal.html",
"content_html": "<p>Parkhotel Stuttgart Messe-Airport. <a href=\"http://maps.apple.com/?ll=48.691851,9.168202\">📍</a></p>\n<p>Heute mal Schnitzel im Parkhotel</p>\n",
"content_text": "Parkhotel Stuttgart Messe-Airport. [📍](http://maps.apple.com/?ll=48.691851,9.168202)\n\nHeute mal Schnitzel im Parkhotel \n",
"date_published": "2025-05-10T17:26:06+02:00",
"url": "https://www.the-sprawl.blog/2025/05/10/parkhotel-stuttgart-messeairport-heute-mal.html"
},