Agent Builder by AirtopWeb agents that heal themselves.
Promoted
Launched this week
GitHub statistics · Velocity Radar
Real GitHub momentum, including private repos & AI agents
19 followers
Real GitHub momentum, including private repos & AI agents
19 followers
Standard GitHub profiles only count green squares. Velocity Radar measures true momentum across public and private repos without exposing private code. Features: • Pace: Compares your last 30 active days to your historical baseline. • Breakdown: Sorts commits into substantive, automated, and merges. • Stamina: Tracks unbroken runs and multi-day solid streaks. Built for high-output developers and AI agent commanders. Add a dynamic radar to your profile.
GitHub statistics · Velocity Radar
GitHub statistics · Velocity Radar
Image endpoint needs explicit Cache-Control headers with max-age=0 and no-cache. GitHub routes all profile README images through Camo proxy (camo.githubusercontent.com). If server does not tell Camo not to cache, GitHub keeps graph-arcade-light.png on edge for days. Ten-minute refresh schedule breaks silently for anyone using snippet)
GitHub statistics · Velocity Radar
@konstantin_tikhaev Good catch, thank you!
The image endpoint was setting s-maxage for our edge cache but nothing for downstream, so Camo picked its own freshness. Fixed today: graphs now send max-age=3600, so a README shows the nightly's figures within an hour. (The "ten minutes" in the guide is how often we check a username after you paste the snippet; the graph itself refreshes nightly.)
max-age=0, no-cache would also have worked, but it'd make Camo re-fetch on every README view for data that changes once a day, so I went with the hour setting.
If you encounter any anything else, good or bad, I'd love to hear it!
@paulwsave I misread the ten-minute note in the guide as graph render cadence. Since the stats only update nightly, a one-hour max-age is a better fit against Camo traffic.