I daresay the best way to keep the community friendly is not removing support for millions of devices with a mandatory, scare-mongering update, but what do I know! My posts are a drop in the bucket compared to that move...
But hey, it only took a week and a dozen days after the hack was publicized to get even the slightest clarification on what happened. If Spotify is operating from a geosyncronous space station moving so fast they experience time different than us, great job. Otherwise, what the heck took so long?
Let me try to parse your reply (which does, in fact, contain words, but not necessarily clarification) in an effort to understand it a bit better:
"Due to the extra safety steps we needed to take to ensure the security of our Android app users, we needed to perform an upgrade. This seems to have caused some issues for users on Android armv5 and armv6 devices."
Well, I'm glad Baghdad Bob appears to have found work! By "caused some issues," you do mean "unilaterally removed support for," correct?
"My understanding up to this point is that these versions may have been impacted prior to this update. However, in the spirit of giving as positive an experience as possible for armv5 and armv6, we took extra steps to ensure these users remained on a version of Spotify that supported these versions. Yet all that changed when circumstances forced us to perform an upgrade."
I don't get what you mean with that first sentence. They were impacted prior to this update? I see no evidence of people complaining prior to the forced upgrade, so this is unclear. Could you clarify what extra steps were taken to ensure support? I really don't understand what any of that means (your use of "versions" to describe platforms and software is also confusing, if that is indeed what you're doing).
"We're sorry for the less than ideal experience this causes for those of you on armv5 and armv6 devices. We'll be posting a more in depth update in the coming days to explain the issue further, as armv7 users should not be affected. We hope you'll understand why we needed to take these steps."
Again, by less than ideal, you mean unilaterally removed support by forcing a mandatory upgrade, correct? I hope I'll understand why you needed to take these steps, too, some day.
In addition to the above, here's the remaining questions I expect Spotify to answer with the update in "the coming days" (which, for the record, can be defined as any day before the sun explodes and destroys the universe, so well done on that wording):
- When did this hack occur? Was the single user who was hacked actually responsible for the hacking, or a victim? If that user is not responsible, have you identified who was?
- How did this hack occur? Was it Heartbleed related? Did Spotify developers follow best practices, or was it their coding error that allowed it? Why should we feel safe now?
- Did the hack have anything to do with DRM/people figuring out how to convert Spotify music files to mp3s, or some similar scheme?
- Why did we have to redownload music? Why didn't the app replacement delete the old songs? Why are there problems with 4.4.2 users unable to save to SD, and when will that be fixed?
- Why didn't you warn arm5/6 users of the "less than ideal" situation you were forcing them into? Was the hack exploit specifically related to this type of hardware? If not, why was this mandatory update the time you deciced to pull support? Why not allow a legacy apk for people to use?
- Why hasn't the Spotify FAQ been updated yet to reflect the devices you don't support? How many weeks does that process take?
- Why did you add new app permissions (again, in a mandatory, scare-mongering, forced update), including the ability to read phone IDs? I expect a full explanation of all of the permissions added.
- Will Spotify warn users of arm7 devices when they plan to cut off support, or will it happen randomly in a forced update?
- Have any steps been taken to improve Spotify communication between developers and customer support, which has been an ongoing issue since...well, the dawn of time?
- Do you ever plan to acknowledge that Chromecast support is being ignored because of Spotify Connect? (Just kidding, I know you guys will continue to ignore that no matter how many people quit in disgust/kudos the idea)
I think that about wraps it up. If you can manage to actually answer those questions, without using mealy mouthed PR babble about "less than ideal" circumstances, I'll be impressed. I will admit, my confidence this will actually be done is very low.
I'm getting a strong MySpace vibe from Spotify of late. You zoomed to the top, but if you continue to treat customers in the manner you have, I assure you that they will turn on you. Do you want the image below to become a meme? Then do what's right and answer the questions above.

https://community.spotify.com/t5/Spotify-Ideas/Add-support-for-Google-ChromeCast/idi-p/482900