I’m going to register a protocol handler, so links to anywhere on the fedi will be opened in the user’s home instance.
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/registerProtocolHandler
Has anyone already done this and if so what was the prefix you used? We might as well all use the same thing. I’m thinking web+fedi.
Too soo-…wait what fucking year is it
rimu@piefed.social interesting idea… I know Evan has some thoughts about this as part of his ActivityPub HTML discovery project
https://swicg.github.io/activitypub-html-discovery/
I am not sure why they did not settle on protocol handlers but I’ve tagged him for comment
The concept sounds excellent, although there is fairly limited mobile support.
Since NodeBB is an installable PWA it would be definitely nice to have it supported there as well.
@rimu web+acct
What does acct stand for?
Maybe similar to webfinger, which uses acct. That’s for people / Actors, the solution I’m seeking would work for posts, comments, communities and people.
Hi @Die4Ever @evan,
it stands for this https://www.rfc-editor.org/rfc/rfc7565.html #URI scheme. #RFC7565In #webfinger https://www.rfc-editor.org/rfc/rfc7033 handles, namely. #RFC7033
It’s a good idea, but
web+fediorweb+activitypubis maybe too broad to be useful? I wouldn’t want a Lemmy post to open in Mastodon, and pretty sure opening a Mastodon post in Lemmy is impossible unless the post was directed to a community.web+threadiversecould solve that issue but that’s kinda hacky. Too bad (AFAIK) they can’t be stacked likeweb+fedi+threadiversewith some kind of priority system.There was a discussion about this for Lemmy but it was never implemented https://github.com/LemmyNet/lemmy-ui/issues/3031
Maybe the real solution is to improve Lemmy and Mastodon so that they are capable of doing these things decently.
I was actually thinking of making a browser extension that handles this instead. Each Fediverse software could write something to
window.fediverseor something like that, with tags for threadiverse, group support, micro blogging, etc. The extension could have methods to infer these values for existing platforms. But the extension could give a dialog box to redirect, based on your preferred instances for certain tags.Yes an extension might be the only way to get something happening on mobile browsers.
It would be helpful if there was a convention for what endpoint to call to ask an instance to convert a url to it’s local equivalent, to replace what navigator.registerProtocolHandler does. Otherwise you’d have to hardcode it for each platform.
On the other hand, most mobile fedi usage would be using an app, not browser. Couldn’t app devs hardcode something?
web+ap, which was proposed by Fedilink authors. To my knowledge, it is the most widely adopted proposalhttps://web.archive.org/web/20250402041648/https://fedilinks.org/
(the main site seems to be offline now)
cc @SoniEx2
Are there implementors of web+ap? I’d be interested in adopting.
I assume the fallback behaviour is to just assume https?
@julian Fedilinks website lists 3 MastoAPI clients, but the list is incomplete. I saw Fedilinks being mentioned in changelogs of other clients too.
There was also an Akkoma PR, it was closed by the author: https://akkoma.dev/AkkomaGang/akkoma/pulls/589. I don’t quite understand the reasoning, perhaps @smitten could clarify.
The PR comments suggest that making the various changes to the backend were too large to justify, and a front-end only approach would be preferred? smitten@key.portend.place
It raises a good point though, where if you serve
web+ap://, it’s not understood by clients that are not aware of this scheme. If there were a way a client could communicate whether there is a protocol handler registered, then the server could tailor its response.
rimu@piefed.social I’ve been using web+acct for the acct URI format.
