Make encrypted book deletion more reliable #20

New Issue

EpicKnarvik97 · 2026-01-08T14:14:54+01:00

EpicKnarvik97 commented

2026-01-08 14:14:54 +01:00

One problem with encrypted books is that encrypted versions of each book must be stored to disk, and files are currently blocking new encryptions for the same book. When the decrypt command is used, the relevant file is deleted from the disk, but what if copies were made in the meantime? Really, there should be a tracking system counting the number of instances of an encrypted book, accounting for stack size and plugin-based and vanilla book copying. Or perhaps it shouldn't be possible to copy an encrypted book?
In any case, there should be a better way to track and delete encrypted books, ensuring the server owner won't need to manually delete books all the time. There might need to be an id for encrypted books to differentiate books with the same title and different passwords.

One problem with encrypted books is that encrypted versions of each book must be stored to disk, and files are currently blocking new encryptions for the same book. When the decrypt command is used, the relevant file is deleted from the disk, but what if copies were made in the meantime? Really, there should be a tracking system counting the number of instances of an encrypted book, accounting for stack size and plugin-based and vanilla book copying. Or perhaps it shouldn't be possible to copy an encrypted book? In any case, there should be a better way to track and delete encrypted books, ensuring the server owner won't need to manually delete books all the time. There might need to be an id for encrypted books to differentiate books with the same title and different passwords.

EpicKnarvik97 added the enhancement label 2026-01-08 14:14:54 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: EpicKnarvik97/Books-Without-Borders#20