new from me: FR#156 - Share Where?
-
new from me: FR#156 - Share Where?
on @Mastodon 's new Share button, the Mastodon API and protocol ownership
@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.
-
@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.
@julian a thats a good addition, thanks!
-
@julian @fediversereport Indeed, the Fediverse desperately needs an URI scheme (for example web+ap, but something else might work too).
In XMPP you can implement a provider independent share with feature with xmpp:?message;body=hi
I've trying to make web+ap: happen for a while and #Conversations_im for example auto links URIs like that (my small contribution as someone who is not really in the Fediverse community)
-
new from me: FR#156 - Share Where?
on @Mastodon 's new Share button, the Mastodon API and protocol ownership
@fediversereport @Mastodon it's interesting to mention email protocols like IMAP or SMTP since neither of those (and indeed POP) started out as a standard either, they lived for a long time as same kind of defacto standards as the Mastodon API but after many versions eventually became actual ones.
-
new from me: FR#156 - Share Where?
on @Mastodon 's new Share button, the Mastodon API and protocol ownership
@fediversereport @Mastodon Is this a failure of Mastodon for not being more open or on the great AP community for not stepping up and getting a more generic share button setup sooner?
-
@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.
@julian @fediversereport i would not say that this is "pure" or "activitypub-based" -- it is a webfinger-based mechanism. the activitypub-based mechanism is POST to outbox.
-
@julian @fediversereport i would not say that this is "pure" or "activitypub-based" -- it is a webfinger-based mechanism. the activitypub-based mechanism is POST to outbox.
@trwnh Yes, that's accurate. I meant “pure” colloquially in contrast to “implementation-specific” (hence the scare quotes), but it is indeed WebFinger that's being extended, not ActivityPub itself.
-
@fediversereport @Mastodon Is this a failure of Mastodon for not being more open or on the great AP community for not stepping up and getting a more generic share button setup sooner?
@phillycodehound @fediversereport @Mastodon I know there's work being done on generic share and follow buttons with the Web Intents stuff by @dansup but in terms of APIs, more definitely needs to be done in that area. I might have an idea but would need to work out the finer details.
-
@phillycodehound @fediversereport @Mastodon I know there's work being done on generic share and follow buttons with the Web Intents stuff by @dansup but in terms of APIs, more definitely needs to be done in that area. I might have an idea but would need to work out the finer details.
-
@trwnh Yes, that's accurate. I meant “pure” colloquially in contrast to “implementation-specific” (hence the scare quotes), but it is indeed WebFinger that's being extended, not ActivityPub itself.
@julian @fediversereport the implementation is still specified by that FEP, though? it assumes that the target template of each link is following the protocol defined by its link relation. so it's a kind of bespoke API endpoint (one for each activity type, with seemingly no way to prefill any information except the type and the object, and even then only for an extremely limited subset of types)
-
@julian @fediversereport the implementation is still specified by that FEP, though? it assumes that the target template of each link is following the protocol defined by its link relation. so it's a kind of bespoke API endpoint (one for each activity type, with seemingly no way to prefill any information except the type and the object, and even then only for an extremely limited subset of types)
@trwnh Your point is going over my head.
(a) Yes, the FEP specifies some behavior, with the goal being that different ActivityPub server software can implement it to achieve vendor-independent share (etc.) buttons.
(b) I've never implemented FEP-3b86 myself, so I'm probably the wrong person to discuss possible shortcomings. Going by the examples, its mapping of parameters to object properties appears to make it quite flexible. But I don't know – take it up with @benpate.
-
new from me: FR#156 - Share Where?
on @Mastodon 's new Share button, the Mastodon API and protocol ownership
@fediversereport @Mastodon The share button does not use the Mastodon API and has nothing to do with whether 3rd party apps or different platforms choose to implement the Mastodon API or not.
-
@fediversereport @Mastodon The share button does not use the Mastodon API and has nothing to do with whether 3rd party apps or different platforms choose to implement the Mastodon API or not.
@Gargron @fediversereport @Mastodon Can the share button also link to other platforms, or only to a Mastodon instance? -
@Gargron @fediversereport @Mastodon Can the share button also link to other platforms, or only to a Mastodon instance?
@hiker @Mastodon @fediversereport If it has a /share page, it works. The tool doesn't care.
-
@hiker @Mastodon @fediversereport If it has a /share page, it works. The tool doesn't care.
@Gargron
But why is it called Mastodon Share Button and not Fediverse Share Button? @Mastodon @fediversereport -
@trwnh Your point is going over my head.
(a) Yes, the FEP specifies some behavior, with the goal being that different ActivityPub server software can implement it to achieve vendor-independent share (etc.) buttons.
(b) I've never implemented FEP-3b86 myself, so I'm probably the wrong person to discuss possible shortcomings. Going by the examples, its mapping of parameters to object properties appears to make it quite flexible. But I don't know – take it up with @benpate.
@julian we may just be using words differently. my confusion was regarding "activitypub-based" and "[not] implementation-specific". to me, both of those statements are false.
i think i may have already mentioned to @benpate the lack of flexibility with the FEP and also the explosion of one-off "intents", as i prefer a single outbox, much as i prefer my definition of "activitypub server" to involve publishing arbitrary activities without enumeration.
-
@julian we may just be using words differently. my confusion was regarding "activitypub-based" and "[not] implementation-specific". to me, both of those statements are false.
i think i may have already mentioned to @benpate the lack of flexibility with the FEP and also the explosion of one-off "intents", as i prefer a single outbox, much as i prefer my definition of "activitypub server" to involve publishing arbitrary activities without enumeration.
-
@julian @fediversereport this was tried and then rolled back at some point, for reasons, though I forget what those were
-
@Gargron
But why is it called Mastodon Share Button and not Fediverse Share Button? @Mastodon @fediversereport@hiker @Mastodon @fediversereport My impression is that a lot of people would be upset with us if we published something claiming to be a "fediverse" tool, as if we own the fediverse. Of course, there's also not nearly the same amount of brand recognition for the fediverse as a concept. There are at least 3 unofficial symbol proposals and most people outside the fediverse aren't familiar with any of them.
-
@hiker @Mastodon @fediversereport My impression is that a lot of people would be upset with us if we published something claiming to be a "fediverse" tool, as if we own the fediverse. Of course, there's also not nearly the same amount of brand recognition for the fediverse as a concept. There are at least 3 unofficial symbol proposals and most people outside the fediverse aren't familiar with any of them.
@hiker @Mastodon @fediversereport Probably the body best suited to publish something like a fediverse share tool is the @swf. Regardless, I think we're well within our rights to publish a tool our users asked for, catered to our own platform. Not everything has to be for everyone. PeerTube has a PeerTube app and Sepia Search, nobody is upset (nor should they be) that those don't work with Mastodon.
