CloudCamp Seattle happened last month but I recently ran across the video of the closing discussion.
Another video:
February 23, 2010
February 3, 2010
Sneak peek at Twitter's browserless OAuth credentials exchange method
Over the past couple of months the Twitter API Google Group has been overflowing with more and more disgruntled developers complaining about lack of bug fixes, slow rollout of promised features, no mobile interface for OAuth, etc. (The list goes on and on) Well I'm happy to say Twitter appears to be almost done with one much requested feature: browserless OAuth credentials exchange. It was hinted that Seesmic Look was using said exchange so today I took a peek at how Look worked behind the scenes.
To start off Look is using the standard oauth/access_token endpoint on the new https://api.twitter.com subdomain.
In addition to the standard POST headers, Look adds several values that include a username and password for the specific user.
The return value is an access_token as expected plus x_auth_expires whose meaning I can only guess at.
I didn't bother to try the exchange with my own consumer key but I would assume access is limited to specific partners for now.
As excited as I am for using browserless OAuth I'm afraid developers with be lazy and implement the credential exchange instead of the full OAuth flow even in environments well suited to jumping from application to browser.
What do you think of the credentials exchange method?
UPDATE: TweetDeck is also using the new OAuth method.
UPDATE2: The xAuth documentation is live.
To start off Look is using the standard oauth/access_token endpoint on the new https://api.twitter.com subdomain.
In addition to the standard POST headers, Look adds several values that include a username and password for the specific user.
The return value is an access_token as expected plus x_auth_expires whose meaning I can only guess at.
I didn't bother to try the exchange with my own consumer key but I would assume access is limited to specific partners for now.
As excited as I am for using browserless OAuth I'm afraid developers with be lazy and implement the credential exchange instead of the full OAuth flow even in environments well suited to jumping from application to browser.
What do you think of the credentials exchange method?
UPDATE: TweetDeck is also using the new OAuth method.
UPDATE2: The xAuth documentation is live.
January 31, 2010
Three Months of TextMate
After more then Three Months of Vim I've decided to try three months of TextMate. I had fun working with Vim and learned some nice tricks and it is time to try something new. Vim does have some deficiencies and I'm excited to compare the workflows. The biggest change will be going from a hosted style development process of SSHing into my dev box to developing everything localhost. Not only will I get rid of some lag but I'll be perfecting my deploy processes.
What are your most invaluable TextMate features or tricks?
What are your most invaluable TextMate features or tricks?
January 25, 2010
January 22, 2010
Amazon Kindle support oddness
Amazon sent me an odd email regarding the cover for my Kindle.
Dear Kindle User,
We’re sending this note to remind you about proper attachment and use of your Kindle cover and about Amazon’s Kindle warranty. You can view instructions and illustrations here:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200390460
ATTACHING THE COVER
To install the Kindle, open the cover and lay it on a flat surface. Then insert the bottom attachment hook on the cover into the bottom slot on the left edge of the Kindle. Rotate the Kindle to insert the top attachment hook. Then slide the switch down slightly to lock the cover attachment hooks in place.
Be sure to place the Kindle flat on the cover during installation. Do not tip the Kindle at an angle during installation, as that may cause the cover attachment hooks to bend.
USING THE KINDLE COVER
When using your Kindle with the cover, be careful to open the front cover only. If you open the back cover and pull the cover away from the Kindle, that may cause the attachment hooks to bend and could result in cracking or other damage to the Kindle.
THE AMAZON KINDLE WARRANTY
Your Kindle is covered by a One-Year Limited Warranty you can view here: http://www.amazon.com/kindlewarranty
If the attachment hooks on your cover have become bent, or your Kindle has developed cracking or other damage near the location where the hooks connect to the Kindle, please contact Kindle Support by phone or email regarding warranty replacement.
You can reach us via phone or e-mail through our website by clicking the Contact Us button on our help pages at http://www.amazon.com/kindlesupport or directly by calling one of these numbers:
Inside the United States: 1-866-321-8851, Outside the United States: 1-206-266-0927.
For more information, please see the Warranty Service section of the Kindle Return Policies Help page:
http://www.amazon.com/kindlereturnpolicy
Sincerely,
The Kindle Team
