When logging in to my LMS Subsonic server, the Symfonium client sends two requests in rapid succession, one with user test and one with the correct user. The server then throttles the second request with the correct login details, and the login fails.
Hum that’s strange and the error code is non standard to react to that
@itm LMS Author is present maybe he have some insight or we can discuss this
The thing is that until I know what is on the other side I do not send the credential, because Subsonic API does not support anything secure (Specially with legacy mode) and I do not want to leak them if the user made a typo.
Do you know the necessary time to wait between attemps in case ITM does not answer soon?
Since this server advertise it’s name I can add a special tempo for it but need to know how long.
The login throttler is global (shared with the embedded LMS’s UI), and really basic: it does not have a failure counter per address before starting to throttle. Looks like it would be the only option to support this server side?
I’ve been using the app since yesterday, and it does many things I’ve been looking for very well. Supporting the embedded lyrics and Replaygain tags in files, fine-grained quality settings for mobile, WiFi and downloads, AutoEQ integration and hardware decoder offloading, these are all very nice features.
Regarding Replaygain support, what exactly are the fallback settings? Is it simply falling back when one type of RG tag doesn’t exist? This type of implementation is questionable…
Well I would not use that mode either, but since many other apps propose that option I supposed it was useful to some.
But yes it’s a fallback, if one is not present use the other. I guess some users have either one of the other depending on the albums and it would work for them.
Please open a feature request for that to discuss side effects like what happen when you queue a song after starting via an album and other possible cases.