191–200 of 289 posts
RTFA - the user discovered that chrome was sending all text from all webpages to the translate service. The advice in the thread isn't "never connect to protonmail using Chrome." It's "don't use Chrome". 100% agree. Firefox is so good now, there's really no excuse.
Earlier quoted context omitted.
No it isn't. It's the difference between "Here's some money, please show this to young Democrats" and "Here's some money, please give me a list of young Democrats." That's a pretty damn big difference.
What stops Google from selling this list if the deal is good and nobody knows about it?
I don't understand how this is related to ProtonMail. It reads more to me like "never use Chrome [if you care about all of your web content being sent to Google]". Sure, ProtonMail is likely to have personal, private stuff in it but so does a bunch of other things, eg. internet banking.
Earlier quoted context omitted.
If you have Google Play installed (doesn't matter if you ever use it) then you'll also have Play Framework or whatever they call it, and that probably has permission to just about everything. If you have an Android phone and don't trust Google then what their apps ask for seems a bit irrelevant - you've almost certainly already given them whatever you don't want them to have.
I had Google Play, but I didn't have Google Account set up on the phone. And it is not like I have much choice - iPhones are overpriced (I don't think is is a good idea to spend over $600-900 for just a phone) and even less open and I trust Apple as much as Google.
This sounds like a religious view rather than one based in any evidence.
"But the conclusion is frightening : it means that the content of every webpage visited using Google Chrome is sent back to Google." This is how it always worked and the number one reason I'm avoiding Google Chrome.
They really have as an Organisation lost the plot on what’s acceptable.
Earlier quoted context omitted.
The issue with XHTML is not parsing, it's generating valid one. The internet got years to try, failed, time to switch to something else... Because parsing invalid XHTML, which all browsers ended doing, is more complicated than parsing HTML5...
It's pretty easy to generate a valid XHTML doc. The issues come when someone is editing by hand and doesn't care. > Because parsing invalid XHTML, which all browsers ended doing, is more complicated than parsing HTML5... I don't understand what you mean. Isn't the non-strict parser for XHTML just the normal HTML parser? The complication levels should be equal.
In the face of arbitrary user-content, like comments? Are you checking they don't include a U+FFFF byte sequence in there? (Ten years ago almost none of the biggest XHTML advocates had websites that would keep outputting well-formed XML in the face of a malicious user, sometimes bringing their whole site down.)
It's absolutely possible to write a toolchain that ensures this, just essentially nobody does.
> Isn't the non-strict parser for XHTML just the normal HTML parser?
Yes. It's literally the same parser; browsers fork simply based on the Content-Type (text/html v. application/xhtml+xml), with no regard for the content.
The bigger problem with XML parsers is handling DOCTYPEs (and even if you don't handle external entities, you still have the internal ones), and DOCTYPEs really make XML parsers as complex as HTML ones. Sure, an XML parser without DOCTYPE support is simpler than an HTML parser, but then you aren't parsing XML.
Earlier quoted context omitted.
The simple fact that Firefox is Open Source, therefore auditable, while Chrome is not. ps. Nope, Chromium is not Chrome.
So use Chromium?
I just don't understand how so many people in the HN community, who are so vocal about privacy, turn around and use Chrome. Don't feed the beast.