# 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 12
# self = https://watcher.sour.is/conv/chlfccq
@sorenpeter curious why you at mentioned a timestamp? π€
@sorenpeter curious why you at mentioned a timestamp? π€
@2024-10-09T08:11:00Z It an easy way of twt-adressing by using the timestamp instead of a nick, which is arbitrary anyhow. Just my suggestion for a new reply-model ;)
@2024-10-09T08:11:00Z It an easy way of twt-adressing by using the timestamp instead of a nick, which is arbitrary anyhow. Just my suggestion for a new reply-model ;)
@2024-10-09T08:11:00Z It an easy way of twt-adressing by using the timestamp instead of a nick, which is arbitrary anyhow. Just my suggestion for a new reply-model ;)
@2024-10-09T08:11:00Z It an easy way of twt-adressing by using the timestamp instead of a nick, which is arbitrary anyhow. Just my suggestion for a new reply-model ;)
@sorenpeterdarch.dk It doesn't workπ€£ No other clients
Support this π
@sorenpeterdarch.dk It doesn't workπ€£ No other clients
Support this π
I know no client support it (yet) - but it could be the future π
I know no client support it (yet) - but it could be the future π
I know no client support it (yet) - but it could be the future π
I know no client support it (yet) - but it could be the future π