Looks like @schmidty's PR to undeprecate datacarriersize was merged to master this evening.
pull down to refresh
31 sats \ 0 replies \ @LibreHans 1 Oct
They are in full damage control mode. Anyway, it's too late for me, the more I looked into how the decision for op_return was made, the less I could trust core devs, I'll never go back.
reply
0 sats \ 2 replies \ @0xbitcoiner 1 Oct
Common sense won in the end. For me, it would've been total loss of faith in the core devs if they didn’t roll back that decision.
reply
0 sats \ 1 reply \ @alice_bob 1 Oct
It is not common sense, it is simply to obey who pays, same as before.
Even the one who pays exonerates from the consequences of not obeying, as if it were necessary....curious.
Disclaimer: I am the executive director of Brink, an organization that funds some Bitcoin Core developers, some of which may review this PR. I have emailed them separately letting them know that any review feedback here (positive or critical) will not impact their standing, funding, or employment with Brink. Independent review and open discussion are critical for Bitcoin Core, and Ive encouraged them to engage as they would with any other contributor.
reply
0 sats \ 0 replies \ @0xbitcoiner 1 Oct
Yeah, I saw that. Not sure if that was the main reason though, a lot of people in the Bitcoin community pushed back hard on that decision. Maybe all the criticism finally made them see the light.
reply
0 sats \ 0 replies \ @alice_bob 1 Oct
Too late, Core has kicked the hornet’s nest, and the swarm is headed towards them.
reply
0 sats \ 0 replies \ @SimpleStacker 1 Oct
‼️
reply