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.

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.

The linux binary is being used.

Try Proton. Currently, Proton is much more developed than the Linux support for many game engines.

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

On the Steam Deck, while using SteamOS (or other Linux distros), EAC (and a few others like Battleye) run in userspace, not as kernel level.

The intention of Anti-Cheat and DRM is to hide what they’re doing, in an attempt to prevent people from cheating or pirating. Malware often uses similar techniques to hide what it’s doing.

Kernel level Anti-Cheat runs with the highest level of permission on your system, meaning it has access to everything happening on your PC, and all your hardware.

That means kernel level Anti-Cheat can do whatever it wants on your computer, and it’s intentionally hard to figure out what it’s doing. Even though it’s probably not harmful, it shares a lot of similarities with actual malware, and we can’t be fully sure whether it is harmful or not. This is why a lot of people are against kernel level Anti-Cheat.

EAC, afaik, has acted as just an anti cheat, and is therefore likely not harmful to your system. However, like other Anti-Cheats, it is harmful with the standards being set.

That’s, very odd. Just watched the bit about TP2 in the video, and I’m getting nowhere near that on my Steam Deck (non-oled).

Setting everything to low, and FSR performance, it looks awful. There’s very obvious upscaling artifacting, especially during motion. Performance is playable at about 30-40 fps, except in the “starting hub” of the game, where performance can dip to 10fps at times (although no real gameplay occurs there).

With everything being set so low, LODs are clearly visible, even on the small screen. Gaps in signs, thin walls, and stairs are visible from ~5 in game meters away.

On the settings they show in the video, with a fresh save, I get similar numbers in the first couple minutes of the game, but FPS tanks after that. On a save further into the game, I’m getting maybe 20fps (50 when staring at the floor).

The game is still very playable on the lowest settings, and if you’re into puzzle games like The Talos Principle, it’s still a good experience. I’m not normally one to stream my games from my PC, but The Talos Principle 2 is just a better experience with more powerful hardware.

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

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.

What difference does it make updating the screen 75 times per second if you’re only getting 25 different images per second? The OLED screen (iirc) doesn’t visually change during every screen refresh (if the displayed frame is the same). Limiting to 25/50/75hz would have zero visual difference at 25fps, but would draw more power at higher refresh rates.

For 2, Persona 5 Royal (in its opening hours if I’m not mistaken). The only one available on Steam.

Edit: Didn’t realise tactica was already out. I stopped following the releases of the Persona spinoffs literred with Denuvo.

Depends on how it’s implemented. Anyone using a “media proxy” will see their discord bridged media probably fail to load (outside of possible caches) after a day. Anyone who has their bridge configured to reupload discord media to their homeserver should see no change.

This isn’t about “making the game work”, or “adding Linux support”. This is about toggling a checkbox to stop explicitly preventing Linux from working.

The games that already did never faced a massive cheater problem because of it. The games that have stopped development long ago or “don’t care about Linux” (without preventing it with anti cheat) were still made playable by Wine and Proton.

If the developer wants, they can add system info to their ticket system and filter out any Linux tickets. It costs a game developer barely anything to decide to allow Linux users. Linux support costs a lot, but valve, wine, and the community has been putting a lot of effort in so game developers don’t have to change anything about their game.

The times I calculated were indeed going over every possible combination, it would take half as long to crack a password on average. Considering reducing the time to 1/1000000 still leaves you with an incomprehensibly large estimated timespan, dividing that by 2 doesn’t do that much for making it brute-forceable.

I did note it was specifically for 8 emojis, not 8 characters or bytes.

And yes, it’s very impractical and likely to break things. It’s better and much easier to add extra letters, numbers, and symbols to your password rather than using emojis. Using a password manager is even better.

As you stated, a single unicode character would mean your password wouldn’t be included with the potential options in almost all brute forcing tools. Whether you use 8 emojis or 1, your password likely won’t get brute forced.

All of my “emoji password” numbers are if the attacker knows it’s a password containing exactly 8 emojis, and nothing more. Adding a regular symbols+upper+lower+numbers 16 character password would make it even more impossible to brute force.

For somewhat more realistic numbers:

According to minerstat.com, an NVidia RTX 4090 has a hashrate of 118.07MH/s. This is 118.07 Megahashes per second, or 118.070.000 hashes per second. For a password with only 8 lowercase letters (208.827.064.576 combinations), it would take an RTX 4090 approximately 1769 seconds (or ~30 minutes) to go through all possible combinations. For an 8 character upper+lower+numbers password (218340105584896 combinations) it would take 1849243 seconds, or 21.4 days.

For an 8 emoji password (32482071647592311234920185856 combinations), it would take 275.108.593.610.504.896.512 seconds, or 8.723.636.276.335 years.

Lets say a magic prediction algorithm reduces the number of possible combinations in each password to 1 out of every 1 million previously possible combinations. 8 lowercase letters would be cracked instantly, while an 8 emoji password would still take 8.723.636 years.