---
title: "Should twitter have its own data storage?"
date: 2009-04-21
description: "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 …"
---

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

I agree with Kevin Marks when [he asks][5] "Why should the storage and the event stream come from the same provider?".

Quoting Dave Winer's article "[Twitter and OAuth, interesting brew][6]":

> 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.

 [1]: http://oauth.net/ "OAuth"
 [2]: http://apiwiki.twitter.com/OAuth-FAQ
 [3]: http://apiwiki.twitter.com/
 [4]: http://en.wikipedia.org/wiki/Information_silo
 [5]: http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8462416
 [6]: http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#disqus_thread