> I agree with you. I’m very pro-privacy/anti-surveillance and pro-freedom, so I’m entirely against the invasive ID-based systems, but the problem you highlight

> I agree with you. I’m very pro-privacy/anti-surveillance and pro-freedom, so I’m entirely against the invasive ID-based systems, but the problem you highlight is pretty real and has to be addressed somehow, and I’m just not sure what the solution is. The solution is client-side filtering/blocking software on the machines you own. And if your response is "but that's hard", that should increase your confidence that server-side filtering and verification are unacceptable. If even tech-savvy people can't get verification working on a local device-- which has the full, correct context who is using it and what should be blocked-- then certainly it's not going to get any better by mandating a solution at scale on the public Internet, where there is much less context about the individual user, credentials can be mocked, proxies can be used, and so on.