digitalcourage.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Diese Instanz wird betrieben von Digitalcourage e.V. für die Allgemeinheit. Damit wir das nachhaltig tun können, erheben wir einen jährlichen Vorausbeitrag von 1€/Monat per SEPA-Lastschrifteinzug.

Server stats:

818
active users

#xslt

28 posts26 participants4 posts today

Didn’t take long until someone accused me of being a Google shill 😂

If only you knew.

I’ve been accused of shilling for Apple or Microsoft, of being ivory-tower with my FLOSS thoughts, of not knowing anything about software development, and of being new to the industry.

So, since #Google and #WHATWG removing support of "obsolete" :drgn_sigh: #XSLT from their browsers — I remove support of their browsers in the nice looking page with my #RSS (Atom) feed, lol :drgn_up_blep:

On these browsers the feed.xml will looks like on the 1st image. Then on the proper browsers the feed.xml will looks like on the second image

Continued thread

New update: members of Whatwg are now claiming that XSLT should not be supported because it could facilitate XSS attacks:

github.com/whatwg/html/issues/

XSS stands for Cross-Site Scripting, and it's basically the idea that if a site is designed without adequate security precautions then an attacker can inject malicious scripts into a page.

For example, if I were to add some malicious code to this post, a Fediverse platform might add it to the page in a way that would indirectly run that code in your browser session when you view it. The platform on which you view it is therefore responsible for displaying posts in a way that treats them as untrustworthy inputs, rendering their content as text rather than full-featured and potentially dangerous HTML.

XSLT transforms XML documents into different structures, which might include scripts if the transformation injects untrusted inputs, but this is just a part of the way the web works regardless of your choice of markup language.

There are of course many legitimate cases where you'd want to inject JavaScript into a page written with XML, just as there are with pages written in HTML. Of course, these same people are not making the case that we should remove JavaScript from HTML.

This argument just doesn't hold up to any detailed scrutiny, but I guess they're hoping that people will see an acronym for an attack, and just accept it as justification for whatever they want to accomplish.

What is the issue with the HTML Standard? Background This is a follow-up to #11523. That issue raises concerns regarding security issues, code maintainability, and the complexity of aging browser c...
GitHubShould the web platform adopt XSLT 3.0? · Issue #11578 · whatwg/htmlBy tony-sull
Continued thread

in today's #XSLT news, the chromium dev who seems to be the main coordinator of this effort to drop support for a long-standing web standard commented on the github issue, which is locked to everyone but "contributors"

he links to a blog posts as an example of people being mean to him[1], and uhh:

a) the blog post actually seems like fair criticism to me

b) I probably wouldn't have seen the blog post had he not linked to it, so thanks, I guess

[1]: jonmsterling.com/01DI/index.xm

[2]: github.com/whatwg/html/issues/

I put scare-quotes on "contributors" because in this context it basically means members of their cartel, not anything egalitarian like people who contributed meaningfully to the discussion

Continued thread

If you're interested in experimenting with #XML & #XSLT to style a website I recommend Evan Widloski's project:
github.com/Evidlo/xsl-website
(his wildcard template to ignore html tags was super useful).
Paco Coursey also has a cool repo:
github.com/pacocoursey/xslt
And the #GrugBrained #ReadMe is worth the price of admission! Complexity very, very bad.

XSL Rendering Example. Contribute to Evidlo/xsl-website development by creating an account on GitHub.
GitHubGitHub - Evidlo/xsl-website: XSL Rendering ExampleXSL Rendering Example. Contribute to Evidlo/xsl-website development by creating an account on GitHub.

Diese #XSLT-Hasser von #WHATWG & Co. haben vermutlich nie ernsthaft damit gearbeitet. Sollten sich schämen und besser 26 Jahre nach 1.0 aktuelle Standards, also XSLT 3.0 und XPath 3.1, implementieren. 👎

Finding #XSLT 1.0 libraries a security risk when executed in web browsers, a WhatWG dev now pushes an unpopular PR to remove all reference to #XSLT in its #HTML specification, rather than call for updated implementations in the latest XSLT standard. github.com/whatwg/html/pull/11

Here’s hoping that wiser heads and the indie web prevail.

This PR removes all mention of XSLT in the html spec.
Closes #11523

 At least two implementers are interested (and none opposed):

…
…


 Tests are written and can be reviewed and commented upon a...
GitHubRemove mentions of XSLT from the html spec by mfreed7 · Pull Request #11563 · whatwg/htmlBy mfreed7