# 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 20
# self = https://watcher.sour.is/conv/n2wah6a
So, I don’t get replying to feeds. Two reasons: they can’t reply back, and the reply context is lost across pods (because not all pods follow the same feeds). Is there a reasonable solution?
@prologic see this twt of yours, for example.
I mean, feeds are one way only. The Dilbert feed will never reply to you, correct? And, as you can see, there is no context for it once I see it in my pod.
Of course, same will apply if you interact with someone you follow, but I don’t, whether is a feed or not. That is the inherent drawback of twtxt. If it catches on, then this drawback has the potential to grow fairly unmanageable.
I don’t think there is a solution for this right? I mean, I can’t subscribe to everyone’s feeds, so that I can see contexts on yarns.
Ahh I see what you’re saying 🤔
Ahh I see what you’re saying 🤔
I _think_ this is the same issue @ullarah described the other day using different verbage.
I _think_ this is the same issue @ullarah described the other day using different verbage.
But it's something that isn't _actually_ related to Twtxt at all per se, it's more of a "feature of decentralised" systems. NOTE: We've made no claims that Yarn.social is "distributed", Twt Hashes are distributed between pods and identical as-long as pods subscribe to the same feeds, but this is in no-way a "distributed" system, only a "decentralised" one.
But it's something that isn't _actually_ related to Twtxt at all per se, it's more of a "feature of decentralised" systems. NOTE: We've made no claims that Yarn.social is "distributed", Twt Hashes are distributed between pods and identical as-long as pods subscribe to the same feeds, but this is in no-way a "distributed" system, only a "decentralised" one.
That being said thought, as I said in yarn:#o3syyvq -- I _think_ this is something we can solve -- As I see this as a "client" behaviour. For example the more I think about this the more I realise to myself:
> Why can't a pod look up the chain of Twts in a Yarn, figure out which feeds it might have no knowledge about and temporarily fetch those on demand to fill in missing "blanks".
That being said thought, as I said in yarn:#o3syyvq -- I _think_ this is something we can solve -- As I see this as a "client" behaviour. For example the more I think about this the more I realise to myself:
> Why can't a pod look up the chain of Twts in a Yarn, figure out which feeds it might have no knowledge about and temporarily fetch those on demand to fill in missing "blanks".
@prologic if “filling the blanks” was possible to provide the context, I am all for it!
And since the network has significantly more pods in the wild now and potentially _willing_ participant Pod Owner/Operators of said pods, we _could_ start to experiment with these ideas and make this work 👌
And since the network has significantly more pods in the wild now and potentially _willing_ participant Pod Owner/Operators of said pods, we _could_ start to experiment with these ideas and make this work 👌