Fun with Filters

Tonight's build is all about extending the existing filtering mechanism to address a few of the longest-standing, most popular requests for SoulseekQt. Primarily that for bitrate filtering, but with a little extra, and built on a base that can be further extended to add new forms of filtering. You can skip all this and just head to the download page, as the filter box present on search result and browsed share pages now has a 'Filter Help' button next to it that will provide you with a more concise version of what I'm going to be saying here about the new filters.

Nightly Build 11/5/2011

  • Search and Share Browse filters now accept exclusion tokens preceded by a dash (-).
  • P2P communication between two clients of this version or higher will be obfuscated in an attempt to avoid detection by ISPs that are crippling Soulseek peer connections. Completely unproven at this point.
  • Client window is now shown before shares are re-scanned so as not to appear that the client hasn't started when scanning large shares.
  • Client will now dump peer messages of improbable lengths, probably avoiding a crash.

Is your ISP crippling Soulseek transfers? You can help us test Soulseek protocol obfuscation.

There have been way more reports than usual in the last few months about Soulseek transfers being unusually slow for different users, from different places on earth at different times of day. We suspect many Internet service providers have taken to slowing down peer Soulseek connections, and have set out to try and do something about it. Since it's not clear what each ISP is doing in each case, we had to resort to a lot of guesswork. Our starting theory is that in many of these cases, protocol analysis is done by the ISP to identify peer Soulseek connections.

Tags: 

Nightly Build 10/18/2011

  • UPnP initialization was moved to a secondary thread to speed up startup time.
  • Client no longer crashes if sharing one or more files larger than 2GB when a peer requests shared file list. (Thanks to CNoise for his tireless work in helping hunt this one down!)
  • Client now asks for username and password if run for the first time.
  • Open File menu option for complete downloads, also works via double-click.
  • Open Folder menu option for downloads.
  • Login failure is now always reported, not just when providing an invalid password.

Regarding the client crashing

I've received a couple of reports about the client crashing in the last few weeks. It's been months since I've had a crash myself, but I'm also not a super-heavy user either. If your client is crashing, the best thing you can do to help me root out these crash-causing bugs is to generate and post a crash report. This is a very simple process on Mac, but a little more involved on Windows.

On Windows:

Multiple upload slots; A few extras

The main addition in tonight's build, as foreshadowed by the announcement title, is the ability to set the maximum number of active uploads past the heretofore limited number of just one. This started off looking like a relatively simple change, but ended up complicating things quite a lot, especially but not exclusively when it came to maintaining a maximum upload speed for several simultaneous uploads. I haven't been able to generate a very heavy upload stream on my end, so the whole thing is only moderately tested.

Nightly Build 9/21/2011

In no particular order:

Nightly Build 9/13/2011

Not enough for a full-blown announcement, too much for a one-line description on the download page. It was 9/13 when I started, I swear.

Wish list, Unicode chat/bugfix

Not much to tonight's build. The wish list feature has been a long time a-coming, and so here it is. There was nothing stopping me from throwing together a quick hack to make wish list searches work on top of regular searches (or so I thought), but I wanted to provide a little something extra, as I try to do with all original client features I have to re-implement. Just getting the basics to work turned out to be more complicated than I had expected.

The Unsharing

The subject of banning is one that I've been reluctant to tackle in SoulseekQt since the very beginning. There are few topics in the history of Soulseek that have been as much the subject of strife and ill-will. Horror story after horror story, it seemed as if for almost every case of it being used to prevent download abuse, someone out there has been banning for all the wrong reasons. Because they didn't like what the other person was sharing, or often for no apparent reason whatsoever, and refusing to answer any questions; a situation I've been in myself in the past.

Pages

Subscribe to Soulseek RSS