Should twitter have its own data storage?

Now that twitter OAuth feature is in public beta, some people argue that twitter should also provide a data storage facility through their API. This would allow developers to add payloads to different twitter objects but would create another information silo, instead of leveraging existing data storage providers.

I agree with Kevin Marks when he asks “Why should the storage and the event stream come from the same provider?”.

Quoting Dave Winer’s article “Twitter and OAuth, interesting brew”:

Maybe it won’t be Twitter or Facebook, but whoever builds the next consensus platform will have open data storage APIs in addition to identity. It’s a vital part of identity. We’ve been waiting too damned long for this.

Let’s see what happens.