Recent posts from feeds followed by sorenpeter@darch.dk
@sorenpeter you wrote:
"This might even be backward compatible with older (pre-yarn) clients."
Yarnd is as backwards compatible with older clients as this. I dare to say, even more so. 😅
Going to try and few up a few more UX bugs today with yarnd.
I wonder if this twtxt will kick Yarnd into working again. There is only one way to find out, right?
@prologic done! hey i got a question, you got any clue why my feeds aren't updating? maybe it has to do with the new cache flag but i messed with that a bit and didn't notice a difference. basically it's like i have to manually restart yarnd to see new posts it's really weird lol
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?
i don't think it's normal to have to restart my yarnd instance every time i wanna see new posts right
@prologic I have:
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
@bender 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 🤔
Interesting edit observed by the new yarnd powering this pod twtxt.net 🧐
søren peter mørch