DISQUS

Scripting News: Twitter and OAuth, interesting brew (Scripting News)

  • kevinmarks · 8 months ago
    Why should the storage and the event stream come from the same provider? FB does that now for photos and videos; Twitter doesn't need to, could use Flickr/Picasa/Smugmug/twitpic and YouTube/Vimeo/blip/qik or whomever else offers the easy storage, as happens now. A Tweetree-like default UX that shows the media links better may be the answer
  • dave · 8 months ago
    Because the power comes from all apps operating on the same data set.

    Of course Twitter's data would live in this space. And it would be possible
    to hang data off their objects: tweets, users, relationships, the calendar,
    profiles, etc.

    It's the same reason apps in the Lotus space stored data in spreadsheet
    cells, and apps in the dBASE space stored them in tables.

    Twitter defines a data space. That's where developers want to work.

    Your company could blow through this one too Kevin.

    BTW, we never agree on these things, and that's okay with me. Let's try all
    approaches. I'm just a wise-ass and think I've been down this road before,
    many times. I could be wrong. If you're fairminded you have to admit that's
    possible for you too. Imho. YMMV.
  • kevinmarks · 8 months ago
    Dave, I'm arguing for the enclosure model you championed with podcasting, where the feed has an external link to the media, not including it inline like email. You seem to be arguing the opposite.
    Are you really saying we should store photos and videos and audio only in a twitter-provided silo, adn not be able to use Flickr in Twitter the way you have been doing?
  • dave · 8 months ago
    Kevin, I'm saying what I said -- not what you say I said. You even have *me*
    confused! :-)
  • kevinmarks · 8 months ago
    Clearly we're confusing each other. Why does Twitter need to compete with companies in the 'large blob of data' storage business (your point 2).
    Why not just use S3 for a general one, one of the ones I mentioned for specific ones, or something like Leah's http://baconfile.com ?
  • dave · 8 months ago
    I answered that question in reply to your first comment here. Let's not go
    round in circles. You're entitled to your opinion Kevin, and of course I am
    entitled to mine.
  • stevegillmor · 8 months ago
    of course. however I am not understanding your opinion Dave. Is it that the benefits you cite outweigh the concern others have about creating the need for large monitization models that may inhibit innovation of the type you've previously favored?
  • dave · 8 months ago
    Okay maybe I'll write more about it in the next few days.

    I don't know what conclusions you've drawn, I do know that Kevin's
    conclusions were very far from what I'm thinking of.

    You haven't given me very much to go by.

    I have written about this before, which is why I only skimmed the surface in
    this post.

    Maybe we should have a phone talk. Maybe do a podcast about this.

    Whatever...
  • stevegillmor · 8 months ago
    any and all of the above. Talk to you tomorrow.
  • Joseph Smarr · 8 months ago
    What's funny is that Facebook's proprietary delegated-auth system (fbauth) is almost identical to OAuth, so it *should* be super-trivial for them to support OAuth alongside fbauth as a way to access all of their APIs. And, IMO, it would be a great bang-for-the-buck developer and PR win for them, with no downside risk (since it's just replacing an existing component with a more standard and functionally equivalent version). Seems like some fb engineer that gets inspired should just hack this up over the weekend or something...any takers? :)
  • dave · 8 months ago
    That's good to hear. It would help simplify things for developers and give
    more choice to users.
  • fredwilson · 8 months ago
    i hope disqus is going to add twitter oath to its login options along with FB connect. i can't wait for that.
  • Jeroen de Miranda · 8 months ago
    Dave, great analogy from the PC platforms wars of the eighties (for those who were active in IT at that time, it is a superb analogy!). Makes me think of all the different flavors of UNIX, and how one had to port applications to them so that you could really earn money with those applications.