3 ms·
Excellent feature, long overdue! I hope that this also means we're going to see the end of what I can only describe as "hellban limits" where support/documentat
by lvh 7y ago
Excellent feature, long overdue! I hope that this also means we're going to see the end of what I can only describe as "hellban limits" where support/documentation insists the limit is n while you're being clearly throttled at m<n and the way to resolve that is escalation to the team itself.
We ran into this, for example, with AWS Organizations, where we were allegedly bumped to like, 32, but as soon as we hit 20 or so newly created accounts had all services disabled including S3 and EC2.
- derefr 7y agoA systems-level confusion between 32 and 20 sounds like operator error during input—32 being 0x20 hexadecimal. Maybe they thought the field’s value was hex when it wasn’t?
- lvh 7y agoI think we’ve seen it in different services and different orgs and at different sizes, but I guess it’s hard to set up an experiment :)