@bender@twtxt.net Haha 🤣

@kat@yarn.girlonthemoon.xyz Please git pull and rebuild 😂 Off of main. I merged the catcher branch already!

@kat@yarn.girlonthemoon.xyz @xuu@txt.sour.is Recommend you git checkout main && git pull && make build. Few bug fixes 😄

@bender@twtxt.net You’re kind of right though 😄 It makes it more engaging IMO 😅

“Monosyllabic replies” refers to responses that consist of a single syllable. These types of replies are typically brief and concise, often used in situations where a simple, direct answer is given. Examples include words like “Yes,” “No,” “Okay,” or “Sure.”

😂 Can I imply you’re not interested in things like “LIke”, “Report”, etc?! 😂

@bender@twtxt.net I knew you wouldn’t be interested in a Twtxt+ActivityPub 😂 Now I have to go figure out what “monosyllabic replies” means 🤣

@movq@www.uninformativ.de Shall I add this to the spec I’m writing? ✍️

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?

The reason I think this can work so well and I’m in full support of it is that it’s the least disruptive way to resolve the issue of:

where did this hash come from?

@movq@www.uninformativ.de I think we can make this work 👌 As long as it’s just a client hint.

@kat@yarn.girlonthemoon.xyz Should be fine 🙌

Otherwise assume normal behavior. Pretty easy to implement I think.

@movq@www.uninformativ.de If we’re focusing on solving the “missing roots” problems. I would start to think about “client recommendations”. The first recommendation would be:

1. Replying to a Twt that has no initial Subject must itself have a Subject of the form (hash; url).
   

This way it’s a hint to fetching clients that follow B, but not A (in the case of no mentions) that the Subject/Root might (very likely) is in the feed url.

@bender@twtxt.net Fuck I meant “bugs” 🐞 Geez 🙄

@kat@yarn.girlonthemoon.xyz Unless you’ve found buds in this branch it should be fine 😆 Um running yhe dame!

@movq@www.uninformativ.de Lwt me think on this.

@kat@yarn.girlonthemoon.xyz Nope it’s totally fine 🤗

@kat@yarn.girlonthemoon.xyz No new peers shoyls show up automatically.

@sorenpeter@darch.dk You’re welcome 🤗 We’ll run into each other again. I’m sure! 🤞

@kat@yarn.girlonthemoon.xyz Well some! 🙌

@thecanine@twtxt.net Yeah this is where I think all the hype really falls down. It’s all just a really really expensive search engine and auto-complete 🤦‍♂️ That’s it!

@kat@yarn.girlonthemoon.xyz MinIO is a good choice for a self-hosted Object Storage (compatible with S3 APIs) 👌

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

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 🤣

@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