# 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 6
# self = https://watcher.sour.is/conv/bmuejga
Speaking of Yarn and/or Twtxt + Activity Pub integration... Been thinking... If a decision is made to turn this into a full-fledged Twtxt bridging services between Twtxt <-> Activity Pub (_which would make things much more transparent, because then yarnd only has to speak Twtxt period_)...
What do we (_or can we_) do about filling in context. Right now with this crappy half-baked implementation I have going (_experimental_) for yarnd, I can just go grab the Activity Pub Note that the inReplyTo references and inject that into the cache.
With a separate more transparent Twtxt <-> Activity Pub; what do we do? Even if we created a feed for the actor referenced in the inReplyTo you wouldn't know to follow them anyway...
Hmmm? 🤔
Speaking of Yarn and/or Twtxt + Activity Pub integration... Been thinking... If a decision is made to turn this into a full-fledged Twtxt bridging services between Twtxt <-> Activity Pub (_which would make things much more transparent, because then yarnd only has to speak Twtxt period_)...
What do we (_or can we_) do about filling in context. Right now with this crappy half-baked implementation I have going (_experimental_) for yarnd, I can just go grab the Activity Pub Note that the inReplyTo references and inject that into the cache.
With a separate more transparent Twtxt <-> Activity Pub; what do we do? Even if we created a feed for the actor referenced in the inReplyTo you wouldn't know to follow them anyway...
Hmmm? 🤔
@prologic I have thought briefly about this. I have no idea how this could be done with the current twtxt thread paradigm.
@prologic I'm probably wildly off as I don't know how this is all implemented exactly, but it sounds like something the bridge itself will have to handle.
@mckinley I'm not sure it can be. It doesn't make sense to me to create feeds for some other actor just because.
@mckinley I'm not sure it can be. It doesn't make sense to me to create feeds for some other actor just because.