@bender@twtxt.net How does it work? 🤔

LOL Amazon displaying tariff prices “hostile and political,” White House say is this the kettle calling the pot black? 🤣 Trump, pfft, what a fucking idiot. No clue how economies work, let alone countries.

@bender@twtxt.net You guessed right 🤣

@bender@twtxt.net LOL how would I have guessed that?! 🤣

@javivf@adn.org.es 12 Hlirs without power? 🧐 Where do you reside?! 🤣

@lyse@lyse.isobeef.org likewise I don’t have the energy for a fundamental shift in any of our specifications that would inevitably cause a lot of toil and try and change in our clients implementations and unforeseen problems that we haven’t really fully understood:

@movq@www.uninformativ.de At this point someone needs to make a decision 🤣 @bender@twtxt.net keeps reminding me of that😅

03:45 You can pretty blame capitalism for everything that’s wrong with anything 🤣

I really do wish we would wake up and smell the roses here 🤦‍♂️ This whole sets of wars is utterly pointless. Senseless waste of precious human beings 😢

https://git.mills.io/yarnsocial/twtxt.dev/pulls/28

@movq@www.uninformativ.de DDoS their ass! 🤣

@bender@twtxt.net Yup! 👍

@lyse@lyse.isobeef.org Noice! 👌

@lyse@lyse.isobeef.org Hahahaha 🤣 I mean it’s “okay” every now and then, but what’s the point of having good clients and tools if we don’t use ‘em 🤣

@lyse@lyse.isobeef.org Yup! Will do 🤗

Nothing like being paged at 00:30 (midnight) for a P2 incident that is now resolved at 02:10 🤯 Obviously I’m not going to work tomorrow (I mean today lol 😂) at the usual start time 🤦‍♂️

I will be adding the code in for yarnd very soon™ for this change, with a if the date is >= 2025-07-01 then compute_new_hashes else compute_old_hashes

We have 4 clients but this should be 6 I believe with tt2 from @lyse@lyse.isobeef.org and Twtxtory from @javivf@adn.org.es?

@bender@twtxt.net Same more or less 😅

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

And speaking of Twtxt (See: #xushlda, feeds should be treated as append-only. Your client(s) should be appending Twts to the bottom of the file. Edits should never modify the timestamp of the Twt being edited, nor should a Twt that was edited by deleted, unless you actually intended to delete it (but that’s more complicated as it’s very hard to control or tell clients what to do in a truely decentralised ecosystem for the deletion case). #Twtxt #Client #Recommendations

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

Nobody writes emails by hand using RFC 5322 anymore, nor do we manually send them through telnet and SMTP commands. The days of crafting emails in raw format and dialing into servers are long gone. Modern email clients and services handle it all seamlessly in the background, making email easier than ever to send and receive—without needing to understand the protocols or formats behind it! #Email #SMTP #RFC #Automation

@bender@twtxt.net Hehe good sleuthing 🤣 I swear it was an edit ✍️ Haha 😂 yarnd now “sees” both every single time, where-as before it would just obliterate the old Twt, but remain in archive. Now you get to see both 😅 Not sure if that’s a good thing or not, but it certainly makes it much clearer how to write “code logic” for detecting edits and doing something more UX(y) about ‘em 🤔

@bender@twtxt.net It’s pretty cool though 🤣

@sorenpeter@darch.dk Oh!

Wrote some serious Python for the first time in like 10 years 😱 I feel so dirty 🤣

@lyse@lyse.isobeef.org Very nice! 👌 So lovely and green 😅 – What’s with the sign in

Image

Interesting edit observed by the new yarnd powering this pod twtxt.net 🧐

@movq@www.uninformativ.de I’ve tried and there’s little interest so I’ve given up for now 😭

@bender@twtxt.net Wut?! 😂

@bender@twtxt.net Oh 🤣🤣🤣

Should ink to this

Image

Hmm not sure how that link is 404’kng for you 🧐 It doesn’t here 🤦‍♂️

@bender@twtxt.net What you talk’n about 🤣 It’s not broken, it’s perfectly functional 🤣

@lyse@lyse.isobeef.org Seems legit 😅

I have a great idea for fixing the US economy. Get rid of all the nuclear weapons 🤣

@javivf@adn.org.es Wanna list it on twtxt.dev? 🧐

@javivf@adn.org.es Ahh! So this is your client implementation? 🧐

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@feeds.twtxt.net 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.

Also you have too much time on your hands 🙌 Haha 😂

@movq@www.uninformativ.de Only 99.9% pfffft 🤣

Was just looking at the client you’re using Twtxtory 🤔 Very nice! 👍 is this your client, did you write it? I’d not come across it before!

@twtxtory@twtxtory.adn.org.es Hello 👋 Welcome to Yarn.social / Twtxt 😅

@javivf@adn.org.es pretty much 👌

@quark@ferengi.one I do have an idea for syncing this 🤞

$ bat https://twtxt.net/twt/edgwjcq | jq '.subject'
"(#yarnd)"

hahahahaha 🤣 Does your client allow you to do this or what? 🤔

Bahahahaha 🤣

@bmallred@staystrong.run Hehe, @bender@twtxt.net is gonna be upset with you for “making up a thread/subject” 🤣

@bmallred@staystrong.run No! Never 😆