mmbleh

7 ms·

1.
by mmbleh 5mo ago
Yeah, our traffic is more from automated systems/servers, nothing from mobile
2.
by mmbleh 5mo ago
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 to build up a list of overrides to do s
3.
by mmbleh 5mo ago
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 solutions in sight. Given that GitHub also offers free serv
4.
by mmbleh 5mo ago
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 single machine gets /64, a malicious user has near
5.
by mmbleh 5mo ago
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 standard when it comes to assigning of IPv6 addresses. s
6.
by mmbleh 9mo ago
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 different ISPs assign IPv6 addresses differently - some give
7.
by mmbleh 9mo ago
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 it until they've patched. So while this makes it lo
8.
by mmbleh 2y ago
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 time, along with automated policies.
9.
by mmbleh 2y ago
40/hour is higher than the current limits for authenticated free users.
10.
by mmbleh 2y ago
(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.
11.
by mmbleh 2y ago
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)
12.
by mmbleh 2y ago
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 been delayed at least a month.
13.
by mmbleh 2y ago
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.
14.
We apologize. We did a terrible job announcing the end of Docker Free Teams(docker.com)
592 points by mmbleh 4y ago|307 comments
15.
by mmbleh 4y ago
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 - everyone seems to account for lambda runtime cost, but
16.
by mmbleh 5y ago
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 value to end users.
17.
by mmbleh 5y ago
> 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 aspiration.
18.
by mmbleh 5y ago
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 completely versus it popping back up periodically.
19.
by mmbleh 5y ago
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.
20.
Architectures for Mitigating AWS Outages(forelse.io)
58 points by mmbleh 6y ago|16 comments
21.
by mmbleh 6y ago
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 resource THEN adds the tags. They are fixing these
22.
by mmbleh 6y ago
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 building APIs
23.
by mmbleh 6y ago
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 the better approach would likely be to just use a Fargate cont
24.
by mmbleh 7y ago
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
25.
by mmbleh 7y ago
GCR runs containers like Fargate, but scales to zero like lambda, so you only pay for usage
26.
by mmbleh 7y ago
https://twitter.com/_msw_/status/1201924979647905792
27.
by mmbleh 9y ago
Google Wave came out a few years too early...
28.
by mmbleh 10y ago
The original comment was hasty, I admit. But there are a lot of ways to tackle these issues. Radar clutter, attenuation, penetration, etc are all affected by wavelengths. By using multiple frequencies, you can get a better idea of what is a
29.
by mmbleh 10y ago
From the "How it works" Google self driving car page: "Sensors Lasers, radars and cameras detect objects in all directions" It uses many kinds of sensors. Yes I know about clutter, I've spent quite a lot of time in
30.
by mmbleh 10y ago
The sensors are primarily radar based. Mud/snow won't really affect them.

More ›