Yes. Idle check + NOOP were orignially implemented to FTP protocol as method for a server to determinate wheter connection is stalled. NOOP stands for No Operation - and as one might guess, it uses very little server resources when executed. Nowdays clients are using commands such as LIST for 'noopping', which consumes enormous amount of server resources for NOTHING - and goal is what?
Servers that want users to be able to idle longer, may set their idle timeout accordingly. It's not up to client to decide, for how long they are allowed to be connected. My suggestion is: remove all but NOOP command from that list - as it's not a feature, but protocol violation
