<blockquote>
<p>At the time of writing, the Twitter engineers are working on an additional authentication scheme similar to Google's AuthSub or Flickr's API Authentication. This will have the added benefit of registering third-party applications to better promote them on the site. The Development Talk group will be notified when this authentication scheme is ready for testing. Note that this new authentication scheme will be optional, not mandatory, once available.</p></blockquote>

<p>From what I hear, Twitter will implement OpenID/OAuth - for which a proposal is in the works. Personally, I find this a lot more interesting than standard username/password authorization because for the user this requires a lot of trust to hand out than the other. I know they are no specifics yet, but I am asking anyway if you e.g. contacted twitter about it.</p>

<p>This aside, I like your __get() and __set() usage. Makes sense to me. <ac:emoticon ac:name="smile" /></p>

<p>It looks great <ac:emoticon ac:name="smile" />. And it's a service I'd love to see implemented.</p>

<p>On the authorisation scheme, it was confirmed in mid October as OAuth Core 1.0 using the HMAC-SHA1 method for signing messages (we have HMAC in Incubator <ac:emoticon ac:name="wink" />). They already have a Token Provider up and running, and users are able to generate unique Tokens for each application they intend authorising. So the scheme is in operation right now. I know Ed Finkler got an ASAP message for his Spaz AIR client about OAuth (haven't seen a Javascript implementation just yet).</p>

<p>I won't be implementing the Zend_Service_OAuth proposal until mid-November so I wouldn't let it hold you up - make it a future feature maybe. A Consumer is not very complex though, the main thing is that the User needs to interact with Twitter.com to give their consent in granting initial authorisation (you may smell a backend datastore). You may want to consider such a server trip (and redirect back) in terms of how a final Service component would work API wise. Some users would need it (OpenID), others might still opt for the username/password.</p>

<ac:macro ac:name="unmigrated-wiki-markup"><ac:plain-text-body><![CDATA[I have the feeling that the method names are far from being optimal. Most of them really feel like strangers. This is strange because even the API methods are not called that way. For example statusUpdate() should of course be Zend_Service_Twitter::updateStatus() etc. pp.

I wrote a service client for twitter too. What I did different was the encapsulation of the API results. In my implementation I have a client-, user-, and tweet-object. The tweet-object always contains a user (the author of the tweet). When I call getFriendsTimeline() I receive a list of tweets, each of the tweets having a user object attached (for performance reasons the client acts as a flyweight, to make sure every unique user and every unique tweet is just instanciated once). The API flow is really natural then:

$client = new TwitterClient($user, $password);
$timeline = $client->getFriendsTimeline();
foreach ($timline as $tweet) {
echo "{$tweet->getUser()>getName()} says: {$tweet>getText()}";
}

]]></ac:plain-text-body></ac:macro>

<p>Good news!</p>

<p>To update a prior comment I made - Twitter OAuth support will turn up late this year, or early next year. Definitely not on the cards in the short term, but still worth noting for when it makes an eventual second debut. Zend_Oauth should be finished and released well before that happens.</p>

<p>Look forward to seeing this in a ZF release <ac:emoticon ac:name="wink" />.</p>

<p>If you want an updated class and tests you can download it here <a href="http://code.bombdiggity.net/phly_twitter.tar.gz">http://code.bombdiggity.net/phly_twitter.tar.gz</a>. I have about 70% code coverage in the test and I hope to have more done by mid-day tomorrow. I'm also going to implement a Zend_Service_Twitter_Search so you can query the search API but that will be next week.</p>

<p>Jon, Matthew,</p>

<p>Keep me informed on further development of this component, because for my current project I need to implement the services like Twitter, Pounce, identi.ca and ping.fm.</p>

<p>I know that identi.ca is implementing the <a href="http://opendefinition.org/ossd?action=show&redirect=osd" title="Open Network Service">Open Network Service</a> and the <a href="http://openmicroblogging.org" title="The OpenMicroBlogging site">OpenMicroBlogging</a> Protocol, so I wanted to create an abstract class for these protocols and a specific component that implements it.</p>

<p>If any of you is interested, I will put the proposal online as soon as I have some decent material ready for testing.</p>

<p>What is the status of this proposal? It looks pretty complete, and people seem to be using it already. If it's ready, let's get it in to a release.</p>

<ac:macro ac:name="note"><ac:parameter ac:name="title">Zend Acceptance</ac:parameter><ac:rich-text-body>
<p>This proposal is accepted for immediate development in the standard incubator.</p>

<p>One suggestion is to have the constructor accept an array and/or Zend_Config object of arguments, to allow flexibility for additional arguments in the future.</p></ac:rich-text-body></ac:macro>