There is a lot of resistance to the idea. The browser UX for registering protocols is not particularly intuitive. The protocol should not be named after Mastodon because they are defensive of their trademark, and it wouldn't be accurate since the user identifier could be followed from any ActivityPub compatible software.
If you look at the newer comments on the Mastodon github thread I posted you can see web+ap:// recommended, or apub://
I think there just needs to be enough collective will to make this happen. Likely another project will need to take the lead because Mastodon team has decided the browser UX is too much of a barrier. Maybe glitch-soc can do a proof of concept.
The API for following a user is not ActivityPub but is actually specific to Mastodon (and the platforms using a compatible API like Pleroma). ActivityPub only provides the server-to-server delivery of messages (a client-to-server protocol exists but is not used by Mastodon or basically anyone else).
Thanks for the Mastodon issue link! The misskey ticket seems different.
Thinking about this more, it is probably easy to write a browser extension or userscript to make "follow" links take me to my own instance. I will look into it.
Oh interesting I didn't realize. Are you talking about the `/api/v1/accounts/:id/follow` endpoint? I would have assumed it used the ActivityPub Follow activity but I'm not familiar enough with it. (https://www.w3.org/TR/activitypub/#follow-activity-outbox)
Just to be clear I'm not talking about the client-to-server interaction but the server-to-server follow interaction.
I think we're talking past each other a bit. I know we were talking about browsers but then you mentioned the API for following. There's two ways to interpret that: the way the client communicates the request to follow to its home server, or the way that server contacts the other server to take the follow action. I'm asking you which you were referring to when you say it's Mastodon specific.
The web browser protocol would only need to take you to the user's profile on your home server. The actions you request with your client after that are a separate step.
on Mastodon: https://github.com/mastodon/mastodon/issues/19679 on Misskey: https://github.com/misskey-dev/misskey/issues/9504
There is a lot of resistance to the idea. The browser UX for registering protocols is not particularly intuitive. The protocol should not be named after Mastodon because they are defensive of their trademark, and it wouldn't be accurate since the user identifier could be followed from any ActivityPub compatible software.
If you look at the newer comments on the Mastodon github thread I posted you can see web+ap:// recommended, or apub://
I think there just needs to be enough collective will to make this happen. Likely another project will need to take the lead because Mastodon team has decided the browser UX is too much of a barrier. Maybe glitch-soc can do a proof of concept.