UnifiedPush was a mistake #282
technopagan
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
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. :(
Beta Was this translation helpful? Give feedback.
All reactions