# 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 1
# self = https://watcher.sour.is/conv/ntvcxtq
Ask HN: Would you (do you) use an unsafe HTTP API?**
What I mean by "unsafe" is that the API lacks protection from the lost update[1] problem, and the answer is obviously "yes".
APIs that implement protections (like If-None-Match and the ilk) aren't uncommon, but they are the minority as far as I can tell by perusing documentation over the years. Why? It seems inevitable that lost updates have been causing problems, but perhaps never at a level that rises to the level of doing something about it?
[1] https://www.w3.org/19 ... ⌘ Read more