asymptotically2

Slightly OT but why should I choose a JWT over creating some opaque token (random bytes) and storing that in a database mapping it to a user's ID?

It seems like people create short lived JWTs and then pass some opaque token to an auth endpoint to get a new JWT signed whenever the old one expires, or they store the JWTs in a database so that they can be revoked, making me question their usefulness.

You need to pay Oracle $lots for a GraalVM enterprise licence to get profile guided optimisations, if you want some of your peak performance back.

Try making your class final. Then it won't bother looking up the address of the virtual function in cases where it knows which class it is.

Having a proof of work function that did something useful outside of minting new blocks would be awful for a cryptocurrency.

You can opt-in to sharing some info with the popcon tool.

Mining with JavaScript or WebAssembly is no longer viable as being competitive now requires using a JIT compiler.

Nothing can really be done about it. Pool operators can ban the wallet addresses of known bot masters from connecting to their pool, but you can't really ban someone from participating in an anonymous decentralised network.

Epic are anti-Linux.

Yes, I'm running them on kernel 5.5.13 (which came out today)

See Monero. Transaction senders, recipients, and amounts are hidden by default.