new from me: FR#156 - Share Where?

[fediversereport@mastodon.social]

new from me: FR#156 - Share Where?

on @Mastodon 's new Share button, the Mastodon API and protocol ownership

https://connectedplaces.online/reports/fr156-share-where/

[julian@activitypub.space]

@fediversereport@mastodon.social I'd say a protocol handler would be one small step in making this better handled.

The friction with a global "share to the fediverse" button is the instance chooser. Not knowing what your home instance is is a major sticking point.

A protocol handler could allow you to skip this step, assuming you have an app that has registered against it.

Otherwise, yes, the same fallback would need to continue to exist (enter your home server! blah blah)

[julian@fietkau.social]

@fediversereport Good overview as usual.

One point I would have added is that, while Mastodon announced this Share button a while back, a “pure” ActivityPub-based way to expose share URLs and similar features exists in FEP-3b86 (https://fediverse.codeberg.page/fep/fep/3b86/) and has also been gaining prominence recently (c.f. the list of implementations).

For example, ActivityPub for WordPress published its v8.0.0 today, which includes new “Like” and “Share” buttons that use this proposal.