nostr:nprofile1qqs0w2xeumnsfq6cuuynpaw2vjcfwacdnzwvmp59flnp3mdfez3czpsprpmhxue69uhkummnw3ezumr0wpczuum0vd5kzmp0ksxxx2 from a purely selfish point of view, is it better or worse for me as a pleb node runner to have to store more arbitrary data on my node. I just can’t see how it’s better for me. It definitely feels worse that the option to filter has been removed.
Discussion
From a resources standpoint you're basically talking about the block size limit, which remains unchanged. With regard to OP_RETURN data like what's currently being discussed, it actually imposes less resource costs upon your node in terms of CPU usage, bandwidth usage, and hard disk usage.
That's because OP_RETURN data does not receive a discount like witness data.
This only works if you also filter out non-OP_RETURN arbitrary data, which you are against, ya jackass.
I have higher data carrier limits than typical, at 160, because that's what I reasoned was the best policy. 83 bytes might actually be better as it is the standing tradition, and projects can optimize for that. Either way, I DON'T GET TO DICTATE THE SETTING FOR OTHER PEOPLE. So the fact that most people relay only up to 83 bytes or less, is a check against my assessment that 160 bytes is fine.
This is all besides the fact that your stated goals regarding miner centralization, like many other BS arguments you and your team put out, are a lie, as these goals would be better served by (A) engaging in an intellectually honest way and (B) embracing DATUM and advocating the use of or creation of competitors to OCEAN.
I would not ask Jameson LARP for insight into my concerns, personally. His entire persona is a facade.
Your Casa Nodes were complete crap.
You are not an Authority on Nodes, or over them.
