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.

They tried that, it’s called UWP. A lot of programs don’t want to be distributed through the microsoft store though, forcing them to use “old” .exe’s

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.

The bootloader of your phone (if locked) is one of the most secure parts. It’s very hard to get into a modern phones bootloader. In contrast, finding an exploit in a running phone is a lot more feasible.

If a vulnerability was abused to get into your running phone, it will persist until the phone reboots, and the bootloader verifies the core parts of the operating system at startup. In order to persist past a reboot, malware like that would need a vulnerability in the bootloader, or a bypass for its integrity checks.

Alongside that, any background services (“daemons”) that got stuck or became slow over time are forced to restart. Operating system updates can be applied, and working memory is cleared.

In general, it’s just good advice to just reboot your phone once in a while. There’s no harm in doing so.

Do NOT click the link. Instead, go to google.com yourself, go to your account settings, and “check activity”. If there’s anything suspicious (like an attempted login from another country), reset password and ensure 2FA is enabled. Otherwise, you can safely ignore/delete the email. (But still enable 2FA for better protection)

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.

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.

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.

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.

NordPass is completely incorrect on the "it makes a password easier to “crack” thing.

I absolutely don’t recommend using emojis in your password, as it is far too easy to get locked out. However, a password containing an emoji is significantly harder to crack.

Hashing is a process used to calculate a large number based on some input data. If the input is the same, the output is the same. If the input differs just slightly, the output is completely different. This process is mathematically irreversible. Since this (and other techniques) is often used for passwords, to “crack”/bruteforce a password, the attacker has to go through every possible combination of input data, calculate the hash, and check if the hash is the same as the password hash.

To make the process of bruteforcing a hash quicker, an attacker often makes assumptions about the input data. If they know a password contains 8 characters, and only lowercase letters, this massively narrows down the amount of passwords that need to be hashed and checked. If they know the password contains someones birth year, that too reduces the time to bruteforce a password.

The more possible characters you have per position in your password, the longer it will take to bruteforce. An 8 character password with just lowercase letters has 208.827.064.576 possible combinations. This sounds like a lot, but it’s often bruteforced rather quickly. Adding uppercase letters and numbers to that, we’re already at 218.340.105.584.896 possible combinations. That’s ~1000x more combinations, and that’s for 8 characters. It’s the difference between bruteforcing taking a day, and taking 1000 days. (Do note an 8 characters lowercase password probably only takes like a few seconds to minutes, not a full day.)

According to https://emojipedia.org/stats there are 3664 different emojis. Lets say we create an 8 emoji password. (some emojis aren’t one character internally, the same principle still applies.) Just 8 completely randomly chosen emojis. That password would have 32.482.071.647.592.311.234.920.185.856 different possible combinations. That is about 148.768.232.755.857 times more combinations than an 8 character uppercase+lowercase+numbers password. That is the difference between bruteforcing taking a day or taking 407584199331 years.

The same things as non-emoji passwords still apply, you can make assumptions about which emojis are used. People aren’t entirely random, so chances are higher they used some of the more common emojis. However, that is similar to prioritizing the letter “e” because it is more common. Yes, it’ll probably reduce the time taken to bruteforce a bunch of passwords, but it’s not set in stone that every password will even contain the letter “e”.

Again, due to the potential of breaking things, locking yourself out, etc. I DO NOT recommend using emojis. Use a password manager with longer passwords.

However, including an emoji in your password makes it significantly more difficult to bruteforce. As the assumption that the characters in your password are letters, numbers, and symbols no longer holds, which drastically increases the possible number of combinations.

You want a magic Discord speedboost? It’s called OpenAsar. Mitigates telemetry, and speeds the client up to usable levels, especially on lower end hardware.

Although with most games, the accessibility options need to be there (even when they sometimes aren’t), some games incorporate their movement mechanics into gameplay heavily. Take BONELAB for example. Great game, but simply impossible to play for some people due to the movement. Adding teleporting (or really any accessibility movement option) would simply ruin it though, as the entire game is based around physics based interactions, walking, running, jumping, climbing, etc.