@prologic@twtxt.net @thecanine@twtxt.net (#6gszxta) The only problem with time-based approaches is that if a feed is down for some reason (or just not fetched in time) you might miss older twts you haven’t seen. Depending on the use case that might even be a feature to ignore outdated content. In my client I just mark every twt read and the next time I start it, all fully read conversations will be hidden.


(#dewqhaa) Didn’t disappear but my pod may have restarted 😂

It’s not just a perk of being on a new platform I don’t think. We’ve gone out of our way to build and design for small interconnected communities of pods.


(#7x6gora) @thecanine@twtxt.net The thing is if you stick around long enough you’ll get to understand and find out the reasons why we made certain decisions and choices along the way 🤗 many of which actually have significant social impacts on individuals and groups of people ☺️


@prologic@twtxt.net (#cdl6foa) I agree on a release process. However, I’m not so sure on the code signing part. M$ lately signed rootkits again. So it’s more a false sense of security. Could be a different story for your own code, though, as there’s no other party involved. Need to think about that a bit more.


@prologic@twtxt.net (#6gszxta) :-D Don’t get me wrong, the idea isn’t bad at all, maybe just needs slight tweaking. Like maybe showing the new unread twts in that conversation if you’re logged in. But I think there’s no concept of read/unread twts in yarnd, so well, probably won’t work, but could be useful I reckon. It’s just an appearance issue.


(#7x6gora) @thecanine@twtxt.net Oh hahah 😂 And you’ve discovered the the side-effect of how this all works. 😂 Since Yarn.social is actually based on and around the Twtxt spec, it has some of its drawbacks, however we also did a lot of work to extend the spec and support what was needed to actually make it viable and useful. The web interface of yarnd only lets users edit their “last post” for a couple of reasons, it’s hard to go back to more than just the last line and it has consequences like changing the hashes 😂


@prologic@twtxt.net (#gyxy4ta) So that’s not too bad. But skimming over Cache.FetchTwts(…) reveals that the cache isn’t touched when the parsing of the feed fails. Assuming that an invalid feed produces an error (might be wrong, didn’t investiage any further), the cache is not populated, triggering a fetch each time somebody visits the profile.