Conversation

Notices

1. Embed this notice
   Daniel Gultsch (daniel@gultsch.social)'s status on Sunday, 30-Mar-2025 02:16:25 JST Daniel Gultsch

   • Fedilab Apps
   • Jenniferplusplus

   @jenniferplusplus @apps 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 https://html.spec.whatwg.org/#custom-handlers also uses variant (a)

   • Embed this notice
     Fedilab Apps (apps@toot.fedilab.app)'s status on Sunday, 30-Mar-2025 02:16:24 JST Fedilab Apps

     in reply to

     • Jenniferplusplus

     @daniel
     I am maybe wrong, but this is mostly a limitation with Android deep links. Without "//" the "web+activitypub" scheme won't be caught by apps.
     @jenniferplusplus

   • Embed this notice
     Fedilab Apps (apps@toot.fedilab.app)'s status on Sunday, 30-Mar-2025 03:34:53 JST Fedilab Apps

     in reply to

     • Jenniferplusplus

     @daniel
     Ok. We use the same intent filter. https://codeberg.org/tom79/Fedilab/commit/db17df93f0bd3851941d948a8b6dbfed28d57481
     I will check if it works without //
     @jenniferplusplus

   • Embed this notice
     Daniel Gultsch (daniel@gultsch.social)'s status on Sunday, 30-Mar-2025 03:34:54 JST Daniel Gultsch

     in reply to

     • Fedilab Apps
     • Jenniferplusplus

     @apps @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: https://gist.github.com/iNPUTmice/79757b4edc5fbfc8c9aab2b965cdcb87

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

   • Embed this notice
     Fedilab Apps (apps@toot.fedilab.app)'s status on Sunday, 30-Mar-2025 05:19:33 JST Fedilab Apps

     in reply to

     • Jenniferplusplus

     @daniel
     I tested. It doesn't work. I think browser apps simply transform XMPP uri before to XMPP://
     That said, that's exactly what conversation will do for sending the intent to Mastodon apps?
     @jenniferplusplus

   • Embed this notice
     Fedilab Apps (apps@toot.fedilab.app)'s status on Sunday, 30-Mar-2025 19:43:21 JST Fedilab Apps

     in reply to

     @daniel Yes, it's fixed and the app now uses the "web+ap" scheme.

   • Embed this notice
     Daniel Gultsch (daniel@gultsch.social)'s status on Sunday, 30-Mar-2025 19:43:22 JST Daniel Gultsch

     in reply to

     • Fedilab Apps

     @apps I assume you are testing with this exact commit? https://codeberg.org/tom79/Fedilab/commit/db17df93f0bd3851941d948a8b6dbfed28d57481

     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: https://github.com/tuskyapp/Tusky/issues/5027#issuecomment-2764451529

     fedilinks uses :// anyway