# 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 1
# self = https://watcher.sour.is/conv/rpl4qnq
{@https://lyse.isobeef.org/twtxt.txt>#pqia4ba} @vain @prologic (#yjtzdka) Nice "Good morning!" example, I didn't think of that! I always thought that there's a pretty much zero chance of two users creating the same twt at the same second. But your sample is actually quite likely to happen, especially if the twtxt universe grows. So, yeah, there are indeed candidates for potential hash collissions without the author information.