mirror of
https://github.com/matze/wastebin.git
synced 2026-04-25 00:25:59 +03:00
[GH-ISSUE #187] Feature suggestion: Delete paste by using the password #109
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/wastebin-matze#109
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @christianmerges on GitHub (Oct 13, 2025).
Original GitHub issue: https://github.com/matze/wastebin/issues/187
At the moment deleting a paste is not possible without saving the cookie from creating. It would be great to just delete it in the frontend and via apicall just by providing the password.
@matze commented on GitHub (Oct 14, 2025):
So you want to conflate decryption with further access control?
@christianmerges commented on GitHub (Oct 14, 2025):
Not really. When it is possible to view the cobtent by providing url and password, it should also be possible for the backend to delete that entry from the database.
@matze commented on GitHub (Oct 14, 2025):
Yes, so much is clear. But the point is: just because I have the password now (perhaps shared by a colleague) why would that give me the right to also be able to delete it?
@christianmerges commented on GitHub (Oct 14, 2025):
Because the creator of the paste chose to. Sonetimes it is needed to open the paste on another device again, so the feature "burn after view" is not helping. I have a bunch of pasts now, where i do not have saved the cooke, which i wanna delete now. We could also make these deletions with an "admin apikey".
@matze commented on GitHub (Oct 14, 2025):
Would be great, if you had phrased it like that in the initial request :-)
@christianmerges commented on GitHub (Oct 14, 2025):
I try to improve every day :)