@wiktor I understand the concern about bad fallback on the web. I just wish people would be a bit more pragmatic about it and at least add support for reading / opening such URIs. Nobody suggested replace all Follow buttons with web+activitypub: links.

Can we have support for FEP-07d7 in #Tusky and #Fedilab? (cc @Tusky @apps)

It shouldn’t be that hard to implement at least one of the possible URI schemes in #Conversations_im, #Lttrs, #Tusky and #Fedilab. Maybe get @delta on board too?

Ticket created, we will work on that support.

codeberg.org/tom79/Fedilab/iss…

@wiktor @Tusky @delta

support for FEP-07d7

See: https://gultsch.social/@daniel/114236429891812116

^Codeberg.org

That’s awesome. I think the URIs are supposed to look like this: web+activitypub:toot.fedilab.app/@apps (Notice the absence of //)

Maybe @jenniferplusplus can chime in to clarify? Maybe also something to be more explicit about in the FEP.

I know that over a decade we had both variants in the #XMPP world and that turned out to be a mess when parsing (Correct in the XMPP world is without the //)

The app can now open profiles with the scheme "web+activitypub"

Examples of working links:

fdroid.fedilab.app/testlink/

@jenniferplusplus personally I belive it's fine to assume https as the transport. While ActivityPub may or may not work over telnet I don't think we'd be using a web+ scheme for that.

However - assuming that we can agree on https - my question was just: is it
a) web+activitypub:something
b) web+activitypub://something

The examples in the FEP indicate a although there isn't any normative text.

The web+soup example here html.spec.whatwg.org/#custom-h… also uses variant (a)

@jenniferplusplus Conversations has been able to open xmpp: URIs (without //) for years.

Just to be sure I tested this with web+activitypub: URIs quickly to make sure web+ URIs don’t get special treatment - and it’s working fine in both Firefox and Chrome on Android.

Here is the intent filter I was using: gist.github.com/iNPUTmice/7975…

I have no strong opinions on whether the // should go in there. But I’m advocating for consistency. (And clarity in the FEP)

AndroidManifest.xml

GitHub Gist: instantly share code, notes, and snippets.

^Gist

@jenniferplusplus OK. Fair enough. Since I’m unsure what other venue would be more appropriate for finding consensus I added my comments to the @Tusky issue tracker: github.com/tuskyapp/Tusky/issu…

Let’s continue the discussion there instead here on Mastodon.

Support 'FEP-07d7: A Custom URL Scheme and Web-Based Protocol Handlers for Linking to ActivityPub Resources' · Issue #5027 · tuskyapp/Tusky

Pitch Support opening links with the web+activitypub: URI scheme. Motivation This would allow android applications like Conversations and Ltt.rs to auto link web+activity: links and open Tusky dire...

^GitHub

I assume you are testing with this exact commit? codeberg.org/tom79/Fedilab/com…

If you wanted web+activitypub: to work (without the //) you can’t have host and pathPattern in there. Only <data android:scheme="web+activitypub" /> analogous to the gist I linked earlier.

However see my comments on the Tusky issue tracker on why I believe fedilinks is better than FEP-07d7: github.com/tuskyapp/Tusky/issu…

fedilinks uses :// anyway

#1160 - Detects acct and intent in URL with scheme web+activitypub · db17df93f0

Fedilab - Fedilab is a multifunctional Android client to access the distributed Fediverse, consisting of microblogging, photo sharing and video hosting

^Codeberg.org