Google首席执行官施密特认为Facebook不是Google的竞争对手，尽管Google正在着手开发自己的社交网和游戏服务，但是施密特还是放出信号，称公司与Facebook并无抵触。

施密特称：“Facebook是否是一个竞争者？我们对此问题非常小心。”

首先，施密特认为就目前而言，Google与Facebook没有在广告收入上直接竞争；因此讨论二者是不是对手“从数学上看是错的”。另外，施密特认为Facebook将更多网民带入网络对Google有利，他说：“Facebook用户使用Google的产品多于其它公司的产品。你们是假定它们做得好，我们做得不好，但实际却是双赢。”

对于Google推出自家社交网与游戏平台的报道，施密特拒绝评论。但他暗示人们所谓有“社交——搜索”大战还很遥远。施密特说：“你们是否认为搜索最终版已经问世？你们是否认为最终的社交网服务已经问世？互联网的规则从没有停步。”

对于Facebook与Google的人才争夺，施密特并非视而不见。过去几年，多位Google高管跳槽到Facebook，他们许多与广告业务有关。有猜测称Facebook准备推出一个广告系统，它纵横数百万家网站，整合已有的服务。这可能让Facebook腾飞，挑战Google的AdSense业务。

施密特说，他不认为从Google叛逃的前员工会将“复制版的AdSense”用在Facebook，他说：“他们已经做过了，他们应该解决新的难题。”

数年前，雅虎与Google竞争时也有相似言论，施密特认为用户会同时使用两个平台，都会给两个公司带来营收。

7月23日，WordPress官方博客撰文发出通告，他们将停止对 PHP 4 和 MySQL 4 的支持。

WordPress一直以来对服务器的要求都是比较低的，这也是为了让用户有更加灵活的选择，因此，WordPress几乎在任何服务器上都能非常完美地运行。不过，服务器不断在发展，有必要对WordPress的服务器要求进行适当的调整，现在WordPress官方决定不再支持 PHP 4、MySQL 4 了。

首先一点，预计在今年年底推出的 WordPress 3.1 将会是最后一个支持 PHP 4 的版本。其次，预计2011年上半年推出的 WordPress 3.2，对PHP版本的最低版本要求将提高到 PHP 5.2 版。为什么选择5.2呢？因为大多数WordPress用户都在使用这个版本，而且它比前几个版本有非常大的改善。Drupal、Joomla等内容管理系统的下个版本（两者都将在今年推出）所支持的最低PHP版本也是5.2。

目前只有大约11%的WordPress运行 PHP 5.2 以下的版本，这其中大多数的主机都支持 PHP 5.2 ，用户只需要在主机控制面板修改配置并激活 PHP 5.2 即可。而且主机商也会意识到跟上步伐来支持最新的WordPress（或Drupal 、Joomla），今年过后这个比例肯定还会下降。

另外，WordPress官方还表示 WordPress 3.1 之后也打算放弃支持 MySQL 4。目前不到6%的WordPress用户在使用 MySQL 4。WordPress 3.2 版本对MySQL的版本要求将变成5.0.15。

如果用户的主机环境没有达到要求，WordPress用户将无法升级到 WordPress 3.2 。为了方便用户确认主机商所提供的版本支持，WordPress官方创建了 Health Check 插件。下载、安装、激活后，目前 Health Check 只会告诉你的主机是否适用于 WordPress 3.2。以后的版本将会向用户提供更加实用的服务器以及WordPress安装的信息。

总之，今年年底推出的 WordPress 3.1 将会是最后一个支持 PHP 4 以及 MySQL 4 的版本，2011年上半年推出的 WordPress 3.2 要求 PHP 5.2 或更高；MySQL 5.0.15 或更高。大家现在也可以安装 Health Check 插件来检查下自己的主机是否已经做好准备！

PHP 4 and MySQL 4 End of Life Announcement
Posted July 23, 2010 by Mark Jaquith. Filed under Hosting.

Our approach with WordPress has always been to make it run on common server configurations. We want users to have flexibility when choosing a host for their precious content. Because of this strategy, WordPress runs pretty much anywhere. Web hosting platforms, however, change over time, and we occasionally are able to reevaluate some of the requirements for running WordPress. Now is one of those times. You probably guessed it from the title — we’re finally ready to announce the end of support for PHP 4 and MySQL 4!

First up, the announcement that developers really care about. WordPress 3.1, due in late 2010, will be the last version of WordPress to support PHP 4.

For WordPress 3.2, due in the first half of 2011, we will be raising the minimum required PHP version to 5.2. Why 5.2? Because that’s what the vast majority of WordPress users are using, and it offers substantial improvements over earlier PHP 5 releases. It is also the minimum PHP version that the Drupal and Joomla projects will be supporting in their next versions, both due out this year.

The numbers are now, finally, strongly in favor of this move. Only around 11 percent of WordPress installs are running on a PHP version below 5.2. Many of them are on hosts who support PHP 5.2 — users merely need to change a setting in their hosting control panel to activate it. We believe that percentage will only go down over the rest of the year as hosting providers realize that to support the newest versions of WordPress (or Drupal, or Joomla), they’re going to have to pull the trigger.

In less exciting news, we are also going to be dropping support for MySQL 4 after WordPress 3.1. Fewer than 6 percent of WordPress users are running MySQL 4. The new required MySQL version for WordPress 3.2 will be 5.0.15.

WordPress users will not be able to upgrade to WordPress 3.2 if their hosting environment does not meet these requirements (the built-in updater will prevent it). In order to determine which versions your host provides, we’ve created the Health Check plugin. You can download it manually, or use this handy plugin installation tool I whipped up. Right now, Health Check will only tell you if you’re ready for WordPress 3.2. In a future release it will provide all sorts of useful information about your server and your WordPress install, so hang on to it!

In summary: WordPress 3.1, due in late 2010, will be the last version of WordPress to support PHP 4 and MySQL 4. WordPress 3.2, due in the first half of 2011, will require PHP 5.2 or higher, and MySQL 5.0.15 or higher. Install the Health Check plugin to see if you’re ready!

Google Apps 现在允许管理员设置每个用户可用的服务了，目前这个功能已经免费提供给专业版和教育版的 Google Apps 客户使用，未付费的标准版客户则无缘享受。

你必须要使用英文版的下一代控制面板才能启用这项新功能（就是设置成 “Next generation (US English only)”）。此外，管理员控制面板的菜单发生微调，原先的用户与组管理菜单 ‘Users and groups’ 现在变成组织与用户 ‘Organization & users’。

有了用户政策管理器，企业就可以一步一步的将办公环境迁移到 Google Apps。比如你只准备好了用 Google Docs 和 Google Sites 协同办公，而还没准备好将邮件系统一起迁移过来，那么就可以先只打开 Google Docs 和 Google Sites ，而关闭Gmail。

管理员也可以用 Google Apps Directory Sync 来将现在的LDAP组织架构映射过来直接使用，或者是用 Google Apps Provisioning API 通过编程来批量设置用户可用的服务，省得一个一个设置。

以下是来自Google的通知邮件：

User policy management now in Google Apps Control Panel

Posted: 20 Jul 2010 10:55 AM PDT

Google Apps administrators can now segment their users into different organizations and control which Google services are enabled/disabled for each of those different sets of users.

- Allows creation of organizations in a tree-like hierarchy
- Manage membership of users into one organization
- Specify policies for which services are on/off by organization

Updates have also been made to the Google Apps Directory Sync Tool and the Provisioning API to take this new functionality into account.

Editions included:
Premier and Education Editions

Languages included:
US English only

How to access what’s new:
The Control Panel tab ‘Users and groups’ now becomes ‘Organization & users’. Click on this new tab to create a new organization.

To create organizational units:
1. In the organizational tree, highlight the organizational unit to which you want to add a child.
2. Click the ‘Add suborganization’ button..
3. Enter a name and description for the new organization.
4. Click the ‘Add organization’ button.
5. The new organizational unit appears as a child of the organizational unit you selected at step 1.

To enable/disable services for specific users:
1. Services that are disabled on the main dashboard will be disabled for all users.
2. Click the ‘Organizations & users’ tab.
3. Select the appropriate organization.
4. Click the ‘Services’ sub-tab.
5. Click ‘On/Off’ to change service settings or if it’s a sub-organization, click ‘Override this setting‘ or ‘Use inherited‘ links to change settings.

- This feature is only available to domains using the ‘Next Generation’ version of the control panel. To enable this version in the control panel, click ‘Domain settings’, then ‘General’ and ensure the checkbox ‘Next generation (US English only)’ is enabled.
- This feature is being rolled out gradually.
- A user can exist in only a single node in the hierarchy tree.

For more information:
http://googleenterprise.blogspot.com/2010/07/introducing-user-policy-management-for.html
Help Center: http://www.google.com/support/a/bin/answer.py?answer=182426