--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.

Go to “http://ntfy.example.com/mytopic/json?poll=1”

With your selfhosted URL and your topic filled in. See what you get back. You can also enable debugging to see if there any clues in the logs, both Android or the server.

https://docs.ntfy.sh/troubleshooting/

Can you elaborate what you mean by “it is asking”? Are you using the Android app or iOS app? Which screen? Can you provide a step by step of what you’re doing, or a screenshot?

It’s probably easy as pie to implement. Feel free to open a ticket on GitHub.

Got it. Yeah no that’s not supported. I have thought about adding that many times, but nobody’s asked for it so far.

I’d probably call them extras though or something, so it’d be:

{
 "topic": "1234", 
 "message": "foo",
 "title": "bar",
 "extras": {
   "customField": "baz"
 }
}

Just try it out. I make no guarantees for odd setups like that though. :-)

It is not possible to log to both. I’m sure there is some Unix trick to do both, but I don’t know.

Can you make an example? Like, you want to just send custom fields when you publish the message and then pass it along to where?

Thanks you for considering a donation.

Open Collective does not accept single-maintainer projects. I tried to open an account and had an email exchange with a person there, and they told me that I’d need a second owner for the account.

I can dig up the exact wording, but there’s sadly not much I can do.

That … actually looks and feels pretty slick. Very neat UI.

Great writeup thank you. May I just say that tmyour original plan was both ambitious and a little insane. And even the current cost and infrastructure is bonkers IMHO.

I do hope you’re getting donations to help with the cost. Good luck.

My instance is on the other end of the spectrum: I pay $6/month for it on digitalocean. It has 1G of RAM. It crashes every now and then, likely because of the RAM and OOM killer. But it’s only for me and a few ntfy fans, so it’s quite different.

I do cover the costs yes, through donations and the paid plans.

It’s definitely fun to do some things, but others are daunting indeed. I do, however, learn a lot. I have learned a lot that I was able to reuse elsewhere. All that is priceless.

Thanks. I don’t work on it full time, no. It’s a side gig project I’ve been doing for a year and a half. I recently added paid plans to get a little side income, but it’s not really taken off. Likely because the free tier is too generous hehe.

Use ntfy.sh. It’s open source and has a free server.

Disclaimer: I made it ;-)

You can type reset to fix your terminal if it gets messed up like that.

In case you’re wondering, yes, I was notified about this post via the script 😂

Here ya go. ChatGPT did all the hard work: https://chat.openai.com/share/7703dbe5-6801-4d5b-8d56-c3f18ca3ac4a

Edit: here’s a manually refined version: https://gist.github.com/binwiederhier/70f13b7c7338a2b75e15438b5567a6d6

That’s what saving the IDs is for right? It’s easy enough to do in a bash script I think. I’ll post it here later, assuming I get it to work.

Oh that’s a good idea. Any reader suggestions? I have thought about trying RSS again for a while. Maybe this is a good enough reason.

Thanks dude. I’m going to try the curl route. What do you mean by it sends you every post? Isn’t that what I want?