topics VS semver

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.

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...

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/...

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.

> 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

> [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.

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).

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.

We increase the version of our product as specified in SemVer and deploy it to production, preferably following good deployment practices to have no downtime.

Using Conventional Commits ⭐ as a standard for your commit messages, makes Semantic Versioning 🔖 as easy as can be, with tools like Conventional Changelog 📄 Standard Version 🔖 and Semantic Release 📦🚀

Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.

npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.

We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.

Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org