

In Signal, push notifications simply act as a ping that tells the app to wake up.
Google only pings your phone via FCM, the Signal App then polls the message itself.
Edit: oops, you meant the pop-up. You can disable them from showing the message.
verspielt verspult 🫠


In Signal, push notifications simply act as a ping that tells the app to wake up.
Google only pings your phone via FCM, the Signal App then polls the message itself.
Edit: oops, you meant the pop-up. You can disable them from showing the message.
This is a great summary. Also, see the GrapheneOS teams list of hardware prequisites. They have said themselves before that this is not a very high bar, but that there are just no other manufacturers focusing on security. Apple claim they do, and get recommended as second best option in the forums sometimes, but given the walled garden approach, it must be next to impossible to develop against, even if they unexpectedly completely open up their ecosystem.
They would probably also have to take a lot of criticism for their implementation approaches and their brand integrity would suffer immensely. Maybe there would even be some new undisclosed vulnerabilities to fix, like the goto fail bug breaking SSL encryption ten years ago.
Compare it to the new open source Nvidia drivers for Linux, they have taken quite a while to develop since Nvidia announced the release, and I don’t know if they have yet reached the performance levels of the proprietary ones. Doing this for a whole Phone, given they even fulfil the requirements hardwarewise, will probably take a decade. And in this decade, ten new iPhones will be released…


There are no phones with working encryption (a must imho and a lot of others) except the ones I listed in my initial comment. iPhones are no option because they are not unlockable. Samsung recently announced they will remove the option to unlock the bootloader as well. They also have a very broad and everchanging lineup of phones.
Google Pixel has been more of a hardware and software reference to developers than a Phone people would usually buy up until the redesign with the Pixel 6. There are so many hardware and software features that make it the perfect device to develop against (up until the recent events lol).
I’d recommend you to read their own documentation on this topic.


mentally unstable individual
Got any links on that?
Edit: nvm, found out about Daniel Micay being difficult to communicate with on the one hand and his history of being harassed and swatted on the other.
while only running that OS on… checks notes… Google’s phones…
They obviously don’t do that to please Google.


Fairphone 6, especially with /e/os is not an option atm from a security standpoint. But then again, no phone is except iPhones and Pixels (and more recent Samsung phones).
Fairphone 6 does not keep up with standard Android privacy/security patches and has no secure element to provide working disk encryption for typical users not using a strong password, among other flaws.
Regarding privacy, Murena is shilling their own proprietary Apps as alternatives to Google.
/e/OS includes numerous non-private apps and services. The Murena voice-to-text service included in /e/OS even sends user speech data to OpenAI with no local option compared to Apple and Google both offering offline speech-to-text support via local models which users can make sure is always used:
https://community.e.foundation/t/voice-to-text-feature-using-open-ai/70509
Taken from the Graphene OS forum
I always point people here: https://youtu.be/uPYjJYQEFSg
Hard to give you hints when we don’t know what your background is, so here is some basics:
For starting selfhosting I’d recommend getting comfortable with the linux command line at first (this may help: https://www.linuxcommand.org/). Set up a VM in Virt-manager / VirtualBox / VMWare / whatever hypervisor you want, install a Linux image (I’d recommend plain Debian without desktop environment). Now you have a sandbox where you can toy around. If you’re on windows you can use WSL2. If you’re already on a linux desktop, toy around there.
If you already got some hardware like a raspberry pi or old Laptop, get that up and running with a distro of your choice, plug it into your network and SSH into it, then you have got your playground there. Get the basic commands in like ls, pwd, cat, tail, touch, mkdir, rm, … And some things you can do with them. Check out their respective man-pages.
After that, install some packages, change configs (I’d recommend nano over vim for starters). From now on, there are no boundaries of what to do. Set up your first basic webserver with apache / nginx / caddy, install docker / podman and containerize / get some images, set up pihole, nextcloud, jellyfin, do whatever you like… Congratulations, you are now “self hosting”.
Maybe some day switch that Raspberry pi out for a thin client as seen in the picture from OP and install a hypervisor like Proxmox on it. If you got all that, which may take a while, you can consider networking and firewalls IMHO (you could get a cheap router that supports OpenWRT to learn about these things). Don’t open ports to the internet as long as you’re not 100% sure what you are doing. You can set up a VPN with DynDNS on most modems / routers connected to your ISP though, opening up your self hosted services only to you / anyone with access. Or use something like Tailscale / Twingate.
I could go on, but like I said, self hosting and home labbing is kind of use case / requirement specific.


Don’t worry, the rest of the world will follow suit in a minute


I actually plan on putting hardware related stuff on an extra pi since I only run a single proxmox node right now. Would be home assistant and nut tools for the ups but I might put pihole and unbound on that as well.
I am worried about the performance though because of home assistant. And it is pretty comfortable to have everything on one host that is far from being used to capacity anyway.
Without support from the vendor they don’t. Mobile computing is so locked down right now that it might be possible that not even the vendor can repair a bricked phone tbh.
Compare it to a broken BIOS on a PC. You can basically throw out your motherboard if you fail while updating it. Some devices have hardware pins used only for provisioning and debugging (JTAG) but they would have to be reverse engineered first.
GrapheneOS will only run on Pixel devices for now (including the Pixel tablet), see https://grapheneos.org/faq#supported-devices
LineageOS has two Lenovo devices listed, your (and my) tablet are not on that list, see https://wiki.lineageos.org/devices/#lenovo
Depending on the model you might find some custom built ROM on e.g. XDADevelopers, but be careful not to brick your device.
He has been the most subscribed youtuber for a while in the past. But yeah, mostly gaming and he already “quit” YouTube several times.
I’m not into drama in general, and those are serious allegations. He sure had questionable stuff going on, but considering him being an actual nazi had always seemed far off to me, but we’ll never know.
This guy rambling about degoogling and GrapheneOS, to an audience (700k views after 3h) that surely has nothing to do with that, is just great news to me as of now.
Crazy to see people stating that they never saw a video of him, but I guess the intersection of his audience and the fediverse is predictably low, especially in a degoogle community.
His recent arc with Linux and now this are pretty nice though.


Those do not have to cancel each other out necessarily. The open and modular design of Application APIs in AOSP lets the user decide which way they want to interact with the devices they own compared to the walled garden. Graphene does an excellent job by leveraging this design with further encapsulation while focusing on baseline compatibility and keeping up with google. Sadly the last one is a difficult task, so some features may take their time, while others we may never see.


That’s interesting. Apart from the pathfinding, Osmand behaves kind of sluggish for me and I had to get used to the UI/UX which can be overwhelming at first (even for tech savy people). But therefor its also a lot more sophisticated and feature complete which I also like.
To each their own, maybe even both ;)


Organic maps is the best alternative I could find. It’s on Accressent which you can get from the GrapheneOS App store. All the maps you want are downloaded to the device, no need for network access afterwards / continuously. Pathfinding is fast compared to e.g. Osmand. It’s pretty barebones though.


Thanks for the great writeup! Some of your Issues may be fixable, others stem from the fact that its sadly an alternative OS developed by a hand full of people compared to a multi billion dollar corp. But trying out new things and seeing true progression in development can be exciting too / make up for the inconveniences. In the long run this project can’t stay dependant on google, since they make their money from data and not hardware, and one of GrapheneOSs main purposes is to remove that source of income i guess. Also google is known to kill their products out of nowhere. Anyways:
Just checked and i guess you’re right! Time to do some distro hopping again lol.
Not the heroes we deserve, but the ones we need.
Would be great to see some major distros shipping with KDE by default. Fedora e.g. had this idea a little while ago.
I like both very much for what they are and would confirm that Caddy is a lot easier for beginners. The only downside is that you have to rebuild the binary with caddyx for more functionality which can be limiting e.g. for people wanting to start with dns challenges for (wildcard) certificates.