I noticed all of my shared content in another Soulseek account is not showing up in any of my other accounts' search queries. This also affects wishlist searches. The content is still visible when the account is browsed.
The Soulseek server removing all your shared content from the search results is going to have a major chilling effect on content found via searches and wishlists.
I run 4 accounts/instances on other physical and VM PCs (each has a different IP and forwarded ports via VPN). One uses Nicotine+ and 3 are Soulseek QT (I don't think it matters).
I first rebooted the box and changed to a different VPN server. I blew through several new accounts and determined one of my live music folders with about 3000 shows is triggering the shadowban. The artist from Canada is not in any of my shares. This appears to be a new thing implemented recently. I don't babysit any of the instances. I just noticed it today while testing if some content from an unknown artist was searchable in other accounts.
They are also shadowbanning your new account(s) via IP. Thus not only do you have to create a new account, right after logging out from your old account, you MUST change your IP before logging in to the new account. VPN usage will become mandatory. Read the next paragraph and you'll see this is moot.
Looking at the big picture, without knowing what content is generating the ban, this is going to keep folks from sharing folders of random content. We *could* have a community list of banned content (a blacklist), but anyone could add a list of all known content which messes up the list. Any implementation of this would need some sort of revision control system so that changes could be reverted. And that may break if non-banned content is slowly added to this blacklist over time.
I can't see a workable solution that keeps searches and wishlists functioning as is and keeps the Soulseek we know. Unless... we get rid of Soulseek! Each user shares their list of shares to all other users. Transferring the list of files from thousands of users to each Nicotine+ user and having RAM to store all this is a severe issue, but maybe doable with 7z compression, broadband internet, and metadata compression in RAM.
A big upside to this is decentralization. A new system like this could use multiple connections for transfers! Imagine the speeds! No more queuing. Smart folks put on your best thinking hats! Remember how one of the early peer-to-peer apps worked? You needed to have the IP of at least one user to bootstrap you into the system (someone name the app; it's been so long). Some folks shared their IP in a forum, IRC, or ICQ to bootstrap new users.
The Soulseek server may have massive amounts of RAM with a custom database implementation not using virtual memory (I'd use Delphi TLists for this as it's crazy fast). Each user would essentially need the amount of RAM the Soulseek server has. I retired years ago and I'm out of the loop with what programming solutions are available today. Is compression of content metadata in RAM widely used yet? Trading CPU power for RAM requirements. Maybe I'm overthinking this...