wip: Send dm on sigit sign/complete #230
No reviewers
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sigit/sigit.io#230
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "92-send-completion-dm"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #92
The PR implements the initial private DM sending (nip17) as discussed in the issue #92, makes the changes to
addRelay
function by skipping duplicate relays while adding, andcreateWrap
function by having a wrap'screated_at
date set randomly in the past (up to 2 days) per recommendations to avoid time-analysis attacks (https://github.com/nostr-protocol/nips/blob/master/59.md#other-considerations).We send the dms on sigit:
/sign
/sign
/verify
Each dm does the following:
Postponed:
createWrap
for side effects. The updated function now setscreated_at
randomly up to two days in the past. How will this affect the sorting we do infetchEvents
(when limit is setfilter.limit
)?Blocked:
callbackPath
navigation -handleRootRedirect
when users are not logged in (#229)Improvement possible:
Checkout
From your project repository, check out a new branch and test the changes.