Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)L
Posts
4
Comments
172
Joined
3 yr. ago

  • Which is better than nothing but I can't help but see it as walking into another exclusive partnership. Also, none of those phones are out yet so I'll believe it when I see it.

    Even if it pans out and there will be one Motorola phone supporting GrapheneOS out of the box in 2027, there's the issue of how much it will cost (I think it's supposed to be a "flagship"), what markets it will be available in, what the unlock process and conditions will be like etc.

    Last but not least I doubt Lenovo's commitment to "seven years of proper updates", which I will also believe when I see. Their track record for Android updates is notoriously poor. They claim 3-5 major Android updates for most of their models but the best I've actually seen them do is one update (13 to 14) – and that's for phones released 2-3 years ago. If that's the pace they wanna go we'll be lucky to get two updates in those 7 years.

  • I mean, it's been 20 years since GPLv3 came out.

  • My MS account is doing a thing lately where I have to enter the TOTP twice to login successfuly. It has to be two different TOTPs, too, can't enter the same one; I have to literally wait until the first one expires and get another one.

    Didn't experience any of the other shenanigans described in the article though, so there's that.

  • These are welcome changes but I hope they will address the elephant in the room sooner or later. They can't go on depending on Pixels and hardware memory tagging. They need a roadmap for opening up the project to more phone models and they need it yesterday.

    They've drummed up some publicity with the journalist debacle so it's a good time to use that. But people who hear about Graphene will want to have some phone choices. "Get an old Pixel" is about to age like milk.

  • Tagged VLANs would be needed regardless, because I have only one server with one physical connection and I wanted to have processes on it on 2 different networks.

    Docker is neither here nor there, you're right it's not needed for the solution. I was using it anyway, I know lots of selfhosters do, and it does make it easy to create an ipvlan and put an app on it.

    Docker is not the only way to achieve containerization but I do appreciate and use containerization (and virtualization). It lets the host OS stay simpler and cleaner and prevents the various apps from messing with it. It makes it easy to control each app's environment. You can do app containers, system containers or VMs as needed. It makes it easy to back up, restore and reproduce an app and its state, independently of the host OS or any other app.

    Abstractions help... they empower you to do more. You invest some time into learning, sure, but it pays off later in time saved managing and the ability to do more complex stuff faster.

    Troubleshooting is what it is. Nothing's perfect, you're going to end up troubleshooting something sometime not matter what you use.

  • I'm not an expert so take this with a grain of salt, but it seemed to me that the driver approach is the more useful abstraction and also the more modern, and that the old one will get eventually phased out (or stay there under the hood, out of the way).

    I did see that some tutorials started out with "figure out if you have a hardware switch" but this way I didn't have to care.

  • I did initially do it with the firewall alone. I created a "br-nvr" device, moved lan1 from br-lan to it, and used br-nvr as the device for the NVR interface and firewall zone, then selectively let my phone and the NVR app from the LAN zone access the camera ports with traffic rules.

    Everything else about the interface and zone stayed the same as they are now. That's what's great about the OpenWRT abstractions. I really appreciated how easy it was to get things working with the firewall zones alone, don't get me wrong.

    The one major issue with that approach was that the NVR app is outside the NVR zone and I wanted it in there.

    • It makes broadcasting a non-issue, (I really don't want to have to learn how to do cross-network broadcasts and I understand they're fraught with problems anyway).
    • Better security with less complexity. A single camera can have like 3 ports that need to be made accessible, and different cameras will have different ports. Making and maintaining traffic rules for multiple cameras would rapidly turn into a nightmare.

    With the NVR app in the same isolated network as the cameras they can do whatever they want in there without needing explicit rules.

    But I couldn't put the NVR docker container into the NVR network, because it lives on a machine on the LAN network, and you can't have the host machine on one network and a app on it in another network, with a single physical cable... unless you use tagged VLANs.

    There are also some potential annoyances in the future if I ever want to move cables around the ports or make more complex setups, the VLAN abstraction makes things easier.

  • In this particular case it wasn't Docker that gave me the headaches, it was OpenWRT and wrapping my head around tagged VLANs.

    Once you have the VLANs working on the router and the tagged interfaces up on the server, pointing a Docker network or an LXC at the eth0.100 interface is equally easy.

    Now, when I first got the camera I was considering adding a secondary network card to the server and plugging the camera into that, so it would be directly hardwired into the machine running the NVR. If I had done that I was given to understand that taking ownership of a physical NIC would have been much easier with LXC than with Docker.

    (We'll never know because I couldn't find the PCI network card.)

  • Selfhosted @lemmy.world

    How to physically isolate a camera with OpenWRT, tagged VLANs and Docker

  • It's virtually unknown in the Linux world too. It's literally something they made up overnight and are trying to astroturf.

    I'd say "what a time to be alive" to see the day someone considers it worth astroturfing a Linux distro, except there's probably some nefarious shit behind it.

  • I'm not OP but yeah, basically. People who are passionate about a specific topic will know what's up in that area.

    I can name half a dozen of the most popular Arch-based distros off the top of my head because... they're actually well-known. Meaning they've been around for years, I've used several personally and can argue their pros and cons, and they feature prominently in objective lineups like the Steam Hardware Survey. Omarchy is none of these things.

  • Paywall.

  • Which is why, hopefully, this union will progress to being a national IT union and not remain a strictly one-time Microsoft thing.

  • They'd have to effectively close down the Czech branch of the company.

    There used to be shenanigans where an owner would shut down one company and continue as another but goverment labor watchdogs have gotten wise to such methods. And it would be ridiculously overt for a corporation like Microsoft especially under these circumstances when they're in the full spotlight.

    No, they'll try to "lobby" the politicians as usual and push for union-unfriendly legislation, try to limit union applicability to certain industry branches, and if all else fails pull out of Czech Republic and hope the rest of Eastern Europe doesn't follow suit.

  • Hetzner + a HDD backup would basically get you to 3-2-1.

    As a rule of thumb I'd keep the SSDs for live data and HDDs for backup.

    Hetzner supports multiple good backup tools so you have options, and their prices are decent.

    But please stick to Restic (or Borg) because they're actually designed for backup and have built-in encryption, compression, deduplication, integrity, recovery etc. Don't use "sync" tools like rsync.

    Please, please, please assume that any of the SSDs and HDDs and cloud storage can dissapear at any time. Sit down and run some scenarios on paper, see what you'd do in each case.

    Also a good idea is to sit down and categorize all your data on a scale of "how much my life would be over if I lost this".

    Sometimes super-essential data can be very small. For example a list of things to do in case of untimely demies (a "digital will") can be a single text file that can be easily stored (encrypted) with family members. EncryptPad is a cross-platform text editor that uses open, standard encryption and can use a simple password.

    If you need an extra form of backup media for ultra-essential data, Blu Ray optical discs are still an option. They are specifically designed for this and an USB optical writer is cheap.

    Last but not least, store your "cold" backups in proper storage enclosures. For HDDs I like Orico padded boxes, for Blu Ray's use a "CD wallet".

  • Who wants to bet we'll see attempts to nullify votes that don't fit the declared affiliation before the next elections are over?

  • They're saying Graphene without MTE is less secure, which isn't something they want.

    Well they're inevitably backing into a dead-end. MTE is obviously off the table now which means eventually they'll have no hardware fitting to their super-exacting demands. Motorola might come through, or not.

    I hate being a conspiracy theorist but honestly sometimes the way Graphene clings to Pixels feels like a Google scheme to boost their pathetic Pixel market share.

  • Not as such, but there are models that will be crippled in various ways by the lack of a connection.

    I saw one that would frantically try to connect (to what, I don't know) for several minutes out of every hour and while that was going on (because it was offline) the UI would slow down.

  • There are models that will try out unencrypted wifi AP just to phone home. No extra equipment needed and unfortunately the chances of finding an open AP are pretty good in the middle of the city.

  • Have you tried using it as a DLNA renderer? For example using BubbleUPnP on a mobile device as DLNA controller to cast content from Jellyfin+DLNA plugin as DLNA server.

  • Selfhosted @lemmy.world

    How do you guys use Tailscale (or other VPN) with containers

  • Selfhosted @lemmy.world

    Migrating away from Gandi, 9 months later

  • Selfhosted @lemmy.world

    Upgrading a self-hosted server (episode 3)