Does this seem right to you so far @david@daiwei.me ? 🤔

2026/07/18 02:55:52 sync-reaper: observe-only pass — 1145 namespaces, 3 anchored, 1089 undatable, 0 idle candidate(s), 0 reaped

So far only 3 users of the Twtxt App have achieved their device settings with a recovery key? 🔑

Morning y’all 👋

Hurray! Finally, the thunderstorm is right over us. The last days we always got skipped. The rain smells so great. :-)

Ta, @david@daiwei.me, much appreciated.

@movq@www.uninformativ.de Hahaha, I didn’t expect anything like that. But yeah, makes perfect sense. :-D

@lyse@lyse.isobeef.org I was wondering for an embarrassingly long time why my NAS wouldn’t boot. (The main power supply switch was turn off.) 🤪

Sunset few days ago:

@prologic@twtxt.net Haha, no, you’re off the hook this time. :-D It’s totally my fault.

@movq@www.uninformativ.de Den Lärm haben sie gut rausgefiltert. Ist mir jedenfalls nicht negativ aufgefallen. Oder es war einfach zu interessant. Tauschen möcht ich aber mit Dir echt nicht. :-(

@movq@www.uninformativ.de Now I’m curious what happened.

@movq@www.uninformativ.de Bwahahaha, absolut großartig! :‘-D

We strolled up our backyard mountain. Visibility wasn’t the best, despite the rain we got yesterday. Oh well, scenery was really beautiful, though.

I found it super funny that we almost overtook a jogger before she turned off to another path right in front of us (yeah, we’ve got a smart pace, but this girl was slow as a snail).

https://lyse.isobeef.org/waldspaziergang-2026-07-18/

Falls sich hier noch jemand fragte, was genau mein Humor ist:

https://sueden.social/@DerSash/112366647794794897

Das Gegenteil von Erbse ist Verdiense.

@lyse@lyse.isobeef.org Das ertrag’ ich wahrscheinlich nur auf Mute. Scheiß Lärm. 🤣

Note to self: If you turn something off, this means it is not on.

@lyse@lyse.isobeef.org Ahh ok! I was just wondering and curious whether it was a bug that I’ve caused anywhere along the way 🧐

@dce@hashnix.club I see, ta!

@movq@www.uninformativ.de @prologic@twtxt.net @itsericwoodward@itsericwoodward.com Let me join the Enterprise Ruined It For Me Club. :-D

@david@daiwei.me Yeah, with the long and thus taller list entries, things are getting off hands. Ah, when focused, you wouldn’t differentiate between read or unread.

@prologic@twtxt.net A screenshot won’t help in this case, as you don’t see anything. :-D It starts off just fine with a conversation tree like that:

Unknown conversation root
└╴Read reply
  └╴Read subreply

Everything works. After reloading the feeds, a new message becomes part of the conversation, so the conversation e.g. looks:

Unknown conversation root
└╴Read reply
  ├╴Read subreply
  └╴Unread subreply

However, the bug is that the whole conversation is not shown at all. None of the three (or four with the root) messages appear in the message tree view. My recursive SQL determining the messages to display is clearly broken.

Tops 25°C is a very welcome change. Tomorrow just 21°C (but right before I went to bed they forecasted two degrees less today).

and @david@daiwei.me your rename shipped 🙌 it’s “Generate recovery code” now (you were right — mints a fresh one each press), + it asks before replacing an existing code so you don’t nuke the one you saved 😅

quick correction on that cleanup timing 🙏 it’s not 28 days. nothing gets deleted for the first 30 days at all (observe-only), and after that only setups unused for ~6 months that also never saved a recovery code. saved a code = safe forever 👍

@david@daiwei.me Good point ! 👌

@david@daiwei.me Nice! 👍

IMPORTANT: Treat the re oery code like a password.

I will be monitoring the server logs for the next ~28 days, after that orphaned Namespaces will start to get cleaned up, especially ones that have never bothered to care about recovery.

📣 ACTION REQUIRED: Hey folks 👋 For those of you whom are using the Twtxt App either via the Hosted option or on your own twtd instnace or via Github/Gitea or any other publishing backend (doesn’t amtter). Please read.

Please open the app and you should be prompted to save your recovery code for your device. This basically is all of your settings, follows, etc in the app itself. This is synced to the Origin everytime you make a change, and also stored on-device. This is what makes it possible to sync your setting across services, move to another device, etc.

Please save a copy of the recovery code somewhere. This is only your only way to recover your settings.

Thank you 🙏

Posting the review and plan here for posterity as it is related to this thread: https://canvas.mills.io/a/6QVGjzRW

The PR(s) as-is will likely not go ahead I’m afraid. More work to be done, but this is basically all about the “Recovery” story and how to anchor and notion of an “account” without well umm an account 🤣

@david@daiwei.me Ma too 🤣

@ponderpoints@twtpub.com Welcome to Yarn.social 👋 Interesting video, I actually watched it all the way through, riverting stuff really and quite well put together. The idea of “subjective experience” is a rather complicated thing to describe and you’re right, how do we even know we have them? 🤔

@david@daiwei.me Holy moly 😱

Ahh yes! Please do upgrade your twtd instance. Few things changed, many bugs fixed there too.

@balloon-fu-sen@tw.fus.f5.si Huh? 🧐 This hasn’t changed. What has is the default proxy used depending on your publishing backend.

@david@daiwei.me It’s truly mind-boggling. All the hand full of episodes I’ve seen so far on this channel are amazing. Totally worth tuning in. I have to catch up a lot. :-)