Each of these nine tasks takes a specific object (or set of objects) as its starting point and tries to locate related objects of the same or of a different type. The colored squares indicate the four tasks that are already supported to some degree. I will briefly describe each of the nine tasks below, list in order of perceived importance and potential impact on usage of CiteULike. Of course, this is completely dependent on the users of CiteULike, so comments and suggestions are most welcome!

Upgrades to the web are incremental. Instead of requiring a complete overhaul of your technical infrastructure, or radical changes to existing behaviors, the web tech that wins is usually the sort of thing that can be adopted piecemeal, integrated as needed or as a normal part of updating one's websites or applications.

Understanding new tech needs to be a weekend-sized problem. For a lot of web developers, long before they start integrating a new protocol or platform into their work, they hack together a rough demo over a long weekend to make sure they truly grasp how it works. And a weekend-scale implementation on a personal site usually translates roughly into a 90-day implementation cycle in a business context, which is a reasonably approachable project size. (In tech, three days in personal effort often translates to three months of corporate effort.)

There has to be value before everybody has upgraded. This is basically a corollary to Metcalfe's Law. While we know networks increase in value as they add more nodes, the nature of web tech is that, in order to be worthwhile, it has to provide value even if the people on the other end haven't upgraded their software or web browsers or clients or servers. Otherwise you're shouting into an empty room.

You have to be able to understand and explain it.

What's new about Wave?
* Powerful realtime collaboration features
* Unlimited versioning of content
* Built around robust XMPP protocol
* Combines chat, document editing, and message threading — wikis + blogs + comments + IM
* Delivered as a very polished rich user interface
What makes Wave great?
* Federation (XMPP)
* The robot protocol (JSONRPC)
* The gadget API (OpenSocial)
* The wave embed API (Javascript)
* The client-server protocol (As defined by GWT)

Pushbutton technologies have been created and advocated by some of the most credible and experienced developers of social web technologies. Here's a brief overview of the impressive pedigree of these components:

• PubSubHubBub was co-created by Brad Fitzpatrick and Brett Slatkin of Google. Brad was founder of LiveJournal, and created or co-created fundamental social web technologies like Memcached, OpenID and more.
• XML-RPC update pings, RSS and the RSS Cloud ideas were pioneered by Dave Winer, who has been actively developing open implementations of each of these technologies.
• Web Hooks have been evangelized by Jeff Lindsay, and have been deployed by a variety of different companies and platforms which all independently developed the technique.

Conducting research online can be much simpler when working at an institution with extensive resources. Online databases are particularly useful, but can often be a hassle to use off-site, owing to the need to log into a proxy system. When your institution subscribes to sites like JSTOR.org, you can access them from your institution's network with no trouble at all. Once you're off-site, though, it gets more complicated. You might find that you can no longer download full-text PDFs or even access the database at all. This is because the site can no longer tell that you are affiliated with your institution and should have access. As such, you need to access the database through your institution's proxy. This is to say that any requests you send to the site will get routed through your institution's network.

Usually, this is done by accessing the database through your institution's site, often the library site, specifically. When you attempt to access the database, you will be redirected to a proxy login page. Once you enter the appropriate credentials, you can use the database as though you were on-site. All this sounds like a bit of a pain, though, right?

Zotero can streamline this whole process by managing the complicated rewriting of URLs involved. When Zotero detects that you are using an institutional proxy to access a particular site, it will ask if you want to remember it in the future. If you agree, from then on, Zotero will then automatically use the proxy for matching URLs. You should be routed through the proxy login site if you're not already logged in, then you can access the database as you normally would.

Zotero users should be able to make complete use of the proxies feature without editing any preferences. By default, Zotero will prompt you to store the proxy and then route you through the proxy automatically and without further input. The default behavior can be changed, though. You can set whether Zotero automatically prompts you to store proxies it detects and whether it should request permission to route requests through any stored proxies.

Proxies can be added manually by clicking on the + button in the Proxies preference tab. From there, you can specify the URL of the database being accessed under hostname and the URL scheme of the proxy. By selecting the Multi-Site option, you can redirect multiple sites/databases through a single proxy.

Normally I used the Greasemonkey script originally from Andrew Perry, but Zotero has a better automated feature to track ezproxy urls and it keep updating the list of proxies by itself.

Comments can not only expose the authors but editors and reviewers as well. Watch out Addendum and Addendum to Addendum.