SaaSHub helps you find the best software and product alternatives Learn more →
Topics Alternatives
Similar projects and alternatives to topics
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Fenix
Discontinued ⚠️ Fenix (Firefox for Android) moved to a new repository. It is now developed and maintained as part of: https://github.com/mozilla-mobile/firefox-android
-
user.js
Firefox privacy, security and anti-tracking: a comprehensive user.js template for configuration and hardening
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
privacytests.org
Source code for privacytests.org. Includes browser testing code and site rendering.
-
Plausible Analytics
Simple, open source, lightweight (< 1 KB) and privacy-friendly web analytics alternative to Google Analytics.
-
Matomo
Empowering People Ethically with the leading open source alternative to Google Analytics that gives you full control over your data. Matomo lets you easily collect data from websites & apps and visualise this data and extract insights. Privacy is built-in. Liberating Web Analytics. Star us on Github? +1. And we love Pull Requests!
-
fugu
Fugu is simple, privacy-friendly, open-source and self-hostable product analytics. 🐡 (by shafy)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
topics reviews and mentions
-
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.
-
A note from our sponsor - SaaSHub
www.saashub.com | 6 May 2024
Stats
patcg-individual-drafts/topics is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of topics is Bikeshed.
Sponsored