This doesn’t affect valve at all though. It’s borrowing their tech that they’ve made open source, and figuring out how to use it elsewhere outside of steam.
Actually, it’ll benefit them. More eyes are on proton and any fix will benefit everyone, including games played via steam.
Supposedly so long as it’s the Epic Online (EOL) version of EAC, then it’s about as easy as checking a tick box in the settings.
Any developer who cares enough to enable it would most likely test that it works as expected and make a couple of tweaks before announcing the support. It’s usually not a good idea to take a vendor by their word that it “just works”.
What happened afterwards? Did you go off on a self searching quest and come to learn the real you?
Thanks,
So they haven’t made an announcement about retiring the proton bridge app yet.
I think I’ll wait until I see them actually remove it before I believe they’re locking us in.
I’ve just skimmed through the proton blog briefly and I couldn’t see anything referencing this. Do you have a link by chance?
That’s a bold claim. Got a source for this move?
I’ll trust what the cyber security and privacy experts say.
Facebook might know who you’re messaging but that’s also true for Signal.
Signal’s sealed sender does a good job at knowing you’re sending a message, but not who to. All it’ll know on the receiving end is that a message was sent to it.
Of course people have found other methods of identifying this but sealed sender does cover most of the low hanging fruit.
Signal does also purposefully attempt to find ways to not collect any metadata, whilst also making it more difficult for anyone attacking to the servers to find anything. (e.g. ORAM for Secure Enclave operations)
My understanding is that meta used E2EE on your messages themselves, but everything else is up for grabs.
As others have mentioned, the main caveat here is that anti cheat games can work if the developers enable the support.
I’ve been playing dead by daylight very happily for a good few months now on Linux. Apex legends has also got official support for Linux as well.
Pulseaudio has been replaced by PipeWire for quite some time in fedora. Since Fedora 34, released in April 2021, apparently.
According to the wiki page, PipeWire originally came about trying to improve video handling on Linux, the same way that pulseaudio improved audio handling.
They then wanted to try and handle audio streams, with the idea of converging use cases for both consumer and professional audio users. Namely, they wanted a single audio system that supported both pulseaudio and JACK, whilst remaining as low latency as possible.
On top of this, because it was a modern reimplementation of audio and video handling in Linux, they designed it to work with Flatpak, and to provide secure methods for screenshotting and screencasting in wayland via the compositors.
(All my info here I just took from the wiki)
It’ll be used by a lot of Linux distributions.
It’s a drop-in replacement to the Pulseaudio and JACK audio systems, with the hopes of making audio handling decent within Linux with as low latency as they can.
Eh, WSL is still enough like Linux that it could be the best option for a lot of people. No risk to the computer being unable to boot whilst still giving you the ability to play with Linux tooling.
And credit where credit’s due: Microsoft details how to do a bare metal install, which is the most likely option to wipe Windows from your machine in the first place.
You’ll want to look into the *arr apps.
Specifically… sonarr, radarr and prowlarr.
Wiki is: https://wiki.servarr.com/
Also, jellyseerr looks like a nice requesting front end https://github.com/Fallenbagel/jellyseerr
I haven’t used jellyseerr as I use a VPS that only offers Ombi, but that’s pretty good too.
It’s most likely easiest to use docker to spin everything up.
GB is metric and it’s easy for us to remember. E.g. 1000 bytes = 1 Kilobyte, 1000 kilobytes = megabyte and so on.
GiB is the binary value. In binary, you have to work in powers of 2. That is… the values double every time (2, 4, 8, 16, 32, 64 and so on…). 1024 bytes = 1 KiB, 1024 KiB = 1 MiB
Since computers work in binary, and 1000 isn’t a number that’s easy to deal with in binary, we use the closest value available to us, 1024. In fact, back in the days when people were only concerned about KBs, they would say that 1000 KB = 1024 KiB.
Of course, we’re now working with TBs rather than KBs. Everything ramps up including the amount of “missing” space an OS reports on a hard drive.
I know windows tries to be helpful and shows you the value of a drive in GB, rather than its GiB value. Ever wonder why a 1TB hard drive appears as ~931GBs? This is why. Other OSes tend to show you the GiB value since that’s generally a lot more accurate.
They haven’t dropped the requirement, but you have to manually go in and disable that check yourself on the windows 11 installer if you want to install it on a non-tpm 2.0 machine
Basically, it’s a faff that only the techie people will realistically do. Everyone else will just go out and buy new hardware.