Discord age verification now locks stage channels, DMs, and adult content behind four ID methods — each with different privacy trade-offs worth knowing.
it would have to ask daily, because you can be 15 today and 16 tomorrow (idk what the age cutoff is), but it also says the date isn’t retained so you might be onto something
That’s a wide opening for a lawsuit, though. This is the kind of thing they’re probably telling the truth about, at least in as much as what they intend to do.
Even then, the prompt could be as easy as a “recheck” button that the user sees on age restricted media. Kind of like how their age verification bucket was going to be. Database side all they need to know is a boolean of true or false of if they are a minor or not. or /maybe/ a trinary (0,1,2) system if that wanted a distinguishment of < 13 13-17 and 18+ It doesn’t have to check daily, it only has to check when the user requests access to age restricted stuff.
it would have to ask daily, because you can be 15 today and 16 tomorrow (idk what the age cutoff is), but it also says the date isn’t retained so you might be onto something
Everybody says the data isn’t retained. It’s very stylish, today, to claim to delete unused data, at least until it get breached
That’s a wide opening for a lawsuit, though. This is the kind of thing they’re probably telling the truth about, at least in as much as what they intend to do.
Even then, the prompt could be as easy as a “recheck” button that the user sees on age restricted media. Kind of like how their age verification bucket was going to be. Database side all they need to know is a boolean of true or false of if they are a minor or not. or /maybe/ a trinary (0,1,2) system if that wanted a distinguishment of < 13 13-17 and 18+ It doesn’t have to check daily, it only has to check when the user requests access to age restricted stuff.