Close button sends client to the tray, statically linked Qt for OSX.
See the Changelog for list of features and fixes currently only available in the nightly builds.
One of the most oft requested features over the years, and one I've always resisted strongly is that of automatically banning users who aren't visibly sharing anything from one's download queue. I have no desire to repeat the many fine points that have been raised time and time again on either side of the argument in a multitude of discussions here and on our original forum. Suffice it to say that I understand that Soulseek relies on openness, on the willingness of its users to share the things that they love with those around them. Many don't see it as a matter of strict give-and-take, and are happy to share what they have with all and sundry. Others are justifiably angered that some of those who are benefiting from their kindness aren't in turn doing their part to support this system of exchange, and who could blame them. Still, outright banning has always struck me as too harsh a measure in this case. As I've said many times before, there are many different reasons someone who is downloading from you doesn't appear to be sharing anything. And though they all vary in degrees of offense, they all share one basic trait: outright banning isn't going to do anything to better the overall situation. Perhaps someone is sharing privately and hasn't gotten around to adding you to their list yet. Or more likely, someone hasn't been on the system long enough that it had occurred to them they really should share if they intend to download from others. Whatever the case may be, there seems to be no scenario where simply saying something to the user isn't the better alternative. And for that purpose I've implemented an automatic empty share warning mechanism in tonight's build. Set your desired message under Options->General, check the 'Send warning message to downloading users with empty shares' option, and your client will attempt to browse every downloading user in the background, and send them your message each time it comes up empty. You can keep track of which users have had the message sent to them under the Diagnostics->Logs->Shared tab.
Additional fixes and changes:
Links are on the download page.