Now RadioDroid is doing a wonderful job of supporting devices back to android 4.1, and until recently, 2.2 - that is just great, listening to internet radio is exactly the type of thing I'd dedicate one of my older devices to. Alas, those devices are stuck on non-upgradable ssl and cryptography system libraries, which means the app, and possibly other ones, too, will fail to fetch or update station data from radiobrowser, with the user not even knowing why.
I'm suggesting to do a sober risk assessment (what am I protecting, what are the worst case scenarios), weighing the invisible, but real damage that oversecurity is causing (by enforcing obsolescence of devices otherwise fit for the purpose), and hopefully , downgrading the server side security requirements to a level that is more in keeping with the intended usefulness of the service.
Now RadioDroid is doing a wonderful job of supporting devices back to android 4.1, and until recently, 2.2 - that is just great, listening to internet radio is exactly the type of thing I'd dedicate one of my older devices to. Alas, those devices are stuck on non-upgradable ssl and cryptography system libraries, which means the app, and possibly other ones, too, will fail to fetch or update station data from radiobrowser, with the user not even knowing why.
I'm suggesting to do a sober risk assessment (what am I protecting, what are the worst case scenarios), weighing the invisible, but real damage that oversecurity is causing (by enforcing obsolescence of devices otherwise fit for the purpose), and hopefully , downgrading the server side security requirements to a level that is more in keeping with the intended usefulness of the service.