Back in July, Google's work on a Web Integrity API emerged and many equated it to DRM. The company announced today it's not proceeding...
While WEI is thankfully cancelled, it's not entirely cancelled... They're planning on making it available still in WebViews with the intention that websites can check if a malicious Android app is trying to do a phishing scheme.
Seems like such a niche "security" feature... what are they really trying to accomplish here? Something seems fishy to me
Its a common practice to do exactly that. Just demand something very absurd and let people rage about it, then "step back" to "please the masses" while in reality your "step back" idea is the thing you actually wanted to do from the beginning on. But now people are happy about it.
Obviously this is more of a strategic retreat and nothing else. It's also a very common tactic to push for something crass, pull back, wait a bit and repeat.
Most commonly resistance gets weaker each time, because people are people.
Now if anyone thinks they made money with a retreat and won't try again, because it's obviously much more lucrative, which stone exactly are you living under?
You are 100% correct. Nothing is won till you make it impossible for Google to push forward or destroy their motivation for trying again later.
Ha, I didn't know there's a name for that, but it's definitely what I assume they're going to do. My initial reaction was to wonder what they'll now present as the "reasonable" option to WEI.
Considering they're rolling it out in Android, maybe they'll just wait a moment and then integrate it into desktop Chrome as well, just without any of the fanfare?
@4censord@dean@rysiek I can see where they could integrate and feature creep to what they really likely want, but in terms of webviews this would likely be beneficial for security.
They want to put it on the default webview in android, which doesn't seem like a huge deal to me. It would basically let apps that use webview for things like logging in beef up their security.
It's not like the entire concept of this API was bad, it's just that with Google's proposed implementation companies would abuse the fuck out of it to do bad things. Not having it in browsers pretty much eliminates that while still letting things like banking apps enjoy some of the benefits.
That's what Google want you to believe, forget about and step back. It's not over yet. We just stopped the first wave and it will get harder with each wave.
A win is when we have forced them to abandon the wretched plan. Them taking it elsewhere with a different name, only to be brought back in the future isn't a win - it's more or less the folly the Trojans committed with the Greek wooden horse.