this post was submitted on 18 Oct 2023
2 points (100.0% liked)

ntfy

10 readers
3 users here now

ntfy (pronounced notify) is a simple HTTP-based pub-sub notification service. You can use it to send push notifications to your phone via HTTP PUT/POST.

ntfy website • Documentation • GitHub • Google Play • F-Droid • Discord • App Store • Matrix

If you'd like to become a sponsor, I would be humbled to accept your donation via GitHub Sponsors or Liberapay 💸💰.

founded 1 year ago
MODERATORS
[email protected]
2
message-expiry-duration vs cache-duration config options (lemm.ee)
submitted 1 year ago by [email protected] to c/[email protected]
2 comments fedilink hide all child comments
 

What is the difference between the two.

The cache-duration is explained in the docs and is fairly clear:

Duration for which messages will be buffered before they are deleted

so it is to account for network interruptions of subscribers.

message-expiry-duration is mentioned but there is no explanation for it in the docs.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

--message-expiry-duration is an option that you can pass when creating a new tier (in your selfhosted instance). It is equivalent to the cache-duration for users publishing in that tier.

For instance, if you are a ntfy Pro user, your messages are cached much longer than the normal 12h (see https://ntfy.sh/v1/tiers).

The naming is a little odd. I think cache-duration should probably be called something else.

[–] [email protected] 2 points 1 year ago

Not quite clear.

Given I have no tiers, I am covered just with cache-duration and can completely ignore message-expiry-duration?

I have a single service that POSTs messages to ntfy which sends them to subscribers. Any subscriber will have to connect within cache-duration or else ntfy deletes messages older than that from the database. Is that accurate? The intention is to keep the sqlite db lean and small.