💸💸 Help me contribute to KDE and do these videos: 💸💸Paypal: https://paypal.me/niccolovePatreon: https://www.patreon.com/niccoloveLiberapay: https://liber...
Thing is, if this takes off and websites adopt it, FF will be forced to integrate it aswell. I’d be fine with some websites not working in FF, but my mother will call me and say “the internet is broken”. I guess Mozilla doesn’t want and/or cannot afford that.
That is correct, but for now, Mozilla has the right stance on the matter.
I’m still waiting for what Apple’s stance is. They integrated functionality into Safari that technically works similarly, but that’s only used for captcha verification. I can see them choosing either side to be honest. They can embrace the Web Integrity API because it fits their “closed ecosystem” (in case of iOS devices) type of product quite well, but on the other hand they don’t really have a website that would be suitable to use the Web Integrity API, so why would they give in to what Google wants? If Apple doesn’t integrate Web Integrity API into Safari, I don’t see any major website using it. They can’t afford to lose ~28% of the mobile market.
Likely true, but as someone pointed out in another thread, it should be possible to “technically” comply with WEI enforcement, and then have a transparent abstraction layer to extract the “enforced” markup and code, exposing it to the user-facing browser to interpret like it normally would.
It’s some real asinine bullshit software engineering that shouldn’t be necessary, but it should work.
Thing is, if this takes off and websites adopt it, FF will be forced to integrate it aswell. I’d be fine with some websites not working in FF, but my mother will call me and say “the internet is broken”. I guess Mozilla doesn’t want and/or cannot afford that.
That is correct, but for now, Mozilla has the right stance on the matter.
I’m still waiting for what Apple’s stance is. They integrated functionality into Safari that technically works similarly, but that’s only used for captcha verification. I can see them choosing either side to be honest. They can embrace the Web Integrity API because it fits their “closed ecosystem” (in case of iOS devices) type of product quite well, but on the other hand they don’t really have a website that would be suitable to use the Web Integrity API, so why would they give in to what Google wants? If Apple doesn’t integrate Web Integrity API into Safari, I don’t see any major website using it. They can’t afford to lose ~28% of the mobile market.
Likely true, but as someone pointed out in another thread, it should be possible to “technically” comply with WEI enforcement, and then have a transparent abstraction layer to extract the “enforced” markup and code, exposing it to the user-facing browser to interpret like it normally would.
It’s some real asinine bullshit software engineering that shouldn’t be necessary, but it should work.