(no title)
pteraspidomorph | 22 days ago
The only way for the server owner to circumvent the filter is to mark a channel as "NSFW", which doesn't necessarily mean the channel actually contains any NSFW content.
This change will not actually require ID for content confirmed to be NSFW. It will require ID for each and every "NSFW mode" (unfiltered) channel. The end result is that you have three choices:
- Ditch Discord features implemented in recent years (or at least this is currently possible) - this prevents a server from being listed as public;
- Require ID checks from all your users (per channel);
- Have everything scanned from all your users (per channel).
palata|22 days ago
Sounds weird to me. Pretty sure that they legally have to make sure that they don't host illegal content. Or does "NSFW" enable some kind of end-to-end encryption?
pteraspidomorph|22 days ago
You don't have to take my word for it, just check it yourself, although it seems that this week, they renamed the NSFW setting to "Age-Restricted Channel" (in preparation for this change, no doubt). The verification-related portion of the behavior I described was implemented for the UK months ago.
The description still contains: "Age-restricted channels are exempt from the explicit content filter."
EDIT: IANAL (or american) but if Discord was policing content for legality rather than age-appropriateness, wouldn't they lose DMCA Safe Harbor protections?