News for hackers. Stuff that matters.
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by userbinator on Sunday September 15, 2024 @08:37PM (#41551688)
It's Mozilla's documentation site. Firefox doesn't have the API. It has no obligation to even mention its existence. The only thing that documentation is doing is helping Chrome.

If I'm interpreting you correctly, please explain how you got from "mozilla.org documents this API" to "firefox is not acting as a user agent".

I'm speaking about browsers in general.

Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by croes on Sunday September 15, 2024 @08:45PM (#41551720)
It's bigger than that

>MDN Web Docs content is maintained by Mozilla, Google employees, and volunteers (community of developers and technical writers). It also contains content contributed by Microsoft, Google, and Samsung who, in 2017, announced they would shut down their own web documentation projects and move all their documentation to MDN Web Docs

https://en.m.wikipedia.org/wiki/MDN_Web_Docs

Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by userbinator on Monday September 16, 2024 @03:56PM (#41560017)
In other words, it's already been infected by the enemy.
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by Dylan16807 on Sunday September 15, 2024 @08:55PM (#41551766)
> It's Mozilla's documentation site.

I kind of want to emphasize "Mozilla's" too. It's not firefox documentation, it's web documentation.

> I'm speaking about browsers in general.

But you're specifically including firefox because of this page, right? That's a hell of extrapolation to make from them "helping" chrome by writing/hosting an article.

Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by refulgentis on Sunday September 15, 2024 @09:48PM (#41551994)
If it makes you feel any better, this sort of nihilist puritanism, combined with the people who actually sell data complaining to the EU it's "anticompetitive" they can't track me via 3P cookies, means this is DoA. And users are the only ones worse for it, modulo Google's sunk cost in investment in trying to do something better.
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by bastawhiz on Monday September 16, 2024 @06:30AM (#41554647)
> The only thing that documentation is doing is helping Chrome.

In what way is documenting the API helping Google? There's a big banner right at the top of the page saying Firefox and Safari aren't going to implement it.

Should Mozilla also not document -webkit- prefixed CSS properties?