Steam Link doesn’t work on Linux. SteamVR, ALVR, WiVRN, and Monado work under Linux.There’s more headsets than the Quest.

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.

Nvidia does not make x86 SoCs. Even if Valve goes with a separate Nvidia dGPU like in laptops, they would have to abandon their last 10+ years of Linux work, and goals of having a platform which isn’t controlled by Microsoft.

Switch uses the Nvidia Tegra X1

KDE Connect, and if needed, ntfy.sh.

I don’t have a direct source other than the source code of the software they use: https://github.com/mautrix/signal

When using one of their “cloud hosted” bridges, the bridge software (that connects between Matrix/Beeper and other protocols) has to read all message content. Otherwise, it’s impossible to bridge to another protocol. E2EE becomes end (other users) to bridge (beeper) encryption.

With “local hosted” bridges, E2EE stays intact, but messages can’t be sent/received if the device hosting the bridge is unavailable.

In the future, with MLS (a different E2EE protocol), it could be possible to keep E2EE even when bridging to Matrix on cloud hosted bridges.

I thought you were referring to Lemmy as a whole. I haven’t visited the linked site, but judging by the post it’s probably AI.

Not the entire site, but definitely some accounts and communities.

iirc NPxSP was getting messy internally, the author went and rewrote a lot of things

per-site process isolation, as mentioned here: https://divestos.org/pages/browsers#processIsolation

My experience with several firefox-based browsers on Android was not usable, with constant freezes, crashes, and performance issues.

There are some security considerations to using a Firefox-based browser on Android. In my experience, performance and stability has not been as good on Firefox Android as Chromium Android.

https://divestos.org/pages/browsers

You’ve read your last complimentary article this month.

I haven’t even read a wire article this year.

Saved 83%

And 100% of the quality/context.

Please, don’t recommend Ubuntu. It actively gets in your way, even as a new user. Something like https://distrochooser.de/ could help OP figure out what distro works best for them.

Unless a proper secure boot + FDE setup is in place.

Since the EFI partition is unencrypted, physical access would do the trick here too, even with every firmware/software security measure.

Most “standard” messaging apps (that includes signal, telegram) use the “OS provided” push service. On Android, they use firebase cloud messaging, a component of google play services.

Degoogled Android means not having any notifications, unless the app supports UnifiedPush, runs in the background 24/7 (which drains battery), or runs in the background occasionally (which delays notifications).

If the app runs in the background occasionaly, you can “burden” the people on the other side by being slow to respond.

It’s used often by novices, because outdated articles keep telling them it’s “the best Linux distro”. Canonical has gotten very corporate over the last several years, forcing things like snap onto users. Ubuntu used to be the number one user friendly distro, now they shove ads in the terminal. It’s not getting hate for being easy to use, it’s getting hate for marketing itself as such, then forcing corporate bs on the user (who are often new to Linux). Many other user-friendly distros have not seen the same amount of hate, because they aren’t objectively bad.

I recommend against using Manjaro, it is poorly maintained and has many downsides compared to something like EndeavourOS (which has a similar goal to manjaro with less downsides).

If you’re comfortable using a specific package manager, go with a distro that uses that package manager. If you’re already familiar with Mint, something else Debian based might suit your needs.

If you’re still looking for the distro that’s right for you, make sure to separate your / and /home into different partitions during your next installation. This allows you to switch distros while keeping all your documents and personal files.

If you’re unsure which distro to try next, https://distrochooser.de/ gives you a set of questions and ranks distros on what would fit best to your needs.

Most malware is written for Windows, especially when it’s distributed as a Windows executable. (Almost) no Windows malware targets Wine specifically. However, Wine on its own is not a sandboxing tool, and Windows ransomware will ruin your day.

Bottles does two things for security:

1. Separate wineprefixes
2. Being a flatpak

By separating wineprefixes, as long as the host filesystem is not directly exposed (which iirc is default for bottles), any malware not written with Wine in mind will only affect its own “bottle”.

By being a flatpak, even if some Windows malware specifically targets Wine, it would still have to escape the flatpak sandbox for elevated permissions. If the bottles flatpak has no access to personal files, “Wine-aware” malware won’t either.

Although malware can still do damage, even in its own sandbox. For example, botnet type malware would still function. The host system is “safe”, but the damage can still be done externally. Usually application-defined “autostarting” of applications is broken under Wine (iirc), which means all non “Wine-aware” malware will only start when an infected windows application is started in bottles.

Any sandbox will eventually be escaped, and malware sophisticated enough will be able to get access to everything on the host system. The chances of running into malware like this in the wild are extremely small.

• Is it fully secure? No.
• Is your virtual Windows environment safe? No.
• Are other “bottles” safe? Likely, as long as the malware isn’t aware of Wine.
• Is your Linux host safe? Most likely, depending on your flatpak settings. (and the malware has to specifically target Wine under Flatpak).