<?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>Educer &#187; wordpress</title>
	<atom:link href="http://www.educer.org/tag/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.educer.org</link>
	<description>cooler than educr</description>
	<lastBuildDate>Tue, 18 May 2010 02:57:14 +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>The (De) Construction Of Twitter</title>
		<link>http://www.educer.org/2009/12/22/the-de-construction-of-twitter/</link>
		<comments>http://www.educer.org/2009/12/22/the-de-construction-of-twitter/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 00:50:54 +0000</pubDate>
		<dc:creator>jeremy</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[pubsubhubbub]]></category>
		<category><![CDATA[rsscloud]]></category>
		<category><![CDATA[tumblr]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.educer.org/?p=182</guid>
		<description><![CDATA[$new_standard = strtolower("Twitter"); In the last couple of weeks, both WordPress and Tumblr have announced support for the Twitter API. The immediate benefits are that any forward thinking Twitter client can now also be a WordPress or Tumblr client as well. Tweetie, one of the most popular iPhone clients, has had support for this for [...]]]></description>
			<content:encoded><![CDATA[<p><code>$new_standard = strtolower("Twitter");</code></p>
<p>In the last couple of weeks, both <a href="http://en.blog.wordpress.com/2009/12/12/twitter-api/">WordPress</a> and <a href="http://staff.tumblr.com/post/287703110/api">Tumblr</a> have announced support for the <a href="http://apiwiki.twitter.com/">Twitter API</a>.</p>
<p>The immediate benefits are that any forward thinking Twitter client can now also be a WordPress or Tumblr client as well. <a href="http://www.atebits.com/tweetie-iphone/">Tweetie</a>, one of the most popular iPhone clients, has had support for this for a while and immediately became the tool of choice for testing the new features out. Choices for users expand.</p>
<p>So, with that development aside, where next? I see three things.</p>
<p>1) WordPress should publish an official plugin for <a href="http://www.wordpress.org">WordPress.org</a> that enables the Twitter API for any blog. This act alone could create millions of possible twitter servers. </p>
<p>2) WordPress/Tumblr should make a big deal about how their new changes are also already tied in with real time protocols <a href="http://rsscloud.org">RSSCloud</a> and <a href="http://code.google.com/p/pubsubhubbub/">pubsubhubbub</a>. This helps make the new twitter servers real time.</p>
<p>3) Everybody outside of Twitter should huddle for a brief second and add some new syntax to the existing twitter api that allows for a piece of metadata to be attached (urls to start), call it optional, and implement.</p>
<p>Or, in short&#8211; Now that you&#8217;ve shown how easy it is to implement Twitter&#8217;s API, rip it out of their hands, build a new community, and then market the hell out of it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.educer.org/2009/12/22/the-de-construction-of-twitter/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Godaddy Vs. WordPress 2.5.1 &#8211; htaccess</title>
		<link>http://www.educer.org/2008/05/30/godaddy-vs-wordpress-251-htaccess/</link>
		<comments>http://www.educer.org/2008/05/30/godaddy-vs-wordpress-251-htaccess/#comments</comments>
		<pubDate>Sat, 31 May 2008 00:04:10 +0000</pubDate>
		<dc:creator>jeremy</dc:creator>
				<category><![CDATA[educer]]></category>
		<category><![CDATA[godaddy]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[site]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.educer.org/?p=4</guid>
		<description><![CDATA[This is more of a reminder to myself than anything else, but WordPress was running slow as hell when I first installed it. After a couple hours and a bunch of page reloading while trying to configure everything, I ran into a 500 internal server error roadblock and couldn&#8217;t get anything to come up anymore [...]]]></description>
			<content:encoded><![CDATA[<p>This is more of a reminder to myself than anything else, but <a href="http://www.wordpress.org">WordPress</a> was running slow as hell when I first installed it.  After a couple hours and a bunch of page reloading while trying to configure everything, I ran into a <b>500 internal server error</b> roadblock and couldn&#8217;t get anything to come up anymore at all.</p>
<p>Thanks go Google, I ran into <a href="http://wordpress.org/support/topic/142309">this forum post</a> right away, from which I gathered (<i>without reading too deeply</i>)&#8211; Godaddy&#8217;s PHP5 needs to be told to use itself or something, so I added this code to the .htaccess file:</p>
<blockquote><p>AddHandler x-httpd-php5 .php<br />
AddHandler x-httpd-php .php4</p></blockquote>
<p>Seems to be working fine again, <b>and</b> it&#8217;s quick, quick, quick.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.educer.org/2008/05/30/godaddy-vs-wordpress-251-htaccess/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
