Web-Environment-Integrity VS nativefier

Repo has be archived - "NOTE: This proposal is no longer pursued."

https://github.com/RupertBenWiser/Web-Environment-Integrity

[2] - https://github.com/RupertBenWiser/Web-Environment-Integrity/...

I think the best issue raised is: Why would I, as a user, want this?

https://github.com/RupertBenWiser/Web-Environment-Integrity/...

There were proposals for protecting against this in the WEI explainer under "Open Questions" https://github.com/RupertBenWiser/Web-Environment-Integrity/...

The Web Environment Integrity is yet another Google proposal for making the web worse for everyone but them.

Point me to anything which would give websites access to that information via WEI. There is nothing. I have seen nothing except FUD. Aside from that, this only attests for the device. Ad-blockers can be external. This does nothing for external ad-blockers.

Explicit non-goals for WEI:

"Enforce or interfere with browser functionality, including plugins and extensions."

https://github.com/RupertBenWiser/Web-Environment-Integrity/...

That also applies to Javascript, or being forced to use some form of an up-to-date browser. What is different with WEI?

I didn't see many people debating the actual text of the WEI explainer[0] on the HN posts about WEI, and that's probably because they were links to articles about WEI. The HN post for the explainer with the most upvotes only has 89[1], likely because most of HN treats the upvote as "I agree/like this" instead of "boost this topic for discussion".

0: https://github.com/RupertBenWiser/Web-Environment-Integrity/...

1: https://news.ycombinator.com/item?id=36785516

> If you don't want my browser to render content as it sees fit, don't serve the content over a protocol where that dynamic is inherent.

to play the devil's advocate, this is why google proposed the WEI (https://github.com/RupertBenWiser/Web-Environment-Integrity/...). Be careful what you wish for...

https://github.com/RupertBenWiser/Web-Environment-Integrity/...

I stopped reading after the explainer’s intro section. The first example is making it easier for websites to sell adds (lmao) and the other 3 are extremely questionable whether if the proposed remedy even helps. And it’s presented as a benevolent alternative to browser fingerprinting, as if we must choose between these two awful choices. It’s an absolute joke of a proposal.

Oh by "Web Environment" you mean "my machine" lol!

I already got caught by this - a https://github.com/nativefier/nativefier app wrapping Youtube Music doesn't work, because Google detects somehow that you are not using a trusted browser and refuses to serve.

AFAIK there's only nativefier and peppermintos' ice.

Install Nativefier from Terminal using the command npm install -g nativefier

Something like nativefier perhaps?

It's still not quite the same as Chromium webapps, which are just isolated windows in the same core process -- FFPWA spins up entire other instances of Firefox -- and in effect operates more like Nativefier (with Firefox instead of Electron/Chromium)

is Electron considered a browser? cuz Nativefier is what i use