this post was submitted on 26 May 2026
51 points (94.7% liked)

Fuck AI

7162 readers
1415 users here now

"We did it, Patrick! We made a technological breakthrough!"

A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.

AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.

founded 2 years ago
MODERATORS
 

Is there an open source no-AI password manager out there?

Trying to bail on BitWarden... KeePassXC (with SyncThing) seems to come up as the most recommended, but they've been using copilot. Seems like they might still have the strongest anti-ai stance of the available options though, despite that.
#PasswordManager #NOAI @fuck_ai

you are viewing a single comment's thread
view the rest of the comments
[–] vala@lemmy.dbzer0.com 1 points 1 day ago (2 children)

No AI, no database, no vault.

Self hosted (html only, zero dependency).

https://github.com/matdombrock/nopaz

[–] MxRemy@todon.eu 1 points 23 hours ago (1 children)

@vala whoaa what!! Lemme see if I understand this right... It's less of a password manager and more of a deterministic password generator? As in, it'll always spit out the same resulting password given the correct input passphrase + domain of the site being logged into? So you just essentially generate it again instead of ever storing it.

I'm so amazed and curious about this approach, what are the pros and cons? Obviously there's still the risk of someone learning your passphrase, but there's no hackable database of passwords. Do you get a different output from different variations of the same URL, like including a "/" at the end? What does saving the bookmark actually do, like pre-fill the URL field? Given that autofilling is supposed to be more secure than copy/pasting, is there some way to make this do that?

Sorry for the barrage but I'm very tempted by this one, it's neat!

[–] vala@lemmy.dbzer0.com 2 points 22 hours ago* (last edited 22 hours ago)

Yeah that's more or less how it works. You generate it deterministically every time.

what are the pros and cons?

Not really sure of the cons aside from the fact that you get significant "vendor"/algo lock-in. You need the exact same algo this app uses to get your password back out (good thing it's GPL).

Do you get a different output from different variations of the same URL, like including a "/".

Yeah an extra slash at the end means a whole new password. The "name" is not really a "URL" per se. It can be any string.

So for example "lemmy.dbzer0.com", "vala@lemmy.dbzer0.com", and "lemmy.dbzer0.com 2" are valid site names and will give different passwords.

That being said I could see omitting some special trailing chars, protocol strings etc.

What does saving the bookmark actually do, like pre-fill the URL field?

Basically every parameter of the password generator is codified into the URL. So bookmarking a URL allows you to load a page with prefilled data like:

  • Special chars
  • Length
  • Revision number
  • Algorithm
  • etc

These parameters are all required to be the same each time you need to generate the password. So it can help you avoid filling these forms each time + act as a reminder of what you used.

Given that autofilling is supposed to be more secure than copy/pasting, is there some way to make this do that?

It will auto-fill your master passphrase but if you mean auto-filling your credentials into sites, it would need to be made into a browser plugin to do that.