• 5 Posts
  • 49 Comments
Joined 2 years ago
cake
Cake day: June 9th, 2023

help-circle
  • I’ve been trying to learn K8s and more recently the Gateway API. The struggles are that most Helm charts don’t know Gateway (most are barely Ingressroute) and I’m trying to find a solution to one service affecting the other gateways.when a service cannot find a pod, the httproute fails and when one route fails, the ingress fails. It’s a weird cascading problem.

    Right now, I’m considering adding a secondary service to each gateway that resolves to a static error page. I haven’t looked into it yet; it cane to me in the brief moment of clarity before I fell asleep last night.

    Also, I may be doing everything wrong, but I am learning and learning is fun.


  • I researched this a little while ago. The new protocol is licensed by Google and has not been released to the public. Also, unless everyone in the middle supports the protocol, messages are routed through Google’s network.

    I settled on Signal for people who will switch and SMS for the rest. I do plug Signal when I can, like sending images between Apple & Android are degraded, but not on Signal.




  • Those are some good points. I guess I was thinking about the hardware. At least where I do RAID, it’s on the controller, so that offloads much of the parity checking and such to the controller and not the CPU. It’s all probably negligible for the apps that I run, but my hardware is quite old, so maybe trying to squeeze all the performance I can is a worthwhile activity.


  • Generally, if a lower level can do a thing, I prefer to have the lower level do it. It’s not really a reason, just a rule of thumb. I like to think that the lower level is more efficient to do the thing.

    I use LVM snapshots to do my backups. I don’t have any other reason for it.

    That all being said, I’m using btrfs on one system and if I really like it, I may migrate to it. It does seem a whole lot simpler to have one thing to learn than all the layers.


  • I’ve got raid 6 at the base level and LVM for partitioning and ext4 filesystem for a k8s setup. Based on this, btrfs doesn’t provide me with any advantages that I don’t already have at a lower level.

    Additionaly, for my system, btrfs uses more bits per file or something such that I was running out of disk space vs ext4. Yeah, I can go buy more disks, but I like to think that I’m running at peak efficiency, using all the bits, with no waste.











  • Yes. It’s the “put a copy somewhere else” that I’m trying to solve for without a lot of cost and effort. So far, having a remote copy at a relative’s is good for being off site and cost, but the amount of time to support it has been less than ideal since the Pi will sometimes become unresponsive for unknown reasons and getting the family member to reboot it “is too hard”.



  • I think you’re missing the point.of the essay. He seems to be saying that Apple has decided what content you should be viewing and that they have captured the “free market” because no amount of consumer crying will change it.

    Consuming the content another way won’t affect Apple in any way since they’ll keep repeating their behavior. The author is saying that the government regulators need to get involved to restore your rights on what you can do with a device that you purchased. Near the end he even goes on to say that you (a consumer) have implicitly waived your right to sue Apple for this.

    I guess the only option is to vote or maybe not use Apple products (but are the alternatives any better?)


  • Take some time and really analyze your threat model. There are different solutions for each of them. For example, protecting against a friend swiping the drives may be as simple as LUKS on the drive and a USB key with the unlock keys. Another poster suggested leaving the backup computer wide open but encrypting the files that you back up with symmetric or asymmetric, based on your needs. If you’re hiding it from the government, check your local laws. You may be guilty until proven innocent in which case you need “plausible deniability” of what’s on the drive. That’s a different solution. Are you dealing with a well funded nation-state adversary? Maybe keying in the password isn’t such a bad idea.

    I’m using LUKS with mandos on a raspberry PI. I back up to a Pi at a friend’s house over TailScale where the disk is wide open, but Duplicity will encrypt the backup file. My threat model is a run of the mill thief swiping the computers and script kiddies hacking in.