Awesome! I suggest you wait for version 1.0.1 which is currently under preview. Alternatively, GitHub source, add extension.

Lots of familiar features, but this is not controlled by any company, but running on an open protocol.

Interesting

Why tho?

Run your vaultwarden server at home and be done with it. 🤷‍♂️

😊

Vous êtes tous énormément drôles en toutes circonstances. J'admire votre capacité de travailler ensemble de manière particulière . Merci pour tout 🙏🗽💜♾️

Dev crypto done correctly?: check source code. Used publicly used crypto packages too.

Centralised password manager servers vs “dedicated vm” I suppose you mean relay?: 2 layer of encryption, even if their entire VM is hacked, there’s no way to decrypt the data.

Replace you password manager?: it’s your choice, currently all if not all stored and controlled centrally, they can change policy, change billing, change anything they want. Here, it’s running on open protocol.

Testing it sync between devices. Checked!

I would be interested in a Firefox extension. 🤙🏻

Yes! I wasn’t able to do it yet. Would love to work with you on it. I’ve also set up geyser fund and ready to go.

I’m glad to see your message mate.

Try version 1.0.1 tomorrow after google is approve it.

Its great.

ahahah, I don't mind!

I just think it settles down a little and you arrive at something that looks like a final format for the events -- or when someone else starts to implement the same standard -- we write a NIP describing what you're doing.

Whoa. This looks cool. Going to dig in tomorrow.

Exactly. I hope devs can help audit it.

But so far, it’s pretty simple, using the same encryption we used to hash DMs, as add another hash on top of it, using standard package to hash with your passcode.

💜

Try it! Version 1.0.1 is under review. Should be out tomorrow. That’s the major release.

Fuck yes finally!

Hey. In my next version which is currently being review. It has a bit more explanations in the FAQ section.

I’m short, it’s pretty save in my opinion. Because it’s is encrypted twice with 2 different things.

You need to lose your secret key, and also the password. In order to lose your data.

Also, if the community and user base likes it, I have plan to include one time password, so you can encrypt and decrypt with google Authenticator (or equivalent).

Isn't that always the case? I mean, it's true that putting databases on relays instantly makes them public, but believing that in other implementations they are private is another security issue imo. Maybe I'm missing something, but everything on the internet should be treated as if it were public, don't be fooled into thinking that your passwords are private in the hands of a company. Even using solutions like keypass there are no guarantees, data can be intercepted at any time if shared between devices, strong encryption is the best solution we have.At least this is what I understand about online security, please correct me if I'm wrong

💪🏻🔨🔥

oh. was there a bounty for a password manager? 👀

nostr:npub1fk8rya2ra7lp8m60f8jrjg4yqfv2cc8dah8wqc49drccs3dqngzqtgc5sk seems to be onboard to make one for Firefox.

Then we need someone to make on React Native, for iOS and android.

And then mass adoption for nostr protocol.

https://satellite.earth/cdn charges a ridiculously small price to store your pictures today.

If we have 3 of these providers you can probably pay them all a total of 50 satoshis and they will store your stuff for a million years.

Having them just be content-agnostic Nostr relays makes the integration easier for everybody.

SLAs

As more and more valuable data is ingested by Nostr use cases this will need to happen (and pretty sure will happen organically)

It’s in my plan to launch relay just to store this for users. Do you think that would be a good idea that would partially solve this?

that's a good question and valid concern. so, we can store them also on our own relay. what about maybe a sync feature where all passwords are stored also in a local database that can be re-broadcasted to different relays in the future? so, if your relays disappear, you aren't screwed because you at least have a locally encrypted copy?

Try it! It’s working good.

Try it tomorrow for version 1.0.1, it’s pending approval. It’s just “more complete”.

Yea. Currently all the password managers out there, people are trusting a company to safe guard encrypted passwords in their database, encrypted with one master password.

🙏🙏🙏

💜

Indeed! It’s in the roadmap. In version 1.0.1 there is a roadmap section. Specialised relay to provide this service.

I have not looked into NIP 42. Mmm

Ya!! I m embarrassed to ask you. But your work is amazing

I was thinking. This logo is bad! It’s some one looking at my password. Lol

medium. you'd have to crack both encryption methods.

I hope a dev will port it. Just wait and see. It might happen.

Yea you can say so.

1. Technology exploration.

2. There are a ton of password managers out there, there is no advantage to use lastpass (just for instance)

3. Giving people the options

4. Inspiring other devs to think outside social use case

I’m thinking where should I put this information. GitHub? This is a great bounty and hackathon. 😄

Generate new ones for new use cases. On the extension it’s just a single click, to on-boarding.

I expect nostr users will have 10 keys for 10 different unique use cases in the future.