For instance Atmos doesn't have public buckets, DNS names for buckets, named keys implemented like S3, regions, etc.
But it does have features that S3 doesn't have like byte range updates, erasure coding, etc.
2,146 karma · joined August 28, 2008
For instance Atmos doesn't have public buckets, DNS names for buckets, named keys implemented like S3, regions, etc.
But it does have features that S3 doesn't have like byte range updates, erasure coding, etc.
The overthrow of tyrannical regimes is a noble cause that a startup would almost certainly never been able to focus on as a solution to a big picture problem.
That's what App.net did --- they built out a complete product offering to only be marginally different from the alternatives.
Who does a whois lookup on domains from spam emails?
Zakaria: How worried are you that the United States is no longer going to be the place that invents the future?
Myhrvold: I'm very worried. Current course and speed --- we're very good at inventing, uh, but we're also undermining our ability to do that in lots of ways.
<facepalm>
For example the push notifications SDK from Urban Airship and app analytics SDK from Flurry depend on having credentials stored in the app.
These examples are not unique to them. I don't disagree that it's wrong, but I don't know how to work around this to be candid.
If you're using a web services API from a 3rd party that requires developer authentication keys you may be storing those keys in the code because there's not a great alternative.
No intention to misguide. I think it's completely accurate. They downloaded my app, inspected it, found AWS credentials and emailed me as a result.
That's not conjecture.
How does a browsable API work when it may need certain HTTP headers, request signatures, etc?