# 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/xzqnrla
When linking to a location that is a directory, I always add the trailing slash. Always. It seems that more than one host agrees with what I do—which isn't unique to me, many people does it, and has done it since the birth of the web, which is why I also do it. There is no reason to leave out the training slash other than sheer laziness.
@prologic ha, we found the lazy one! 😂 Did you read the page I linked? Some interesting finds there on the pros and cons of using the trailing slash, or not. I am old school, what can I say?
@david Hey, interesting link and discussion.
I think everything was screwed up when we stopped having the concept of directories, and the resources were not files, like on some Restful APIs and such.
And then the frameworks place their own ideas for managing routing. I've had the question, what's 'better'?
My preference as a user are shortest URLs although I get the point of the trailing slash and the correctness behind the absolute and relative links.
I leave this link as an additional ref https://blog.cdivilly.com/2019/02/28/uri-trailing-slashes
On the web I always use trailing slashes (unless I messed up) just as explained in the article. On the file system on the other hand I usually omit them, because my shell does, too.