My understanding is that they don't... practically at all. But if compelled by a court to give your information, they could later learn that the information you provided was false. Or maybe someone reported you and they ask for some type of verification. Either way, it's one of many tactics that can be used against someone, even if you only gave fake information to protect your own privacy.
Frivolous DMCAs have also been used to reveal identities of people someone didn't like.
I can see the argument from both sides... and maybe both is true. I think the same could be said about twitter... having to login to read tweets means they can easily track who looks at what... which is very valuable information to a lot of people with money.
I think the only issue with that is that when/if it is found out then the domain will likely be seized because you violated your contract with the registrar to provide accurate information.
But the RT patches have been available for 20 years... not sure why the fact that it is mainlined would suddenly expand its popularity? It might be easier to get started sure, but people doing RT were already going to such troubles anyway.
Batteries don't explode, they burn.
But actual explosives were planted in the mentioned devices.
I wish they didn't switch to requiring a login to search code... seems like a big privacy issue cause you just know they're saving all those searches and associating it with your account.
The problem is not near enough projects support reproducible builds, and many that do aren't being regularly verified, at least publicly.
Yea because I tested it myself. Nobody else seems to care, and if they did, I would think there would be a public way to see regular test results regardless.
I know this exists for some projects, but somehow nothing privacy-sensitive
I have seen people with an axe to grind use frivolous lawsuits to reveal domain identities, you don't actually have to do anything wrong for that to happen.
@refalo
@programming.dev