-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add nip-05 #15
base: master
Are you sure you want to change the base?
feat: add nip-05 #15
Conversation
Is this a "must", because of #7? Currently this is optional |
Yes, I think so |
@@ -4,6 +4,7 @@ export const users = pgTable("users", { | |||
id: serial("id").primaryKey(), | |||
encryptedConnectionSecret: text("connection_secret").notNull(), | |||
username: text("username").unique().notNull(), | |||
nostrPubkey: text("nostr_pubkey").unique(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this should be unique. It's a contact pubkey, and one person could create two or more lightning addresses
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bumi do you have any thoughts here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we make it not unique, it's not really protecting anything as discussed.
Fixes #5
Also fixes the create users endpoint which returns server error when something goes wrong (no secret, same username and now same nostr pubkey etc)