nostr:nprofile1qqs0erxlk3srn6pwa5mfn4t0pvfg2l3cyjhztpmjucms24mmnjk03rgpp4mhxue69uhkummn9ekx7mqpzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmc3tyyv9 It is already there and it indeed is less of an issue because it requires jumping through hoops to display the data that was scrambled and hacked onto my node. Whether it truly "doesn't matter" to the law is a legal question that hasn't been tested in court, but it certainly helps that the software was not intended for this use and does nothing to facilitate it... Until v30.
My concern is that there will be fewer hoops to jump through, and that core is making it easier to store arbitrary contiguous data for no monetary reason.
nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpzdmhxw309aex2mrp0yhx5c34x5hxxmmdqyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnvv9hxgpywa92 I may be wrong, but I thought the Bitcoin core desktop software will display op return, without xor. I may be wrong. I don't have time to check right now. But either way, I think the distinction between different "one liners" is very important and should not be flippantly ignored.