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
@prologic@twtxt.net 🚀🚀🚀🎉🎉🎉
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
@news-minimalist@feeds.twtxt.net so many “good news”, we are “winning” big time. I listen to NPR on my way to work, and they were talking about the foot depletion. You could hear the desperation of the people they put on, so incredibly sad. 😢
@lyse@lyse.isobeef.org LOLed in RL, my office mates were, “what’s going on, where, what?!”. 😂
git pull on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
@movq@www.uninformativ.de DDoS their ass! 🤣
tt2 from @lyse and Twtxtory from @javivf?
@bender@twtxt.net Yup! 👍
@lyse@lyse.isobeef.org Noice! 👌
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
@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 🤣
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
@lyse@lyse.isobeef.org Yup! Will do 🤗
git pull on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
@movq@www.uninformativ.de oi, that has to be a bot. AI bot? Maybe not, but still a bot. I see this becoming more and more of an issue, sorry to say…
tt2 from @lyse and Twtxtory from @javivf?
@prologic@twtxt.net I have:
- jenny
- buckket’s original (patched, or not)
- tt/tt2
- Timeline
- Twtxtory
- Yarnd
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
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 😅
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
@prologic@twtxt.net pinging the involved (@andros@twtxt.andros.dev, @abucci@anthony.buc.ci, @eapl.me@eapl.me, @lyse@lyse.isobeef.org, @movq@www.uninformativ.de, @sorenpeter@darch.dk), just in case. I might have forgotten someone, please feel free to ping them.
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
@prologic@twtxt.net I now see my twtxts as written in the proverbial stone. That is, no edits, no deletions, no matter how embarrassing their content might be. 😅
Hear, hear, @prologic@twtxt.net! :-)
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
@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 🤣
yarnd powering this pod twtxt.net 🧐
@sorenpeter@darch.dk you raw feed says otherwise. Also, https://txt.sour.is/conv/wj5bcwq.
yarnd powering this pod twtxt.net 🧐
yarnd powering this pod twtxt.net 🧐
@prologic@twtxt.net it was not an edit but a double posting
yarnd powering this pod twtxt.net 🧐
@prologic@twtxt.net yup. Funny enough, the first twtxt should have sufficed, as if there is no domain, there will be no feed (at that domain). The edit to add that the feed will not be available is redundant.
@prologic@twtxt.net stop fooling around, and smell the flowers (careful with the bees, they sting)! An unofficial sign done by children, I am sure. :-D
@lyse@lyse.isobeef.org hey pascal bro! My first coding class was with an old Borland Turbo Pascal. I made my own little window manager for the assignments for class.
The teacher didn’t appreciate it much since I had to print out the code to turn it in. My Yatzee game was a stack of pages. 🤪
@lyse@lyse.isobeef.org Very nice! 👌 So lovely and green 😅 – What’s with the sign in
? 🧐
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?! 😂
@lyse@lyse.isobeef.org yikes! I knew there will be collateral damage, but I wasn’t expecting it to affect The Tubes! 😱
Hi @lyse@lyse.isobeef.org, I canceled the domain, so neotxt or my feed there are not coming back.
@twtxtory@twtxtory.adn.org.es sorry, it isn’t. After you enter the password, it takes a very long time to render anything. I don’t have the patience to wait. Longest I waited is 3 minutes, and nothing. Super extremely slow.
@bender@twtxt.net Oh 🤣🤣🤣
@prologic@twtxt.net ah, yes, a feed that I have muted. 😂
Should ink to this 
@javivf@adn.org.es the demo doesn’t work. When trying to login, it simply times out.
@prologic@twtxt.net oh, sorry, you are right. Beautiful 404. The most beautiful 404 I have ever seen. Tremendous! 🤪
@bender@twtxt.net What you talk’n about 🤣 It’s not broken, it’s perfectly functional 🤣
@prologic@twtxt.net first we need to fix broken links. 😅
@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? 🧐
@prologic@twtxt.net This was like 20 minutes, but yeah 🤣
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.
@movq@www.uninformativ.de Only 99.9% pfffft 🤣
@twtxtory@twtxtory.adn.org.es Hello 👋 Welcome to Yarn.social / Twtxt 😅
jenny, tt or any other client where fetches are driven by user interactions of invoking the app. What do we call this type of client? Hmmm 🤔 Then I can tell who uses yarnd because they are "seen" more frequently 🤣
@javivf@adn.org.es pretty much 👌