Baest (probably) has until July 1, 2023 to implement "Reasonable age verification", close registrations permanently, or migrate to revolver.
illust_32814898_20230504_032002.jpg

cc @hj @lanodan is there any way at all to omit posts marked as sensitive from the API for unauthenticated users?

@sjw @hj Could be either a backend setting or something like an MRF to put all things sensitive as followers-only (bleh).

But honestly, might be better to just remove API access from unauthenticated users as stuff is going to slip through regularly. (like FSE users typically don't tag porn as sensitive)

@lanodan @sjw @hj

> stuff is going to slip through regularly

from a legal standpoint this often doesn't matter. typically you just need to make a "reasonable effort" at whatever it is. so the combination of "you must tag NSFW" plus "we will (on a best-effort basis) force tag accounts and/or instances that don't do this" plus "unauthenticated users are not permitted to view NSFW tagged posts" should cover you as long as you actually do make a best effort attempt to force tag repeat offenders

@roboneko @lanodan @hj nope it will be my duty to verify the age of users before I give them access to NSFW media. This is why I want the ability to block NSFW at the API level.

Also blocking unauthenticated search would be really nice

@sjw @hj @lanodan separate issues. one being what the legal requirements for age verification are and the other being what level of effort you would need to exercise to prevent unauthenticated users (ie potentially not of age users) to view such material

my comment was regarding the second point. that if some amount of NSFW slips through it likely doesn't matter as long as the efforts being made to catch and correct it are "reasonable" same as for fedposts and etc

but yeah that would really suck if you had to verify age via legal documents for accounts. talk about death by bureaucracy and chilling effects on speech

@roboneko @sjw @lanodan @hj the bill says you need to verify age using either a government issued ID or public/private transactional data ("a sequence of information that documents an exchange, agreement, or transfer between an individual, commercial entity, or third party used for the purpose of satisfying a request or event. Transactional data can include, but is not limited to, records from mortgage, education, and employment entities").

however, it does also say in the bill that the website can not retain this information after it has been given to them, otherwise they will be held liable to the person's ID they kept, including any court costs. so it isn't something they are allowed to keep on file. kind of similar to a bartender looking at your ID real quick to make sure you can legally purchase alcohol.

it says that if 1/3 of a website contains harmful material, then age verification is necessary. if some things slip through by people not tagging stuff as NSFW, then it would surely not make up 1/3 of the content that the unverified user is seeing.

@beardalaxy @beardalaxy @roboneko @lanodan @hj I really need the ability to block sensitive posts from the API.

I've literally been asking for that feature for years.