UnifiedPush was a mistake

[technopagan]

I'm sorry to say this, bu I've just deleted FOSS-Warn in frustration.

The move to Unified-Push was a mistake. It required almost everyone to set up something like nfty or similar, deal with lots of server-settings that were beyond common knowledge AND it turns out to be less reliable due to battery-savings issues on devices. But the job of an alerting-app is to be reliable.

My personal nail in the coffin now was that I've noticed for a while that I was NOT receiving alerts from FOSS-Warn and I've managed to narrow it down to the KDE FSAM(?!) server rejecting my area request. I've tried over a dozen different times over days, but the flow in the app is just 100% broken: you search for a location (town etc) by name, you tap the result, the map shows the area with an overlay of the area you are supposed to receive alerts for, you can adjust the area with the slider (or leave it like it is by default), you hit the button to subscribe and everything is peachy. But ONE app restart later and the KDE server rejects the request with an "Invalid area range" error. Like I said, I've tried A LOT of different things to try and get around this error, but I can't and now I am rage-quitting. So much wasted time and energy for an app that was supposed to be helpful - and IT HAD BEEN until UnifiedPush. :(

[nucleus-ffm]

Thank you for your comment. It's true that UnifiedPush is more complex and unreliable than I originally thought. Unreliable server such as KDE's ntfy server under unifiedpush.kde.org did not help in increasing the acceptance of UnifiedPush. I tried to compensate for that with a new self-check and a warning when using ntfy.sh or unifiedpush.kde.org. Also, I tried to have extensive documentation in the wiki on how to set that up.

If you have a concrete error that you believe is a bug, please open an issue with more details. I'm not sure what you mean by "invalid area range" error. If you want to help make FOSSWarn more stable and robust, open an issue and include instructions for reproducing the error. Without that, I'm not able to fix the error or help you otherwise.

Also note that I implemented a choice for the alerting service in version 1.1.0 alpha 1. This allows you to use the legacy polling instead of push notifications. This still needs extensive testing until it is ready for the final release, but maybe you want to give it another chance at some point.