Open Question: Profile Pages/HTTP URIs #16

Open
opened 2 years ago by malacoda · 0 comments
malacoda commented 2 years ago
Owner

Currently local accounts on a Who Server are exposed as acct: URIs, which resemble email addresses. There isn't (right now) a plan to support profile pages, or expose an HTTP URI for accounts on the Who Server.

I feel like full-fledged profile pages are out of scope for Who Server, but maybe we could exposes an HTTP URI specifically for consumption by other Who Servers or IndieAuth relying parties, or as a RelMeAuth delegate. So, for example, acct:sterling@archer.com and https://archer.com/users/sterling can be synonymous. The question then is what are the contents of this page? Blank? JSON? hCard? Blank except for a hidden authorization_endpoint?

Currently local accounts on a Who Server are exposed as `acct:` URIs, which resemble email addresses. There isn't (right now) a plan to support profile pages, or expose an HTTP URI for accounts on the Who Server. I feel like full-fledged profile pages are out of scope for Who Server, but maybe we could exposes an HTTP URI specifically for consumption by other Who Servers or IndieAuth relying parties, or as a RelMeAuth delegate. So, for example, `acct:sterling@archer.com` and `https://archer.com/users/sterling` can be synonymous. The question then is what are the contents of this page? Blank? JSON? hCard? Blank except for a hidden `authorization_endpoint`?
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.