再来看seo，这是业内争议较大的部分。从理论上讲，在其他条件一致的情况下，与关键词越接近的域名搜索排名则越高。这一理论在英文域名中被广泛接受，但中文域名的具体表现则有待观察了。有人经试验发现google中该理论仍然有效但百度却未见效果，甚至连收录都有问题。

从上面的分析不难看出，百度对中文域名的支持相当的差，一般将其视为百度技术落后的表现。但有一点需要注意，目前各大搜索引擎都已经注册了自己的中文域名，而唯独百度没有注册一个“百度”相关的中文域名（目前仅发现“我.cn”一个中文域名，不知是出于什么目的）。这似乎说明了某些问题，隐隐觉得百度对中文域名的支持问题不是技术上的而是态度上的，即百度根本不愿意看到中文域名流行起来。原因何在？很简单，中文域名的流行将大幅减少百度的流量。我们知道，目前人们进入一个网站的途径一般有以下几条：网址、收藏夹、导航站、搜索引擎、默认首页、友情链接、强制弹出。这里面就有一个很关键的问题，有多少人是通过搜索引擎进网站的？可以说比例是相当大的，而这里面由于多少人是搜索网站名字然后点击进入网站的？换句话就是说，搜索引擎的流量借助了大量别人网站的流量，举个例子，某人要上新浪网但不记得网址，就先搜索“新浪”二字然后进入新浪网，关闭搜索引擎。这里浏览者对百度的访问完全是新浪带来的。想想我们身边有多少人是通过这种方式进入网站的。一旦中文域名普及开来，人们记得网站名直接在地址栏输入就能进入网站那，搜索引擎的这部分流量必然流失。可能有人觉得这部分流量有限，但请注意国内四大门户的流量约为百度流量的1.5倍，仅以此算有1%的人通过上述办法进入四大门户，如损失后百度流量将下降1.5%再加上其他网站，百度的流量损失是相当可观的。因此，有理由相信百度在利用自己中文网络市场的垄断地位阻击中文域名。同时中文域名日益流行必然对百度工具条之类的插件形成更大压力，这也是百度所不愿意看到的。作者：杨志欣 原文《中文域名现状分析》

错误快照

谷歌快照

谷歌快照

这种现象我也是第一次遇到 如果有网友知道留言

We’re still investigating what happened, but as a prophylactic measure we’ve decided to force-reset all passwords on WordPress.org. To use the forums, trac, or commit to a plugin or theme, you’ll need to reset your password to a new one. (Same for bbPress.org and BuddyPress.org.)

As a user, make sure to never use the same password for two different services, and we encourage you not to reset your password to be the same as your old one.

Second, if you use AddThis, WPtouch, or W3 Total Cache and there’s a possibility you could have updated in the past day, make sure to visit your updates page and upgrade each to the latest version.

An RC comes after the beta period and before final release. We think we’re done, but with tens of millions of users, a variety of configurations, and thousands of plugins, it’s possible we’ve missed something. So if you haven’t tested WordPress 3.2 yet, now is the time! Please though, not on your live site unless you’re extra adventurous.

Things to keep in mind:

• With more than 350 tickets closed, there are plenty of changes. Plugin and theme authors, please test your plugins and themes now, so that if there is a compatibility issue, we can figure it out before the final release.
• Users are also encouraged to test things out. If you find problems, let your plugin/theme authors know so they can figure out the cause.
• Twenty Eleven isn’t quite at the release candidate stage. Contents may settle.
• If any known issues crop up, you’ll be able to find them here.

If you are testing the release candidate and think you’ve found a bug, there are a few ways to let us know:

• Post it to the Alpha/Beta area in the support forums or wp-testers
• Join the development IRC channel and tell us live at irc.freenode.net #wordpress-dev
• File a bug ticket on the WordPress Trac

To test WordPress 3.2, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip).

Happy testing!

If you’d like to know which levers to pull in your testing, check out a list of features in our Beta 1 post.

• Various security hardening by Alexander Concha.
• Taxonomy query hardening by John Lamansky.
• Prevent sniffing out user names of non-authors by using canonical redirects. Props Verónica Valeros.
• Media security fixes by Richard Lundeen of Microsoft, Jesse Ou of Microsoft, and Microsoft Vulnerability Research.
• Improves file upload security on hosts with dangerous security settings.
• Cleans up old WordPress import files if the import does not finish.
• Introduce “clickjacking” protection in modern browsers on admin and login pages.

Consult the change log for more details.

Download WordPress 3.1.3 or update automatically from the Dashboard → Updates menu in your site’s admin area.

WordPress 3.2 Beta 2 also available

In other news, our development of WordPress 3.2 development continues right on schedule. We released Beta 1 thirteen days ago, and today we’re putting out Beta 2 for your testing pleasure.

This is still beta software, so we don’t recommend that you use it on production sites. But if you’re a plugin developer, a theme developer, or a site administrator, you should be running this on your test environments and reporting any bugs you find. If you’re a WordPress user who wants to open your presents early, take advantage of WordPress’ famous 5-minute install and spin up a secondary test site. Let us know what you think!

The plan is to start putting out release candidates in early June, and to release WordPress 3.2 by the end of the month. The more you help us iron out issues during the beta period, the more likely we are to hit those dates. To misappropriate and mangle a quote from Mahatma Gandhi: “Be the punctuality you want to see in the WordPress.” In other words, test now!

Here are some of the things that changed since Beta 1:

• Google Chrome Frame is now supported in the admin, if you have it installed. This is especially useful for IE 6 users (remember, IE 6 is otherwise deprecated for the admin).
• The admin is less ugly in IE 7.
• The blue admin color scheme has caught up to the grey one, and is ready for testing.
• We are now bundling jQuery 1.6.1. You should test any JS that uses jQuery. WordPress JavaScript guru Andrew Ozz has a post with more info.

Download WordPress 3.2 Beta 2

使用方法：

1、设置栏出现WP-o-Matic选项，在add campaign点击Basic设置一个大分类。
2、在feeds里添加要采集的目标站的feed地址，可同时添加多个，categories选择采集分类。在categories里设置要采集目标文 章归类
3、在options里设置采集路径等，默认就行，Cache images要求用户自己建立个“Cache”文件夹并修改权限为777。每次采集都需要在add campaign执行，addcampaign设置完成后点击submit后，如果未设置好，他会提示你，直到Campaign added successfully. Edit it or fetch it now后点击fetch it now。
4.关于一Rewrite设置，如果不熟悉的话建议配合WordPress固定链接翻译插件以免采集到的文章URL是中文。

百度搜索引擎优化指南（官方版）

百度账户通顺度

新质量度优化指导手册

通顺度标准

账户通顺度优化

百度商桥

第一课：认识商桥：销售不在，别谈推广
第二课：安装商桥：工欲善其事必先利其器
第三课：学会用商桥沟通：沟通，销售的自我修养

百度统计

第一课：带您认识百度统计
第二课：简单三步，学会安装
第三课：教您读报告，发现网站背后的故事