One thing that Steam/Valve has done with the Steam Deck is lock down the ISO by default, and provide no tools to modify your image persistently. That is of course on purpose, because that works for 99% of users, but the 1% of users may wanna use something where they can, for instance, overlay packages and keep them with updates, or apply extra gaming-focused tweaks that may be more of a hassle to maintain on SteamOS.
For instance, I use Fedora Silverblue daily on my Desktop, and even though it is immutable just like the Deck, it offers me tools to modify my image as I see fit and have the same modifications be applied to future updates too.
They should be, the Steam Deck updates system components separately through steam.
As a diagnostic step, you might wanna run flatpak update in a new Konsole window to see if there are any errors that Discover might not be telling you about.
Not because it inherently makes you less private, but because having bad security makes it hard to be private, and opening up a way in android to allow apps to do what they want (selective root access) usually requires punching a lot of holes.
Even with AVBRoot, which allows you to setup Magisk or KernelSU with full Verified Boot support, you're still leaving open the possibility that something abuses the fact you're rooted against you.
But just so you know, if you insist, you can skip the step of locking your pixel's bootloader and install Magisk, but do not expect any support from that point onwards.
Proton and Wire didn't share any decrypted ciphertexts, Wire shared a ProtonMail address and Proton an iCloud Address that they had set as a recovery method.
Personal info like where they live came from Apple.
there are additional cookies with duration as high as 1825 days, not 180... So which is it?
Whatever the browser reports is what they are actually doing.
In Firefox, enter the developer tools, navigate to the "Storage" tab and open the "Cookies" dropdown.
For any given domain you can now look at the "Max Age" or Expiry date.
I think what you're experiencing online is a mix of loud minorities1 and online disinhibition2, not an accurate representation of vegans.
1: When there exists a minority in XYZ Group that is "louder" than the majority, causing people to associate XYZ group with the minority.
2: The phenomena of people acting out more violently, frequently, or pushy online when compared to being in-person, primarily due to anonymity
Specifically the annoyingly loud, self-righteous, insists-everyone-must-join-them vegans.
Unfortunately, most people only really see this sort of vegan
On this note, I'd like to point to the Loud Minority problem; You have XYZ group, and within XYZ group there exists a minority that comes across as very "loud". You can barely miss them, and because they state they're a part of XYZ group, you start associating that group with the loud minority.
Happens with Vegans a lot, and usually people which have already associated a group with a minority within said group which annoys them do not want to learn that they are wrong, or will just refuse to accept they are wrong.
The only data that they have, based on transparency reports and dissections of their source code, is the time you created your account and last connected to the servers.
Messages themselves are essentially only relayed, with sealed sender, and anything that would be actually useful to identify who was at a protest and who wasn't encrypted.
Things like, e.g when messages arrive at the server would have to be monitored live on compromised servers, which reasonably unless you assume* it is wiretapped already prior to a protest, isn't realistic.
*: of course, I am saying this because making an assumption and portraying it as truth (e.g assuming something is already wiretapped based on no evidence at all) is not the smartest of moves when it comes to threat modeling...especially if you wanna stay sane whilst having a threat model
have they paid 2.4 million? Last time someone with supposedly that much funding got fucked over by Nintendo they have been sent to jail, and once they came out had to basically pay rent to nintendo for the rest of time.
The reason we didn't hear anything of that, if I had to guess, is probably an NDA.
Simon Müller @ cyrus @sopuli.xyz Posts 3Comments 130Joined 1 yr. ago
One thing that Steam/Valve has done with the Steam Deck is lock down the ISO by default, and provide no tools to modify your image persistently. That is of course on purpose, because that works for 99% of users, but the 1% of users may wanna use something where they can, for instance, overlay packages and keep them with updates, or apply extra gaming-focused tweaks that may be more of a hassle to maintain on SteamOS.
For instance, I use Fedora Silverblue daily on my Desktop, and even though it is immutable just like the Deck, it offers me tools to modify my image as I see fit and have the same modifications be applied to future updates too.