Funny, I was just looking for an alternative to pushover that doesn't use google services last week. Tested this and it worked quite well. I actually wound up just using an SMS gateway provider with a simple API you can just fire a get request to.
I had exactly the same problem, and ended up using Signal. I like it more than normal push notifications because you can reply and have a full chatbot running.
Awesome! I've been working on a collection of news source parsers [1] (a combination of RSS and HTML scrapers) that this will work perfect with to replace my native news app. All I have to do is pipe the lines from my parser through a Python script issuing these message POST requests and it just works out of the box.
I get why that's "yuck" but if I'd hedge a bet...it's probably done because it's easier to make a GET than it is a POST or PUT request and the length of a text message will never exceed the query string uri length limits. Not saying I disagree, but i don't know it changes a whole lot in this case.
How is a GET request easier? I assume you need to include authentication somehow, so it isn't like you are triggering it by typing the url in a browser.
Is there a standard understanding of what are push notifications? Are they the same for android and iOS? I’m not sure what this project is about!
https://en.wikipedia.org/wiki/Push_technology
Right but as the article shows, there are many "push technologies"... what is this project about? Someone subscribed for notifications and then this server sends them?
I get why that's "yuck" but if I'd hedge a bet...it's probably done because it's easier to make a GET than it is a POST or PUT request and the length of a text message will never exceed the query string uri length limits. Not saying I disagree, but i don't know it changes a whole lot in this case.
If you really want to, you can in fact issue a POST with a query string and no body. It would admittedly be rather unusual.
Also, application/x-www-form-urlencoded bodies are literally identical to query strings anyway, so if you can construct a query string, you can easily construct a POST body using that Content-Type too.
Interesting project. Is this intended to replace Firebase Cloud Messaging on android or be a wrapper in front of it? I only saw android support, anything for iOS in the works?
From what I can tell it appears to be a replacement FCM/APNS. The client subscribes directly via websocket to a self-hosted server (Go binary). New messages in the queue are then notified (gotified) via the websocket. https://gotify.net/api-docs#/message/streamMessages The payload can be picked up and managed via REST API as well. I'm building a similar solution for a slightly different usecase, so wanted to have a l…
So, their conclusion in the end that it is technically impossible to build a self-hosted notification solution on iOS due to Apple's restrictions. Shame because I would love to be able to deploy something like this internally at work, but of course, half the business is walking around with iPhones. I'm kind of curious though why it doesn't ruin every single XMPP client out there - there seem to be a few on the App store.
Right but as the article shows, there are many "push technologies"... what is this project about? Someone subscribed for notifications and then this server sends them?
Useless without iOS support. What’s the point of an abstraction that has only a single implementation?
I'm not sure, but I don't think iOS lets apps auto-start and run in the background forever. This would be needed for any alternative push notification app, else it would be too easy to miss notifications.
It doesn't, but iOS will wake your app up when it receives push notifications.