Totally agree. I have a close friend that works at AWS (although not anywhere close to s3) and this article was making the rounds internally. I know people have been upset about this, but it genuinely just sounds like one of those edge cases they overlooked until it was exposed. It sucks, but any developer has a good story of a time they’ve done it. Hopefully they get a fix out soon.
To be fair to you, I thought they were talking about AWS S3 at first and was very confused until I read the article.