Sadly there would still be wars, as some see "the other side losing" as a win. Even if both sides are completely destroyed.
deadcade
joined 1 year ago
That was a possibility with this exploit, but realistically that doesn't affect nearly as many people as "All GNU/Linux systems".
"But it looks bad and could be bad for the battery!"
Every other wireless mouse has it in the front, Apple has no valid reason to leave it at the bottom.
Even there, if the stars align (network access, cups being used), you still need to convince the user of the device to switch printer.
As far as I'm aware, the exploit requires someone to try printing using a malicious networked printer. It is a vulnerability, yes, but it affects essentially nobody. Who tries manually printing something on a server exposed to the internet?
Although for local network access, like in a corporation using Linux on desktops, the vulnerability is an actual risk.
If this was the case, the phrashing around the issue would've likely been different. Yet bitwarden remained very vague, and even locked github comments on the issue.
Especially considering that a move like this alienates their core target demographic (people who use FOSS), they would've been much more open and much quicker if it wasn't intentional.
I will personally be switching, likely to KeePassXC.
GrapheneOS developer is very toxic, if you trust him is up to you. I prefer not running his code on my personal devices, especially after him blaming large parts of his community for coordinated harassment. Watch Louis Rossman's video on it.
Although for security-focussed custom roms on the google pixel, like Calyx or Divest, you can re-lock the bootloader, so there's less security risk. A factory reset is required to unlock it again, similar to a factory bootloader lock.
Was yes. They have introduced an "internal sdk" into all their clients with no available source code. That's what everyone's complaining about. They call it a "packaging bug", but in reality Bitwarden clients are just no longer open source.
As in, 0x11 is 17 in decimal.
AI photo, check the coins on the left
VR "works", but as someone who uses it, I can't reccomend it for now.
Compatibility is wildly different between headsets. And no matter which route you take, you will need to tinker and troubleshoot. There is no plug and play solution right now.
If you want to plug in your VR headset, and just play some games, stick to Windows for now. If you're fine tinkering around, there's always SteamVR, but also check out Envision and Monado.
As for desktop games, you can find what works on ProtonDB. Most games work fine, with the exception of games with kernel level anti-cheat.
view more: next ›
Gemini, the protocol is built on never adding new shit, so it's only basic pages