<?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: $10k a week on Myspace</title>
	<atom:link href="http://seoblackhat.com/2006/07/04/10k-a-week-on-myspace/feed/" rel="self" type="application/rss+xml" />
	<link>http://seoblackhat.com/2006/07/04/10k-a-week-on-myspace/</link>
	<description>Tired of useless Top 10 Lists for ranking in Google? Looking for effective and insightful info? SEO Black Hat Blog offers articles on Blackhat SEO, Linkbait &#38; Link Spamming. And if you need to escape White Hat SEO Whiners, check out he Private Black Hat Search Engine Optimization Forum.</description>
	<lastBuildDate>Fri, 04 Feb 2011 05:07:23 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jak</title>
		<link>http://seoblackhat.com/2006/07/04/10k-a-week-on-myspace/comment-page-1/#comment-3021</link>
		<dc:creator>Jak</dc:creator>
		<pubDate>Thu, 06 Jul 2006 01:14:07 +0000</pubDate>
		<guid isPermaLink="false">http://seoblackhat.com/2006/07/04/10k-a-week-on-myspace/#comment-3021</guid>
		<description>MySpace just recently stopped the ability to have a bulletin already filled in when the user lands on the post page, which put a huge damper on trains and other ways to utilize bulletins.  Now users have to manually copy and paste the code in, which most of them haven&#039;t the slightest clue how to do.  I&#039;m guessing that this exploit was one reason for that happening.  Ahh well, it was great while it lasted. :)</description>
		<content:encoded><![CDATA[<p>MySpace just recently stopped the ability to have a bulletin already filled in when the user lands on the post page, which put a huge damper on trains and other ways to utilize bulletins.  Now users have to manually copy and paste the code in, which most of them haven&#8217;t the slightest clue how to do.  I&#8217;m guessing that this exploit was one reason for that happening.  Ahh well, it was great while it lasted. <img src='http://seoblackhat.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

