Node.js devs, so picture this: you run npm install and you get a bunch of packages with audit errors.
The one thing I want to know at that point: what’s the root package that these dependencies belong to. (Running npm audit fix is a last resort as I don’t like it fiddling around with the dependencies of nested packages.)
It’s also not a straightforward thing to do, but it’s nothing jq and a bit of piping can’t fix:
"From the very beginning, Ukraine's desire was to join NATO, these are real security guarantees. Some partners from the US & Europe did not support this direction," he said in answer to questions from reporters in a WhatsApp chat.
"Thus, today, bilateral #security guarantees between #Ukraine & the #US, Article 5-like guarantees for us from the US, & security guarantees from European colleagues, as well as other countries — #Canada, #Japan — are an opportunity to prevent another Russian invasion," #Zelensky said.
"And it is already a compromise from our part," he said, adding that the security guarantees should be legally binding.
Two questions are particularly interesting: can the vendor access passwords (5/10 no) and is the entire storage encrypted (3/10 yes). Which leaves 1Password, Keepass2 Android and KeePassXC usable without reservations, while Avira Password Manager and Firefox Password Manager are usable with some concerns (the former uses crypto that cannot be verified, the latter requires a main password to be set explicitly). The other five tested products (Chrome Password Manager, mSecure, PassSecurium, SecureSafe, S-Trust) should not be used.
Not exactly news to me but good to see this confirmed – and good to see a proper analysis rather than grabbing low-hanging fruit for some bullshit statements.
Avevamo ragione, come sempre, nel comunicare che fino ad Aprile 2026 il chat control sarebbe tornato a massacrarci l'esistenza! A molti di voi potrebbe non interessare ma consegnare i nostri dati a Big Tech, far indebolire la cifratura dei certificati ssl e stravolgere le regole per un controllo di massa anche no! Agite al link sottostante:
@mathewi 4/ I’m going to delay elaborating my other concerns about the maturity of #SelfDriving#autonomous vehicles. For now, please consider the following:
1. #AI in general, self-driving cars in particular, are not people. These technology systems do not have our human-lived experiences, they do not think like us, even if you believe that thinking is computational. With a few exceptions, such systems have no common sense ability to reason about the world. They don’t understand human behavior the way we do.
2. They will not make the same mistakes that humans make while driving. That is not only a requirement, it follows from 1. Instead, they will make their own mistakes. We are already seeing plenty of these. Sure, engineers will grind out most of these, but not all.
3. The first two points mean that the behavior of self-driving cars will be difficult to predict in all but the most common vanilla driving situations. People complain about how rigid the current vehicles are at following the law. What? Now you want them to break the law when it is expedient?
4. There are a near infinite number of “edge cases” and those are when safe driving is the most difficult — exactly when we want self-driving vehicles to excel. There are too many to test. The complexity of the real-world, specifically edge cases, cannot be simulated in a laboratory. A decade or more experience on the road is required.
5. Cars are increasingly connected and computerized, and that makes them a new #security threat. Any modern car today can be hacked and remotely controlled. AI systems add multiple new attack vectors. Yes, companies are working on security, but so are the bad guys. #Infosec people will tell you their world is hand-to-hand combat. The more such cars are on the road, the greater the opportunity and attraction for mischief (or worse).
The big question is when will we, as a society, feel safe and convinced by the benefits of self-driving cars? That question is a trap, because most people don’t know the details. It is already happening.
Speaking as an expert and a grandfather, I will not be putting my grandchildren in the back seat of a self-driving car any time soon.
Users cannot be deleted This is simply not an option in the API. Server admin can perform a "deactivate" (disable login) and "erase" (remove related data, which claims to be GDPR-compliant) on user accounts, but the accounts themselves stay on the server forever.
LOL.
Here is my take on why you should trash Matrix and use XMPP, or ta least Signal instead: