Post

@evan Thank you, I'll read through this!

@stefan

Activity Intents.

You want FEP-3b86 - Activity Intents: https://w3id.org/fep/3b86

It's gaining broad support from:

* Mastodon
* Wordpress
* Loops
* Friendica
* Emissary
* Forte
* Mitra
* PieFed
* (streams)

And there's two client libraries in the works. Mine is https://github.com/EmissarySocial/camperjs - it starts with intents, then falls back oStatus, then to known endpoints for older servers.

I'd love to work with you to see it solve this issue on your sites.

This shows me:

"aliases": [
"https://server.social/@user",
"https://server.social/users/user"
]

and

{
"rel": "http://ostatus.org/schema/1.0/subscribe",
"template": "https://server.social/authorize_interaction?uri={uri}"
}

So I know I should link to https://server.social/authorize_interaction?uri=https://RemoteServer.social/@ExternalUser

And I am fairly confident this will work. But I'd rather not ask people to put in their usernames, I'd hope I can figure this out from their server's domain?

Shouldn't the "subscribe" template be the same for all accounts on the same server/platform?

Maybe I could ask for the domain, determine the platform via nodeinfo, and then keep a list of URLs, eg if server.social runs on Mastodon, use the Mastodon "authorize_interaction" URL, for Friendica, it's "contact/follow", Misskey uses "authorize-follow", etc.

Is there such a list?