• 0 Posts
  • 4 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle

  • I don’t think you’ve used anything but a Boox in a long time, and have forgotten what the standard is. Boox has 1/10 the battery life, takes forever to wake up, and doesn’t support deep sleep properly (so it either drains battery when sitting idle, or shuts off entirely taking 5+ minutes to power back on). It’s decent hardware with very badly designed software. Neither Kobo or Kindle devices have these problems, they have battery that actually lasts, deep sleep when idle for any length of time, and power back up, even from deep sleep in 10 seconds or less.


  • Except so far the only time they’ve actually gotten any fines paid by anyone significant, the initial multi-billion euro fine on Meta was settles for only a few hundred million euro after half a decade of litigation and ended up including all subsequent fines in what was forgiven despite them continuing the activity. In theory it should dissuade them, but the companies being fined that really deserve it have annual profits greater than most countries’ GDPs. They can litigate indefinitely against the entire EuroBlock and keep making a profit from the activities while doing it.


  • This. It’s weird how a particular GrapheneOS supporter keeps arguing how awful /e/ and CalyxOS are/were, and how microG is the worst thing ever. But then offers only native Google or nothing for Play Services (sandboxed mind you). The very first fallacy you learn in Cybersecurity is that if it can’t do what someone needs, it’s not secure because it’s not viable. Having nothing for Play Services is often not an option for many people. And when Google itself is one of your threat actors, literally the world’s worst solution that provides the barest modicum of protection against Google is by definition more secure. Just allow Sandboxing MicroG as an option already for those of us with a bigger threat surface from Google than from Cellebrite-using nation-state actors.

    Full disclosure: I’ve looked at using their absolutely excellent build tools to create a fork with MicroG allowed. But it turns out to be non-trivial to add the signature spoofing permission to the system and grant it to only MicroG, and conflicts with the custom Google Play config that allows Sandboxing.