While twitter integration is pretty straightforward to implement using oAuth and the twitter toolkit available on the platform, you need to think through your use case pretty clearly. Yes, twitter does support private messages, it is inherently public---by design. Chatter builds upon the existing security framework of the force.com platform to provide a private, and governable conversation.
I can certainly see a good use case to pull data into the Chatter conversation from other sources like twitter to enrich the Chatter stream, and I can see other opportunities to connect public and private conversations, but you just have to make sure you understand the implications.
Ah, you're speaking of the TwitterForce set of classes. I've been
working with these for about a week and have found a pretty major bug.
I've contacted the author (SimonF) but have yet to hear back from him. The
problem is that there is some character in the XML that causes the XML
parser to fail. I've taken a very deatiled look at the posts that cause
the failure and have yet to determine a patten.
Okay, dev community that's gotta be the first thing anyone writes! Ready... go!
:)
Garry
While twitter integration is pretty straightforward to implement using oAuth and the twitter toolkit available on the platform, you need to think through your use case pretty clearly. Yes, twitter does support private messages, it is inherently public---by design. Chatter builds upon the existing security framework of the force.com platform to provide a private, and governable conversation.
I can certainly see a good use case to pull data into the Chatter conversation from other sources like twitter to enrich the Chatter stream, and I can see other opportunities to connect public and private conversations, but you just have to make sure you understand the implications.
How do you acceess the "twitter toolkit available on the platform" that you've mentioned in this thread?
Thanks
Phillip
Ah, you're speaking of the TwitterForce set of classes. I've been working with these for about a week and have found a pretty major bug. I've contacted the author (SimonF) but have yet to hear back from him. The problem is that there is some character in the XML that causes the XML parser to fail. I've taken a very deatiled look at the posts that cause the failure and have yet to determine a patten.
Thanks,
Phillipwhat character ? or is that the problem, how to find the offending char?
can you post the xml to the chatter dev zone ?
Is the "Salesforce.com for Twitter" application going to continue to be enhanced or replaced by applications built by SFDC or Partners using Chatter?