I still got an open bounty for a nostr based password manager, anyone up for it?

Reply to this note

Please Login to reply.

Discussion

So many attack vectors.

why? isn't that an implementation detail? why nostr?

Using relays as a database sounds like an anti incentive for relay operators. Why do you need a password manager with censorship resistance capabilities?

Why would you want a password manager from which you can easily be censored?

Redundancy is super important, especially for password managers.

who's censoring pass managers? and who will do it?

I agree that redundancy is important but if we start using nostr as a distributed db for whatever you need (contacts, media, passwords, code, etc...) wouldn't that bloat relays and make relay operators require a monetary incentive to allow you use them?

I guess nostr will fail to scale gracefully.

You could have just one single relay for storage, if scale is the issue.

Another benefit is that there might be multiple clients that can be used to retrieve the passwords, so that bitrott of unmaintained clients isn't an issue.

Single relay goes against redundancy.

still not bought into the idea, if you use nostr as a transport, the client still need to implement some logic on top.