https://movq.de/v/5c51be2cd3/s.png
https://movq.de/v/5c51be2cd3/s.png
https://movq.de/v/5c51be2cd3/s.png
https://movq.de/v/5c51be2cd3/s.png
https://gitlab.com/muttmua/mutt/-/issues/131
They closed it because the solution was supposed to be implemented in terminals … Apparently, that never happened?
https://gitlab.com/muttmua/mutt/-/issues/131
They closed it because the solution was supposed to be implemented in terminals … Apparently, that never happened?
https://gitlab.com/muttmua/mutt/-/issues/131
They closed it because the solution was supposed to be implemented in terminals … Apparently, that never happened?
https://gitlab.com/muttmua/mutt/-/issues/131
They closed it because the solution was supposed to be implemented in terminals … Apparently, that never happened?
https://staystrong.run/user/bmallred/twtxt.txt returned 200 but no Last-Modified header - can’t cache content :-)Another modification I made is to actually cache it anyways. Otherwise,
tt wouldn't show anything. I implemented that for some other feed that doesn't exist anymore.
Screenshot of neomutt running jenny, a twtxt client
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.
Just curious, how are you accomplishing this? Using egress
iptables blocks?
yarns (_the search engine_) 😢
yarns (_the search engine_) 😢
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!" 🤣
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!" 🤣
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"
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"
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. 🤷🏻♂️
yarnd peers with each pod in its own network to do exactly that. Maybe we could open up the protocol and you could potentially pee with other pods?
yarnd peers with each pod in its own network to do exactly that. Maybe we could open up the protocol and you could potentially pee with other pods?
yarnd has never implement automatic un-following for this very reason. It's hard (likely impossible) to get 100% right.
yarnd has never implement automatic un-following for this very reason. It's hard (likely impossible) to get 100% right.
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!
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!