- 0 posts
- 5 comments
Your concerns are nonsensical. Google profits from the logic of surveillance-capitalism. Their hardware division is about ensuring people use their software. They’ll sell hardware at a loss to retain and expand their user-base.
Google does not manufacture hardware. Don’t get hung up on the branding. Pixels are made by the same company that makes iPhones and a plethora of other computers with a myriad of different brandings.
If a Pixel is sold at a loss buying a Pixel new and installing GrapheneOS on it damages Google financially. I really want to impress upon readers the important distinctions here.
Something to think about: If GrapheneOS grows in usage their clientele are targets that Google wants. The framing by some users of Google harassing a tiny minority of consumers fails to understand that Google is a surveillance company. If all the high-value targets migrate entirely of Google’s platforms their leverage to secure governmental contracts weakens significantly.
I also think it’s the typical managerial class being disconnected entirely from the realities on the ground and within the organization’s working-class. Many of Google’s employees are against the position and direction the company’s moving towards. Google has a powerful monopoly and everything should be done to weaken it. Users should donate to GrapheneOS just in solidarity–take them to court and set precedent; what Google is doing should be illegal.
Privacy@lemmy.ml•Smartphone - Privacy - Is there really an alternative to GrapheneOS?bydropdrip@lemmy.ml
19 hoursThere’s not. Procure a Pixel and use GrapheneOS. Even if your primary concern was just mass surveillance this is still the best you can do. /e/OS compromises:
Other projects likewise make compromises with Google.
Google is a mass-surveillance company that runs on the logic of surveillance-capitalism. Small compromises still give Google a plethora of data from which derivatives can be inferred. There should be no compromises.
An alternative is a GNU/Linux phone like the Pinephone. Mobian (Debian for mobiles) supports other platforms too. This is my preferred approach as it’s not derived from AOSP which is ultimately controlled by Google. It’s also more experimental with all the implications that entails: less secure, less reliable blah blah blah.
Concerns about supporting Google via procuring a Pixel device:
Your concerns are nonsensical. Google profits from the logic of surveillance-capitalism. Their hardware division is about ensuring people use their software. They’ll sell hardware at a loss to retain and expand their user-base.
Google does not manufacture hardware. Don’t get hung up on the branding. Pixels are made by the same company that makes iPhones and a plethora of other computers with a myriad of different brandings.
If a Pixel is sold at a loss buying a Pixel new and installing GrapheneOS on it damages Google financially. I really want to impress upon readers the important distinctions here.



Of course, but you will need a display server.
That command will launch Xorg and Libreoffice. (Curious if wayland has an equivalent [please message me if you know how].) This is generally how I use my machines.
You can then switch between ttys (inside X you press CTRL+ALT+[function key]; inside a tty you just press ALT+[function key] and launch separate programs. You can have multiple graphical programs running, each under its own display server, or have multiple under the one (manually specifying geometry so they don’t overlap).
Cage is in the debian-repository and seems to accomplish what I want: run a single program under wayland from a tty. I really don’t understand wayland’s design though so I would appreciate it if someone more familiar with wayland could explain other ways of accomplishing this. Ideally I’d like to specify window geometry and cage doesn’t seem to support this.