# 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 5
# self = https://watcher.sour.is/conv/6on3rza
@falsifian @prologic @bender The twt was edited. In my cache, it also has hash st3wsda and it started like this:

(#yqke7sq) I've been sketching out some …

When fetching the feed *now*, the twt starts like this and the current twt gets the hash 6mdqxrq:

(#yqke7sq) I've been sketching out some …

This can’t be avoided, really. Publishing twts and then editing them is like doing a git push --force after rewriting the commit history. Chaos will ensue. 😅
@falsifian @prologic @bender The twt was edited. In my cache, it also has hash st3wsda and it started like this:

(#yqke7sq) I've been sketching out some …

When fetching the feed *now*, the twt starts like this and the current twt gets the hash 6mdqxrq:

(#yqke7sq) I've been sketching out some …

This can’t be avoided, really. Publishing twts and then editing them is like doing a git push --force after rewriting the commit history. Chaos will ensue. 😅
@falsifian @prologic @bender The twt was edited. In my cache, it also has hash st3wsda and it started like this:

(#yqke7sq) I've been sketching out some …

When fetching the feed *now*, the twt starts like this and the current twt gets the hash 6mdqxrq:

(#yqke7sq) I've been sketching out some …

This can’t be avoided, really. Publishing twts and then editing them is like doing a git push --force after rewriting the commit history. Chaos will ensue. 😅
@falsifian @prologic @bender The twt was edited. In my cache, it also has hash st3wsda and it started like this:

(#yqke7sq) I've been sketching out some …

When fetching the feed *now*, the twt starts like this and the current twt gets the hash 6mdqxrq:

(#yqke7sq) I've been sketching out some …

This can’t be avoided, really. Publishing twts and then editing them is like doing a git push --force after rewriting the commit history. Chaos will ensue. 😅
@movq right, there is no way to forbid anyone from editing their text files. There is no hand holding here. :-D Thank you very much for shedding light into this "mystery"!