# 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 6
# self = https://watcher.sour.is/conv/fujqeeq
I'm not super a fan of using json. I feel we could still use text as the medium. Maybe a modified version to fix any weakness.
What if instead of signing each twt individually we generated a merkle tree using the twt hashes? Then a signature of the root hash. This would ensure the full stream of twts are intact with a minimal overhead. With the added bonus of helping clients identify missing twts when syncing/gossiping.
Have two endpoints. One as the webfinger to link profile details and avatar like you posted. And the signature for the merkleroot twt. And the other a pageable stream of twts. Or individual twts/merkle branch to incrementally access twt feeds.
And to add close integration with salty/ratchet for realtime private chat
And to add close integration with salty/ratchet for realtime private chat
@xuu Yeah I agree changing or detracting from the underlying Twtxt format we use would ruin our other hard work 😢 Like Salty.IM 👌
@xuu Yeah I agree changing or detracting from the underlying Twtxt format we use would ruin our other hard work 😢 Like Salty.IM 👌
@xuu Yeah I agree changing or detracting from the underlying Twtxt format we use would ruin our other hard work 😢 Like Salty.IM 👌