Pourquoi les chaînes d’info montrent-elles surtout la casse ? Pour Perrine Vasque, c’est un choix éditorial : on envoie des reporters là où "ça va péter", et ce sont eux qu’on prend à l’antenne. Les milliers de manifestants pacifiques passent, eux, sous les radars.
Voir l'émission : https://www.arretsurimages.net/emissions/arret-sur-images/et-si-on-en-finissait-avec-les-pseudos-chaines-dinfo
Well, you know, you can hope that all those companies whose Microsoft-dependent email or office365 or teams mandates have crashed today will have learned a valuable lesson.
But.
They won't. They haven't and they won't.
It was a demonstrably bad decision at the time, and it's an even more demonstrably bad decision now. But you don't get to the big-league c-suite on the strength, accuracy, or correctness of your decision-making.
Holy shit, @molly0xfff and Coffeezilla going after the president's vast and insane web of cryptocorruption.
https://www.youtube.com/watch?v=W4PIkmjwGsQ
Let's, and I cannot stress this enough, go.
La #Caf sabote les mails en texte simple et assume :
« Nous ne pouvons pas vous adresser des mails sous un autre format, il convient donc de modifier vos paramètres si vous souhaitez accéder à nos réponses. »
Connaissez-vous des associations d'utilisateurs dont une des missions est de demander des pratiques numériques décentes ?
Le repouète emmerde les chefaillons qui prennent des décisions « pour le bien de l'utilisateur » au mépris de l'#ergonomie.
Noivember 10
RE: https://newsie.social/@ProPublica/117592622978754900
Bill Gates is a monster.
it’s about fucking time a lot of y’all in #tech say it loudly and with the chest. he has proven right those of us who’ve been saying it since the 1990s.
all that bullshit about vaccines? he uses his foundation to push the stock up of his pharma companies. one of the points of the program was so he could develop a new generation of wage slaves; to work as curators of the vile & violent content techbros use for their aislop grift.
Bill Gates is a monster.
RE: https://mamot.fr/@benzogaga33/117591638457068192
Cory Doctorow a raison : l'IA, c'est l'amiante qu'on est en train de fourrer à plein régime dans nos systèmes informatique. Le nettoyage va être absolument dégueulasse.
Pour le retrait de tout compte de structure publique ou parapublique sur X (ex-Twitter)
Plateforme des pétitions de l’Assemblée nationale
My school's community is looking for a humane, ideally open-source, tool for organising things like parents pitching in, school events, etc. Like a **very normal-person-friendly** message board.
Any suggestions? Something at least as easy to use as Facebook Groups. I'm able to host services on a VPS.
#mastodaoine #foss #community #meitheal
You'll have to endure another shameless job offer from my workplace, but it's a really cool job, so I thought I'd share this:
https://hetzner-cloud.de/jobs/2800749
We're looking for a (Senior) Embedded FPGA Developer (m/w/d).
We're looking for folks with deep knowledge about (Xilinx) FPGAs, PC hardware, Linux. Networking would be a bonus point.
It's a new codebase and I promise it's interesting 😎
Fully remote (in Germany).
La droite, toujours prête à faire la courte échelle à l'extrême droite.
Le Portier là, il pourrait dire qu'ils vont examiner la pétition mais que l'AN n'a pas le pouvoir de fermer une chaîne, et hop on enterre une fois de plus une pétition massive sous un prétexte quelconque tout en se gardant bien de traiter le problème de fond.
Mais même pas, les mecs il faut qu'ils en rajoutent et qu'ils tripotent le totem de la liberté d'expression avec leurs petits doigts dégoûtants.
Des mecs qui voulaient dissoudre LFI la semaine dernière ...
Et qu'on foute la paix à Voltaire.
Voltairien de mes fesses oui
Bon ben c’est fait… L’Europe éradique le RGPD au motif que l’IA
https://noyb.eu/en/ai-eu-member-states-approve-digital-expropriation-europeans-ai-companies
MatrixRTC has landed! 📞
The world’s first decentralised, end-to-end encrypted, multiparty VoIP protocol is now part of Matrix.
Every server can run its own conferencing server, calls are E2EE by default, and it’s an open standard. @connect2x has built its own implementation in Tammy, and Element Call and Tammy are calling each other live at #MatrixConf
How it works: https://element.io/blog/operator-i-need-an-exit-from-big-tech-calls/
I have had a lot of discussions over the last decade on correct handling for out-of-memory conditions. There are two very distinct philosophical camps.
The Windows kernel has a policy of 'don't make promises you can't keep'. This means that a call to malloc will either return memory that is already available or the result of a new call to VirtualAlloc2, with committed memory. When the NT kernel says it has 'committed' memory, it means it promises that memory will be available when you try to access it. There is space reserved either in RAM or in swap to permit something else to be moved from RAM to make space for the thing that you need.
The other extreme says that you should assume that sometimes components fail. Erlang embodies this as the 'let it crash' philosophy. Google discovered fairly early on that, when you're looking at jobs distributed across large fleets of machines, a single node experiencing hardware failure is basically unavoidable. Mainframes deal with this by duplicating all of the hardware (often multiple times) so a hardware failure can be transparently worked around. But clouds built from consumer hardware don't do that: sometimes VMs die and you deal with it.
In the 'let it crash' model, you already need to build resilience at a higher level. Your individual jobs may fail because the hardware that runs on them fails. You need to be able to roll back any partially committed transactions that they started and restart them from the beginning. For things like web servers, that's usually easy: This HTTP request failed? The client can retry.
Once you have that mechanism, you rapidly realise that you can use it for other infrequent operations. Memory allocation almost never fails. If it does, let the program crash. Systems like iOS and macOS encourage programs to persist any user-visible state frequently, so a program crashing is fine - you may lose a couple of seconds work. In exchange for this, you get much simpler code. Rather than every allocation having to come with error handling (and there are tens of thousands of individual allocation points in a typical non-trivial program), you just assume it works and crash if it failed.
Some kernels, such as Linux and FreeBSD, lean into this even further. If the kernel claims it's given you memory, that isn't a promise, it's a best-effort guarantee. When you actually use it, they'll either ensure it's there or deliver a signal. It turns out most programs ask for memory that they'll need in their worst case, but this mechanism gives them the memory that they actually need. And this means that fewer allocations fail. You can't easily handle the allocation failure locally, but you're now less likely to hit allocation failure.
And this is a big win for overall reliability and performance. Because it turns out that gracefully handling out-of-memory conditions is really hard. Often, good error recovery requires allocating memory, but you can't do that if you've hit an out-of-memory condition. And these errors propagate outwards. Every function that allocates memory not may fail due to memory exhaustion. So it's not just routines that allocate memory that need to handle out-of-memory errors, it's everything that calls them. And you have to get it right at every place that needs to do any kind of cleanup if memory is exhausted.
This is one of the biggest reasons that embedded development is harder than application development: you can't assume memory exhaustion is rare and you don't always have an outer layer that can handle component-level failures. But in every other situation, the correct approach is to assume that memory is infinite and allocations never fail, and to assume that the component making that assumption will crash periodically.
This is a post about PHP.
How do you like "Cybersecurity Awareness month" so far?
La souveraineté numérique européenne coûterait trop cher, selon une étude financée par la CCIA.
Entre 36 et 233 Mrds d'€ selon les scénarios, loin de l'estimation de 18 Mrds d'€ de la CE.
Voici la liste des contributeurs de la CCIA, à toutes fins utiles...
J'ai vu des gens qui ont essayé pendant mes études, de me convaince que « l'informatique professionnelle c'est microsoft, tu pourra jamais travailler dans l’informatique si tu refuse les produits microsoft » soudainement découvrir des cartes ARM sous Linux années après en mode « c'est intéressant à bidouiller/pour apprends » (LOL)… Des gens qui n'ont jamais travaillé dans l’informatique soit dit en passant
6/n
Pour rappel, X c’est ça ⬇️