谷歌涉黄――政府力量对网络民意一次拙劣的报复

本文转自天涯社区

文/阑夕

当绿坝丢人现眼成一个留也不是、撤也不是的笑话，当工信部狼狈得要通过英文版《中国日报》来间接表示绿坝不会被强制要求安装，当网络民意再一次被推动到能够影响专制决策的高度并受到大规模的乐观与幽默看待，面对执意要求自由的孩子，那个以暴力著称的家长并没有如往常那样抽出耳光，他作出谦和、纵容的神情，然后朝院子里泼满了脏水和玻璃渣，对孩子慈祥的说道：“去吧，去自由的玩耍吧。”

火的对立面必然是冰，爱的对立面必然是恨，善的对立面必然是恶，谷歌的不作恶信条，在恶势力本身看来便是最大的“作恶”，所以恶势力发话了：“你色情，你低俗，你作恶。”

谷歌会感到很委屈，它成为了政府力量拿来开刀的对象，作为一个进入中国多年、世界上享誉无数、在搜索结果的反映上向中国政府妥协过多次的搜索引擎，被中央电视台在全国收视率最高的新闻节目上以敌对的口吻大加斥责，仿佛邓贵大正是由谷歌带入歧途而去染指了邓玉娇，导致党和国家失去了一名好干部，也导致中国脆弱腐朽的法制建设被又一次裸露在世人眼前。

百度也感到很委屈，曾有传言在Google进入中国之初，出于竞争压力和惧怕心理，百度曾整理了几百页攻击谷歌搜索结果中含有所谓政治问题、宗教问题、情色问题的材料去向中国政府部门举报，直接导致了谷歌被封杀了一段时间以及其快照功能的阉割，但是，我相信，在这次央视诋毁谷歌的事件中，百度是毫不知情的。百度在现在或许会觉得唇亡齿寒，因为当谷歌受到痛击而吃紧时，网民们纷纷将怒火撒到了百度身上，百度在年初耗费4000万人民币将李彦宏推上春晚的事件又被往复重提，而那些能够证明“百度也可以搜索出色情内容”的关键词列表也不断被网友在互相之间传播着，被凭空侮辱为“被谷歌蛊惑得神情恍惚”的网民们咬牙切齿、出于本能的把谷歌的直接竞争对手——百度拉下了马，成功的。

中国政府的手段几十年来未曾进步一点，首先串通好相关人员，编排剧情，然后借喉舌媒体来宣告天下，理直气壮的给它的攻击对象扣上一顶帽子，然后苦口婆心的告诫全国人民：为了保护祖国花朵的健康成长，我们要义不容辞的为花朵除去那些害虫。

有人精辟的总结道：社会主义初级阶段的主要矛盾是人民群众日益增长的智商与各级官员不断下降的道德之间的矛盾。

只是，这次中国政府犯了几点明显的错误，一不留神就露出了险恶的马脚，他们不但没有从绿坝风波吸取足够的教训，反而更加的笨拙和愚蠢了。

1、搜索引擎之责任

杀人犯拿菜刀杀了人，要不要追究到出售菜刀的商业身上？搜索引擎检索第三方网站的信息，且不论其在是否需要遵守一个政府所定义的“不良”标准来进行过滤——在技术上这就不可行，网民通过谷歌搜索出了对自己身心造成负面影响的内容，在丝毫不谴责内容源头的基础上，将罪魁祸首降临于搜索引擎上，这不但古怪得很，而且根本就是逻辑混乱。

2、接受信息之权利

我反对网民通过用“证明百度也能够搜索出色情”的方式来为谷歌说话，因为这不是能否搜索出色情信息的问题，而是一个成年人是否有权自由获得信息的问题。央视用来旁证谷歌有害的是一名大学生，而我们都知道，大学是允许自由恋爱的，也包括做爱，假如只是在网上看到别人做爱的画面和镜头就神情恍惚，那么那些身体力行享受爱情欢愉甜蜜的大学生，岂不是都要茶不思饭不想、精虫上脑迸裂而亡？

3、新闻原则之践踏

当你要对几亿人编造一个明知会让他们不高兴的故事之前，一定要串供到万无一失的地步，你不会还不知道“人肉”的威力吧？

那位接过张殊凡衣钵、面对央视侃侃而谈笑风生的天之骄子，恐怕不曾料到，他会因为充当帮助央视圆谎的道具，而完全的，彻底的，毁掉了自己的名声，以及道德评价。

我们或许会同情张殊凡，因为她的年龄太小，分辨能力尚不足以应对这个复杂的社会，可能听到老师的教唆后就去扮演了那个在查学习资料时看到“很黄很暴力”内容的角色，是坏大人们利用了孩子的童真。

但我们不会同情高也，因为他是一个心智健全、拥有足够辨别能力的成年人，而当网民们人肉出他在校内的个人主页、在新浪的个人博客，看到他那叫人作呕的叙述：“中央电视台，估计这一辈子为其跑腿也不过这一次，……我觉得卖身到央视何尝不是我的愿望，完全不觉得害怕，而简直就是渴望。大家说央视很官方，我不管那么多，现实一点来讲，有银子就足够了。……”没有任何一个人会谅解这么一个朝着恶性体制奴颜婢膝、主动献身的说谎者。

换而言之，鄙人现在神情恍惚，执迷不悟的认为：既然你敢于对着全国行使蒙骗之事，那么我也很乐意侵犯你的隐私权，让你明白作恶的代价和后果。

----------------------------------------------------------------------------------------------

高也在校内的个人主页：http://status.xiaonei.com/getdoing.do?curpage=0&id=222637323

已注销？没事，这里有在他注销之前的言论存档及截图：

“用事实说话，焦点访谈。。。选题请进。”【暴露其是焦点访谈内部员工的决定性证据】

“做一个积极的纯粹的富有理想的身体健康的优秀中国大学本科生”【身体健康乃至心理健康者，可是不会谈性色变的哦】

----------------------------------------------------------------------------------------------

高也在新浪的个人博客：http://blog.sina.com.cn/gaoye007

已删光？没事，我们有网页快照和截图：

“中央电视台，估计这一辈子为其跑腿也不过这一次，还是要报以认真的态度。罗京走了，悲痛也许只是一阵子的事情，但电视台还要运转，我们这些新鲜血液或许能促进一下血液循环。之前有个同学说害怕被卖身到央视，我觉得卖身到央视何尝不是我的愿望，完全不觉得害怕，而简直就是渴望。大家说央视很官方，我不管那么多，现实一点来讲，有银子就足够了。再说，官方的东西并不都是不好的。（现在官方好像成了贬义词。）”【浪漫主义和现实主义的完美杂交。】

http://cache.baidu.com/c?m=9d78d513d99907e91afa950d100b8738440197634b968b492cc3933fc23904564711b2e73a77435998927e6504bb0e1cb4ff6c34714137b6e8d5951a83e6c73f2fff666f2c4f9141658244f0dc4652907c8d1bf4ff47baefe735e7a98585d554569b50077982f2dd06434bdd6f874e77bcf8&p=9066d059c5904ea908e2977f4742&user=baidu

“到了北京，会有什么样的困难，现在想都想得到：流落街头，像只小狗；累死累活，像只老牛；受人冷落，像只无辜的蚂蚁。不过，实习就是这样，未来就是这样，当你有资格奚落别人，指使别人，冷眼对人的时候，才会领悟到这是多么顺利成长的事情，不过现在，只能把这些困难看成必须承受的不公。”【你没有想到自己现在的遭遇吧？】

http://cache.baidu.com/c?m=9d78d513d99907e91afa950d100b8738440197634b968b492cc3933fc23904564711b2e73a77435998927e6504bb0e1cb4ff6c34714137b6e8d5951a83e6c73f2fff666f2c4f9141658244f0dc4652907c8d1bf4ff47baefe735e7a98585d554569b50077982f2dd03544fdd6f874e77bcf8&p=84759a43dd9117ec0be293344549&user=baidu

----------------------------------------------------------------------------------------------

高也的女朋友的博客：http://blog.sina.com.cn/871224zzy

我不太赞同在批评一个人的时候将战火蔓延到他的周遭去，但是我也没有想到，如此纯情的一名大学生，竟然、竟然是有女朋友的！有女朋友，这不是意味着、意味着他们两人有可能牵过手！？哎呀，不要说了啦，羞死人啦！高也哥哥不会是这么邪恶的人的啦！

博客范文一篇：

“也哥哥走了(2009-06-08 22:04:17)

2009年5月8日，也哥哥去北京啦！

说好不哭的，到最后关头了还是哭了。我真应该去送送他的。

好想他啊！昨天也哥哥帮妹妹买了一个圆圆书包，好乖哟，妹妹肯定会喜欢的！妹妹一定要好好学习，背上小书包，高高兴兴去学校！

据说中央电视台要进行改革，以后风格会改很多，将是十多年以来对包括新闻联播在内的新闻节目做出重大改革，我希望乖乖能学到很多东西，真的希望乖乖可以把这些东西记下来，会很有用的。

乖乖说，我们以后还是去媒体吧！我觉得媒体也很不错的。要是我们都能进的话就好了，真的。

乖乖说，以后有钱了就买张大床，铺粉红色的床单，蓝色的墙。

我还要弄一个小毛毛在上面耍，我好打他！哈哈！”

网友经典回复：

“你也哥这么纯洁你就别说这些了..看到这些我会心神不宁的”

“你们这样的革命情侣 也需要性生活吗”

“也嫂嫂近来是否心神不宁？”

“冒昧打听一下 也哥哥那么纯洁 他怎么满足你啊”

“你家也哥哥上电视罗，哈哈。但愿他真的像在电视上说的那样，是个纯洁的人。你俩在纯洁的大床上，没能力做任何低俗的事情。哈哈。”

----------------------------------------------------------------------------------------------

最后，友情揭露央视要肃整谷歌的原因：

图1、图2

----------------------------------------------------------------------------------------------

另，根据小道消息，为避免被殃及池鱼，百度决定启用新型技术“全频带马赛克干扰”来屏蔽其搜索结果中可能包含的色情信息，效果图如下：

但是，有试用女性反映，在受到“全频带马赛克干扰”保护的百度搜索页面上，依然看到了令她“心神不宁”的信息，举报页面如下：

阅读全文...

Why Free Software has poor usability, and how to improve it

When I wrote the first version of this article six years ago, I called it “Why Free Software usability tends to suck”. The best open source applications and operating systems are more usable now than they were then. But this is largely from slow incremental improvements, and low-level competition between projects and distributors. Major problems with the design process itself remain largely unfixed.

Many of these problems are with volunteer software in general, not Free Software in particular. Hobbyist proprietary programs are often hard to use for many of the same reasons. But the easiest way of getting volunteers to contribute to a program is to make it open source. And while thousands of people are now employed in developing Free Software, most of its developers are volunteers. So it’s in Free Software that we see volunteer software’s usability problems most often.

That gives us a clue to our first two problems.

1. Weak incentives for usability. Proprietary software vendors typically make money by producing software that people want to use. This is a strong incentive to make it more usable. (It doesn’t always work: for example, Microsoft, Apple, and Adobe software sometimes becomes worse but remains dominant through network effects. But it works most of the time.)
   With volunteer projects, though, any incentive is much weaker. The number of users rarely makes any financial difference to developers, and with freely redistributable software, it’s near-impossible to count users anyway. There are other incentives — impressing future employers, or getting your software included in a popular OS — but they’re rather oblique.
   Solutions: Establish more and stronger incentives. For example, annual Free Software design awards could publicize and reward developers for good design. Software distributors could publish statistics on how many of their users use which programs, and how that number is changing over time. A bounty system could let people pay money in escrow for whoever implements a particular usability improvement. And distributed version control could foster quicker competition: distributors could choose not just which application to ship, but also which variant branch of an application, with usability as a factor in their choice.
   
2. Few good designers. Some musicians are also great composers, but most aren’t. Some programmers are also great designers, but most aren’t. Programming and human interface design are separate skills, and people good at both are rare. So it’s important for software to have dedicated designers, but few Free Software projects do. Some usability specialists are employed by Free Software vendors such as Mozilla, Sun, Red Hat, and Canonical. But there aren’t many, and skilled volunteer designers are even harder to find.
   Solutions: Provide highly accessible training materials for programmers, and volunteer designers, to improve the overall level of design competence. Foster communities that let programmers collaborate with usability specialists. And encourage Free Software projects to have a lead programmer, a lead human interface designer, a help editor, and a QA engineer, these being separate people.
   

But why is there a shortage of volunteer designers in the first place? That brings us to the third problem.

3. Design suggestions often aren’t invited or welcomed. Free Software has a long and healthy tradition of “show me the code”. But when someone points out a usability issue, this tradition turns into “patches welcome”, which is unhelpful since most designers aren’t programmers. And it’s not obvious how else usability specialists should help out.
   Solution: Establish a process for usability specialists to contribute to a project. For example, the lead designer could publish design specifications on the project’s Web site, and invite feedback on a Weblog, wiki, or mailing list. The designer could respond courteously to design suggestions (even the misguided ones). And the project maintainer could set up an editable issue tracker, instead of an append-only bug tracker — making it easy to refine, approve or decline, and prioritize implementation of design suggestions in the same way as bug reports.
   

So why do programmers respond differently to usability suggestions than to more technical bug reports?

4. Usability is hard to measure. Some qualities of software are easily and precisely measured: whether it runs at all, how fast it starts, how fast it runs, and whether it is technically correct.
   But these are only partial substitutes for more important qualities that are harder to measure: whether the software is useful, how responsive it feels, whether it behaves as people expect, what proportion of people succeed in using it, how quickly they can use it, and how satisfied they are when they’re finished.
   These human-related qualities can often be measured in user tests. But doing that takes hours or days that volunteers are unwilling to spend. User tests are usually low-resolution, picking up the big problems, but leaving designers without hard evidence to persuade programmers of the small problems. And even once a problem is identified, a solution needs to be designed, and that may need testing too.
   Without frequent user testing, volunteer projects rely on subjective feedback from the sort of people devoted enough to be subscribed to a project mailing list. But what these people say may not be representative of even their own actual behavior, let alone the behavior of users in general.
   Solutions: Promote small-scale user testing techniques that are practical for volunteers. Develop and promote screen capture, video recording, and other software that makes tests easier to run. Encourage developers to trust user test results more than user opinions. And write design guidelines that give advice on the common small problems that user tests won’t catch.
   

The lack of dedicated designers, in turn, contributes to three cultural problems in Free Software projects.

5. Coding before design. Software tends to be much more usable if it is, at least roughly, designed before the code is written. The desired human interface for a program or feature may affect the data model, the choice of algorithms, the order in which operations are performed, the need for threading, the format for storing data on disk, and even the feature set of the program as a whole. But doing all that wireframing and prototyping seems boring, so a programmer often just starts coding — they’ll worry about the interface later.
   But the more code has been written, the harder it is to fix a design problem — so programmers are more likely not to bother, or to convince themselves it isn’t really a problem. And if they finally fix the interface after version 1.0, existing users will have to relearn it, frustrating them and encouraging them to consider competing programs.
   Solution: Pair up designers with those programmers wanting to develop a new project or a new feature. Establish a culture in Free Software of design first, code second.
   
6. Too many cooks. In the absence of dedicated designers, many contributors to a project try to contribute to human interface design, regardless of how much they know about the subject. And multiple designers leads to inconsistency, both in vision and in detail. The quality of an interface design is inversely proportional to the number of designers.
   Solution: Projects could have a lead human interface designer, who fields everyone else’s suggestions, and works with the programmers in deciding what is implementable. And more detailed design specifications and guidelines could help prevent programmer-specific foibles.
   
7. Chasing tail-lights. In the absence of a definite design of their own, many developers assume that whatever Microsoft or Apple have done is good design. Sometimes it is, but sometimes it isn’t. In imitating their designs, Free Software developers repeat their mistakes, and ensure that they can never have a better design than the proprietary alternatives.
   Solution: Encourage innovative design through awards and other publicity. Update design guidelines, where appropriate, to reflect the results of successful design experiments.
   

Other reasons for poor usability exist regardless of the presence of dedicated designers. These problems are more difficult to solve.

8. Scratching their own itch. Volunteer developers work on projects and features they are interested in, which usually means software that they are going to use themselves. Being software developers, they’re also power users. So software that’s supposed to be for general use ends up overly geeky and complicated. And features needed more by new or non-technical users — such as parental controls, a setup assistant, or the ability to import settings from competing software — may be neglected or not implemented at all.
   Solutions: Establish a culture of simplicity, by praising restrained design and ridiculing complex design. And encourage volunteer programmers to watch their friends and families using the software, inspiring them to fix problems that other people have.
   
9. Leaving little things broken. Many of the small details that improve a program’s interface are not exciting or satisfying to work on. Details like setting a window’s most appropriate size and position the first time it opens, focusing the appropriate control by default when a window opens, fine-tuning error messages and other text to be more helpful, or making a progress bar more accurately reflect overall progress. Because these things aren’t exciting or satisfying, often years go by before they get fixed. This gives users a general impression of poor design, and that may in turn discourage usability specialists from contributing.
   Solution: When scheduling bug fixes, take into account how long they will take, possibly scheduling minor interface fixes earlier if they can be done quickly. Involve interface designers in this scheduling, to guard against usability flaws being downplayed because “it’s just a UI issue”.
   
10. Placating people with options. In any software project with multiple contributors, sometimes they will disagree on a design issue. Where the contributors are employees, usually they’ll continue work even if they disagree with the design. But with volunteers, it’s much more likely that the project maintainer will agree to placate a contributor by adding a configuration setting for the behavior in question. The number, obscurity, and triviality of such preferences ends up confusing ordinary users, while everyone is penalized by the resulting bloat and reduced thoroughness of testing.
    Solution: Strong project maintainers and a culture of simplicity. Distributed version control may help relieve the pressure, too, by making it easier for someone to maintain their own variant of the software with the behavior they want.
    
11. Fifteen pixels of fame. When a volunteer adds a new feature to a popular application, it is understandable for them to want recognition for that change — to be able to point to something in the interface and say “I did that”. Sometimes this results in new options or menu items for things that should really have no extra interface. Conversely, removing confusing or unhelpful features may draw the ire of the programmers who first developed them.
    Solutions: Provide alternative publicity, such as a Weblog, for crediting contributors. Establish design review of code changes that affect the human interface. Regularly review the entire interface, asking “Do we really need this bit”.
    
12. Design is high-bandwidth, the Net is low-bandwidth. Volunteer software projects are usually highly distributed, with contributors in different cities or even different continents. So project communications are mostly plain text, in e-mail, instant messaging, IRC, or a bug tracking system. But interaction design is multi-dimensional, involving the layout and behavior of elements over time, and the organization of those elements in an overall interface.
    When developers are in the same room, they can discuss interaction design using whiteboards, paper prototypes, spoken words, and gestures. But on the Internet, these often aren’t available, making discussions much slower and prone to misunderstandings.
    Solutions: Develop and promote VoIP, video chat, virtual whiteboard, sketching, and animation software that allows easier communication of design ideas over the Internet. And whenever possible, hold physical meetings for developers to collaborate in person.
    

Finally, a few problems are specific to Free Software development.

13. Release early, release often, get stuck. The common practice of “release early, release often” can cause poor design to accumulate. When a pre-release version behaves a particular way, and testers get used to it behaving that way, they will naturally complain when a later pre-release version behaves differently — even if the new behavior is better overall. This can discourage programmers from improving the interface, and can contribute to the increase in weird configuration settings.
    Solution: Publish design specifications as early as possible in the development process, so testers know what to expect eventually.
    
14. Mediocrity through modularity. Free software hackers prize code reuse. Often they talk of writing code to perform a function, so that other programmers can write a “front end” (or multiple alternative “front ends”) to let humans actually use it. They consider it important to be able to swap out any layer of the system in favor of alternative implementations.
    This is good for the long-term health of a system, because it avoids relying on any single component. But it also leads to a lack of integration which lessens usability, especially if the interfaces between the layers weren’t designed with usability in mind.
    For example, most terminal commands do not provide information on how complete a process is, or estimate how much time is remaining. This is traditional behavior in a terminal, but in graphical software, progress feedback is crucial. If a graphical utility is developed merely as a “front end” to the terminal command, it can’t easily provide that feedback.
    Solution: Design an example graphical interface first, so that interface requirements for the lower levels are known before they are written.
    
15. Gated development communities. When you do anything on a computer system you are relying on software from several different development teams. For example, if you print this Web page to show someone else, that task will involve not just the Web browser, but also a layout engine, a window manager, an interface toolkit, a variety of other libraries, a graphical subsystem, a printing subsystem, a printer driver, a filesystem, and a kernel, almost all of these implemented by separate teams. Oten these teams don’t communicate with each other frequently. And unlike their proprietary competitors, they nearly all have different release cycles. This makes usability improvements difficult and slow to implement, if those improvements involve coordinating changes across multiple parts of the system.
    Solutions: Free Software system vendors can coordinate cross-component features like this, if they have employees working on all relevant levels of the software stack. And volunteer contributors to different software layers can meet at conferences arranged for that purpose.

That’s a long list of problems, but I think they’re all solvable. In the coming months I’ll discuss examples of each of the solutions, and what I’m doing personally to help make Free Software a success.
阅读全文...

Goobuntu —— Internet的老新闻

　　【eNet硅谷动力消息】美国互联网搜索巨头Google公司正在拒绝承认它有关于要发布一款基于Linux的操作系统Ubuntu的计划。Ubuntu是一款能够与微软公司的Windows XP操作系统竞争的开放原代码操作系统，它是由南非的企业家马克开发的。

　　据Google公司的代表桑娅表示，Google公司在回应有关媒体报道的它将发布这一种被称为Goobuntu的Ubuntu版本的操作系统时指出：尽管我们在内部使用Ubuntu，但我们并没有将它向外部发布的计划。

　　然而，虽然Google公司已经否认了自己有任何进入操作系统市场的计划，但由于受最近Google公司发布的与微软公司产品竞争的软件的影 响，新闻媒体已经对其这一传言进行密切关注了。据Frost & Sullivan公司的分析师穆库表示，Google公司正在向诸如MSN等微软公司的许多服务性产品发起挑战。据目前的传闻称：Google公司正在进 入操作系统领域。一旦它发布了Goobuntu，那么，在软件领域，它将与微公司成为针锋相对的一大竞争对手。据穆库表示，Google公司上个月在美国 拉斯维加斯举行的电子展会上发布Google Pack是一个具有重大意义的举措，在这一Google Pack中包括了Google Talk、Google Desktop、Mozilla Firefox、Trillian、RealPlayer和Picasa。我们这些分析家们过去曾经认为Google公司可能会在未来的四年内进入软件领 域，但目前来看似乎比我们预计的更快。这一情形的发展是很有趣的，这是因为：如果Google公司对Goobuntu的定价比Windows XP操作系统低，那么许多人都将使用Goobuntu。如果这一价格低至20美元，那么象印度和中国等国家具有高科技背景的用户就会使用Goobuntu。我们就会看到发展中国家的人们将购买廉价计算机，然后加载Goobuntu。

　　另外，穆库还摒除了有关对Google公司将免费提供Goobuntu软件的传言。据他表示：我认为Google公司将对这款产品收费，尽管 到目前为止，其业务模式仍然是向广告主而不是最终用户收费。然而，据我认为，Goobuntu的价格将会是象征性的，这样许多人就会购买它，就我本人而 言，我就对运行它感兴趣。他还表示，Google公司正在成为微软公司最大的竞争对手，在软件开发方面，它能够负担起巨额投资，在人才方面，它拥有具有高 才能的开发人员，而且还在从微软公司那里高聘有才能的软件设计师。

　　据穆库表示，然而，微软公司被许多计算机用户看作是正统的，而Google公司则不然。如果Google公司以Linux操作系统为契机打进 软件市场，那么，它就会在反微软公司的计算机用户心中树立一面旗帜。开放源代码软件存在的其中的一个问题就是它通常是免费的，它意味着开发人员仅仅能够在 他们的业余时间内进行开发活动。但如果Google公司投巨资进行开发开放源代码软件，那么就会大大加快它上市的速度。
阅读全文...

Gimmie - Gnome的下一代开始菜单

　　Gimmie从性质上来看，似乎更像是Gnome的一个系统插件。它的作用是给Gnome用户在菜单的使用和计划提供更多的选择。因为Gnome是一个Network Object Module性质的操作系统，在菜单、工具条的创建和使用上已经有很大的自由度，但是传统的条状菜单已经让喜欢尝鲜的用户感到乏味，同时树结构的菜单也有其固有的缺陷。不过Gnome菜单还好，只允许有一层目录。不过更小的自由度带给大家的肯定是更多的不方便。

　　于是Gimmie横空出世了，这个带有标准的.Net特性的软件，和Mono居然毫无关联？（不过个人对Mono好感缺乏，现在很多小公司都利用Mono Developer开发商业软件了，真是让人郁闷）它首先提供了类似于Gmail的功能，对软件快捷方式的搜索但是不排序；强大的分类功能；标签式的管理。这些东西的确在我们工作的时候可以节省很多的时间。而且漂亮的主菜单，看上去比Windows Vista还要拽。Vista不过是把搜索直接整合到了开始菜单中，其实质性的进步太少了；甚至菜单没有换一个样式。看来微软的缺乏诚意之作又要继续我们的审美疲劳了。

　　Gimmie的第一次实际应用，是Novell的Suse Linux Enterprise Edition 10，第一次看到它感觉就是惊艳！
它的下载地址：
www.beatniksoftware.com/gimmie/
不过似乎仅仅有源代码哦！
BTW:似乎Gimmie在发布到0.2.8版本之后，就一直处于停滞开发的状态。

阅读全文...

Linux to go！

　　GPE is GPE Palmtop Environment!我个人认为也可以说是Gnome Palmtop Environment!毕竟，这个掌上操作系统和Gnome太相似了，简直如出一辙。而且在Gnome的官方网站，GPE的新闻也在频频曝光，看样子，它和Gnome也有摆脱不了的联系。
　　虽然Linux之父一直在炮轰Gnome，支持KDE。但是有一点他不容否认的是，KDE使用了QT的代码，而QT不是GPL协议发布的，而是需要付费的私有代码。现在它可怜开源事业，如果有一天它翻脸不认人，那么kde就不存在了。所以现在，大家在使用KDE桌面的时候，看到的版权信息都写着：基于GPL v2或者v3发布，软件使用者只可以使用本软件，但是没有权利修改。这样的做法让开源变成了空谈，只能看，不能修改，不能重新发布，还有什么意义呢？所以，在这个层面上，我一直是Gnome的忠实支持者。而且，Gnome并没有让我感到失望，而是飞速发展，到2.10版本，已经在任何一个方面都不逊于KDE了。Gnome is GNU's Network Objective Module Environment，GNU的网络模块环境，就是系统在内核以外都是以模块的形式添加进去的，这样保证了发展的最大自由度和想像度。以这样的理念可以使系统发展的更迅速。
　　显然，GPE的出现证明了在下的观点。
　　GPE的官方网站：
http://gpe.handhelds.org/
http://gpe.linuxtogo.org/
　　在Linux to go，可以看到更多的GPE的相关截图。
以前的日子，在handheld领域，一直是Windows CE和Palm OS的天下，而现在Palm已经是昨日黄花，从treo 700开始向Windows妥协。而Linux在中国是一个彻底的新生事物，在handheld上更是新得不得了。虽然由于它的商业模式还是值得商榷，但是在技术上已经相对成熟。相信，以后在使用handheld的日子里，会有更多的选择。
　　不过应当重申的是，大家应该看到更多的是Linux的技术优势而不单单是成本优势。看到成本优势只能造成更多的掠夺和滥用，而看到技术优势，我们才能对Linux和GPE的发展有所贡献，对他们有所贡献，他们才会有所发展，他们有所发展才能为我们创造更多的价值和选择。
阅读全文...

Linux将可以跟Google talk 语音通话了

　　Jabber/XMPP协议进行了语音方面规范的扩展，Google Talk 也公布了语音接口API，多个新的开源项目即将启动。

去看看 www.jabber.org 的头条新闻
－－－－－－－－－－－－－－－－－－－－－－－－－－
第一个：Client端的
NewsForge reports that FreeSWITCH, an open-source softswitch project, has added support for interoperability with Google Talk and other XMPP/Jingle applications.

http://newsvac.newsforge.com/newsvac/06/04/13/1435210.shtml

第二个：服务器端交换
Dave Greenfield of Networking Pipeline has posted some detailed news about the combination of the Jingle XMPP extensions and the open-source Asterisk PBX application, along with informed speculation about what it will mean for enterprise voice-over-IP.
http://www.networkcomputing.com/blog/dailyblog/archives/network_infrastructure/index.htmlarchives/2006/04/asterisk_server.html
阅读全文...

微软开了用Linux需收费之先河！

Linux电脑操作系统的支持者，准备反对微软最近签署的一项协议，因为该协议首次确立了使用Linux要向微软支付费用的原则。不久前微软与Linux 软件提供商之一 Novell公司签署系统兼容协议，按照协议，Novell向微软支付了一定数额的费用，以保证微软不会以侵犯专利权为由起诉Novell的客户。

　　而最大的Linux软件提供商Red Hat公司，并未与微软签署这样的协议，可能面临与微软进行长期的法律诉讼战，这将使用户离开Red Hat而投奔Novell。虽然Linux是免费的，但提供商提供了包装、文档，最重要的是安装和维护服务，因此失去用户就意味着失去了收入。纽约软件自 由法律中心的创始董事、哥伦比亚法学院的教授伊班-摩伦（Eban Moglen）认为，只有两种结果，一是客户离开Red Hat投奔Novell以保证安全，另一个是Red Hat被迫与微软签署同样的协议。

　　摩伦称，微软的协议绕过了适用于Linux 和其他免费软件的GNU通用公共许可。他与其他人已经开始修正该许可，通过承诺不起诉以弥补漏洞，如微软给予Novell的承诺，所有软件自动提供给任何 人。这可有效遏止微软强加协议，并保证了用户不会遭到起诉。摩伦表示，这种条款应该能获得开源社区的同意，在数周或数月后就会推出。

　　按照微软与Novell 的协议，双方同意不起诉对方的客户，微软支付了3.48亿美元而Novell支付微软4000万美元。微软透露，在Linux上拥有某些技术的专利权，但 从未确切说出是哪些专利技术。微软CEO鲍尔默曾表示，如果用户不从Novell购买 Linux，他们将面临麻烦。他表示，用户可能会向提供商发出这样的疑问“有必要为使用微软的专利负责吗”，微软的回答是肯定，如果用户直接下载非 SUSE的Linux，他们应该小心了。

　　不知道Novell是怎么想的，简直就是大脑进水了！他正在帮助Linux的敌人在瓦解Linux阵营。如果Suse Linux合理合法地成为私有软件，那么其他版本的Linux肯定会在不久的将来遭到Microsoft的版权起诉，因为“它们在Microsoft未经授权的情况下，使用了Microsoft Linux的私有代码。”似乎这个起诉理由在以后会很有说服力啊！
阅读全文...

碰到了个好黑客

　　我和朋友们一起开了一个论坛，用的是PHPWind。有一天突然发现论坛登录不上了，写着几个字：PHPWind论坛最近出了一个很大的漏洞，我们已经帮您关闭了论坛。请到我们的网站下载PHPWind相关补丁。
　　我开始以为这是个恶作剧，对这个擅自关闭我论坛的家伙深恶痛绝。而且他还修改了我的登录密码，搞得我现在还无法修改回去。我到了他的网站，本想骂他一顿，却找不到留言的地方，败兴而归。
　　不过３个小时后，我的一个论坛版主在QQ上告诉我，国内N多打开的PHPWind论坛都被黑了，而被关闭的却没事。当时不由得又对这位好管闲事的黑客产生了万分的感激。但是，由于我当时太气愤，把那位仁兄在我网站留的所有墨宝都删除了，现在想表达感激之情也没地方了，可惜啊。
阅读全文...

McAfee AntiVirus Updated.

　　终于，在Windows Vista即将走向大众的时候，McAfee Antivirus Enterprise 也推出了它支持Windows Vista的新版本：8.5i。
　　8.5i 在外观上没有多大变化，毕竟企业版本的软件这个方面不是卖点。但是功能上却强大了很多：
　　1, 推出了32位和64位操作系统的两个版本。
　　2, 可以同时作为服务器和客户端使用。
　　3, 内置了新一代的5100杀毒引擎，连版本号都和以前不一样了。这个5100和8.0i的5100可不是一回事情。
　　4, 第一次拥有了多语言支持！
　　5, 万众期待的对Windows Vista的完美支持。
　　看来McAfee还是保持着AntiVirus市场的领袖风范，虽然因为Vista不兼容8.0i，McAfee和Microsoft没有少干仗，^_^
　　最后，提供一下它的下载地址吧：
　　http://www.crsky.com/soft/9071.html
阅读全文...