11–20 of 64 posts
You built your own sync engine? Why?
Most sync engines are targeted towards being fast. I suppose for a PM you'd want one that's very resource efficienct. I'm just spitballing here, I'm not OP
Earlier quoted context omitted.
Fair enough. I like staying pseudonymous on the internet, but I also understand where you're coming from. My name is Doug, based in Toronto, Canada. I've been a software engineer for over 10 years, working in various startups that handle very sensitive data (fintech, health tech, legal tech.) I've had the opportunity to build security-heavy software and directly handled sensitive info like SIN, bank details, patient…
How's support for credit card form entries? That's the one thing that makes me miss 1Password as a current keepass user and will make me move over.
Give it a try and if you find anything, I'll prioritize fixing it. I'm really keen on getting a top-notch autofill engine.
Congrats! How’s it compare vs self-hosted vaultwarden?
Way less overhead than hosting your own vaultwarden instance, so way more user friendly with basically the same effect. The big difference is there's no server at all. With vaultwarden you're running a box that holds your whole vault and you have to keep it patched, backed up and secured (sysadmin skills basically). Bramble just syncs your devices directly so there's nothing to host or maintain = no single point of failure.
One tradeoff is both devices need to be online at the same time, since there's no server in the middle holding your changes for later. For me that's worth it and intentional.
What ai tools are you using if I may ask, genuinely interested.
You built your own sync engine? Why?
Bramble's sync is built around its own encrypted vault instead. When two devices conflict it just compares timestamps on the encrypted entries and keeps the newer one as-is, without ever unwrapping your per-entry keys to merge. Nothing off the shelf did that against my vault format, so the core is custom. It's a pretty simple implementation tbh
Really clean concept. Keeping everything entirely on-disk instead of relying on a third-party cloud is something I've been wanting to see more of.
I think local-first password managers are the way forward. Big tech companies already have way too much power and having them mediate our most important data is a bad precedent to set. I like that you made this P2P, I designed one that sits on top of sqlite and is 100% local first but is not P2P, take a look if you are interested in some prior art in this space: https://saveoursecrets.com/ I decided to go with native…
I'll check out your website and see what's up!
When I hear P2P I imagine my data going through other people's devices - but it sounds like this is a private P2P network.