logoalt Hacker News

dataflowtoday at 12:34 AM2 repliesview on HN

I had the same reaction as you this entire time until half an hour ago when I saw the second link in this comment: https://news.ycombinator.com/item?id=47382650

Meta being behind all of these efforts makes it incredibly suspicious, especially given the New York law is ridiculously more invasive than the California one. It sure makes it seem like there's likely a larger plan here that this is merely facilitating.

So I don't think I can still buy it at face value that California's version is a good-faith attempt to balance privacy and child safety, even if that's what it is in the eyes of the legislature, given who's actually behind it and what else they've been pushing for.


Replies

lambdatoday at 2:03 PM

Just because Facebook supports it doesn't mean it's bad. They may not support it for the same reasons, they probably just don't want the cost and liability of doing identify verification themselves and so want to make sure all of the cost and liability is on the OS vendor.

Yes, the New York proposed law is far worse, and we absolutely should be pushing back against that. And Facebook doesn't care, because they only care about moving the liability onto the OS vendor, not on actual privacy.

But still, just because this was supported by Facebook doesn't make it bad. Sure, Facebook doesn't care about privacy, but they do care about not being liable for this, and in this case, they're right, it is actually much more efficient to centralize this function in the OS, and it happens that that way it can be done in a privacy preserving way as California's law shows.

show 1 reply
pocksuppettoday at 1:52 AM

The larger plan is probably to avoid banning social media for under-18s

show 1 reply