After many months of hard™ work, I’ve finally been able to get Mu (µ) lang to a point where the duplication of machine code / assembly between the ARM64/AMD64 and Mach-O and ELF formats are not all eliminated. This now means that writing a new backend target os/arch for Mu is now relatively simple to do, or far less duplicated work/effort.
Oh good 😅
2026/07/19 02:55:52 sync-reaper: observe-only pass — 1152 namespaces, 6 anchored, 1094 undatable, 0 idle candidate(s), 0 reaped
@movq@www.uninformativ.de Hmmm you’ve given me an idea 🧐
(1) Why The Ocean’s Top Predator Refuses to Hunt Us - YouTube – The first half of this documentary is amazing! 😮 – The remaining half however is sad and depressing, making me never want to visit another zoo again 😢
@aelaraji@aelaraji.com oh good was that the in app nudge?
i think there should be at least 4 we know of right?
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 👋
tt. I run into this bug almost daily for weeks now.
@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 🧐
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
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 😅
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
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 👍
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
@david@daiwei.me Good point ! 👌
@david@daiwei.me Nice! 👍
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
IMPORTANT: Treat the re oery code like a password.
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
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 Danke 🙏
@david@daiwei.me Cool 😅
@david@daiwei.me Please 🙏
I’ll see if I can unblock just that VPN provider 🤞
Testing the NEW Composer Preview
there us a recovery path
no, not what um dating at all
sue expand ed on the main thread
the only reason twtd has and records a followers.json is because that’s where your feed is hosted from and where the UA discover occurs
the correct fix for what you observed is a recovery token to re-sync settings from the sync API
it’s client sue not on any publishing backend
not stored on twtd no
@bender@twtxt.net I meant the hookers 🤣
@bender@twtxt.net Who’s buying? 🤔
I see you 👀
tt. I run into this bug almost daily for weeks now.
@lyse@lyse.isobeef.org Can you explain this like i’m five? 🤣 Scgeenshot?
@aelaraji@aelaraji.com Haha 😆 Oh dear!
@dce@hashnix.club Ah brilliant 👌
To retest: reload the app, reconnect Codeberg/Gitea with the same token, fill in the new Owner field (dce), repo twtxt, and Feed URL https://hashnix.club/~dce/twtxt.txt. Publish to Codeberg, serve from Hashnix — exactly what you wanted 🤞 lemme know!
@dce@hashnix.club Fixed! 🥳 That 403 was our bug — connect was checking your token via /api/v1/user (needs read:user), but your token’s scoped to just the repo so it can’t. Now it validates against the repo itself instead 👍
@misskatie@twtpub.com Haha 🤣 Nice Avatar 👌
@david@daiwei.me Bahahaha 🤣
@david@daiwei.me Oh yes blame me for you not having fun on the “Play Station” 🚉 Haha 🤣
@GabesArcade@gabesarcade.com I may be blocking that provider due to abuse from bots using VPN(s) – What was your last IP?
@david@daiwei.me I think yhwre was 😅
@david@daiwei.me I think it might be a bug i just fixed 🤞
@movq@www.uninformativ.de I can’t do Java ever again 🤣