| Login

Marc's Voice

building the open web one bit at a time

Interop of Twitter and Pownce

The conversation should not be about which is better - Twitter or Pownce and who will support who - but “how can we achieve interop BETWEEN Pownce and Twitter?”

And 100 other ‘clones’.

None of this functionality is rocket science. The challenge comes in establishing relationships ACROSS vendor’s offerings - which just happens to be the exact same challenge for connecting people between social networking systems.

Come on folks - focus on the RIGHT issues!

Date: Sunday, July 1st, 2007 | Time: 11:05 pm
Tags:
Add a comment

No Replies

  1. let a thousand flowers bloom, or something.

  2. let a thousand flowers bloom, or something.

  3. let a thousand flowers bloom, or something.

  4. Marc you’re absolutely right.

    Twitter has an excellent API, what about Pownce’s?

    Ideally, it would support the exact same API, so that software written for Twitter would work with Pownce, and vice versa.

    Mike — help us ask the question. It’s super important!

  5. Marc you’re absolutely right.

    Twitter has an excellent API, what about Pownce’s?

    Ideally, it would support the exact same API, so that software written for Twitter would work with Pownce, and vice versa.

    Mike — help us ask the question. It’s super important!

  6. Marc you’re absolutely right.

    Twitter has an excellent API, what about Pownce’s?

    Ideally, it would support the exact same API, so that software written for Twitter would work with Pownce, and vice versa.

    Mike — help us ask the question. It’s super important!

  7. they’re competitors…I wouldn’t expect them to want to work together. Nor do I think it’s a good thing in this case. Some services live, some die. Once they are fully established, then it’s time to talk interop. Like the IM networks are slowly doing now.

  8. they’re competitors…I wouldn’t expect them to want to work together. Nor do I think it’s a good thing in this case. Some services live, some die. Once they are fully established, then it’s time to talk interop. Like the IM networks are slowly doing now.

  9. they’re competitors…I wouldn’t expect them to want to work together. Nor do I think it’s a good thing in this case. Some services live, some die. Once they are fully established, then it’s time to talk interop. Like the IM networks are slowly doing now.

  10. I don’t think anyone actually wants to work together. And besides, what if someone did it better than someone else? So much for ’standards’.

    I don’t know that I want to live in a world where Toyota fuel injectors can fit onto my Mercedes engine, ya know?

    And API is great, good for Twitter, whoopee. Maybe release some new features, that’d be neat.

  11. I don’t think anyone actually wants to work together. And besides, what if someone did it better than someone else? So much for ’standards’.

    I don’t know that I want to live in a world where Toyota fuel injectors can fit onto my Mercedes engine, ya know?

    And API is great, good for Twitter, whoopee. Maybe release some new features, that’d be neat.

  12. I don’t think anyone actually wants to work together. And besides, what if someone did it better than someone else? So much for ’standards’.

    I don’t know that I want to live in a world where Toyota fuel injectors can fit onto my Mercedes engine, ya know?

    And API is great, good for Twitter, whoopee. Maybe release some new features, that’d be neat.

  13. marc

    that was exactly my thought. why do i have to join a new namespace just to try pownce? why can’t i use my twitter name. or my AIM name?

    the whole social media space is dying for interops.

    fred

  14. marc

    that was exactly my thought. why do i have to join a new namespace just to try pownce? why can’t i use my twitter name. or my AIM name?

    the whole social media space is dying for interops.

    fred

  15. marc

    that was exactly my thought. why do i have to join a new namespace just to try pownce? why can’t i use my twitter name. or my AIM name?

    the whole social media space is dying for interops.

    fred

  16. Fred, exactly — that’s what an API on Pownce would do, bridge the namespaces.

    Mike, cloning your competitor’s API is a strategy for making it easier for customers to switch.

    Microsoft used to be the master of this approach called Embrace & Extend.

  17. Fred, exactly — that’s what an API on Pownce would do, bridge the namespaces.

    Mike, cloning your competitor’s API is a strategy for making it easier for customers to switch.

    Microsoft used to be the master of this approach called Embrace & Extend.

  18. Fred, exactly — that’s what an API on Pownce would do, bridge the namespaces.

    Mike, cloning your competitor’s API is a strategy for making it easier for customers to switch.

    Microsoft used to be the master of this approach called Embrace & Extend.

  19. dan farber Jul 2nd 2007

    Human nature and the profit motive…..same old story….but as suggested bridging namespaces isn’t giving away the store

  20. dan farber Jul 2nd 2007

    Human nature and the profit motive…..same old story….but as suggested bridging namespaces isn’t giving away the store

  21. dan farber Jul 2nd 2007

    Human nature and the profit motive…..same old story….but as suggested bridging namespaces isn’t giving away the store

  22. I’ve got RSS flying around between all these services via Twitterfeed and dummy Twitter accounts. And I’ve then got Twitter tweets ending up in a Skype chat. So I’m getting all my friends updates on all the status systems ending up in one place. But that’s only a 1/3 of the battle. I also need:-

    - Update one service and have my account on the others update automatically. Tricky when so many of them are closed (see Facebook).

    - There’s no way to see a list of all my friends on all the services. And like everyone else there’s a feeding frenzy of finding the same people to add to the friend’s list on this week’s hot new system.

    If everyone has RSS out, then aggregating it all is easy. But those second two issues are hard. Not impossible, but hard.

  23. I’ve got RSS flying around between all these services via Twitterfeed and dummy Twitter accounts. And I’ve then got Twitter tweets ending up in a Skype chat. So I’m getting all my friends updates on all the status systems ending up in one place. But that’s only a 1/3 of the battle. I also need:-

    - Update one service and have my account on the others update automatically. Tricky when so many of them are closed (see Facebook).

    - There’s no way to see a list of all my friends on all the services. And like everyone else there’s a feeding frenzy of finding the same people to add to the friend’s list on this week’s hot new system.

    If everyone has RSS out, then aggregating it all is easy. But those second two issues are hard. Not impossible, but hard.

  24. I’ve got RSS flying around between all these services via Twitterfeed and dummy Twitter accounts. And I’ve then got Twitter tweets ending up in a Skype chat. So I’m getting all my friends updates on all the status systems ending up in one place. But that’s only a 1/3 of the battle. I also need:-

    - Update one service and have my account on the others update automatically. Tricky when so many of them are closed (see Facebook).

    - There’s no way to see a list of all my friends on all the services. And like everyone else there’s a feeding frenzy of finding the same people to add to the friend’s list on this week’s hot new system.

    If everyone has RSS out, then aggregating it all is easy. But those second two issues are hard. Not impossible, but hard.

  25. I spoke with Blaine from Twitter about this a bit on Friday. We’re both really interested in interoperability, and we’re architecting the Pownce API with it in mind. I’m in charge of API development, so feel free to add me on Pownce (and Twitter) if you want to stay abreast of what I’m working on. You can contact me through either of those services if you have any specific requests or suggestions.

  26. I spoke with Blaine from Twitter about this a bit on Friday. We’re both really interested in interoperability, and we’re architecting the Pownce API with it in mind. I’m in charge of API development, so feel free to add me on Pownce (and Twitter) if you want to stay abreast of what I’m working on. You can contact me through either of those services if you have any specific requests or suggestions.

  27. I spoke with Blaine from Twitter about this a bit on Friday. We’re both really interested in interoperability, and we’re architecting the Pownce API with it in mind. I’m in charge of API development, so feel free to add me on Pownce (and Twitter) if you want to stay abreast of what I’m working on. You can contact me through either of those services if you have any specific requests or suggestions.