# 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 10
# self = https://watcher.sour.is/conv/tugbvia
From now on, my twtxt feed is gpg signed. I hope this works for everyone.
From now on, my twtxt feed is gpg signed. I hope this works for everyone.
@sdk It won't work mate -- There is no formalized spec for this and no consensus around signing a feed.
@sdk It won't work mate -- There is no formalized spec for this and no consensus around signing a feed.
@sdk for what I can see you signature is broken, your feed has two signature blocks. As @prologic said, it means close to nothing as is.
@sdk No client verifies it automatically, but at least it doesn’t break anything. I did that for a while, too. But as the other guys said, without automatic verification, it’s not very useful. 😐
@sdk No client verifies it automatically, but at least it doesn’t break anything. I did that for a while, too. But as the other guys said, without automatic verification, it’s not very useful. 😐
@sdk No client verifies it automatically, but at least it doesn’t break anything. I did that for a while, too. But as the other guys said, without automatic verification, it’s not very useful. 😐
@movq @sdk We will be working on a spec for encryption and signing -- There is at least a draft spec in progress -- Needs more eyes on it, but we're basing it on the use of Saltpack
@movq @sdk We will be working on a spec for encryption and signing -- There is at least a draft spec in progress -- Needs more eyes on it, but we're basing it on the use of Saltpack