# 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 8
# self = https://watcher.sour.is/conv/ecusyya
@movq I think subscribing to the tweets endpoint is a better idea, as accessing the users endpoint can be done easily if wanted, and would be pretty easy to make a short script to subscribe to all users from the registry. So parsing the tweets endpoint (could be the mentions endpoint if wanted, any endpoint that uses the format as the tweets endpoint would be valid) and adding another parameter to that specific follow, (maybe a special 'registry' user, (I think it should check if the user starts with registry, to be able to have multiple registries), and then jenny would just check the registry and handle the messages using the data in those endpoints, changing the user and twtxt url acordingly.
@jmjl Hmmmmmmm, I’m not sure. 🤔 Other than what @prologic said, I think this could be one of those features that open the gates for spam. You don’t really have control anymore over which people you follow, so anyone could come along, push twts to that registry and thus spam your timeline. (Hence jenny would also need a *mute* feature.)
twtxt is very *pull*-based at the moment. In my eyes, this is a core feature. Making it *push*-based changes the game a lot. 🤔
I get the appeal, though. Discovering new people doesn’t work that well *inside of twtxt*. You need external tools for that.
@jmjl Hmmmmmmm, I’m not sure. 🤔 Other than what @prologic said, I think this could be one of those features that open the gates for spam. You don’t really have control anymore over which people you follow, so anyone could come along, push twts to that registry and thus spam your timeline. (Hence jenny would also need a *mute* feature.)
twtxt is very *pull*-based at the moment. In my eyes, this is a core feature. Making it *push*-based changes the game a lot. 🤔
I get the appeal, though. Discovering new people doesn’t work that well *inside of twtxt*. You need external tools for that.
@jmjl Hmmmmmmm, I’m not sure. 🤔 Other than what @prologic said, I think this could be one of those features that open the gates for spam. You don’t really have control anymore over which people you follow, so anyone could come along, push twts to that registry and thus spam your timeline. (Hence jenny would also need a *mute* feature.)
twtxt is very *pull*-based at the moment. In my eyes, this is a core feature. Making it *push*-based changes the game a lot. 🤔
I get the appeal, though. Discovering new people doesn’t work that well *inside of twtxt*. You need external tools for that.
@movq Yeah, I guess then I'd have to make some system to tailor my requirements. So yeah it'll open up the gates for spam I guess, depending on how it's configured.