- 71 Posts
- 517 Comments
24·1 day agoI don’t really know how this works, but if they have the cooperation of an OEM they should have the same access to AOSP security updates the OEM has, and access to hardware drivers from a company that’s not trying to thwart them. I can see how this would be preferable to a basically antagonistic relationship with Google, who are making things difficult because they want all Pixel phones to run their stock OS. The thing I wonder is what motivates the OEM to continue a cooperative relationship with Graphene OS.
Yeah, it would be great if they would support a range of devices from whichever OEM this is, at different price points.
1·1 day agoThis was an update to the entertainment system that somehow had the side effect of disabling the power train while driving. You’d think these would be two entirely separate computer systems, but they must be sharing something.
Ha, joke’s on you Microsoft: I don’t have any mates.
20·2 days agoHowever, it is that seemingly arbitrary three-times-a-year limit applied to the People section that is most concerning. Why not four? Why not as many times as a user wants?
Possibly because deleting or recreating the data is resource-intensive on the servers. It might actually be a good sign that Microsoft really removes the data, not just mark it inactive, when you turn the feature off.
2·2 days agoWill they be able to circumvent Google’s restriction?
151·3 days agoI’ve not noticed Cinnamon being any faster than KDE. I’d recommend KDE for someone coming from Windows.
I like OpenSUSE Tumbleweed: everything’s up to date and it’s very stable for a rolling distro. Very occasionally an update is problematic but there are easy rollbacks thanks to btrfs. KDE Plasma is an easy desktop environment for a former Windows user too. One weirdness is you’ll have to get used to using the command line to update native packages and Flatpaks (“sudo zypper dup” and “sudo flatpak update”), because the GUI updater apparently isn’t really intended for the rolling distro.
It’s just about convincing investors that you’re going places. Customers don’t have to want your new features or buy more of your stuff because it has them. Users certainly don’t have to want or use them. Just do buzzword-driven development and keep the investors convinced that you’re the future.
It’s not that they’re especially fragile. It’s really only when you combine them with a sync process. I once had a sync go wrong and it resulted in the contents of a vault being unreadable. Because all you have are a bunch of encrypted files with meaningless names and a flattish structure, which Cryptomator interprets and mounts as a different directory structure, when something goes wrong it’s not easy to know where in the vault files the problem lies. You can’t say “ah, I’m missing the documents folder so I’ll restore that one from backup” like you could with an unencrypted directory. And if you’ve made changes since the last vault backup you can’t just restore the whole vault either. You could mount a backup of the vault, from a time when it was intact, and then copy files across into your live copy, but I feel safer having a copy in another format somewhere else. Not necessary, I guess, but it can make recovery easier.
It depends how the backup is encrypted. Most backup solutions will give you an encryption key, or a password to a key, that you have to keep safely and securely somewhere else. If you have an online password manager or a Keepass database in cloud storage, that would be a reasonable place to keep the key. Or on a USB stick (preferably more than one because they can fail) or a piece of paper which you mustn’t lose.
compressed with AES-256
I guess you mean encrypted.
Cryptomator is good but it’s important also to keep backups of the unencrypted content of the Cryptomator vault that are not encrypted by Cryptomator. (You could encrypt the backups with another system.) Cryptomator vaults are more fragile than the underlying file system, and it’s easier for a glitch in the sync process to corrupt them so they’re unrecoverable. I have lost data due to this in the past. So it’s best to make sure all the contents of your vaults also exist somewhere else, encrypted in another way.
There are plenty of people who are smart with tech and engineering but not very smart with people, society and politics. And these people sometimes develop a tendency to see all society’s messiness and difficulties as engineering problems to be fixed. If you’re looking at it that way, it’s easy to become either a tankie or a fascist, because both offer neat engineering solutions that promise to make life work cleanly.
YouTube’s ‘second chance’ process fits with a broader trend at Google and other major platforms to ease strict content moderation rules imposed in the wake of the pandemic and the 2020 election.
Oh goody, we’re going to get a whole new wave of far-right videos on YouTube.
So much money sunk into AI and they could have just used a hat.
This is why management insists it’s useful. If you’re only aiming to make some plausible-sounding bullshit, it’s the perfect tool. Unfortunately it’s only useful to the people whose jobs are mainly bullshit.
From Discord’s age verification page, under “Privacy and Data Security”:
Q: Is my data stored when I use Face Scan or Scan ID verification?
A: Discord and k-ID do not permanently store personal identity documents or your video selfies. The image of your identity document and the ID face match selfie are deleted directly after your age group is confirmed, and the video selfie used for facial age estimation never leaves your device.
So is that a lie?
I wonder whether there’s some shared development agreement too. Perhaps the OEM stands to gain some software improvements for its own non-Graphene devices, or perhaps Graphene OS will become its mainstream offering. There has to be more to it than picking up the small percentage of customers who shop for privacy.