# 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 13
# self = https://watcher.sour.is/conv/4nrpsdq
@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 concur 👌
> 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. 🤔
This is the primary reason I'm pulling activity pub support out of yarnd. I _may_ (_and it was planned_) still build a completely separate service the abstract away the "push" nature of ActivityPub forcing our usage/interaction of it to be "pull" based. We'll see 🤔
@movq Yeah I concur 👌
> 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. 🤔
This is the primary reason I'm pulling activity pub support out of yarnd. I _may_ (_and it was planned_) still build a completely separate service the abstract away the "push" nature of ActivityPub forcing our usage/interaction of it to be "pull" based. We'll see 🤔
@movq Yeah I concur 👌
> 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. 🤔
This is the primary reason I'm pulling activity pub support out of yarnd. I _may_ (_and it was planned_) still build a completely separate service the abstract away the "push" nature of ActivityPub forcing our usage/interaction of it to be "pull" based. We'll see 🤔
@prologic you're planning to stop AP support before doing the bridge?
@prologic you're planning to stop AP support before doing the bridge?
@marado Maybe we can leave the code for now until we build the bridge? 🤔
@marado Maybe we can leave the code for now until we build the bridge? 🤔
@marado Maybe we can leave the code for now until we build the bridge? 🤔