461–470 of 1001 posts
I encourage everyone to switch to Forgejo. We ditched GitHub and could not be happier. The experience is smoother, faster and distraction-free. Our runners are faster, our CI is smoother than ever. Transitioning was a matter of a few hours, which we took as a fun hackaton.
Earlier quoted context omitted.
blacksmith.sh just raised tens of millions on the core premise that self-hosting CI/CD is hard [0]. they've had multiple outages in the last week, so i guess they are proving themselves correct. in practice, giving ssh/sudo to AI (codex) and telling it to setup ephemeral self-hosted runners on your own host VM (qemu), takes about 30 minutes and works extremely well. it bangs out all the shell scripts. moved my own bu…
They run on top of GH, so if GH goes down, so does Blacksmith, every time
GitHub, Charles Schwab, Microsoft Teams, Copilot, New York State, AWS, Progressive, Azure, Microsoft Store, Cloudflare, ADP, Google Sheets, E-Trade, Fidelity... Did Mythos break out of it's container? https://downdetector.com/
This is starting to feel like Twitter. For a variety of reasons, we had a centralized place where everyone of a particular set of persuasions could connect, and this had outsize benefits for the community as a whole. That place is becoming untenable, and with the loss of goodwill and stability, the community’s started to dissipate. But there isn’t one obvious transition candidate, so the diaspora is finding itself sp…
I think that, exactly how 95% of the people that left Twitter eventually returned, we will see a similar outflux of people from Github and the vast majority of them will quietly be back in a few months.
I wonder if you could replace the whole github issues feature with just a directory within each git repo named "Issues/". Within that, have another couple directories, "open/", and "closed/". Within "open", have a directory per issue, e.g. "such-and-such-does-not-work/". Within each issue directory, have "issue.txt", or "issue.md", which takes the place of the page for each issue on github. You could store other thin…
Did Anthropic or OpenAI fail to sandbox their models again?
> Error: Response status code does not indicate success: 429 (Too Many Requests).
> Warning: Back off 19.714 seconds before retry.
> Warning: Failed to download action 'https://codeload.github.com/'.
> Error: Response status code does not indicate success: 502 (Bad Gateway).
> Warning: Back off 22.228 seconds before retry.
> Error: Response status code does not indicate success: 429 (Too Many Requests).
> Error: Failed to download archive 'https://codeload.github.com/' after 3 attempts.
Nice - even their own action runners are getting rate limited atm
Can anyone shed some light why GitHub is having so many problems lately?
Copy/paste of a comment I posted a couple months ago: I am not trying to make any excuses for GitHub, however I recall one tweet that made my eyes bug-out: > Yup, platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.) > GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week i…