this post was submitted on 10 Aug 2026
33 points (97.1% liked)
Fediverse
43448 readers
350 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Realistically speaking, this could only work as another development that's built directly and only against Mastodon. Something that won't work anywhere else.
These URLs are different everywhere in the Fediverse, that's why. It'd be tedious to implement even only the most common Fediverse server applications, and it'd be even more tedious to implement them all.
For one, profile/account/channel URLs are different everywhere. Besides, the URL for someone else's profile/account/channel on your server is different everywhere yet again.
Here are a few out of many examples. Let's assume you're on foo.com, and you want to look at the profile of alice@bar.org.
Lemmy users
The local scheme is /u/
The remote scheme is /u/@
Lemmy communities
The local scheme is /c/
The remote scheme is /c/@
Mastodon up to 4.6, also Pixelfed, Pleroma, Akkoma and apparently also GoToSocial:
The local scheme is /users/
The alternative local scheme is /@
The remote scheme is /users/@
Mastodon from 4.7 on:
The local scheme is /ap/users/
The alternative local scheme is /@
The remote scheme is /ap/users/@
PeerTube accounts (there's no content to be found here):
The local scheme is /a/ or /accounts/
PeerTube channels (this is where the actual videos are):
The local scheme is /c/ or /video-channels/
*key:
The local scheme is /users/
The alternative local scheme is /@
WriteFreely:
The local scheme is /api/collections/
Friendica:
The local scheme is /profile/
Hubzilla:
The local scheme is /channel/
The remote scheme for the local "in-between page" is /chanview?f=&hash=<Full local account/channel URL of the remote account/channel>
The remote scheme for actually viewing the account/channel remotely, but using OpenWebAuth magic sign-on, is <Full local account/channel URL of the remote account/channel>?zid=@
This means that the remote URL on Hubzilla is different, depending on where the account/channel is. The remote scheme for a Hubzilla channel is different from the remote scheme for a Mastodon account, which is different from the remote scheme for a *key account, which is different from the remote scheme for a Lemmy community.
So if you want to use such an add-on, and you're on Hubzilla, then the add-on will have to know which Fediverse server application @user@domain.tld is on.
Oh, and if that wasn't bad enough: Not everything everywhere in the Fediverse uses @user@domain.tld. Some server applications use user@domain.tld. Friendica has done so since 2010, Hubzilla has since 2012, just to give you two examples.
So the add-on would have to cope with Fediverse handles with as well as without the leading @ and be able to tell whether that ID without the leading @ is an e-mail address, a Fediverse handle, an XMPP ID or something else again.
How does Mastodon‘s „Open URL“ work then? It works with the URLs I get from Lemmy, so it does support some other software…
Mastodon internally converts it into something it understands, maybe using Webfinger.
That'd be one reason why Webfinger, which is not part of the official W3C ActivityPub spec, is a hard requirement for federating with Mastodon.
The idea behind this Firefox add-on idea appears to be that it shall work with any Fediverse server application, regardless of which one you use. Or it should be if it has "Fediverse" in its description. You should be able to use it with Mastodon or with Lemmy, but you should be able to use it with Akkoma or Misskey or Iceshrimp.NET or Hollo or Mbin or Friendica or Hubzilla or (streams) or Wafrn all the same.
But it already gets tricky if it has to support Lemmy (as in being on Lemmy) in addition to Mastodon.
In case I'm missing something, is there a good reason to not use the webfinger? It would be a simple request to https://
domain.tld/.well-known/webfinger?resource=acct:user@domain.tldand you would get everything you're looking for