What the fuck is wrong with #GoogleChrome / #Blink developers and their obsession with making the #web worse for *everybody*?
https://github.com/whatwg/html/issues/11523
We need to break #Google's dominance on the #web yesterday, and make it painful for them.
Ten years ago they tried this shit with #SMIL
https://groups.google.com/a/chromium.org/g/blink-dev/c/5o0yiO440LM/m/YGEJBsjUAwAJ
the web standard for JS-less animations and interactions that can be used to build interactive #SVG graphics. That one was luckily aborted. Now it's time to put pressure on them to keep #XSLT in.
Especially if you're an #indieWeb supporter, you should consider this feature *essential*, as it's what gives you the ability e.g. to make your #RSS feeds nicely formatted even on browsers that have removed built-in support for them (i.e. basically anything except for #VivaldiBrowser).
Of course, it can be used for more than that. I wrote about this (in Italian) on my website a couple of years ago
@oblomov Hello, a question from a sympathetic programmer here. Why is it important to format RSS feeds for human browsability, and why XSLT in particular?
RSS was never intended to be directly viewable, and I would bet that in practice RSS is almost never valid XML anyway. That means it has its own serious security issues when we add XSLT
Just FYI I was an expert user of XSLT for DocBook conversions, so I am decently informed about the topic, but curious where XSLT is in 2025
@neilk because they are XML documents (when they are not, that's a generator bug, and that's irrelevant to the discussion), and one of the purposes of XSLT is specifically to make XML documents accessible to web presentation.
@oblomov I’m familiar with the technical vision. My question isn’t “what is the correct way to process XML” but more like “how many people would be affected if they couldn’t see an RSS document transformed by XSLT”?
Like maybe I’m not aware that millions of people use this every day? As far as I can tell web publishers have largely abandoned it. We have enough trouble convincing them to use RSS
@neilk there are some numbers in the links posted to the original issue, and that's still irrelevant.
Nearly half of the web is on WordPress, and therefore has RSS feeds, and despite the efforts by Google to suppress the format (this is just one more nail in its coffin) and Mozilla's spineless caving to the Google directive, it still enjoys widespread usage.
And it's not even the only use of XML+XSLT on the web. Now please go somewhere else with your sealioning.
@light
the fact that my threads are my spaces, even if the only moderation option that Mastodon offers is a total account block.
@oblomov
>even if the only moderation option that Mastodon offers is a total account block.
I mean, if someone is annoying you, don't you want to not hear from them ever again?
Or do you want to only not hear from them in one specific thread?
I get wanting that kind of thing. I used to get really annoyed by people from particular instances, but was unwilling to just instance mute them because of the few "good"/tolerable characters.
So I thought it would be cool if we had scripts that filtered our feeds based on complex rules. So I could have something like:
```
(host == $baddomain) hide
(username == $goodperson1) show
(username == $goodperson2) show
```
where rules are applied one after the other and latest takes precedence.
