I certainly think this is worth digging into, particularly if you run a node because we may have to make a decision whether we're going to go with what's happening or not. This could actually be something that causes Bitcoin core to be forked.

And at the very least, we could choose not to update nodes and advocate for the removal of the change.

To sum up what is happening... Peter Todd has made two pull requests with the same idea which is to remove the limits that nodes can set on the size of the data in op_return that lives in the mempool.  This was established in the first place as a safe place that people could put arbitrary data. So, removing it would allow people to spam at least the mempool.

But what's more interesting than the technical aspects of this are the facts that there is no consensus in the GitHub discussions and a lot of very intelligent people who are important to the Bitcoin infrastructure are objecting to this. But the core devs are saying that only they get to decide what's going to go in and this is a change from the way things have worked in the past.

That is a possibly slightly inaccurate version of what I believe is happening here. But the thing I think is important is to be aware, because this could be just as big as the block size wars, but hopefully not. Hopefully it just fizzles out somehow.