Post · bonfire.cafe

@ansuz@social.cryptography.dog · 2 months ago

chrome developers: we are thinking of dropping support for rendering RSS feeds as something other than garbage code. does anyone have any reasons not to do this?

developers from many different backgrounds: yes, I rely on normal people being able to understand RSS for my business. dropping support will be disastrous for me because I can't rely on people to have some random extension installed.

chrome devs: OK well we're probably going to do it anyway because we can't be bothered to support web standards. uwu google is only a teensy wee company uwu

https://github.com/whatwg/html/issues/11523

#xslt #standards #openWeb

Gadfly (-booq-)

@gaditb@icosahedron.website replied · 2 months ago

@ansuz Holy frick did you look at the actual minutes of the WHATNOT meetings?

There was moderate consensus that those statistics might actually be undercounts, and then he f---ing GHOSTED them!

Gadfly (-booq-)

@gaditb@icosahedron.website replied · 2 months ago

@ansuz

WHATNOT meeting on 2025-03-27
https://github.com/whatwg/html/issues/11146#issuecomment-2759059949
"""
panos: next item, removing XSLT. There are usage numbers.
stephen: I have concerns. I kept this up to date historically for Chromium, and I don't trust the use counters based on my experience. Total usage might be higher.
dan: even if the data were accurate, not enough zeros for the usage to be low enough.
mason: is XSLT supported officially?
simon: supported
mason: maybe we could just mark it deprecated in the spec, to make the statement that we're not actively working on it.
brian: we could do that on MDN too. This would be the first time we have something baseline widely available that we've marked as removed.
dan: maybe we could offer helpful pointers to alternatives that are better, and why they're better.
panos: maybe a question for olli. But I like brian's suggestion to mark it in all the places.
dan: it won't go far unless developers know what to use instead.
...

Gadfly (-booq-)

@gaditb@icosahedron.website replied · 2 months ago

@ansuz
...
brian: talk about it in those terms also. Would anyone want to come on the podcast and talk about it? I'm guessing people will have objections.
emilio: we have a history of security bugs, etc.
stephen: yeah that was a big deal
mason: yeah we get bugs about it and have to basically ignore them, which sucks
brian: people do use it and some like it
panos: put a pin in it, and talk with olli next time?
"""

WHATNOT meeting on 2025-08-07
https://github.com/whatwg/html/issues/11527#issuecomment-3163230726
"""
Minutes: We quickly went through the existing issues and PRs and skipped XSLT as Mason wasn’t here.
"""

Aslak Raanes

@aslakr@mastodon.social replied · 2 months ago

@ansuz And this happens now because the open source library they used for XSLT was made by people that got burned out by multi billion companies using it without giving something back https://gitlab.gnome.org/GNOME/libxml2/-/issues/913

ansuz / ऐरन

@ansuz@social.cryptography.dog replied · 2 months ago

my favourite* part is how when someone commented that google is a nearly 2.5 Trillion dollar company the team hid it as off-topic

* it's actually it's one of my least favourite parts

ansuz / ऐरन

@ansuz@social.cryptography.dog replied · 2 months ago

chrome developers: see, we need to drop support for this feature because the library we use has vulnerabilities

web devs: why does it have vulnerabilities? can't they be fixed?

chrome devs: welllll, there's one person maintaining it for zero compensation even though pretty much all major browser vendors rely on their work and we keep sending new bug reports for them to fix and they basically told us to fuck off after years of exploitation

web devs: excuse me, what?

chrome devs: yea, so unreasonable, right?

ansuz / ऐरन

@ansuz@social.cryptography.dog replied · 2 months ago

lol they locked the discussion as "too heated"

#missionAccomplished #weDidItFedi

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.0-rc.3.1 no JS en

Automatic federation enabled