# 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 5
# self = https://watcher.sour.is/conv/vcsqa4a
@darch it is the same, split it or not. The aim is to make it fit for everyone while on mobile, and to have it show consistently the same for everyone. Right now it wraps for long pod domains, and it doesn’t for short ones. The approach being talked about fixes that. The alternative is to elipse it, just like the twt context is being ellipsed now.
@fastidious ah you beat me to it haha. So what is the deciding factor? Do we have @prologic bang the gavel on a decision or? 😅
@ullarah the implementer decides, in my opinion. If I were doing it, I would place the pod domain on the second line, and ellipse it if it is so huge that overflows to yet another line (very rare but possible).
Using an… Isn’t actually a bad idea really for long domains
Using an… Isn’t actually a bad idea really for long domains