5c94639bf2
It makes sense that vCard in XMPP roughly maps to WHOIS in IRC, but there is no code that actually handles receiving WHOISes properly: they just get passed through as plain messages coming from user!ircserver@irc.xmppserver.tld. I suppose sometimes you want to manually be able to run a WHOIS and see the results, so I don't want them banned entirely, but I don't want them on each run. Sending spurious WHOISes pisses off Xabber, which overenthusiastically sends "get vCard" IQ stanzas on every single presence change (even "unavailable"); this has the horrible side effect of spawning a huge number of private chats with users I have never talked to, and buzzing my phone uncontrollably for a good minute, whenever I join a channel with more than 50 people in it, and the same every time someone's connection drops. Disabling this scratches an itch for me and patches over what is arguably Xabber's problem, but in fact, this code was already half-disabled: *even though it sends IRC commands* it returns ?ERR_FEATURE_NOT_IMPLEMENTED. Was this an oversight? |
||
|---|---|---|
| atom_pubsub | ||
| ejabberd_auth_http | ||
| extra | ||
| ircd | ||
| mod_archive | ||
| mod_cron | ||
| mod_deny_omemo | ||
| mod_filter | ||
| mod_grafite | ||
| mod_irc | ||
| mod_log_chat | ||
| mod_logsession | ||
| mod_logxml | ||
| mod_mam_mnesia | ||
| mod_message_log | ||
| mod_muc_log_http | ||
| mod_openid | ||
| mod_post_log | ||
| mod_pottymouth | ||
| mod_profile | ||
| mod_rest | ||
| mod_s2s_log | ||
| mod_shcommands | ||
| mod_statsdx | ||
| mod_webpresence | ||
| .gitignore | ||
| README-broken.md | ||
| README.md | ||
README.md
ejabberd-contrib
This is a collaborative development area for ejabberd module developers and users.
For users
To use an ejabberd module coming from this repository:
-
You need to have ejabberd installed.
-
If you have not already done it, run
ejabberdctl modules_update_specsto retrieve the list of available modules. -
Run
ejabberdctl module_install <module>to get the source code and to compile and install thebeamfile into ejabberd's module search path. This path is either~/.ejabberd-modulesor defined by theCONTRIB_MODULES_PATHsetting inejabberdctl.cfg. -
Edit the configuration file provided in the
confdirectory of the installed module and update it to your needs. Then apply the changes to your main ejabberd configuration. In a future release, ejabberd will automatically add this file to its runtime configuration without changes. -
Run
ejabberdctl module_uninstall <module>to remove a module from ejabberd.
For developers
The following organization has been set up for the development:
-
Development and compilation of modules is done by ejabberd. You need ejabberd installed. Use
ejabberdctl module_check <module>to ensure it compiles correctly before committing your work. The sources of your module must be located in$CONTRIB_MODULES_PATH/sources/<module>. -
Compilation can by done manually (if you know what you are doing) so you don't need ejabberd running:
cd /path/of/module mkdir ebin /path/of/ejabberd's/erlc \ -o ebin \ -I include -I /path/of/ejabberd/lib/ejabberd-XX.YY/include \ -DLAGER -DNO_EXT_LIB \ src/*erl -
The module directory structure is usually the following:
README.txt: Module description.COPYING: License for the module.doc/: Documentation directory.src/: Erlang source directory.lib/: Elixir source directory.priv/msgs/: Directory with translation files (pot, po and msg).conf/<module>.yml: Configuration for your module.<module>.spec: Yaml description file for your module.
-
Module developers should note in the
README.txtfile whether the module has requirements or known incompatibilities with other modules.