<?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: What WordPress should Do ?</title>
	<atom:link href="http://sparun.in/what-wordpress-should-do/feed/" rel="self" type="application/rss+xml" />
	<link>http://sparun.in/what-wordpress-should-do/</link>
	<description>WordPress, Windows and the Web.</description>
	<lastBuildDate>Fri, 18 Jun 2010 04:08:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1-alpha</generator>
	<item>
		<title>By: An Apology &#124; S . P . A r u n . I n</title>
		<link>http://sparun.in/what-wordpress-should-do/#comment-416</link>
		<dc:creator>An Apology &#124; S . P . A r u n . I n</dc:creator>
		<pubDate>Wed, 16 Sep 2009 07:00:19 +0000</pubDate>
		<guid isPermaLink="false">http://sparun.in/?p=113#comment-416</guid>
		<description>[...] yesterday, i write a post about What wordpress should do . I was attempting to make some points regarding WordPress , but obviously did so in a very poor [...]</description>
		<content:encoded><![CDATA[<p>[...] yesterday, i write a post about What wordpress should do . I was attempting to make some points regarding WordPress , but obviously did so in a very poor [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Kingsley Clark</title>
		<link>http://sparun.in/what-wordpress-should-do/#comment-411</link>
		<dc:creator>Scott Kingsley Clark</dc:creator>
		<pubDate>Tue, 15 Sep 2009 23:34:57 +0000</pubDate>
		<guid isPermaLink="false">http://sparun.in/?p=113#comment-411</guid>
		<description>I&#039;ll do my best to address my concerns with this post as legibly as possible so that you understand it.

1. Don&#039;t CAPITALIZE every other word to give context, we can read your words just fine. Capitalizing them makes you seem like you are yelling, or being very aggressive. Both of which, no one reacts well to.

2. WordPress is, and has always been secure to the best of the developer team&#039;s abilities. If a security vulnerability is found, the WordPress Core Dev team fixes it. So being afraid that WordPress isn&#039;t taking security seriously doesn&#039;t seem to make sense. They have had a long preexisting trend since the beginning in releasing updates and fixes for any security threat that was found.

3. WordPress is infinitely customizable if you&#039;ve got the right knowledge under your belt. You don&#039;t need to go into the Core to change things, that&#039;s what plugins are for. Why are you against using plugins? WordPress is constantly evolving, if the need for a feature to disable post revisions is necessary for the majority of the community, then it&#039;s built in. For everything else, there&#039;s the plugin realm of WordPress. You can do just about anything with a plugin, and that along with Theming, is what makes WordPress a solid choice for running a site on it.

4. It&#039;s not WordPress&#039; responsibility to chase down every host on the planet and get them to support WordPress auto upgrades. I guarantee you that there&#039;s hundreds more hosts not listed here that already support WordPress automatic upgrades and they don&#039;t even know it. There are already 93 hosts (and counting) that are listed on the WP.org site as confirmed. That list already includes all the big hosting companies here in the US (and across the world), so it&#039;s up to the host (or hosting client) themselves to test for this and be listed here. Also, nothing is stopping you from simply uploading WP through FTP if you want to upgrade and are unable to use the Automatic Upgrade.

5. Search Google for &quot;wp-hackers&quot; and you&#039;ll find the mailing list that you can probably ask some more of your questions more directly than the forums.

WordPress isn&#039;t as flawed as you may think, you&#039;ve just got to take the time to understand it and learn from the information out there. The same applies to many other complex content management systems, there are high barriers to entry for anyone who wants to do something but doesn&#039;t know how. Trial and error is your best bet.
.-= Scott Kingsley Clark´s last blog ..&lt;a href=&quot;http://www.scottkclark.com/rt-rocketgenius-gravity-form/&quot; rel=&quot;nofollow&quot;&gt;RT @rocketgenius: Gravity Form…&lt;/a&gt; =-.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll do my best to address my concerns with this post as legibly as possible so that you understand it.</p>
<p>1. Don&#8217;t CAPITALIZE every other word to give context, we can read your words just fine. Capitalizing them makes you seem like you are yelling, or being very aggressive. Both of which, no one reacts well to.</p>
<p>2. WordPress is, and has always been secure to the best of the developer team&#8217;s abilities. If a security vulnerability is found, the WordPress Core Dev team fixes it. So being afraid that WordPress isn&#8217;t taking security seriously doesn&#8217;t seem to make sense. They have had a long preexisting trend since the beginning in releasing updates and fixes for any security threat that was found.</p>
<p>3. WordPress is infinitely customizable if you&#8217;ve got the right knowledge under your belt. You don&#8217;t need to go into the Core to change things, that&#8217;s what plugins are for. Why are you against using plugins? WordPress is constantly evolving, if the need for a feature to disable post revisions is necessary for the majority of the community, then it&#8217;s built in. For everything else, there&#8217;s the plugin realm of WordPress. You can do just about anything with a plugin, and that along with Theming, is what makes WordPress a solid choice for running a site on it.</p>
<p>4. It&#8217;s not WordPress&#8217; responsibility to chase down every host on the planet and get them to support WordPress auto upgrades. I guarantee you that there&#8217;s hundreds more hosts not listed here that already support WordPress automatic upgrades and they don&#8217;t even know it. There are already 93 hosts (and counting) that are listed on the WP.org site as confirmed. That list already includes all the big hosting companies here in the US (and across the world), so it&#8217;s up to the host (or hosting client) themselves to test for this and be listed here. Also, nothing is stopping you from simply uploading WP through FTP if you want to upgrade and are unable to use the Automatic Upgrade.</p>
<p>5. Search Google for &#8220;wp-hackers&#8221; and you&#8217;ll find the mailing list that you can probably ask some more of your questions more directly than the forums.</p>
<p>WordPress isn&#8217;t as flawed as you may think, you&#8217;ve just got to take the time to understand it and learn from the information out there. The same applies to many other complex content management systems, there are high barriers to entry for anyone who wants to do something but doesn&#8217;t know how. Trial and error is your best bet.<br />
.-= Scott Kingsley Clark´s last blog ..<a href="http://www.scottkclark.com/rt-rocketgenius-gravity-form/" rel="nofollow">RT @rocketgenius: Gravity Form…</a> =-.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter van der Does</title>
		<link>http://sparun.in/what-wordpress-should-do/#comment-410</link>
		<dc:creator>Peter van der Does</dc:creator>
		<pubDate>Tue, 15 Sep 2009 21:18:19 +0000</pubDate>
		<guid isPermaLink="false">http://sparun.in/?p=113#comment-410</guid>
		<description>XP still gets it&#039;s updates until it&#039;s no longer supported and a big security flaw is discovered in IE. XP relates to WordPress 1.x while Vista would WordPress 2.x . See 2.8 as Service Pack 8. I guess WordPress 3 would be Windows 7.

Why they keep a list? So you can be informed to what hosting providers provide a reliable environment for WordPress. It&#039;s not WordPress (a.k.a. Automattic) duty to change the hosting providers, I think it&#039;s a good thing they do give you a list of providers that work with WordPress.It&#039;s like Ferrari suggesting a high octane gas, not that lower octance won&#039;t work but it could, according to Ferrari, lead to less performance.
.-= Peter van der Does´s last blog ..&lt;a href=&quot;http://feedproxy.google.com/~r/mythoughts2/~3/i9hg9_6JkiA/&quot; rel=&quot;nofollow&quot;&gt;How to update your custom Ubuntu Jaunty kernel after a new kernel release – revised.&lt;/a&gt; =-.</description>
		<content:encoded><![CDATA[<p>XP still gets it&#8217;s updates until it&#8217;s no longer supported and a big security flaw is discovered in IE. XP relates to WordPress 1.x while Vista would WordPress 2.x . See 2.8 as Service Pack 8. I guess WordPress 3 would be Windows 7.</p>
<p>Why they keep a list? So you can be informed to what hosting providers provide a reliable environment for WordPress. It&#8217;s not WordPress (a.k.a. Automattic) duty to change the hosting providers, I think it&#8217;s a good thing they do give you a list of providers that work with WordPress.It&#8217;s like Ferrari suggesting a high octane gas, not that lower octance won&#8217;t work but it could, according to Ferrari, lead to less performance.<br />
.-= Peter van der Does´s last blog ..<a href="http://feedproxy.google.com/~r/mythoughts2/~3/i9hg9_6JkiA/" rel="nofollow">How to update your custom Ubuntu Jaunty kernel after a new kernel release – revised.</a> =-.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
