Viewing profile — mmbleh

Yeah, our traffic is more from automated systems/servers, nothing from mobile

It is because the IPv6 rollout has not been consistent. Some assign /64 per machine, some assign /64 per data center. Some even go the other way and do a /56 per machine. We've had…

Yeah, absolutely no expectations for the future. My point was more that while there may be clear benefits for users, IPv6 presents real problems for service operators with no clear…

Anonymous rate limits for us are skewed towards preventing abusive behavior. Most users do not have a problem, even there is a CGNAT on IPv4. For IPv6, if we block on /128 and a si…

IPv6 is very difficult to implement and enforce reliable rate limits on anonymous traffic. This is something we've struggled a lot with - there is no consistent implementation or s…

Maybe a different take, but as someone that manages a large public API that allows anonymous access, IPv6 has been a nightmare to try and enforce rate limits on. We've found differ…

CVE response time is a toss up, they all patch fast. Chainguard can only guarantee zero active exploits because they control their own exploit feed, and don't publish anything on i…

Yep, agree that comms have a lot of room for improvement. We do have initial delete capabilities of manifests available now, but functionality is fairly basic. It will improve over…

40/hour is higher than the current limits for authenticated free users.

(I work there) If you have a support contact or AE they can tell you if you need an official source. Marketing communications should be sent out at some point.

These platforms do cache quite a bit. It's just that there is a very high volume of traffic and a lot of it does update pretty frequently (or has to check for updates)

The storage enforcement costs have been delayed until 2026 to give time for new (automated) tooling to be created and for users to have time to adjust. The pull limits have also be…

These dates have been delayed. They will not take effect March 1. Pull limit changes are delayed at least a month, storage limit enforcement is delayed until next year.

Step one for me is just educating people on how cloud providers charge for resources. So many people don't understand everything that goes into an AWS bill. Take AWS for example - …

Interesting reaction. This could also be interpreted as making it _more_ reputable, by removing abuse and cruft, allowing engineering time to be focused on things that provide valu…

> It's the ecosystem that every contender would love to be. Trying to clarify - do you mean other JS ecosystems? Outside of JS, NPM is usually used as what not to do, not as an asp…

The article explains it a bit further - you _can_ just close the notification and skip the update as a free user. The difference being the "pro" option ignores the update completel…

If you read the blog post, anyone can dismiss the notification and skip the update. The option is about ignoring all updates for a particular update.

Kinda, but it isn't consistent. They've been steadily improving/fixing it, but for some resources, tagging new resources via the console is a 2 step process - it creates the resour…

Yup, that's exactly how I recommend clients to write lambdas for API purposes... Such a great balance of getting per request pricing while retaining all existing tooling for buildi…

Differing opinion - I think RDS Proxy is the wrong approach. Adding an additional fixed cost service to enable lambda seems like an indicator of a bad architecture. In this case th…

I wonder if as the platforms merge, if AWS will make Fargate into a Google Cloud Run competitor, or if that'd take away too much from Lambda

GCR runs containers like Fargate, but scales to zero like lambda, so you only pay for usage