There's really no rational reason for third-party cookies to still exist. The only reason they're still around is because an advertising company's browser has like 97% market share.
The order doesn't mandate that. It mandates google SELL the data it has collected on people to third parties.
There are also privacy focussed, ad blocking focussed alternatives trivially available on the market....and people are not choosing them.
Any company which buys Chrome (Microsoft?) will have just as strong an incentive as Google to track people and run ads.
FWIW, Chrome has a 66% market share: https://gs.statcounter.com/browser-market-share
======
Disliking a company doesn't justify any arbitrary policy against that company
It already owns Edge. I would rather bet on Meta or Amazon.
There's no way Meta or Amazon will (/should) be allowed to buy chrome.
Doesn't really seem like much of a win for consumers though... it's just trading one personal data hungry megacorp for another.
I suppose it would help Meta greatly expand their ad business, to places far beyond FB/IG.
That would have been nice in 2014 but in 2024 the big ad industry is ready.
The only ones who will hurt the most are the ones without tie ins to authentication systems like Google auth or FB auth or apple ID etc.
Although I'm sure theres plenty of mega databases which don't need overt auths to ID a user. And contextual ads work just fine.
Start with the Sherman act and then see that "what antitrust means" has had a long, changing history. By the way, the European understanding of antitrust still includes harm to competition as well, which often pops up on HN (e.g. how does Facebook's action harm consumers? That was not the question!).
Yet, you have lots of people in this thread claim that we have always been at war with Eastasia.
>This law aims to promote fair competition and prevent unfair business practices that could harm consumers. It prohibits certain actions that might restrict competition, like tying agreements, predatory pricing, and mergers that could lessen competition.
>The Antitrust Division enforces federal antitrust and competition laws. These laws prohibit anticompetitive conduct and mergers that deprive American consumers, taxpayers, and workers of the benefits of competition.
Both are aimed squarely at consumer benefit. Restrictions on anticompetitive behaviour and mergers *where those things impact consumer benefit.*.
Mergers and actions against competitors are obviously allowed in the normal course of business.
Lots of people have other ideas about what kind of antitrust law they'd like to see, but such a law has not passed the US Congress.
https://www.justice.gov/atr/antitrust-laws-and-you#:~:text=T....
“Taxpayers” is an extremely broad category as well, though you need an appetite for it to argue through that clause.
Though I think you can easily make a consumer argument for Chrome being unbundled (competition for Chromes default search engine pick)
Monetizing browsers requires either subscriptions or (further) enshittification of the web experience. Forcing /market/ competition into the space will not be great for consumers, IMO.
Perhaps some antitrust action would help with this.
So, it's plainly written - ations don't have to actually harm consumers, the fact they could do so is enough - and the key criteria is that they might restrict competition.
You paraphrased incorrectly. The correct paraphrasing would be, “Restrictions on anticompetitive behaviour and mergers where those things deprive consumers of the benefits of competition.”
Competition is the heart, NOT consumer benefit.
It would be nice to have a completely open source browser that can be built with a simple one liner from cargo. Having several thousands of eyes on the code daily to check for telemetry violations, privacy issues, security, and performance daily in mostly a single language, small, and well structured browser repo would be phenomenal compared to the disjoint jumbled messes we have today.
Most developers work with a Unix mindset (do one thing well, with focus on simple and easily managed code), which tyically means telemetry is _wildly_ out of line (offers no real benefit for the basics while adding huge complexity), so privacy and security are naturally far better. Lynx like TUI browsers are a nice idea, but unfortunately sometimes an image is desired to be manually viewed, or javascript is required. It would be wonderful if javascript were simply dropped from most websites, but we don't live in that world, so we're stuck with the next best thing (disabling all js until explicitly allowed by the user).
These are the types of things people in software devs typically care about, which there are many in HN.