Quilibrium

PSA: Github has disabled the node client repository due to alleged TOS violation. We are aware and working to get it restored/contest the violation, along with setting up a secondary repository outside of GH control. If you are experiencing issues with the node client and are up to date (1.4.18-p2) please stand by.

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

app.intersend.io | sequence. pimlico. poap. polygon. consensys. paxful. flipside crypto. dash. bridgewater. darpa. secdef. navy. dia | linktr.ee/alexanderchopan

https://github.com/quilibriumnetwork/ceremonyclient

wen u r not busy dealing w this can u share a link to more context?

Stuck at the crossroads of crypto and AI. 
The Crossroads: axilo.substack.com

Founder - angel investor - convergence maxi

I wish I could, they've given none. I have a few theories but without clarification from GH support it's purely theory. That being said, we announced a follow up PSA about an hour later: we have a public repository on internal infrastructure now, immune from this nonsense. We'll keep it alive even if GitHub resolves.

Could you provide more details as to why exactly?

ack!
(standing by, good luck Cassie...what BS!)

family dude & toucher of grass 🌄
learning to build. elevate others. enjoyoor of OG FC moments./purple 🟣#127. base64.tech 
 

ugghh, probably annoying AF but sounds like Q is hittin' on the message 😏

add to list: GH clone on Q ; )

Time to switch to ipfs or arweave
Or even better: develop a git clone for both of them
Great work btw
Tos violation means you are hitting the right buttons of mainstream censorship

sorry to hear, someone was saying microsoft hadn't ruined github yet.

they have. we just don't' know

sorry to hear, someone was saying microsoft hadn't ruined github yet.

they have. we just don't' know

https://about.gitea.com/

so no rush to update from 1.4.18-p1 then ?

Thanks for the update. Hoping the TOS issue gets resolved soon. We'll wait for news on restoring the main repository and setting up the backup.

Good luck in solving this ! Do you think it s because too many nodes update at the same time ? Which look like ddos github from github point f view