Conversation

Notices

1. Embed this notice
   Matthias Pfefferle (pfefferle@mastodon.social)'s status on Wednesday, 25-Sep-2024 14:25:53 JST Matthias Pfefferle

   • yuki - queen of the snow

   @yukijoou what platform are you on? is it using the old mastodon way: simply use the summary as warning, without checking for the sensitive flag? https://docs.joinmastodon.org/spec/activitypub/#sensitive

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Wednesday, 25-Sep-2024 16:04:33 JST Matthias Pfefferle

     in reply to

     • yuki - queen of the snow
     • mcv

     @mcv @yukijoou mastodon uses `as:sensitive` to check if the summary is a summary or a content warning. https://docs.joinmastodon.org/spec/activitypub/#sensitive

     I really like the idea of the sensitive flag, because to use the summary as a synonym for content-warning harms the spec.

     Maybe we have to file some issue!?!

   • Embed this notice
     mcv (mcv@friendica.opensocial.space)'s status on Wednesday, 25-Sep-2024 16:04:35 JST mcv

     in reply to

     • yuki - queen of the snow

     @pfefferle @yukijoou

     I notice that when I (on Friendica) respond to a Mastodon post with a content warning, I get an <abstract> element, and it certainly doesn't act as a content warning. So there seems to be some inconsistency in implementation.

     That said, I'm not getting a content warning from this post.

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Wednesday, 25-Sep-2024 16:07:44 JST Matthias Pfefferle

     in reply to

     • yuki - queen of the snow
     • mcv

     or maybe it is because the WordPress plugin does not send an `as:sensitive: false` yet. we have a PR for that, I will try to release a new version to see if this will fix it. https://github.com/Automattic/wordpress-activitypub/pull/900

     can I maybe ping you two, to run test on your instances @mcv @yukijoou ?

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Wednesday, 25-Sep-2024 16:36:09 JST Matthias Pfefferle

     in reply to

     • yuki - queen of the snow
     • mcv

     @mcv @yukijoou sure, overloading a different field is always bad!

   • Embed this notice
     mcv (mcv@friendica.opensocial.space)'s status on Wednesday, 25-Sep-2024 16:36:11 JST mcv

     in reply to

     • yuki - queen of the snow

     @pfefferle @yukijoou

     A sensitive flag sounds like a great idea, but repurposing a summary as content warning based on a flag sounds like a bad idea to me. If there's no explicit content warning field, I think a spoiler tag is a better fit, because that already functions similarly without the flag.

     But I'd prefer an explicit content warning field. There's clearly a need for it, and if it's explicit, you could set your client to always show or hide certain content.