Web-Environment-Integrity
topics
Web-Environment-Integrity | topics | |
---|---|---|
54 | 30 | |
536 | 564 | |
- | 2.1% | |
10.0 | 8.1 | |
6 months ago | 8 days ago | |
Bikeshed | ||
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Web-Environment-Integrity
-
Google apparently backs off on WEI
Repo has be archived - "NOTE: This proposal is no longer pursued."
https://github.com/RupertBenWiser/Web-Environment-Integrity
-
The boiling frog of digital freedom
[2] - https://github.com/RupertBenWiser/Web-Environment-Integrity/...
-
It's time we do a uno reverse to Web Integrity API
I think the best issue raised is: Why would I, as a user, want this?
https://github.com/RupertBenWiser/Web-Environment-Integrity/...
- Issues / Web-Environment-Integrity
-
EFF denounces Google's WEI proposal
There were proposals for protecting against this in the WEI explainer under "Open Questions" https://github.com/RupertBenWiser/Web-Environment-Integrity/...
-
Web Environment Integrity: Google strikes again
The Web Environment Integrity is yet another Google proposal for making the web worse for everyone but them.
-
Google’s Plan to DRM the Web Goes Against Everything Google Once Stood For
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/...
-
With merge of this pull request, Brave Browser disables WebEnvironmentIntegrity
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
-
Adtech is built on a privacy fault line
> 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...
-
The Right to Lie and Google’s “Web Environment Integrity”
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.
topics
-
How to Turn Off Google's "Privacy Sandbox" Ad Tracking–and Why You Should
The browser keeps track of he top 5 categories from this list of these 629 topics. https://github.com/patcg-individual-drafts/topics/blob/main/...
Other than when it returns a random topic, the browser only reveals a topic to a site if that site has observed the user on a site with that topic before.
- UX Is Misleading
-
Google Chrome just rolled out a new way to track you and serve ads
Delete Chrome.
“The intent of the Topics API is to provide callers (including third-party ad-tech or advertising providers on the page that run script) with coarse-grained advertising topics that the page visitor might currently be interested in.”
https://github.com/patcg-individual-drafts/topics#the-api-an...
-
Alert: No Google Topics in Vivaldi
Those are the top-level categories. Each of them has subcategories which are more granular. Not all of them are public, from what I can tell. Here's an example of some that are. https://github.com/patcg-individual-drafts/topics/blob/main/...
-
Go to Chrome://settings/adPrivacy to turn off the spyware that in Chrome
https://github.com/patcg-individual-drafts/topics/blob/main/...
>knows that you are male and sees that you've been recently interested in dresses and panties, and this website happens to be a far-right-leaning activist website, and decides to dox you, or blackmail you, or forward this information to Ron DeSantis's administration for possible criminal prosecution, you're all good with that?
If you want to keep topics a secret you can just block them. Every week of your 5 topics that gets selected there is a 5% chance that a topic in replaced with a random one. If you see a user's topic is /Shopping/Apparel/Women's Clothing/Dresses it could be there by chance. It would also require the site to take out a bunch of ads on these women clothing sites hoping that one of your future website visitors would see your ad.
-
Google is already pushing WEI (web DRM) into Chromium
> You seem to be taking things that are factual, normal, everyday, aspects of the WHATWG working process and trying to imply that chrome is doing something unusual, or untoward with its process here, but it isn't. It's doing what is necessary to make a proposal with WHATWG: have a trial.
And yet, we've seen many such proposals go through this process because Chrome is paying lip service to it. Whatever Google wants it ships. And Google wants this.
As an adjacent (ads- and tracking-related) example: Google's FLoC flopped, hard. So they immediatey shipped the replacement Topics API [1] despite there being no consensus. E.g. Firefox is against [2] (but Chrome presents Firefox's position as "No signal" in the feature status). And despite the fact that its status is literally "individual proposal, not accepted" [3]
Do not assume any good intent on Google's part when it comes to Google's business interests. Their intent is always malicious until proven otherwise. And there have been fewer and fewer cases when they have been proven otherwise.
[1] https://chromestatus.com/feature/5680923054964736
[2] https://github.com/mozilla/standards-positions/issues/622
[3] https://github.com/patcg-individual-drafts/topics
-
Google asks websites to kindly not break its shiny new targeted-advertising API
> [0] https://github.com/patcg-individual-drafts/topics/blob/main/...
Nice v1 at the end. We can assume that this list is final and will not be changed?
> nor (by policy) other kinds of sensitive PII.
Yeah, it just exposes interest in family planing, loans, ..., which we do know have absolutely no potential for abuse.
Or given the attempts to outlaw drag there is probably no potential way to use interest in Nail Care or Makeup in a negative fashion, right?
> Yes, if you assume the people who designed this API were idiots
I assume they are getting paid well to play the role.
- Say Goodbye to Privacy with Google Chrome's Latest Update! Aren't you happy that you're using Firefox instead? It's a good time to educate your Chrome friends.
-
What is "Ad privacy"?
It's related to Google's Topics API proposal, I guess. This new API automatically categorizes users into pre-defined "topics" that are inferred by the browser through a classifier model (basically matching the hostname with the classifier model). So, in the end, advertisers sent ads for these topics, and users within shall see them).
-
W3C re-launched as a public-interest non-profit organization
Don't take my word for it: WordPress treated FLoC as a security concern in 2021: https://make.wordpress.org/core/2021/04/18/proposal-treat-fl...
A good overview of the context: https://digiday.com/media/we-cant-un-floc-ourselves-googles-...
More detail: https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-...
When it comes to Topics, it's essential that there be hands on the wheel at W3C that approach the solidification of e.g. the Topics taxonomy https://github.com/patcg-individual-drafts/topics/blob/main/... from a neutral perspective that takes into account the various ways in which proposed topics could be dangerous, and how strongly to word the specification to prevent it from creeping in increasingly privacy-eroding ways in the future.
What are some alternatives?
use-cases - Uses Cases for the Anti-Fraud CG
AmIUnique - Learn how identifiable you are on the Internet
dillo-plus - A lightweight web browser based on Dillo but with many improvements, such as: support for http, https, gemini, gopher, epub, reader mode and more...
semver - Semantic Versioning Specification
SupplyChainAttacks
standards-positions
BrowserBoxPro - :cyclone: BrowserBox is Web application virtualization via zero trust remote browser isolation and secure document gateway technology. Embed secure unrestricted webviews on any device in a regular webpage. Multiplayer embeddable browsers, open source! [Moved to: https://github.com/BrowserBox/BrowserBox]
uBlock-issues - This is the community-maintained issue tracker for uBlock Origin
bikeshed - :bike: A preprocessor for anyone writing specifications that converts source files into actual specs.
brave-browser - Brave browser for Android, iOS, Linux, macOS, Windows.
encrypted-media - Encrypted Media Extensions
Plausible Analytics - Simple, open source, lightweight (< 1 KB) and privacy-friendly web analytics alternative to Google Analytics.