Skip Navigation

Posts
2
Comments
240
Joined
2 yr. ago

  • I'm good with him staying on in a state where he can't fuck us over more. My worry is who then pulls the puppet strings.

  • I'm fine with bluetooth, but I think a problem for usb-c is that it comes out the bottom of the phone, so awkward to use the phone with headphones. Also, can't charge and listen.

  • You can't really do configuration management with a GUI. Or version control. Everything I do I manage with Ansible as much as possible. YAML is self-documenting as well. How much effort is 'run command with parameter' documentation vs explaining how to navigate a GUI?

  • "keeping up with new tech" is often just re-inventing the wheel. If it isn't broke, and can still be maintained, then why break it because you like the flavor of the week?

  • As with all things infosec (and life in general), best practice is to not get yourself into the mess in the first place vs. trying to clean up the mess later. You should have already not had personal data "in the cloud" and should have been using unique identifiers and authentication for every service that you use.

  • Linux/Cups. Postscript. Laser. Have never had a problem. Printers not working is a "put the logic in the Windoze driver" problem vs telling a good printer "Print this".

  • Because marketing dweebs in powerful companies now own the internet.

  • For a disc you need a new fork if it does not already have mounts for the disc calipers. By "new set of gears" I assume rear cassette. You will need a chain whip and a cassette tool. Keep in mind that all drivetrain parts tend to wear together. Its important to swap your chain when it starts to wear. I just do mine every spring to be safe. If it's been awhile, you'll need new chaingring(s), casette, and chain. After a longer time, it's good to replace the pulleys in the rear derailleur too.

    But like others have said, with this amount of effort, just get another bike.

  • You can't drive a helicopter down the freeway. You can't land one just anywhere.

  • I don't like lxc containers, and my build automation works well at the full system level vs containers.

    Running your services bare metal these days is insane. If I have a problem, I just restore or rebuild that purpose-built vm from configuration management. This is also a lot more flexible and cost effective vs having separate hardware for each thing.

    Redundancy is also easier, should I decide it is worth the hardware investment.

  • I run proxmox on a System76 Thelio. ZFS mirror, 16 cores, 64GB. Synology NAS for data storage and backup. Dual NICs bonded with ovs for the VMs. The onboard NIC for connecting to proxmox itself. One of the VMs then rclones the backup share to rsync.net

    One of the VMs is Plex/Sonarr/Radarr/Transmission. Media is stored via NFS to the NAS.

  • Me too, but worse all of my whitewater and mountain bike buddies only coordinate through Facebook, so I'm stuck using that too.

  • Thanks, I'll try that!

  • The new NIST guidance is to have something long. Special characters don't matter. So a good passphrase that you can remember > short line noise. NIST also recommends against constant password rotation, but to instead audit for dictionary attacks. See also: https://www.netsec.news/summary-of-the-nist-password-recommendations-for-2021/

    Yes, it is bad programming. Of course, on the backend you must never store passwords in the clear. You should never grow your own hashing algorithm.

  • I would never own one. I don't like closed systems that try to lock my data away. Also, the inflexible UI sucks.

    I didn't really care much about other people's preferences until this past weekend at my Aunt's celebration of life gathering. My cousin insisted on sending photos taken there via iMessages (translation: group mms) instead of posting somewhere or using email. Blurry is an understatement. Those photos are useless.