<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: MyBlogLog API To Open The Door To Social Network Spamming?</title>
	<atom:link href="http://www.whoisandrewwee.com/social-networking/mybloglog-api-to-open-the-door-to-social-network-spamming/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.whoisandrewwee.com/social-networking/mybloglog-api-to-open-the-door-to-social-network-spamming/</link>
	<description>BizExcellerated Internet Marketing: Achieve mastery in blogging, affiliate marketing, social traffic generation at Andrew Wee</description>
	<lastBuildDate>Thu, 18 Mar 2010 00:16:44 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: SlightlyShadySEO</title>
		<link>http://www.whoisandrewwee.com/social-networking/mybloglog-api-to-open-the-door-to-social-network-spamming/comment-page-1/#comment-481878</link>
		<dc:creator>SlightlyShadySEO</dc:creator>
		<pubDate>Mon, 17 Mar 2008 18:19:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.whoisandrewwee.com/social-networking/mybloglog-api-to-open-the-door-to-social-network-spamming/#comment-481878</guid>
		<description>Well, while I see little point in targetting 1 particular person vs. just scraping for random digg profiles and such, it&#039;s going to be a difficult thing to restrict.
I would say that the best move may be to have relatively tight restriction on API key access(manual blog review perhaps) then after that have the rate limit of how much you can use it go up based on how long you&#039;ve had it. That way, abuse would be limited, or the abuser would have to be super patient.</description>
		<content:encoded><![CDATA[<p>Well, while I see little point in targetting 1 particular person vs. just scraping for random digg profiles and such, it&#8217;s going to be a difficult thing to restrict.<br />
I would say that the best move may be to have relatively tight restriction on API key access(manual blog review perhaps) then after that have the rate limit of how much you can use it go up based on how long you&#8217;ve had it. That way, abuse would be limited, or the abuser would have to be super patient.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrew wee</title>
		<link>http://www.whoisandrewwee.com/social-networking/mybloglog-api-to-open-the-door-to-social-network-spamming/comment-page-1/#comment-481802</link>
		<dc:creator>andrew wee</dc:creator>
		<pubDate>Mon, 17 Mar 2008 05:46:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.whoisandrewwee.com/social-networking/mybloglog-api-to-open-the-door-to-social-network-spamming/#comment-481802</guid>
		<description>As a web 2.0 aggregator/meta reference site, i think it&#039;s a useful resource.

It&#039;s all predicated on the members of the community knowing how to use the information responsibly - eg: following what someone is doing, rather than taking it as an easy opportunity to spam public msgs or bulletins all over their profiles.

Maybe this is an opportunity to introduce a reputation-based ranking system, so the good social guys can be differentiated from the less-than-good ones.</description>
		<content:encoded><![CDATA[<p>As a web 2.0 aggregator/meta reference site, i think it&#8217;s a useful resource.</p>
<p>It&#8217;s all predicated on the members of the community knowing how to use the information responsibly &#8211; eg: following what someone is doing, rather than taking it as an easy opportunity to spam public msgs or bulletins all over their profiles.</p>
<p>Maybe this is an opportunity to introduce a reputation-based ranking system, so the good social guys can be differentiated from the less-than-good ones.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Kennedy</title>
		<link>http://www.whoisandrewwee.com/social-networking/mybloglog-api-to-open-the-door-to-social-network-spamming/comment-page-1/#comment-481798</link>
		<dc:creator>Ian Kennedy</dc:creator>
		<pubDate>Mon, 17 Mar 2008 04:34:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.whoisandrewwee.com/social-networking/mybloglog-api-to-open-the-door-to-social-network-spamming/#comment-481798</guid>
		<description>Hi Andrew,

You bring up an interesting point. Just to be clear, MyBlogLog is bringing together pointers to your profile pages that you volunteer. We do not crawl pages looking for these services nor do we ask for or store any passwords, these pointers are public and entirely controlled by each user. 

That said, each API request including the lookup you mention is controlled via a Yahoo API key so we also have pretty fine-grained control over access to the MyBlogLog API as well should we receive complaints for a particular bad apple.

Keep the feedback coming.

Ian</description>
		<content:encoded><![CDATA[<p>Hi Andrew,</p>
<p>You bring up an interesting point. Just to be clear, MyBlogLog is bringing together pointers to your profile pages that you volunteer. We do not crawl pages looking for these services nor do we ask for or store any passwords, these pointers are public and entirely controlled by each user. </p>
<p>That said, each API request including the lookup you mention is controlled via a Yahoo API key so we also have pretty fine-grained control over access to the MyBlogLog API as well should we receive complaints for a particular bad apple.</p>
<p>Keep the feedback coming.</p>
<p>Ian</p>
]]></content:encoded>
	</item>
</channel>
</rss>
