OK folks, we need to stop assuming #Mastodon is the entire #Fediverse and expecting its idiosyncrasies to be mandated on everyone else.

Emelia 👸🏻

@mikedev we can agree to disagree.

(Also Emoji's haven't historically been hashtags in anything that used TwitterText, since that library only supports ascii hashtags)

Mike Macgirvin 🖥️

I just spit beer all over the lounge. You're serious?

bumblefudge

@fe06 @julian @santisbon the specs aren't that hard to extend, no protocol design experience necessary! tag me here if you open a PR describing this kind of property extension on https://codeberg.org/fediverse/fep/ and i'll chip in a little editing, it gets easier after you've written 1 or 2

bumblefudge

@santisbon @fbievan this is a pretty useful cheat-sheet!

julian

@[email protected] definitely will be requesting some assistance when I draft an FEP regarding topic synchronization!

bumblefudge

@thisismissem @santisbon I totally agree that the solution is a FEP for implementation to opt-in to universal CW support, whether it's written by someone (Em) with a deep knowledge of what upgrade path for Masto is feasible and fully backwards-compatible, or by someone deep in peertube/lemmy/etc and familiar with what would require the least or no lift from those major implementations to present a unified front. Or (best of all worlds)... both?

silverpill

@thisismissem @santisbon Lemmy is implementing "post tags" which are similar to content labels: https://github.com/LemmyNet/rfcs/blob/main/0004-post-tags.md. Perhaps you could collaborate? They seem to be interested in such FEP too: https://github.com/LemmyNet/rfcs/pull/4#discussion_r1679203468

cc @julian

silverpill

@mikedev @thisismissem I think content labels should be different from hashtags on the protocol level, but in UI they can be unified.

Emelia 👸🏻

@silverpill @santisbon @julian yeah... I was about to say that those look like hashtags but slightly different (no hash)

It'd be really great if they came to an AP issue triage or something; I'm semi often being tagged by others in relation to Lemmy work, and I'm not sure I've the bandwidth to subscribe to watch the entire project.

Definitely open to collaborate with projects on trust & safety if I can (sometimes time is against me)

Emelia 👸🏻

@silverpill @santisbon @julian
@by_caballero

I think there's two parts here: free-form content warnings where entropy is extremely high, and then more structured content labels, which should ideally have fairly low entropy.

(Cont)

Emelia 👸🏻

@silverpill @santisbon @julian @by_caballero

With content labels I was thinking along the lines of there being perhaps a few sets of them from well-known providers, e.g., from IFTAS, such that the URIs for a given label is the same no matter which AP software it came from, and supporting something like sameAs from the RDF/OWL world for linking tags from different providers.

I think if you do it per-community, you'll see fragmentation of the content labels, and they'll become less effective.

julian

@[email protected] if that's the case then I would caution you to keep the standard labels as vague as humanly possible, otherwise you'll end up playing referee over which specific, esoteric labels to add next (with very very vocal proponents, I'm sure!)

But... Why not both?

Possibly even a first line, standardized "opinionated" and "promotional" CW tags, and additional community specific CW tags.

Steve Bate

@santisbon @fbievan Nice diagram, but I don't see any Actor base type in the normative specs.

santisbon

@steve @fbievan they are called "actor types" so I had to come up with an abstraction for the diagram to cleanly convey their shared attributes.

Emelia 👸🏻

@silverpill @santisbon @julian @by_caballero

That's basically fine, in that there's pretty clear definitions for a core set like blood & gore, violence, politics, etc. but of course others can always define their own set of additional labels — the idea is to move the labels to be separate from the community, such that we reuse common labels, rather than needing to constantly block/filter additional copies lf effectively the same label

santisbon

@by_caballero @thisismissem I like the notion of a proper extension for a "hiding" feature. Since a CW and a spoiler alert are essentially the same mechanism it might be good to give it a generic name that doesn't exclude either use. Something like "Preview".

Used together with a sensitive attribute goes really well. For example, a news org would not hide the content for a politics post since that's exactly what its followers expect on their posts but might want to designate a specific image or video as sensitive.

Emelia 👸🏻

@santisbon @by_caballero so yeah, in what I'm envisioning, a platform about movies & tv could totally have a "Spoiler" label, perhaps many (one for each movie/tv show) and we could have a parent label that could be used to block/filter all child labels (linked data yay)

But you probably wouldn't create a label for each episode, and instead use the content warning free text for that

santisbon

@thisismissem @by_caballero the more I think about it the more I lean towards making it as simple and consistent as possible. I prefer the idea of a preview field so we can stop misusing summary i.e. use it consistently across Note and Article. If someone wants to hide the content it doesn't really make a difference if it's because it might spoil the movie or trigger someone's arachnophobia; the end result is the same. Then sensitive can be applied to things like images and videos, with or without the need for a preview. I'll keep giving it some more thought but that's where I am right now.

Steve Bate

@santisbon @fbievan I understand, but those /shared properties/ are wishful thinking. The AS2 core spec states "Actor objects are specializations of the base Object type" and they are defined "in only the most generalized way, stopping short of defining semantically specific properties for each." The AS2 vocab spec uses the phrase "Actor Types" but those are the specific types listed in the spec and those derive directly from Object (with no Actor-related abstraction).

Emelia 👸🏻

@santisbon @by_caballero yeah, I've given this a fair amount of thought, I think the "content warning" is what'll be most used, but I think some may opt into using structured labels too, which I think would be good, but only with finite labels