<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: No Articles Grandfathered</title>
	<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html</link>
	<description></description>
	<pubDate>Fri, 25 Jul 2008 08:55:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Christopher M. Knight</title>
		<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-11584</link>
		<pubDate>Tue, 18 Sep 2007 19:20:29 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-11584</guid>
					<description>Amy,

Thanks for the private and public feedback.

I've reviewed your account.

First, visitors every day complain about articles and every single day we evaluate and make remove/reject decisions to use the user-generated feedback to improve the quality of the site.

Second, I believe you're specific case is one that is unfair because when I reviewed your articles, if we lived in a world where every member was reasonable with their self serving links... we wouldn't have had to make a policy to draw the line in the sand on the link count for both self-serving and non-self serving....

In other words, you suffer because too many people prior to you have spammed us with endless excessive links in their articles.

Also, in your specific case, we can't easily figure out if your links are self serving or not as it appears you're trying to give resources in the form of links.

In conclusion, sorry... the reality is that we live in a world where too many authors abuse links in articles and I believe that wasn't your intent, but apologize that you're impacted by our no grandfather rule.</description>
		<content:encoded><![CDATA[<p>Amy,</p>
<p>Thanks for the private and public feedback.</p>
<p>I&#8217;ve reviewed your account.</p>
<p>First, visitors every day complain about articles and every single day we evaluate and make remove/reject decisions to use the user-generated feedback to improve the quality of the site.</p>
<p>Second, I believe you&#8217;re specific case is one that is unfair because when I reviewed your articles, if we lived in a world where every member was reasonable with their self serving links&#8230; we wouldn&#8217;t have had to make a policy to draw the line in the sand on the link count for both self-serving and non-self serving&#8230;.</p>
<p>In other words, you suffer because too many people prior to you have spammed us with endless excessive links in their articles.</p>
<p>Also, in your specific case, we can&#8217;t easily figure out if your links are self serving or not as it appears you&#8217;re trying to give resources in the form of links.</p>
<p>In conclusion, sorry&#8230; the reality is that we live in a world where too many authors abuse links in articles and I believe that wasn&#8217;t your intent, but apologize that you&#8217;re impacted by our no grandfather rule.<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Amy</title>
		<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-11583</link>
		<pubDate>Tue, 18 Sep 2007 18:52:49 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-11583</guid>
					<description>Personally, I can see this from two sides. One as a writer, the other as a publisher. As a publisher who uses this site, I want only quality articles to be there. It's a huge waste of time to go through articles that are outdated, have invalid links, or are just ads for websites dressed up as articles. That said, as someone who just updated their articles to keep them current, and got rejected, I have some other thoughts.

This is like putting a band-aid that on a wound that really needed stitches. Just because an article has extra links doesn't mean it isn't worth reading. Just because it is older, doesn't mean it isn't valid. Really, if you want better quality, doesn't that start with current article submissions? And beyond that, wouldn't a better method be to have someone go through your database and start weeding out the articles that don't meet current standards? You have to have a way to start in a certain year, and go through the older ones first.  There are tons of articles that are probably not of your current standards, but a lot of those people also wouldn't take time to follow-up years later and make sure they are still current. Why punish those of us who have? 

Just my very big $.02 - LOL. As I said, this doesn't really solve the problem, as tons of older articles that are hidden ads are still in there, still polluting the pool. Someone should be cleaning them out, or visitors should be able to rate an article to help you do your cleaning. Quality doesn't always have to do with external links. ;)</description>
		<content:encoded><![CDATA[<p>Personally, I can see this from two sides. One as a writer, the other as a publisher. As a publisher who uses this site, I want only quality articles to be there. It&#8217;s a huge waste of time to go through articles that are outdated, have invalid links, or are just ads for websites dressed up as articles. That said, as someone who just updated their articles to keep them current, and got rejected, I have some other thoughts.</p>
<p>This is like putting a band-aid that on a wound that really needed stitches. Just because an article has extra links doesn&#8217;t mean it isn&#8217;t worth reading. Just because it is older, doesn&#8217;t mean it isn&#8217;t valid. Really, if you want better quality, doesn&#8217;t that start with current article submissions? And beyond that, wouldn&#8217;t a better method be to have someone go through your database and start weeding out the articles that don&#8217;t meet current standards? You have to have a way to start in a certain year, and go through the older ones first.  There are tons of articles that are probably not of your current standards, but a lot of those people also wouldn&#8217;t take time to follow-up years later and make sure they are still current. Why punish those of us who have? </p>
<p>Just my very big $.02 - LOL. As I said, this doesn&#8217;t really solve the problem, as tons of older articles that are hidden ads are still in there, still polluting the pool. Someone should be cleaning them out, or visitors should be able to rate an article to help you do your cleaning. Quality doesn&#8217;t always have to do with external links. ;)<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lance Winslow</title>
		<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10376</link>
		<pubDate>Wed, 27 Jun 2007 00:35:08 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10376</guid>
					<description>Indeed, I had the exact same thought and even mentioned it in our Online Think Tank.</description>
		<content:encoded><![CDATA[<p>Indeed, I had the exact same thought and even mentioned it in our Online Think Tank.<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jennifer Thieme</title>
		<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10374</link>
		<pubDate>Wed, 27 Jun 2007 00:26:21 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10374</guid>
					<description>I understand the reasons for not grandfathering, but I have encountered this myself when trying to edit an older article. In all honesty it's a little frustrating. I was not changing the resource box, but editing a simple typo. The article got rejected for the word count. This was during the time when the word count went up from 200 to 250. What I learned was, &quot;Leave your older articles alone, even if they need a little work.&quot;

What I'm trying to say is that one undesired consequence of the &quot;no grandfathering&quot; rule may be that authors will become unwilling to edit older articles at all, even if it really does improve them otherwise.</description>
		<content:encoded><![CDATA[<p>I understand the reasons for not grandfathering, but I have encountered this myself when trying to edit an older article. In all honesty it&#8217;s a little frustrating. I was not changing the resource box, but editing a simple typo. The article got rejected for the word count. This was during the time when the word count went up from 200 to 250. What I learned was, &#8220;Leave your older articles alone, even if they need a little work.&#8221;</p>
<p>What I&#8217;m trying to say is that one undesired consequence of the &#8220;no grandfathering&#8221; rule may be that authors will become unwilling to edit older articles at all, even if it really does improve them otherwise.<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: KokPang Yeo</title>
		<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10296</link>
		<pubDate>Fri, 22 Jun 2007 01:49:08 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10296</guid>
					<description>Chris,

Wow! You folks are working on tracking the % and section change of an article? This is what I call quality service to the writers.

Really appreciate all the good work you and your team have done and will continue to do.


KokPang</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>Wow! You folks are working on tracking the % and section change of an article? This is what I call quality service to the writers.</p>
<p>Really appreciate all the good work you and your team have done and will continue to do.</p>
<p>KokPang<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Christopher M. Knight</title>
		<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10288</link>
		<pubDate>Thu, 21 Jun 2007 20:43:59 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10288</guid>
					<description>KokPang,

We attempt to track the history of every members interaction with the site so that we can save the day or prove what really happened when complaints come in.

In fact, one of the projects we're working on is going to alert an editor as to what percentage of an article was edited and which sections of the article was edited (title vs summary vs body vs resource box, etc).</description>
		<content:encoded><![CDATA[<p>KokPang,</p>
<p>We attempt to track the history of every members interaction with the site so that we can save the day or prove what really happened when complaints come in.</p>
<p>In fact, one of the projects we&#8217;re working on is going to alert an editor as to what percentage of an article was edited and which sections of the article was edited (title vs summary vs body vs resource box, etc).<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: KokPang Yeo</title>
		<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10265</link>
		<pubDate>Thu, 21 Jun 2007 02:07:06 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10265</guid>
					<description>Hmm...

I see no problem with what Chris and the EzineArticles staff are doing with re-submission.

A re-submission is a new application as far as I'm concerned - even if it's just a changing of a spelling of a word. I don't think EA keep a copy of the original article before the edit, do they? How are EA supposed to know what has been changed? So the solution is to treat the edited article as a new submission and assess it as such.


KokPang</description>
		<content:encoded><![CDATA[<p>Hmm&#8230;</p>
<p>I see no problem with what Chris and the EzineArticles staff are doing with re-submission.</p>
<p>A re-submission is a new application as far as I&#8217;m concerned - even if it&#8217;s just a changing of a spelling of a word. I don&#8217;t think EA keep a copy of the original article before the edit, do they? How are EA supposed to know what has been changed? So the solution is to treat the edited article as a new submission and assess it as such.</p>
<p>KokPang<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Christina Sponias</title>
		<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10230</link>
		<pubDate>Tue, 19 Jun 2007 15:36:50 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10230</guid>
					<description>Hi Chris and everyone! 
I faced the mentioned problem with my article number one, because it was not an article I wrote for the Ezine, but something I wrote to promote my first ebook only, a pure ad. However, it was accepted the first time I sent it. I was on a hurry, I didn’t read any orientation. I sent my article as if it was an ad and I forgot about it. 
Later, Chris sent me an invitation to comment his article and suddenly I woke up and understood what this Ezine was and how much I could do writing here… I started writing original articles exclusively for this Ezine. 
But some day I noticed my resource box was not as it should be because I was not sending people to my site. In the beginning I didn’t read anything about that either… So, I fixed my resource box. However, my articles had to be accepted again… and my article number one was not accepted! I had an advice telling me I could improve it, but I didn’t want to. I thought I could better write articles specifically for the Ezine from the beginning. It was a favor for me to delete that article; it didn’t fit in my article collection! I was ashamed of it, because later I understood that it was not supposed to be accepted. But I guess it was accepted because I was saying there that I’m a writer. So, the Ezine members thought that perhaps some day I could write good articles for the Ezine… what really happened when Chris showed me what I had to do here! 
This example shows us that sometimes some articles are accepted because the Ezine makes an exception for some reason, but it doesn’t mean that the first reasons that made the Ezine accept these articles can justify their acceptance later.</description>
		<content:encoded><![CDATA[<p>Hi Chris and everyone!<br />
I faced the mentioned problem with my article number one, because it was not an article I wrote for the Ezine, but something I wrote to promote my first ebook only, a pure ad. However, it was accepted the first time I sent it. I was on a hurry, I didn’t read any orientation. I sent my article as if it was an ad and I forgot about it.<br />
Later, Chris sent me an invitation to comment his article and suddenly I woke up and understood what this Ezine was and how much I could do writing here… I started writing original articles exclusively for this Ezine.<br />
But some day I noticed my resource box was not as it should be because I was not sending people to my site. In the beginning I didn’t read anything about that either… So, I fixed my resource box. However, my articles had to be accepted again… and my article number one was not accepted! I had an advice telling me I could improve it, but I didn’t want to. I thought I could better write articles specifically for the Ezine from the beginning. It was a favor for me to delete that article; it didn’t fit in my article collection! I was ashamed of it, because later I understood that it was not supposed to be accepted. But I guess it was accepted because I was saying there that I’m a writer. So, the Ezine members thought that perhaps some day I could write good articles for the Ezine… what really happened when Chris showed me what I had to do here!<br />
This example shows us that sometimes some articles are accepted because the Ezine makes an exception for some reason, but it doesn’t mean that the first reasons that made the Ezine accept these articles can justify their acceptance later.<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lance Winslow</title>
		<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10226</link>
		<pubDate>Tue, 19 Jun 2007 11:25:45 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10226</guid>
					<description>Well it give the individual a chance to pony up and use their current skill level to improve the past article right?</description>
		<content:encoded><![CDATA[<p>Well it give the individual a chance to pony up and use their current skill level to improve the past article right?<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Denis Bonneau</title>
		<link>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10224</link>
		<pubDate>Mon, 18 Jun 2007 22:46:38 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/no-articles-grandfathered.html#comment-10224</guid>
					<description>Maybe I'm shooting myself in the foot by saying this but I would rather challenge myself to keep up with a higher standard than stagnate. Having said that, if one of my articles is rejected, I would like to know why, so I don't repeat the same mistakes.

Cheers, 

D</description>
		<content:encoded><![CDATA[<p>Maybe I&#8217;m shooting myself in the foot by saying this but I would rather challenge myself to keep up with a higher standard than stagnate. Having said that, if one of my articles is rejected, I would like to know why, so I don&#8217;t repeat the same mistakes.</p>
<p>Cheers, </p>
<p>D<br />
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
