This release changes the way UnifiedPush (UP) topics are rate limited from publisher-based rate limiting to subscriber-based rate limiting. This allows UP application servers to send higher volumes, since the subscribers carry the rate limits. However, it also means that UP clients have to subscribe to a topic first before they are allowed to publish. If they do no, clients will receive an HTTP 507 response from the server.
We also fixed another issue with UnifiedPush: Some Mastodon servers were sending unsupported Authorization headers, which ntfy rejected with an HTTP 401. We now ignore unsupported header values.
As of this release, ntfy also supports sending emails to protected topics, and it ships code to support annual billing cycles (not live yet).
As part of this release, I also enabled sign-up and login (free accounts only), and I also started reducing the rate limits for anonymous & free users a bit. With the next release and the launch of the paid plan, I'll reduce the limits a bit more. For 90% of users, you should not feel the difference.
Features:
- UnifiedPush: Subscriber-based rate limiting for
up*topics (#584/#609/#633, thanks to @karmanyaahm) - Support for publishing to protected topics via email with access tokens (#612, thanks to @tamcore)
- Support for base64-encoded and nested multipart emails (#610, thanks to @Robert-litts)
- Payments: Add support for annual billing intervals (no ticket)
Bug fixes + maintenance:
- Web: Do not disable "Reserve topic" checkbox for admins (no ticket, thanks to @xenrox for reporting)
- UnifiedPush: Treat non-Basic/Bearer
Authorizationheader like header was not sent (#629, thanks to @Boebbele and @S1m for reporting)
Documentation:
Additional languages:
- Arabic (thanks to @ButterflyOfFire)