NEW EPISODE OF nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqywhwumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wsqzq7q8pqp9qg6mz0y0keaw4u6q7fxr8pzmy3cw0hw8asx5psqxsfj9w2rsvz WITH nostr:nprofile1qyv8wumn8ghj7mn0wd68ytnvdac8qtnnda3kjctv9uqzpaegm8nwwpyrtrnsjv84efjtp9mhpkvfenvxs487vx8d48y28qgxxgzsvk JUST DROPPED.
WE DISCUSS:
- CORE VS KNOTS + SIGNAL VS NOISE
- SPAM VS FILTERS
- QUANTUM VS BITCOIN
- $5 WRENCH ATTACKS VS SOCIAL ENGINEERING
- RETARDED LEFT VS RIGHT POLITICIZATION OF BITCOIN
AND MORE
LISTEN HERE: https://www.fountain.fm/episode/F2XMl0iPF4tPxN3AEXQO
WATCH HERE: https://youtu.be/vddGaTgdLfQ
sigh. Everyone wants to focus on spam vs filters, and not choice vs no choice.
Knots lets you choose your mempool policy, regardless of its defaults.
Core (v30+) doesn't.
Run what you want, but even if Knots was permissive or ordinals by default and Core filtered them by default, and all else was equal, I'd be running Knots. As I was before Core decided to own goal.
Not your code, not your node.
Perhaps you are misinformed but there are no mempool config options that are being removed from Core.
heads-up: we looked for a lightning address on your profile but could not find one... u can get a free one at https://rizful.com ... and then reply back to this comment so we can zap you.
This appears correct -- because they never made it user configurable in the first place. I'd seen the config option proposed, but didn't realize it was never there in the first place, only that it was rejected.
So yes, my characterization of the order of events was flawed. The end result though is still that Knots provides options that Core refuses to.
OPreturn is configurable in Core. What do you believe isnt configurable?
Ahh, they haven't removed it yet -- but it's marked as deprecated, and I'm seeing that at least the suggestion of this is that it means it will be removed in the future (though of course it's code and anything can change).
The option here is datacarriersize.
