# 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/5gagcea
@xuu So... From a practical perspective, wouldn't it make sense to have related identifiers that are "related" to the subject? Hence rel? If I were a user, I would expect to lookup only prologic@twtxt.net to find both my Yarn and Salty accounts and ways to follow or message me as such.
@xuu So... From a practical perspective, wouldn't it make sense to have related identifiers that are "related" to the subject? Hence rel? If I were a user, I would expect to lookup only prologic@twtxt.net to find both my Yarn and Salty accounts and ways to follow or message me as such.
@xuu So... From a practical perspective, wouldn't it make sense to have related identifiers that are "related" to the subject? Hence rel? If I were a user, I would expect to lookup only prologic@twtxt.net to find both my Yarn and Salty accounts and ways to follow or message me as such.
@xuu So... From a practical perspective, wouldn't it make sense to have related identifiers that are "related" to the subject? Hence rel? If I were a user, I would expect to lookup only prologic@twtxt.net to find both my Yarn and Salty accounts and ways to follow or message me as such.
@prologic you need to write more like this. No errors, no emoji, no *stylised* words. Ah, yes, so much easier to read. Keep it up!
@bender I often do when I'm rather serious and well when I'm not trying to convey "emotion" 😅