@movq So the way this works in my design/prototype is this. You fork my repo in the app, it clones it to your own forge, follows my instance and it's repo for updates and ping my instance to indicate "you've forked me". Then when you publish changes, I can see them by pulling your instance's feed. It all works on the same plain text principles of Tstxt itself. The feeds are "pull"-based with push-based "pings" on things like "someone forked your repo", "a new issue has been raised against your repo", etc.

@fossham I hope you enjoy it 😅 You might want to update your Avatar and Description at some point in your settings 👌

@david Do you mind re-testing too with the updates i just pushed out? 🙏

@balloon-fu-sen Fixed! 🥳 The Avatar URL field now actually gets written to your feed's # avatar = metadata. Turned out it needed changes in both the app and twtd itself — so you'll want to update your twtd instance once the new build lands. Thanks for the report! 🙏

We someone need to get @kat to update her pod hmmm 🤔

Shit i need to update yarnd 😅

Global update: Trump in Scotland says EU trade deal has 50-50 chance as tariff row grows. Gaza sees 9 more starvation deaths (122 total); UN says famine is deliberate. Thai-Cambodia clashes kill 16, displace 135k. US raid in Syria kills top ISIS leader & sons.

After yarnd v0.16 is released and the next round of specification updates are done and dusted, who wants me to have another crack at building Twtxt and activity pub integration support?

Finally I propose that we increase the Twt Hash length from 7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update

Just like we don't write emails by hand anymore (See: #a3adoka), we don’t manually write Twts or update our twtxt.txt feeds. Instead, we use modern Twtxt clients that conform to the specifications at Twtxt.dev for a seamless, automated experience. #Twtxt #Twt #UserExperience

Today I added support for Let's Encrypt to eris via DNS-01 challenge. Updated the gcore libdns package I wrote for Caddy, Maddy and now Eris. Add support for yarn's cache to support # type = bot and optionally # retention = N so that feeds like @tiktok work like they did before, and... Updated some internal metrics in yarnd to be IMO "better", with queue depth, queue time and last processing time for feeds.