<?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: Send Me Home Like an Elephant Stone	</title>
	<atom:link href="https://www.obscuresound.com/2009/06/send-me-home-like-an-elephant-stone/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.obscuresound.com/2009/06/send-me-home-like-an-elephant-stone/</link>
	<description>Indie Music Reviews, New Tracks &#38; Albums</description>
	<lastBuildDate>Sat, 03 Oct 2009 00:17:12 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Matty		</title>
		<link>https://www.obscuresound.com/2009/06/send-me-home-like-an-elephant-stone/#comment-252705</link>

		<dc:creator><![CDATA[Matty]]></dc:creator>
		<pubDate>Sat, 20 Jun 2009 19:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://obscuresound.com/?p=3021#comment-252705</guid>

					<description><![CDATA[hmm - the code I inserted, which is showing up as LINK TEXT didn&#039;t come through. Not sure if it did in your comments view either. So just to be sure, my suggestion was to add &#039;target=_blank&quot; in the href tags on your links.

-m]]></description>
			<content:encoded><![CDATA[<p>hmm &#8211; the code I inserted, which is showing up as LINK TEXT didn&#8217;t come through. Not sure if it did in your comments view either. So just to be sure, my suggestion was to add &#8216;target=_blank&#8221; in the href tags on your links.</p>
<p>-m</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Matty		</title>
		<link>https://www.obscuresound.com/2009/06/send-me-home-like-an-elephant-stone/#comment-252703</link>

		<dc:creator><![CDATA[Matty]]></dc:creator>
		<pubDate>Sat, 20 Jun 2009 19:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://obscuresound.com/?p=3021#comment-252703</guid>

					<description><![CDATA[Thanks for the blog - I appreciate the intros to a lot of good music. Two suggestions for you however, from a fellow writer who has been reading you for about a year now. 

The first is easy:
1. Can you make it so the links open up a new tab? Use &lt;a HREF=&quot;LINK&quot; rel=&quot;nofollow&quot;&gt;LINK TEXT&lt;/A&gt;. Because many times I read while I listen and then I click a link and lose the tune...

This 2nd suggestion is probably going to get you a bit upset and most of the masses a-commenting: 
2. My vote is that you edit down your text a little. You make very few if any writing errors so I know you must be going over your posts before putting them into wordpress. But for my tiny little pea brain - many times I need less words and long drawn out sentences. I find that I mainly skim your grafs as oppose to pore over them - and you have good things to say. The question is - how to say them in the easiest-to-read-webified way? Something I too grapple with. (As you can see by the length of this 2nd suggestion.) Anyhoo - something to keep in mind as you continue to hone the craft. 

Thanks,
Matt]]></description>
			<content:encoded><![CDATA[<p>Thanks for the blog &#8211; I appreciate the intros to a lot of good music. Two suggestions for you however, from a fellow writer who has been reading you for about a year now. </p>
<p>The first is easy:<br />
1. Can you make it so the links open up a new tab? Use <a HREF="LINK" rel="nofollow">LINK TEXT</a>. Because many times I read while I listen and then I click a link and lose the tune&#8230;</p>
<p>This 2nd suggestion is probably going to get you a bit upset and most of the masses a-commenting:<br />
2. My vote is that you edit down your text a little. You make very few if any writing errors so I know you must be going over your posts before putting them into wordpress. But for my tiny little pea brain &#8211; many times I need less words and long drawn out sentences. I find that I mainly skim your grafs as oppose to pore over them &#8211; and you have good things to say. The question is &#8211; how to say them in the easiest-to-read-webified way? Something I too grapple with. (As you can see by the length of this 2nd suggestion.) Anyhoo &#8211; something to keep in mind as you continue to hone the craft. </p>
<p>Thanks,<br />
Matt</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
