Hi everyone, I have an old Google account that I don’t use anymore, and I’m thinking about deleting it. But I’m worried I may have used that email address for government services or other important accounts in the past, and I don’t want to overlook something that could cause problems later.

What should I check before deleting it? Do you have similar experience?

  • LewdLemon@sh.itjust.works
    3·
    6 hours ago

    Great questions, all of them! No, there need not be any “master file” - but there can be. ;) Let me lay it out for you.

    There are two possible models you can build with Syncthing:

    • a star-shaped client-server structure places the server at the centre of the network. The server is the central authority that always holds the “master file”, i.e. the newest version of the file, and the clients receive it from there (or don’t, if they’re already up to date). This structure, mind you, does not require dedicated server hardware: if you, say, have a phone, a notebook and a desktop PC, you can also make your phone the “server”, i.e. the only device that is connected to all the others and that “serves” everyone the newest version of your password DB.
    • a meshed peer-to-peer structure has no centre - just a number of clients that are connected to all other clients. In this network, whichever device has the “newest” version of the file is the device that distributes this newest copy to all connected peers.

    Which model you go for depends on how many devices you’re planning to hook up. If you only need to keep two devices in sync (e.g. your phone and your notebook), the client-server structure would probably be overkill, and actually Syncthing is typically deployed in serverless peer-to-peer scenarios.

    However, if you have a lot of devices to sync, it may be more efficient to go with the client-server setup. Example time to make this more transparent!

    Let’s say you go with the p2p structure because you only have a phone and a notebook hooked up to Syncthing. You configure:

    • on the phone: share a folder with the notebook!
    • on the notebook: share a folder with the phone!

    But now you want to add another device, e.g. a desktop PC. Now you need to

    • add the PC to the phone, and add the share
    • add the PC to the notebook, and add the share
    • add the phone and the notebook to the PC, and add the share

    Otherwise you end up with a partial mesh, i.e. not every device immediately writes its changes to all others.

    If you now add a fourth device that also needs to receive the share, you already have to make changes on four devices. And so on and so on. The more devices you add, the more work you need to put in.

    TL;DR:

    Syncthing can work without a “master file”. It can do peer-to-peer shares and work without a server. However, the more devices you need to share to, the more efficient a star-shaped / server-like architecture will become. This, however, does not require dedicated server hardware; you just decide that one of the devices will fulfil the role of the server by hooking all client devices up to it.

    One last, minor correction: Syncthing only lets you share folders, not files. So you’d create a “KeePass” folder, toss your DB in there and share the folder to the receiving devices.

    • imminent_nebula@lemmy.ca
      1·
      6 hours ago

      Appreciate it thank you! So basically in either setup syncthing just checks for an updated version of the file on any device and replaces the old versions on all devices? Do I have this right?:

      A simple 2 device setup would be easy with a p2p structure, but can get convoluted when adding more as they all then need to connect to eachother. If I have multiple devices (which I do) a star-shaped structure means each device only has to connect to the main server device.

      In the p2p example, the phone adds a new password, the notebook sees the change through syncthing monitoring the phones folder, and replaces it’s file with the new one. If I change something on the phone when I’m out of network, the change is local and works fine on the phone (but obviously wouldnt on the notebook) then syncs when i get back on the network and updates the notebooks file.

      In the star-shaped structure, all devices point to the server file. I change something on network on my phone, the server file then sees the change and updates, then the other devices do the same. If I change something off network, again the same as the p2p example with one extra step; once back on network the server sees the change on the phone, updates, then the other devices update to that.

      Is that the jist of it?

      Edit: So basically if I wait for my laptop, I set it up, then on my phone for example I set syncthing to the folder on the laptop, then change the local Keepass folder to the syncthing laptopo folder?

      • LewdLemon@sh.itjust.works
        1·
        4 hours ago

        Accurate, all of it. You’ve got it.

        Two more (nice) things:

        1. (Assuming a star-shaped setup with a server at the centre) If you happen to make changes on the phone and another client device simultaneously (meaning: there is a collision of versions, since both have changes to write), Syncthing normally creates a “conflicted copy”. Whenever you see these files, you know that some changes couldn’t be merged and need to manually untangle the changes. No biggy normally.
        2. Syncthing does support versioning, meaning: Your server can store several versions of the same database file. That way, if you happen to accidentally delete some entries from your DB, you can revert back to an earlier copy of the file.