10 comments

  • danielmartins10 minutes ago
    I still don’t get why password managers builders think it’s a great idea to store MFA token together with the password, totally defeating the purpose of MFA in the first place.
  • thehamkercat19 minutes ago
    A vibe-coded password-manager? Sure! where do i sign up?
  • gregable1 hour ago
    How does it compare to KeePassXC?
    • d0mkaaa1 hour ago
      KeePassXC is definitely much more mature right now. I mean, Sesame is similar in being local-first and not requiring a cloud service, but I am aiming for a more modern consumer style experience. There is still a lot of work ahead to get it up to speed. I might also build more products around it eventually, so there’s a consistent ecosystem.<p>(and of course, it would be great to eventually surpass some of the existing projects :) )
      • gonzalohm2 minutes ago
        What do you mean by a &quot;consumer style experience&quot;?
  • arlattimore1 hour ago
    I like that this could be self hosted. I don&#x27;t have anything against the big password managers (I use and pay for one), but they are a massive target for hackers for obvious reasons. If everyone could self host their own vault on a personal domain, the reward for hackers is much more difficult to get access to.
    • d0mkaaa39 minutes ago
      I don&#x27;t really have anything against the big password managers either. I just don&#x27;t love having to pay for a full year upfront with some of them. More than that though, a lot of them just don&#x27;t quite fit what I want, or they feel a bit dated to use, like KeePassXC. That&#x27;s a big part of why I started building Sesame. (and hoping to expand later on to have a more pleasurable ecosystem)
  • oscarcp20 minutes ago
    How does it compare to a local deploy of PSONO?
  • ramon1563 hours ago
    how does this compare to vaultwarden + bitwarden? my only concern there is that VW can throw self-host support out the door whenever they like. not that they&#x27;d have a reason to
    • d0mkaaa2 hours ago
      vaultwarden + bitwarden is way more mature right now, but the main difference is that sesame is local-first by design. Vaultwarden also depends on staying compatible with bitwarden&#x27;s clients&#x2F;api, while this owns the whole stack
      • alacritas011 minutes ago
        bitwarden clients are open source, so it would be possible to fork them if bitwarden ever makes user unfriendly decisions
  • majorchord36 minutes ago
    No offense but you might want to consider a different styling for the app&#x2F;site because IMO this one screams &quot;Claude vibe-code style&quot;.
    • thehamkercat21 minutes ago
      it _is_ vibe-coded, you can read the commit descriptions in sesame-desktop repo<p>I wouldn&#x27;t trust any password manager or critical applications like this written after 2024<p>bitwarden&#x2F;KeePassXC are already more than enough
    • Hamuko17 minutes ago
      It&#x27;s good that vibecoded software look vibecoded, because I then immediately know not to trust that it works, not to trust that it&#x27;s secure, and not to trust that the maintainer will give a shit about it in six months.
    • d0mkaaa23 minutes ago
      Yeah I can see what you mean, but it wasn&#x27;t really intentional. I mainly wanted to avoid the usual black&#x2F;blue security-product look. I will probably keep the general direction but give it more of its own identity over time. Thank you for sharing your opinion!
  • konaraddi1 hour ago
    Does it purge passwords from memory on vault lock?
  • vladkens33 minutes ago
    Again Tauri. How then it different from Bitwarden? Desktop != Web
  • cyberax1 hour ago
    I don&#x27;t see the support for passkeys listed anywhere?
    • d0mkaaa59 minutes ago
      Passkeys will be added in the coming weeks