vinnymac

Oddly not much to trip it. I once ran “touch AKAMAI.md” and then had Claude run git status and it fell back to Opus as if I had just broken into the pentagon itself.

I tried to use this the other day and found out they still don’t support arm64 :(

Somehow ECS does though… tradeoffs everywhere I look have made me dizzy.

I find this recommendation funny, because I completely agree from a sysadmin perspective.

I used to use Gitlab at work, and small teams would run into so many footguns with CI that we had to throw up guardrails to prevent mistakes. Far too many links to gitlab issues that were not fixed even after >8+ years of being open ended up biting us. With GHA I haven't had that experience, and same for all of my self hosted Forgejo instances. I used to hate using GHA from about ~2018 to 2021, but they've fixed a lot of things I disliked since then.

If you're actively considering self hosting, I recommend giving forgejo a try. The experience is much more similar to what GitHub offers, actions API is nearly identical to name one similarity of which there are many. Moving essentially becomes one prompt and a coffee later for a small team.

Just to be clear, I am on Github Enterprise, and am also experiencing this disruption both privately and publicly on every org and project I have access to.

For me this started happening when I type "stat" too.

Which surprised me because of the many hundreds of services I rely on regularly that also have status pages.

As someone who notices a lot of things, I was talking recently with someone who notices almost nothing. When I spoke about my desire to seek out the truth, they simply replied, "I just want to live a happy life."

There’s a perception that those who seek knowledge and truth are somehow less happy. Ignorance, and the willingness to take the path of least resistance, can be seen as an advantage for those who would rather not look too closely. Fundamentally, perhaps the difference comes down to red pill versus blue pill, and the illusions we’re willing to accept.

Thanks to you I’ve now upgraded to v16, and can confirm the logs API works beautifully!

Nice! I was hoping they would add this in v16. Unfortunately I am still on v15 of all my instances of Forgejo

If you know GitHub actions then you’ll immediately understand Forgejo actions. It was designed that way intentionally. There are some differences, but at least for me not enough to warrant any pitchforks.

If you have advanced use cases you might be more frustrated, but I’m not aware of any off the top of my head. I think my biggest complaint is that they haven’t exposed action logs over the API, so I can’t build tooling around them at the CLI level, feed them to an LLM, or more quickly diagnose problems that arise without using the website.

Same, I have gotten good results out of Opus 4.6,4.7,4.8 for my security work though. So I continue to use them for this.

Curious if you’ve find yourself enjoying DS or Kimi more than Opus 4?

I once described Mythos and then Fable as escaping the box we put them in. This would certainly fit that narrative.

> For a long time they would have global outages where the status page would list everything as green and the only reason you'd know something was wrong was the forum threads. Their response was that they were too busy fixing the issues to update the status board. Right.

Are you talking about AWS or Fly here? I seriously cannot tell.