Twitter日益流行，越来越多的人想给自己的家人、朋友、同事建立一个像Twitter这样的微博客，其实这并没有想象中的难。在这里我给大家介绍下如何在WordPress中轻松创建微博客。

前言

Twitter的成功是大家有目共睹的，微博客无疑是非常实用和高效的。它可以让我们随时跟家人、朋友、同事保持联系。 尽管Twitter已经很出色了，但是作为私人空间，比如与同事分享工作体验或是向家人汇报近况，Twitter却不是最佳的选择。

为此，之前我用开源程序laconi.ca创建自己的微博客网站，它可以让用户创建类似于Twitter 的微博客网站。说实话，它不怎么让我满意，应该说挺后悔安装它的。
在这次不愉快的体验后，我觉得应该让WordPress来实现这一功能。

动手吧！

说了这么多，让我们行动起来用WordPress创建自己的私人微博客吧！

1. 安装WordPress

首先要做的当然是在服务器上安装WordPress。安装WordPress非常简单，你可以在网上找到安装教程，这里就不再讲述。需要帮助的话，你可以阅读相关文档。

2.使用P2 主题

Automattic公司出品的适合微博客应用的一个非常酷的主题，叫做P2，你可以 免费下载 。

下载完后，将它上传到WordPress的the wp-content/ themes 目录下。然后，登陆到WordPress后台的外观/主题，选择P2主题并激活。 这样你就成功安装P2主题，一切准备就绪了。

3.关于登录面板

尽管P2主题已经不错了，你还可以通过一些方法完善它。由于P2允许用户不通过WordPress后台直接从frontpage发布内容。在主题的侧边栏添加个登录控制面板是个不错的主意。 登录控制面板可以帮你实现：

• 如果用户尚未登录或还没有账户，系统将会显示登录表单及注册链接，访问者可以自己创建账户。
• 如果用户已经登录，系统会显示一个退出和账户选项的链接，因此就算是不懂WordPress的用户也可以轻松更新他的资料。

在主题的侧边栏添加登录面板，只要打开主题中sidebar.php文件，粘贴下面的代码就行：

<li>
<?php global $user_ID, $user_identity, $user_level ?>
<?php if ( $user_ID ) : ?>

<h2>Control panel</h2>
<ul>
<li>Identified as <strong><?php echo $user_identity ?></strong>.
<ul>
<li><a href=”<?php bloginfo(‘url’) ?>/wp-admin/”>Dashboard</a></li>

<li><a href=”<?php bloginfo(‘url’) ?>/wp-admin/profile.php”>Profile and personal options</a></li>
<li><a href=”<?php bloginfo(‘url’) ?>/wp-login.php?action=logout&amp;redirect_to=<?php echo urlencode($_SERVER['REQUEST_URI']) ?>”>Logout</a></li>

<?php
if (is_single()) {?>
<li><a href=”<?php bloginfo(‘wpurl’);?>/wp-admin/edit.php?p=<?php the_ID(); ?>”>Edit Post</a>
</li>
<?php } ?>

</ul>
</li>
</ul>

<?php elseif ( get_option(‘users_can_register’) ) : ?>
<h2>Identification</h2>
<ul>
<li>

<form action=”<?php bloginfo(‘url’) ?>/wp-login.php” method=”post”>
<p>
<label for=”log”><input type=”text” name=”log” id=”log” value=”<?php echo wp_specialchars(stripslashes($user_login), 1) ?>” size=”22″ /> User</label><br />
<label for=”pwd”><input type=”password” name=”pwd” id=”pwd” size=”22″ /> Password</label><br />
<input type=”submit” name=”submit” value=”Login” />
<label for=”rememberme”><input name=”rememberme” id=”rememberme” type=”checkbox” checked=”checked” value=”forever” /> Remember me</label><br />
</p>
<input type=”hidden” name=”redirect_to” value=”<?php echo $_SERVER['REQUEST_URI']; ?>”/>
</form>

</li>
<li><a href=”<?php bloginfo(‘url’) ?>/wp-register.php”>Register</a></li>
<li><a href=”<?php bloginfo(‘url’) ?>/wp-login.php?action=lostpassword”>Recover password</a></li>
</ul>

<?php endif; ?>
</li>

4. 微博客保密化
登录/注册表单在某些情况下是挺完美了，但是别人还是可以通过搜索引擎引用你的内容。如果你想要让你的网站完全保密，也是没有问题的。 这就需要使用到WordPress插件Private WP，（下载）。下载完后，将它上传到wp-content/plugins 目录下。然后登陆WordPress后台，激活该插件。

这样，你的网站就可以自动检测登录用户，只有登录用户才可阅读和发布文章。对于未知访问者，系统将会自动转向到WordPress登录面板。

结论

这再次验证了WordPress的可扩展性以及功能的强大。如果你对WP比较熟悉，不用半个小时就可以用P2主题创建一个类似于Twitter的站点。够神奇吧！

这里只是简单介绍创建微博客网站的一些基本技巧，如果有兴趣，还有很多有意思的功能可以用来加强你的微博网站。比如，创建一个页面显示所有的会员列表或者过滤文章（只有特定的会员才可以发布文章）等等。

原文：

Create your own private Twitter site using WordPress

With the incredible popularity of Twitter theses days, many people are asking themselves how can they create their own Twitter-like network for their family, friends or company. This may be a lot easier than you think. In this tutorial, I’m going to show you how to do it easily, using WordPress.

Getting ready

Twitter success is the proof, microblogging is definitely something useful and efficient. It can help you staying tuned with friends, family or coworkers.

While Twitter is great, it may not be the best choice if you’re looking for a private network, for example for sharing work tips with colleagues, or notice your familly about what’s up.
As I was searching for an easy and quick way to create a private microblogging website, I stumbled upon an open source app called laconi.ca, which was created to allow people to launch their own private “Twitter like” microblogging sites. I didn’t really liked it and it was a total pain to install.

After this not so good experience, I decided that WordPress should do that job, and do it good as always.

Let’s doing it

Well, enought talk for now! Let’s create our own, private microblogging website using our beloved WordPress.

1. Installing WordPress

The first thing to do is obviously to install WordPress on your server. Installing WordPress is definitely easy and and I’ll not explain it here due to the incredible amount of tutorials you can find on the internet.
If you need help for installing WordPress, you should read the documentation. Or even better, you can register at WpWebHost, the WordPress hosting experts, and use Fantastico to get your WordPress installed automatically in a minute. Just click here if you want to know more.

2. Get your copy of the P2 theme

The guys from Automattic (The company behing WordPress) released, some time ago, a very cool WordPress theme for social microblogging. The theme is called P2 and you can get it for free here.

After you downloaded P2, simply uncompress the archive and upload it to the wp-content/themes directory of your WordPress install. Once done, login to your WordPress dashboard and go to “Appearance”, “Themes”. Slect the P2 theme and activate it.

That’s easy as that, you have sucessfully installed P2 and you’re ready for social microblogging.

3. What about a login form?

Althought the P2 theme itself is very good, it is possible to enhance it even more. As P2 allow users to post directly from the frontpage, without visiting WordPress dashboard, a good idea should be to integrate a control panel in the theme sidebar.
Our control panel will do the following:
If the user isn’t logged in or have no account yet: We’ll display a login form as well as a link to register, so the visitor can create his account.
If the user is already logged in: We’ll display a link to logout as well as a link to account options, so the user (Even if (s)he doesn’t know much about WordPress) can easily update his/her profile.

To integrate a login form in your theme sidebar, simply open the sidebar.php file and paste the following code:

<li>
  <?php global $user_ID, $user_identity, $user_level ?>
  <?php if ( $user_ID ) : ?>

    <h2>Control panel</h2>
	 <ul>
	   <li>Identified as <strong><?php echo $user_identity ?></strong>.
	   <ul>
		  <li><a href="<?php bloginfo('url') ?>/wp-admin/">Dashboard</a></li>

			<li><a href="<?php bloginfo('url') ?>/wp-admin/profile.php">Profile and personal options</a></li>
			<li><a href="<?php bloginfo('url') ?>/wp-login.php?action=logout&amp;redirect_to=<?php echo urlencode($_SERVER['REQUEST_URI']) ?>">Logout</a></li>

         <?php
         if (is_single()) {?>
           <li><a href="<?php bloginfo('wpurl');?>/wp-admin/edit.php?p=<?php the_ID(); ?>">Edit Post</a>
           </li>
         <?php } ?>

	</ul>
	</li>
	</ul>

  <?php elseif ( get_option('users_can_register') ) : ?>
    <h2>Identification</h2>
    <ul>
      <li>

      <form action="<?php bloginfo('url') ?>/wp-login.php" method="post">
      <p>
        <label for="log"><input type="text" name="log" id="log" value="<?php echo wp_specialchars(stripslashes($user_login), 1) ?>" size="22" /> User</label><br />
        <label for="pwd"><input type="password" name="pwd" id="pwd" size="22" /> Password</label><br />
<input type="submit" name="submit" value="Login" />
        <label for="rememberme"><input name="rememberme" id="rememberme" type="checkbox" checked="checked" value="forever" /> Remember me</label><br />
</p>
        <input type="hidden" name="redirect_to" value="<?php echo $_SERVER['REQUEST_URI']; ?>"/>
      </form>

      </li>
      <li><a href="<?php bloginfo('url') ?>/wp-register.php">Register</a></li>
      <li><a href="<?php bloginfo('url') ?>/wp-login.php?action=lostpassword">Recover password</a></li>
    </ul>

<?php endif; ?>
</li>

4. Making your network private

While the login/register form option can be good in some case, it will still allow people to read your discussions and search engines to index your content. If your need is a 100% private website, don’t worry. This is far from being a problem.
To do so, we’ll use a WordPress plugin, named Private WP. Get your copy here. Once you have it, extract the archive on your hard drive and upload the private-wp to the wp-content/plugins directory of your WordPress install. Then, simply login to WordPress, go to the dashboard, then to “Plugins” and activate the plugin.

That’s all you have to do. Now, your website will automatically detect logged in users, who’ll be able to read and post content, and unknown visitors, who’ll be automatically redirected to WordPress loggin panel.

Conclusion

The first thing which have to be said is that, one more time, WordPress show how extensible and powerful it is. If you’re familiar with WP, creating this “Twitter-like” site using the P2 theme should not take you more than 30 minutes. Isn’t that great? I’ll not say that I love WordPress, because all of you already know

This tutorial was focused on making a private microblogging site and used only basic techniques, but there’s a lot of other interresting things that can be done in order to enhance this “Twitter-like” site. For example, you may want to create a page template listing all members, or even better, filtering posts to see only those posted by a selection of members?

针对有的用户抱怨WordPress运行效率低，这里我就给大家介绍下优化WP博客运行的一些简单方法：

1. 理智地选择主机服务

不要被低价主机的宣传所诱惑，要记住没有白捡的便宜。随着网站越来越受欢迎，你可能得考虑升级为独立服务器甚至是云方案，才能保证更好的运行时间（特别党是你的文章被大网站推荐时）并提供优质的服务。

2. 利用插件与垃圾邮件抗争

Akismet 成为WP中最受欢迎的插件不是偶然的（并不仅仅因为安装时就自带）。因为它确实阻止了很多垃圾邮件。还有其他什么保护措施呢？你可以再安装Simple Trackback Validation作为Akismet的补充。垃圾邮件越来越先进了，防垃圾邮件的工具也要更新。任何博客都少不了反垃圾邮件插件。

3. 备份

记住不能光靠主机服务商为你的博客备份。任何网站都可能会遭遇失误，包括：丢失文件、数据库损坏、插件出问题或是软件更新出错等等。安装数据库备份插件才能让自己放心。(小帖士: 创建一个专门的Gmail账户，每天发送备份文件到邮箱)。一旦出现什么问题，你可以重新恢复你上一次的配置并且保持良好的运行。

4. 留心更新

如果你使用的是WordPress (2.6及以上)版本，可能会有一大堆的软件更新提示。 如果你安装了很多插件或者自定义主题，在按任何更新按钮之前都要三思而后行。(按照第三条，首先就是要备份。)，同时要记住删除任何“自动更新”类型的插件，很多管理员因为这些插件的不可兼容性而无法操作后台。学习下该如何管理服务器以及更新之前的测试工作。

5.为什么我的博客这么慢？

博客打开像蜗牛一般吗？这可能有多种原因，常见的有以下原因：

• 你的虚拟主机方案 (具体见1)
• 运行了太多有潜在冲突的插件（可能的话尽量不用) 。
• 使用太多的小工具（代码编写的可能比较差）。
• 过于依赖外部服务（比如，很多文件都是来自Flickr、Twitter、YouTube， 意  味着你要等待这些文件从他们的服务器上运行）。
• 使用免费、现成的主题（可能他们的代码编写比较差，甚至里面有流氓代码）。

工具箱

• WordPress – http://www.wordpress.org
• Akismet – http://wordpress.org/extend/plugins/akismet
• Simple Trackback Validation – http://wordpress.org/extend/plugins/simple-trackback-validation/
• Bad Behavior – http://wordpress.org/extend/plugins/bad-behavior/
• WordPress Database Backup – http://wordpress.org/extend/plugins/wp-db-backup/

附原文：

5 Ways to Keep WordPress Running Smoothly

Here are some easy steps you can take to ensure that your WordPress blog is running optimally.

1. Choose Your Host Wisely
While it’s tempting to go for a shared plan that’s under $5/month, you have to remember you get what you pay for. As your site gets popular, you may need to consider upgrading to a virtual private server, a dedicated server, or even a cloud solution. These plans can often guarantee better uptimes (especially when you land on the home page of Digg) and offer superior performance overall.

2. Fight Spam with Plugins
It’s no accident that Akismet is WordPress’s most popular plugin (and not just because it’s included with your install). It really stops most spam in its tracks. Want even more protection? You can supplement Akismet by installing Simple Trackback Validation (to thwart pesky trackback spam) and Bad Behavior. As spammers get more sophisticated, so do these tools. No blog should be launched without them.

3. Back It Up
Remember you can’t rely on your host alone to get your blog’s data back. As with any website, there are many, many points of failure, including lost files, corrupted databases, plugin breakages, and software upgrade errors. Install the WordPress Database Backup plugin for peace of mind. (Bonus Tip: create a special Gmail account and have your backup files sent there daily). When things go wrong, you can restore to your last good known configuration and be back running quickly.

4. Watch Those Upgrades
If you are running a newer version of WordPress (2.6 and above), you can be bombarded with prompts to update your out-of-date software. If you have a lot of plugins or a customized theme, you should think twice about blindly pressing any update buttons (see #3 and do a backup first!). Also, please delete any “automatic upgrade” plugins, which have been known to lock many an admin out of their dashboard due to incompatibilities. Learn how to create development server and test out your upgrades before applying them to your production site.

5. Why is My Blog Slow?
There can be many reasons why your blog is behaving up like a snail. Common causes can be traced to:

 Your host or your plan (see #1)
 Running too many potentially conflicting plugins (pare them down when possible)
 Using too many widgets (which may be poorly coded)
 Relying on external services (when you pull in files from Flickr, Twitter, or YouTube, for example, it means you have to wait on them to serve up images, tweets, and videos from their sites.)
 Using a free, off-the-shelf theme (they can be programmed poorly or even have rogue code within them)

Toolbox
 WordPress – http://www.wordpress.org
 Akismet – http://wordpress.org/extend/plugins/akismet
 Simple Trackback Validation – http://wordpress.org/extend/plugins/simple-trackback-validation/
 Bad Behavior – http://wordpress.org/extend/plugins/bad-behavior/
 WordPress Database Backup – http://wordpress.org/extend/plugins/wp-db-backup/

Follow these 5 tips and you’ll find that your WordPress blog is more stable and easier to manage.

过去几年，各个新版本相继解决了在各种系统中运行WP出现的各种问题。但是把这些修改都移植到2.0.x 是一项很艰巨的任务，可能会带来新的不稳定因素和bug。WordPress开发组不得不权衡稳定性和兼容所有的修改，在两者间做出艰难的决定。另外，越 来越少人使用2.0.x了。在对WordPress的新功能（以及插件提供的功能）进行了测试 ，发现它们很多都不支持旧版的WP。

WP2.0.x 不能坚持到2010年，是有点让人失望。不过考虑到其失败的最大原因在于WP新版本大范围内的安全改善，2.0.x 退出舞台还是值得的！

附原文：

The WordPress 2.0.x Legacy Branch is Deprecated

本文转载自：把WordPress变成Twitter（WordPress啦！）

Twitter日益流行，越来越多的人想给自己的家人、朋友、同事建立一个像Twitter这样的微博客，其实这并没有想象中的难。在这里我给大家介绍下如何在WordPress中轻松创建微博客。

前言

Twitter的成功是大家有目共睹的，微博客无疑是非常实用和高效的。它可以让我们随时跟家人、朋友、同事保持联系。 尽管Twitter已经很出色了，但是作为私人空间，比如与同事分享工作体验或是向家人汇报近况，Twitter却不是最佳的选择。

为此，之前我用开源程序laconi.ca创建自己的微博客网站，它可以让用户创建类似于Twitter 的微博客网站。说实话，它不怎么让我满意，应该说挺后悔安装它的。
在这次不愉快的体验后，我觉得应该让WordPress来实现这一功能。

动手吧！

说了这么多，让我们行动起来用WordPress创建自己的私人微博客吧！

1. 安装WordPress

首先要做的当然是在服务器上安装WordPress。安装WordPress非常简单，你可以在网上找到安装教程，这里就不再讲述。需要帮助的话，你可以阅读相关文档。

2.使用P2 主题

Automattic公司出品的适合微博客应用的一个非常酷的主题，叫做P2，你可以 免费下载 。

下载完后，将它上传到WordPress的the wp-content/ themes 目录下。然后，登陆到WordPress后台的外观/主题，选择P2主题并激活。 这样你就成功安装P2主题，一切准备就绪了。

3.关于登录面板

尽管P2主题已经不错了，你还可以通过一些方法完善它。由于P2允许用户不通过WordPress后台直接从frontpage发布内容。在主题的侧边栏添加个登录控制面板是个不错的主意。 登录控制面板可以帮你实现：

• 如果用户尚未登录或还没有账户，系统将会显示登录表单及注册链接，访问者可以自己创建账户。
• 如果用户已经登录，系统会显示一个退出和账户选项的链接，因此就算是不懂WordPress的用户也可以轻松更新他的资料。

在主题的侧边栏添加登录面板，只要打开主题中sidebar.php文件，粘贴下面的代码就行：

<li>
<?php global $user_ID, $user_identity, $user_level ?>
<?php if ( $user_ID ) : ?>

<h2>Control panel</h2>
<ul>
<li>Identified as <strong><?php echo $user_identity ?></strong>.
<ul>
<li><a href=”<?php bloginfo(‘url’) ?>/wp-admin/”>Dashboard</a></li>

<li><a href=”<?php bloginfo(‘url’) ?>/wp-admin/profile.php”>Profile and personal options</a></li>
<li><a href=”<?php bloginfo(‘url’) ?>/wp-login.php?action=logout&amp;redirect_to=<?php echo urlencode($_SERVER['REQUEST_URI']) ?>”>Logout</a></li>

<?php
if (is_single()) {?>
<li><a href=”<?php bloginfo(‘wpurl’);?>/wp-admin/edit.php?p=<?php the_ID(); ?>”>Edit Post</a>
</li>
<?php } ?>

</ul>
</li>
</ul>

<?php elseif ( get_option(‘users_can_register’) ) : ?>
<h2>Identification</h2>
<ul>
<li>

<form action=”<?php bloginfo(‘url’) ?>/wp-login.php” method=”post”>
<p>
<label for=”log”><input type=”text” name=”log” id=”log” value=”<?php echo wp_specialchars(stripslashes($user_login), 1) ?>” size=”22″ /> User</label><br />
<label for=”pwd”><input type=”password” name=”pwd” id=”pwd” size=”22″ /> Password</label><br />
<input type=”submit” name=”submit” value=”Login” />
<label for=”rememberme”><input name=”rememberme” id=”rememberme” type=”checkbox” checked=”checked” value=”forever” /> Remember me</label><br />
</p>
<input type=”hidden” name=”redirect_to” value=”<?php echo $_SERVER['REQUEST_URI']; ?>”/>
</form>

</li>
<li><a href=”<?php bloginfo(‘url’) ?>/wp-register.php”>Register</a></li>
<li><a href=”<?php bloginfo(‘url’) ?>/wp-login.php?action=lostpassword”>Recover password</a></li>
</ul>

<?php endif; ?>
</li>

4. 微博客保密化
登录/注册表单在某些情况下是挺完美了，但是别人还是可以通过搜索引擎引用你的内容。如果你想要让你的网站完全保密，也是没有问题的。 这就需要使用到WordPress插件Private WP，（下载）。下载完后，将它上传到wp-content/plugins 目录下。然后登陆WordPress后台，激活该插件。

这样，你的网站就可以自动检测登录用户，只有登录用户才可阅读和发布文章。对于未知访问者，系统将会自动转向到WordPress登录面板。

结论

这再次验证了WordPress的可扩展性以及功能的强大。如果你对WP比较熟悉，不用半个小时就可以用P2主题创建一个类似于Twitter的站点。够神奇吧！

这里只是简单介绍创建微博客网站的一些基本技巧，如果有兴趣，还有很多有意思的功能可以用来加强你的微博网站。比如，创建一个页面显示所有的会员列表或者过滤文章（只有特定的会员才可以发布文章）等等。

原文：Create your own private Twitter site using WordPress
翻译：WordPress啦! ]]> http://xwxy.zzspy.com/2009/07/29/create-your-private-twitter-like-wordpress/feed/ 1 http://xwxy.zzspy.com/2009/07/23/wordpress-switches-to-hourly-pinging-tells-no-one/ http://xwxy.zzspy.com/2009/07/23/wordpress-switches-to-hourly-pinging-tells-no-one/#comments Thu, 23 Jul 2009 09:18:11 +0000 jacobxx http://xwxy.zzspy.com/?p=160

本文转载自：WordPress啦！

WordPress 2.8 修改了默认的ping频率，将发布或编辑文章时的ping改为每小时一次。这一修改既没有写进文档也没有在发布说明中提到，发现这一问题的是一位名叫Christian Bolstad的WordPress用户。

这会造成什么影响呢？

• 推迟了RSS订阅的更新。
• 推迟了RSS订阅的更新意味着推迟了所有与其相关的服务。
• 推迟了RSS订阅意味着与RSS相关的搜索引擎的工作也推迟。

我猜测这个功能是为了加快管理界面的执行速度。如果很多服务要执行Ping，比如发布或编辑文章等，意味着你要等待管理界面解析Ping后再执行。 Christian Bolstad有人认为此举严重阻碍了实时网站的实现。 这么说可能有点过了，但是它确实延迟了一切从WordPress上发出的东西。

这一变动的负责人，Denis de Bernardy（WordPress核心开发成员之一）认为Christian Bolstad 的文章是危言耸听的，并发表了评论:

如果最终用户没有代码经验不能写补丁，他随时可以提交一个评论或建议，这也就罢了。 但对于程序员来说，就不太好了，把一篇危言耸听的文章置顶，这行为是让人无法忍受的。他能够也应该写一个补丁。如果不写补丁的话，就应该接受我们的修改。

至于为什么没有在版本说明里阐明，因为这根本就是很小的事，对WordPress用户（也包括免费用户）都不值得一提。如果你觉得有必要可以自己添加这个说明。

很明显他是在为Ping行为的修改做辩解，只不过这辩解显得苍白无力。从某种程度上来讲，他认为程序员不能对这种决定评头论足，他们应该安安静静地提交补丁。真是滑稽，希望他的本意不是这样的。 总之，要记住现在WordPress默认的不再是发布时就执行Ping了，而是每个小时Ping一次。你可以随时修改Ping行为，但是可能你的网站会受到影响，甚至崩溃。

原文：WordPress Switches to Hourly Pinging, Tells No One

Blogger Christian Bolstad found a new feature in WordPress 2.8, undocumented and not among the release notes in the Codex. Basically, it changes the notification behavior of WordPress, from notifying ping services like Pingomatic and others you might use automatically when publishing a post or editing a previously published post, to doing a once an hour notification using the built-in pseudo cron.

So why is this a bad thing? [Note! Bullets updated below! See comments for more.]

• It delays updates to the RSS feed to services relying on pinging.
• Delaying pings delaying all services depending on pinging.
• Delaying pinging to middle man services means that syndication of the links will be delayed.

My guess is that this feature was implemented to speed up the admin interface. After all, if you’ve got a bunch of services to ping, publishing or editing a published post would mean that you’d have to wait while the admin interface parsed through the pinging.

Christian Bolstad thinks this is putting the real time web to a halt. That might a bit over the top, but it does delay everything coming from a WordPress install.

Denis de Bernardy was the developer responsible for this change in behavior, and he find the post alarmist and intolerable. This are his words in a comment on the post:

If an end user with no coding skills can’t write a patch, he can always submit a comment in trac, and suggest things to be done otherwise. That’s fine.

The same from a coder is not fine. Add an alarmist post on top, and things become intolerable. If a coder isn’t not happy with a behavior, he can and should write a patch. If he doesn’t, he should put up with the behavior.

As to why this wasn’t added in the release notes, it’s a Wiki. It occurred to nobody who contributed to them (without getting paid either) that it was worth a mention. Go right ahead and add the note yourself if you think it’s so important.

Obviously he is just defending the decision to change the pinging behavior, albeit in a somewhat poor way. For some reason he thinks that coders are not allowed to criticize choices made, they should be quiet and submit patches instead. Let’s hope he didn’t really mean it that way. And the fact that an end user should update the release notes is something of an issue with open source overall, because as Bernardy says the developers do it on their free time. Ideally they would write complete release notes, but if the choice is to either finish a function/feature, or write the notes, the developer will finish his coding instead. As he should. Still, it is an issue as this discussion surely points out.

Anyway, one should be aware that WordPress per default does not ping on publish anymore, it does it on a per-hour basis instead. It is also a reminder of the fact that developers can change behavior at any time, and that it might in fact effect your site, or even break it.