this post was submitted on 14 May 2024
118 points (96.8% liked)
Programming
17349 readers
225 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In other words, a big customer finally got effected
Haven't read into this too much, but I think the affected person that made this get attention was a solo dev that was prototyping a solution for one of his customers.
And the reason he raised a stink was because he had a huge bill, as the name he chose for his bucket was by chance the same an open source project used as a sample bucket name, so whenever someone deployed it without first customising the config, it was pinging his bucket and getting a 403.
Edit: Here's his original medium post / Archive
Given the timing i suspect this was the article that drove the change. It was shared quite a bit over past few weeks.
This is why most of our thornier bugs eventually get fixed.