secureness

Actually JWT will have the same secureness like Bearer Tokens or Cookies, wherever you store it, its not `less` secure.

But if we rely on this too much it would in theory give more power to hackers, and more reliance on the secureness of such a system.

If worried about the secureness of your Dropbox, you can create a free new account that only stores your airdropper folder and share that folder with your primary account.

Yeah, but just in terms of redeploy without a downtime, secureness if new version won’t start properly, and redundancy when one server is down because of an OS error while you were asleep.

For instance, we can do this with something like a TCP library just by evaluating it against the state machine published in the RFC. Similarly, custom protocols are ultimately just state machines, and it's easier to effect secureness when you limit the protocol to a regular or context-free grammar[1].

Companies must balance where they want to be in the secureness spectrum against the investment cost to get there and it seems that high grade security isn't worth the opportunity cost for a pretty big class of companies and customers.