<?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: Ow.ly and Hootsuite in widespread breach of newspaper / other site T&amp;Cs</title>
	<atom:link href="http://www.malcolmcoles.co.uk/blog/owly-hootsuite-in-widespread-breach-of-newspaper-site-tcs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.malcolmcoles.co.uk/blog/owly-hootsuite-in-widespread-breach-of-newspaper-site-tcs/</link>
	<description>Where to find Malcolm Coles, reviews, and tips on how to do things I couldn&#039;t do.</description>
	<lastBuildDate>Mon, 25 Mar 2013 16:22:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Phil</title>
		<link>http://www.malcolmcoles.co.uk/blog/owly-hootsuite-in-widespread-breach-of-newspaper-site-tcs/#comment-1672</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Thu, 26 Mar 2009 11:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=617#comment-1672</guid>
		<description>It&#039;s almost impossible to programatically interpret T&amp;C&#039;s and you can&#039;t expect these services to manually trawl through the whole of the web.

Perhaps the w3c should step in here with a recommendation for sites that don&#039;t wish to be deep linked or framed.
A simple meta tag would make it very easy for both web developers and browsers to identify such sites.</description>
		<content:encoded><![CDATA[<p>It's almost impossible to programatically interpret T&amp;C's and you can't expect these services to manually trawl through the whole of the web.</p>
<p>Perhaps the w3c should step in here with a recommendation for sites that don't wish to be deep linked or framed.<br />
A simple meta tag would make it very easy for both web developers and browsers to identify such sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Schenk</title>
		<link>http://www.malcolmcoles.co.uk/blog/owly-hootsuite-in-widespread-breach-of-newspaper-site-tcs/#comment-1662</link>
		<dc:creator>Christian Schenk</dc:creator>
		<pubDate>Thu, 26 Mar 2009 06:30:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=617#comment-1662</guid>
		<description>BTW: have you tried entering &quot;ow.ly&quot; into the input field on ow.ly? Guess what it comes up with? ;) Obviously there isn&#039;t any extra logic but just the &quot;I&#039;ll &#039;shrink&#039; whatever comes my way&quot; behaviour.</description>
		<content:encoded><![CDATA[<p>BTW: have you tried entering "ow.ly" into the input field on ow.ly? Guess what it comes up with? <img src='http://www.malcolmcoles.co.uk/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  Obviously there isn't any extra logic but just the "I'll 'shrink' whatever comes my way" behaviour.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malcolm Coles</title>
		<link>http://www.malcolmcoles.co.uk/blog/owly-hootsuite-in-widespread-breach-of-newspaper-site-tcs/#comment-1654</link>
		<dc:creator>Malcolm Coles</dc:creator>
		<pubDate>Wed, 25 Mar 2009 22:16:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=617#comment-1654</guid>
		<description>As you know, I had a good laugh at sites with T&amp;Cs &lt;a href=&quot;http://www.malcolmcoles.co.uk/blog/dont-link-to-us-part-two/&quot;&gt;forbidding linking&lt;/a&gt; - these were ridiculous, unenforcable terms.
But I think framing other people&#039;s sites is probably worse - forbidding it is a fairly standard T&amp;C on sites (so I&#039;m sure ow.ly would know about it in general), as it mucks about with sites&#039; visitor tracking etc.</description>
		<content:encoded><![CDATA[<p>As you know, I had a good laugh at sites with T&#038;Cs <a href="http://www.malcolmcoles.co.uk/blog/dont-link-to-us-part-two/">forbidding linking</a> - these were ridiculous, unenforcable terms.<br />
But I think framing other people's sites is probably worse - forbidding it is a fairly standard T&#038;C on sites (so I'm sure ow.ly would know about it in general), as it mucks about with sites' visitor tracking etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Schenk</title>
		<link>http://www.malcolmcoles.co.uk/blog/owly-hootsuite-in-widespread-breach-of-newspaper-site-tcs/#comment-1653</link>
		<dc:creator>Christian Schenk</dc:creator>
		<pubDate>Wed, 25 Mar 2009 22:05:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=617#comment-1653</guid>
		<description>Well, &quot;ow.ly is ignoring them&quot; seems to be a little over the top. They just didn&#039;t bother to read all the T&amp;Cs of those pages they&#039;re creating short links for and in turn didn&#039;t respect the &quot;unauthorised framing&quot; thing in their redirection thingy.

So, what might be a solution for this? I don&#039;t think and expect the URL shortening services to read all those (sometimes weird) T&amp;Cs. Wouldn&#039;t it just be better if you could link to where ever you want? Even frame the content if the &quot;frame&quot; isn&#039;t that disturbing?

I guess the various URL shortening services will have to obey the T&amp;Cs eventually. In the end they&#039;re creating links and should be responsible for them - if the links violate some T&amp;Cs they should be removed. This will result in a lot of &quot;overhead&quot; for ow.ly &amp; Co. ...</description>
		<content:encoded><![CDATA[<p>Well, "ow.ly is ignoring them" seems to be a little over the top. They just didn't bother to read all the T&amp;Cs of those pages they're creating short links for and in turn didn't respect the "unauthorised framing" thing in their redirection thingy.</p>
<p>So, what might be a solution for this? I don't think and expect the URL shortening services to read all those (sometimes weird) T&amp;Cs. Wouldn't it just be better if you could link to where ever you want? Even frame the content if the "frame" isn't that disturbing?</p>
<p>I guess the various URL shortening services will have to obey the T&amp;Cs eventually. In the end they're creating links and should be responsible for them - if the links violate some T&amp;Cs they should be removed. This will result in a lot of "overhead" for ow.ly &amp; Co. ...</p>
]]></content:encoded>
	</item>
</channel>
</rss>
