fishcake on Nostr: Also note that if you upload duplicate, we will only delete associations as per spec: ...
Also note that if you upload duplicate, we will only delete associations as per spec:
Deletion
DELETE $api_url/<sha256-hash>(.ext)
AUTH required
Note that the /<sha256-hash> part is from the original file, not from the transformed file if the uploaded file went through any server transformation.
The extension is optional as the file hash is the only needed file identification.
The server should reject deletes from users other than the original uploader with the appropriate http response code (403 Forbidden).
It should be noted that more than one user may have uploaded the same file (with the same hash). In this case, a delete must not really delete the file but just remove the user's pubkey from the file owners list (considering the server keeps just one copy of the same file, because multiple uploads of the same file results in the same file hash).
The successful response is a 200 OK one with just basic JSON fields:
{
status: "success",
message: "File deleted."
}
🐶🐾🫡
Deletion
DELETE $api_url/<sha256-hash>(.ext)
AUTH required
Note that the /<sha256-hash> part is from the original file, not from the transformed file if the uploaded file went through any server transformation.
The extension is optional as the file hash is the only needed file identification.
The server should reject deletes from users other than the original uploader with the appropriate http response code (403 Forbidden).
It should be noted that more than one user may have uploaded the same file (with the same hash). In this case, a delete must not really delete the file but just remove the user's pubkey from the file owners list (considering the server keeps just one copy of the same file, because multiple uploads of the same file results in the same file hash).
The successful response is a 200 OK one with just basic JSON fields:
{
status: "success",
message: "File deleted."
}
🐶🐾🫡