If you don't believe your opinion is better than other opinions without anyone convincing you that other opinion is better yet, than you have no opinion at all.
I've made my opinions completely clear - ordinals are spam, but we shouldn't be censoring them. Censoring transactions based on some people's opinions is what happens in fiat, not in bitcoin.
The question is, if ordinals and inscriptions in general are bringing harm to bitcoin in any way, preventing its usage as money, isn't this something worth doing something about?
Yes absolutely, but censorship is not the solution. If the bitcoin network cannot handle a small handful of users sending ordinals, how is it ever supposed to scale to a global currency? What will we do when fees are 1,000 sats/vbyte because 100 million people are using bitcoin? Censor entire countries? Or maybe censor everyone involved with political causes we don't like?
The solution is not to censor - it's to figure out how to scale better.
I don't mean a hard-fork, or a soft fork, I really don't know, but I think it worth discussing without throwing out that anything related with discussing this would be "censorship".
I don't see how you can call it anything else. There are transactions that we don't like, and we are discussing how to ban those transactions from happening.
Yes, they pay for it, as I pay for Google Drive space or iCloud... they are using my node as a cloud storage and paying for someone that's not me. It's expensive and unfair with "amateur" node runners, with their 1 TB storage and a raspberry pi.
The natural state of the bitcoin network is to have a competitive fee market with consistently full blocks. This is the only way the network will stay secure once the block subsidy is near zero. Whether those blocks are filled with regular transactions or ordinals is irrelevant to the rate of growth of the blockchain. And a quick Amazon search shows an 8TB hard drive for less than $100, which will take decades to fill.
The correction would make the node configuration be respected and not accept anything over the size you configured you want to accept.
The variable in question is placing a limit on OP_RETURN data. Ordinals do not use OP_RETURN data; they put their data within the witness.