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
github.com/whatwg/html/issues/…
Should we remove XSLT from the web platform?
What is the issue with the HTML Standard? XSLT v1.0, which all browsers adhere to, was standardized in 1999. In the meantime, XSLT has evolved to v2.0 and v3.0, adding features, and growing apart f...mfreed7 (GitHub)
reshared this
Aslak Raanes
in reply to ansuz / ऐरन • • •Triaging security issues reported by third parties (#913) · Issues · GNOME / libxml2 · GitLab
GitLabansuz / ऐरन
in reply to ansuz / ऐरन • • •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 / ऐरन
in reply to ansuz / ऐरन • • •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?
reshared this
Bubu reshared this.
Oblomov
in reply to ansuz / ऐरन • • •and XSLT isn't even just for RSS. It can be used as an alternative to server-side includes to assemble (X)HTML documents from fragments
labrador.oblomov.eu/uberprufun…
and to produce SVG plots
wok.oblomov.eu/tecnologia/plot…
and sparklines
wok.oblomov.eu/tecnologia/plot…
wok.oblomov.eu/tecnologia/spar…
from XML data, with potentially massive saves in hosting costs.
It could do even more if browsers hadn't stopped at XSLT1.
Google's control of the web must be uprooted.
Plotting sparklines with XSLT
wokjonny (good kind)
in reply to Oblomov • • •@oblomov
Saw you in there getting your comments hidden while telling good history. Thanks for that. Hiding replies definitely is having a streisand effect there
Oblomov
in reply to jonny (good kind) • • •@jonny sadly it won't matter. Google has a stranglehold on the WHATWG, Mozilla is subservient and guided by people who couldn't care less about its users (see them shoving AI everywhere), and Apple is happy to follow suit as well.
We'd need someone truly independent of GAFAM on the WHATWG that could block the process.
@dillo ? @servo ?