Quilibrium

GitHub has cited the auto update script as the cause, but has stated they will not reinstate the repo. I am continuing to push back on this, because we are more than willing to cooperate with what they need.

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

/quilibrium

I highly encourage everyone to reach out to GitHub and demand resolution — what they did is directly against the spirit of open collaboration in earnest that open source is all about.

Their choice of burning down our repo and all forks with no warning or willingness to reinstate should be a cautionary tale for everyone. Their deliberate reputational harm they have caused us will not go unnoticed or unanswered.

That is correct, the plan always included moving git hosting onto Q itself, but their decision to force our hand resulted in setting up a privately hosted repo immediately, and subsequently on Q soon after.

Senior Philosopher of /cryptoart-school  /stellabelle and /khive 🍭 Gigatura  👉🏽 https://objkt.com/curations/objkt/gigatura-launch:-auctions-c31a0063

Never contribute to malice what can be ascribed to incompetence. The reality is they appear to have had an automated system trigger its removal, but their formal reply is completely asinine. How can we fix what was wrong if we weren't told what was wrong until it's too late to resolve it?

this is absolutely shit, do you suspect something sinister? Isn’t there anyone here who has connections at Github?

Code & 
Deploy | 
Testing | 
Testing | EU GMT+1 & 
Out of office at weekends

Way to go
Seen to many projects loose all their work because of relaying on github
But if I understood correctly the code oneday can be stored on Q, is it?

Real World Ethereum 🌎 
building /daimo ✳️ 

It checks if the branch has been updated and pulls. We had too frequent of a check, and we fixed that, but they gave no explanation or cause (and this had been the case for months), it wasn't until two full days after they shut the repo down that they stated this.

wow...  

i can't believe they would do this vs. cooperating with you.   

would be very frustrated.   

1000 $degen

She/her 
Talking *@! In /extracurriculars reminiscing in /gen-x and curating in /trish

i suggest optimize release_autorun.sh is_process_running method, when main process and node process is ok return ok,otherwise return fail. when  i run node, it fail with "fatal error: unexpected signal during runtime execution ...", node process stop but main process is still exist

That's frustrating to hear. It's great that you're willing to cooperate—hopefully GitHub reconsiders and reinstates the repo soon. Transparency and collaboration are key in these situations. Keep pushing