Hacker News Reader

Comment by capableweb | Hacker News Reader

> How exactly does that work with end-to-end encryption?

Exactly how we deal with everything else that works across platforms: standardization. We've done it at least once before (SSL/TLS), I'm sure these rich and "amazingly smart" companies can figure out how to achieve it once again.

> Isn't there, again, some hardware security issues in play with that?

Is there hardware security issues with accept CC details on the web? Assuming the computer itself isn't compromised, the web seems to (again) have figured out how to deal with it across platforms, both OSes and browsers, why can't phone OSes do it?

View on HN

Ah, so now nobody can ever launch any new messaging features without reaching a consensus in a standardization body. Progress!

Nope, that's not how standardization works.

I'd refer you to the process of HTML/CSS/JavaScript if you want to see how it can work in a global manner that also works for innovation too (unless you'd argue that HTML/CSS/JavaScript is exactly the same in terms of "innovation" since they each first were created).

In short, the process is something like this: 1) a browser implements a new feature they think is useful 2) standard bodies start watching 3) another browser implements the same feature either the same way, or differently 4) standard bodies start working on a specification to unify the feature across browsers and OSes 5) Specification gets "blessed" and is now official recommendation 6) browsers modify their feature to be compliant with the specification

Step 1 of that process violates the law, if it adds new “core messaging capability”. Perhaps the EU considers “core messaging capability” to refer exclusively to functionality that already exists today, and it could not even in principle refer to anything that doesn’t already exist, but that seems vague and unlikely. If support for Unicode emoji did not already exist, would a vendor be allowed to unilaterally add it? It seems uncertain.

So now, instead of websites breaking from browser to browser. My messages will fail from each app? Browsers show how global standards fail and the only thing preventing 99.99% market share of chrome is the walled garden that is apple & safari

Yeah, web is the best example…

In short, the process is something like this: 1) Chrome implements a new feature they think is useful 2) Google uses their people in the standard committees to push it into the standards 3a) it's actually useful: other Browsers implement it or 3b) it's basically useful to Google: they'll continue blaming other browsers to not implement standards, “This website works only in Chrome” incoming

You have any evidence of this happening?

All cases I can think of for the last 4-5 years, have been Chrome/Firefox implements something -> The other implements it -> Standard pops up

What features has Chrome managed to standardize without having another browser implement the same feature?

Reply on news.ycombinator.com