# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 24
# self = https://watcher.sour.is/conv/v63droa
@movq Da fuq?! 😳 What feed is that?
@movq Da fuq?! 😳 What feed is that?
@movq Oh well yarnd didn't grow native support for Gopher feeds until recently, so it's unlikely any Yarn.social pods would be hitting it 😂 Although I want to hit it temporarily at least once now to see these posts 🤣
@movq Oh well yarnd didn't grow native support for Gopher feeds until recently, so it's unlikely any Yarn.social pods would be hitting it 😂 Although I want to hit it temporarily at least once now to see these posts 🤣
@movq This is hilarious! 🤣 😂
Whoever owns/runs that gopher server, why don't they just turn it off or remove that file? Seriously?! 🤦♂️
@movq This is hilarious! 🤣 😂\n\n \n\n \n\nWhoever owns/runs that gopher server, why don't they just turn it off or remove that file? Seriously?! 🤦♂️
@movq This is hilarious! 🤣 😂
Whoever owns/runs that gopher server, why don't they just turn it off or remove that file? Seriously?! 🤦♂️
@prologic I don’t have a clue! 🥴 Most of all, they had to install a new cronjob to do this. 🥴 Maybe some (older?) clients don’t cope very well with *unavailable* feeds, so the author thinks it’s friendlier to post those notices? 🤔
@prologic I don’t have a clue! 🥴 Most of all, they had to install a new cronjob to do this. 🥴 Maybe some (older?) clients don’t cope very well with *unavailable* feeds, so the author thinks it’s friendlier to post those notices? 🤔
@prologic I don’t have a clue! 🥴 Most of all, they had to install a new cronjob to do this. 🥴 Maybe some (older?) clients don’t cope very well with *unavailable* feeds, so the author thinks it’s friendlier to post those notices? 🤔
@movq @prologic Yeah, I had to unfollow just to see anything else in my timeline! 🙄
@movq Very rigorous argumentation. The original twtxt client offers are following command which then reports 404 alongside, but one has to do than manually. I was also wondering how I'm gonna implement all the subscription management in tt to help catch dead feeds.
@jlj You can also Mute a feed 😆
@jlj You can also Mute a feed 😆
@lyse My client mostly ignores failures during feed retrieval. Instead, it stores a “last seen” timestamp for each feed. Then I have an additional cronjob that prints those timestamps along with a little notice like “you haven’t seen this feed in a month”. Works quite well. In the beginning, I reported failures immediately, but that was too noisy. In my experience, twtxt feeds often disappear for a week or so, and then they come back and work fine. It’s probably because everybody is doing self-hosting and, well, private servers have lots of downtime. 🤷
@lyse My client mostly ignores failures during feed retrieval. Instead, it stores a “last seen” timestamp for each feed. Then I have an additional cronjob that prints those timestamps along with a little notice like “you haven’t seen this feed in a month”. Works quite well. In the beginning, I reported failures immediately, but that was too noisy. In my experience, twtxt feeds often disappear for a week or so, and then they come back and work fine. It’s probably because everybody is doing self-hosting and, well, private servers have lots of downtime. 🤷
@lyse My client mostly ignores failures during feed retrieval. Instead, it stores a “last seen” timestamp for each feed. Then I have an additional cronjob that prints those timestamps along with a little notice like “you haven’t seen this feed in a month”. Works quite well. In the beginning, I reported failures immediately, but that was too noisy. In my experience, twtxt feeds often disappear for a week or so, and then they come back and work fine. It’s probably because everybody is doing self-hosting and, well, private servers have lots of downtime. 🤷
@movq That seems like a good approach. twtxt also records the last download timestamp in its cache.