357 private links
Un site dédié: chiffrer à la place de crypter.
L'extension signale les sites générés par IA, ainsi que les "noms de domaine proche visuellement (la proximité visuelle est obtenue par le fait que de nombreux systèmes d'écriture utilisent des caractères se ressemblant) d'un autre nom de domaine connu ».
Signaler tout courriel indésirable reçue.
Inscrire son téléphone afin de bloquer les appels publicitaires (selon la loi).
Après 30 jours, il est aussi possible de signaler les numéros téléphoniques.
The beautiful thing about software is that the size and complexity of "intellectually manageable programs" can change over time as we develop better technologies.
It is really pushed by Rust enthusiasts or community using Rust, so I can see the lobbying here.
It is still true and right though.
The PDF https://trifectatech.org/docs/improving-europes-cybersecurity-posture-through-memory-safety.pdf
A great explanation of how servo came to be and how is it developed now.
It highlights Rust advantages over C++ (massive parallelism, ...) and its independance. Servo is hosted under the Linux Foundation and managed openly by the Technical Steering Committee.
A webview (for android and apps) is currently built!
Recent developments: Incremental layout (computation optimisation), WebDriver support to automate the browser (and testing), SVG support and DevTools from Firefox
Plans: editability and interactivity enhancements, CSS Grid Layout support, Embedding API, initial accessibility support and performance improvements.
Long-term: leading embeddable web rendering engine ecosystem, powering innovative applications and framework, offering unparalleled performance, stability and modern web standards compliance.
All infos can be found on https://github.com/servo or https://servo.org/
An example of semantic class names and a teaser on server of Kelp to have dynamic HTML through WebComponents.
Google uses AI to report security vulnerability.
They order a fix and they plan to release the vulnerability after 90 days.
FFmpeg is an open source project though. The project owes nothing to Google, and Google has no right to impose anything on the project. The company can largely finance or submit fixes.
Tcherneva concludes by pointing out that, as with tech enshittification, labor enshittification "is a political choice, not an economic inevitability." Labor enshittification is the foreseeable outcome of specific policies undertaken in living memory by named individuals. As with tech enshittification, we are under no obligation to preserve those enshittificatory policies. We can replace them with better ones.
A job guarantee restores interoperability, worker power, job safety as the private empyer will have to beat the job guarantee's wages and benefits.
Tcherneva concludes by pointing out that, as with tech enshittification, labor enshittification "is a political choice, not an economic inevitability." Labor enshittification is the foreseeable outcome of specific policies undertaken in living memory by named individuals. As with tech enshittification, we are under no obligation to preserve those enshittificatory policies. We can replace them with better ones.
Geburt des ersten Kindes: -1.6 auf einer Skala von 0 (unglücklich) bis 10 (glücklich(.
Zum Vergleich:
- Tod des Partners: −1
- Arbeitslosigkeit: −1
- Scheidung: −0,6
Studie im 2015 veröffentlicht.
So RSS won't be supported anymore and other formats too.
Only the web HTML + CSS + JS will remain and Chrome is pushing implementations at a faster pace that the other browsers can not . There is effectively an attempt to capture the web by Google.
I remember the library for XLST used in browsers is not maintained by the big corporations. Ah it's LibXML.
The depreciation notice: https://groups.google.com/a/chromium.org/g/blink-dev/c/CxL4gYZeSJA/m/yNs4EsD5AQAJ
Ah yes, a maintainability thing "Chromium uses the libxslt library to process these transformations, and libxslt was unmaintained for ~6 months of 2025".
Usage of the JS XSLTProcessor API is fairly volatile, registering somewhere between 0.01% and 0.1% of page loads, averaging around 0.05% over time. These numbers are above the typical 0.001% deprecation threshold. Again, we feel that the increased potential for breakage is balanced by the reduced security risk to 100% of Chromium users.
It's for security reason? XSLT users hacked are 0. Where are the security vulnerability?
Pas lu, mais ce sera utile pour plus tard.