SayCyberOnceMore

  • 4 Posts
  • 145 Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle
  • Why do I use a a different email address for everything? I can just close an account once I no longer use the service or once they start getting spammy, I get next to no spam.

    This is really useful and I do this too with the service / product name as the “name” (ie microsoft-mail@mydomain.tla)

    It’s interesting to see how emails are sold / transferred over time…





  • Not quite following you there, let me see if my system helps.

    I have a NAS with multiple syncthing instances (services) running:

    • me, my laptops, my phone
    • my partner, their laptop & phone
    • other equipment in the house (for Music, etc) For me & my partner, I added a shared folder that both syncthing instances used.

    It works fine if you ignore file ownerships and set the underlying permissions so both users (ie the group users) have write access. But, if we’re both editing something, syncthing will nuke one of them (so I have versioning on). But for us this never happens as they’re rarely writing to those files.




  • The NAS is on site, yes. It’s backed up to Hetzner - inc. it’s own /etc, /home, etc. so the NAS itself is kinda a 2-1 (2 backups, 1 offsite), but it would be a lot of rework to restore and that’s the device I’d need to recover everything else in case of a total disaster (like a house fire).

    (🤔 better check the Hetzner encryption is noted in my keypass file)

    I do need to get it’s config setup in Ansible though so it can be rebuilt automatically, but Ansible for single devices can be a little overkill and difficult to maintain.

    Similar for my hypervisor box… damn… there goes some more evenings…


  • Nice philosophy.

    I’m kinda in the middle ground here.

    I backup “everything” from my raspberries, and just \home for laptops but for an actual disaster recovery I’d just do a clean install, get an IP address and then reinstall everything via Ansible, then drag my home data back off the NAS

    But… I like that statement. I’ll use that at work.


  • I suggest you have 2 separate physical devices.

    1 - a NAS 2 - a server that you’re running everything on.

    Use OMV for the NAS if you’re not technical enough / want less maintenance and just keep your data there with only a backup app installed,

    On the other device pick whatever you’re comfortable with, docker is the mainstream choice, you’ll get loads of youtube / forum / lemmy support, but there’s other options of course.

    The advantage to this setup is that you can backup your server and if when you f*ck up you can restore it again.

    Less eggs in more baskets

    And as others have said, look at your router & internet security too










  • Sorry, no disrespect intended, but I’m shocked. It’s like hearing someone say they drive a 1988 Toyota Cressida because it’s great…

    How did you know I had an 88 Cressida? (jk)

    You have good points there, but for a homelab, it does show some interesting insights (ie, I did an upgrade of my Raspberry Pi Zeros and saw how all their latency changed after the reboot… weird)

    I’ve been using this for years as it just worked, but a recent update has broken it (a simple “v1.10 is earlier than v1.9” issue) and I had to rollback and have been waiting for someone to fix the bug for a few weeks, so, yep, the slowness of response is a fair point.

    Ah, dunno, maybe I’ll look at some alternatives… one day…