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
If you are aware of this issue, it is your obligation to tell all of your friends, family, associates and coworkers to stop using Chrome immediately, and try out a new search engine.
It’s the least you can do.
This behaviour by Google is not going to stop. The mask has slipped too many times. They have become the very thing they swore to destroy.
Not many people will be ready to de Google their phones and stop buying their products. It’s the little things that will hurt them the most and show they’ve stepped over a line this last year or so.
For whatever reason I am the least convincing person on earth, and 99% of the time it’s pretty useful shit I’m trying to inform people about and they just want nothing to do with the information. The 1% is when I went full retard and thought GME was going to make me rich instead of much poorer and tried to get others to invest, I’m glad no one listened to me on that one.
Agreed, but I disagree about the first part. It being only available in webviews can’t really be abused and makes all the difference. Sure they could try to reintroduce all the bad stuff, even if the had cancelled it altogether, but for now this is a success.
Had to go brush up on what webviews was. you’re right, that really isn’t a big deal For WEI to be implemented on it
Big edit: nope! My original statement was correct, this is going to screw over people who use things like NewPipe, reVanced or Spotube on Android! F*** Google and WEI for Android!
This means that they will implement it, and then it’s only a tiny change to make it available everywhere if they decide to do so later.
The option alone also now also allows people to build stuff that will only work in those WebViews, rejecting to work without the integrity check, which is already a huge loss.
The option alone also now also allows people to build stuff that will only work in those WebViews, rejecting to work without the integrity check, which is already a huge loss.
Can you give a concrete example how this would be a huge issue? A webview is part of an app, which is already a closed system. If a developer wants to, they can already build their app using native UI with integrity checks. Now they can do the same when using webviews. It really has none of the implications it would have for browsers.
He means this builds all the backend and proof of concepts necessary to force it on every other environment, and websites will be prepared for the switch, giving the public that much less time to react when they push it to desktop again
It’s basically “OK, we can’t stop the pushback, so we’ll tell the public it will only work on android web view, but all teams keep working full steam, we’ll wait to merge into the bigger systems until all this dies down, and we won’t have lost any dev time!”
That’s what he wrote in his second paragraph and it’s a fair point. In his third paragraph (the one I quoted) he claims that just having that functionality in webviews is already a “huge loss” though and I was curious what kind of scenario he was thinking of.
You don’t think having to go through all this to stop it again next time, but it’s even harder because it can now be implemented orders of magnitude faster than before, counts as a “huge loss”?
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
We did it!
If it’s still available I some capacity, we didn’t do much. We gotta remain vigilant.
If you are aware of this issue, it is your obligation to tell all of your friends, family, associates and coworkers to stop using Chrome immediately, and try out a new search engine.
It’s the least you can do.
This behaviour by Google is not going to stop. The mask has slipped too many times. They have become the very thing they swore to destroy.
Not many people will be ready to de Google their phones and stop buying their products. It’s the little things that will hurt them the most and show they’ve stepped over a line this last year or so.
For whatever reason I am the least convincing person on earth, and 99% of the time it’s pretty useful shit I’m trying to inform people about and they just want nothing to do with the information. The 1% is when I went full retard and thought GME was going to make me rich instead of much poorer and tried to get others to invest, I’m glad no one listened to me on that one.
Agreed, but I disagree about the first part. It being only available in webviews can’t really be abused and makes all the difference. Sure they could try to reintroduce all the bad stuff, even if the had cancelled it altogether, but for now this is a success.
Had to go brush up on what webviews was. you’re right, that really isn’t a big deal For WEI to be implemented on it
Big edit: nope! My original statement was correct, this is going to screw over people who use things like NewPipe, reVanced or Spotube on Android! F*** Google and WEI for Android!
No; it is a big deal.
They will bide their time and polish the feature out on Android WebViews then make another push for Desktop.
You must never agree to allow WEI exist in any form. It WILL BE MISUSED AND ABUSED!
You’re completely wrong.
This means that they will implement it, and then it’s only a tiny change to make it available everywhere if they decide to do so later.
The option alone also now also allows people to build stuff that will only work in those WebViews, rejecting to work without the integrity check, which is already a huge loss.
Can you give a concrete example how this would be a huge issue? A webview is part of an app, which is already a closed system. If a developer wants to, they can already build their app using native UI with integrity checks. Now they can do the same when using webviews. It really has none of the implications it would have for browsers.
He means this builds all the backend and proof of concepts necessary to force it on every other environment, and websites will be prepared for the switch, giving the public that much less time to react when they push it to desktop again
It’s basically “OK, we can’t stop the pushback, so we’ll tell the public it will only work on android web view, but all teams keep working full steam, we’ll wait to merge into the bigger systems until all this dies down, and we won’t have lost any dev time!”
That’s what he wrote in his second paragraph and it’s a fair point. In his third paragraph (the one I quoted) he claims that just having that functionality in webviews is already a “huge loss” though and I was curious what kind of scenario he was thinking of.
You don’t think having to go through all this to stop it again next time, but it’s even harder because it can now be implemented orders of magnitude faster than before, counts as a “huge loss”?
deleted by creator
deleted by creator
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.
Specifically, everyone who’s not using Chrome and its derivates did it. Use Firefox, people.