File

mod_cloud_notify(all the extentions): remove rockspec dependemcy so the prosody community module does not get installed, since trunk already has it. diff --git a/mod_cloud_notify_encrypted/README.md b/mod_cloud_notify_encrypted/README.md --- a/mod_cloud_notify_encrypted/README.md +++ b/mod_cloud_notify_encrypted/README.md @@ -2,9 +2,6 @@ labels: - 'Stage-Alpha' summary: 'Support for encrypted payloads in push notifications' -rockspec: - dependencies: - - mod_cloud_notify ... Introduction diff --git a/mod_cloud_notify_filters/README.md b/mod_cloud_notify_filters/README.md --- a/mod_cloud_notify_filters/README.md +++ b/mod_cloud_notify_filters/README.md @@ -2,9 +2,6 @@ labels: - 'Stage-Alpha' summary: 'Support for push notification filtering rules' -rockspec: - dependencies: - - mod_cloud_notify ... Introduction diff --git a/mod_cloud_notify_priority_tag/README.md b/mod_cloud_notify_priority_tag/README.md --- a/mod_cloud_notify_priority_tag/README.md +++ b/mod_cloud_notify_priority_tag/README.md @@ -2,9 +2,6 @@ labels: - 'Stage-Alpha' summary: 'Support for indicating importance to push notification servers' -rockspec: - dependencies: - - mod_cloud_notify ... Introduction

---
summary: Allow specified JIDs to bypass rate limits
...

This module allows you to configure a list of JIDs that should be allowed to
bypass rate limit restrictions.

It is designed for Prosody 0.11.x. Prosody 0.12.x supports this feature
natively.

## Configuration

First, enable this module by adding `"limits_exception"` to your
`modules_enabled` list.

Next, configure a list of JIDs to exclude from rate limiting:

```
unlimited_jids = { "user1@example.com", "user2@example.net" }
```

## Compatibility

Made for Prosody 0.11.x only.

Using this module with Prosody trunk/0.12 may cause unexpected behaviour.