pull down to refresh

100 sats \ 6 replies \ @TheCharlatan 6h \ parent \ on: Bitcoin devs cheer block reconstruction stats, ignore security budget concerns bitcoin
Yeah, don't get me wrong, I am in favour of a future where different clients are in a mad max like standoff, constantly trying to out compete each other, optimising for different use cases and targetting different audiences. It's great to see people seriously thinking about this.
write
preview
0 sats \ 5 replies \ @optimism 6h
Yes! That would also be healthier than just all the pressure being on one repo.
reply
0 sats \ 4 replies \ @sudonaka 4h
The current core devs have only been there since about 2021 correct?
What are they responsible for in that time from the user’s perspective?
Inscriptions, forcing filter changes and now a 20% rebellion from the repo?
What is the track record that ya’ll are so eager to defend?
reply
0 sats \ 3 replies \ @optimism 4h
Here is where you can see maintainers of Core.
reply
0 sats \ 2 replies \ @sudonaka 4h
I’m asking you specifically about the chain code labs employees.
They all are paid by the same company, they work from the same office.
You have zero concerns about that?
reply
200 sats \ 1 reply \ @optimism 3h
I’m asking you specifically about the chain code labs employees.
No you didn't. Read your own comment: #1227740.
They all are paid by the same company, they work from the same office.
Naw bruh. If you would have clicked the link I gave you (I even put it on blame so you could straight move on to the commit authors for each key and not have to lookup pgp keys) and done some research you would have known the % of maintainers that work for chaincode. Takes... 20 minutes if you manually verify everything like a real Chad.
The problem isn't the funding, and you would know that if you would just do your research. Don't take my word for it! Go check it out yourself! Reach your own conclusions! Be a king in the age of retardation!
You have zero concerns about that?
I have serious concerns about the echo chamber I'm perceiving; probably more serious than you can ever imagine. And because of that, and because we know we cannot tell people what to do, I agreed with you above that it would be good to have a third fork. So who are you arguing with?
reply
0 sats \ 0 replies \ @sudonaka 3h
It was a different thread I specifically referred to the chain code employees.
Chain code seems to be the source pushing this filter drama and the apparent centralization there is a much bigger problem than default mempool policy.
I agree with you that we should have more implementations and luckily it looks like we are moving in that direction as a result of this saga.
Have a good day.
reply