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 @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.
-
@hiker @Mastodon @fediversereport If it has a /share page, it works. The tool doesn't care.
-
@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
-
@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.
-
@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.
@gargron@mastodon.social that actually makes a lot of sense. I don't want to subscribe to the idea that you're on your way to the third E (😝)... that you're simply trying to stay in your lane is the simplest most logical explanation.