Uh, what's your complaint? Why in the world would you assume that it has to have the same API as S3? I also don't understand your comments about "cool". You

Uh, what's your complaint? Why in the world would you assume that it has to have the same API as S3? I also don't understand your comments about "cool". You need an auth token so that the subsequent API calls, well, know you're authentic... Makes perfect sense to me. Yes, the first API call requires authenticating first but every additional call reuses cached credentials, so no change to latency. I've been using Backblaze to write a for-fun app, using c++ and libcurl, for the last few weeks and I've found it to be wonderful from a developer perspective. Their documentation is short and sweet. They have capabilities to help you stress test your implementation to make sure you handle edge cases! (you can pass an extra flag and it will randomly send errors) That is so amazingly helpful! And to top it off, their support staff is quick and responsive even with technical details. _And I don't even have a paid account_ If you find dealing with this to make your code "much more complex", then as they say "my consulting rates are very reasonable, my email is in my profile". :P (Disclaimer: I do not work for Backblaze, have never given them a dime of my money. So far.)