RT Messaging Coming To Mozilla

Tuesday September 7th, 1999

Our third news item of the day is again about third-party Mozilla development. Jeremie Miller writes in with this announcement about Jabber, a universal, real-time messaging client:

" is announcing an effort to create a universal real-time messaging client integrated with Mozilla.

The Jabber team has been designing and developing an architecture for real-time messaging that is fully open, utilizes an XML based protocol, will support the IETF/IMPP developments, and can bridge transparently to 3rd party messaging services such as IRC, ICQ, and AIM.

We are very excited to join the two open-source efforts and create an integrated Jabber client for Mozilla. The combination will significantly enhance the communication power and functionality available within the Mozilla browser and create a standard and powerful client for Jabber.

The initial Mozilla-based client is in its early stages and will exist within the sidebar. We are working with the Mozilla team to contribute our development into the main Mozilla codebase and utilize the site for announcements, FAQs, and other documents. Over the next few weeks the Jabber client should be available in CVS and the real-time messaging area on updated. We are anticipating a working client and some test servers to be online by the end of September.

If anyone is interested in learning more about Jabber, please visit If you have any questions or would like to contribute to this, please feel free to contact the Jabber team at"

Awesome news. An IRC client and a RT-messaging client, both done third-party! Woohoo!

#17 features != bloat

by Anon

Wednesday September 8th, 1999 10:51 AM

You are replying to this message

It's clear that users demand streamlined browsers. When Netscape shipped Communicator 4.0, the intention was only to ship the combined Navigator+Composer+Messenger (Dogbert) client . Only later, after user demand, was the Messenger-ectomy performed, and the Navigator (known internally as Ratbert) was release on its own.

So, why was a browser-only solution needed? Possibly because the huge download size of the full communicator package (15,800kb) was huge, and people would rather download the smaller, leaner, ratbert package (10,200kb).

Since that was 2 years ago, and modem speeds have gotten faster, and cable modems, and DSL are coming, download speed is not really a factor any more.

I think you were misunderstanding the point of the 'streamlined browser' - it doesn't mean feature-starved. It means streamlined in terms of code.

I think there's a market for a 'lean browser' - minimal footprint but there is a BIGGER market for a browser with as many plugins as possible included out of the box.

I *hate* downloading and installing plugins - have you tried the latest Quicktime 4 thing. It's a mess. You want users to be able to use all the latest mime-types out of the box - there's some great fractal image compression stuff that I'd love to see more widely deployed, and Mozilla can help promote it.

Remember that mozilla is not just a browser, - it's a great framework for building other applications - and this IRC/messaging stuff is a great example. Plus, you get to be x-platform practically for free.

In the end, it'll be up to AOL to choose the components in its distribution, and who knows - depending on some $$$$ spent on martket research, it may develop two or more versions of the package. But if they only include the bare-bones browser, you can bet that someone, somewhere will come up with the all-signing all-dancing version.