# 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 11
# self = https://watcher.sour.is/conv/s5r44ma
@fastidious Oh But somehow @lyse saw the old Twt and replied to that 🤦♂️
This is the downside of not fetching often enough or refreshing just in case a feed has changed your replying to hmmm 🤔
@fastidious Oh But somehow @lyse saw the old Twt and replied to that 🤦♂️
This is the downside of not fetching often enough or refreshing just in case a feed has changed your replying to hmmm 🤔
@prologic I have thought about this because even though it doesn’t happen often, when it does it bothers me greatly. I haven’t found a solution. How about you? What could be done to avoid this from happening?
I know we have been over this in more than one occasion. Ideas about editing timeouts, or not allowing to edit/delete came up, but were quicky discarded as absurd.
@fastidious Only thing I can think of is to warn a user if their feed has already been fetched 🤔
Only other thing that will work is to also insert the new Twt into your Pod’s archive and not just the Cache so peering will work as expected 👌
@fastidious Only thing I can think of is to warn a user if their feed has already been fetched 🤔
Only other thing that will work is to also insert the new Twt into your Pod’s archive and not just the Cache so peering will work as expected 👌
@prologic how about offering a preview, with the option to go back and edit, before the twt gets posted? It might not fully eliminate the issue, but reduce it to the point we might see a disconnected twt every once in a Blue Moon.
@fastidious my second suggestion would work and it’s only a couple of lines of code so why don’t we try that first?
@fastidious my second suggestion would work and it’s only a couple of lines of code so why don’t we try that first?
@prologic by all means, of course. I was just throwing an idea, to spark some yarning. So, we test this tomorrow? :-)