Discourse has a “social share” component so that readers can share a post on different platforms. On the link above you will find ways to share with all kinds of social media silos, but not a single one to share with an ActivityPub instance. This, to me, is a terrible overlook from the ActivityPub community, that it does not make easy for people to perform one-click sharing of contents.
I agree that the use-case of “sharing with” decentralized instances is not the same as with sharing with a unique instance. But this does not mean it should be more difficult to do: actually it should be as easy as documenting an URI template such as: https://your.social.example/sharing?url=
.
If we could agree that all ActivityPub implementations would implement such a template, then it would bring a very easy way to catch up with centralized services. Eventually, this could become standardized, but even before considering this, let’s consider the actual use-case of adding the possiblity for people to share with their favorite ActivityPub instance.
Since Diaspora already has such a template, documented at the link above (https://share.diasporafoundation.org/?title={title}&url=
), we can see that: 1) there’s a convenient, but centralized, way of sharing a link to D*; 2) there should be a similar service that would detect, maybe through fediverse.space, which instance you’d like to share with – or, even better, “force” a local instance, that would then ask you to log in and forward the sharing request to your own instance (which would mean to specify more precisely this workflow in ActivityPub).
I’m just throwing wild thoughts here, but the problem to solve does not seem to be too difficult for coordinated action, while the benefit seems, in the current state of the web, an avenue to take back from centralized services.