Screenshot of neomutt running Jenny, the best twtxt client
Screenshot of neomutt running Jenny, the best twtxt client
Screenshot of neomutt running Jenny, the best twtxt client
nice run. kept it pretty chill albeit humidity was a bitch. before ending my first loop another runner cruised by me and i resisted the urge to join (not that i could have maintained the pace or anything).
#running
nice run. kept it pretty chill albeit humidity was a bitch. before ending my first loop another runner cruised by me and i resisted the urge to join (not that i could have maintained the pace or anything).
#running
nice run. kept it pretty chill albeit humidity was a bitch. before ending my first loop another runner cruised by me and i resisted the urge to join (not that i could have maintained the pace or anything).
#running
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. 🤷🏻♂️