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 In case you reconsider, it would be even easier then to just send an HTTP 429 Too Many Requests
. :-)
now()
or the message's creation timestamp? I reckon the latter is the case, but it's undefined right now. Then we can discuss and potentially tweak the proposal.
@bender@twtxt.net Hehehe! :-D
@movq@www.uninformativ.de I have to admit, I didn’t follow the topic very closely, but I was under the impression that there were more votes on location-based addressing. But maybe I’m completely wrong. Anyway. I don’t have the energy to be part of a fundamental debate.
@prologic@twtxt.net Thank you for writing this together. I just left a few comments.
now()
or the message's creation timestamp? I reckon the latter is the case, but it's undefined right now. Then we can discuss and potentially tweak the proposal.
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. 🥴
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.
Nah, I’m not taking any action yet. 😅 The good thing is that I don’t run a Git daemon on my server. It’s all just HTTP, which is fast and doesn’t consume a lot of memory.
@prologic@twtxt.net if not that, what else? Communism? Is there, really, such thing? 🤣
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. 😢
now()
or the message's creation timestamp? I reckon the latter is the case, but it's undefined right now. Then we can discuss and potentially tweak the proposal.
@lyse@lyse.isobeef.org LOLed in RL, my office mates were, “what’s going on, where, what?!”. 😂
Gaza blockade depletes World Food Programme stocks + 1 more story
North Korea confirms sending troops to Russia as a defense pact; Gaza blockade leaves World Food Programme out of supplies, risking starvation for millions. ⌘ Read more
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 You better push new code sooner!!
As @bender@twtxt.net says, that sounds like a bot. I’d just block the IP address, hoping it doesn’t change all the time. But then you know for sure that it’s the AI fuckwits.
Also, the devil in me thinks it’s funny to swap out the repo in question for something entirely different. :-D
Oh wow, that 48 hours timelapse from SDO is super cool: https://social.bund.de/system/media_attachments/files/114/413/834/747/006/466/original/91b1698392ae5188.mp4 At the end, the moon is whizzing by.
@xuu@txt.sour.is Hahaha, that’s cool! You were (and still are) way ahead of me. :-)
We started with a simple traffic light phase and then added pedestrian crossing buttons. But only painting it on the canvas. In our computer room there was an actual traffic light on the wall and at the very end of the school year our IT basics teacher then modified the program to actually control the physical traffic light. That was very impressive and completely out of reach for me at the time. That teacher pulled the first lever for me ending up where I am now.
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…
@prologic@twtxt.net Exactly, @bender@twtxt.net! :-D This is at the entrance of a veggie farm (11 & 12) where there are free-ranging kids playing on the road, so people should slow down when driving there to buy some supplies. I also wondered why the sign says “Halt!” instead of “Langsam fahren!” (Drive slowly!) or something like that. On second thought, maybe to actually park there on the street right at the property line.
I actually never walked on that road before and discovered that this was a dead end. There’s usually at the very least a foot path on which to continue when passing a farm. Not this time, though. I didn’t want to stamp down the high grass to cut across country, so I had to walk back maybe 150 meters. Not too bad.
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
@prologic@twtxt.net Phew, I’m indeed not twtxt.dev, because I sometimes actually do edit my feed with vim like a barbarian.
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 Can you please draft up a specification for that proposed change with all the details? Such as which date do you actually refer to? Is it now()
or the message’s creation timestamp? I reckon the latter is the case, but it’s undefined right now. Then we can discuss and potentially tweak the proposal.
Also, I see what you did there in regards to the reply model change poll. ]:->
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
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 🤔
yarnd
powering this pod twtxt.net 🧐
Or rather, https://txt.sour.is/conv/a36exfa.
@bender@twtxt.net It’s pretty cool though 🤣