<?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: BeTwittered gets a new feature, and some nice changes</title>
	<atom:link href="http://32hours.com/2008/02/23/betwittered-gets-a-new-feature-and-some-nice-changes/feed/" rel="self" type="application/rss+xml" />
	<link>http://32hours.com/2008/02/23/betwittered-gets-a-new-feature-and-some-nice-changes/</link>
	<description>My journey into the software development world.</description>
	<lastBuildDate>Sat, 07 Jan 2012 13:20:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: robert</title>
		<link>http://32hours.com/2008/02/23/betwittered-gets-a-new-feature-and-some-nice-changes/comment-page-1/#comment-30</link>
		<dc:creator>robert</dc:creator>
		<pubDate>Tue, 26 Feb 2008 02:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/2008/02/23/betwittered-gets-a-new-feature-and-some-nice-changes/#comment-30</guid>
		<description>Thanks for the feedback!  I&#039;ll have a look tonight.  I think I already know what the problem is.  This should be a pretty quick fix.  I have a bit of code that is supposed to make sure long words wrap nicely.  It&#039;s probably just &quot;eating&quot; long links for lunch.  I&#039;d probably only done testing with &quot;tinyurl&quot; links, which tend to be very short.  Not sure how it went this long without me noticing it myself.
Thanks Vince!</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback!  I&#8217;ll have a look tonight.  I think I already know what the problem is.  This should be a pretty quick fix.  I have a bit of code that is supposed to make sure long words wrap nicely.  It&#8217;s probably just &#8220;eating&#8221; long links for lunch.  I&#8217;d probably only done testing with &#8220;tinyurl&#8221; links, which tend to be very short.  Not sure how it went this long without me noticing it myself.<br />
Thanks Vince!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vince</title>
		<link>http://32hours.com/2008/02/23/betwittered-gets-a-new-feature-and-some-nice-changes/comment-page-1/#comment-29</link>
		<dc:creator>Vince</dc:creator>
		<pubDate>Tue, 26 Feb 2008 00:52:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/2008/02/23/betwittered-gets-a-new-feature-and-some-nice-changes/#comment-29</guid>
		<description>When twitxr updates are posted to twitter it messes up the url by separating the last two characters for some reason....an example tweet below.

vkoser: The aforementioned new floor - photo at http://twitxr.com/vkoser/updates/73 80

for instance where the url should end in 7380.  Checking the api feed at http://twitter.com/statuses/friends_timeline.xml the url is correct and the tweet is non truncated.

Just thought I&#039;d let you know, thanks for the great widget.</description>
		<content:encoded><![CDATA[<p>When twitxr updates are posted to twitter it messes up the url by separating the last two characters for some reason&#8230;.an example tweet below.</p>
<p>vkoser: The aforementioned new floor &#8211; photo at <a href="http://twitxr.com/vkoser/updates/73" rel="nofollow">http://twitxr.com/vkoser/updates/73</a> 80</p>
<p>for instance where the url should end in 7380.  Checking the api feed at <a href="http://twitter.com/statuses/friends_timeline.xml" rel="nofollow">http://twitter.com/statuses/friends_timeline.xml</a> the url is correct and the tweet is non truncated.</p>
<p>Just thought I&#8217;d let you know, thanks for the great widget.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BeTwittered updates are live.</title>
		<link>http://32hours.com/2008/02/23/betwittered-gets-a-new-feature-and-some-nice-changes/comment-page-1/#comment-28</link>
		<dc:creator>BeTwittered updates are live.</dc:creator>
		<pubDate>Sat, 23 Feb 2008 15:37:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.32hours.com/2008/02/23/betwittered-gets-a-new-feature-and-some-nice-changes/#comment-28</guid>
		<description>[...] I got a bit of a lesson this morning.  I updated BeTwittered, and was very pleased.  Well, until I noticed that the formatting was junk.  What did I learn?  Stylesheets get cached, and pretty liberally.  So if you were using BeTwittered this morning, and it suddenly looked a bit clunky, my apologies.  One interesting thing, IE was better than Firefox in this case.  It surprised me that IE picked up the changes when I closed it and re-opened.  Firefox was VERY stubborn&#8230;  So, here&#8217;s the &#8220;official&#8221; notice. [...]</description>
		<content:encoded><![CDATA[<p>[...] I got a bit of a lesson this morning.  I updated BeTwittered, and was very pleased.  Well, until I noticed that the formatting was junk.  What did I learn?  Stylesheets get cached, and pretty liberally.  So if you were using BeTwittered this morning, and it suddenly looked a bit clunky, my apologies.  One interesting thing, IE was better than Firefox in this case.  It surprised me that IE picked up the changes when I closed it and re-opened.  Firefox was VERY stubborn&#8230;  So, here&#8217;s the &#8220;official&#8221; notice. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

