@david@daiwei.me It would appear so 👌

@thoshi@yarn.thoshis.net I wouldn’t bother if I were you 😅 They’re both fairly outdated protocols and very much an “silo” IMO. THey don’t make very good places to host your Twtxt feed either.

@thoshi@yarn.thoshis.net Welcome to the Yarn.social / Twtxt ecosystem 🙌

And @lyse@lyse.isobeef.org is right. Not being on Github is a good thing IMO. Even when I was there with all my many projects, I basically got the same amount of “attention” as I do now. The only real way to gain more “attention” is to artificially play the “game”. You know. The stupid “Stargazer” one, and whatever you can to get into the “Top 10 X” charts. – But ultimately that doesn’t buy you “quality” contributors or users or whatever. So it’s all pointless.

@movq@www.uninformativ.de So I see it slightly differently… Over the years I have recieved great contributions from the likes of yourself and @lyse@lyse.isobeef.org and the many forms of @bender@twtxt.net and his friends 😅 Hell even others along the way that have come and gone. Likewise I also think you have recieved many contributions to Jenny over the yeras in much the same way, perhaps not in patches, but user reports, feedback, etc.

So I think what I’m saying here is this… Ever since leaving Github (like you), I find that my desire to continue to build up the community we’ve built here and to contribute to grow and cultivate it is important to me. My desire to thwart and eliminate useless traffic like bots and ai even strongers.

I want to find a good balance.

@thecanine@twtxt.net Always love your work ! 👌

@david@daiwei.me OH no ! 😟 My wife caught COVID some weeks ago, then we got sick again with a cold, it was awful 😢

Oh god 🤣 I mean I had this idea to re-invent “Git hosting”, but failed. Maybe I’ll try it again. I dunno. The thing is I hardly get “Issues” really, only when I ask nicely, of folks I know every well 🤣 So think at much “smaller scale” we need a different solution, and I think @movq@www.uninformativ.de is on to something, but not to the extend implemented, somewhere in the middle I think? 🤔

@david@daiwei.me Bah you 🤣 Do you know how hard™ it is to write a compier, a self-hosted compiler that has two runtime engines? 😅

On that note, I just finished writing the linux/risc64 backend and it only took ~2k lines of code 🎉

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 🧐

@aelaraji@aelaraji.com Noice 👌

(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 👋

@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 🧐

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 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 👀

@lyse@lyse.isobeef.org Can you explain this like i’m five? 🤣 Scgeenshot?

@aelaraji@aelaraji.com Haha 😆 Oh dear!