AkkomaGang/akkoma

Fork 91

fix inconsistent image sensitivity behavior #21

New issue

Closed

opened 2022-06-26 17:59:09 +00:00 by toast · 6 comments

toast commented

2022-06-26 17:59:09 +00:00

Here's a summary of how things work(ed?) on pleroma:

images are marked sensitive when federating if the "mark image as sensitive" box is ticked
images on the frontend are marked sensitive if there is a subject/cw or a #nsfw tag

The consequence of this is that users of pleroma consistently garner ill will from all other frontend users, because the UX makes it appear as though having a cw or tag is enough to mark media as sensitive, despite this being a frontend behavior.
"Upstream" was unwilling to change this (there was also a rather heated discussion off-platform).

It would be nice if this negative effect on the fediverse as a whole was fixed.
How I see this happening, ideally:

purge the behavior to mark media sensitive on subject/cw/tag from the frontend (this is important for users to be able to inspect their own posts - most people will delete and redraft if they realize they posted something they intended to be marked sensitive without that being the case)
automatically tick "mark image as sensitive" if an attachment is uploaded while there is already a subject/cw or configurable set of tags

And optionally:

make it possible to mark individual attachments as sensitive

If any of this has already been done in akkoma's tree, please do just tick things out or comment on the state of things.

Here's a summary of how things work(ed?) on pleroma: * images are marked sensitive when federating if the "mark image as sensitive" box is ticked * images *on the frontend* are marked sensitive if there is a subject/cw or a `#nsfw` tag The consequence of this is that users of pleroma consistently garner ill will from *all other frontend users*, because the UX makes it appear as though having a cw or tag is enough to mark media as sensitive, despite this being a frontend behavior. "Upstream" was [unwilling](https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1082) to change this (there was also a rather heated discussion off-platform). It would be nice if this negative effect on the fediverse as a whole was fixed. How I see this happening, ideally: * [x] purge the behavior to mark media sensitive on subject/cw/tag from the frontend (this is important for users to be able to inspect their own posts - most people will delete and redraft if they realize they posted something they intended to be marked sensitive without that being the case) * [x] automatically tick "mark image as sensitive" if an attachment is uploaded while there is already a subject/cw or configurable set of tags And optionally: * [ ] make it possible to mark individual attachments as sensitive If any of this has already been done in akkoma's tree, please do just tick things out or comment on the state of things.

floatingghost commented

2022-06-26 18:04:35 +00:00

Owner

oh actually a lot of this functionality was already changed in my frontend release because i had a lot of the same thoughts

pleroma-fe (akkoma edition (akkoma-fe??)) has a setting to do almost exactly this, and won't modify the image sensitivity as seen by the user

oh actually a lot of this functionality was already changed in my frontend release because i had a lot of the same thoughts ![image](/attachments/08b8788a-8d3e-4aca-97b6-371d5d6c7a9e) pleroma-fe (akkoma edition (akkoma-fe??)) has a setting to do almost exactly this, and won't modify the image sensitivity as seen by the user

image.png

9.8 KiB

👍 1

toast commented

2022-06-26 18:05:44 +00:00

Author

That's a good start, and addresses the initial UX disconnect. It's off by default, right?

floatingghost commented

2022-06-26 18:08:00 +00:00

Owner

yep, off by default

it might be useful to have a little warning like "yes you have a subject line but the media is not sensitive" if you don't have it on though

yep, off by default it might be useful to have a little warning like "yes you have a subject line but the media is not sensitive" if you don't have it on though

👍 1

toast commented

2022-06-26 18:13:34 +00:00

Author

Ok, that'd make the first tick completed then. Automatic ticking and per-attachment settings might still be warranted. Also the warning as you mention.
Still, huge improvement relative to elsewhere.

Ok, that'd make the first tick completed then. Automatic ticking and per-attachment settings might still be warranted. Also the warning as you mention. Still, huge improvement relative to elsewhere.

floatingghost commented

2022-06-28 13:10:56 +00:00

Owner

added warning when you've got a subject line but nsfw is false

leaving as per-status rather than per-image, since that's the masto schema -> https://docs.joinmastodon.org/methods/statuses/

added warning when you've got a subject line but nsfw is false leaving as per-status rather than per-image, since that's the masto schema -> https://docs.joinmastodon.org/methods/statuses/ ![image](/attachments/40758441-e751-4296-bd5c-534c27ebb45d)

image.png

137 KiB

toast commented

2022-06-28 19:07:25 +00:00

Author

Sounds good enough to me then. Closing ^^