@violet Pleroma has full-text search, but tagging is helpful for post discovery. Had Mastodon never happened, we would likely live in a world now where the fediverse had ontological tags throughout the ecosystem.
since you intend to subpost me (and somebody boosted it) i feel the need to provide an informative reply.
- The "foundation of the fediverse" is ActivityStreams 2.0.
- ActivityStreams 2.0 specifies the use of ontological tags for the purpose of content filtering.
- The Mastodon CW system does not use ontological tags, but instead abuses the `summary` field on messages.
- Mastodon's developer was not in favor of CWs, CWs landed in Mastodon as "spoiler alerts" and this is reflected in the Mastodon API where CWs are referred to as spoiler_text.
- Using ontological tags for filtering would allow the end user to decide for themselves what content they should see or not see, while encouraging creators to tag their posts by design as they help to improve reach and discoverability, not just improved curation.
- I actually support authoring posts with as much tagging as is practical, but only if the experience is frictionless. Mastodon's CW system, due to political compromise, is worst of all possible worlds: high friction for both authors and consumers with little control given to neither.
i donβt know, i havenβt ever looked at the docs, but lets be real, with the exception of mastodon (Gargron is a technical writer at heart), most fedi software has crap docs ;)
Trev sold Gargron on something resembling CWs by referring to them as βspoiler alertsβ, this is why the Mastodon API still refers to them as spoiler_text
basically no iteration on CWs has happened since
meanwhile, Qvitter and Pleroma FE were working on filters using ontological tagging (which would have notably worked without any need for modifications to OStatus)
and for completeness, lets discuss the other fediverse players:
Pleroma eventually added support for Mastodon-style CWs (we call them Subjects as the AP spec intends, but optionally do the collapse) in early 2018.
GNU Social (and Qvitter) still do not support CWs.
@sivy@Pixley yes, it's technically already possible in Pleroma. i have a custom filter module running on pleroma.site that rejects posts with links from accounts that have never had any other post observed by our instance, for example. helps tons with spam.
this was very early in Mastodon development, but the "CW as message subject" verses "ontological tagging" argument has been ongoing since 2016. i remember it distinctly from when i was still using GNU Social.
2. you address those posts to `as:Public` (Public or Unlisted scope)
3. object fetches of `as:Public` labelled posts in activitypub have no authorization requirement.
4. because of this, when threads get reconstructed, your instance is willingly giving the instances you blocked, your posts.
5. because of this, your instance block is "bypassed."
instance blocking, when it refers to `as:Public` labelled posts, is only for inbound content. because of the semantics of `as:Public` posts, there is no possible way to stop unauthorized instances from fetching them, as there is no authorization step in fetching `as:Public` objects. in fact, authorization in activitypub at all is left unspecified.
my blog discusses that issue and more issues where ActivityPub performs in ways that are unexpected.
this will eventually be solved with OCAP, which there are a few proposals that are moving toward singularity. of course, that requires big elephant to actually implement them. however, OCAP is the centerpiece of the next revision to ActivityPub, so it shouldn't be that big of a deal.
and when you imply Pleroma is morally defective, you empower the people shitting on your friends by legitimizing their view with your own social capital.
@monorail oh, right, Canada never had diebold election machines.
basically Diebold Election Systems is a company which made polling machines that were trivial to compromise, and many people have said that various contests using Diebold machines were rigged.