A CLI or authenticated web endpoint requires somewhat arbitrary terminal or code access. MCP wraps the functionality in a way that doesn't require nearly the same permissions. Doesn't that enable a whole different class of users?
Interesting how much the post sounds like an AI prompt itself. Are we all going to start talking like that? Think hard, make a plan, and only reply after deep consideration.
There was a post from Github a few weeks ago showing commit volume exploded from linear to exponential growth about 6 months ago. I don't know for sure, but I think they weren't ready for the scale out. Whether that means actual scaling issues or cost cutting because of the scale out, who knows.
Feels like this is missing some of the key points of using generic bucket storage for me:
1. Archive pricing for really large old documents.
2. Cross-provider backups; especially for critical documents.
How much did they end up costing? We do a similar PCB medallion every year for another event and haven't been able to get quite that fancy due to cost. We usually only manage to get some LEDs and a processor in our lower budget range.
The total ended up being about $10/badge for 60 (5 for badge, 5 for eink), and we made the mistake of not ordering enough, so we ordered a couple more that were about $1 more expensive each. We bought all the badges from JLC and the prod files are in the repo if you want to see how much they come to in higher order quantity!
We've been doing this with simple mkdocs for ages. My experience is that rendering the markdown to feel like public docs is important for getting humans to review and take it seriously. Otherwise it goes stale as soon as one dev on the project doesn't care.
reply