I see, Thanks again for breaking down some of these arguments.

Obviously I'm not a Core developer, so I just wanted to know what's going on as I can only look at it from my own view and usage and wonder if I missed something.

Now I feel like this whole debate in nonsensical. 

 if I opened Bitcoin Core QT and on IBD a pop up asked:

"do you want mempoolfullrbf=0, or  mempoolfullrbf=1"

This would be the only way to stop hurting sensitivities. Anyone who runs CLI is going to know how to change defaults anyway.

Actually Chivo ATMs are allowing BTC to be converted to dollars; El Salvador uses the US dollar and BTC as their two official currencies.

I saw somebody make the point that miners need to align to node runners, not the other way around.

That argument is nonsense. People are fully able to run their own nodes, with their own policies. Full-RBF is in fact an example of that: I have a full-RBF peering fork of Bitcoin Core that ensures full-RBF replacements get to miners who are interested in mining them.

bitcoin

Over 70% of hash power has enabled Full-RBF; Bitcoin Core has not

petertodd

Actually Chivo ATMs are allowing BTC to be converted to dollars; El Salvador uses the US dollar and BTC as their two official currencies.

> I saw somebody make the point that miners need to align to node runners, not the other way around.

That argument is nonsense. People are fully able to run their own nodes, with their own policies. Full-RBF is in fact an example of that: I have a full-RBF peering fork of Bitcoin Core that ensures full-RBF replacements get to miners who are interested in mining them.