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 ๐คฆโโ๏ธ_
yarnd very soonโข for this change, with a if the date is >= 2025-07-01 then compute_new_hashes else compute_old_hashes
tt2 from @lyse and Twtxtory from @javivf?
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~
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
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 ๐ค
16? ๐ง
yarnd powering this pod twtxt.net ๐ง
# type = bot and optionally # retention = N so that feeds like @tiktok 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.
$ bat https://twtxt.net/twt/edgwjcq | jq '.subject'
"(#yarnd)"
hahahahaha ๐คฃ Does your client allow you to do this or what? ๐ค
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 ๐คฃ
I'll think about doing this too, but I have to do it carefully so as not to cost too much in terms of resources or performance...
- Drift into Failure: From Hunting Broken Components to Understanding Complex Systems by Sidney Dekker (2011)
- Engineering a Safer World by Nancy Leveson (2011)
The former I haven't read. The later I haven't finished reading ๐
- asynchronous evolution
- drift into failure
yarnd: pods establish cryptographic identities, exchange signed /info and /twt payloads with signature verification, ensuring authenticity, integrity, and spoof-proof identity validation across the distributed network.
cacher branch? ๐ค It is recommended you take a full backup of you pod beforehand, just in case. Keen to get this branch merged and to cut a new release finally after >2 years ๐คฃ
yarnd ๐คฃ Nice! ๐
twtxt.net feels very clear of late hmmm ๐ง This is good right? ๐