@kat@yarn.girlonthemoon.xyz Don’t be nervous, I make sure I test the shit™ out of things before anyone else does 🤣

@prologic@twtxt.net exciting!!!!!! i’m SO SORRY i didn’t get to doing the migration for my instance though - i’ve been really busy! T__T but i hope to get to it sometime this week i really wanna upgrade i think i’m just a bit nervous for whatever reason lol

@thecanine@twtxt.net do you read ed zitron’s newsletter? he writes in depth about how AI is a crock of shit it makes me feel normal for once

@movq@www.uninformativ.de this looks really cool

@Yarn@yarn.social yo, what’s up? I am busy running my business here!

@thecanine@twtxt.net “*BuT cAnInE, tHe A(G)i ReVoLuTiOn Is NoW*” Hahahaha! Thanks for good laugh! 🤣

Hello @Yarn.social@yarn.social 👋 (testing something)

@thecanine@twtxt.net Sorry, but you were expecting what now?! 🤣

I also fundamentally do not believe in the notion that Twtxt should be readable and writable by humans. We’ve thrown this “argument” around in support of some of the proposals, and I just don’t buy it (sorry). As an analogy, nobody writes Email by hand and transmits them to mail servers vai SMTP by hand. We use tools to do this. Twtxt/Yarn should be the same IMO.

@eapl.me@eapl.me I honestly believe you are overreacting here a little bit 🤣 I completely emphasize with you, it can be pretty tough to feel part of a community at times and run a project with a kind of “democracy” or “vote by committee”. But one thing that life has taught me about open source projects and especially decentralised ecosystems is that this doesn’t really work.

It isn’t that I’ve not considered all the other options on the table (which can still be), it’s just that I’ve made a decision as the project lead that largely helped trigger a rebirth of the use of Twtxt back in July 1 2020. There are good reasons not to change the threading model right now, as the changes being proposed are quite disruptive and don’t consider all the possible things that could go wrong.

@bender@twtxt.net ROFL 🤣

@prologic@twtxt.net if I tell you I will lose the edge. I want to mass produce them, as a business venture. LOL.

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

@andros@twtxt.andros.dev We don’t know the cause, yet, do we? 🤔

@prologic@twtxt.net that mechanical magical ball I built is doing a good job, thus far. :-P

@lyse@lyse.isobeef.org Oh, no, this is vastly exaggerated. Neil deGrass Tyson says, the earth is smoother than a cue ball (billiard): https://www.youtube.com/watch?v=OMP5dNsZ-6k That would make for a very dull OpenGL program, though. 😂

@bender@twtxt.net You guessed right 🤣

@iolfree@tilde.club Fuck no. 😅

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

@prologic@twtxt.net Spain. Duh! 😂

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

@lyse@lyse.isobeef.org

Also, I see what you did there in regards to the reply model change poll. ]:->

The community is heavily divided in this regard, and yet we need consensous. We’re like the three Borg in VOY: Survival Instinct. 🥴

@prologic@twtxt.net if not that, what else? Communism? Is there, really, such thing? 🤣

@prologic@twtxt.net 🚀🚀🚀🎉🎉🎉

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

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

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

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

@prologic@twtxt.net I have:

• jenny
  
• buckket’s original (patched, or not)
  
• tt/tt2
  
• Timeline
  
• Twtxtory
  
• Yarnd

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 😅

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