• 2 Posts
  • 1.69K Comments
Joined 3 years ago
cake
Cake day: July 11th, 2023

help-circle

  • if you have an always available central storage, and your keepass clients are never offline when you want to use them, I recommend to use that for storing the database file. but this is rare, and things can go wrong such that this central storage is not accessible, like network breaking down.

    Otherwise, devices are online at different times, I would recommend using Syncthing, and then all devices can upload/download the database file when they see each other.

    when using synthing, you’ll likely get into file conflicts, though. but it is predictable when will it happen, and you can avoid it if you are careful.
    lets say, you edit the database on your phone, syncthing on it is sleeping for energy saving, you turn on your computer and you edit the database there too. then computer is kept running, and later the syncthing app on the phone wakes up. syncthing will see that the database file has changed on multiple devices, in a different way, and you will have to choose which one to keep.

    if you can’t use keeshare of keepassxc, you’ll be holding your primary database on the syncthing folder. you will lose the changes made on one of your devices, depending on which one you discarded. but syncthing should save the discarded version with a special name, and I think, but you should check, the desktop version can handle this: if it has the database opened and unlocked, and you discard the local version in syncthing on your PC, resaving the database in keepass should merge the changes and no data is lost; if you have edited the same field of an entry on both devices, both values will be in the entry history. if this works this way, the conflict backup made by syncthing is nt needed.

    if you can use keeshare, I believe discarding any of the versions in syncthing should fix it up eventually without data loss, because keeshare maintains a copy of the DB where your client can look for the “global state” of the DB, and always add anything to it that it deems to be new local changes not yet present in the global state. but the global state will only get eventually fixed up if all your devices will keep being able to sync to it; because if in the above scenario on your desktop you discarded the updated global state coming from your phone, to be able to accept the updated global state coming from your desktop, later your phone’s syncthing needs to be able to receive the global state you accepted elsewhere, potentially you will need to accept the remote changes here, then your keepass app needs to open the local database, process the global state database (updating it again with the local changes), and sync it to at least one other device (conflict free if there were no changes elsewhere in the meantime).
    I don’t know how deletions are handled by keeshare. if it does not keep an index of deleted entries, then keepass on your local devices will keep readding the last version of this entry. that’s likely fine if it is only added back to the trash folder, and all devices know to delete it after a certain time being there.



  • The remote devices should have local database because my main computer will not always be online.

    yeah, about that. none of the official bitwarden clients allow editing if the server is not accessible. they didn’t want to have to deal with conflict resolution

    Or should I just set up keepass instead since IIRC that’s one of the ways it can be set up.

    sounds like a better idea. but synchronization wise, conflict resolution has to happen somewhere. like when you edit an entry on two devices, and later they try to sync both changes at once. Fortunately tye keepass format has a more comprehensive entry edit history than bitwarden, so clients can figure it out.
    keepassxc on linux supports something called keeshare, check how is compatibility for that with your mobile keepass app. original keepass on windows supports some kind of automatic merging on saving and loading, maybe keepassxc does that too? if you end up using synthing, conflicts could occur at that layer, which is not hard but not so straightforward to handle, but keeshare is supposed to help with that I think.







  • if you can even verify it, unlike the proposed EU identity app that adds in all the obfuscation, and anti-debugging DRM of the world, also denying operation on any device and operating system not directly made by one of the two tech monopolies in the field.

    but that is not only what you should worry about. even with an actually auditable app, they just change it one day and practically nobody bats an eye. the common person can not and will not check anything, it updates automatically and thry know nothing. if they don’t comply, they are immediately excluded from half the world. the thing is auditability is a nice plus, but doesn’t actually matter, because it requires a fully benevolent government. if they want to push through a change, they can roll it out in 5 minutes across the whole country and no businesses can defy it.



  • by denying childcare benefits, and giving a visit from child welfare.

    the school should start the procedure when they see the kid scrolling social media regularly, or if the kid regularly says they want their phone (when somehow taken away) as that means they are already kinda addicted to it. child welfare investigates whether the suspicions are true, initiates denying benefits, and communicates directly with the parents being willing to support them improving the situation, including offering free assistance from child’s psychologist. then, the point becomes not denying benefits, but recognizing that they have little time to figure it out themselves, and giving all the help they need.









  • On it’s bacsic premise, no, you’re allowed to move my arms or person (to the extent that it is not assault, kidnapping, etc) but say, altering the state of my atoms in a way that ends my life or does me physical harm is criminal.

    see! there’s nuance! not everything is a useless sea of light switches. there is no problem with squishing a grape, but there is a problem with causing similar physical harm to living beings

    My claim is that altering the position of a switch is not destruction of property,

    switches are like grapes. digital storage in your phone is like living beings. something that is not easy or possible to reproduce the same way it was before the damage.