Alright, we really need to figure out "mailto" links, but for the #fediverse.
-
Alright, we really need to figure out "mailto" links, but for the #fediverse.
For context, just like clicking an "email link" opens your email client, clicking a link to a fediverse post or profile should open it on your home server.
We do have some workarounds, but for this to work seamlessly, it has to be handled by your browser.
@stefan we have the acct: URI scheme, made for Webfinger.
-
@stefan we have the acct: URI scheme, made for Webfinger.
@evan Great! How do we move this forward?
-
@evan Great! How do we move this forward?
@evan Ah. "May 2015".
-
@irelephant Right, but the official Bluesky Android app doesn't seem to use it?
Definitely not any major browsers.
-
@evan Ah. "May 2015".
@stefan I don't know what you mean about that date.
Anyway, there's a problem with acct:, which is that it's not whitelisted for use in HTML5. I think we could get it done, but for now you need to use web+acct:
This is an example app that will register with your browser as a handler for web+acct and then show the person when you click a link with that format.
For real use, you'd want it to go to your home server or web app instead.
-
@stefan I don't know what you mean about that date.
Anyway, there's a problem with acct:, which is that it's not whitelisted for use in HTML5. I think we could get it done, but for now you need to use web+acct:
This is an example app that will register with your browser as a handler for web+acct and then show the person when you click a link with that format.
For real use, you'd want it to go to your home server or web app instead.
@evan Ah, I'm just being impatient. Don't mind me.
But wait, I think I'm a bit behind here. It sounds like web+acct is already supported by (some?) browsers? Is this just a matter of fediverse platforms adding any missing pieces?
I have some reading to do on this.
-
This is a real pain point. As a savvy user, I can figure it out, but I can’t imagine someone who isn’t trying to navigate the verse with so many gates. I can see them hitting this snag once and then immediately running back to their old centralized platforms
-
This is a real pain point. As a savvy user, I can figure it out, but I can’t imagine someone who isn’t trying to navigate the verse with so many gates. I can see them hitting this snag once and then immediately running back to their old centralized platforms
@eve Absolutely. But it looks like we're closer to solving this than I realized?
https://cosocial.ca/@evan/116313168828923330
Trying to get up-to-speed.
-
@irelephant Right, but the official Bluesky Android app doesn't seem to use it?
Definitely not any major browsers.
Annoyingly, no, but most custom clients have it.
I don't think this is as much of a problem on the Atmosphere; a record is referred to by its rkey, lexicon and owner, whereas an AP post's id can be any url.Here's an example at:// uri,
at://did:plc:22l5hixwr3ffouf6eabgpvo2/app.bsky.feed.post/3mi7aryutyc2wThey will always have the structure:
at:////
Which on bluesky is https://bsky.app/profile/did:plc:22l5hixwr3ffouf6eabgpvo2/post/3mi7aryutyc2wA record will have a consistent id everywhere, so its easy to convert a bsky.app link to an at uri and vice versa.
Atproto is also designed so that this isn't really necessary: apps listen to the whole network by design, but can also fetch just the data they need through https://constellation.microcosm.blue/ (in short, missing information isn't as much as a problem), for example, https://reddwarf.app runs client side without a relay or appview but doesn't suffer from missing information.
-
Annoyingly, no, but most custom clients have it.
I don't think this is as much of a problem on the Atmosphere; a record is referred to by its rkey, lexicon and owner, whereas an AP post's id can be any url.Here's an example at:// uri,
at://did:plc:22l5hixwr3ffouf6eabgpvo2/app.bsky.feed.post/3mi7aryutyc2wThey will always have the structure:
at:////
Which on bluesky is https://bsky.app/profile/did:plc:22l5hixwr3ffouf6eabgpvo2/post/3mi7aryutyc2wA record will have a consistent id everywhere, so its easy to convert a bsky.app link to an at uri and vice versa.
Atproto is also designed so that this isn't really necessary: apps listen to the whole network by design, but can also fetch just the data they need through https://constellation.microcosm.blue/ (in short, missing information isn't as much as a problem), for example, https://reddwarf.app runs client side without a relay or appview but doesn't suffer from missing information.
@irelephant Yes, the Atmosphere definitely has a big advantage of starting off 99.99% centralized.
I do trust that this is all going to continue to improve over time. For me the question is, will that happen before Bluesky itself enshittifies, and will the rest of the network survive. Maybe! Possibly.
If not, the fediverse is still very much "in the game". If yes, well, we'll see.
-
Annoyingly, no, but most custom clients have it.
I don't think this is as much of a problem on the Atmosphere; a record is referred to by its rkey, lexicon and owner, whereas an AP post's id can be any url.Here's an example at:// uri,
at://did:plc:22l5hixwr3ffouf6eabgpvo2/app.bsky.feed.post/3mi7aryutyc2wThey will always have the structure:
at:////
Which on bluesky is https://bsky.app/profile/did:plc:22l5hixwr3ffouf6eabgpvo2/post/3mi7aryutyc2wA record will have a consistent id everywhere, so its easy to convert a bsky.app link to an at uri and vice versa.
Atproto is also designed so that this isn't really necessary: apps listen to the whole network by design, but can also fetch just the data they need through https://constellation.microcosm.blue/ (in short, missing information isn't as much as a problem), for example, https://reddwarf.app runs client side without a relay or appview but doesn't suffer from missing information.
There's also at://wormhole: https://chromewebstore.google.com/detail/atwormhole/aihndpeeoneojofmliffjknbegmipbim
It could be done with registerProtocolHandler, but that has no chrome support. Piefed (activitypub) does this iirc.
-
@evan Ah, I'm just being impatient. Don't mind me.
But wait, I think I'm a bit behind here. It sounds like web+acct is already supported by (some?) browsers? Is this just a matter of fediverse platforms adding any missing pieces?
I have some reading to do on this.
@stefan that's cool. I should probably put together a repo and a project for it in SWF GitHub.
-
@stefan that's cool. I should probably put together a repo and a project for it in SWF GitHub.
@evan That would be very appreciated!
-
Alright, we really need to figure out "mailto" links, but for the #fediverse.
For context, just like clicking an "email link" opens your email client, clicking a link to a fediverse post or profile should open it on your home server.
We do have some workarounds, but for this to work seamlessly, it has to be handled by your browser.
Side note, I made one such workaround, in the form of a browser plugin.
If you find yourself using the ol' "copy the link and put it in the search box on your home server" trick a lot, maybe check this out?
https://stefanbohacek.com/project/mastodon-tools-browser-extension/
Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.
Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.
Con il tuo contributo, questo post potrebbe essere ancora migliore 💗
Registrati Accedi