<?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>SplatDot.com &#187; Twitter</title>
	<atom:link href="http://splatdot.com/category/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://splatdot.com</link>
	<description>software. systems. solutions.</description>
	<lastBuildDate>Mon, 04 Apr 2011 01:12:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>The OAuthpocalypse and Keynote Tweet</title>
		<link>http://splatdot.com/the-oauthpocalypse-and-keynote-tweet/</link>
		<comments>http://splatdot.com/the-oauthpocalypse-and-keynote-tweet/#comments</comments>
		<pubDate>Mon, 13 Sep 2010 23:29:00 +0000</pubDate>
		<dc:creator>dean</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[AppleScript]]></category>
		<category><![CDATA[curl]]></category>
		<category><![CDATA[iWork]]></category>
		<category><![CDATA[Keynote]]></category>
		<category><![CDATA[Keynote Tweet]]></category>
		<category><![CDATA[keynotetweet]]></category>
		<category><![CDATA[OAuth]]></category>
		<category><![CDATA[OAuthcalypse]]></category>
		<category><![CDATA[OAuthpocalypse]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[Twitter API]]></category>

		<guid isPermaLink="false">http://splatdot.com/?p=323</guid>
		<description><![CDATA[The Twitter OAuthpocalypse arrived on September 1st. Starting on that date Twitter API clients are required to use OAuth and are no longer allowed to use basic authentication. This change broke more than a few applications that were unprepared for the change. One of those apps is Keynote Tweet. Keynote Tweet is a simple AppleScript [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://groups.google.com/group/twitter-development-talk/browse_thread/thread/c03fa2b1ae90d2a9?hl=en_US#">Twitter OAuthpocalypse</a> arrived on September 1st. Starting on that date <a href="http://dev.twitter.com/doc">Twitter API</a> clients are required to use <a href="http://oauth.net/">OAuth</a> and are no longer allowed to use <a href="http://apiwiki.twitter.com/Authentication">basic authentication</a>. This change broke more than a few applications that were unprepared for the change. One of those apps is <a href="http://code.google.com/p/keynotetweet/">Keynote Tweet</a>.</p>
<p>Keynote Tweet is a simple AppleScript utility that allows you to send tweets from your Keynote presentations. Keynote Tweet uses the <a href="http://curl.haxx.se/">curl</a> command-line utility to submit tweets to the Twitter API. Unfortunately there is no easy way to implement OAuth using the curl command-line. It also appears that it would be very difficult to implement OAuth directly in AppleScript.</p>
<p>One solution to making Keynote Tweet work again is to replace curl with <a href="http://github.com/marcel/twurl">twurl</a>. twurl is a curl-like command-line utility for the Twitter API written in <a href="http://www.ruby-lang.org/en/">Ruby</a>. twurl&#8217;s <a href="http://github.com/marcel/twurl/blob/master/INSTALL">installation</a> and <a href="http://github.com/marcel/twurl/blob/master/README">OAuth setup</a> is simple. The twurl syntax is not identical to curl&#8217;s, but it is simple to swap twurl out for curl in the Keynote Tweet AppleScript. Simply change the call to curl:</p>
<blockquote><pre>
do shell script "curl --user " &#038; twitter_login &#038; " --data-binary " &#038; twitter_status &#038; " http://twitter.com/statuses/update.json"
&nbsp;
</pre>
</blockquote>
<p>To a call to twurl:</p>
<blockquote><pre>
do shell script "twurl -d " &#038; twitter_status &#038; " /1/statuses/update.xml"
&nbsp;
</pre>
</blockquote>
<p>The keyring code in the original script is no longer necessary and can be ripped out of the script. You can download the updated script and documentation here:</p>
<blockquote><p><strong><a href="http://splatdot.com/wp-content/uploads/Keynote-Tweet-2.zip">Download Keynote Tweet 2</a><br />
&nbsp;<br />
</strong></p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://splatdot.com/the-oauthpocalypse-and-keynote-tweet/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>twitterfeed: Tweet Your RSS Feeds</title>
		<link>http://splatdot.com/twitterfeed-tweet-your-rss-feeds/</link>
		<comments>http://splatdot.com/twitterfeed-tweet-your-rss-feeds/#comments</comments>
		<pubDate>Fri, 09 Jan 2009 19:45:05 +0000</pubDate>
		<dc:creator>dean</dc:creator>
				<category><![CDATA[Twitter]]></category>
		<category><![CDATA[TwitterFeed]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[twitterfeed lets you tweet any RSS or Atom feed &#8211; a kind of RSS multicasting. Register with twitterfeed, or just login with your existing OpenID credentials, and add a feed. The main problem with using twitterfeed is that you have to trust it with your twitter credentials. I didn&#039;t see any reason not to trust [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://twitterfeed.com">twitterfeed</a> lets you <a href="http://twitter.com">tweet</a> any <a href="http://en.wikipedia.org/wiki/RSS_(file_format)">RSS</a> or <a href="http://en.wikipedia.org/wiki/Atom">Atom</a> feed &#8211; a kind of RSS multicasting. Register with twitterfeed, or just login with your existing <a href="http://openid.net">OpenID</a> credentials, and add a feed.</p>
<div style="text-align:center;"><a href="http://twitterfeed.com"><img src="http://www.splatdot.com/wp-content/uploads/twitterfeed.png" alt="twitterfeed" title="twitterfeed" width="480" height="411" class="aligncenter size-full wp-image-38" /></a></div>
<p>The main problem with using twitterfeed is that you have to trust it with your twitter credentials. I didn&#039;t see any reason not to trust it but given the recent spate of twitter hacking many people will be understandably reluctant. One option would be to set up a separate twitter account just for twitterfeed and let that account do the publishing. The drawback to that is that you would need to get your followers to follow that new account too. Hopefully twitterfeed will adopt something like <a href="http://oauth.net">OAuth</a> in the near future so they don&#039;t need your credentials. Ideally twitter will someday introduce a third party application approval mechanism similar to <a href="http://www.flickr.com/services/auth/list.gne?from=extend">the one Flickr provides</a>.</p>
<p>Once you&#039;ve decided how to handle the twitter credentials, enter the URL for any RSS or Atom feed &#8211; <code>http://www.splatdot.com/rss.xml</code> for example &#8211; and then you can control to some extent what, when and how get published from the feed.</p>
<ul>
<li><strong>Update frequency</strong> Tells twitterfeed how often to poll the RSS feed for updates &#8211; from every 30 minutes to once every 24 hours.</li>
<li><strong>Post up to</strong>: The number of new entries from the RSS feed to post. This can be set from 1 to 5. If there are more new items than that in the feed they will not be posted to twitter. Ever.</li>
<li><strong>Include&#8230;</strong>: Specify whether to include the title, the description or both.</li>
<li><strong>Include item link</strong>: Include a link to the item along with the text. I can&#039;t really think of a situation where you would not want to send the link but somebody must have or this wouldn&#039;t be an option.</li>
<li><strong>Post new items based on</strong>: Publication date or GUID.</li>
<li><strong>Prefix each tweet with</strong>: This option lets you add some static text to the beginning of each tweet. I haven&#039;t tried it but you should also be able to use this to either send the tweet with &#8220;@user&#8221; or &#8220;d user&#8221;. If you set up a second account you could have it direct tweet your main accoount with a feed you don&#039;t want your followers to see.</li>
<li><strong>Filter by keywords</strong>: If you set up filter keywords only items from the feed that match one of the keywords will be posted.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://splatdot.com/twitterfeed-tweet-your-rss-feeds/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

