As well they should, because (the hypothetical) you built and deployed something that relied for safety on users doing something you knew they wouldn't do.
Non-rhetorical question: how would you build this feature? What if the user lies about their age to avoid COPPA? What if the user uploaded 100 videos in the past, but didn't want to make this video public? Should we bug them every single time to verify if they wanted to make the video public? How many times should we bug them about it?
No, you make the default safe and make the "dangerous" option hidden behind an advanced menu, so at the very least you can be certain the user can read and follow directions. Like a two-stage weapon switch.
The tools you give them should come preconfigured to stop them hurting themselves, because you already know they will if you don't. It's not hard to go from that knowledge to questioning what it means if the defaults are harmful.
