Burn After Reading and JS disabled about zerobin HOT 2 OPEN

The way it works currently, the server accesses the data from the identifier, regardless of whether or not the crypto key is correct. This is because the crypto data is stored in the file along with whether or not the file is burn-on-read. As a part of fetching that data, it reads whether or not the file is burn-on-read, then if it is, wipes the file. That's the design of ZeroBin. A way to get around this would be to create a basic HTML page with an instant meta redirect to the content, then share that to the person who you intend to share the information with. Not very quick or easy, but it works.

from zerobin.

I don't care if it gets deleted if you use the wrong key, that's fine.

But if you delete it when JS is off...

from zerobin.