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:
"Jabber.org 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 mozilla.org 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 mozilla.org 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 http://jabber.org/. If you have any questions or would like to contribute to this, please feel free to contact the Jabber team at firstname.lastname@example.org."
Awesome news. An IRC client and a RT-messaging client, both done third-party! Woohoo!
#21 Features = Complexity
Wednesday September 8th, 1999 12:37 PM
You are replying to this message
By adding features, you also increase the complexity of the product. From the viewpoint of a IT manager, if you don't take steps to manage that complexity - either through being able to turn off/disable features, or by creating plugins that act more like virtual features that are perhaps downloaded as needed/requested - you are making the product harder to manage. Also, as Microsoft continues to prove, the more features you provide, the more oportunities for security risks - we should be allowed to manage the level of risk we want to expose us (or our companies) to. I am not impressed with the security history of ICQ, and I don't want to bring that history to the new browser. I am not trying to stifle the creativity and enthusiasm of the development community, but please do not assume that everyone wants or needs every set of features. I for one would like to be able to disable any features other than browser (and maybe email).