drawnSignature management #242

New Issue

b · 2024-11-04T10:08:09Z

b commented

2024-11-04 10:08:09 +00:00

drawnSignature data is too big for relays

We should store on blossom, using the hash

The meta.json should contain the HASH (not the data) in the drawnSignatures section
When exporting (encrypted or not) we should include the signature data in the files folder in the zipped file (HASH.json)
Signature data should also be verified on the verify page (make sure the hash of the file is the hash in the meta.json)
The actual signing box should also be larger! And scaled down to the drawn box.

This would mean that file size is no longer a real concern.

In a future release we can save signature data in the user (app) data, so that it can be re-used across multiple sigits

`drawnSignature` data is too big for relays We should store on blossom, using the hash - [x] The meta.json should contain the HASH (not the data) in the `drawnSignatures` section - [x] When exporting (encrypted or not) we should include the signature data in the files folder in the zipped file (HASH.json) - [x] Signature data should also be verified on the verify page (make sure the hash of the file is the hash in the meta.json) - [x] The actual signing box should also be larger! And scaled down to the drawn box. This would mean that file size is no longer a real concern. In a *future release* we can save signature data in the user (app) data, so that it can be re-used across multiple sigits

enes was assigned by b

2024-11-04 10:08:15 +00:00

enes referenced this issue

2024-11-18 17:13:27 +00:00

squiggle with signature-pad and smoother lines + blossom #258

enes commented

2024-11-22 16:30:07 +00:00

When exporting (encrypted or not) we should include the signature data in the files folder in the zipped file (HASH.json)

The signature data is saved under signatures/<encrypted_hash>.json

Signature data should also be verified on the verify page (make sure the hash of the file is the hash in the meta.json)

The current implementation only throws an error if there is mismatch during hash comparison as soon as we fetch the data in fetchAndDecrypt function, there is no visual representation in the UI.

>When exporting (encrypted or not) we should include the signature data in the files folder in the zipped file (HASH.json) The signature data is saved under `signatures/<encrypted_hash>.json` >Signature data should also be verified on the verify page (make sure the hash of the file is the hash in the meta.json) The current implementation only throws an error if there is mismatch during hash comparison as soon as we fetch the data in `fetchAndDecrypt` function, there is no visual representation in the UI.

enes commented

2024-11-29 09:01:37 +00:00

Closed by #258

Closed by https://git.nostrdev.com/sigit/sigit.io/pulls/258

enes closed this issue

2024-11-29 09:01:37 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sigit/sigit.io#242