pull down to refresh

Yesterday, I had the surprise and the displeasure to see my GH account blocked from Lightning BOLTs.
No explanation. No warning. No justification. Only a github email notification.
So we have one company Block Inc, because some employees have administrative control of the Github repository can decide who is allowed and who is not allowed to contribute on Lightning….
The kind of situation to arm oneself with patience and calm.
In the meanwhile, keep building.
Fundamentally, if I’m asked about the conflict here I’ll describe in the following way.
You have 2 types of open-source developers in bitcoin open-source.
The first group, sincerely believe in bitcoin mission of censorship-resistant money, but if they have a hard choice to make, i.e between independence and a comfortable salary at the end of the month, they will always take the second alternative. Let’s not make angry the corporate hand that feed you, after all. And being your own boss or in charge, that’s very scary with all the responsibilities, you know…Typically Matt Corallo.
I would say that’s 80% of the contributors.
The second group, sincerely believe in bitcoin mission of censorship-resistant money too, but they don’t see themselves contributing on bitcoin, without sacrificing their personal independence. It’s free and open-source code but it’s also yourself staying free in the process. The folks who prefer to stay self-sovereign on the software run, on their finance and their responsibilities.
I would say that’s 20% of the contributors.
The problem is when the first group, more numerous in people, are starting to instrumentalize code of conduct and moderation rules, at the demand of their corporate backers, to push out the first group out of the bitcoin development forums.
At the end of the day, independent people, they might have their interests more aligned with the end-users, but that makes things slower as you know "we’re busy we have quarterly newsletter to write to our shareholders” so shut up !
(…I’ve enough friends who have been at Goldman Sachs to make an IPO if need…it’s not magic it’s just a lot lot of downsides…)
In my view, you should be free to work on bitcoin open-source, without having to bind the knee or ask permission to a random CEO with a flat listed company stock price or a bullshit messiah who never has contribute one line of code to bitcoin.
We reject: kings, presidents and voting. That’s the bitcoin way.
It’s a hill I have no problem to fight on as long as I’ll have to.
reply
I bet you won't get an answer. Git being moved to total Microsoft control is likely to make this kind of thing far more common.
reply
I already got an answer from Microsoft actually on this subject….
Satya won’t play his reputation for Jack.
reply
Well, you did better than I did before I got banned on the git for Quarto. (They still don't have a glossary)
reply
Matt and Steve are consistently arrogant, hostile, and on the wrong side of just about everything and have been for awhile.
At this point should assume that Jack likes it that way.
reply
I’m putting apart Steve Lee, worked professionally with him a long time, he’s different.
I’m just sad for him that he failed Bitcoin Works, his previous initiative before Spiral.
Now, he found himself stuck in a nexus of perverse incentives...
reply
Why the block?
reply
185 sats \ 1 reply \ @theariard OP 2h
I refuse to bind to LDK and Lightning completely arbitrary codes of conduct.
I started to work on rust-lightning and bitcoin core in 2018.
So before Square Crypto was a thing in 2019.
If Jake and his employes don’t change their behaviors, they will pay the price.
Met Jake Dorsey and Ray Youssef in the past, know which impressed me the most.
Like I said, I’m arming myself with calm and patience on this issue.
reply
Smart man.
reply
Hey man- it seems like you are having a tough time. I would suggest talking to a professional. You are incredibly talented and obviously something isn’t working here. Before blaming others it might be best to do some self reflection and step away from the computer.
reply
Before blaming others
"No explanation. No warning. No justification. Only a github email notification."
That's not blame. He is describing the problem. Why are you defensive about this? You seem to know something about this problem.
reply