# 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/5l2lqta
Just added support for deleting and editing arbitrary Twt(s) at anypoint in your timeline. Some things to note:
- I'm not really that happy with the code between PostHandler() and DeleteTwtHandler() anymore 😢 It _really_ needs some major refactoring, and better tests.
- This only works for users (_for now_), no support for Persona(s) / Feeds sorry.
One side-effect I've noticed (_which was always the case_); an Edited Twt whilst preserves the original timestamp, gets appended to your feed at the bottom of the file. This is counter intuitive when you think about editing text files with a text editor, but it does make sense in the way yarnd treats feeds as append-only (_I had just forgotten_). I'm not doing anything about this though.
Just added support for deleting and editing arbitrary Twt(s) at anypoint in your timeline. Some things to note:
- I'm not really that happy with the code between PostHandler() and DeleteTwtHandler() anymore 😢 It _really_ needs some major refactoring, and better tests.
- This only works for users (_for now_), no support for Persona(s) / Feeds sorry.
One side-effect I've noticed (_which was always the case_); an Edited Twt whilst preserves the original timestamp, gets appended to your feed at the bottom of the file. This is counter intuitive when you think about editing text files with a text editor, but it does make sense in the way yarnd treats feeds as append-only (_I had just forgotten_). I'm not doing anything about this though.
@prologic what is the side effect of this for others not using Yarn? Right now conversations break upon editing, wouldn’t this potentially cause more havoc? Wouldn’t the specification need to be extended somehow to force a refresh of any edited twtxt?
@bender Nothing that isn't already a known side effect. Really it is up to clients to figure this out and have storage or caching mechanisms that can cope with diverging threads.
@bender Nothing that isn't already a known side effect. Really it is up to clients to figure this out and have storage or caching mechanisms that can cope with diverging threads.