<?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: Orgoo&#8217;s service down for over a month because of their user&#8217;s actions</title>
	<atom:link href="http://greenwhite.org/blog/2008/11/30/orgoos-service-down-for-over-a-month-because-of-their-users-actions/feed/" rel="self" type="application/rss+xml" />
	<link>http://greenwhite.org/blog/2008/11/30/orgoos-service-down-for-over-a-month-because-of-their-users-actions/</link>
	<description>Coffee Sessions for the Industry!</description>
	<lastBuildDate>Sat, 12 May 2012 08:39:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: KhalidM</title>
		<link>http://greenwhite.org/blog/2008/11/30/orgoos-service-down-for-over-a-month-because-of-their-users-actions/comment-page-1/#comment-61280</link>
		<dc:creator>KhalidM</dc:creator>
		<pubDate>Mon, 01 Dec 2008 07:04:14 +0000</pubDate>
		<guid isPermaLink="false">http://greenwhite.org/2008/11/30/orgoos-service-down-for-over-a-month-because-of-their-users-actions/#comment-61280</guid>
		<description>I have also had an experience like this with my hosting company. I had posted a story from Christian Science Monitor about the UN Interfaith Dialogue. CSM notified my hosting partner, not us, of a Digital Content Violation and the hosting company took my entire blog down and notified me.

Our hosting company was more interactive in that they gave us immediately access to the blog and the data to remove the information that CSM felt was a copyright breach, which I still don&#039;t believe was. Within a few hours the whole blog was back up and live.

The hosting company, by law, must give you access to the data to remove the objectionable content. If you are not willing to remove the content, then the site can be frozen indefinately. If you are willing to remove it and your hosting partner is cooperative, it can be restored immediately for the data owner to remove the information in question.

My 2 cents.</description>
		<content:encoded><![CDATA[<p>I have also had an experience like this with my hosting company. I had posted a story from Christian Science Monitor about the UN Interfaith Dialogue. CSM notified my hosting partner, not us, of a Digital Content Violation and the hosting company took my entire blog down and notified me.</p>
<p>Our hosting company was more interactive in that they gave us immediately access to the blog and the data to remove the information that CSM felt was a copyright breach, which I still don&#8217;t believe was. Within a few hours the whole blog was back up and live.</p>
<p>The hosting company, by law, must give you access to the data to remove the objectionable content. If you are not willing to remove the content, then the site can be frozen indefinately. If you are willing to remove it and your hosting partner is cooperative, it can be restored immediately for the data owner to remove the information in question.</p>
<p>My 2 cents.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

