geonames.org 是一个关于地理信息的宝库。除了提供以 Creative Commons 方式授权的数据库的自由下载之外，还有非常强大的 Web Services 可用。

比如，各类城市和机场的各种名字，代码及经纬度都可以在这个数据库中查到。对我最近在做的一个项目十分有帮助。推荐给大家。[ read more on livid.cn ]

　　使用Google Reader阅读器的用户，在订阅了几百个Feed后，通常都会遇到阅读过载的情况，似乎总有读不完的文章，未读数一直都是1000+，我这里介绍一下我的一些阅读经验，可以减轻并消灭1000+的阅读情况。

　　一、目录分类

　　分类对于高效阅读非常重要，我自己的分类规则包含以下几条：

　　1、严格按照Feed的类型进行分类，不同类型的Feed放在不同目录。

　　2、英文Feed和中文Feed分开。

　　3、每天大量更新的Feed（超过3篇的）用增加一个单独的Tag标记。

　　4、每天必读的Feed也使用另一个单独的Tag标记。

　　二、阅读顺序

　　在Google Reader中设置起始地址为“必读”的Tag，每天阅读的时候，先全文阅读必读的Tag，读完后按照不同类型顺序阅读，大量更新的目录先不要阅读。

　　三、阅读方式

　　对于重要的Feed，应该使用全文阅读的阅读方式（快捷键1），阅读完成后，对于大量更新Feed的目录，建议切换到标题阅读方式（快捷键2），对于标题可以一扫而过，最后再“Mark all as read”。

　　四、善用快捷键

　　使用快捷键是快速阅读的一个好方法，记住一些常用的快捷键，基本上就不会用到鼠标了，对于加快阅读速度很有用。Google Reader的官方博客也总结了一些用户常用的快捷键，列表如下：

Key	Description	Presses
j	next item	1,000.00 milli-Js
n	item scan down	324.18 milli-Js
k	previous item	139.49 milli-Js
m	mark as read/unread	43.91 milli-Js
t	tag item	37.48 milli-Js
p	item scan up	31.30 milli-Js
shift-n	next subscription	23.09 milli-Js
v	view original	17.98 milli-Js
o	expand/collapse item	16.81 milli-Js
s	star item	15.45 milli-Js

　　以上是我的一些使用Google Reader的阅读经验，对于消灭1000+还是比较有效的，如果你有更好的经验或者技巧，请也留言告诉我。

《我是怎么消灭Google Reader的1000+的》的相关评论留言

相关文章：

• Google Reader订户数的扩展  (2008-2-7 19:41:57)
• Google Reader的好友阅读共享很不错  (2007-12-21 21:20:49)
• Google Reader分享和Google Talk集成  (2007-12-15 11:27:38)
• Google Reader推出订阅发现和推荐  (2007-12-1 14:12:04)
• 那不是Google Reader的订阅数  (2007-10-16 0:10:30)
• Google Reader中文版发布  (2007-9-18 15:20:29)

LinuxRen 写道 "1998年2月9日，Bruce Perens第一次向世人公布了“Open Source”这个单词，2008年2月9日是”Open Source”十岁生日。 在最近的一篇文章当中，Bruce Perens对这十年间“Open Source”所取得的进展进行了回顾，对一些大的事件进行了评论，强调OpenSource最重要的是用户，是用户造就了OpenSource。 “Open Source”和Stallman先生的”Free Software”在过去十年当中影响了整个IT，颠覆了人们对“革新”的理解，任何人都可以通过开源社区分享自己的发现。未来的十年将会发生什么变化呢？谁知道。据说未来4年内将会有80%的软件开源。 Bruce Perens同时承认，Microsoft仍是最令人头疼的问题。"

Posted by T.V. Raman, Research Scientist

From time to time, our own T.V. Raman shares his tips on how to use Google from his perspective as a technologist who cannot see -- tips that sighted people, among others, may also find useful. - Ed.

Language barriers can be a primary source of accessibility problems on the web, and automatic translation, though not perfect, provides a useful solution.

We recently made our machine translation technology accessible from within Gmail and Google Talk, which gives mail and IM users instant access to translation capabilities at the point where they might most need them, e.g., when communicating with friends and colleagues around the world. If you find yourself wanting to translate a few words or short phrase, you can IM an appropriate chat-bot to obtain an immediate translation. As an example, the Google translation bot for going from English to Chinese is available as en2zh@bot.talk.google.com. In general, translation bots are named using two-letter codes for the source and target language.

Surfacing machine translation in this manner is a great example of how Web 2.0 mashups bring together useful services to create solutions that are bigger than the sum of their building blocks. I've blogged here in the past about the potential presented by web mashups for users with special needs. Using our work on AxsJAX to inject accessibility enhancements into Web applications, my officemate Charles Chen and I recently augmented Google Talk to produce appropriate spoken feedback when used with adaptive technologies such as self-voicing browsers.

The combination of machine translation, instant messaging and AxsJAX-enabled spoken output produces an interesting result that is obvious after the fact: when I use Google IM to message a translation bot, I now hear the result in the target language. This makes for a very interesting chat buddy -- one who can act as my personal interpreter!

And let's not forget that little translate this page within Google search results. Next time you find that some of the documents in your search results are non-English, try clicking on that translate link. You'll be able to specify the source and target languages to obtain an automatically generated translation. A nice thing about the translated page is that when you follow any links from that document, the newly retrieved document will be automatically translated. Thus, if you find an article in German that matches your query and you're an English speaker, you can translate from de|en (that's German to English using two letter language codes) and as you read the translated English version, following links from that document will result in their being automatically translated to English.