Python-ntfy

Latest version: v0.4.5

Safety actively analyzes 706267 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 9

2.1.1

Released March 1, 2023

This is a tiny release with a few bug fixes, but it's big for me personally. After almost three months of work,
**today I am finally launching the paid plans on ntfy.sh** 🥳 🎉.

You are now able to purchase one of three plans that'll give you **higher rate limits** (messages, emails, attachment sizes, ...),
as well as the ability to **reserve topic names** for your personal use, while at the same time supporting me and the
ntfy open source project ❤️. You can check out the pricing, and [purchase plans through the web app](https://ntfy.sh/app) (use
promo code `MYTOPIC` for a **50% discount**, limited time only).

And as I've said many times: Do not worry. **ntfy will always stay open source**, and that includes all features. There
are no closed-source features. So if you'd like to run your own server, you can!

**Bug fixes + maintenance:**

* Fix panic when using Firebase without users ([641](https://github.com/binwiederhier/ntfy/issues/641), thanks to [u/heavybell](https://www.reddit.com/user/heavybell/) for reporting)
* Remove health check from `Dockerfile` and [document it](config.mdhealth-checks) ([635](https://github.com/binwiederhier/ntfy/issues/635), thanks to [Andersbiha](https://github.com/Andersbiha))
* Upgrade dialog: Disable submit button for free tier (no ticket)
* Allow multiple `log-level-overrides` on the same field (no ticket)
* Actually remove `ntfy publish --env-topic` flag (as per [deprecations](deprecations.md), no ticket)
* Added `billing-contact` config option (no ticket)

2.1.0

Released February 25, 2023

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](https://github.com/binwiederhier/ntfy/pull/584)/[#609](https://github.com/binwiederhier/ntfy/pull/609)/[#633](https://github.com/binwiederhier/ntfy/pull/633), thanks to [karmanyaahm](https://github.com/karmanyaahm))
* Support for publishing to protected topics via email with access tokens ([612](https://github.com/binwiederhier/ntfy/pull/621), thanks to [tamcore](https://github.com/tamcore))
* Support for base64-encoded and nested multipart emails ([610](https://github.com/binwiederhier/ntfy/issues/610), thanks to [Robert-litts](https://github.com/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 `Authorization` header like header was not sent ([629](https://github.com/binwiederhier/ntfy/issues/629), thanks to [Boebbele](https://github.com/Boebbele) and [S1m](https://github.com/S1m) for reporting)

**Documentation:**

* Added example for [Traccar](https://ntfy.sh/docs/examples/#traccar) ([631](https://github.com/binwiederhier/ntfy/pull/631), thanks to [tamcore](https://github.com/tamcore))

**Additional languages:**

* Arabic (thanks to [ButterflyOfFire](https://hosted.weblate.org/user/ButterflyOfFire/))

2.0.1

Released February 17, 2023

This is a quick bugfix release to address a panic that happens when `attachment-cache-dir` is not set.

**Bug fixes + maintenance:**

* Avoid panic in manager when `attachment-cache-dir` is not set ([617](https://github.com/binwiederhier/ntfy/issues/617), thanks to [ksurl](https://github.com/ksurl))
* Ensure that calls to standard logger `log.Println` also output JSON (no ticket)

2.0.0

Released February 16, 2023

This is the biggest ntfy server release I've ever done 🥳 . Lots of new and exciting features.

**Brand-new features:**

* **User signup/login & account sync**: If enabled, users can now register to create a user account, and then login to
the web app. Once logged in, topic subscriptions and user settings are stored server-side in the user account (as
opposed to only in the browser storage). So far, this is implemented only in the web app only. Once it's in the Android/iOS
app, you can easily keep your account in sync. Relevant [config options](config.mdconfig-options) are `enable-signup` and
`enable-login`.
<div id="account-screenshots" class="screenshots">
<a href="../../static/img/web-signup.png"><img src="../../static/img/web-signup.png"/></a>
<a href="../../static/img/web-account.png"><img src="../../static/img/web-account.png"/></a>
</div>
* **Topic reservations** 🎉: If enabled, users can now **reserve topics and restrict access to other users**.
Once this is fully rolled out, you may reserve `ntfy.sh/philbackups` and define access so that only you can publish/subscribe
to the topic. Reservations let you claim ownership of a topic, and you can define access permissions for others as
`deny-all` (only you have full access), `read-only` (you can publish/subscribe, others can subscribe), `write-only` (you
can publish/subscribe, others can publish), `read-write` (everyone can publish/subscribe, but you remain the owner).
Topic reservations can be [configured](config.mdconfig-options) in the web app if `enable-reservations` is enabled, and
only if the user has a [tier](config.mdtiers) that supports reservations.
<div id="reserve-screenshots" class="screenshots">
<a href="../../static/img/web-reserve-topic.png"><img src="../../static/img/web-reserve-topic.png"/></a>
<a href="../../static/img/web-reserve-topic-dialog.png"><img src="../../static/img/web-reserve-topic-dialog.png"/></a>
</div>
* **Access tokens:** It is now possible to create user access tokens for a user account. Access tokens are useful
to avoid having to paste your password to various applications or scripts. For instance, you may want to use a
dedicated token to publish from your backup host, and one from your home automation system. Tokens can be configured
in the web app, or via the `ntfy token` command. See [creating tokens](config.mdaccess-tokens),
and [publishing using tokens](publish.mdaccess-tokens).
<div id="token-screenshots" class="screenshots">
<a href="../../static/img/web-token-create.png"><img src="../../static/img/web-token-create.png"/></a>
<a href="../../static/img/web-token-list.png"><img src="../../static/img/web-token-list.png"/></a>
</div>
* **Structured logging:** I've redone a lot of the logging to make it more structured, and to make it easier to debug and
troubleshoot. Logs can now be written to a file, and as JSON (if configured). Each log event carries context fields
that you can filter and search on using tools like `jq`. On top of that, you can override the log level if certain fields
match. For instance, you can say `user_name=phil -> debug` to log everything related to a certain user with debug level.
See [logging & debugging](config.mdlogging-debugging).
* **Tiers:** You can now define and associate usage tiers to users. Tiers can be used to grant users higher limits, such as
daily message limits, attachment size, or make it possible for users to reserve topics. You could, for instance, have
a tier `Standard` that allows 500 messages/day, 15 MB attachments and 5 allowed topic reservations, and another
tier `Friends & Family` with much higher limits. For ntfy.sh, I'll mostly use these tiers to facilitate paid plans (see below).
Tiers can be configured via the `ntfy tier ...` command. See [tiers](config.mdtiers).
* **Paid tiers:** Starting very soon, I will be offering paid tiers for ntfy.sh on top of the free service. You'll be
able to subscribe to tiers with higher rate limits (more daily messages, bigger attachments) and topic reservations.
Paid tiers are facilitated by integrating [Stripe](https://stripe.com) as a payment provider. See [payments](config.md#payments)
for details.

**ntfy is forever open source!**
Yes, I will be offering some paid plans. But you don't need to panic! I won't be taking any features away, and everything
will remain forever open source, so you can self-host if you like. Similar to the donations via [GitHub Sponsors](https://github.com/sponsors/binwiederhier)
and [Liberapay](https://en.liberapay.com/ntfy/), paid plans will help pay for the service and keep me motivated to keep
going. It'll only make ntfy better.

**Other tickets:**

* User account signup, login, topic reservations, access tokens, tiers etc. ([522](https://github.com/binwiederhier/ntfy/issues/522))
* `OPTIONS` method calls are not serviced when the UI is disabled ([598](https://github.com/binwiederhier/ntfy/issues/598), thanks to [enticedwanderer](https://github.com/enticedwanderer) for reporting)

**Special thanks:**

A big Thank-you goes to everyone who tested the user account and payments work. I very much appreciate all the feedback,
suggestions, and bug reports. Thank you, nwithan8, deadcade, xenrox, cmeis, wunter8 and the others who I forgot.

1.31.0

Released February 14, 2023

This is a tiny release before the really big release, and also the last before the big v2.0.0. The most interesting
things in this release are the new preliminary health endpoint to allow monitoring in K8s (and others), and the removal
of `upx` binary packing (which was causing erroneous virus flagging). Aside from that, the `go-smtp` library did a
breaking-change upgrade, which required some work to get working again.

**Features:**

* Preliminary `/v1/health` API endpoint for service monitoring (no ticket)
* Add basic health check to `Dockerfile` ([555](https://github.com/binwiederhier/ntfy/pull/555), thanks to [bt90](https://github.com/bt90))

**Bug fixes + maintenance:**

* Fix `chown` issues with RHEL-like based systems ([566](https://github.com/binwiederhier/ntfy/issues/566)/[#565](https://github.com/binwiederhier/ntfy/pull/565), thanks to [danieldemus](https://github.com/danieldemus))
* Removed `upx` (binary packing) for all builds due to false virus warnings ([576](https://github.com/binwiederhier/ntfy/issues/576), thanks to [shawnhwei](https://github.com/shawnhwei) for reporting)
* Upgraded `go-smtp` library and tests to v0.16.0 ([569](https://github.com/binwiederhier/ntfy/issues/569))

**Documentation:**

* Add HTTP/2 and TLSv1.3 support to nginx docs ([553](https://github.com/binwiederhier/ntfy/issues/553), thanks to [bt90](https://github.com/bt90))
* Small wording change for `client.yml` ([562](https://github.com/binwiederhier/ntfy/pull/562), thanks to [fleopaulD](https://github.com/fleopaulD))
* Fix K8s install docs ([582](https://github.com/binwiederhier/ntfy/pull/582), thanks to [Remedan](https://github.com/Remedan))
* Updated Jellyseer docs ([604](https://github.com/binwiederhier/ntfy/pull/604), thanks to [Y0ngg4n](https://github.com/Y0ngg4n))
* Updated iOS developer docs ([605](https://github.com/binwiederhier/ntfy/pull/605), thanks to [SticksDev](https://github.com/SticksDev))

**Additional languages:**

* Portuguese (thanks to [ssantos](https://hosted.weblate.org/user/ssantos/))

1.30.1

Released December 23, 2022 🎅

This is a special holiday edition version of ntfy, with all sorts of holiday fun and games, and hidden quests.
Nahh, just kidding. This release is an intermediate release mainly to eliminate warnings in the logs, so I can
roll out the TLSv1.3, HTTP/2 and Unix mode changes on ntfy.sh (see [552](https://github.com/binwiederhier/ntfy/issues/552)).

**Features:**

* Web: Generate random topic name button ([453](https://github.com/binwiederhier/ntfy/issues/453), thanks to [yardenshoham](https://github.com/yardenshoham))
* Add [Gitpod config](https://github.com/binwiederhier/ntfy/blob/main/.gitpod.yml) ([#540](https://github.com/binwiederhier/ntfy/pull/540), thanks to [yardenshoham](https://github.com/yardenshoham))

**Bug fixes + maintenance:**

* Remove `--env-topic` option from `ntfy publish` as per [deprecation](deprecations.md) (no ticket)
* Prepared statements for message cache writes ([542](https://github.com/binwiederhier/ntfy/pull/542), thanks to [nicois](https://github.com/nicois))
* Do not warn about invalid IP address when behind proxy in unix socket mode (relates to [552](https://github.com/binwiederhier/ntfy/issues/552))
* Upgrade nginx/ntfy config on ntfy.sh to work with TLSv1.3, HTTP/2 ([552](https://github.com/binwiederhier/ntfy/issues/552), thanks to [bt90](https://github.com/bt90))

Page 3 of 9

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.