Burn after read & encryption problem

[ZeroTwopy]

I have issue with"burn after read" as when it's checked, the file opens immediately upon saving on the current page, making it impossible for anyone other than the author to read it because the link expires right after creation. The second issue is that if "encrypted" is checked and the password isn't entered, a lot of random characters appear in the link. In my opinion, there should be an option for default disabling of this for EVERYONE rather than in the settings for just one user, for example, the option to disable it would be in the .env or Docker config.

[Yureien]

Will look into the first issue, thanks for the report.

The second issue is that if "encrypted" is checked and the password isn't entered, a lot of random characters appear in the link

That's an inherent property: those random characters are the key to decrypting the messages since it's not being stored in the server.