powered by Jive Software

Stricter MUC controls?

As we deploy Openfire at MIT, we’'re also looking into ways multi-user chats can be integrated into other aspects of our infrastructure. Here are some features we would find desirable:

  • The ability to run more than one MUC server with different policies on each, or alternatively the ability to run Openfire purely as a MUC server with no c2s or s2s. For examples, chatrooms for classes could live in a separate namespace which is set up with tighter controls than the generic conference server.

  • The ability to allow only members of a particular domain to create chatrooms.

  • The ability to allow only members of a particular domain to enter chatrooms, either on a per-chatroom basis or globally.

  • The ability to restrict nicknames to match usernames, or something along those lines. Right now it may be possible to do this by configuring a chatroom “Members only” and “Only login with registered nickname,” but then you have to set up nicknames for each user. Moreover, as far as I can tell you can’‘t set up registrations for other users as a chatroom owner, and you can’'t even do this via the admin console; you would have to directly edit the database.

Thanks.

We are looking to deploy Openfire at University of Pennsylvania, and we are looking for this functionality as well:

The ability to restrict nicknames to match usernames, or something

along those lines. Right now it may be possible to do this by

configuring a chatroom “Members only” and "Only login with registered

nickname," but then you have to set up nicknames for each user.

Moreover, as far as I can tell you can’'t set up registrations for

other users as a chatroom owner, and you can’'t even do this via the

admin console; you would have to directly edit the database.