Co-relation does not equal causation. This is an observational study, it does not show that melatonin causes heart failure.

FTA:

Note also that the melatonin users in the study were prescribed melatonin, which probably means it was a much higher dose than what over-the-counter users take, often 1-3mg. But those details weren't mentioned in this article.

And this:

His terrible security practices were the worst part of that story. He stored a large amount of bitcoin on an Internet-connected server, which was hacked, losing his coins, and didn't bother to do a proper clean up. He continues to use the same server for Knots development, despite that the server may very well still be compromised, and it is hosting the Knots binaries that people are downloading and installing on their nodes! It's crazy.

The irony of the outrage train that Luke the Drama Queen started and way, way too many people jumped aboard is that they are objecting to a change that, had it been adopted much earlier, would probably have resulted in a lot less spam stuck in the permanent UTXO dataset. Had nodes advertised a higher data limit on OP_RETURN, there would have been less incentive for spammers to have gone to the effort of creating a system with which they can stuff their data into non-prunable, permanent fields. Nodes don't have to store OP_RETURN data, but they do have to store UTXOs. Now we're stuck with it, and with a system that makes it easy to keep adding more spam to the blockchain.

The whole shit show just served as an advertisement for the fact that the spammers succeeded, so now why would future ones want to use OP_RETURN, only to have their jpegs pruned off by nodes who choose to? Luke and company are continuing to incentivize the use of non-prunable UTXO space for arbitrary data. 🫠