• 3 Posts
  • 54 Comments
Joined 2 months ago
cake
Cake day: September 27th, 2026

help-circle

  • Your end goal, friend, is noble, and I don’t mean to discourage you or gatekeep. And yet I must strongly advise you to slow your horses before you squander what I’d call your “social capital”, i.e. the willingness of the people close to you to follow your recommendations and try out new things. If they find their user experience greatly lagging behind what they’re used to, not only will they return to the services they were using prior to your suggestion: they will also be less likely to listen to you in the future and meet alternatives with skepticism, if not hostility. (“I’ve tried it and all this other stuff doesn’t work…”)

    Thus, you need to make sure that they have an excellent first experience with whatever you throw their way. As a tinkerer, tech enthusiast, privacy advocate, or whatever you want to call yourself, you’re likely willing to accept a great amount of jankiness, pain, and lack of feature parity because you feel you get something more valuable in return. But that is not how most people use computers. Most people do not care about privacy, digital independence or any of the things you may cherish; they want things to “just work”.

    And, to put it brutally bluntly (sorry!),

    Like I think I’d need tailscale and docker (still dont get what docker really is)

    this part alone tells me your solution is unlikely to “just work” for them. These are some basic skills to have if you want to try and compete with a billion-Dollar company and the convenience it provides to your friends.

    So, my advice is this: don’t aim for “perfect”, aim for “better”. And basically anything is better than using FB Messenger, Whatsapp, Discord or whatever they may be using. Either go for one of the large public Matrix nodes (Matrix.org is unlikely to go down any time soon…) or move your comms to Signal messenger. Both may not be fully under your control (Signal is centralised, and Matrix nodes might be closed or defederated), but they’re e2ee and so professionally managed that your friends might actually enjoy them, use them on a day-to-day basis, and even pull other people over. That way, you’re also building social capital, so that once you’ve obtained the skill to run your own and get it to the level of polish it needs to have, they’ll be willing to follow you there too.

    (If this posting sounds like I’ve learnt this the hard way, that’s because I have. Things are fine now, though: almost my entire social graph is reachable via Signal, and I’m preparing to self-host my own comms.)


  • but if message are not encrypted during transit it’s bad.

    I did not say that. ;) If you’ve secured your connection via SSL (which Nextcloud AIO forces you to do anyway), messages are encrypted in transit.

    I said they’re not end-to-end encrypted, i.e. they’re stored on the server without encryption. To be fair, in theory, this is less of an issue if you’re the one hosting the service.

    Strangely, on complain I received about signal was that they found it hard to save the pictures and videos shared on it

    That is somewhat true. Messengers like Telegram (yuck!) and (correct me if I’m wrong!) even Meta’s Whatsapp (doubleyuck!) do or at least can store all media unencrypted on the device in a folder. Signal does not do this. Every single pic/vid/whatever needs to explicitly be stored in device memory in encrypted form (there’s even a nag screen every time you do this). Also Signal does no appear to have an option so it will store media in encrypted format to the device storage. (Just looked, didn’t find anything of that kind.)

    With nextcloud talk, I would expect all the shared files to be available on the cloud drive.

    That might be correct. When you install it, Talk stubbornly creates a “Talk” folder in your NC files, which is likely to hold all media shared via Talk.




  • I’ve come across it, and I love the concept of making communication even more robust by making it independent even of the infrastructure of the internet. That said, I assumed that it would come with a lot more friction than the userbase I have in mind would tolerate. For now, my plan is to first seek an equally accessible, yet more decentralised alternative to Signal, and reserve digging into mesh networks for later.



  • Thank you so much for your offer! I’ve actually set it up last night and it’s running fine so far. It’s just that it won’t relay any calls if either of the devices is not on my network. Tunneling back into the network via VPN might be an option, but make it more cumbersome to use for some of the less techy folks around me.

    What’s your primary reason to self-host Synapse? And who do you use it with?





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

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


  • I heard keepass was going hard on the AI. Is that true? I can’t find much about it tbh.

    I can’t tell you much about that, other than

    • I’ve never heard about that
    • they haven’t got an agents.md or similar giveaway files in their Github repo that suggest they do
    • they do have a short paragraph about GenAI in their Github that reads:

      Generative AI is fast becoming a first-party feature in most development environments, including GitHub itself. If the majority of a code submission is made using Generative AI (e.g., agent-based or vibe coding) then we will document that in the pull request. All code submissions go through a rigorous review process regardless of the development workflow or submitter.

    Personally, I don’t mind devs using GenAI if it’s used in a responsible fashion, i.e.

    • it is used to support software engineering, not replace it: any actual creative / design work is done by humans, GenAI is only there to help with simple, but tedious tasks (writing smaller, easy-to-review code snippets, unit testing, etc.).
    • there’s a human at the helm, meaning: every line of code is human-reviewed.

    Also, I tend to trust projects more whose code base started long before GenAI was a thing. Typically, these have a large base of maintainers and contributors, and the people contributing code know what they’re doing. This is certainly true of Keepass.


  • Check your password manager. What other accounts is the e-mail address account linked to? Change it, then delete the account.

    If you don’t have a password manager: Now is the time to get one. I recommend KeepassXC (PC, cross-platform) / KeepassDX (Android). Combine with Syncthing for cloudless cross-device sync of the password database file.

    Also, don’t worry too much. You wouldn’t be the first to lose access to an e-mail address. Governments or “other important accounts” usually have procedures to deal with that issue. But: a Google account shouldn’t be linked to anything important anyway, let alone government accounts.







  • I set up KeePass yesterday and it works great, but without a server I’ve just been replacing the file per device as I make changes.

    If I understand, with syncthing installed on each device I can point KeePass from each of my PCs/laptops/phone to the directory on my laptop server? This will also work remotely?

    There are several misunderstandings here. Let me clear this up:

    While there is a server-based version of Syncthing, you need no server to get all the syncthing goodness! Syncthing is designed to work peer-to-peer. Just hook up, say, your mobile phone and your PC and the folder(s) you’ve shared will be in sync - no server needed.

    As for “working remotely”: while Syncthing can do that, I’d advise sticking to the default configuration, which means “LAN only”. As soon as both devices are on the same network and “see” each other, they’ll sync. This will cover most use cases anyhow. If you’re out and about, make changes to your database on your phone and then return home, your phone will talk to your stationary PC in the background and update the DB. For the odd case where changes are made on both devices, Syncthing will create a conflict file, i.e. you’ll have both changed databases and can merge them so you won’t lose either change. (Syncthing even supports versioning files, but that is for later.)