commit: a096e57bb938e3977d8d2eb0ccffe4e7c3e4520c Author: Gerion Entrup <gerion.entrup <AT> flump <DOT> de> AuthorDate: Wed Jan 6 09:10:35 2021 +0000 Commit: gerion <gerion.entrup <AT> flump <DOT> de> CommitDate: Wed Jan 6 09:10:35 2021 +0000 URL: https://gitweb.gentoo.org/repo/user/gerislay.git/commit/?id=a096e57b
net-im/prosody-modules: drop, in tree now Signed-off-by: Gerion Entrup <gerion.entrup <AT> flump.de> net-im/prosody-modules/Manifest | 2 - net-im/prosody-modules/metadata.xml | 316 --------------------- net-im/prosody-modules/prosody-modules-9999.ebuild | 197 ------------- 3 files changed, 515 deletions(-) diff --git a/net-im/prosody-modules/Manifest b/net-im/prosody-modules/Manifest deleted file mode 100644 index fd419b7..0000000 --- a/net-im/prosody-modules/Manifest +++ /dev/null @@ -1,2 +0,0 @@ -EBUILD prosody-modules-9999.ebuild 6871 BLAKE2B cb26b2d419de4a456baa10df6560fb659dd19306ceee1a02944fc2433b621671315c033ded1364d10c007458b25c3da864a551652719fdb137fbc65d6e030d00 SHA512 cb6bfc7799b83d93bdf6991a843810c9e678e7f8cfc3713e0e6cdcfb233b9da718595fd5cb9c670bea4498da00087fb42e3dbcd27f6ab0c7772926ae7c1e8b56 -MISC metadata.xml 73009 BLAKE2B 70e3f88e460c28132eb09eb9b42f4d3104014bb56f5ea2d86c0502a5b5690dd1dc64cde6421a991792ac236cff68d1acb6e69fff41e93614f78154b794ca134e SHA512 b2c2e8efbd1e1c91ad77c31c7d331523067a995934292306135b9eca7a3084dc4239bcf59b17fe7bb1e6f1b774ef499b9885fd21628b19d79ad3ba62f8c53510 diff --git a/net-im/prosody-modules/metadata.xml b/net-im/prosody-modules/metadata.xml deleted file mode 100644 index fb0d024..0000000 --- a/net-im/prosody-modules/metadata.xml +++ /dev/null @@ -1,316 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!DOCTYPE -pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd";> -<pkgmetadata> - <maintainer type="person"> - <email>[email protected]</email> - <name>Gerion Entrup</name> - </maintainer> - <longdescription>Modules for <pkg>net-im/prosody</pkg>, - developed by the community</longdescription> - <use> - <flag name='misc'></flag> - <flag name='prosody_modules_addressing'>This module is a partial implementation of XEP-0033: Extended Stanza Addressing. (info: https://modules.prosody.im/mod_addressing)</flag> - <flag name='prosody_modules_adhoc_account_management'>This module adds an ad-hoc command that lets an user change their password. This is useful for clients that don’t have support for XEP-0077 style password changing. In the future, it may provide other account management commands. (info: https://modules.prosody.im/mod_adhoc_account_management)</flag> - <flag name='prosody_modules_adhoc_blacklist'>This module provides the Edit Blacklist ad-hoc command described in XEP-0133 and also performs the actual blocking of incoming and outgoing server-to-server connections. (info: https://modules.prosody.im/mod_adhoc_blacklist)</flag> - <flag name='prosody_modules_adhoc_dataforms_demo'>This module adds an Ad-Hoc command with a demo data form that includes all kinds of fields. It’s meant to help debug both Prosodys util.dataforms library and clients, eg seeing how various field types are rendered. (info: https://modules.prosody.im/mod_adhoc_dataforms_demo)</flag> - <flag name='prosody_modules_adhoc_groups'>This module lets you join groups using an ad-hoc command. When a user joins a group, everyone in the group is added to their roster, and they are added to the rosters of existing members. (info: https://modules.prosody.im/mod_adhoc_groups)</flag> - <flag name='prosody_modules_admin_blocklist'>This module uses the blocklists set by admins for blocking s2s connections. (info: https://modules.prosody.im/mod_admin_blocklist)</flag> - <flag name='prosody_modules_admin_message'>This module provides a console over XMPP. All the commands of the mod_admin_telnet module are available from an XMPP client. (info: https://modules.prosody.im/mod_admin_message)</flag> - <flag name='prosody_modules_admin_probe'>This module lets server administrators send <presence type="probe"/> to any local user and receive their presence in response, bypassing roster checks. (info: https://modules.prosody.im/mod_admin_probe)</flag> - <flag name='prosody_modules_admin_web'>This module provides a basic web administration interface. It currently gives you access to Ad-Hoc commands on any virtual host or component that you are set as an administrator for in the Prosody config file. It also provides a live list of all S2S and C2S connections. (info: https://modules.prosody.im/mod_admin_web)</flag> - <flag name='prosody_modules_alias'>This module allows you to set up aliases that alert people who try to contact them or add them to their roster what your actual JID is. This is useful for changing JIDs, or just in the case where you own both example.com and example.net, and want people who contact [email protected] to be alerted to contact you at [email protected] instead. (info: https://modules.prosody.im/mod_alias)</flag> - <flag name='prosody_modules_atom'>This module exposes users microblogging on Prosodys built-in HTTP server. (info: https://modules.prosody.im/mod_atom)</flag> - <flag name='prosody_modules_auth_any'>This module accepts any username and password, which can be useful for testing. (info: https://modules.prosody.im/mod_auth_any)</flag> - <flag name='prosody_modules_auth_ccert'>This module implements PKI-style client certificate authentication. You will therefore need your own Certificate Authority. How to set that up is beyond the current scope of this document. (info: https://modules.prosody.im/mod_auth_ccert)</flag> - <flag name='prosody_modules_auth_custom_http'>To authenticate users, this module does a POST request to a configured URL with a JSON payload. It is not async so requests block the server until answered. (info: https://modules.prosody.im/mod_auth_custom_http)</flag> - <flag name='prosody_modules_auth_dovecot'>This is a Prosody authentication plugin which uses Dovecot as the backend. (info: https://modules.prosody.im/mod_auth_dovecot)</flag> - <flag name='prosody_modules_auth_external'>Allow client authentication to be handled by an external script/process. (info: https://modules.prosody.im/mod_auth_external)</flag> - <flag name='prosody_modules_auth_ha1'>This module authenticates users against hashed credentials stored in a plain text file. The format is the same as that used by reTurnServer. (info: https://modules.prosody.im/mod_auth_ha1)</flag> - <flag name='prosody_modules_auth_http_async'>This is an experimental authentication module that does an asynchronous HTTP call to verify username and password. (info: https://modules.prosody.im/mod_auth_http_async)</flag> - <flag name='prosody_modules_auth_http_cookie'>This is an experimental authentication module that does an asynchronous HTTP call to verify username and password. (info: https://modules.prosody.im/mod_auth_http_cookie)</flag> - <flag name='prosody_modules_auth_imap'>This is a Prosody authentication plugin which uses a generic IMAP server as the backend. (info: https://modules.prosody.im/mod_auth_imap)</flag> - <flag name='prosody_modules_auth_internal_yubikey'>A YubiKey is a small USB one-time-password (OTP) generator. (info: https://modules.prosody.im/mod_auth_internal_yubikey)</flag> - <flag name='prosody_modules_auth_joomla'>This module allows you to authenticate against an Joomla database. (info: https://modules.prosody.im/mod_auth_joomla)</flag> - <flag name='prosody_modules_auth_ldap'>This is a Prosody authentication plugin which uses LDAP as the backend. (info: https://modules.prosody.im/mod_auth_ldap)</flag> - <flag name='prosody_modules_auth_ldap2'>See mod_lib_ldap for more information. (info: https://modules.prosody.im/mod_auth_ldap2)</flag> - <flag name='prosody_modules_auth_oauthbearer'>This is an authentication module for the SASL OAUTHBEARER mechanism, as provided by mod_sasl_oauthbearer. (info: https://modules.prosody.im/mod_auth_oauthbearer)</flag> - <flag name='prosody_modules_auth_pam'>This module makes Prosody authenticate users against PAM (Linux Pluggable Authentication Modules) (info: https://modules.prosody.im/mod_auth_pam)</flag> - <flag name='prosody_modules_auth_phpbb3'>This module allows you to authenticate against an PHPBB3 database. (info: https://modules.prosody.im/mod_auth_phpbb3)</flag> - <flag name='prosody_modules_auth_sql'>Allow client authentication to be handled by an SQL database query. (info: https://modules.prosody.im/mod_auth_sql)</flag> - <flag name='prosody_modules_auth_token'>This module enables Prosody to authenticate time-based one-time-pin (TOTP) HMAC tokens. (info: https://modules.prosody.im/mod_auth_token)</flag> - <flag name='prosody_modules_auth_wordpress'>This module allows you to authenticate against an Wordpress database. (info: https://modules.prosody.im/mod_auth_wordpress)</flag> - <flag name='prosody_modules_auto_accept_subscriptions'>In some environments where all users on the system have mutual trust in each other, it’s sometimes fine to skip the usual authorization process to add someone to your contact list and see their status. (info: https://modules.prosody.im/mod_auto_accept_subscriptions)</flag> - <flag name='prosody_modules_auto_activate_hosts'>By default Prosody does not automatically activate/deactivate hosts when they are added to and removed from the configuration. (info: https://modules.prosody.im/mod_auto_activate_hosts)</flag> - <flag name='prosody_modules_auto_answer_disco_info'>This module intercepts disco#info queries and checks if we already know the capabilities of this session, in which case we don’t transmit the iq and answer it ourselves. (info: https://modules.prosody.im/mod_auto_answer_disco_info)</flag> - <flag name='prosody_modules_benchmark_storage'>To benchmark mod_storage_internal: (info: https://modules.prosody.im/mod_benchmark_storage)</flag> - <flag name='prosody_modules_bidi'>This module implements XEP-0288: Bidirectional Server-to-Server Connections. It allows servers to use a single connection for sending stanzas to each other, instead of two connections (one for stanzas in each direction). (info: https://modules.prosody.im/mod_bidi)</flag> - <flag name='prosody_modules_block_outgoing'>This module blocks all outgoing stanzas from a list of users. (info: https://modules.prosody.im/mod_block_outgoing)</flag> - <flag name='prosody_modules_block_registrations'>On a server with public registration it is usually desirable to prevent registration of certain “reserved” accounts, such as “admin”. (info: https://modules.prosody.im/mod_block_registrations)</flag> - <flag name='prosody_modules_block_s2s_subscriptions'>No documentation yet :( (info: https://modules.prosody.im/mod_block_s2s_subscriptions)</flag> - <flag name='prosody_modules_block_strangers'>No documentation yet :( (info: https://modules.prosody.im/mod_block_strangers)</flag> - <flag name='prosody_modules_block_subscribes'>No documentation yet :( (info: https://modules.prosody.im/mod_block_subscribes)</flag> - <flag name='prosody_modules_block_subscriptions'>No documentation yet :( (info: https://modules.prosody.im/mod_block_subscriptions)</flag> - <flag name='prosody_modules_blocking'>Privacy lists are a widely implemented protocol for instructing your server on blocking communications with selected users and services. (info: https://modules.prosody.im/mod_blocking)</flag> - <flag name='prosody_modules_bob'>This module extracts cid: URIs (as defined in XEP-0231) from messages, and replies with their content whenever another client asks for the actual data. (info: https://modules.prosody.im/mod_bob)</flag> - <flag name='prosody_modules_bookmarks'>This module fetches users’ bookmarks from Private XML and pushes them to PEP on login, and then redirects any Private XML query to PEP. This allows interop between older clients that use XEP-0048: Bookmarks in its 1.0 version and recent clients which use it in PEP. (info: https://modules.prosody.im/mod_bookmarks)</flag> - <flag name='prosody_modules_bookmarks2'>This module fetches users’ bookmarks from Private XML and pushes them to PEP on login, and then redirects any Private XML query to PEP. This allows interop between older clients that use XEP-0048: Bookmarks in its 1.0 version and recent clients which use it in PEP. (info: https://modules.prosody.im/mod_bookmarks2)</flag> - <flag name='prosody_modules_broadcast'>This module largely duplicates the functionality of the standard mod_announce that is included with Prosody. It was developed for compatibility with some clients (e.g. iChat) that do not support ad-hoc commands or sending to JIDs with the format ‘example.com/announce/online’. (info: https://modules.prosody.im/mod_broadcast)</flag> - <flag name='prosody_modules_c2s_conn_throttle'>This module allows to throttle those client connections which exceed a n*seconds limit. (info: https://modules.prosody.im/mod_c2s_conn_throttle)</flag> - <flag name='prosody_modules_c2s_limit_sessions'>This module lets you limit number of resources a user may connect. (info: https://modules.prosody.im/mod_c2s_limit_sessions)</flag> - <flag name='prosody_modules_cache_c2s_caps'>This module listens on presences containing caps (XEP-0115) and asks the client for the corresponding disco#info if it changed. (info: https://modules.prosody.im/mod_cache_c2s_caps)</flag> - <flag name='prosody_modules_captcha_registration'>Prosody-captcha is a little modification of prosody’s “mod_register.lua” module that provides captcha protection for registration form. (info: https://modules.prosody.im/mod_captcha_registration)</flag> - <flag name='prosody_modules_carbons'>This module implements XEP-0280: Message Carbons, allowing users to maintain a shared and synchronized view of all conversations across all their online clients and devices. (info: https://modules.prosody.im/mod_carbons)</flag> - <flag name='prosody_modules_carbons_adhoc'>No documentation yet :( (info: https://modules.prosody.im/mod_carbons_adhoc)</flag> - <flag name='prosody_modules_carbons_copies'>No documentation yet :( (info: https://modules.prosody.im/mod_carbons_copies)</flag> - <flag name='prosody_modules_checkcerts'>This module periodically checks your certificate to see if it is about to expire soon. The time before expiry is printed in the logs. About a week before a certificate expires, reminder messages will be sent to admins. (info: https://modules.prosody.im/mod_checkcerts)</flag> - <flag name='prosody_modules_client_certs'>XEP-0257 specifies a protocol for clients to store and manage client side certificates. When a client presents a stored client side certificate during the TLS handshake, it can log in without supplying a password (using SASL EXTERNAL). This makes it possible to have multiple devices accessing an account, without any of them needing to know the password, and makes it easier to revoke access for a single device. (info: https://modules.prosody.im/mod_client_certs)</flag> - <flag name='prosody_modules_client_proxy'>This module must be used as a component. For example: (info: https://modules.prosody.im/mod_client_proxy)</flag> - <flag name='prosody_modules_cloud_notify'>This is an implementation of the server bits of XEP-0357: Push Notifications. It allows clients to register an “app server” which is notified about new messages while the user is offline, disconnected or the session is hibernated by mod_smacks. Implementation of the “app server” is not included1. (info: https://modules.prosody.im/mod_cloud_notify)</flag> - <flag name='prosody_modules_compact_resource'>No documentation yet :( (info: https://modules.prosody.im/mod_compact_resource)</flag> - <flag name='prosody_modules_compat_bind'>No documentation yet :( (info: https://modules.prosody.im/mod_compat_bind)</flag> - <flag name='prosody_modules_compat_dialback'>This module provides a workaround for servers that do not set the to attribute on stream headers, which is required per RFC6120: (info: https://modules.prosody.im/mod_compat_dialback)</flag> - <flag name='prosody_modules_compat_muc_admin'>Adds compatibility for old clients/libraries attempting to change affiliations and retrieve ’em sending the < http://jabber.org/protocol/muc#owner > xmlns instead of < http://jabber.org/protocol/muc#admin >. (info: https://modules.prosody.im/mod_compat_muc_admin)</flag> - <flag name='prosody_modules_compat_vcard'>No documentation yet :( (info: https://modules.prosody.im/mod_compat_vcard)</flag> - <flag name='prosody_modules_component_client'>This module turns Prosody hosts into components of other XMPP servers. (info: https://modules.prosody.im/mod_component_client)</flag> - <flag name='prosody_modules_component_http'>This module allows you to implement a component that speaks HTTP. Stanzas (such as messages) coming from XMPP are sent to a configurable URL as a HTTP POST. If the POST returns a response, that response is returned to the sender over XMPP. (info: https://modules.prosody.im/mod_component_http)</flag> - <flag name='prosody_modules_component_roundrobin'>This module enables multiple instances of external components to connect at the same time, and does round-robin load-balancing of incoming stanzas. (info: https://modules.prosody.im/mod_component_roundrobin)</flag> - <flag name='prosody_modules_compression_unsafe'>NOTE: XMPP compression has unresolved security concerns, and this module has been removed from Prosody and renamed. (info: https://modules.prosody.im/mod_compression_unsafe)</flag> - <flag name='prosody_modules_conformance_restricted'>This module sends processing instructions, comments, DTDs and a non predefined entity (defined by the DTD) to the requesting entity. (info: https://modules.prosody.im/mod_conformance_restricted)</flag> - <flag name='prosody_modules_conversejs'>This module serves a small snippet of HTML that loads Converse.js, configured to work with the VirtualHost that it is loaded onto. (info: https://modules.prosody.im/mod_conversejs)</flag> - <flag name='prosody_modules_couchdb'>Note: This module needs updating to the 0.8 storage module API. (info: https://modules.prosody.im/mod_couchdb)</flag> - <flag name='prosody_modules_csi'>This module implements XEP-0352: Client State Indication, a way for mobile clients to tell the server that they are sitting in someones pocket and would rather not get some less urgent things pushed to it. (info: https://modules.prosody.im/mod_csi)</flag> - <flag name='prosody_modules_csi_battery_saver'>Please use this module instead of mod_csi_pump if you want timestamping, properly handled carbon copies, support for handling encrypted messages and correctly handled smacks events. (info: https://modules.prosody.im/mod_csi_battery_saver)</flag> - <flag name='prosody_modules_csi_compat'>This module implements the google:queue protocol and maps it to mod_csi events. (info: https://modules.prosody.im/mod_csi_compat)</flag> - <flag name='prosody_modules_csi_pump'>Stanzas are queued in a buffer until either an “important” stanza is encountered or the buffer becomes full. Then all queued stanzas are sent at the same time. This way, nothing is lost or reordered while still allowing for power usage savings by not requiring mobile clients to bring up their radio for unimportant stanzas. (info: https://modules.prosody.im/mod_csi_pump)</flag> - <flag name='prosody_modules_data_access'>This module gives HTTP access to prosody’s storage mechanism. It uses normal HTTP verbs and Basic HTTP authentication, so you could call it RESTful if you like buzzwords. (info: https://modules.prosody.im/mod_data_access)</flag> - <flag name='prosody_modules_default_bookmarks'>This module allows you to add default bookmarks for users. It only kicks in when the user has no existing bookmarks, so users are free to add, change or remove them. (info: https://modules.prosody.im/mod_default_bookmarks)</flag> - <flag name='prosody_modules_default_vcard'>It is possible for the user to supply more than just a username and password when creating an account using mod_register. This module automatically copies over that data to the user’s vcard. (info: https://modules.prosody.im/mod_default_vcard)</flag> - <flag name='prosody_modules_delay'>This module adds “Delayed Delivery”-tags to every message stanza passing the server containing the current time on that server. (info: https://modules.prosody.im/mod_delay)</flag> - <flag name='prosody_modules_delegation'>Namespace Delegation is an extension which allows server to delegate some features handling to an entity/component. Typical use case is an external PEP service, but it can be used more generally when your preferred server lack one internal feature and you found an external component which can do it. (info: https://modules.prosody.im/mod_delegation)</flag> - <flag name='prosody_modules_deny_omemo'>No documentation yet :( (info: https://modules.prosody.im/mod_deny_omemo)</flag> - <flag name='prosody_modules_devices'>This is an experimental module that aims to identify the different devices (technically clients) that a user uses with their account. (info: https://modules.prosody.im/mod_devices)</flag> - <flag name='prosody_modules_disable_tls'>This module can be used to prevent Prosody from offering TLS on client ports that you specify. This can be useful to work around buggy clients when transport security is not required. (info: https://modules.prosody.im/mod_disable_tls)</flag> - <flag name='prosody_modules_discoitems'>This Prosody plugin lets you manually override the service discovery items for a host. (info: https://modules.prosody.im/mod_discoitems)</flag> - <flag name='prosody_modules_dwd'>This module implements an optimization of the Dialback protocol, by skipping the dialback step for servers presenting a valid certificate. (info: https://modules.prosody.im/mod_dwd)</flag> - <flag name='prosody_modules_e2e_policy'>This module was written to encourage usage of End-to-end encryption for chat and MUC messages. It can be configured to warn the sender after every plaintext/unencrypted message or to block all plaintext/unencrypted messages. It also supports MUC and JID whitelisting, so administrators can for example whitelist public support MUCs ;-) (info: https://modules.prosody.im/mod_e2e_policy)</flag> - <flag name='prosody_modules_email_pass'>This module aims to help in the procedure of user password restoration. To start the restoration, the user must go to an URL provided by this module, fill the JID and email and submit the request. (info: https://modules.prosody.im/mod_email_pass)</flag> - <flag name='prosody_modules_extdisco'>This module adds support for XEP-0215: External Service Discovery, which lets Prosody advertise non-XMPP services. (info: https://modules.prosody.im/mod_extdisco)</flag> - <flag name='prosody_modules_fallback_vcard'>No documentation yet :( (info: https://modules.prosody.im/mod_fallback_vcard)</flag> - <flag name='prosody_modules_filter_chatstates'>Some mobile XMPP client developers consider Chat State Notifications to be a waste of power and bandwidth, especially when the user is not actively looking at their device. This module will filter them out while the session is considered inactive. It depends on mod_csi for deciding when to begin and end filtering. (info: https://modules.prosody.im/mod_filter_chatstates)</flag> - <flag name='prosody_modules_filter_words'>No documentation yet :( (info: https://modules.prosody.im/mod_filter_words)</flag> - <flag name='prosody_modules_firewall'>Note: mod_firewall is in its very early stages. This documentation is liable to change, and some described functionality may be missing, incomplete or contain bugs. (info: https://modules.prosody.im/mod_firewall)</flag> - <flag name='prosody_modules_flash_policy'>This Prosody plugin adds support for flash socket policies. When connecting with a flash client (from a webpage, not an exe) to prosody the flash client requests for an xml “file” on port 584 or the connecting port (5222 in the case of default xmpp). Responding on port 584 is tricky because it requires root priviliges to set up a socket on a port < 1024. (info: https://modules.prosody.im/mod_flash_policy)</flag> - <flag name='prosody_modules_graceful_shutdown'>This module is an experiment about a more graceful shutdown process. (info: https://modules.prosody.im/mod_graceful_shutdown)</flag> - <flag name='prosody_modules_group_bookmarks'>mod_groups allows you to insert contacts into users’ contact lists. Well mod_group_bookmarks allows you to insert chatrooms into the user’s bookmarks. These are fetched by their client and automatically joined when the log in. (info: https://modules.prosody.im/mod_group_bookmarks)</flag> - <flag name='prosody_modules_host_blacklist'>No documentation yet :( (info: https://modules.prosody.im/mod_host_blacklist)</flag> - <flag name='prosody_modules_host_guard'>As often it’s undesiderable to employ only whitelisting logics in public environments, this module let’s you more selectively restrict access to your hosts (component or server host) either disallowing access completely (with optional exceptions) or blacklisting certain sources. (info: https://modules.prosody.im/mod_host_guard)</flag> - <flag name='prosody_modules_host_status_check'>This module allows you to monitor the state of hosts and components in your Prosody server. For example, it will track whether components are connected and (if the component supports it) listen for heartbeats sent by the component to indicate that it is functioning. (info: https://modules.prosody.im/mod_host_status_check)</flag> - <flag name='prosody_modules_host_status_heartbeat'>This module integrates with mod_host_status_check to provide heartbeats at regular intervals. (info: https://modules.prosody.im/mod_host_status_heartbeat)</flag> - <flag name='prosody_modules_http_altconnect'>No documentation yet :( (info: https://modules.prosody.im/mod_http_altconnect)</flag> - <flag name='prosody_modules_http_auth_check'> (info: https://modules.prosody.im/mod_http_auth_check)</flag> - <flag name='prosody_modules_http_authentication'>This module enforces HTTP Basic authentication across all HTTP endpoints served by Prosody. (info: https://modules.prosody.im/mod_http_authentication)</flag> - <flag name='prosody_modules_http_avatar'>This module serves avatars from local users who have one set in their vCard, see XEP-0054 and XEP-0153. (info: https://modules.prosody.im/mod_http_avatar)</flag> - <flag name='prosody_modules_http_dir_listing'>This module generates directory listings when invoked by mod_http_files. See documentation on mod_http_files. (info: https://modules.prosody.im/mod_http_dir_listing)</flag> - <flag name='prosody_modules_http_dir_listing2'>This module generates directory listings when invoked by mod_http_files. See documentation on mod_http_files. (info: https://modules.prosody.im/mod_http_dir_listing2)</flag> - <flag name='prosody_modules_http_favicon'>This simple module serves a favicon.ico from prosodys HTTP server and nothing else. (info: https://modules.prosody.im/mod_http_favicon)</flag> - <flag name='prosody_modules_http_host_status_check'>This module exposes serves over HTTP the information collected by mod_host_status_check and mod_host_status_heartbeat in a convenient format for automated monitoring tools. (info: https://modules.prosody.im/mod_http_host_status_check)</flag> - <flag name='prosody_modules_http_hostaliases'>No documentation yet :( (info: https://modules.prosody.im/mod_http_hostaliases)</flag> - <flag name='prosody_modules_http_index'>This module produces a list of enabled HTTP “apps” exposed from Prosody at http://example.org:5280/, e.g. mod_http_muc_log, mod_http_files or mod_admin_web. If you think Prosodys default “root” web page (a 404 error usually) is boring, this might be the module for you! :) (info: https://modules.prosody.im/mod_http_index)</flag> - <flag name='prosody_modules_http_logging'>This module produces more detailed HTTP logs for Prosodys built-in HTTP server. The format is similar to that of Apache and go into Prosodys normal logs at the info level. (info: https://modules.prosody.im/mod_http_logging)</flag> - <flag name='prosody_modules_http_muc_log'>This module provides a built-in web interface to view chatroom logs stored by mod_mam_muc. (info: https://modules.prosody.im/mod_http_muc_log)</flag> - <flag name='prosody_modules_http_pep_avatar'>This module serves avatars from local users who have published XEP-0084: User Avatar via PEP. (info: https://modules.prosody.im/mod_http_pep_avatar)</flag> - <flag name='prosody_modules_http_rest'>This module provides a RESTful method for sending XMPP stanzas. (info: https://modules.prosody.im/mod_http_rest)</flag> - <flag name='prosody_modules_http_roster_admin'>NOTE: THIS MODULE IS RELEASED UNDER THE MOZILLA PUBLIC LICENSE VERSION 2. (info: https://modules.prosody.im/mod_http_roster_admin)</flag> - <flag name='prosody_modules_http_stats_stream'>This module provides a streaming interface to Prosodys internal statistics via Server-sent events. (info: https://modules.prosody.im/mod_http_stats_stream)</flag> - <flag name='prosody_modules_http_upload'>This module implements XEP-0363, versions 0.2 and 0.3, which let clients upload files over HTTP. (info: https://modules.prosody.im/mod_http_upload)</flag> - <flag name='prosody_modules_http_upload_external'>This module implements XEP-0363, which lets clients upload files over HTTP to an external web server. (info: https://modules.prosody.im/mod_http_upload_external)</flag> - <flag name='prosody_modules_http_user_count'>No documentation yet :( (info: https://modules.prosody.im/mod_http_user_count)</flag> - <flag name='prosody_modules_idlecompat'>This module adds XEP-0319 idle tags to presence stanzas containing XEP-0012: Last Activity tags for idle indication (e.g. supported by libpurple clients). It works on outgoing and incoming presence stanzas. (info: https://modules.prosody.im/mod_idlecompat)</flag> - <flag name='prosody_modules_ignore_host_chatstates'>No documentation yet :( (info: https://modules.prosody.im/mod_ignore_host_chatstates)</flag> - <flag name='prosody_modules_incidents_handling'>This module implements XEP-268. (info: https://modules.prosody.im/mod_incidents_handling)</flag> - <flag name='prosody_modules_inject_ecaps2'>This module injects ecaps2 elements in the presence once the legacy caps (XEP-0115) are received. (info: https://modules.prosody.im/mod_inject_ecaps2)</flag> - <flag name='prosody_modules_inotify_reload'>No documentation yet :( (info: https://modules.prosody.im/mod_inotify_reload)</flag> - <flag name='prosody_modules_invite'>This module allows users with an account to generate single-use invite URLs using an ad-hoc command. The invite URLs allow new users to create an account even if public registration is disabled. (info: https://modules.prosody.im/mod_invite)</flag> - <flag name='prosody_modules_ipcheck'>Sometimes for various reasons a client might want to know its IP address as it appears to the server. This simple XEP allows the client to ask the server for the IP address it is connected from. (info: https://modules.prosody.im/mod_ipcheck)</flag> - <flag name='prosody_modules_isolate_host'>In some environments it is desirable to isolate one or more hosts, and prevent communication with external, or even other internal domains. (info: https://modules.prosody.im/mod_isolate_host)</flag> - <flag name='prosody_modules_jid_prep'>This is a plugin that implements the JID prep protocol defined in http://xmpp.org/extensions/inbox/jidprep.html (info: https://modules.prosody.im/mod_jid_prep)</flag> - <flag name='prosody_modules_json_streams'>This plugin encodes XMPP as JSON. This is an implementation of XEP-0295: JSON Encodings for XMPP. (info: https://modules.prosody.im/mod_json_streams)</flag> - <flag name='prosody_modules_lastlog'>Simple module that stores the timestamp of when a user logs in. (info: https://modules.prosody.im/mod_lastlog)</flag> - <flag name='prosody_modules_latex'>This module intercepts messages between users and into chatrooms, and attaches a links to a rendered version of any LaTeX in the message. This requires client support for XHTML-IM, and fetching images via HTTP. (info: https://modules.prosody.im/mod_latex)</flag> - <flag name='prosody_modules_lib_ldap'>This module is used by other modules to access an LDAP server. It’s pretty useless on its own; you should use it if you want to write your own LDAP-related module, or if you want to use one of mine (mod_auth_ldap2, mod_storage_ldap). (info: https://modules.prosody.im/mod_lib_ldap)</flag> - <flag name='prosody_modules_limit_auth'>This module lets you put a per-IP limit on the number of failed authentication attempts. (info: https://modules.prosody.im/mod_limit_auth)</flag> - <flag name='prosody_modules_limits'>On some servers, especially public ones, it is desired to make sure that everyone gets their fair share of system resources (and no more). (info: https://modules.prosody.im/mod_limits)</flag> - <flag name='prosody_modules_list_active'>This module lists those users, who have used their account in a defined time-frame, basically the inverse of mod_list_inactive. (info: https://modules.prosody.im/mod_list_active)</flag> - <flag name='prosody_modules_list_inactive'>This module lists those users, who haven’t used their account in a defined time-frame. (info: https://modules.prosody.im/mod_list_inactive)</flag> - <flag name='prosody_modules_listusers'>This module adds a command to prosodyctl for listing users. (info: https://modules.prosody.im/mod_listusers)</flag> - <flag name='prosody_modules_log_auth'>Prosody doesn’t write IP addresses to its log file by default for privacy reasons (unless debug logging is enabled). (info: https://modules.prosody.im/mod_log_auth)</flag> - <flag name='prosody_modules_log_events'>No documentation yet :( (info: https://modules.prosody.im/mod_log_events)</flag> - <flag name='prosody_modules_log_http'>This module logs outgoing requests that go via the internal net.http API. (info: https://modules.prosody.im/mod_log_http)</flag> - <flag name='prosody_modules_log_mark'>This module sends -- MARK -- to the log once per minute. This may be useful to give a sense of how busy the server is or see that logging and timers are still working. (info: https://modules.prosody.im/mod_log_mark)</flag> - <flag name='prosody_modules_log_messages_sql'>Consider using mod_mam together with mod_readonly instead. (info: https://modules.prosody.im/mod_log_messages_sql)</flag> - <flag name='prosody_modules_log_rate'>If you ever wanted to collect statistics on the number of log messages, this is the module for you! (info: https://modules.prosody.im/mod_log_rate)</flag> - <flag name='prosody_modules_log_sasl_mech'>No documentation yet :( (info: https://modules.prosody.im/mod_log_sasl_mech)</flag> - <flag name='prosody_modules_log_slow_events'>Most activities in Prosody take place within our built-in events framework, for example stanza processing and HTTP request handling, authentication, etc. (info: https://modules.prosody.im/mod_log_slow_events)</flag> - <flag name='prosody_modules_mam'>Implementation of XEP-0313: Message Archive Management. (info: https://modules.prosody.im/mod_mam)</flag> - <flag name='prosody_modules_mam_adhoc'>This module complements mod_mam by allowing clients to change archiving preferences through an Ad-hoc command. (info: https://modules.prosody.im/mod_mam_adhoc)</flag> - <flag name='prosody_modules_mam_archive'>Implementation of XEP-0136: Message Archiving for mod_mam. (info: https://modules.prosody.im/mod_mam_archive)</flag> - <flag name='prosody_modules_mam_muc'>This module logs the conversation of chatrooms running on the server to Prosody’s archive storage. To access them you will need a client with support for XEP-0313: Message Archive Management version 0.5 or a module such as mod_http_muc_log. (info: https://modules.prosody.im/mod_mam_muc)</flag> - <flag name='prosody_modules_mamsub'>No documentation yet :( (info: https://modules.prosody.im/mod_mamsub)</flag> - <flag name='prosody_modules_manifesto'>This module informs users about the XMPP Test day and whether their contacts are affected. For mor info about the test day, see https://stpeter.im/journal/1496.html (info: https://modules.prosody.im/mod_manifesto)</flag> - <flag name='prosody_modules_measure_client_features'>This module measures the features supported by each connected client. (info: https://modules.prosody.im/mod_measure_client_features)</flag> - <flag name='prosody_modules_measure_client_identities'>This module measures the number of connected clients per identity. (info: https://modules.prosody.im/mod_measure_client_identities)</flag> - <flag name='prosody_modules_measure_client_presence'>This module measures the number of resources of a certain show (available, away, etc.) currently connected, and reports using Prosody 0.10 APIs (info: https://modules.prosody.im/mod_measure_client_presence)</flag> - <flag name='prosody_modules_measure_cpu'>This module measures CPU usage and reports using Prosody 0.10 APIs (info: https://modules.prosody.im/mod_measure_cpu)</flag> - <flag name='prosody_modules_measure_malloc'>This module collects stats from util.pposix.meminfo usage and reports using Prosody 0.10 APIs (info: https://modules.prosody.im/mod_measure_malloc)</flag> - <flag name='prosody_modules_measure_memory'>This module measures memory usage and reports using Prosody 0.10 APIs (info: https://modules.prosody.im/mod_measure_memory)</flag> - <flag name='prosody_modules_measure_message_e2ee'>This module measures the rate at which text messages are exchanged, and their encryption status. (info: https://modules.prosody.im/mod_measure_message_e2ee)</flag> - <flag name='prosody_modules_measure_message_length'>Simple module that collects statistics on message length in bytes, word count and line count. (info: https://modules.prosody.im/mod_measure_message_length)</flag> - <flag name='prosody_modules_measure_stanza_counts'>This module measures the number of stanzas handled and reports using Prosody 0.10 APIs (info: https://modules.prosody.im/mod_measure_stanza_counts)</flag> - <flag name='prosody_modules_measure_storage'>This module collects statistics from storage operations. (info: https://modules.prosody.im/mod_measure_storage)</flag> - <flag name='prosody_modules_message_logging'>Often service administrators need to log their users’ messages for reasons such as auditing and compliance. This module simply logs user messages to simple text files, which can be easily searched, archived or removed on a regular basis. (info: https://modules.prosody.im/mod_message_logging)</flag> - <flag name='prosody_modules_migrate'>This module adds a command to prosodyctl for copying data between storage drivers. (info: https://modules.prosody.im/mod_migrate)</flag> - <flag name='prosody_modules_minimix'>Normally when joining a MUC groupchat, it is each individual client that joins. This means their presence in the group is tied to the session, which can be short-lived or unstable, especially in the case of mobile clients. (info: https://modules.prosody.im/mod_minimix)</flag> - <flag name='prosody_modules_motd_sequential'>mod_motd_sequential is a variant of mod_motd that lets you specify a sequence of MOTD messages instead of a single static one. Each message is only sent once and the module keeps track of who as seen which message. (info: https://modules.prosody.im/mod_motd_sequential)</flag> - <flag name='prosody_modules_muc_access_control'>No documentation yet :( (info: https://modules.prosody.im/mod_muc_access_control)</flag> - <flag name='prosody_modules_muc_badge'>This module generates a badge for MUC rooms at a HTTP URL like https://conference.example.com:5281/muc_badge/[email protected] containing the number of occupants. (info: https://modules.prosody.im/mod_muc_badge)</flag> - <flag name='prosody_modules_muc_ban_ip'>One frequent complaint about XMPP chatrooms (MUCs) compared to IRC is the inability for a room admin to ban a user based on their IP address. This is because an XMPP user is not identified on the network by their IP address, only their JID. (info: https://modules.prosody.im/mod_muc_ban_ip)</flag> - <flag name='prosody_modules_muc_block_pm'>This module prevents unaffiliated users from sending private messages in chat rooms, unless someone with an affiliation (member, admin etc) messages them first. (info: https://modules.prosody.im/mod_muc_block_pm)</flag> - <flag name='prosody_modules_muc_cloud_notify'>This is an experimental fork of mod_cloud_notify which allows a XEP-0357 Push Notifications App Servers to be registered against a MUC domain (normally they’re only registered against your own chat server’s domain). (info: https://modules.prosody.im/mod_muc_cloud_notify)</flag> - <flag name='prosody_modules_muc_config_restrict'>Sometimes, especially on public services, you may want to allow people to create their own rooms, but prevent some options from being modified by normal users. (info: https://modules.prosody.im/mod_muc_config_restrict)</flag> - <flag name='prosody_modules_muc_eventsource'>This module and its docs shamelessly forked from mod_pubsub_eventsource. (info: https://modules.prosody.im/mod_muc_eventsource)</flag> - <flag name='prosody_modules_muc_gc10'>Groupchat 1.0 was probably the protocol that predated XEP-0045: Multi-User Chat and there is still some compatibility that lives on, in the XEP and in implementations. (info: https://modules.prosody.im/mod_muc_gc10)</flag> - <flag name='prosody_modules_muc_intercom'>This module allows sending a message to another MUC room. (info: https://modules.prosody.im/mod_muc_intercom)</flag> - <flag name='prosody_modules_muc_lang'>This module adds support for advertising the language used in a room. (info: https://modules.prosody.im/mod_muc_lang)</flag> - <flag name='prosody_modules_muc_limits'>This module allows you to control the maximum rate of ‘events’ in a MUC room. This makes it useful to prevent room floods (whether malicious or accidental). (info: https://modules.prosody.im/mod_muc_limits)</flag> - <flag name='prosody_modules_muc_log'>This module logs the conversation of chatrooms running on the server to Prosody’s data store. To view them you will need a module such as mod_muc_log_http. (info: https://modules.prosody.im/mod_muc_log)</flag> - <flag name='prosody_modules_muc_log_http'>This module provides a built-in web interface to view chatroom logs stored by mod_muc_log. (info: https://modules.prosody.im/mod_muc_log_http)</flag> - <flag name='prosody_modules_muc_ping'>This module implements the Server Optimization part of XEP-0410: MUC Self-Ping (info: https://modules.prosody.im/mod_muc_ping)</flag> - <flag name='prosody_modules_muc_restrict_rooms'>This module allows disabling room creation based on regexp patterns defined in configuration. (info: https://modules.prosody.im/mod_muc_restrict_rooms)</flag> - <flag name='prosody_modules_munin'>This module implements the Munin reporting protocol, allowing you to collect statistics directly from Prosody into Munin. (info: https://modules.prosody.im/mod_munin)</flag> - <flag name='prosody_modules_net_dovecotauth'>mod_net_dovecotauth is a server implementation of the Dovecot authentication protocol. It allows you to authenticate e.g. Postfix against your Prosody installation. (info: https://modules.prosody.im/mod_net_dovecotauth)</flag> - <flag name='prosody_modules_net_proxy'>This module implements the PROXY protocol in versions 1 and 2, which fulfills the following usecase as described within the official protocol specifications: (info: https://modules.prosody.im/mod_net_proxy)</flag> - <flag name='prosody_modules_offline_email'>Quite often when I am out and about, I’m not able to connect to Jabber. It is usually much more likely I can access my email though (whether via the web, or a mobile client). (info: https://modules.prosody.im/mod_offline_email)</flag> - <flag name='prosody_modules_omemo_all_access'>Traditionally OMEMO encrypted messages could only be exchanged after gaining mutual presence subscription due to the OMEMO key material being stored in PEP. (info: https://modules.prosody.im/mod_omemo_all_access)</flag> - <flag name='prosody_modules_onhold'>Enable mod_onhold to allow temporarily placing messages from particular JIDs “on hold” – i.e. store them, but do not deliver them until the hold status is taken away. (info: https://modules.prosody.im/mod_onhold)</flag> - <flag name='prosody_modules_onions'>This plugin allows Prosody to connect to other servers that are running as a Tor hidden service. Running Prosody on a hidden service works without this module, this module is only necessary to allow Prosody to federate to hidden XMPP servers. (info: https://modules.prosody.im/mod_onions)</flag> - <flag name='prosody_modules_openid'>OpenID is an decentralized authentication mechanism for the Web. mod_openid turns Prosody into an OpenID provider, allowing users to use their Prosody credentials to authenticate with various third party websites. (info: https://modules.prosody.im/mod_openid)</flag> - <flag name='prosody_modules_password_policy'>No documentation yet :( (info: https://modules.prosody.im/mod_password_policy)</flag> - <flag name='prosody_modules_password_reset'>This module allows users to reset their password via a simple link to a web page. (info: https://modules.prosody.im/mod_password_reset)</flag> - <flag name='prosody_modules_pastebin'>Pastebins are used very often in IM, especially in chat rooms. You have a long log or command output which you need to send to someone over IM, and don’t want to fill their message window with it. Put it on a pastebin site, and give them the URL instead, simple. (info: https://modules.prosody.im/mod_pastebin)</flag> - <flag name='prosody_modules_pep_vcard_avatar'>This module pushes the users nickname and avatar from vCards into PEP, or into vCards from PEP. This allows interop between older clients that use XEP-0153: vCard-Based Avatars to see the avatars of clients that use XEP-0084: User Avatar and vice versa. (info: https://modules.prosody.im/mod_pep_vcard_avatar)</flag> - <flag name='prosody_modules_pep_vcard_png_avatar'>Conversations (an XMPP client for Android) is publishing PEP avatars in the webp file format. However Pidgin and other XMPP desktop clients can only show vcard avatars, that are in the PNG file format. This module is the mod_pep_vcard_avatar module extended to also change the avatar file format to PNG. (info: https://modules.prosody.im/mod_pep_vcard_png_avatar)</flag> - <flag name='prosody_modules_persisthosts'>This module creates stub configuration files for newly activated hosts. (info: https://modules.prosody.im/mod_persisthosts)</flag> - <flag name='prosody_modules_pinger'>No documentation yet :( (info: https://modules.prosody.im/mod_pinger)</flag> - <flag name='prosody_modules_poke_strangers'>In order to build heuristics for which messages are spam, it is necessary to log as many details as possible about the spammers. This module sends a version and disco query whenever a message is received from a JID to a user it is not subscribed to. The results are printed to Prosody’s log file at the ‘info’ level. Queried full JIDs are not queried again until Prosody restarts. (info: https://modules.prosody.im/mod_poke_strangers)</flag> - <flag name='prosody_modules_post_msg'>Sometimes it’s useful to have different interfaces to access XMPP. (info: https://modules.prosody.im/mod_post_msg)</flag> - <flag name='prosody_modules_presence_cache'>This module stores a timestamp of the latest presence received from users contacts so that the client can see who is online faster when they sign in, and won’t have to wait for remote servers to reply. (info: https://modules.prosody.im/mod_presence_cache)</flag> - <flag name='prosody_modules_presence_dedup'>This module tries to squash incoming identical presence stanzas to save some bandwidth at the cost of increased memory use. (info: https://modules.prosody.im/mod_presence_dedup)</flag> - <flag name='prosody_modules_privacy_lists'>Privacy lists are a flexible method for blocking communications. (info: https://modules.prosody.im/mod_privacy_lists)</flag> - <flag name='prosody_modules_private_adhoc'>This is a very simple module which implements an adhoc commant toretrieves the users private XML data. (info: https://modules.prosody.im/mod_private_adhoc)</flag> - <flag name='prosody_modules_privilege'>Privileged Entity is an extension which allows entity/component to have privileged access to server (set/get roster, send message on behalf of server, access presence informations). It can be used to build services independently of server (e.g.: PEP service). (info: https://modules.prosody.im/mod_privilege)</flag> - <flag name='prosody_modules_proctitle'>This module sets the process name to prosody so it shows up as such instead of lua in process management tools. (info: https://modules.prosody.im/mod_proctitle)</flag> - <flag name='prosody_modules_profile'>This module provides a replacement for mod_vcard. In addition to the ageing protocol defined by XEP-0054, it also supports the new vCard 4 based protocol and integrates with Personal Eventing Protocol. (info: https://modules.prosody.im/mod_profile)</flag> - <flag name='prosody_modules_prometheus'>This module implements the Prometheus reporting protocol, allowing you to collect statistics directly from Prosody into Prometheus. (info: https://modules.prosody.im/mod_prometheus)</flag> - <flag name='prosody_modules_proxy65_whitelist'>This module attempts to restrict use of non-whitelisted XEP-0065 proxies. (info: https://modules.prosody.im/mod_proxy65_whitelist)</flag> - <flag name='prosody_modules_pubsub_eventsource'>Server-Sent Events is a simple HTTP/line-based protocol supported in HTML5, making it easy to receive a stream of “events” in realtime using the Javascript EventSource API. (info: https://modules.prosody.im/mod_pubsub_eventsource)</flag> - <flag name='prosody_modules_pubsub_feeds'>This module allows Prosody to fetch Atom and RSS feeds for you, and push new results to subscribers over XMPP. (info: https://modules.prosody.im/mod_pubsub_feeds)</flag> - <flag name='prosody_modules_pubsub_github'>This module accepts Github web hooks and publishes them to a local pubsub component for XMPP clients to subscribe to. (info: https://modules.prosody.im/mod_pubsub_github)</flag> - <flag name='prosody_modules_pubsub_hub'>This module implements a PubSubHubbub (PuSH) hub, allowing PuSH clients to subscribe to local XMPP Publish-Subscribe nodes stored by mod_pubsub and receive real time updates to feeds. (info: https://modules.prosody.im/mod_pubsub_hub)</flag> - <flag name='prosody_modules_pubsub_mqtt'>MQTT is a lightweight binary pubsub protocol suited to embedded devices. This module provides a way for MQTT clients to connect to Prosody and publish or subscribe to local pubsub nodes. (info: https://modules.prosody.im/mod_pubsub_mqtt)</flag> - <flag name='prosody_modules_pubsub_pivotaltracker'>No documentation yet :( (info: https://modules.prosody.im/mod_pubsub_pivotaltracker)</flag> - <flag name='prosody_modules_pubsub_post'>Lets you easily publish data to PubSub using a HTTP POST request. The payload can be Atom feeds, arbitrary XML, or arbitrary JSON. The type should be indicated via the Content-Type header. (info: https://modules.prosody.im/mod_pubsub_post)</flag> - <flag name='prosody_modules_pubsub_stats'>This module publishes data from Prosody’s internal statistics into a PubSub node in XEP-0039 format. (info: https://modules.prosody.im/mod_pubsub_stats)</flag> - <flag name='prosody_modules_pubsub_text_interface'>This module lets you manage subscriptions to pubsub nodes via simple chat messages. Subscriptions are always added based on bare JID. The include_body flag is enabled so that a plain text body version of events can be included, where supported. (info: https://modules.prosody.im/mod_pubsub_text_interface)</flag> - <flag name='prosody_modules_pubsub_twitter'>Twitter has an open ‘realtime’ search API, but it requires polling (within their rate limits). This module allows Prosody to poll for you, and push new results to subscribers over XMPP. (info: https://modules.prosody.im/mod_pubsub_twitter)</flag> - <flag name='prosody_modules_query_client_ver'>This module sends a version query to clients when they connect, and logs the response, allowing statistics of client usage to be recorded. (info: https://modules.prosody.im/mod_query_client_ver)</flag> - <flag name='prosody_modules_rawdebug'>Sometimes it is useful to get the raw XML logs from clients for debugging purposes, but some clients don’t expose this. (info: https://modules.prosody.im/mod_rawdebug)</flag> - <flag name='prosody_modules_readonly'>This module blocks configured queries that change server state. (info: https://modules.prosody.im/mod_readonly)</flag> - <flag name='prosody_modules_register_dnsbl'>This module checks the IP addresses attempting to register an account against a DNSBL, blocking the attempt if there is a hit. (info: https://modules.prosody.im/mod_register_dnsbl)</flag> - <flag name='prosody_modules_register_dnsbl_firewall_mark'>No documentation yet :( (info: https://modules.prosody.im/mod_register_dnsbl_firewall_mark)</flag> - <flag name='prosody_modules_register_dnsbl_warn'>This module checks the IP address of newly registered users against a DNS block list. If a positive match is found, it gets logged. (info: https://modules.prosody.im/mod_register_dnsbl_warn)</flag> - <flag name='prosody_modules_register_json'>This module let’s you activate a httpserver interface to handle data from webforms with POST and Base64 encoded JSON. (info: https://modules.prosody.im/mod_register_json)</flag> - <flag name='prosody_modules_register_oob_url'>Registration redirect to out of band URL as described in XEP-0077: In-Band Registration. (info: https://modules.prosody.im/mod_register_oob_url)</flag> - <flag name='prosody_modules_register_redirect'>Registration Redirect as explained in the IBR XEP. (info: https://modules.prosody.im/mod_register_redirect)</flag> - <flag name='prosody_modules_register_web'>There are various reasons to prefer web registration instead of “in-band” account registration over XMPP. For example the lack of CAPTCHA support in clients and servers. (info: https://modules.prosody.im/mod_register_web)</flag> - <flag name='prosody_modules_reload_components'>This module allows to load/unload external components after they have been added/removed to a configuration file. It is necessary to explicitly initiate a reload on Prosody either via prosodyctl reload or config:reload(). (info: https://modules.prosody.im/mod_reload_components)</flag> - <flag name='prosody_modules_reload_modules'>By default Prosody does not reload modules at runtime unless instructed to via one of its admin interfaces. However sometimes you want to easily reload a module to apply new settings when the config changes. (info: https://modules.prosody.im/mod_reload_modules)</flag> - <flag name='prosody_modules_remote_roster'>This module adds support for XEP-0321: Remote Roster Management which is commonly used to allow components such as transports to modify the rosters of local users. (info: https://modules.prosody.im/mod_remote_roster)</flag> - <flag name='prosody_modules_require_otr'>OTR, “Off The Record”, encryption allows clients to encrypt messages such that the server cannot read/modify them. (info: https://modules.prosody.im/mod_require_otr)</flag> - <flag name='prosody_modules_roster_allinall'>This module is similar in purpouse to mod_groups, for when you want all users on the server to be in each others roster. (info: https://modules.prosody.im/mod_roster_allinall)</flag> - <flag name='prosody_modules_roster_command'>This module allows you to perform various actions on user rosters via prosodyctl. (info: https://modules.prosody.im/mod_roster_command)</flag> - <flag name='prosody_modules_s2s_auth_compat'>This module is a workaround for servers that try to do s2s authentication with certificates and SASL EXTERNAL, but do not send correct stream headers. Notably Openfire versions since 3.7 or 3.8. (info: https://modules.prosody.im/mod_s2s_auth_compat)</flag> - <flag name='prosody_modules_s2s_auth_dane'>This module implements DANE as described in Using DNS Security Extensions (DNSSEC) and DNS-based Authentication of Named Entities (DANE) as a Prooftype for XMPP Domain Name Associations. (info: https://modules.prosody.im/mod_s2s_auth_dane)</flag> - <flag name='prosody_modules_s2s_auth_fingerprint'>This module allows you to manually pin certificate fingerprints of remote servers. (info: https://modules.prosody.im/mod_s2s_auth_fingerprint)</flag> - <flag name='prosody_modules_s2s_auth_monkeysphere'>Monkeysphere is a project aiming to introduce PGP’s web of trust to protocols such as SSH and TLS (which XMPP uses). (info: https://modules.prosody.im/mod_s2s_auth_monkeysphere)</flag> - <flag name='prosody_modules_s2s_auth_posh'>PKIX over Secure HTTP (POSH) describes a method of securely delegating a domain to a hosting provider, without that hosting provider needing keys and certificates covering the hosted domain. (info: https://modules.prosody.im/mod_s2s_auth_posh)</flag> - <flag name='prosody_modules_s2s_auth_samecert'>No documentation yet :( (info: https://modules.prosody.im/mod_s2s_auth_samecert)</flag> - <flag name='prosody_modules_s2s_blacklist'>This module lets you block connections to remote servers at the s2s level. (info: https://modules.prosody.im/mod_s2s_blacklist)</flag> - <flag name='prosody_modules_s2s_idle_timeout'>Some people find it preferable to close server-to-server connections after they have been silent for a while. (info: https://modules.prosody.im/mod_s2s_idle_timeout)</flag> - <flag name='prosody_modules_s2s_keepalive'>This module periodically sends XEP-0199 ping requests to remote servers to keep your connection alive. (info: https://modules.prosody.im/mod_s2s_keepalive)</flag> - <flag name='prosody_modules_s2s_keysize_policy'>This module sets the security status of s2s connections to invalid if their key is too small and their certificate was issued after 2014, per CA/B Forum guidelines. (info: https://modules.prosody.im/mod_s2s_keysize_policy)</flag> - <flag name='prosody_modules_s2s_log_certs'>This module produces info level log messages with the certificate status and fingerprint every time an s2s connection is established. It can also optionally store this in persistent storage. (info: https://modules.prosody.im/mod_s2s_log_certs)</flag> - <flag name='prosody_modules_s2s_never_encrypt_blacklist'>Let’s you stop Prosody from sending <starttls xmlns=‘urn:ietf:params:xml:ns:xmpp-tls’> feature to choppy/buggy servers which therefore would fail to re-negotiate and use a secure stream. (e.g. OpenFire 3.7.0) (info: https://modules.prosody.im/mod_s2s_never_encrypt_blacklist)</flag> - <flag name='prosody_modules_s2s_reload_newcomponent'>Currently, module:reload command in console doesn’t load new components. This module will automatically load the new components (if any) when the config:reload command is run in the console. (info: https://modules.prosody.im/mod_s2s_reload_newcomponent)</flag> - <flag name='prosody_modules_s2s_whitelist'>This module lets you block connections to any remote servers not on a whitelist. (info: https://modules.prosody.im/mod_s2s_whitelist)</flag> - <flag name='prosody_modules_s2soutinjection'>This module is similar to mod_srvinjection but less of an hack. (info: https://modules.prosody.im/mod_s2soutinjection)</flag> - <flag name='prosody_modules_sasl_oauthbearer'>This module adds a new SASL mechanism OAUTHBEARER, as defined in RFC-7628. (info: https://modules.prosody.im/mod_sasl_oauthbearer)</flag> - <flag name='prosody_modules_saslauth_muc'>No documentation yet :( (info: https://modules.prosody.im/mod_saslauth_muc)</flag> - <flag name='prosody_modules_saslname'>This module implements a manual method for advertsing the Kerberos principal name as per XEP-0233. It could be used in conjection with a Kerberos authentication module. (info: https://modules.prosody.im/mod_saslname)</flag> - <flag name='prosody_modules_seclabels'>This module implements XEP-0258: Security Labels in XMPP, but not actual policy enforcement. See for example mod_firewall for that. (info: https://modules.prosody.im/mod_seclabels)</flag> - <flag name='prosody_modules_secure_interfaces'>Sometimes you might run clients without encryption on the same machine or LAN as Prosody - and you want Prosody to treat them as secure ( e.g. allowing plaintext authentication) even though they are not encrypted. (info: https://modules.prosody.im/mod_secure_interfaces)</flag> - <flag name='prosody_modules_server_status'>This module fetches the current status of configured hosts and/or stanza statistics from mod_stanza_counter. And outputs it in either XML or JSON format. (info: https://modules.prosody.im/mod_server_status)</flag> - <flag name='prosody_modules_service_directories'>No documentation yet :( (info: https://modules.prosody.im/mod_service_directories)</flag> - <flag name='prosody_modules_sift'>SIFT is a technology to allow clients to filter incoming traffic on the server. This helps save bandwidth, etc. (info: https://modules.prosody.im/mod_sift)</flag> - <flag name='prosody_modules_slack_webhooks'>This module provides a Slack-compatible “web hook” interface to Prosody MUCs. Both “incoming” web hooks, which allow Slack integrations to post messages to Prosody MUCs, and “outgoing” web hooks, which copy messages from Prosody MUCs to Slack-style integrations by HTTP, are supported. This can also be used, in conjunction with various Slack inter-namespace bridging tools, to provide a bidirectional bridge between a Prosody-hosted XMPP MUC and a Slack channel. (info: https://modules.prosody.im/mod_slack_webhooks)</flag> - <flag name='prosody_modules_smacks'>By default XMPP is as reliable as your network is. Unfortunately in some cases that is not very reliable - in some network conditions disconnects can be frequent and message loss can occur. (info: https://modules.prosody.im/mod_smacks)</flag> - <flag name='prosody_modules_smacks_noerror'>By default mod_smacks sends back error stanzas for every unacked message stanza when the hibernation times out. This leads to “message not delivered” errors displayed in clients. (info: https://modules.prosody.im/mod_smacks_noerror)</flag> - <flag name='prosody_modules_smacks_offline'>No documentation yet :( (info: https://modules.prosody.im/mod_smacks_offline)</flag> - <flag name='prosody_modules_sms_clickatell'>This module provides and SMS gateway component which uses the Clickatell HTTP API to deliver text messages. See clickatell.com for details on their services. Note that at present, this is entirely one way: replies will either go nowhere or as sms to the source number you specify. (info: https://modules.prosody.im/mod_sms_clickatell)</flag> - <flag name='prosody_modules_spam_reporting'>This module is a very basic implementation of XEP-0377: Spam Reporting. (info: https://modules.prosody.im/mod_spam_reporting)</flag> - <flag name='prosody_modules_srvinjection'>This Prosody plugin lets you manually override SRV records used for a remote host. (info: https://modules.prosody.im/mod_srvinjection)</flag> - <flag name='prosody_modules_sslv3_warn'>No documentation yet :( (info: https://modules.prosody.im/mod_sslv3_warn)</flag> - <flag name='prosody_modules_stanza_counter'>This module counts incoming and outgoing stanzas from when the instance started, and makes the data available to other modules by creating a global prosody. object (info: https://modules.prosody.im/mod_stanza_counter)</flag> - <flag name='prosody_modules_stanzadebug'>This module logs the full stanzas that are sent and received into debug logs, for debugging purposes. (info: https://modules.prosody.im/mod_stanzadebug)</flag> - <flag name='prosody_modules_statistics'>No documentation yet :( (info: https://modules.prosody.im/mod_statistics)</flag> - <flag name='prosody_modules_statistics_auth'>No documentation yet :( (info: https://modules.prosody.im/mod_statistics_auth)</flag> - <flag name='prosody_modules_statistics_cputotal'>No documentation yet :( (info: https://modules.prosody.im/mod_statistics_cputotal)</flag> - <flag name='prosody_modules_statistics_mem'>No documentation yet :( (info: https://modules.prosody.im/mod_statistics_mem)</flag> - <flag name='prosody_modules_statistics_statsd'>No documentation yet :( (info: https://modules.prosody.im/mod_statistics_statsd)</flag> - <flag name='prosody_modules_statistics_statsman'>A module providing a streaming statistics interface like mod_statistics but based on the new statistics API introduced in Prosody 0.10. (info: https://modules.prosody.im/mod_statistics_statsman)</flag> - <flag name='prosody_modules_statsd'>No documentation yet :( (info: https://modules.prosody.im/mod_statsd)</flag> - <flag name='prosody_modules_storage_appendmap'>This is an experimental storage driver where changed data is appended. Data is simply written as key = value pairs to the end of the file. This allows changes to individual keys to be written without needing to write out the entire object again, but reads would grow gradually larger as it still needs to read old overwritten keys. This may be suitable for e.g. rosters where individual contacts are changed at a time. In theory, this could also allow rolling back changes. (info: https://modules.prosody.im/mod_storage_appendmap)</flag> - <flag name='prosody_modules_storage_ejabberdsql_readonly'>This is a storage backend using Ejabberd’s SQL backend. It depends on LuaDBI (info: https://modules.prosody.im/mod_storage_ejabberdsql_readonly)</flag> - <flag name='prosody_modules_storage_gdbm'>This is a storage module using GNU DBM as backend. It supports archives. (info: https://modules.prosody.im/mod_storage_gdbm)</flag> - <flag name='prosody_modules_storage_ldap'>See mod_lib_ldap for more information. (info: https://modules.prosody.im/mod_storage_ldap)</flag> - <flag name='prosody_modules_storage_lmdb'>This is a storage module using OpenLDAP Lightning Memory-Mapped Database as backend. (info: https://modules.prosody.im/mod_storage_lmdb)</flag> - <flag name='prosody_modules_storage_memory'>This module acts as a normal storage module for Prosody, but saves all data in memory only. All data is lost when the server stops. This makes it useful for testing, or certain specialized applications. (info: https://modules.prosody.im/mod_storage_memory)</flag> - <flag name='prosody_modules_storage_mongodb'>This is a storage backend that uses MongoDB. Depends on luamongo bindings (info: https://modules.prosody.im/mod_storage_mongodb)</flag> - <flag name='prosody_modules_storage_muc_log'>mod_muc_log provided logging of chatrooms running on the server to Prosody’s data store. This module gives access to this data using the 0.10+ stanza archive API, allowing legacy log data to be used with mod_mam_muc and mod_http_muc_log. (info: https://modules.prosody.im/mod_storage_muc_log)</flag> - <flag name='prosody_modules_storage_muconference_readonly'>This is a storage backend using MU-Conference’s SQL storage. It depends on LuaDBI (info: https://modules.prosody.im/mod_storage_muconference_readonly)</flag> - <flag name='prosody_modules_storage_multi'>This module attemtps to provide a storage driver that is really multiple storage drivers. This could be used for storage error tolerance or caching of data in a faster storage driver. (info: https://modules.prosody.im/mod_storage_multi)</flag> - <flag name='prosody_modules_storage_xmlarchive'>This module implements stanza archives using files, similar to the default “internal” storage. Unlike “internal”, it saves messages in two files per day (and per user), one containing metadata and one containing the actual messages in XML format (hence the name). (info: https://modules.prosody.im/mod_storage_xmlarchive)</flag> - <flag name='prosody_modules_streamstats'>No documentation yet :( (info: https://modules.prosody.im/mod_streamstats)</flag> - <flag name='prosody_modules_strict_https'>This module implements HTTP Strict Transport Security and responds to all non-HTTPS requests with a 301 Moved Permanently redirect to the HTTPS equivalent of the path. (info: https://modules.prosody.im/mod_strict_https)</flag> - <flag name='prosody_modules_support_contact'>This Prosody plugin adds a default contact to newly registered accounts. (info: https://modules.prosody.im/mod_support_contact)</flag> - <flag name='prosody_modules_support_room'>This module adds newly registered users as members to a specified MUC room and sends them an invite. In a way, this is similar in purpose to mod_support_contact and mod_default_bookmarks. (info: https://modules.prosody.im/mod_support_room)</flag> - <flag name='prosody_modules_swedishchef'>This module does some conversions on message bodys passed through it causing them to look like our beloved swedish chef had typed them. (info: https://modules.prosody.im/mod_swedishchef)</flag> - <flag name='prosody_modules_tcpproxy'>It happens occasionally that I would like to use the XMPP server as a generic proxy for connecting to another service. It is especially awkward in some environments, and impossible in (for example) Javascript inside a web browser. (info: https://modules.prosody.im/mod_tcpproxy)</flag> - <flag name='prosody_modules_telnet_tlsinfo'>This module adds two commands to the telnet console, c2s:showtls() and s2s:showtls(). These commands shows TLS parameters, such as ciphers and key agreement protocols, of all c2s or s2s connections. (info: https://modules.prosody.im/mod_telnet_tlsinfo)</flag> - <flag name='prosody_modules_test_data'>This module is of use to developers who want to fill their Prosody storage with test data, e.g. for debugging, testing or performance measurements of Prosody or client code. (info: https://modules.prosody.im/mod_test_data)</flag> - <flag name='prosody_modules_throttle_presence'>For most people ‘presence’ (status changes) of contacts make up most of the traffic received by their client. However much of the time it is not essential to have highly accurate presence information. (info: https://modules.prosody.im/mod_throttle_presence)</flag> - <flag name='prosody_modules_throttle_unsolicited'>This module limits the rate of outgoing unsolicited messages from local clients. Optionally, unsolicited messages coming in from remote servers may be limited per s2s conneciton. A message counts as “unsolicited” if the receiving user hasn’t added the sending user to their roster. (info: https://modules.prosody.im/mod_throttle_unsolicited)</flag> - <flag name='prosody_modules_tls_policy'>This module arose from discussions at the XMPP Summit about enforcing better ciphers in TLS. It may seem attractive to disallow some insecure ciphers or require forward secrecy, but doing this at the TLS level would the user with an unhelpful “Encryption failed” message. This module does this enforcing at the application level, allowing better error messages. (info: https://modules.prosody.im/mod_tls_policy)</flag> - <flag name='prosody_modules_traceback'>This module writes out a traceback to traceback.txt in Prosodys data directory (see prosodyctl about) when the signal SIGUSR1 is received. This is useful when debugging seemingly frozen instances in case it is stuck in Lua code. (info: https://modules.prosody.im/mod_traceback)</flag> - <flag name='prosody_modules_track_muc_joins'>This module attempts to keep track of what MUC chat rooms users have joined. It’s not very useful on its own, but can be used by other modules to influence decisions. (info: https://modules.prosody.im/mod_track_muc_joins)</flag> - <flag name='prosody_modules_turncredentials'>XEP-0215 implementation for time-limited TURN credentials. (info: https://modules.prosody.im/mod_turncredentials)</flag> - <flag name='prosody_modules_twitter'>Twitter has simple API to use, so I tried to deal with it via Prosody. I didn’t manage to finish this module, but it is nice example of component that accepts registrations, unregistrations, does HTTP polling and so on. Maybe someone will finnish this idea. (info: https://modules.prosody.im/mod_twitter)</flag> - <flag name='prosody_modules_uptime_presence'>This module simply responds to a presence probe sent to the server with a presence staza containing a timestamp from when the server started. (info: https://modules.prosody.im/mod_uptime_presence)</flag> - <flag name='prosody_modules_vcard_command'>No documentation yet :( (info: https://modules.prosody.im/mod_vcard_command)</flag> - <flag name='prosody_modules_vcard_muc'>This module adds the ability to set vCard for MUC rooms. One of the most common use case is to be able to define an avatar for your own MUC room. (info: https://modules.prosody.im/mod_vcard_muc)</flag> - <flag name='prosody_modules_vjud'>Basic implementation of XEP-0055: Jabber Search. (info: https://modules.prosody.im/mod_vjud)</flag> - <flag name='prosody_modules_watchuntrusted'>Similar to mod_watchregistrations, this module warns admins when an s2s connection fails due for encryption or trust reasons. (info: https://modules.prosody.im/mod_watchuntrusted)</flag> - <flag name='prosody_modules_webpresence'>Quite often you may want to publish your Jabber status to your blog or website. mod_webpresence allows you to do exactly this. (info: https://modules.prosody.im/mod_webpresence)</flag> - <flag name='prosody_modules_xhtmlim'>This module attempts to sanitize XHTML-IM messages. (info: https://modules.prosody.im/mod_xhtmlim)</flag> - </use> -</pkgmetadata> diff --git a/net-im/prosody-modules/prosody-modules-9999.ebuild b/net-im/prosody-modules/prosody-modules-9999.ebuild deleted file mode 100644 index 731a429..0000000 --- a/net-im/prosody-modules/prosody-modules-9999.ebuild +++ /dev/null @@ -1,197 +0,0 @@ -# Copyright 1999-2019 Gentoo Foundation -# Distributed under the terms of the GNU General Public License v2 - -EAPI=6 - -inherit eutils multilib mercurial - -DESCRIPTION="Add-on modules for Prosody IM Server written in Lua." -HOMEPAGE="https://modules.prosody.im/"; -EHG_REPO_URI="https://hg.prosody.im/prosody-modules"; - -LICENSE="MIT" -SLOT="0" -KEYWORDS="" - -IUSE="misc luajit" - -PROSODY_MODULES=" - addressing adhoc_account_management adhoc_blacklist adhoc_dataforms_demo - adhoc_groups admin_blocklist admin_message admin_probe admin_web alias - atom auth_any auth_ccert auth_custom_http auth_dovecot auth_external - auth_ha1 auth_http_async auth_http_cookie auth_imap - auth_internal_yubikey auth_joomla auth_ldap auth_ldap2 auth_oauthbearer - auth_pam auth_phpbb3 auth_sql auth_token auth_wordpress - auto_accept_subscriptions auto_activate_hosts auto_answer_disco_info - benchmark_storage bidi block_outgoing block_registrations - block_s2s_subscriptions block_strangers block_subscribes - block_subscriptions blocking bob bookmarks bookmarks2 broadcast c2s_conn_throttle - c2s_limit_sessions cache_c2s_caps captcha_registration carbons - carbons_adhoc carbons_copies checkcerts client_certs client_proxy - cloud_notify compact_resource compat_bind compat_dialback - compat_muc_admin compat_vcard component_client component_http - component_roundrobin compression_unsafe conformance_restricted - conversejs couchdb csi csi_battery_saver csi_compat csi_pump data_access - default_bookmarks default_vcard delay delegation deny_omemo devices - disable_tls discoitems dwd e2e_policy email_pass extdisco fallback_vcard - filter_chatstates filter_words firewall flash_policy graceful_shutdown - group_bookmarks host_blacklist host_guard host_status_check - host_status_heartbeat http_altconnect http_auth_check - http_authentication http_avatar http_dir_listing http_dir_listing2 - http_favicon http_host_status_check http_hostaliases http_index - http_logging http_muc_log http_pep_avatar http_rest http_roster_admin - http_stats_stream http_upload http_upload_external http_user_count - idlecompat ignore_host_chatstates incidents_handling inject_ecaps2 - inotify_reload invite ipcheck isolate_host jid_prep json_streams lastlog - latex lib_ldap limit_auth limits list_active list_inactive listusers - log_auth log_events log_http log_mark log_messages_sql log_rate - log_sasl_mech log_slow_events mam mam_adhoc mam_archive mam_muc mamsub - manifesto measure_client_features measure_client_identities - measure_client_presence measure_cpu measure_malloc measure_memory - measure_message_e2ee measure_message_length measure_stanza_counts - measure_storage message_logging migrate minimix motd_sequential - muc_access_control muc_badge muc_ban_ip muc_block_pm muc_cloud_notify - muc_config_restrict muc_eventsource muc_gc10 muc_intercom muc_lang - muc_limits muc_log muc_log_http muc_ping muc_restrict_rooms munin - net_dovecotauth net_proxy offline_email omemo_all_access onhold onions - openid password_policy password_reset pastebin pep_vcard_avatar - pep_vcard_png_avatar persisthosts pinger poke_strangers post_msg - presence_cache presence_dedup privacy_lists private_adhoc privilege - proctitle profile prometheus proxy65_whitelist pubsub_eventsource - pubsub_feeds pubsub_github pubsub_hub pubsub_mqtt pubsub_pivotaltracker - pubsub_post pubsub_stats pubsub_text_interface pubsub_twitter - query_client_ver rawdebug readonly register_dnsbl - register_dnsbl_firewall_mark register_dnsbl_warn register_json - register_oob_url register_redirect register_web reload_components - reload_modules remote_roster require_otr roster_allinall roster_command - s2s_auth_compat s2s_auth_dane s2s_auth_fingerprint s2s_auth_monkeysphere - s2s_auth_posh s2s_auth_samecert s2s_blacklist s2s_idle_timeout - s2s_keepalive s2s_keysize_policy s2s_log_certs - s2s_never_encrypt_blacklist s2s_reload_newcomponent s2s_whitelist - s2soutinjection sasl_oauthbearer saslauth_muc saslname seclabels - secure_interfaces server_status service_directories sift slack_webhooks - smacks smacks_noerror smacks_offline sms_clickatell spam_reporting - srvinjection sslv3_warn stanza_counter stanzadebug statistics - statistics_auth statistics_cputotal statistics_mem statistics_statsd - statistics_statsman statsd storage_appendmap - storage_ejabberdsql_readonly storage_gdbm storage_ldap storage_lmdb - storage_memory storage_mongodb storage_muc_log - storage_muconference_readonly storage_multi storage_xmlarchive - streamstats strict_https support_contact support_room swedishchef - tcpproxy telnet_tlsinfo test_data throttle_presence throttle_unsolicited - tls_policy traceback track_muc_joins turncredentials twitter - uptime_presence vcard_command vcard_muc vjud watchuntrusted webpresence - xhtmlim -" - -for x in ${PROSODY_MODULES}; do - IUSE="${IUSE} ${x//[^+]/}prosody_modules_${x/+}" -done - -DEPEND="net-im/prosody" -RDEPEND=" - ${DEPEND} - prosody_modules_inotify_reload? ( - dev-lua/linotify - ) - prosody_modules_auth_joomla? ( - dev-lua/luadbi - ) - prosody_modules_lib_ldap? ( - dev-lua/lualdap - ) - prosody_modules_client_certs? ( - dev-lua/luasec - ) - prosody_modules_listusers? ( - dev-lua/luasocket - dev-lua/luafilesystem - ) - prosody_modules_pubsub_pivotaltracker? ( - dev-lua/luaexpat - ) - prosody_modules_auth_phpbb3? ( - dev-lua/luadbi - ) - prosody_modules_log_messages_sql? ( - dev-lua/luadbi - ) - prosody_modules_message_logging? ( - dev-lua/luafilesystem - ) - prosody_modules_onions? ( - virtual/lua[bit] - ) - prosody_modules_couchdb? ( - dev-lua/luasocket - ) - prosody_modules_auth_custom_http? ( - dev-lua/luasocket - ) - prosody_modules_checkcerts? ( - dev-lua/luasec - ) - prosody_modules_auth_internal_yubikey? ( - virtual/lua[bit,luajit=] - dev-lua/yubikey-lua - ) - prosody_modules_auth_dovecot? ( - dev-lua/luasocket - ) - prosody_modules_storage_ldap? ( - dev-lua/luasocket - ) - prosody_modules_statistics? ( - dev-lua/luaposix[ncurses] - ) - prosody_modules_http_dir_listing? ( - dev-lua/luasocket - dev-lua/luafilesystem - ) - prosody_modules_log_messages_sql? ( - dev-lua/luasocket - dev-lua/luadbi - ) - prosody_modules_storage_mongodb? ( - dev-lua/luamongo - ) - prosody_modules_offline_email? ( - dev-lua/luasocket - ) - prosody_modules_auth_wordpress? ( - dev-lua/luadbi - ) - prosody_modules_muc_log_http? ( - dev-lua/luafilesystem - dev-lua/luaexpat - ) - prosody_modules_component_client? ( - dev-lua/luasocket - ) - prosody_modules_auth_external? ( - dev-lua/lpc - ) - prosody_modules_auth_sql? ( - dev-lua/luadbi - ) -" - -REQUIRED_USE=" - prosody_modules_auth_ldap? ( prosody_modules_lib_ldap ) - prosody_modules_auth_ldap2? ( prosody_modules_lib_ldap ) -" - -src_install() { - cd "${S}"; - use prosody_modules_mam || ewarn "mod_mam is ignored. Using prosody's instead." - for m in ${PROSODY_MODULES//mam /}; do - if use prosody_modules_${m}; then - insinto /usr/lib/prosody/modules; - doins -r "mod_${m}" - fi - done - use misc && ( - insinto /usr/lib/prosody/modules - doins -r misc - ) -}
