AWS had 2023 revenue of $90.8B
Wonder how much of that was from the “Useless error messages you can’t control” product line?
https://aws.amazon.com/about-aws/whats-new/2024/05/amazon-s3-no-charge-http-error-codes/
I had a really strange experience yesterday. It’s unlikely that I’m alone in being excited to see USB-C as the sole charging standard. I really can’t wait to carry one charge block with four or so identical ports, and one set of cables that are all interchangeable.
So, I was very excited when I saw the Outdoor Technologies CHIPS 2.0 Bluetooth helmet headset. I ski a lot in the winter, and I love having a headset in my helmet. It’s also a good way to keep in touch with people. These babies also support USB-C. At $225 they’re ridiculously expensive, but so cool. They even come with a charging case. OK, sold.
I get them, and plug them into a USB-C cable I had hooked up to a charging station in my kitchen. No light. Wha’?? Tried another USB-C cable. Nothing there either. Finally looked at the cable in the box - it’s a USB-A <-> USB-C cable. Weird, I plug that in and now it charges.
Digging a bit deeper, it becomes obvious what has happened. Yes, the *plug* on these things is USB-C, but it doesn’t implement the actual power delivery objectives (PDO) negotiation of USB-C. It simply wants to draw 5v at 2a. In other words, it has a USB-C connector, but the firmware doesn’t support the USB PD standard, so it can’t use it with a USB-C source, only USB-A sources.
I really wonder where this is going. The EU has dictated that all devices must support USB-C. The question is whether this means supporting USB PD, or simply having a USB-C shaped connector? If they let manufacturers get away with the latter we won’t have the universal standard that we are looking for, but simply an even more confusing state where you can’t just look at the physical shape of the connector to determine how to use it.
If your $dayjob is at all related to security, I'd love to hear from you about what type of mobile phone you currently rely on.
I've never really seen a data-based breakdown of the answer to this question, and I'm genuinely curious. Thanks!
p.s. if you vote, please also boost this poll!
It is February 24, 2023. The WebAuthn specification was published almost exactly four years ago, and Microsoft Office 365 for Mac still is not compatible with WebAuthn.
This is fixable. All you need to do is pop the authentication dialog in the default browser rather than a WebView. The fact that Microsoft has known about this problem for half a dozen years and not bothered fixing it is really a corporate culture issue.
Cc. @ajohnsocyber