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.
-
@trwnh @benpate I agree. It should always be web first. But for those that made the leap, choose from the 100,000 servers and have an app, we shouldn’t make them relive the trauma
by asking them to log in on every instance where they just want to either follow someone or like somethingImagine i send you the link below through signal. It opens in the browser or webview. If i want to follow them all, i have to log in x times https://joinfediverse.wiki/Notable_Fediverse_accounts
@ricferrer @benpate right now, if you link me x accounts and i find n interesting, i copy-paste n links (n <= x) into my fedi address bar (search bar) to access them in my "layer 2" browser-in-a-browser
i am not entirely convinced it would be better for every page to have to publish 2x links as opposed to publishing x links and you copying n links. 2x > x + n
what could be improved is opening n links in a different app (pwa included) but you can't avoid that unless you make your browser auth'd
-
@benpate how do we get people to use fedi without an account?
@trwnh sorry. What I mean is: the “share” and “like” workflows are gateways to the signup process.
If someone already has an account, use that.
Otherwise, give them a big orange button that goes directly to a signup page — no awful “instance chooser”, but that’s another conversation.
With Activity Intents, all the real work happens on your home server so we don’t need you to “sign in” on the remote server; just declare where you’re going to go when you want to interact.
-
@trwnh @benpate
The issue with PWA targets afaik is that they are like universal/app links -> bound to a domainApps from different vendors can pick it up (it’s only a problem if you have more than one on iOS, Android lets you choose)
For 3b to work you would need to tell the page with the content which one is your home server every time for every content
Do you use a browser for the fediverse mostly or an app? I am 100% app
@ricferrer @benpate the app is a browser too but i mainly use either firefox or subway tooter
-
@trwnh @benpate
The issue with PWA targets afaik is that they are like universal/app links -> bound to a domainApps from different vendors can pick it up (it’s only a problem if you have more than one on iOS, Android lets you choose)
For 3b to work you would need to tell the page with the content which one is your home server every time for every content
Do you use a browser for the fediverse mostly or an app? I am 100% app
@ricferrer @benpate the "end goal" for me is to have them discriminate by content type so i can open pdfs in my pdf viewer and activities in my activity viewer
-
just some historical context,
since at least 2010 (16 years ago) registerProtocolHandler is specified and worked for mailto: then for tel: (cause nice for gooles android) back in 2015 (11 years ago) we (w3c SocialCG) had talked to all the browser makers about making ActivityPub and webmention trusted protocols.In 2016 (T-10 years) I demoed the existing practical problems at Jeremy Keiths indiewebcamp in Brighton see the demo https://www.youtube.com/live/W70wd56i0Bg?si=DJgm9WsGpwzaLdGJ&t=2030 (indiewebcamp demos are written in incredible short time …)
Anyway - nothing changed at the browser makers except the browser makers switched their positions from company to company. @jaffathecake
[edit; well: Mozilla did BrowserId, renamed it to Persona and directly trashed it cause then gaming and AI [where the parts of the teams went to] was more important …
@sl007 @julian @jaffathecake @benpate but you don’t need approval or the blessing from the browsers to implement a uri scheme right? iTunes used it with itms: , zoom does it.
It works of people have the app. You would only need their support if you want the browser to do something with the uri out of the box when there is no app other than showing an error. Right?
-
@sl007 @julian @jaffathecake @benpate but you don’t need approval or the blessing from the browsers to implement a uri scheme right? iTunes used it with itms: , zoom does it.
It works of people have the app. You would only need their support if you want the browser to do something with the uri out of the box when there is no app other than showing an error. Right?
@ricferrer@mastodon.social yes and no. I think standalone apps can listen for their own protocol handlers (like julian:// what a great protocol)
But PWAs must use the
web+prefix. The OS (or maybe just the browser) won't allow registration otherwise@trwnh@mastodon.social @benpate@mastodon.social @sl007@digitalcourage.social
-
@trwnh @benpate
The issue with PWA targets afaik is that they are like universal/app links -> bound to a domainApps from different vendors can pick it up (it’s only a problem if you have more than one on iOS, Android lets you choose)
For 3b to work you would need to tell the page with the content which one is your home server every time for every content
Do you use a browser for the fediverse mostly or an app? I am 100% app
“For 3b to work you would need to tell the page with the content which one is your home server every time”
Not quite. FedCM solves this. And in the interim, we can put this in localStorage so you only need to enter your handle once per domain. And even that can be reduced if all the JS widgets are served by a shared location.
-
@trwnh @benpate
The issue with PWA targets afaik is that they are like universal/app links -> bound to a domainApps from different vendors can pick it up (it’s only a problem if you have more than one on iOS, Android lets you choose)
For 3b to work you would need to tell the page with the content which one is your home server every time for every content
Do you use a browser for the fediverse mostly or an app? I am 100% app
I’m 70/30 app/browser. I used the browser, for instance, when traveling internationally so I don’t have an app signed in to my identity.
But I’m not the target audience. I’m already sold. The main reason to put open web first is to give an on-ramp to newbies who would join us if we made it easy enough
-
@ricferrer@mastodon.social yes and no. I think standalone apps can listen for their own protocol handlers (like julian:// what a great protocol)
But PWAs must use the
web+prefix. The OS (or maybe just the browser) won't allow registration otherwise@trwnh@mastodon.social @benpate@mastodon.social @sl007@digitalcourage.social
-
@ricferrer@mastodon.social yes and no. I think standalone apps can listen for their own protocol handlers (like julian:// what a great protocol)
But PWAs must use the
web+prefix. The OS (or maybe just the browser) won't allow registration otherwise@trwnh@mastodon.social @benpate@mastodon.social @sl007@digitalcourage.social
That’s really helpful. Thanks, Julian://
One follow up question? Is it possible for regular apps to use the web+ prefix, too? Otherwise we’d have to pick one over the other, which might be problematic.
-
@ricferrer@mastodon.social yes and no. I think standalone apps can listen for their own protocol handlers (like julian:// what a great protocol)
But PWAs must use the
web+prefix. The OS (or maybe just the browser) won't allow registration otherwise@trwnh@mastodon.social @benpate@mastodon.social @sl007@digitalcourage.social
well, the difference is what I demoed at IWC:
Apple itself (itms) or zoom https://www.visualcapitalist.com/zoom-boom-biggest-airlines/ can do anything.
You will not be asked for consent.
Same with mailto …But as shown the consent mechanism is not standardized and when I see the nearly white icon in the white browser bar I wanted to hit the person who made it cause at least 30% will not even realize it …
-
That’s really helpful. Thanks, Julian://
One follow up question? Is it possible for regular apps to use the web+ prefix, too? Otherwise we’d have to pick one over the other, which might be problematic.
This is possible as just answered to Julian but someone needs to fix the consent issues in the browsers (shown in posted demo video) which is nothing we can do …
-
This is possible as just answered to Julian but someone needs to fix the consent issues in the browsers (shown in posted demo video) which is nothing we can do …
@benpate @julian @ricferrer @trwnh
PS History continued, two years later, in 2019 I sponsored the first offiial ActivityPub Conf https://conf.tube/c/apconf_channel/videos and in the Prague dox museum we had a short session where we said to talk to the browser people again in some years. The 2020 Conf was fully packed and then I was personally overloaded with the EU DMA/DSA consulting (disclaimer; invited expert but all voluntary) …
But maybe that time would benow - at least in the interest of accessibility …[Jake Archibald and Jenn Simmons and more browser makers are meanwhile in fedi themselves …]
-
@benpate @trwnh @evan @julian @rimu I know I implemented it at some point by analyzing what Facebook and co were doing. I think it was kind of a hack, but it worked. It didn’t let you know what was available. It just assumed it worked if you left the page and if you were still there it opened http. Like I said sometimes you had the page open when you came back to the browser (so it effectively opened both) but it wasn’t that annoying
@ricferrer @benpate @trwnh @julian @rimu so, maybe we should have a group working on this problem.
-
@ricferrer @benpate @trwnh @julian @rimu so, maybe we should have a group working on this problem.
-
@ricferrer@mastodon.social I feel keeping this on fedi is easier, but that's also because I don't have a matrix account
-
@ricferrer@mastodon.social I feel keeping this on fedi is easier, but that's also because I don't have a matrix account
@julian @ricferrer I meant, taking it to a Task Force. It's a really important question.
-
@julian @ricferrer I meant, taking it to a Task Force. It's a really important question.
@evan@cosocial.ca yep! I was responding to using a matrix chat room.
I'm all for a task force on this.
-
-
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
️@julian @evan @rimu @ricferrer @trwnh I think handlers like this are an older desktop paradigm, on mobile we already have share sheets, and we’re sharing a url, to an app, what happens when the app receives the url is a client concern. Get the ActivityPub representation, and carry on as you would in the fedi (actor follow, or object like share, reply)!
Desktop OS’ have already adopted this UX
or should I make one?