No problem whatsoever, on the contrary, it helps prevent mining centralization: https://njump.to/nevent1qqs8zeu9ufx8s3875rvu8w8x382jqg0at73rfhtjqw3tuwh03gyjj3gppemhxue69uhkummn9ekx7mp0qgsx9nhcswrrqg4y78tq64y90jwh99jswqkflc38kzvgczmwxmztensrqsqqqqqp0g4pud

nostr:nevent1qqsx2v69eugc9g2dejw5f2g6jpvyh2xfgmsf360tp29kp8qycy7250gppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj7qgcwaehxw309aex2mrp0yhxvmm4de6xz6tw9enx6tcxe6c03

That's missing the bigger picture. OP_RETURN was deliberately limited (80 bytes, one per tx) as a DISCOURAGEMENT mechanism for non-monetary data on the base layer. It was never meant to be a general-purpose data dumpster. By uncapping it to effectively unlimited, Core removed that discouragement...

because its a monetary timechain, not a datachain. what makes bitcoin unique is, we can run our nodes, and use them. node runners don't want to be abused as cdn server. and bitcoin is the node runners. --- at hopefully in the near future we will make bitcoin node running and storage requiremen...

The fact that something is "within consensus" doesn't mean that it can't change Bitcoin fundamentals for the worse. FAFO-ing with mempool policy can also have terrible long-term consequences just like FAFO-ing with consensus can. That's why I think that this is perhaps the most important lesson we c...