DO NOT COMPLY.
Uncategorized
13
Posts
1
Posters
2
Views
-
DO NOT COMPLY.
#Google is moving forward with its removal of #XSLT support instead of fixing their library and/or adopting a library that supports a more modern version of the XSLT standard.
The dishonest and incomplete reporting on their developer page omits any explanation on why they have not pursued the corect course of action, and is instead dumping on users and developers the task of compensating for the Chrome team choices:
https://developer.chrome.com/docs/web-platform/deprecating-xslt
DO NOT COMPLY.
-
DO NOT COMPLY.
#Google is moving forward with its removal of #XSLT support instead of fixing their library and/or adopting a library that supports a more modern version of the XSLT standard.
The dishonest and incomplete reporting on their developer page omits any explanation on why they have not pursued the corect course of action, and is instead dumping on users and developers the task of compensating for the Chrome team choices:
https://developer.chrome.com/docs/web-platform/deprecating-xslt
DO NOT COMPLY.
This is a trillion-dollar company abusing their power to control the open web, and one it's catastrophic how even among the purported supporters of an open web there are people stanning for this choice because of their personal dislike of the piece of tech being forcefully obsoleted on false and flimsy premises.
A reminder that I recently wrote up a historical review on Google's efforts in this direction
-
This is a trillion-dollar company abusing their power to control the open web, and one it's catastrophic how even among the purported supporters of an open web there are people stanning for this choice because of their personal dislike of the piece of tech being forcefully obsoleted on false and flimsy premises.
A reminder that I recently wrote up a historical review on Google's efforts in this direction
Do not install the polyfill. Do not change your XML files to load it. Instead, flood their issue tracker with requests to bring back in-browser XSLT support. Report failed support for XSLT as a broken in browsers, because this is not a website issue.
-
undefined Ju shared this topic
-
Do not install the polyfill. Do not change your XML files to load it. Instead, flood their issue tracker with requests to bring back in-browser XSLT support. Report failed support for XSLT as a broken in browsers, because this is not a website issue.
Note that the #Chrome team could trivially ship the polyfill itself and nobody would have even _cared_ about the change in the way #XSLT support was implemented in browser. This would have completely solved the “security” issue due to #Google leeching on a #FLOSS libraries without giving back. The fact that they haven't shows that the security issues in the libraries are just an excuse.
Any comment on this, @drott ?
-
Note that the #Chrome team could trivially ship the polyfill itself and nobody would have even _cared_ about the change in the way #XSLT support was implemented in browser. This would have completely solved the “security” issue due to #Google leeching on a #FLOSS libraries without giving back. The fact that they haven't shows that the security issues in the libraries are just an excuse.
Any comment on this, @drott ?
There's an older parallel here for when #Mozilla helped #Google in their path to kill #RSS (note that this #XSLT is *also* about that) by removing the Live Bookmark feature. At the time, the excuse was that the implementation was incompatible with some important code changes that were happening at the same time, but the fact that support could be trivially brought in via extension showed that the issue there wasn't technical, but a matter of intent.
-
There's an older parallel here for when #Mozilla helped #Google in their path to kill #RSS (note that this #XSLT is *also* about that) by removing the Live Bookmark feature. At the time, the excuse was that the implementation was incompatible with some important code changes that were happening at the same time, but the fact that support could be trivially brought in via extension showed that the issue there wasn't technical, but a matter of intent.
#Chrome's deprecation of #XSLT is just the next step in the decade-long efforts by #Google to kill an open, independent web (reminder that I've collected some of that history here <https://wok.oblomov.eu/tecnologia/google-killing-open-web/>). The #WebKit developers at #Apple or the prone #Mozilla developers agreeing on this choice detracts nothing from the argument.
-
undefined TiTiNoNero :__: shared this topic
-
#Chrome's deprecation of #XSLT is just the next step in the decade-long efforts by #Google to kill an open, independent web (reminder that I've collected some of that history here <https://wok.oblomov.eu/tecnologia/google-killing-open-web/>). The #WebKit developers at #Apple or the prone #Mozilla developers agreeing on this choice detracts nothing from the argument.
#Apple is no better than #Google at stewarding the #openWeb. #Mozilla has abundantly shown in the last years that they are just controlled opposition, and the amount of their allegedly restricted resources they waste on invasive features nobody wants shows that they can't be trusted in any way to defend the users' interest. Currently, their only redeeming quality is that they haven't removed support for uBlock Origin and other #adblockers from their browsers —a meager point.
-
#Apple is no better than #Google at stewarding the #openWeb. #Mozilla has abundantly shown in the last years that they are just controlled opposition, and the amount of their allegedly restricted resources they waste on invasive features nobody wants shows that they can't be trusted in any way to defend the users' interest. Currently, their only redeeming quality is that they haven't removed support for uBlock Origin and other #adblockers from their browsers —a meager point.
I haven't head from any @servo developers about their stance about XML support. I would like to know what they think about it. Currently their engine has no support for XSLT, and I would like to know if they intend to keep it that way, or they plan to introduce support for it.
-
I haven't head from any @servo developers about their stance about XML support. I would like to know what they think about it. Currently their engine has no support for XSLT, and I would like to know if they intend to keep it that way, or they plan to introduce support for it.
I think it's time for another browser war, this time not as corporation vs corporation, but users vs corporate control. Who are our champions? Not @Vivaldi or any other Blink or WebKit browser, for sure, unless they take it upon themselves to fork off the engines to preserve these features. The Firefox forks, perhaps? That landscape is currently a constellation of fragmented projects: is there anything documenting the difference between @palemoon @librewolf or @Waterfox and how many others?
-
I think it's time for another browser war, this time not as corporation vs corporation, but users vs corporate control. Who are our champions? Not @Vivaldi or any other Blink or WebKit browser, for sure, unless they take it upon themselves to fork off the engines to preserve these features. The Firefox forks, perhaps? That landscape is currently a constellation of fragmented projects: is there anything documenting the difference between @palemoon @librewolf or @Waterfox and how many others?
I appreciate that part of the #indieWeb is “running away” from the corporate controlled web in #GeminiSpace, and there are some very interesting idea being developed around there. There's something to be said about not wanting to share your environment with the poison that a large part of the web has become, but at the same time, there's also something to be said about throwing away the baby with the bathwater. The problem with the web isn't technical, it's social. The tech itself is fine.
-
I appreciate that part of the #indieWeb is “running away” from the corporate controlled web in #GeminiSpace, and there are some very interesting idea being developed around there. There's something to be said about not wanting to share your environment with the poison that a large part of the web has become, but at the same time, there's also something to be said about throwing away the baby with the bathwater. The problem with the web isn't technical, it's social. The tech itself is fine.
(I don't dislike gemtext. And I love the idea of a web built on lightweight markup. I would love it if user agents had native support for plain formats like markdown or asciidoc. I even like the #GeminiProtocol. And I see no reason why you shouldn't ship text/gemini over HTTP or HTML over Gemini.)
-
(I don't dislike gemtext. And I love the idea of a web built on lightweight markup. I would love it if user agents had native support for plain formats like markdown or asciidoc. I even like the #GeminiProtocol. And I see no reason why you shouldn't ship text/gemini over HTTP or HTML over Gemini.)
This, by the way, is part of the same rant. There is absolutely nothing preventing, say, #Firefox from adding support for the #GeminiProtocol and for the gemtext format. It would have been a better time investment for their engineers than the time they wasted adding integration with #LLM chatbots that people now have to waste their time disabling (or removing from the code).
-
This, by the way, is part of the same rant. There is absolutely nothing preventing, say, #Firefox from adding support for the #GeminiProtocol and for the gemtext format. It would have been a better time investment for their engineers than the time they wasted adding integration with #LLM chatbots that people now have to waste their time disabling (or removing from the code).
I'm going to have to write up part 2 of my «Google is killing the open web» article, ain't I?
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@ALFA sì stanze adiacenti.
Ma per fortuna devo solo sostituire le magliette a mezza manica con i maglioni.
Il resto è come dite voi: tutto nello stesso armadio.
-
@LaVi e deve essere un guasto bello brutto: ancora non hanno risolto e la linea risulta chiusa
-
Nel 2020, la Francia ha restituito 24 teschi all'Algeria. Da oltre un secolo erano conservati al Musée de l'Homme di Parigi, catalogati, numerati ed esposti.
I resti appartenevano ai combattenti della resistenza algerina uccisi e decapitati durante la colonizzazione francese nel XIX secolo.
Il museo esponeva i resti dei popoli colonizzati come esemplari per studiarli, misurarli e classificarli secondo una gerarchia razziale che giustificava la dominazione.
-
@ju @Uilebheist che io sappia la Gran Bretagna è anche un caso a parte perché la ricchezza privata dei sovrani è significativamente maggiore di quella degli altri sovrani europei, e mi risulta sia molto più ai livelli “influenzare significativamente la politica della nazione in cui sono” degli altri.
-
@francina1909
...e ovviamente gli armadi sono in stanze diverse? 🤔
-
@simonett_a
Buon sabato Simo
@ALFA
-
@ALFA non mi ci entrano tutti nello stesso armadio 😭😭😭
-
@Uilebheist @ju però il potere temporale del papa si esercita su mezzo km quadrato e su meno di un migliaio di persone che hanno solo una cittadinanza temporanea e generalmente possono scegliere quando vogliono¹ di andarsene e non essere più soggetti.
sarà anche potere assoluto, ma è decisamente residuale pure quello
¹ con i limiti del dover cambiare / trovare un altro lavoro, ma hanno comunque un'altra cittadinanza in automatico, non è come dover migrare in un altro stato nel caso standard.
