# 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 26
# self = https://watcher.sour.is/conv/el5mh5a
@cel any takers to help me with this work? 🤔
@cel any takers to help me with this work? 🤔
@cel any takers to help me with this work? 🤔
@cel any takers to help me with this work? 🤔
@prologic eight people interacted (six stars/favourites and four boosts/reblogs) but no replies that I see.
@prologic What's your current plan/concept on this?
But.... I'm a bit more convinced that it _might_ be possible to create a Twtxt <-> ActivityPub bridge as a separate optional (opt-in) service for Yarn.social users -- Hell I _think_ it might be possible in general for any self-hosted Twtxt users that self-host their own feed (_without yarnd_).
But.... I'm a bit more convinced that it _might_ be possible to create a Twtxt <-> ActivityPub bridge as a separate optional (opt-in) service for Yarn.social users -- Hell I _think_ it might be possible in general for any self-hosted Twtxt users that self-host their own feed (_without yarnd_).
But.... I'm a bit more convinced that it _might_ be possible to create a Twtxt <-> ActivityPub bridge as a separate optional (opt-in) service for Yarn.social users -- Hell I _think_ it might be possible in general for any self-hosted Twtxt users that self-host their own feed (_without yarnd_).
But.... I'm a bit more convinced that it _might_ be possible to create a Twtxt <-> ActivityPub bridge as a separate optional (opt-in) service for Yarn.social users -- Hell I _think_ it might be possible in general for any self-hosted Twtxt users that self-host their own feed (_without yarnd_).
@prologic Awesome. We need to catch up. Hoping to make it tomorrow maybe.
@prologic that would be very nice, and remove the need to have more services running. I think it would attract more people to run this to use that, sunce yarnd is very easy to set up and run.
@stigatle Do you think it should directly be integrated into yarnd or a separate service / binary / project? 🤔 Opt-in or Opt-out?
@stigatle Do you think it should directly be integrated into yarnd or a separate service / binary / project? 🤔 Opt-in or Opt-out?
@stigatle Do you think it should directly be integrated into yarnd or a separate service / binary / project? 🤔 Opt-in or Opt-out?
@stigatle Do you think it should directly be integrated into yarnd or a separate service / binary / project? 🤔 Opt-in or Opt-out?
@prologic personally I would like it integrated and opt-in. just enable with a flag when starting up yarnd.
@prologic a separate binay would work too, maybe yarnd could just start it. if its a separate project - then it could possibly be useful for others as well? Im not sure, Im just thinking - the easier it is to set up and run - the better it is for everyone. Im sure it can be easy to set up and use either way.
@stigatle The reason I was thinking about a separate binary / project / service is to bring along our Twtxt friends like @movq and @lyse and anyone else that self-hosted their Twtxt feed on their own. But this of course has added complexities like spinning up yanrd along with whatever this thing will be called configuring the two and connecting them. Fortunately however yarnd already does this with the feeds service and defaults to using feeds.twtxt.net -- So we would so something similar there too. Further thoughts? 🤔
@stigatle The reason I was thinking about a separate binary / project / service is to bring along our Twtxt friends like @movq and @lyse and anyone else that self-hosted their Twtxt feed on their own. But this of course has added complexities like spinning up yanrd along with whatever this thing will be called configuring the two and connecting them. Fortunately however yarnd already does this with the feeds service and defaults to using feeds.twtxt.net -- So we would so something similar there too. Further thoughts? 🤔
@stigatle The reason I was thinking about a separate binary / project / service is to bring along our Twtxt friends like @movq and @lyse and anyone else that self-hosted their Twtxt feed on their own. But this of course has added complexities like spinning up yanrd along with whatever this thing will be called configuring the two and connecting them. Fortunately however yarnd already does this with the feeds service and defaults to using feeds.twtxt.net -- So we would so something similar there too. Further thoughts? 🤔
@stigatle The reason I was thinking about a separate binary / project / service is to bring along our Twtxt friends like @movq and @lyse and anyone else that self-hosted their Twtxt feed on their own. But this of course has added complexities like spinning up yanrd along with whatever this thing will be called configuring the two and connecting them. Fortunately however yarnd already does this with the feeds service and defaults to using feeds.twtxt.net -- So we would so something similar there too. Further thoughts? 🤔