Water Cooler -- AJAX chat for the enterprise
Water Cooler requires Rails 2.1 and the following gems:
- Make sure the required gems are installed ("rake gems").
- Set up your database information in
- Migrate your database.
- Set up which services you want to use in
- Start the server and go
Water Cooler should be fairly straightforward, but there are several main features to know about.
Users and logging in
When a user first logs in, Water Cooler looks for an existing user in the database. For LDAP users, it looks for a user with the same short username. For OpenID users, it looks for the OpenID identity in the username field of the users. If the user isn't found, it creates a new user. On the first login, Water Cooler will also give a user a nickname. For LDAP users, this is the same as the username (however a nice feature would be to check for a nickname LDAP attribute). For OpenID users, the simple registration
nickname parameter is used.
application.yml. For OpenID users it checks the list of OpenID admins in
After login, the user is taken to the list of chat rooms.
In the page footer, there is a line of text that says "You are known as...". By clicking "change", the user can change his or her nickname. The new nickname will appear in the list of room members and before each message posted by the user. To see a user's username (i.e. LDAP username or OpenID identity), just hover over the person's name in the room member list and the tooltip will show the real name.
Users can set an away message indicating that they aren't currently paying attention to the chat. Away messages are listed next to a user's nickname in the member list for each chat room.
When a user is away, all notifications are sticky and stay visible until the user returns from away.
The member list for a chat room shows all of the current members of the room. If a user's nickname is italicized, it means that they are either away, or currently viewing a different chat room. Non-italicized names may be a little misleading however since they may indicate simply that a user was last viewing the room before closing their browser, even if they haven't visited it in weeks.
Administrators and the owner of a room can evict any member of that room. This will boot the member from the room the next time their browser hits the room checking for new messages.
The real power of Water Cooler comes from its keyword notifications system. By default, a keyword is created for the current user's nickname. This means that anytime a user's nickname is mentioned in any chat room the user is a member of, they will receive a notification.
Users can add their own keywords using regular expressions to alert them when words or phrases of interest are mentioned. Also, by adding a keyword of the form
from:nickname and they will receive a notification any time that user speaks in a chat room the current user is a member of.
Notifications are cleared when the user is available and visits the chat room in which the notification occurred.
Tip: Add the keyword
^all: so that room members can say "all: Hello World!" to notify all members of the room.
Please submit bug reports via Lighthouse at http://thadd.lighthouseapp.com/projects/20676-water-cooler/overview.
Aside from the bugs that are already reported at Lighthouse, there are several known issues that don't really warrant their own bugs.
- IE 6 Support - Currently Water Cooler doesn't work with IE 6. This is mostly because IE 6 is a lousy browser, but more specifically, the transparent PNG files don't work in IE 6. Ticket #14 will probably fix most of the IE 6 issues, but I just don't see the value in wasting too much time on it.
- Performance - Water Cooler is a bit inefficient. If you have 15 users, you're going to be getting about 20 requests per second. This is fine for most uses (it's designed for small software teams), but if you want to use Water Cooler to support a much larger audience or if you have real bandwidth/CPU concerns, it needs some enhancement in that area.
- Stale users - There's no cleanup actions to speak of in Water Cooler. This means that if a user logs in once and never comes back, they will remain in all of the chat rooms they were in when they left. For more teams this isn't much of a issue, especially since admins and room owners can kick out the stale users, but if you're going to be using Water Cooler in an environment with a lot of transient users then this problem should be addressed.
Water Cooler is released under the MIT license.