this post was submitted on 06 Aug 2023
124 points (89.2% liked)
Asklemmy
43755 readers
1339 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Again, 2 huge points I pointed out, I am not the developer or the privacy focused engineers who are putting forward these ideas, and again, compromise. The option of "I don't want to do it" may not be on the table anymore. If it's going to happen, it would be better to compromise and instead push a privacy focused approach.
For this to be on the table you need to convince all the browser manufacturers to implement it and close the sources so it cannot be undone by the users or forked. And remove all the earlier copies and sources Next you need to ban tools like curl or wget because they can pretend to be browsers. If you want something that can't be removed in reasonable time realistically you have to demand full web drm a-la Google but this means a bunch of older computers needs to be thrown away just because they can't use newer browsers and/or newer OS.
Now that we figured out what needs to be done on the client site - let's talk about server side. You need to convince every porn site out there to perform this check. A few more interesting things to think about - how many porn sites are out there? What to do with those that won't follow your proposal?
In short - from technical point of view if you really want to achieve "enforced age verification" - internet must become a very different, much more closed system.
I mean they're already doing that, there's already a handful of states that require porn sites check a user's ID before granting access, that's why I keep reiterating compromise, because it's already happening. And the version they're pushing is we hand over our ID to ever site which then of course would be subpoenable. So, again, I don't know why you're thinking these solutions are the bad ones, the bad ones are already in place and being used, they're just trying to roll it out nationwide now.
And again, I really feel like I keep repeating the same point over and over and over and over and over again, if it's going to happen, which they're really trying to push through and looks like they are going to, a compromise would be to at least have a privacy focused approach.
A handful of states can require that, sure, but requiring is not enough. All the browsers and all the porn sites need to follow that and this is not going to happen
If the goal is to make sure there's age verification for users of some porn sites with some web browsers - yea, you can totally achieve that. A workaround is a) switch the website or b) switch the browser. That's security theater though. Wastes time and money, fails to achieve the goal. If the goal is to make sure age is tested for users of all the porn sites for users of all browsers - this goal cannot be achieved without massive effort.
They have internet with porn in it in other nations :)