cotsuka has quit [Read error: Connection reset by peer]
cotsuka has joined #bitcoin-core-dev
bugs_ has joined #bitcoin-core-dev
dviola has quit [Ping timeout: 245 seconds]
diego has joined #bitcoin-core-dev
strat___ has quit [Changing host]
strat___ has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
bitdex has quit [Remote host closed the connection]
bitdex has joined #bitcoin-core-dev
ddebernardy has joined #bitcoin-core-dev
cotsuka has quit [Read error: Connection reset by peer]
laanwj has quit [Ping timeout: 252 seconds]
BlueMatt[m] has quit [Ping timeout: 245 seconds]
pinheadmz[m] has quit [Ping timeout: 246 seconds]
Sjors[m] has quit [Ping timeout: 246 seconds]
b10c[m] has quit [Ping timeout: 246 seconds]
stratospher[m] has quit [Ping timeout: 272 seconds]
sr_gi[m] has quit [Ping timeout: 272 seconds]
b10c has quit [Ping timeout: 245 seconds]
BlueMattTest has quit [Ping timeout: 245 seconds]
bitcoin-git has quit [Ping timeout: 246 seconds]
Murch[m] has quit [Ping timeout: 252 seconds]
BlueMattMtrxBot has quit [Ping timeout: 268 seconds]
cotsuka has joined #bitcoin-core-dev
Sjors[m] has joined #bitcoin-core-dev
pinheadmz[m] has joined #bitcoin-core-dev
BlueMatt[m] has joined #bitcoin-core-dev
b10c[m] has joined #bitcoin-core-dev
laanwj has joined #bitcoin-core-dev
bitcoin-git has joined #bitcoin-core-dev
BlueMattTest has joined #bitcoin-core-dev
stratospher[m] has joined #bitcoin-core-dev
sr_gi[m] has joined #bitcoin-core-dev
b10c has joined #bitcoin-core-dev
BlueMattMtrxBot has joined #bitcoin-core-dev
ddebernardy has quit [Ping timeout: 244 seconds]
Murch[m] has joined #bitcoin-core-dev
<BlueMatt[m]>
So GitHub has decided that LDK is permanently banned from access to CI, including self-hosted CI. All our contacts resulted in “sorry, we aren’t going to reconsider, and no we won’t tell you why, go fuck yourself”
<BlueMatt[m]>
That plus outages and the general trend of GitHub towards worse and worse features and customer service this seems like there’s more than enough reason for everyone to move off GitHub at this point.
<BlueMatt[m]>
I’d really strongly encourage folks to seriously consider one of the many pretty-much-equivalent services at this point.
<nkaretnikov>
BlueMatt[m]: what was their justification for the ban?
<BlueMatt[m]>
“ToS Violations”
<BlueMatt[m]>
I went through pretty carefully and see no reason for it under the ToS
<BlueMatt[m]>
But even Block’s corporate contract with GitHub wasn’t enough to get a real answer.
<BlueMatt[m]>
They’ve gone from responding quickly to support@github to giving no answer even to people who pay them 🤷♂️
<BlueMatt[m]>
(And somehow the violations also apply to self-hosted CI, which most of our jobs are)
<nkaretnikov>
I suggest you post on YC’s Hacker News. This usually generates enough publicity for someone to notice and respond.
<BlueMatt[m]>
Anyway, rust-bitcoin had already started migrating to a self-hosted forgejo and we likely will use the same instance
<BlueMatt[m]>
nkaretnikov: I don’t think there’s any reason to stick with GitHub at this point - they’ve gone down hill so fast over the past five years we kinda already wanted to move off.
<nkaretnikov>
then there’s no problem :)
<BlueMatt[m]>
If they can’t answer professionally without a PR crisis the idea that anyone should continue using them is absurd :)
<BlueMatt[m]>
I raise it here because the comedy of errors is probably relevant to Bitcoin core deciding whether to continue using GitHub as its primary location as well.
ddebernardy has joined #bitcoin-core-dev
<BlueMatt[m]>
Also given the level of gratuitous user bans is seems pretty bad to keep using GitHub now.
<BlueMatt[m]>
We’ve seen a lot of people try to contribute and then get their account blocked and all their PRs get immediately disappeared with no way to access them.
<BlueMatt[m]>
The ban is just the straw that made us spend the time to migrate, but with the bans we’ve seen I’m not really sure anyone should use GitHub anymore.
<BlueMatt[m]>
Anyway, opened an issue to at least discuss it more formally. I know it’s come up a few times over the years and seems like now there’s a lot more reasons to do it, if yall are ever gonna do it.
cotsuka has quit [Read error: Connection reset by peer]
cotsuka has joined #bitcoin-core-dev
luke-jr_ has quit [Quit: Konversation terminated!]
<pinheadmz>
BlueMatt[m] one thing to consider is all the github links out there already, in Dockerfiles etc. so some kind of long term support is prob still needed
<bitcoin-git>
[bitcoin] ptrinh opened pull request #35577: coins: pack cache entry flags into list pointer (master...coins-pack-cache-entry-flags) https://github.com/bitcoin/bitcoin/pull/35577
ddebernardy has quit [Ping timeout: 248 seconds]
cotsuka has quit [Read error: Connection reset by peer]
<bitcoin-git>
[bitcoin] stratospher opened pull request #35578: net: don’t self advertise tor exit node ip addresses in outbound connections (master...2026-05-self-adv-tor-exit) https://github.com/bitcoin/bitcoin/pull/35578
mudsip has joined #bitcoin-core-dev
mudsip has quit [Client Quit]
cotsuka has quit [Read error: Connection reset by peer]
cotsuka has joined #bitcoin-core-dev
<willcl-ark>
That is concerning. I have a radicle mirror of bitcoin core at https://radicle.fish.foo/ but I don't really see it as a viable alternative at this point in time... Have already been checking out sourcehut, which seems pretty awesome, but will add forgejo to that list too.
jarthur has joined #bitcoin-core-dev
ddebernardy has quit [Ping timeout: 265 seconds]
sliv3r__ has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
sliv3r__ has joined #bitcoin-core-dev
cotsuka has quit [Read error: Connection reset by peer]
cotsuka has joined #bitcoin-core-dev
ddebernardy has joined #bitcoin-core-dev
<darosior>
pinheadmz: i think any move should conserve the Github repo as a read-only mirror
rustaceanrob has quit [Ping timeout: 245 seconds]
___nick___ has quit [Ping timeout: 276 seconds]
sliv3r__ has quit [Ping timeout: 276 seconds]
sliv3r__ has joined #bitcoin-core-dev
cotsuka has quit [Read error: Connection reset by peer]