[–] 16 points 3 days ago*

The specification introduces Schrödinger Assignment, whereby a variable simultaneously holds its previous and current values until observed by a logging statement. Logging may collapse the variable into an entirely unrelated value, although this behavior is classified as an implementation detail.

I've seen this in some recent troubleshooting I did, so this must be in use already

  • source
  • [–] 1 point 3 days ago

    But do you have File Versioning setup on all the syncthing end points?

    If so, you'll at least get sync-conflict copies - yes, you'll still need to fix them, but at least they won't (shouldn't) be totally lost.

    I guess another idea is to have separate personal keepass files to help reduce the editing on a common file...? (That's what we have)

  • source
  • parent
  • context
  • [–] 2 points 4 days ago (3 children)

    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.

  • source
  • [–] 3 points 1 week ago

    Our problem is that we're using these as boot drives and transferring files to appliances (ie network switches, etc) so we can't use a lot of the software based encryption.

    I'll just hope that the iStorage and Apricorn drives use more than smoke & mirrors to protect the contents

  • source
  • parent
  • context
  • [–] 2 points 1 week ago (2 children)

    Meh. I don't like Autumn... yeah the colour in the trees are nice, but it's just muddy mush everywhere.

    Winter's coming, but not quite here, Summer's gone, but some days are nice...

    Went into town to get a few things, yep, Christmas stuff everywhere...

    I just want to complain about not enough rain and it's too hot again.

    But apart from all that negativity, yeah, the week was ok 😁

  • source
  • [–] 2 points 1 week ago

    I'm just going to wave the MythTv flag and wave it around a little.

    Self-built box which is under clocked to run cool with a passive CPU cooler so it's quiet

    A few Hauppage TV tuner cards to record programs and then lots of torrents stored locally as I want to download / stream once.

    No issues for years, decent TV UI for TV, films and music... and it just works.

    It's just not in vogue at the moment.

  • source
  • [–] 3 points 2 weeks ago (1 child)

    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...

  • source
  • parent
  • context
  • [–] 2 points 2 weeks ago (3 children)

    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.

  • source
  • parent
  • context
  • [–] 3 points 2 weeks ago

    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

  • source
  • [–] 2 points 4 weeks ago

    Yep, our parents become our children eventually...

    I hope things smooth out for your Dad sooner rather than later!

    And everytime I go to London I see less reasons to be there and more reasons to stay away... although it does have good social / alcohol events 😉

  • source
  • parent
  • context
  • view more: next ›