Mucho plugin
John | 2009-02-16, 12:59 Note: This plugin isn’t developed since 2009, but there is a updated version written by mavnn on Github: https://github.com/mavnn/mucho
Mucho is a plugin for the Openfire XMPP server that spawns users and echoes all messages sent to it to a chat room. This might be useful for automated messages that is sent to a Jabber user that needs to be monitored by a group of people. It handles multiple users where each joins a separate chat room.
Mucho is short for “Multi User Conference Echo”. 🙂
Download
- mucho-1.3.0.jar (sourecode in mucho-1.3.0-src.jar)
Added setting plugin.mucho.conferenceService to be able to specify conference service if having more than one. - mucho-1.2.0.jar (sourcecode in mucho-1.2.0-src.jar)
Added setting plugin.mucho.showSenderJID to enable the original JID of the sender to be shown in each message broadcasted by the bot. - mucho-1.1.0.jar (sourcecode in mucho-1.1.0-src.jar)
Added command @sayto, to be able to have bot say stuff. Also added a debug flag to enable/disable verbose log output. - mucho-1.0.1.jar (sourcecode in mucho-1.0.1-src.jar)
Fixed bug that new room wasn’t unlocked. - mucho-1.0.0.jar (sourcecode in mucho-1.0.0-src.jar)
Initial version.
Installation
Rename mucho-[version].jar to mucho.jar and copy it into the plugins directory of your Openfire installation. The plugin will then be automatically deployed. Read the included readme.html for further instructions.
Configuration
The Mucho plugin is configured via Openfire system properties. Read the included readme.html for further instructions.
Example of usage
In this example you have setup a Cruisecontrol build server to announce new builds to a Jabber user (JID).
- Setup Mucho to join the room “cc” by setting the Server Property “plugin.mucho.ids” to “cc”.
- Setup Cruisecontrol to announce to the Mucho user: “cc@mucho.server.com”.
- Join the chat room “cc@confernce.server.com”.
- Tell others that might want to know when cc is announcing a new build to join that chat room.
[…] Läs mer (och ladda ner) här! Vardagen | | Trackback | RSS […]
Released version 1.1.0 with “@sayto command”. Sending “@sayto [somejid] [somemessage]” in the conference will make Mucho bot say [somemessage] to user with [somejid] JID. Also added a debug flag to enable/disable debugging log output.
This is what we needed! One request though- it would be great if it could show the jid of the user that sent the message. Any way to do this?
Hi Sean – I’m pleased to hear that you found it useful and thanks for the request. I’ve created a new version – 1.2.0 – where the setting plugin.mucho.showSenderJID is added, making broadcasted messages start with the sender JID. Hope it helps.
Brilliant plugin!
I’m dying to use it but can’t – It can only send messages to chatrooms on ‘conference.domain.tld’! We have two MUC services, one on official.domain.tld and another on conference.domain.tld for general chatrooms, but can’t seem to make the bot send to the Official MUC service 😐
Is there any way to at least configure this?
Thanks!
Hi, Brian!
I’m glad you liked the plugin.
No, I’m afraid it isn’t – if there is more than one conference service the plugin chooses “the first one” as they are presented by the server. I took the easy way out when implementing this “feature”. I suppose a better way would be to enable “conference server” as a configurable property. I’ll look into it and try to fix it in next release!
Cheers,
/John
Released version 1.3.0 where the property plugin.mucho.conferenceService is added. If this is set, it is used when connecting to the conference service, if not default is the “first” available service.
Example:if plugin.mucho.conferenceService = “mymuc” on the server server.com, mucho will try to connect to “mymuc.server.com”.
Thanks Brian for the request!
You are not right. I can prove it.
Hello onabype,
I am not interrested.
Hope you don’t mind, but I’ve updated this to work with openfire 3.7.1.
Source at https://github.com/mavnn/mucho
Thanks for this plugin!
@michael Great – thanks! I haven’t worked on this since 2009 so I’m very happy that someone can make it work in newer versions of Openfire! I will mention this fork in the post.