# 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 18
# self = https://watcher.sour.is/conv/akietaq
@movq FYI editing Twts won’t break conversations nearly as much as they used to. We fixed a lot of the issues a while ago now. I think the worst that happened is a forked conversation.
@movq FYI editing Twts won’t break conversations nearly as much as they used to. We fixed a lot of the issues a while ago now. I think the worst that happened is a forked conversation.
@prologic Hmmm, maybe it won’t break on yarn.social, but it will break in my client. 😂 What did you change on your end regarding threading?
@prologic Hmmm, maybe it won’t break on yarn.social, but it will break in my client. 😂 What did you change on your end regarding threading?
@prologic Hmmm, maybe it won’t break on yarn.social, but it will break in my client. 😂 What did you change on your end regarding threading?
@prologic Actually, I didn’t have my first coffee today. It won’t break with my client. 😴 🤦
@prologic Actually, I didn’t have my first coffee today. It won’t break with my client. 😴 🤦
@prologic Actually, I didn’t have my first coffee today. It won’t break with my client. 😴 🤦
@prologic @movq But it certainly will with mine. ;-)
@movq Eagerly archiving what is fetched. So if it changes that's okay, it'll just get forked.
@movq Eagerly archiving what is fetched. So if it changes that's okay, it'll just get forked.
@movq @lyse It should only fork conversations with your client too no?
@movq @lyse It should only fork conversations with your client too no?
@prologic Right. Unless, of course, I wipe my “cache” and refetch everything (which is not something that I do regularly).
@prologic Right. Unless, of course, I wipe my “cache” and refetch everything (which is not something that I do regularly).
@prologic Right. Unless, of course, I wipe my “cache” and refetch everything (which is not something that I do regularly).
@movq That's why pods have a "cache" (_held in memory_) and an archive (_held on disk_).
@movq That's why pods have a "cache" (_held in memory_) and an archive (_held on disk_).