@bender@twtxt.net Same more or less 😅

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

@sorenpeter@darch.dk you raw feed says otherwise. Also, https://txt.sour.is/conv/wj5bcwq.

@sorenpeter@darch.dk Oh!

@prologic@twtxt.net it was not an edit but a double posting

@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

@yejokjanan@texto-plano.xyz hey ya viste la nueva temporada de black mirror???

@javivf@adn.org.es Go for it! You’re free to use it.
It’s been a community adventure to explore the whole DM/encryption thing. So the community can do with it whatever they want. 😎

@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?! 😂

@kat@yarn.girlonthemoon.xyz IT IS HOLY HECK THE TALENT!!!! 🙌🏻🙌🏻

twtxt tui - como va quedando??? https://0x0.st/8Wc4.png

@lyse@lyse.isobeef.org yikes! I knew there will be collateral damage, but I wasn’t expecting it to affect The Tubes! 😱

@movq@www.uninformativ.de I started with Delphi in school, the book (that we never ever used even once and I also never looked at) taught Pascal. The UI part felt easy at first but prevented me from understanding fundamental stuff like procedures or functions or even begin and end blocks for ifs or loops. For example I always thought that I needed to have a button somewhere, even if hidden. That gave me a handler procedure where I could put code and somehow call it. Two or three years later, a new mate from the parallel class finally told me that this wasn’t necessary and how to do thing better.

You know all too well that back in the day there was not a whole lot of information out there. And the bits that did exist were well hidden. At least from me. Eventually discovering planet-quellcodes.de (I don’t remember if that was the original forum or if that got split off from some other board) via my best schoolmate was like finding the Amber Room. Yeah, reading the ITG book would have been a very good idea for sure. :-)

In hindsight, a console program without the UI overhead might have been better. At least for the very start. Much less things to worry about or get lost.

Hence, I’d recommend to start programming with a console program. As for the language, not sure. But Python is probably a good choice, it doesn’t require a lot of surrounding boilerplate like, say Java or Go. It also does exceptionally well in the principle of least surprise.

probando mi nuevo tui para twtxt :P

@sorenpeter@darch.dk I see, ta. The big spring cleaning continues. ;-)

Hi @lyse@lyse.isobeef.org, I canceled the domain, so neotxt or my feed there are not coming back.

@bender@twtxt.net Must be the US tariffs, it’s working reasonably quick in Europe. :-D

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

@movq@www.uninformativ.de Your next experiment should be triangles. :-)

@bender@twtxt.net is it working now?

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

@prologic@twtxt.net In few weeks for sure, I have a couple of features in mind that I would like to implement (DM extension for example but I’ll ask for permission to @arne@uplegger.eu to use his PoC or ask him to contribute to twtxtory directly)

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

@prologic@twtxt.net Yup! :)

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

@twtxtory@twtxtory.adn.org.es is the demo instance for Twtxtory just in case someone would like to have a look (password is in the README file of the project) sorry for the confusion! O:)

@prologic@twtxt.net I started to write it in order to understand better how twtxt works and I thought it could be useful for non-geek people but they like to host their own data

@movq@www.uninformativ.de Bwahahaahaaa, this is fucking brilliant, I love it! :-D What a wonderful thing to start my Sunday.

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