verspielt verspult 🧑‍💻

  • 0 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2024

help-circle



  • 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…






  • Also e.g. the lobbying around ACPI breaking suspend to ram sometimes. Funny little Bill Gates quote on that:

    One thing I find myself wondering about is whether we shouldn’t try and make the “ACPI” extensions somehow Windows specific. It seems unfortunate if we do this work and get our partners to do the work and the result is that Linux works great without having to do the work. Maybe there is no way to avoid this problem but it does bother me. Maybe we could define the APIs so that they work well with NT and not the others even if they are open. Or maybe we could patent something related to this.



  • 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.




  • 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.






  • 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.