926 sats \ 6 replies \ @benthecarman 21 Feb 2023
Core devs dropping like flies...
reply
6 sats \ 5 replies \ @moel 22 Feb 2023
I wonder if the pressure of litigation is one of his reasons?
reply
5 sats \ 4 replies \ @benthecarman 22 Feb 2023
That's exactly it
reply
0 sats \ 3 replies \ @sancristrader 22 Feb 2023
This is the litigation background.
I wonder if it is possible to organize and fundraise among the whales for a defense campaign, that would not only end this but punish this vexatious litigant.
reply
38 sats \ 0 replies \ @jonatack 22 Feb 2023
There is a Bitcoin Legal Defense Fund (thank goodness).
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019741.html
reply
21 sats \ 1 reply \ @felix 23 Feb 2023
At this point, i honestly believe Craig Wright is simply a CIA op...
reply
0 sats \ 0 replies \ @RdioActiv 25 Feb 2023
100% being paid by the elites.
reply
192 sats \ 5 replies \ @TonyGiorgio 21 Feb 2023
Has he spoken about taking a step back before? Just curious if it's been known publicly. All the respect to the hard work he's put in.
reply
739 sats \ 4 replies \ @Murch OP 21 Feb 2023
There is a thread on Twitter, but his account is protected.
reply
0 sats \ 1 reply \ @jonatack 22 Feb 2023
FWIW many developers now are making their GitHub profile private and Twitter account protected.
reply
0 sats \ 0 replies \ @l0k18 23 Feb 2023
We pulled our activity off github and have greatly reduced our activity on twitter, pretty much SN, keet, and my colleague still doomscrolls a bit but part of our specific reason for doing it is that once we have a live production mainnet for Indra that's where we are gonna live online. Also don't want to get so much attention at this point things are not finished.
reply
0 sats \ 1 reply \ @TonyGiorgio 21 Feb 2023
Ah okay can't read it.
reply
711 sats \ 0 replies \ @Murch OP 21 Feb 2023
He basically just said it’s time for him to transition out of the role, thanked his sponsors, and said that he’s at least around until the summer when his grant expires. He did not make a statement about whether he was planning to contribute in the future beyond the period of his grant.
reply
13 sats \ 3 replies \ @mf 21 Feb 2023
I appreciate him. On the other hand, slowing down develkpment is not necessarely a bad thing.
More will come if the value is returned.
reply
12 sats \ 2 replies \ @jonatack 22 Feb 2023
Fewer contributors means less reviewing and testing, fewer eyes on the code to catch issues.
Slowing down bug fixes and regular maintenance isn't necessarily a good thing.
Development isn't just about new features, or even mainly about that.
reply
10 sats \ 1 reply \ @mf 22 Feb 2023
I agree. The points don't negate eachother.
This also made me think about conteibuting with code reviewing. You see, for each action there's also a reaction 😁
reply
0 sats \ 0 replies \ @jonatack 23 Feb 2023
Doing review and testing would be great. Marco was a very prolific reviewer.
reply
3 sats \ 0 replies \ @WeAreAllSatoshi 21 Feb 2023
So according to the WSJ shitrag, Bitcoin is now controlled by 5 engineers? Lol what morons they are
reply
3 sats \ 0 replies \ @Busybe3z 21 Feb 2023
We hibernate in bear market, and stampede in a bull… to be expected, slowing down is wise in these times! Especially with regulations coming in
reply
10 sats \ 0 replies \ @faithandcredit 22 Feb 2023
Same thing happened with Satoshi the guy who originally created bitcoin. He just stopped one day.
reply
1 sat \ 0 replies \ @etmorale3 22 Feb 2023 freebie
I hope it's a about perspectives. Who knows?
0 sats \ 2 replies \ @Entrep 22 Feb 2023
Where can one learn to be a bitcoin core dev?
reply
1274 sats \ 1 reply \ @Murch OP 22 Feb 2023
I would suggest to take a look at Jon Atack’s articles about contributing to Bitcoin Core, check out the Bitcoin Protocol Development Seminar by Chaincode Labs (disclosure: I work at Chaincode) or browse our self-paced seminar, swing by the Bitcoin Core PR Review Club, or dive right in with a Good First Issue.
reply
0 sats \ 0 replies \ @ursuscamp 23 Feb 2023
This one comment is a great resource, thank you.
reply