Post B36fifbAgFkaIBMhu4 by trwnh@mastodon.social
 (DIR) More posts by trwnh@mastodon.social
 (DIR) Post #B34jov06L88XIbLDH6 by ricferrer@mastodon.social
       2026-02-05T20:52:52Z
       
       0 likes, 0 repeats
       
       @julian @rimu @evan isn’t an URI scheme the way that would offer fastest compatibility? after all it’s been around forever, most browsers just let the OS handle it and even apps like zoom and iTunes have successfully implemented it for their service 🤔
       
 (DIR) Post #B34joweCDXnqPF6kPQ by evan@cosocial.ca
       2026-02-05T21:08:06Z
       
       0 likes, 0 repeats
       
       @ricferrer @julian @rimu We already have an URI scheme for ActivityPub objects; it's https: .
       
 (DIR) Post #B34joxewSFzfXqSrD6 by ricferrer@mastodon.social
       2026-02-05T21:11:41Z
       
       0 likes, 0 repeats
       
       @evan @julian @rimu it’s horrible UX. It opens a browser where I am not logged in instead of opening my default app, like it happens with mailto: https: is for webpages
       
 (DIR) Post #B34joyQRbdzVvAgnFg by trwnh@mastodon.social
       2026-02-06T18:21:26Z
       
       0 likes, 0 repeats
       
       @ricferrer @evan @julian @rimu https: is not for web pages. it's for http resources, which can be any content type. the content should be dispatched to the appropriate content handler; for example:- html opens in an html viewer- pdf opens in a pdf viewer- png opens in a png viewer- mp4 opens in an mp4 vieweractivity+json could be opened in an activity viewer. see firefox for example in pic 1:
       
 (DIR) Post #B34joz4rBOJjwVb4F6 by strypey@mastodon.nzoss.nz
       2026-02-07T10:41:25Z
       
       0 likes, 0 repeats
       
       How about we start by acknowledging that this is indeed a pain point, and it's been widely discussed that it needs a fix;@ricferrer> it’s horrible UX. It opens a browser where I am not logged in instead of opening my default appIn @moshidon, fediverse URLs are often (but not always) recognised as such, and opened in the app, instead of sent to a browser. Can you explain how you achieve this Lucas, and why it doesn't work with every fediverse URL?@trwnh @evan @julian @rimu
       
 (DIR) Post #B34k3ah67ZdqfBRszg by trwnh@mastodon.social
       2026-02-07T10:44:09Z
       
       0 likes, 0 repeats
       
       @strypey did we not start with exactly that? we're way past the point of acknowledging the pain point...
       
 (DIR) Post #B34nNReZkAAwHJQaVk by ricferrer@mastodon.social
       2026-02-05T20:25:36Z
       
       0 likes, 1 repeats
       
       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)
       
 (DIR) Post #B36fiZo4DOV6KRLvAe by ricferrer@mastodon.social
       2026-02-06T18:42:49Z
       
       0 likes, 0 repeats
       
       @trwnh @evan @julian @rimu while this is true now, it was an evolution. As you probably know, the ht in html and http stands for HyperText, the fundamental concept that enabled websites in the early 90sThe question is what is more realistic for wide adoption… that all browsers start recognizing activities and decide if rendering in a viewer inside the browser or redirecting outside to an app makes sense.
       
 (DIR) Post #B36fibJIcl4szayNUW by ricferrer@mastodon.social
       2026-02-06T18:47:24Z
       
       0 likes, 0 repeats
       
       @trwnh @evan @julian @rimu I think the biggest difference with pdfs, mp4 in your example and an activity is that I most likely want to interact with an activitypub object: either follow, repost/announce, etc for this to work I need to be logged in. So is the solution to include an activitypub client in the browser? Use an external viewer that intercepts through browser extensions?Now even the experience inside mastodon sometimes opens a webview 🤷🏻‍♂️
       
 (DIR) Post #B36ficMWiFFmFtUTA0 by benpate@mastodon.social
       2026-02-06T19:00:48Z
       
       0 likes, 0 repeats
       
       I think the right solution is to use a combination of FedCM (making progress in the W3C) plus Activity Intents (FEP-3b86) to link you back to the web page for your home server.FedCM will let you “sign in” to your browser, and make that information available (with consent) to the pages you visit online.Activity Intents publish the operations your home server supports, then give links to complete the intent.We already have the tools we need.@ricferrer @trwnh @evan @julian @rimu
       
 (DIR) Post #B36fidRsfp89cn0G92 by trwnh@mastodon.social
       2026-02-06T19:05:44Z
       
       0 likes, 0 repeats
       
       @benpate @ricferrer @evan @julian @rimu should be possible even without necessarily those specific tools -- although fedcm can make it "friendlier" ux-wise- authenticate your id ("i am this person")- get the linked claims from the id ("this is my proxy url")- submit the request ("fetch me this thing")i mean, you could write a web extension right now that does it in a very minimal way, i'm pretty sure? "POST the current URL to this proxyUrl" is not exactly a difficult thing to do...
       
 (DIR) Post #B36fieXwalZh1sqcEa by benpate@mastodon.social
       2026-02-06T19:11:12Z
       
       0 likes, 0 repeats
       
       You’re correct.FedCM is a bonus, but not required.And Activity Intents just normalize the mess of “remote follows” and “share intents” that many apps already support. I currently “polyfill” intents for servers (like Mastodon) that don’t publish explicitly.It should, however, start with a GET to my home server (not a POST) so I can see what I’m about to do. There’s so much variation between servers; we’re asking for bugs if we skip this step.@trwnh @ricferrer @evan @julian @rimu
       
 (DIR) Post #B36fifbAgFkaIBMhu4 by trwnh@mastodon.social
       2026-02-06T19:12:12Z
       
       0 likes, 0 repeats
       
       @benpate @ricferrer @evan @julian @rimu i'm not entirely sure why it's POST proxyUrl instead of GET proxyUrl but i think it has to do with leaking metadata iirc
       
 (DIR) Post #B36figNjlgbAio5UbQ by benpate@mastodon.social
       2026-02-06T19:15:34Z
       
       0 likes, 1 repeats
       
       In the end, we need real “share” and “like” buttons for the Fediverse - with as few clicks as possible - wrapped up as easily installable widgets that go next to Twitter and Facebook on every site online.(That’s step 1)Once we do this, step 2 is to lobby sites to JUST use Fediverse buttons, and drop the ones for hateful platforms. @trwnh @ricferrer @evan @julian @rimu
       
 (DIR) Post #B36fiit0SOncUMjUcS by trwnh@mastodon.social
       2026-02-06T19:06:25Z
       
       0 likes, 0 repeats
       
       @benpate @ricferrer @evan @julian @rimu there's a shortcoming where mobile browsers don't let you install web extensions as easily but that can also be overcome i think.
       
 (DIR) Post #B36fioocPcr2sUj4c4 by trwnh@mastodon.social
       2026-02-06T19:07:04Z
       
       0 likes, 0 repeats
       
       @benpate @ricferrer @evan @julian @rimu native apps can also expose share targets so you can "share" the current web URL to those apps and it opens in those apps.