chadgpt2

Honest question: Is there anything scary about this apart from lowering your ISP's reputation score?

Both are terrible for privacy so it comes down to which one has a nicer screen now. :(

I'd rather have Google check an Apple phone attestation than have Google check a Google phone attestation, and vice versa, though, because you can assume each company is trying to keep as much information private to themselves instead of giving it to the other. Google is probably just getting "yes it's an Apple phone" and some kind of temporary token, instead of my IMEI, IMSI, phone number, all signed in accounts, biometrics and so on.

Luckily the marketplace of money will ensure that businesses who block their customers shrink and businesses who don't block their customers grow.

Violating ToS isn't illegal in most cases. Companies just put scary looking clauses in their ToS to discourage you from doing things they don't like.

How would the phone camera know the domain name of the website displaying the QR code it's scanning?

Was this FOSS or commercial?

If it's commercial software, you're paid to make it work, no matter how stupid that may be, and forced stupidity isn't your problem.

If it's FOSS, you can tell the user to deal with it and close the ticket.

Do people expect that Instagram can't read their Instagram private messages? I don't think people expect that. And E2EE is not nearly as cheap as the HN crowd likes to pretend—how do those devices get those keys if not through a central service? Especially if one of them is a web browser?

Interesting idea, thanks for the link