> Mentions are embedded within the text in either @
So the lextwt parser we use will simply call this an invalid mention, which it does.
> Mentions are embedded within the text in either @
main π€£ I'm fixing little things here and there. Also please report bugs π
* 101f3eb0 - (HEAD -> main) Fix a bunch of UX to do with following/unfollowing, bookmarking and unbookmarking (3 seconds ago) <James Mills>
Testing UI/UX is hardβ’ π
yarnd.
main recently? π€
q or a π€£
git checkout main && git pull, rebuild and redeploy: make build, and however you deploy. π Lots of fixes (_no more stalling_) and optimizations to the feed fetcher, smoother cpu usage, better internal metrics.
main. I merged the catcher branch already!
git checkout main && git pull && make build. Few bug fixes π
π Can I imply you're not interested in things like "LIke", "Report", etc?! π
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?
> where did this hash come from?
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.
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.
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.