Thanks!
Does that mean that the "intended" behaviour of the api is that the sort=song_hotttnesss-desc will try to provide the hottest songs?
If possible, it would be interesting to know roughly when you are planning to deploy this fix, so that i know if I should look into a work around or not.