<?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"
	>
<channel>
	<title>Comments for Will Johnston | Mind Muse</title>
	<atom:link href="http://willfjohnston.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://willfjohnston.com</link>
	<description>Not just another WordPress weblog</description>
	<pubDate>Sun, 06 Jul 2008 02:27:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on Sports and Student Loans by Online Education Advisor</title>
		<link>http://willfjohnston.com/2008/07/03/sports-and-student-loans/#comment-359</link>
		<dc:creator>Online Education Advisor</dc:creator>
		<pubDate>Sat, 05 Jul 2008 02:02:25 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=52#comment-359</guid>
		<description>The projected Stafford Loan Rates can be found online at:

http://www.staffordloan.com/stafford-loan-info/interest-rates.php

It is never to late to get good news!</description>
		<content:encoded><![CDATA[<p>The projected Stafford Loan Rates can be found online at:</p>
<p><a href="http://www.staffordloan.com/stafford-loan-info/interest-rates.php" rel="nofollow">http://www.staffordloan.com/stafford-loan-info/interest-rates.php</a></p>
<p>It is never to late to get good news!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on God&#8217;s Plans by DJ</title>
		<link>http://willfjohnston.com/2008/04/02/gods-plans/#comment-355</link>
		<dc:creator>DJ</dc:creator>
		<pubDate>Fri, 04 Jul 2008 21:04:54 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/2008/04/02/32/#comment-355</guid>
		<description>HI WILL,  The church I attend is looking for a youth pastor.

We'd love to have you....it's the same denomination as the church you presently attend.

I just read the full article on your life....very interesting &#38; well written.

God Bless,
DJ</description>
		<content:encoded><![CDATA[<p>HI WILL,  The church I attend is looking for a youth pastor.</p>
<p>We&#8217;d love to have you&#8230;.it&#8217;s the same denomination as the church you presently attend.</p>
<p>I just read the full article on your life&#8230;.very interesting &amp; well written.</p>
<p>God Bless,<br />
DJ</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on twhirl Stop Working?  Here&#8217;s a Fix. by Twitter Restores API Limit to 50 Requests Per Hour &#124; Will Johnston &#124; Mind Muse</title>
		<link>http://willfjohnston.com/2008/05/26/twhirl-stop-working-heres-a-fix/#comment-280</link>
		<dc:creator>Twitter Restores API Limit to 50 Requests Per Hour &#124; Will Johnston &#124; Mind Muse</dc:creator>
		<pubDate>Tue, 10 Jun 2008 12:19:12 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=47#comment-280</guid>
		<description>[...] As you can probably tell, I was not (and am still not) very pleased with the way that Twitter decided to cope with the stress on the system.  I just shut Twitter off yesterday.  Later, the Status Blog mentioned that they had increased the request limit to 20 requests per hour, but this still wasn&#8217;t enough.  Twitter requires separate requests for messages, @ replies, and direct messages, meaning that I could still only get updates about once every 4 minutes, and I could only request @ replies and direct messages once per hour.  Remember that the original API limit was 70 requests per hour; then they dropped it to 30.  This change, done without any announcement until well after it was implemented, caused trouble for many users. [...]</description>
		<content:encoded><![CDATA[<p>[...] As you can probably tell, I was not (and am still not) very pleased with the way that Twitter decided to cope with the stress on the system.  I just shut Twitter off yesterday.  Later, the Status Blog mentioned that they had increased the request limit to 20 requests per hour, but this still wasn&#8217;t enough.  Twitter requires separate requests for messages, @ replies, and direct messages, meaning that I could still only get updates about once every 4 minutes, and I could only request @ replies and direct messages once per hour.  Remember that the original API limit was 70 requests per hour; then they dropped it to 30.  This change, done without any announcement until well after it was implemented, caused trouble for many users. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Twitter API Lowers Authenticated Request Limit to 30 Per Hour by Twitter Restores API Limit to 50 Requests Per Hour &#124; Will Johnston &#124; Mind Muse</title>
		<link>http://willfjohnston.com/2008/05/24/twitter-api-lowers-authenticated-request-limit-to-30-per-hour/#comment-279</link>
		<dc:creator>Twitter Restores API Limit to 50 Requests Per Hour &#124; Will Johnston &#124; Mind Muse</dc:creator>
		<pubDate>Tue, 10 Jun 2008 12:17:58 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=46#comment-279</guid>
		<description>[...] and direct messages once per hour.  Remember that the original API limit was 70 requests per hour; then they dropped it to 30.  This change, done without any announcement until well after it was implemented, caused trouble [...]</description>
		<content:encoded><![CDATA[<p>[...] and direct messages once per hour.  Remember that the original API limit was 70 requests per hour; then they dropped it to 30.  This change, done without any announcement until well after it was implemented, caused trouble [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Twitter API Lowers Authenticated Request Limit to 30 Per Hour by twhirl and Other Twitter Clients Exceeding Usage Limits &#124; Will Johnston &#124; Mind Muse</title>
		<link>http://willfjohnston.com/2008/05/24/twitter-api-lowers-authenticated-request-limit-to-30-per-hour/#comment-238</link>
		<dc:creator>twhirl and Other Twitter Clients Exceeding Usage Limits &#124; Will Johnston &#124; Mind Muse</dc:creator>
		<pubDate>Tue, 27 May 2008 01:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=46#comment-238</guid>
		<description>[...] Twitter&#8217;s recent change to their API means that your favorite Twitter client might not be working properly.  My (not personally verified) understanding is that the IM clients (GTalk, AIM, etc.) aren&#8217;t working at all right now, and many people have been reporting problems with twhirl.  Typically the user receives a message stating &#8220;limit exceeded&#8221; or something to that effect. [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter&#8217;s recent change to their API means that your favorite Twitter client might not be working properly.  My (not personally verified) understanding is that the IM clients (GTalk, AIM, etc.) aren&#8217;t working at all right now, and many people have been reporting problems with twhirl.  Typically the user receives a message stating &#8220;limit exceeded&#8221; or something to that effect. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Twitter API Lowers Authenticated Request Limit to 30 Per Hour by Paul Smith</title>
		<link>http://willfjohnston.com/2008/05/24/twitter-api-lowers-authenticated-request-limit-to-30-per-hour/#comment-237</link>
		<dc:creator>Paul Smith</dc:creator>
		<pubDate>Tue, 27 May 2008 00:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=46#comment-237</guid>
		<description>Thanks much for this. I was going nuts with the near constant over limit messages on Twhirl! Despite my patience being tested, I'm staying. It's worth it, overall, for the people, the connections, the new knowledge. Wish I knew coding and could help!</description>
		<content:encoded><![CDATA[<p>Thanks much for this. I was going nuts with the near constant over limit messages on Twhirl! Despite my patience being tested, I&#8217;m staying. It&#8217;s worth it, overall, for the people, the connections, the new knowledge. Wish I knew coding and could help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Embeddable Widescreen YouTube Player by YouTube e Alta Qualità: Come Inserire nel Tuo Sito i Video in Qualità Migliorata</title>
		<link>http://willfjohnston.com/2008/05/12/embed-widescreen-youtube-player/#comment-224</link>
		<dc:creator>YouTube e Alta Qualità: Come Inserire nel Tuo Sito i Video in Qualità Migliorata</dc:creator>
		<pubDate>Wed, 21 May 2008 09:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=44#comment-224</guid>
		<description>[...] spunto per scrivere questo articolo l&#8217;ho preso da un post apparso su www.Willfjohnston.com. Segnala [...]</description>
		<content:encoded><![CDATA[<p>[...] spunto per scrivere questo articolo l&#8217;ho preso da un post apparso su <a href="http://www.Willfjohnston.com" rel="nofollow">http://www.Willfjohnston.com</a>. Segnala [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Embeddable Widescreen YouTube Player by sEPH</title>
		<link>http://willfjohnston.com/2008/05/12/embed-widescreen-youtube-player/#comment-201</link>
		<dc:creator>sEPH</dc:creator>
		<pubDate>Thu, 15 May 2008 03:26:13 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=44#comment-201</guid>
		<description>coolness. thanks.</description>
		<content:encoded><![CDATA[<p>coolness. thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Embeddable Widescreen YouTube Player by Will Johnston</title>
		<link>http://willfjohnston.com/2008/05/12/embed-widescreen-youtube-player/#comment-195</link>
		<dc:creator>Will Johnston</dc:creator>
		<pubDate>Wed, 14 May 2008 03:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=44#comment-195</guid>
		<description>While I suppose the quality could be better still, if you set your profile to always play in high quality (or just click the link below the videos that have a link to a high quality version, it's actually not too bad.  This only works for new content that was uploaded at a higher resolution though.</description>
		<content:encoded><![CDATA[<p>While I suppose the quality could be better still, if you set your profile to always play in high quality (or just click the link below the videos that have a link to a high quality version, it&#8217;s actually not too bad.  This only works for new content that was uploaded at a higher resolution though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Embeddable Widescreen YouTube Player by Justin Hamilton</title>
		<link>http://willfjohnston.com/2008/05/12/embed-widescreen-youtube-player/#comment-191</link>
		<dc:creator>Justin Hamilton</dc:creator>
		<pubDate>Tue, 13 May 2008 11:51:09 +0000</pubDate>
		<guid isPermaLink="false">http://willfjohnston.com/?p=44#comment-191</guid>
		<description>now they just need to improve the quality</description>
		<content:encoded><![CDATA[<p>now they just need to improve the quality</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.413 seconds -->
