-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve follow flow with custom web protocols (web+follow:username@host.tld) #14187
Comments
We used to register protocol handlers but stopped doing that because of a combination of it not being actually used much, and browser's UI being off-putting: #8127 |
Oh, so sad. I think it is Hen/Egg problem. If there is no service using it, I think it will not improve. |
This should be re-added but not after 5 minutes but with a button at a good place. |
👍 to having a button in a good place. I'd put it under preferences. however, a bigger issue is that websites can't just provide a fallback handler like they can provide base URLs for anchors. see also whatwg/html#4584 |
@SoniEx2 you are right... the implementation is far from perfect, but I think a platform like mastodon (or the complete fediverse) would (hopefully) give some importance to the custom protocol handler and would help to improve the spec and the current browser implementations. ...but I would recommend to not use |
yeah. |
I've added a suggestion on the Mozilla side for first party |
see also #19613 |
Pitch
In 2010 Mozilla wrote an article "RegisterProtocolHandler Enhancing the Federated Web".
The idea is to register a protocol handler when logged into a mastodon account:
On the profile pages, the follow button could look like:
RegisterProtocolHandler
is supported by most modern browsers (except Safari but maybe Mastodon could change this). If there is a check, it should not break anything.Motivation
Improve the "decentralized follow" flow, to feel more like a classic silo (twitter, facebook) follow.
The text was updated successfully, but these errors were encountered: