sigit/sigit.io
7
2
Fork 0
Code Issues 51 Pull Requests 3 Actions Packages Projects 1 Releases Wiki Activity

feat: use nip04 for encryption and decryption of userData to store on blossom server #162

Merged
enes merged 4 commits from nip44 into staging 2024-08-22 13:52:20 +00:00
Conversation 0 Commits 4 Files Changed 4 +32 -18
s commented 2024-08-22 08:19:49 +00:00
Owner
Copy Link
  • use nip04 for encryption and decryption of userData to store on blossom server
* use nip04 for encryption and decryption of userData to store on blossom server
s added 1 commit 2024-08-22 08:19:49 +00:00
feat: use nip04 for encryption and decryption of userData to store on blossom server
Some checks failed
Open PR on Staging / audit_and_check (pull_request) Failing after 17s
Details
18270c5d8a
s added 1 commit 2024-08-22 09:37:40 +00:00
chore(workflow-audit): omit dev dependencies in npm audit
All checks were successful
Open PR on Staging / audit_and_check (pull_request) Successful in 41s
Details
73a5d42fcf
s changed title from feat: use nip04 for encryption and decryption of userData to store on blossom server to WIP: feat: use nip04 for encryption and decryption of userData to store on blossom server 2024-08-22 10:04:12 +00:00
s added 1 commit 2024-08-22 11:11:30 +00:00
fix: use old approach of using sha256 for generating d tag
All checks were successful
Open PR on Staging / audit_and_check (pull_request) Successful in 44s
Details
49c1714962
s added 1 commit 2024-08-22 11:13:08 +00:00
chore: quick fix
All checks were successful
Open PR on Staging / audit_and_check (pull_request) Successful in 43s
Details
070b02abee
s changed title from WIP: feat: use nip04 for encryption and decryption of userData to store on blossom server to feat: use nip04 for encryption and decryption of userData to store on blossom server 2024-08-22 11:13:26 +00:00
enes approved these changes 2024-08-22 11:51:16 +00:00
enes merged commit 0b9c9906b7 into staging 2024-08-22 13:52:20 +00:00
enes deleted branch nip44 2024-08-22 13:52:20 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
enes
Labels
Clear labels   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
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.

Dependencies

No dependencies set.

Reference: sigit/sigit.io#162
No description provided.
Delete Branch "nip44"

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?