That was a possibility with this exploit, but realistically that doesn’t affect nearly as many people as “All GNU/Linux systems”.

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.

According to Jim Starkey, the person who coined the term, “Blob don’t stand for nothin’.” However, it is often referred to as a “Binary Large OBject”, meaning a large file with content not easily readable by people.

With an open source project, you have source code which is turned into executables/“blobs” by the compiler. As long as you trust the compiler, you can (functionally) know the content of the blobs by looking at the source code they were made from.

In the case of Ventoy, several “blobs” are included from an unknown or vague origin. This is a great way to bundle malware, as seen with the XZ backdoor from earlier this year. As such, the original creator of the linked issue is requesting they are built/obtained at compile time, so either the content or origin of these files can easily be found.

https://github.com/neonwatty/meme_search

Linux, it fits my needs better on desktop, and is much less painful to troubleshoot than Windows, with more freedom and control than macOS.

Correct, Vector does not receive this information unless you willingly share it with them.

Element is able to use features called “Integration Manager” and “Identity Server”. When using an Identity Server, you can choose to link name, email, and phone number to your Matrix account. When using an Integration Manager, there’s a feature to share your location with others in chat.

As such, Vector discloses that they “collect this information”, although (except some diagnostics), this is completely optional.

(I am not associated with Vector, just interested in Matrix)

“clean driver install”, which heavily suggests you installed nvidia drivers, probably from the website. That issue is entirely on you.

Although “custom Windows ISOs” are a big security risk, AtlasOS isn’t a “custom ISO” and running a random binary off some guy on YouTube is arguably just as bad. He has next to no knowledge of Linux, neither do any other “Linux YouTubers”. Trusting someone like that with your Linux machine is risky at best.

Lets go through the summary and see if anything is wrong or misleading:

Linutil is a distro-agnostic toolbox designed to simplify everyday Linux tasks. It helps you set up applications and optimize your system for specific use cases. The utility is actively developed in Rust 🦀, providing performance and reliability.

• It is not distro agnostic. There is Arch and Fedora specific code, which are not separated into modules, but part of other scripts. Outside of the package manager, it also relies heavily on systemd.
• Installing “Diablo II Resurrected loot filters” is not an “everyday task”. A lot of other scripts are similar, very specific, “one time use” things, not “everyday tasks”.
• helps you set up applications, maybe, but only if you count running sudo pacman -S networkmanager as “helping”, even when it ignores existing network configuration.
• “optimize your system for specific use cases”, it does nothing of the sort. There’s no kernel parameter tweaking, no other cpu scheduler, no IO options being changed, or anything remotely similar.
• “The utility is actively developed in Rust” except for the ~70% that is shell scripts. (according to GitHub)
• “Providing performance and reliability”, which is not something that’s determined by the programming language.

So lets revise the short description, to exclude any incorrect/misleading statements:

Linutil is a toolbox. The utility is actively developed.

Alongside all that, the “installation instructions” include the biggest sin of all:

curl -fsSL https://christitus.com/linux | sh

TL;DR Never trust Chris Titus, or any “Linux YouTuber”, with your Linux machine. They do not know what the hell they’re doing.

mount -o remount,ro /

I think the last thing you’d have to worrh about is your job when nearly all infrastructure collapses.

Despite the downsides of F-Droid, there’s one thing they provide that other stores like Accrescent simply can’t. F-Droid provides APK builds with the exact source used for the build available. There’s a lot of trust involved, but this trust is in a single entity, rather than random developers. F-Droid has existed for a long time without adding malicious code to builds, so when they say “this source code produces this APK”, they have years of history doing exactly that to back their claim.

A random app developer has no such trust built up. Stores like Accrescent, even if you download only FOSS apps, trust the app developer with building apps. It’s less prone to one massive takeover, but APKs built by random devs are much harder to verify and check for malicious code than the source code. If F-Droid is taken over, it should be noticed relatively quickly, but affects everyone using F-Droid. If an app on Accrescent bundles malware, only users of that app are affected, but it may go unnoticed for a much longer time.

This person uses an 8GB mac, and tried to defend Apple in the debate, going as far as to say that Apple hardware is “not that expensive”, and within 2 months regrets buying the 8gb mac.

They think Open Source is “overrated”, insecure, and not important. They think Linux users are “normies” and fakers, Linux is not a desktop OS, and have explicitly stated “F*** LINUX”.

That’s a lot of terrible opinions in just 4 months, especially for someone who calls the internet “stupid”, and supposedly doesn’t have any education.

This is either a troll account, or someone with less than zero credibility considering their opinions and statements.

Android is a dead end for FOSS in the future, but moving from one corporate owned semi-proprietary OS to another doesn’t solve anything.

Afaik the bug was never present in a release. The developer who quit had to jump through a bunch of hoops, and treat it as a security issue, when it only affected people running the latest git commit.

KDE Connect, and if needed, ntfy.sh.