We should not show NSFW media in the media modals if the user does not have "show mature content" selected in their settings.

We should be passing this through as a parameter to the endpoint to avoid data wastage.

• [] If the user allows NSFW content, allow it in the the modal pager
• [] If the user does not allow NSFW content, filter out NSFW content

added scoped labels

cc/ @brianhatchet (to save us duplicating the issue)

added scoped label

assigned to @edgebal

changed the description

changed milestone to %Sprint:01/29 Abatic Aenome

changed weight to 2

changed time estimate to 2h

@edgebal this sounds like a simple filtering parameter. Please, let me know if I have underestimated the work

added scoped label and automatically removed label

assigned to @eiennohi

unassigned @edgebal

added scoped label and automatically removed label

changed milestone to %Sprint::02/12 - Bartone Baboon

assigned to @omadrid

added scoped label

unassigned @eiennohi

How did they open the modal without giving nsfw consent? I presume we are simply talking about nth screens with pagination and not the first one. We don't want to have to click nsfw accept twice.

Correct, we're talking about navigating through a feed and encountering NSFW content

@benhayward.ben @brianhatchet

• what is the current behavior? Is it that users who have not selected 'show mature content' are seeing the NSFW content when using the modal pager (when they've opened the modal on SFW content?)
• Is the current NSFW content in the modal pager blurred or not blurred?
• If unblurred, do you want me to make it blurry or make it so the pager skips it entirely?
• If blurred, I assume that means you want me to skip it entirely. Is that correct?
• If we are passing this through as an endpoint param, should this not also be an engine issue first?