# 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 16
# self = https://watcher.sour.is/conv/knoga2q
caesar
twtxt.net
View Thread
@prologic have you considered adding `rel="me"` to "User Links"?
prologic
twtxt.net
View Thread
@caesar Hmmm? πŸ€” Please elaborate?
prologic
twtxt.net
View Thread
@caesar Hmmm? πŸ€” Please elaborate?
caesar
twtxt.net
View Thread
@prologic The `me` value of the HTML `rel` attribute indicates that the linked page is the same user's profile on another site. It's useful for identity consolidation, enabling things like RelMeAuth on the IndieWeb. So it would be nice to be able to have that attribute on links to one's own website (and to one's profiles on other sites) from the "User Links" section of our profiles here.
caesar
twtxt.net
View Thread
@prologic If you check out someone's GitHub profile that has a link to that person's own website, for example you'll find rel="me" on the link.
caesar
twtxt.net
View Thread
@prologic another nice example is how Mastodon show's a user's external link to their own website as "verified" if the target site includes a rel="me" link back to their Mastodon profile, since this "proves" that the person has control of the linked site. I think I've seen other sites use it for verification in the same way.
prologic
twtxt.net
View Thread
@caesar Sorry I understand how the rel=me attribute works and why it's important -- I guess I was missing something though in the back of my mind I didn't make clear...

Do we just assume that any User Link a user inputs into their profile or we find on their feed (it's actually part of the Metadata spec) should have a rel=me attr? πŸ€” Ca we make that assumption?
prologic
twtxt.net
View Thread
@caesar Sorry I understand how the rel=me attribute works and why it's important -- I guess I was missing something though in the back of my mind I didn't make clear...

Do we just assume that any User Link a user inputs into their profile or we find on their feed (it's actually part of the Metadata spec) should have a rel=me attr? πŸ€” Ca we make that assumption?
caesar
twtxt.net
View Thread
@prologic Ah sorry, gotcha. πŸ˜€
Hmm, you make an interesting point. I would assume that *most* links a user would add would be to their own profiles, but maybe not all?
The Metadata spec says "A link to some other resource which is often connected to the feed or author".
I think my inclination would be yes, add it to all of them, but I can also see that a user *could* put links there that aren't their own. πŸ€”
prologic
twtxt.net
View Thread
@caesar

> but I can also see that a user could put links there that aren’t their own. πŸ€”

This is my main concern. I don't _think_ we can make this assumption.

The Metadata spec on Links doesn't really allow for anything else besides a Title and URL anyway, so I'm not sure how we can deal with this except to have some Pod-specific behaviour we attach to the links? πŸ€” (some kind of UI/UX around the user indicating whether the link is in fact theirs and maybe a custom icon?) cc @ullarah
prologic
twtxt.net
View Thread
@caesar

> but I can also see that a user could put links there that aren’t their own. πŸ€”

This is my main concern. I don't _think_ we can make this assumption.

The Metadata spec on Links doesn't really allow for anything else besides a Title and URL anyway, so I'm not sure how we can deal with this except to have some Pod-specific behaviour we attach to the links? πŸ€” (some kind of UI/UX around the user indicating whether the link is in fact theirs and maybe a custom icon?) cc @ullarah
caesar
twtxt.net
View Thread
@prologic Hmm, short of "clarifying" the spec to specifically state that links *must* be to the user's own sites, it's hard to think of a universal solution. I think I'd still err towards *assuming* that links are to the user's own pages, since I think they will be in almost all cases, but obviously there's an argument to be made against making that assumption, too…
prologic
twtxt.net
View Thread
@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
twtxt.net
View Thread
@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?
ullarah
txt.quisquiliae.com
View Thread
@prologic We could have a external redirect message that states this is a link outside of this pod. I've seen that type of thing implemented on other services like Steam.
caesar
twtxt.net
View Thread
@ullarah Ugh, please no! 😫 As a user I hate those interstitial pages, because they add an unwanted step between me and the page I'm trying to get to, and they obscure the real target of the link (also they're often used for user tracking). And as a web geek I hate the fact that they break the semantic model of a link pointing to its real target, turning external links into faux internal ones.