It’s really surprising to me that the #fediverse hasn’t agreed on a standardized way to open cross-instance #activitypub objects and instead relies on links that open in the browser.
-
It’s really surprising to me that the #fediverse hasn’t agreed on a standardized way to open cross-instance #activitypub objects and instead relies on links that open in the browser. #urischeme
I found this proposal and what’s thinking… https://codeberg.org/fediverse/fep/src/branch/main/fep/07d7/fep-07d7.md Which one would be your favorite?
(If anyone has updates on the progress, feel free to point me in the right direction)
@ricferrer There is `acct:` for Webfinger from https://datatracker.ietf.org/doc/html/rfc7565
-
@ricferrer There is `acct:` for Webfinger from https://datatracker.ietf.org/doc/html/rfc7565
@astro completely missed this. Will Check it out. Thanks
-
@ricferrer There is `acct:` for Webfinger from https://datatracker.ietf.org/doc/html/rfc7565
@astro just read into it and it’s not designed to be actionable on its own (clicking it won’t open a client or app). It’s also only for accounts and handles used to identify a user. What I meant that we need is something that open a client to a specific post and user profile, among others. Similar protocol handlers like itms: (Apple App Store), mailto: (e-mail), tel: (phone numbers) or magnet: (BitTorrent)
-
I understand the need to link back to an app. It’s important, but I’m voting for the open web.
All the search and discovery interactions *should* start out on a website somewhere, then link back to your home website (or possibly an app) to share and like.
But, using a new URL scheme will lock out everyone who doesn’t have an app installed, and that’s a bad UX.
Plus, I think we can solve this “back to my server” issue in other ways WITHOUT needing a URL scheme, like: #FEP3b86
@benpate
> I think we can solve this “back to my server” issue in other ways WITHOUT needing a URL scheme, like: #FEP3b86The finer details of this are beyond me for now, but I know that @moshidon often seems to know that a URL leads to AP object, and opens it in-app instead of passing it to a web browser. Can you link us to any resources you used to make that magic happen Lucas?
