🥳 Finally! After nearly 4 years, yarnd v0.16.0 “Silver Sojourner” is out! 🚀 Twt Hash v2, SQLite FTS5 search, HTMX-powered UI, first-time setup wizard and literally hundreds of bug fixes 🐛

Release notes: https://git.mills.io/yarnsocial/yarn/releases/tag/0.16.0

Upgrading is fully automatic — the Twt Hash v2 migration re-fetches all feeds on first start, so expect the first cycle to be a bit heavier. Images on Docker Hub as prologic/yarnd:0.16.0 👌

cc @kat@yarn.girlonthemoon.xyz @abucci@anthony.buc.ci @shinyoukai@yume.laidback.moe @eldersnake@we.loveprivacy.club 🙏

@balloonfu-sen@yarn.girlonthemoon.xyz I could in toehry publish a specification for what twtd implements, which forms the basis of the API between twtxt.app <-> twtd, if you wanted to write your own twtd / twtxt.app compatible publishing backend (assuming you didn’t want to use Github/Gitea, etc).

Yeah to @david@daiwei.me’s point re Editing. It’s only really safe to do so if you are sure that no-one has yet fetched your feed or replied to your Twt. But even then, you have to be quick 🤣 Editing/fixing a Twt inside of an existing thread is “oaky”, as long as it also doesn’t get forked and becomes the root of a new conversation 😅

Thanks to twtxt.app, I probably won’t need to build a yarnd. Instead, I can either install twtd and manage it on my VPS or similar, or put the twtxt text file in a Git repository. Consider other options as well.

Editing isn’t good. I would recommend you forget editing exist, as it breaks threads and twtxts ended up not making sense. Consider everything typed written in stone. Send a follow up twtxt amending if at all needed.

@prologic@twtxt.net Ah, I clearly checked the strange timeline. https://yarn.girlonthemoon.xyz/twt/h5otbvq

The search engine @prologic@twtxt.net refers about is at https://search.twtxt.net/.

@prologic@twtxt.net Could it be…… I edited several times earlier, so that might be the influence. Not the old yarnd.

I am now seeing it exceed 100 twts for the first time. Today’s twtxt is lively. https://yarn.girlonthemoon.xyz/

Hmm. I might consider setting up a twtxt environment on my VPS.

@balloonfu-sen@yarn.girlonthemoon.xyz Thank you for doing this 🙏 – Just a thought… It might be possible for this to be fully automated from the Twtxt Search engine / crawler? Right? 🤔 It has all of the data… I also think it might be possible to distinguish between 1-way feedsa and “real folks” (ya know, 2-ways feeds) 🤣

@balloonfu-sen@yarn.girlonthemoon.xyz Such tilde(s), etc, could in theory just run a twtd instance per user, or if I was convinced enough to make twtd also multi-user capable (optionally) that would also work. But many ~tilde(s) barely implement the Twtxt specs we continue to build and improve (albiet slowly and carefully).

@david@daiwei.me Hello! I have added you to this list. https://balloon.oldcities.org/twtxt-active-users.txt

Added 1 account (david) https://balloon.oldcities.org/twtxt-active-users.txt

@prologic@twtxt.net if twtxt user are using a VPS, twtd can be an option. People who use twtxt also exist in SDF and Tilda, so I thought it wouldn’t be possible. Could they not improve their environment?

We someone need to get @kat@yarn.girlonthemoon.xyz to update her pod hmmm 🤔

@balloonfu-sen@yarn.girlonthemoon.xyz Unfortunately I tried to support SFTP but ripped this out as Browsers (which the Swag framework uses under the hood as a framework to build PWA(s)) doesn’t support raw TCP connections. So FTP / SFTP is not possible without hacks like a proxy. Which I don’t really want to support. So only things that have some kind of HTTP API are possible viable publihsing backends right now. That is Github/Gitea, twtd, Yarn, etc.

@balloonfu-sen@yarn.girlonthemoon.xyz it is perfect. Truly responsive and fast.

@balloonfu-sen@yarn.girlonthemoon.xyz That should work. LMK if you run into any issues!

(#nmdjwpo3sy5a) (#nmdjwpo3sy5a) (#nmdjwpo3sy5a) @prologic@twtxt.net Some web hosting platforms still use FTP (which can be used from older devices) and SFTP, so having that option in twtxt.app might be a good option.

@prologic@twtxt.net A few days ago, twtxt.app had been talked about, so I was concerned. I just tried connecting this yarn account to twtxt.app.

@david@daiwei.me Nice! 😊

I am using both, twtxt.app and twtd. Working like a charm!

👍 definitely using the Twtxt App as my daily-driver now for Twtxt/Yarn. Not using twtd however, as I just pair the app with my already existing yarnd powered profile on twtxt.net

So… Quick count. Hands up those who are using the Twtxt App? 🤔 – And who’s also pairing this with the twtd publishing backend?

@david@daiwei.me Good! 👍

@bender@twtxt.net Test!

@prologic@twtxt.net nice, now tagging works on mobile.

Pretty cool, @prologic@twtxt.net, I am glad we helped! 🎉😂

Looks like twtxt.app on mobile emits +00:00 UTC timestamps instead of Z – Yarnd should handle both, but doesn’t 🤦‍♂️ On the list 🤞

@bender@twtxt.net @david@daiwei.me Good debugging session 👌 Sounds like the root cause is twtxt.app on mobile — +00:00 timestamps and quoted mentions. I’ll dig into Yarnd’s side of that 🧐

@bender@twtxt.net Yeah, Yarnd’s mention parser is pretty naive — if twtxt.app wraps the mention in quotes it probably strips them wrong. Worth fixing 🤔

Forking @bender@twtxt.net:

@david@daiwei.me now I am forking:

I see @bender@twtxt.net twtxt just above this one. Good, so far.

@david@daiwei.me now I am forking:

I see @bender@twtxt.net twtxt just above this one. Good, so far.

I see @bender@twtxt.net twtxt just above this one. Good, so far.

@david@daiwei.me bender variable in. First thing I see on Yarnd is that my mention is broken. It was entered between quotes on twtxt.app. Yarnd has always had parsing problems, so I am not blaming twtxt.app this time.

Now let’s wait, and stop posting from here, and after this one shows at Yarnd, I will introduce the “@ variable”.

This is another reply, same root=jlte7el5tcyi, which makes it the sixth twtxt in the conversation (flat, not counting forks).

root=idtig63uigwe and another, quoting the previous twtxt:

root=idtig63uigwe this isn’t a fork, just a reply on the previous fork.

root=7cnr5hulfahb fork. I am now forking:

Lyse swears the issue at with the app. So, I will continue testing on this conversation. I am not going to fork yet, these are just twtxts on the conversation.

root=idtig63uigwe fork. I am forking:

And I am saying that, because everything looks fine on twtxt.app, but not in Yarnd. But I am confused because jenny is also showing things not the way it should be.

Lyse swears the issue at with the app. So, I will continue testing on this conversation. I am not going to fork yet, these are just twtxts on the conversation.

And I am saying that, because everything looks fine on twtxt.app, but not in Yarnd. But I am confused because jenny is also showing things not the way it should be.

Now I don’t know if Yarnd is the one having issues, or if twtxt.app is at fault.

@movq@www.uninformativ.de this one:

2026-07-11T17:28:31Z	(#fcyeeyd3ii2o) No yet. Let’s keep it rolling a little bit longer. I am reply to “[..] I don’t see any broken threads here. 🤔“. I can’t tag followings while on mobile. <-- THIS BROKE

Was a reply to:

2026-07-11T16:39:22+00:00	(#iqqsqst5vokf) @<david https://daiwei.me/twtxt.txt> Well, I don’t see any broken threads here. 🤔

Hmm…

This is how it shows in jenny:

@movq@www.uninformativ.de this is what I see on twtxt.app (all looks good there, though, but not here, on Yarnd):

@balloonfu-sen@yarn.girlonthemoon.xyz 初めまして！

@oberon@nightfall.city one day I will get there :B