Final DM (SIGit complete) not being sent #92

Open
opened 2024-05-29 09:54:19 +00:00 by b · 4 comments
Owner

When the final signer has signed, the notification email (SIGit complete + link) is not being sent

When the final signer has signed, the notification email (SIGit complete + link) is not being sent
b changed title from Final email (SIGit complete) not being sent to Final DM (SIGit complete) not being sent 2024-05-29 15:06:26 +00:00
enes self-assigned this 2024-10-09 12:29:06 +00:00
Member

@b

  1. Do we want to have a link to the /sign or a /verify in the DM?
  2. Should we send the DM as the user (last signer) or generate random private key for sending?
@b 1. Do we want to have a link to the /sign or a /verify in the DM? 2. Should we send the DM as the user (last signer) or generate random private key for sending?
Author
Owner

We can't send a kind 4 DM as the signer, as that would leak a relationship between the signers

We should either send gift-wrapped DMs or a DM from a random NPUB as you suggest

Probably kind-17 makes the most sense as otherwise the SIGit DMs could be an attack vector (trick people into visiting a dangerous url)

About the link - it should be /sign or /verify depending on whether the target NPUB is the next signer or not

We can't send a kind 4 DM as the signer, as that would leak a relationship between the signers We should either send gift-wrapped DMs or a DM from a random NPUB as you suggest Probably kind-17 makes the most sense as otherwise the SIGit DMs could be an attack vector (trick people into visiting a dangerous url) About the link - it should be /sign or /verify depending on whether the target NPUB is the next signer or not
Member

Probably kind-17 makes the most sense as otherwise the SIGit DMs could be an attack vector (trick people into visiting a dangerous url)

Did you mean
https://github.com/nostr-protocol/nips/blob/master/17.md
or
https://github.com/nostr-protocol/nips/blob/master/25.md#reactions-to-a-website or

About the link - it should be /sign or /verify depending on whether the target NPUB is the next signer or not

Ah, it's not just final signer. So, just to make sure I've understood everything, after each signing, we are sending a DM.
If there's a next signer, we send a single DM with link to /sign, and if it's a final signer we notify everyone with /verify link (creator, signers and viewers)?

This is how it looks in coracle for the quick test (nip04)
image

> Probably kind-17 makes the most sense as otherwise the SIGit DMs could be an attack vector (trick people into visiting a dangerous url) > Did you mean https://github.com/nostr-protocol/nips/blob/master/17.md or https://github.com/nostr-protocol/nips/blob/master/25.md#reactions-to-a-website or > About the link - it should be /sign or /verify depending on whether the target NPUB is the next signer or not > Ah, it's not just final signer. So, just to make sure I've understood everything, after each signing, we are sending a DM. If there's a next signer, we send a single DM with link to `/sign`, and if it's a final signer we notify everyone with `/verify` link (creator, signers and viewers)? This is how it looks in coracle for the quick test (nip04) <img width="454" alt="image" src="attachments/1032c376-9906-4d68-b1b6-fb1a6f1ac6d9">
Author
Owner

Sorry yeah, NIP-17 not kind-17 lol

We should send the creator and the signer a message after every signature (/sign or /verify depending on status). If it's a final signature then it would be sent to everyone (creator, signers, viewers, /verify only)

Sorry yeah, NIP-17 not kind-17 lol We should send the creator and the signer a message after every signature (`/sign` or `/verify` depending on status). If it's a final signature then it would be sent to everyone (creator, signers, viewers, `/verify` only)
enes added the
Kind/Feature
Status
Blocked
Priority
Low
labels 2024-10-14 11:50:08 +00:00
enes added a new dependency 2024-10-14 11:51:41 +00:00
enes added a new dependency 2024-10-14 11:51:52 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: sigit/sigit.io#92
No description provided.