• 1 Post
  • 36 Comments
Joined 11 months ago
cake
Cake day: August 28th, 2023

help-circle




  • Dandroid@sh.itjust.workstoSelfhosted@lemmy.worldPost your Servernames!
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    3 months ago

    Mine are named after fictional robots, computer programs, or AI. It started with my wifi being GLaDOS for 5 GHz and Wheatley for 2.4 GHz. I thought it was funny that everyone could immediately tell that Wheatley was the slower one. Over time, I continued the trend. My gaming PCs are named after characters from the Mega Man X series (desktop is Zero, laptop is X, steam deck is Sigma). My macs are named EVE and WALL-E. My server is named Sibyl System (from Psycho Pass).








  • I have a mesh system made up of Asus Zenwifi ET8s, and I have been very happy with them. They have a lot of cool features, such as having a VPN server and VPN client, with the VPN client allowing me to apply the VPN to only selected devices. It has tons of customization options for those that are knowledgeable about that sort of thing. For example, I can tweak at what signal strength AP steering happens. It has WiFi 6E and 2.5 Gbps wired backhaul.

    When I first got it, it was very buggy, and some features straight up didn’t work. But they eventually got all the bugs that I found fixed. It’s in a really good state right now.

    To address your desired features, it does have wireguard. I don’t know about DDNS, but it does not have pihole built in. It has adguard built in, but it doesn’t really seem to do much, tbh. Then again, pihole didn’t really do anything for me either. I ended up shutting off my pihole because I didn’t even notice a difference.


  • As a podman user myself, they’re essentially the same. I look at the docker documentation when learning new things about podman. 99.9% of the time, it’s exactly the same. For the features that aren’t in podman, you can use the podman-docker package. This gets you a daemon so you can have some docker-specific features such as a container being able to start/stop other containers by mounting the socket as a volume, and it allows you to use docker-compose.






  • I like podman because rootless and daemonless are built-in and default. Yes, it can be done on docker, but you have to do a bunch of shit to get it set up.

    You could create the alias alias docker="podman" and 99% of the time, you won’t even be able to tell the difference since podman is a docker drop in replacement. All the docker documentation applies to podman as well. But since docker runs as root by default, some edge cases might not work out of the box (like binding to a port on the host less than 1000).

    Podman comes with some neat tools like being able to create systemd service files to start and stop containers as services.

    To use docker-compose, you’ll need some additional packages. That’s probably the biggest drawback to podman imo. Podman wants to use pods instead of docker-compose, but I think they gotta take their heads out of their asses and just support the more popular format on that one. Not to mention docker-compose is just plain better imo. Easier to define, easier to understand, easier to modify. The list goes on and on.


  • I used to be an Android device developer back in the Lollipop days. I compiled the various images myself, including the bootloader, recovery, and the Android OS. I can say with 100% certainty that at least back in the Lollipop days, and at least on the vast, vast majority of devices (a device could theoretically change this, and I don’t know everything about every device ever released), the battery percentage that shows up when the phone is off is part of the bootloader, not Android. It’s a separate image entirely.


  • My work uses Dell servers, which have this thing called iDRAC, which is a separate embedded system that can manage the server even if the server is off. The iDRAC can turn the server on even if it’s off. Even if the server is off, you can log into the iDRAC and check the status of the server and see if there are any hardware issues, see if the server is on or off, update the firmware, etc.

    This sounds like overkill for a phone, but I wonder if they are doing it this way, with a separate embedded system. If they did, it could potentially use only a small fraction of the battery power Android uses. It could potentially last weeks or even months on a charge.

    More likely, it’s booting a separate image - not unlike recovery mode - when it turns off, and like you said, it’s not actually off. But it would be interesting if it has a separate embedded system just for tracking the location even when the OS is powered down.

    Ideally they’ll let you turn off this feature regardless of battery implications, because it sounds like a security concern if your location can be tracked even if your phone is off.

    Edit: wow, I worded my first section really poorly. But I’m to tired to fix right now. Hopefully you understand what I was saying.