@tonychang430 My contribution to the greenery π± Just applied.
Making infrastructure something coding agents can operate end to end is a problem Iβd love to help solve at InsForge.
It feels like there is a lot of things wrong with @ChatGPT these days.
- Dot feels like it's no longer using astra
- Schedule jobs are not running on time and something not running at all.
I am on 200 max plan and noticed it within the last 24 hrs.
@github My organization has been charged unnecessarily for the last few months for "GitHub Code Quality Usage."
The setting under Code Quality β Repository Access has been set to "No repository" for the last few months. As I understand it, that should fully disable Code Quality and stop any related billing, but I am still being charged.
I have opened support ticket 4808549 about this.
Is there another step required to turn it off, or is this a billing error? Also, why can't I manage this from "Budget and alerts" ?
@dabit3 tmux-web - access running tmux sessions from the browser instead of SSH-only.
https://t.co/HayO9vp0KA
Iβd use Devin Max to finish remote attach, polish the scheduler, and add a test suite around the WebSocket PTY layer
Who is designing the graphics for these posts?
The graphics are completely misleading. In general remote control these days means you can control the session from your phone (such as we have this in chatgpt/claude)
The image indicates that we can control the agy session from phone, but I checked entire article and there is nothing around remote control from phone at all. Completely useless and misleading.
@dabit3 Enhancing my existing portfolio manager trading bot. Biggest gap is reliable testing around execution, slippage, failed orders, and risk limits.
I'd use Devin + Astra to generate the test suite, reports, and monitoring so I can iterate strategies without breaking live trading.
@github A lot of the internet can host a repo. Almost nobody is giving developers this much hosted compute and repo capacity, at GitHubβs scale, for $0.
So roast the outages. And still: thank you, @github .
Everyone dunks on @github when it goes down.
Fair. Outages suck.
Also true: they still give away an absurd amount of infrastructure, at a scale almost nobody else even tries to match
@github So yes: criticize the downtime. Demand they scale. Paying customers especially get to be angry.
Just donβt pretend the free part is free.Unlimited repos + hosted multi-OS CI for public code, given away, while usage went vertical.
Roast the outages. The subsidy is still real.