@lyse@lyse.isobeef.org so, is it safe to assume you occasionally, but carefully, vet your feeds, and have contingencies in place to not keep requesting a seemingly dead feed over and over?

@bender@twtxt.net If you look at your Following list yarnd is continually improving the tools and data available to you especially regarding feed acailabiliry and maybe this helps you manage who/what you follow? 🤔 – I’ve certainly found it immediately useful!

@prologic@twtxt.net I understand. It is useful. But Lyse doesn’t use Yarn.

I think I am not successfully explaining the problem I perceive here. People checking non existing feeds with the hope they will come back, over and over, and no provisions in Yarn to do much about it. 🤷🏻‍♂️

@bender@twtxt.net No no, I get it. It’s just not as simple as any particular solution. Right now I don’t even know what the feed’s full URI was nor who on this pod (if at all) still follows it? I’ll bet it’s an inactive user right? Gimme the full URI was it was and I’ll have a poke at the DB? 🤔

I took a guess based on my shell history 🤣

prologic@JamessMacStudio
Thu Aug 22 20:50:32
~/Projects/yarnsocial/yarn
 (main) 0
$ ./tools/who_follows.sh 'https://arrakis.netbros.com/user/pedantic/twtxt.txt'
"darch follows https://arrakis.netbros.com/user/pedantic/twtxt.txt and was last seen 625 days ago"

@bender@twtxt.net Btw, as you know, one thing the yarnd client has always lacked is some kind of “in-app” notification of sorts. Something to inform the user, “hey, you know what feed you follow, it’s looking like it’s kind of dead, maybe consider unfollowing it!” 🤣

Correct, @bender@twtxt.net. Since the very beginning, my twtxt flow is very flawed. But it turns out to be an advantage for this sort of problem. :-) I still use the official (but patched) twtxt client by buckket to actually fetch and fill the cache. I think one of of the patches played around with the error reporting. This way, any problems with fetching or parsing feeds show up immediately. Once I think, I’ve seen enough errors, I unsubscribe.

tt is just a viewer into the cache. The read statuses are stored in a separate database file.

It also happened a few times, that I thought some feed was permanently dead and removed it from my list. But then, others mentioned it, so I resubscribed.