Tickets :: Comment on [#9855] Ensure Horde_Service_Twitter supports the twitter API and isn't just bound to twitter.com

* Your Email Address
* Spam protection	Enter the letters below: . , __.. ,. .. \./ (__ \./ \|\ \|\| \| .__) \| \| \\|\|___
Comment	> To answer Chuck's question first, I think that if you can support > both, then that would be good, but as long as the site knows how to > talk out to any Twitter-like API, then that would be good (for > example, posting to my SN instance when I put a new photo into Ansel). > > In response to Michael's comment: > > "FWIW, I think it makes sense to add this to Service_Twitter (though > according to the docs pointed to by the OP, there are some > differences/omissions in the API)." > > I agree. If you have any issues with the API, the various support > methods listed at http://status.net/support should be able to help > you. > > "Though unless we only want to support a single twitter-like API per > installation, this would be a bit more work, and would require the > admin to make some changes in code." > > Personally, this is where I saw it occurring - presumably, to get a > user to connect to Twitter, they click a button which says "something > something Twitter"? Could there be an equivelent which says > "Something something Social Network" and then asks for the site when > clicking on it (similar to the OpenID dialogues on sites like Stack > Overflow) - doing it this way means you can also add other Social > Networks with relative ease - Buzz, Ping, OneSocialWeb etc. > > I know I'm asking for a lot with this, and there's no way I want this > to hamper any other project work, but I'd just like to stick a line > in the sand so that it doesn't get lost at some point down the line.
Attachment
Watch this ticket

Saved Queries