<?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: Change.org ordered to turn over IP addresses in GATE petition forgery</title>
	<atom:link href="http://www.davisenterprise.com/local-news/change-org-ordered-to-turn-over-ip-addresses-in-gate-petition-forgery/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davisenterprise.com/local-news/change-org-ordered-to-turn-over-ip-addresses-in-gate-petition-forgery/</link>
	<description>Yolo County, California</description>
	<lastBuildDate>Wed, 19 Jun 2013 05:21:36 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Bob Erwin</title>
		<link>http://www.davisenterprise.com/local-news/change-org-ordered-to-turn-over-ip-addresses-in-gate-petition-forgery/comment-page-1/#comment-402695</link>
		<dc:creator>Bob Erwin</dc:creator>
		<pubDate>Sun, 17 Mar 2013 01:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.davisenterprise.com/?p=305609#comment-402695</guid>
		<description><![CDATA[A more thorough reporter would have pointed out the fact that whoever forged the signatures used the correct email addresses of the victims, thus increasing the probability that the forgeries would be discovered. Why would that be? 

Perhaps the simplest explanation is that the perpetrator sought to discredit those who support the Davis GATE program. I wonder who that could be? I also wonder motivates such a person, certainly not the best interests of the children of Davis!

By the way, does it seem a bit odd to anyone that the PAGE petition is still online and gathering signatures despite their knowledge that the Change.org petition tool is flawed?]]></description>
		<content:encoded><![CDATA[<p>A more thorough reporter would have pointed out the fact that whoever forged the signatures used the correct email addresses of the victims, thus increasing the probability that the forgeries would be discovered. Why would that be? </p>
<p>Perhaps the simplest explanation is that the perpetrator sought to discredit those who support the Davis GATE program. I wonder who that could be? I also wonder motivates such a person, certainly not the best interests of the children of Davis!</p>
<p>By the way, does it seem a bit odd to anyone that the PAGE petition is still online and gathering signatures despite their knowledge that the Change.org petition tool is flawed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rong Liu</title>
		<link>http://www.davisenterprise.com/local-news/change-org-ordered-to-turn-over-ip-addresses-in-gate-petition-forgery/comment-page-1/#comment-402689</link>
		<dc:creator>Rong Liu</dc:creator>
		<pubDate>Sat, 16 Mar 2013 19:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.davisenterprise.com/?p=305609#comment-402689</guid>
		<description><![CDATA[The Davis Enterprise shows its bias on the issue of GATE in articles such as this one. Are Davis Enterprise readers aware that the PAGE petition also had signatures forged? This is important information that was excluded from the article -- particularly as it would indicate the perpetrator is less interested in the pros and cons of the educational issue and is more interested in simply playing mind games with the community. Also relevant is that the Enterprise trusts people to sign their web submitted comments (such as this one) and letters to the editors. My friends report that, in their experience, the Enterprise makes no effort to verify identities. I noticed in the week before this article appeared the Enterprise falsely attributed a letter to the editor to someone who complained that they had not written that letter. This seems relevant to the story above, but was also omitted. The Enterprise seems to hold a special grudge against the Excel group because they delivered comments collected via the petition to DJUSD and the school board -- but the petition was addressed to the DJUSD and so such delivery was what the petition promised to do. Meanwhile the Davis Enterprise delivers newspapers to thousands of residents with letter &quot;signed&quot; by names that may or may not be the authors.]]></description>
		<content:encoded><![CDATA[<p>The Davis Enterprise shows its bias on the issue of GATE in articles such as this one. Are Davis Enterprise readers aware that the PAGE petition also had signatures forged? This is important information that was excluded from the article &#8212; particularly as it would indicate the perpetrator is less interested in the pros and cons of the educational issue and is more interested in simply playing mind games with the community. Also relevant is that the Enterprise trusts people to sign their web submitted comments (such as this one) and letters to the editors. My friends report that, in their experience, the Enterprise makes no effort to verify identities. I noticed in the week before this article appeared the Enterprise falsely attributed a letter to the editor to someone who complained that they had not written that letter. This seems relevant to the story above, but was also omitted. The Enterprise seems to hold a special grudge against the Excel group because they delivered comments collected via the petition to DJUSD and the school board &#8212; but the petition was addressed to the DJUSD and so such delivery was what the petition promised to do. Meanwhile the Davis Enterprise delivers newspapers to thousands of residents with letter &#8220;signed&#8221; by names that may or may not be the authors.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  www.davisenterprise.com/local-news/change-org-ordered-to-turn-over-ip-addresses-in-gate-petition-forgery/feed/ ) in 0.21716 seconds, on Jun 19th, 2013 at 7:57 am PDT. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Jun 19th, 2013 at 8:57 am PDT -->