<?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: The Problem with Frame-Wrapping URL Shorteners</title>
	<atom:link href="http://www.zmogo.com/web/frame-wrapping-url-shorteners-bad-for-site-owners/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zmogo.com/web/frame-wrapping-url-shorteners-bad-for-site-owners/</link>
	<description>Information about New and Popular Gadgets</description>
	<lastBuildDate>Sat, 13 Mar 2010 02:32:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Curious</title>
		<link>http://www.zmogo.com/web/frame-wrapping-url-shorteners-bad-for-site-owners/comment-page-1/#comment-1877</link>
		<dc:creator>Curious</dc:creator>
		<pubDate>Mon, 13 Apr 2009 22:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.zmogo.com/?p=3028#comment-1877</guid>
		<description>&gt; Because digg.comÃ¢â‚¬â„¢s URL shortener always wraps your site in a digg.com frame, it always appears that it is digg.com requesting your site.

Is this really the case?  Your browser is still loading the content in the iframe with a direct HTTP call, I&#039;d think digg.com would always be the REFERRER but not the request source.

It would still muck up your analytics though, the whole thing is an obnoxious move on the part of Digg.com.</description>
		<content:encoded><![CDATA[<p>&gt; Because digg.comÃ¢â‚¬â„¢s URL shortener always wraps your site in a digg.com frame, it always appears that it is digg.com requesting your site.</p>
<p>Is this really the case?  Your browser is still loading the content in the iframe with a direct HTTP call, I&#8217;d think digg.com would always be the REFERRER but not the request source.</p>
<p>It would still muck up your analytics though, the whole thing is an obnoxious move on the part of Digg.com.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
