# 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 9
# self = https://watcher.sour.is/conv/7boroia
@caesar Let's put it this way.. what's the worst that would happen if we do make this assumption that all user links are their own?
@caesar Let's put it this way.. what's the worst that would happen if we do make this assumption that all user links are their own?
@prologic when using rel=“me” it isn’t an assumption. It is a fact. There is no way to fake it.
@david i'm not really sure what you were implying here…
@david i'm not really sure what you were implying here…
@david I'm not sure what you mean. rel="me" is just an html attribute which makes a *claim* that the target of the link belongs to the same person. It doesn't *prove* it; unless it's reciprocal.
@prologic I *think* the "worst that could happen" is "it would be semantically wrong". I don't think it could ever be actively harmful, since it is correctly treated as a *claim*, not proof of ownership of the target – it can be used to prove ownership of the *origin* page, but not of the *destination*.

That said, I would be in favour of making it explicit (ideally in the Metadata spec) that "User Links" SHOULD be "connected to the feed or author", not just "usually". This would make the link metadata more semantically useful.
@caesar Makes sense 👌
@caesar Makes sense 👌