# 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 7
# self = https://watcher.sour.is/conv/ugpi43a
Thanks @david I was already aware of the AWS Blog Post itself, but I'm glad you linked this to me anyway on IRC, because I _actually_ "listened" to the blog post via -- As much as I don't like to rely on "Cloud Services" Amazon Polly is kind of cool here π
Thanks @david I was already aware of the AWS Blog Post itself, but I'm glad you linked this to me anyway on IRC, because I _actually_ "listened" to the blog post via -- As much as I don't like to rely on "Cloud Services" Amazon Polly is kind of cool here π
@prologic hmm, I don't understand your twt asking "Anyone have any other details on this story from AWS with their EFS and sub-millisecond latencies? Apparently the story posted on /. was a dupe, but I canβt find the original one" then. The "story" was simply the blog post I linked you on IRC, nothing else. It was posted twice on Slashdot. This one, and this one.
So... There is some thinking amongst the community that there _might_ not be a lot of technical marvel here with AWS EFS and their sub-millisecond latency at all. It _might_ very well just be a giant cache in front of EFS. Which is kinda what I was thinking too.
So... There is some thinking amongst the community that there _might_ not be a lot of technical marvel here with AWS EFS and their sub-millisecond latency at all. It _might_ very well just be a giant cache in front of EFS. Which is kinda what I was thinking too.