And the paaster github even says you have to run your own instance for security and privacy.
It says a “instance you host or trust” this is true of any web app (including Proton etc.)
Even if you self host data leaks can occur.
The fact you don’t see the need for a encrypted pastebin only speaks to your limited imagination.
Matter of facts are, people share data not wanting it to be indexable or open to data leaks by the server, data in pastebins can be sensitive & people are using E2EE pastebins.
Here is a use case what matches all your arbitrary requirements. “User wants to share sensitive data over a insecure channel (like discord), they can send a Paaster link what deletes after view, so if Discord ever tries to view it in the future they cant see the data.”
E2EE now labeled security theater 🤣
Maybe your specific use case doesn’t benefit off E2EE, but can’t believe I have to explain this. You aren’t the center of the universe and use cases of E2EE pastebins aren’t limited to your specific use case.
Even pastebin.com sees the benefit of “private” pastes, but according to your logic this shouldn’t even exist too!
Anyways this conversation has lost any sense of productivity & obviously your care or understanding of privacy is minimal.
As a final question (what I don’t want a response to) is, should every paste ever always be accessible by everyone?.. Hopefully your answer is no & you can put 2 & 2 together.
Have a good day & use any data collecting, raw text, insecure platform you want!
Certbot is great when using Nginx (or Apache2), but if you can use a different engine. Its worthwhile checking out Caddy!