<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: The future of WP to Twitter</title>
	<atom:link href="http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<lastBuildDate>Tue, 07 Feb 2012 10:51:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Mildura</title>
		<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/comment-page-1/#comment-34764</link>
		<dc:creator>Mildura</dc:creator>
		<pubDate>Thu, 08 Jul 2010 12:27:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=787#comment-34764</guid>
		<description>I think OAuth would be the way to go!</description>
		<content:encoded><![CDATA[<p>I think OAuth would be the way to&nbsp;go!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Eh?</title>
		<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/comment-page-1/#comment-34687</link>
		<dc:creator>Michael Eh?</dc:creator>
		<pubDate>Tue, 29 Jun 2010 23:25:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=787#comment-34687</guid>
		<description>I find WP to Twitter one of the finest utils out there. I think that Twitter is making the change that THEY should have to give support to developers to switch over.  Besides, it&#039;s August 25th is the switch over according to Twitter API section.</description>
		<content:encoded><![CDATA[<p>I find WP to Twitter one of the finest utils out there. I think that Twitter is making the change that THEY should have to give support to developers to switch over.  Besides, it&#8217;s August 25th is the switch over according to Twitter <abbr title="Application Programming Interface">API</abbr>&nbsp;section.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/comment-page-1/#comment-34556</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Mon, 21 Jun 2010 23:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=787#comment-34556</guid>
		<description>@Daniel15 Not under the Twitter setup, without providing my own secret key in plain text -- which I&#039;m not going to do. However, there have been changes in their policies which specifically apply to open source applications which will make a significant difference. Essentially, plugins will be able to be registered as child applications of the plugin; the plugin will be registered, and instance will be registered as a child of the original. Doesn&#039;t sound simpler, but it will be much easier to work with for users.</description>
		<content:encoded><![CDATA[<p>@Daniel15 Not under the Twitter setup, without providing my own secret key in plain text&thinsp;&#8212;&thinsp;which I&#8217;m not going to do. However, there have been changes in their policies which specifically apply to open source applications which will make a significant difference. Essentially, plugins will be able to be registered as child applications of the plugin; the plugin will be registered, and instance will be registered as a child of the original. Doesn&#8217;t sound simpler, but it will be much easier to work with for&nbsp;users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel15</title>
		<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/comment-page-1/#comment-34554</link>
		<dc:creator>Daniel15</dc:creator>
		<pubDate>Mon, 21 Jun 2010 23:11:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=787#comment-34554</guid>
		<description>&quot;every one of you would have to register one application with Twitter for every site where you installed the plugin&quot;

Couldn&#039;t you use the one application across multiple sites?</description>
		<content:encoded><![CDATA[<p><span class="dquo">&#8220;</span>every one of you would have to register one application with Twitter for every site where you installed the&nbsp;plugin&#8221;</p>
<p>Couldn&#8217;t you use the one application across multiple&nbsp;sites?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gaz</title>
		<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/comment-page-1/#comment-34503</link>
		<dc:creator>Gaz</dc:creator>
		<pubDate>Wed, 16 Jun 2010 01:09:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=787#comment-34503</guid>
		<description>I hear ya Joe - I thought I was onto something with scheduled posts - setting the publishing date into the future (even just a couple of minutes) generated the short URL into the custom fields and it seemed to be going well for a few posts, then it went back into its old habits.

I stumbled across something on wp.org a hour or two ago - one of the newsletter plugins (sorry forgot which one already - will check if its valuable) had a post on their own site about scheduling issues in WP 2.9 and 2.9.2 that didn&#039;t appear in 2.8 or 2.9.1 related to the interval in wp-cron.php between checks for scheduled posts - default is 1 second, and the patch was to rejig it to 20 seconds (ah! Post Notifications plugin - check their forums under files and patches section).  

Apparently this fixed scheduled posts not being published.  The connection with previous musings about time-outs fetching the short URL or sending to twitter was what made me think of it.

In the same vein, I&#039;m also wondering if reader activity on-site, coinciding with a click to publish, could be causing a &quot;script stutter&quot; although it&#039;s generally a bit too consist for that, for the people suffering from it.

Gaz</description>
		<content:encoded><![CDATA[<p>I hear ya Joe - I thought I was onto something with scheduled posts - setting the publishing date into the future (even just a couple of minutes) generated the short <abbr title="Uniform Resource Locator">URL</abbr> into the custom fields and it seemed to be going well for a few posts, then it went back into its old&nbsp;habits.</p>
<p>I stumbled across something on wp.org a hour or two ago - one of the newsletter plugins (sorry forgot which one already - will check if its valuable) had a post on their own site about scheduling issues in WP 2.9 and 2.9.2 that didn&#8217;t appear in 2.8 or 2.9.1 related to the interval in wp-cron.php between checks for scheduled posts - default is 1 second, and the patch was to rejig it to 20 seconds (ah! Post Notifications plugin - check their forums under files and patches&nbsp;section).  </p>
<p>Apparently this fixed scheduled posts not being published.  The connection with previous musings about time-outs fetching the short <abbr title="Uniform Resource Locator">URL</abbr> or sending to twitter was what made me think of&nbsp;it.</p>
<p>In the same vein, I&#8217;m also wondering if reader activity on-site, coinciding with a click to publish, could be causing a &#8220;script stutter&#8221; although it&#8217;s generally a bit too consist for that, for the people suffering from&nbsp;it.</p>
<p>Gaz</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/comment-page-1/#comment-34502</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Tue, 15 Jun 2010 21:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=787#comment-34502</guid>
		<description>@Gaz I&#039;ve looked at it, and it&#039;s a bit puzzling. I&#039;ve been primarily focusing on one of my other plugins while waiting on Twitter, but I&#039;ll be putting some attention in on that issue soon. I just haven&#039;t found &lt;em&gt;anything&lt;/em&gt; concrete to work with yet...and I hate random bug exploration...</description>
		<content:encoded><![CDATA[<p>@Gaz I&#8217;ve looked at it, and it&#8217;s a bit puzzling. I&#8217;ve been primarily focusing on one of my other plugins while waiting on Twitter, but I&#8217;ll be putting some attention in on that issue soon. I just haven&#8217;t found <em>anything</em> concrete to work with yet&#8230;and I hate random bug&nbsp;exploration&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/comment-page-1/#comment-34500</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 15 Jun 2010 21:00:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=787#comment-34500</guid>
		<description>@Joe Dolson

Great!</description>
		<content:encoded><![CDATA[<p>@Joe&nbsp;Dolson</p>
<p>Great!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gaz</title>
		<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/comment-page-1/#comment-34499</link>
		<dc:creator>Gaz</dc:creator>
		<pubDate>Tue, 15 Jun 2010 20:59:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=787#comment-34499</guid>
		<description>Fantastic news Joe

While you&#039;re twiddling your thumbs waiting for twitter to finalise things ... any work on what&#039;s causing the shortening errors?  Any hint of it getting straightened out?  Thanks for the ability to switch the error messages off by the way - great move.

Gaz</description>
		<content:encoded><![CDATA[<p>Fantastic news&nbsp;Joe</p>
<p>While you&#8217;re twiddling your thumbs waiting for twitter to finalise things &#8230; any work on what&#8217;s causing the shortening errors?  Any hint of it getting straightened out?  Thanks for the ability to switch the error messages off by the way - great&nbsp;move.</p>
<p>Gaz</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/comment-page-1/#comment-34498</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Tue, 15 Jun 2010 20:33:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=787#comment-34498</guid>
		<description>An update: 

The authentication change is supposed to &lt;a href=&quot;http://countdowntooauth.com/&quot; rel=&quot;nofollow&quot;&gt;happen on June 30th&lt;/a&gt; -- two weeks from now. I&#039;m still waiting on making a decision about what I&#039;m going to do. The Twitter API development team has made some changes to the API implementation which significantly simplify the OAuth process for open source applications, which is fabulous news -- however, there are still some changes to be worked out. I&#039;m waiting to see what the final outcome will be, rather than find myself needing to make changes twice. 

However, what you need to know as plugin users is quite simple: I &lt;em&gt;will&lt;/em&gt; be implementing OAuth support in the plugin. There will still be some hoops for you to jump through in activating the plugin and registering it with Twitter, but nothing like what it would have been with the previous work flow.</description>
		<content:encoded><![CDATA[<p>An&nbsp;update: </p>
<p>The authentication change is supposed to <a href="http://countdowntooauth.com/" rel="nofollow">happen on June 30th</a>&thinsp;&#8212;&thinsp;two weeks from now. I&#8217;m still waiting on making a decision about what I&#8217;m going to do. The Twitter <abbr title="Application Programming Interface">API</abbr> development team has made some changes to the <abbr title="Application Programming Interface">API</abbr> implementation which significantly simplify the OAuth process for open source applications, which is fabulous news&thinsp;&#8212;&thinsp;however, there are still some changes to be worked out. I&#8217;m waiting to see what the final outcome will be, rather than find myself needing to make changes&nbsp;twice. </p>
<p>However, what you need to know as plugin users is quite simple: I <em>will</em> be implementing OAuth support in the plugin. There will still be some hoops for you to jump through in activating the plugin and registering it with Twitter, but nothing like what it would have been with the previous work&nbsp;flow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/comment-page-1/#comment-34368</link>
		<dc:creator>David</dc:creator>
		<pubDate>Wed, 02 Jun 2010 15:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=787#comment-34368</guid>
		<description>Do we know when in June this is supposed to happen?

I just tried a test post from &lt;a href=&quot;http://nomorepencils.com&quot; rel=&quot;nofollow&quot;&gt;nomorepencils&lt;/a&gt; and it worked. I have abandoned the link shortener (both bit.ly and cli.gs) because something was happening somewhere that was unpredictable, but the full link post worked today.</description>
		<content:encoded><![CDATA[<p>Do we know when in June this is supposed to&nbsp;happen?</p>
<p>I just tried a test post from <a href="http://nomorepencils.com" rel="nofollow">nomorepencils</a> and it worked. I have abandoned the link shortener (both bit.ly and cli.gs) because something was happening somewhere that was unpredictable, but the full link post worked&nbsp;today.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

