<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Standards, Accessibility &#38; More &#187; meetup</title>
	<atom:link href="http://weboverhauls.com/dennislembree/blog/tag/meetup/feed/" rel="self" type="application/rss+xml" />
	<link>http://weboverhauls.com/dennislembree/blog</link>
	<description>Personal blog of Dennis E. Lembrée, web site professional</description>
	<lastBuildDate>Wed, 25 Aug 2010 02:21:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>twitterapi Meetup at Twitter HQ</title>
		<link>http://weboverhauls.com/dennislembree/blog/2010/03/03/twitterapi-meetup-at-twitter-hq/</link>
		<comments>http://weboverhauls.com/dennislembree/blog/2010/03/03/twitterapi-meetup-at-twitter-hq/#comments</comments>
		<pubDate>Wed, 03 Mar 2010 17:14:02 +0000</pubDate>
		<dc:creator>Dennis</dc:creator>
				<category><![CDATA[Twitter]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[event]]></category>
		<category><![CDATA[meetup]]></category>

		<guid isPermaLink="false">http://weboverhauls.com/dennislembree/blog/?p=901</guid>
		<description><![CDATA[A couple nights ago, I attended a @twitterapi meetup at the Twitter HQ in downtown San Francisco. It was pretty cool just being there, and great to get updated on the Twitter API while also doing a little networking. It was pretty informal as expected which was good. The Twitter guys basically opened up the [...]]]></description>
			<content:encoded><![CDATA[<p>A couple nights ago, I attended a <a href="http://twitterapi-meetup.eventbrite.com/">@twitterapi meetup</a> at the Twitter HQ in downtown San Francisco. It was pretty cool just being there, and great to get updated on the Twitter API while also doing a little networking. It was pretty informal as expected which was good. The Twitter guys basically opened up the floor for questions and comments on the Twitter API. They said &#8220;in order for us to succeed, you [the 3rd party developers] need to succeed&#8221;. Beer and pizza was served which was cool, and not surprising since there were about 3 women scattered in a sea of 25- to 40 year-old men! There was approximately 150 people in attendance.</p>
<p>Here are some takeaways from the discussion:</p>
<ul>
<li>Basic Authentication to be deprecated as soon as June 2010, just a few months away! In favor of <a href="http://apiwiki.twitter.com/OAuth-FAQ">Open Auth</a>.</li>
<li>For non-web clients, xauth is suggested for authentication. You may email &#8220;api AT twitter DOT com&#8221; to request access.</li>
<li>A few asked, but they didn&#8217;t respond to questions about advertising.</li>
<li>An address book API is coming soon.</li>
<li>They plan on using the HTML5 Geolocation feature.</li>
<li>Enhancing functionality for Favorites in the API is on the list, but not a priority.</li>
<li>The word &#8220;Tweet&#8221; is OK to use in an application name as long as the app is solely a Twitter app (does not include other social networking functionality).</li>
<li>Follow the Twitter API at <a href="http://twitter.com/twitterapi">@twitterapi</a></li>
</ul>
<p><img title="Twitter API Meetup, 2010 Mar 1" src="http://weboverhauls.com/dennislembree/blog/wp-content/uploads/2010/03/twitter-api-meetup-3463301-1937.jpg" alt="candid shot of numerous male developers sitting in large open room" width="550" height="336" /></p>
]]></content:encoded>
			<wfw:commentRss>http://weboverhauls.com/dennislembree/blog/2010/03/03/twitterapi-meetup-at-twitter-hq/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
