#FediDev is there a generic Android intent for sharing to the Fediverse?
Technical Discussion
5
Posts
2
Posters
0
Views
-
#FediDev is there a generic Android intent for sharing to the Fediverse?
-
#FediDev is there a generic Android intent for sharing to the Fediverse?
@travisfw@fosstodon.org short answer: no
Slightly longer answer: not yet
Long-ass thread (just from last month!): https://activitypub.space/topic/e00a0fd8-31d2-494e-bd8a-31eedcd16ac2/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
😅
-
@julian it's complicated, isn't it. I was focusing on the narrower case of one app calling a default (or system dialog to choose) app to handle the post, rather than even necessarily involving the browser. But could one solution (somewhere in that veritably long-ass thread) serve the whole matrix of calling web->web, web->app, app->app, and app->web?
-
@julian it's complicated, isn't it. I was focusing on the narrower case of one app calling a default (or system dialog to choose) app to handle the post, rather than even necessarily involving the browser. But could one solution (somewhere in that veritably long-ass thread) serve the whole matrix of calling web->web, web->app, app->app, and app->web?
@travisfw@fosstodon.org I don't blame you for not reading through the whole thread.
Suffice to say I think there is merit in using
web+ap://scheme at the browser (and possibly app) level.PWAs can register themselves as a handler of those types (
web+), and on the web side there are tricks to allow for the opening of them in the PWA or falling back to browser https.It's worth experimentation, I think.
-
@julian I really tried. Maybe should have reached for AI. I'll look into that web+ap:// scheme, thank you!
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@julian I really tried. Maybe should have reached for AI. I'll look into that web+ap:// scheme, thank you!
-
@travisfw@fosstodon.org I don't blame you for not reading through the whole thread.
Suffice to say I think there is merit in using web+ap:// scheme at the browser (and possibly app) level.
PWAs can register themselves as a handler of those types (web+), and on the web side there are tricks to allow for the opening of them in the PWA or falling back to browser https.
It's worth experimentation, I think.
-
@julian it's complicated, isn't it. I was focusing on the narrower case of one app calling a default (or system dialog to choose) app to handle the post, rather than even necessarily involving the browser. But could one solution (somewhere in that veritably long-ass thread) serve the whole matrix of calling web->web, web->app, app->app, and app->web?
-
@travisfw@fosstodon.org short answer: no
Slightly longer answer: not yet
Long-ass thread (just from last month!): https://activitypub.space/topic/e00a0fd8-31d2-494e-bd8a-31eedcd16ac2/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
😅
-
#FediDev is there a generic Android intent for sharing to the Fediverse?
-
the type information is largely unnecessary and shouldn't factor into handling CRUD
Servers needs to know the core type / class in order to determine the "owner" of an object (actor, attributedTo, etc).
how does the server know which ids to assign and which ones not to?
The result property could be declared as special in the FEP. Servers will be required to assign IDs to embedded activities. What is a blank node identifier, id: null? Using this to indicate a need for ID is a good idea too.
I don't think side effect activities should be fragments.
lastly as:result itself maybe doesn't have these semantics defined, so should a subproperty or different property be used, or do we skip non-CRUD results?
Why skip non-CRUD results? I think side effects shouldn't be limited to basic activities like Create/Update/Add/Remove.
-
@silverpill @steve so we might need to recommend that these "side effect" activities in as:result SHOULD have fragment identifiers, to be able to refer to them later? or do we intend to never refer to them later? we could say they're transient activities so don't need to be referred to later (only processed in-order).
lastly as:result itself maybe doesn't have these semantics defined, so should a subproperty or different property be used, or do we skip non-CRUD results?
-
@silverpill @steve also the server's main responsibility being publishing and therefore needing to mint an identifier for the top level activity, we should ask if the server is expected to assign any inner ids as well? assigning ids changes the graph so it's not clear cut. <how does the server know *which* ids to assign and which ones not to?> is an open question (and maybe blank node identifiers are actually in practice required to avoid ambiguity?)
