Soulseek News

2004-03-05T12:52:00.000-08:00

Client version 154test1 available here, and includes a number of new handy features:

* Room-based searches: right click a room and select "search for files in room". Unlike regular searches which rely on a distributed network and so virtually never reach everyone, a room-based search is guaranteed to be received by each and every user in the room.

* Userlist searches: right click your userlist and select "search for files in userlist". Your search will be received by every user on your list that is online.

* User notes: right click any username and select "user notes" to write (or read) your own personal notes about that user. In your userlist, keep the mouse over any username to see the notes associated with it.

* Offline status marking in search results: Search results shown anywhere will now keep track of the users listed that have gone offline by marking them red.

* Sort search results by "in queue" field. Users with free upload slots will be shown first. Offline users will be shown at the very bottom.

* A new "report privileges problem" button in the check privileges window allows you to file such a report with a system administrator.

The official discussion thread for this release can be found here

Cheers, Nir

2004-02-17T16:24:00.000-08:00

Soulseek client version 153 release candidate 1 is now available here. This is what changed since the last test version:

Soulseek now generates a random listening port number when it first starts to avoid detection by ISPs.
You can manually set your listening port number.
The client prompts you to configure your router to forward the selected port when one is randomly generated.
The client alerts you when the configured listening port is already taken by another application.
Ticker performance has been optimized for the benefit of those who had performance problems with the original ticker.
Ignores now work for ticker entries as well.

If you haven't tried out any of the previous test versions, here's the rest of what's new since 152:

Can now specify "Dislike" entries as well as "Like" entries.
Global and personalized negative rankings based on people's dislikes.
A reference counting system now used for getting other users' online status. Your client doesn't bother getting the online status of users you're not downloading from/chatting with.
Scrolling room ticker allows each user to add their own text.

The official discussion for this release is here.

2004-01-13T14:17:00.000-08:00

Help test hate lists! Hate lists are basically negative recommendations. They let you list all the things that make you wish you were dead, see which things are the most hated on the system overall, and even get your own personalized list of un-recommendations! The client is available here (right-click the link and choose save if you are having problems downloading). The official discussion thread for the hatelist feature is here.

2004-01-01T21:56:00.000-08:00

The room ticker is an old feature I tried out a long time ago and now decided to bring back in a hopefully less annoying format. It's basically a running line of text on top of each chatroom that everyone can add to. The client is here. To enter your own text into the ticker, right-click the room window and select "set personal ticker". You'll be able to save your ticker text for that room or for every room you go into. Your text is taken off the ticker when you leave the room. You can also hide the ticker if you so desire. I'm gonna add a few more features to this in the coming couple of days and once I'm done with this, I'll start working on hate lists in the recommendations, then release it all as 153. The official discussion regarding the ticker feature is here.

2003-11-20T16:50:00.000-08:00

Just wanted to clarify regarding the server being up and down a lot in the last few weeks. Thanks to some excellent investigative work from arzenik, our system administrator, we've recently discovered that there are certain limitations of linux and the 32 bit architecture that gives us a lot less room for growth than we thought we had. Coupled with a signifcant rise in the usership, this forced us to start looking for drastic solutions. Those include anything from hacks to the linux kernel (again, courtesy of arzenik) to a complete revamping of the server code. As a result, things are very very shaky right now. We don't know exactly how long it will be before things stabilize, but we are doing this so that we can continue letting as many people use Soulseek as want to. I completely understand anyone who's tired of the current instabilities and opts to switch to a different file-sharing instead. I probably would too by now. If that's the choice you make, all I ask is that you make it without anger or bitterness. You're always free to check up on us later, when things might be better.

2003-11-19T18:46:00.000-08:00

Oh yeah, if you're a donating user, or if you're considering donating in the future, get the recently posted version 152 of the client here. The web window in that one automatically knows what your username is so next time you donate there's no chance of you forgetting to send us your username or alternately giving us the wrong username. You have no idea how often that happens.

2003-11-19T18:11:00.000-08:00

Every time we make things better, enough new users log in to bring the server down again. We've temporarily taken the recommendations system offline until we can figure out how to make it, or some other server component, take less memory so it doesn't crash next time we hit our daily user record (which is a little over 96k users right now).

2003-11-08T17:15:00.000-08:00

The limit has been raised to maxium 100000 simultaneous users, privileged users have priotity. Your client should now display "This server is private" if the limit has been reached.

2003-11-06T14:15:00.000-08:00

To help with server stability, the server is currently limited to maximum 70000 simultaneous users. If the server is full, your client will connect and then immediately disconnect. We are working to get this limit raised higher as soon as possible.

2003-10-21T18:04:00.000-07:00

Client version now posted to the homepage. Get it here. Includes some major improvements to the recommendations system: the abilities to get a list of users with few or more of the same recommendations on your list, getting recommendations based on just one item in your list as well as the people in the system who have it.

2003-10-18T23:10:00.000-07:00

The recommendations system seems to be working fine on the isle, so I released a client version supporting it on the main server. Get it here.

2003-10-17T21:58:00.000-07:00

The old recommendations system is back and is being tested on the old Isle! Get the client here, log in, click the "Things I Like" button and start listing everything and anything you're into, be it anything from artists to television shows to your favorite pornstar. The system will cross-reference and link between related items and once the database is big enough will be able to give you a list of items strongly related to your own as "recommendations". Have fun! and don't be surprised if the server crashes a lot, I'm there to bring it back up.

2003-10-07T16:53:00.000-07:00

A screwup in 149b came into play when the old slsk.org domain got picked up today, which is why you can't connect. Get 149c for a quick fix. Don't forget to back-up your *.cfg files!

2003-09-12T15:24:00.000-07:00

Our site is back up at www.slsknet.org for now. I'll post more details on the domain change later today. Version 149b is now posted to the new site that uses slsknet.org to locate the server. If you're using the temporary DNS fix, it's still a good idea to get it in case our IP changes for any reason.

2003-09-04T00:12:00.000-07:00

A temporary DNS fix client is available here. I recommend you backup your *.cfg files before you install this, just in case. If clicking directly on the link doesn't work, try right-clicking it and selecting "save...", that should do the trick.

2003-09-03T19:59:00.000-07:00

We currently have domain name troubles. Until we get those fixed you won't be able to connect We are working on a workaround, we will keep you updated.

2003-08-31T11:14:00.000-07:00

In order to help stabilize the server and help with some memory problems, The Isle will be unavailable for some time. Please use the main server meanwhile.

2003-07-23T12:22:00.000-07:00

A bit of update. Performance issue during peak time have been pinpointed to some precise elements. We are currently reviewing the possibilities to make things works better with some tuning already made the network driver layer.

2003-07-05T15:24:00.000-07:00

The server was unavailable this morning, it seems it went out of memory. We are investigating.

2003-07-02T15:54:00.000-07:00

The main server was restarted a couple of time today, sorry for this but Im doing some performance tweaking again. Thanks to extensive profiling, we managed to find a couple of places that can be optimized a little bit more. Feedback on the changes appreciated in the forums if any.

2003-06-24T19:24:00.000-07:00

The first version of Soulseek Isle is now available here. Here's a short Q&A to try to explain what it is we're trying to do and what you should expect:

Q: What are the differences between Soulseek Isle and the regular Soulseek client?

A: Virtually nothing, except that the Isle client logs on to the new Soulseek Isle server, which runs on separate resources from the main server, and so is expected to have considerably less users, but at the same time, it's also expected to be a lot less congested than the main server.

Q: New server? Why?

A: We've reached a roadblock. The main server already simultaneously supports more than sixty thousand users and we just can't figure out any other ways to make it take more without becoming congested. This in turn affects the server's ability to process new logins, and probably even worse, severly restricts its ability to distribute searches. Testing and profiling the server software is extremely difficult because it's very busy 24 hours a day. So the next natural choice would be to start branching out, start creating new servers. Soulseek Isle is the very first step in that direction. While it is only a tiny patch over the original Soulseek client, we're hoping it would prove useful in starting the separation process.

Q: Wasn't the new server hardware supposed to take care of this?

A: Yes. It didn't. We're not sure why but even if it had, the solution would've only been temporary.

Q: So is this going to be like Napster, where people can't find each other because every person is on a different server?

A: Only to a lesser degree. Soulseek's always aimed to group users by areas of interest. When we started out, the system revolved entirely around the subject of electronic music. Everyone was interested in more or less the same thing, and on the whole the environment felt friendlier and more accommodating. As Soulseek became more popular, much of that was gone. That's something that we're hoping to have back once we successfully branch out.

Q: You said you wanted each server to be topic-specific. What's the "Isle" supposed to be specific to?

A: Nothing at the moment. Again, this is just the very first step in our branching out process. Personally we hope it would become the server of choice for people interested in electronic music, but there's no telling how things would turn out for the Isle. Once the Isle takes in a more specific direction, we'll designate it as such. In the meanwhile we're planning on taking advantage of the smaller, more manageable Soulseek environment to develop new features to better support a multiple server environment.

Q: Didn't Soulseek use to have multiple server support?

A: Yes, and it's going to be a lot like that again pretty soon.

Q: What if I'm not interested in anything specific, but just like to get files files files?

A: You would eventually be able to switch between servers as you wish. Besides that, Soulseek's generic selection of files was never its strong side.

Q: Can I run the Isle client at the same time I'm running the regular client?

A: Yes. The Isle client uses its own folder and registry settings. That also means you'd have to reenter your information into the Isle client once you install it, as it uses its own configuration files. Or, you can copy all *.cfg files from c:\program files\soulseek to c:\program files\SoulseekIsle before running the Isle client.

Q: Isn't the Isle client just the test client with a slightly different tray icon?

A: Yes.

2003-06-18T16:05:00.000-07:00

If you can't seem to connect to the server right now, we're doing some profiling to try and find some potentially removable bottlenecks in the server software code. This should take a few hours, so please bear with us.

2003-06-15T16:47:00.000-07:00

Posted version 149 to the homepage, it includes a few minor fixes, some optimizations to search handling, and a change in the way the client handles itself in the distributed network that should help ease things up for the server if enough people use it. Expect this to become the minimum allowable version soon if no unexpected problems arise.

2003-05-12T19:59:00.000-07:00

The upgrade operation completed successfully. The SoulSeek services are now running on the new platform. Downtime lasted 40 minutes.

2003-05-11T17:59:00.000-07:00

Moving of server software to new hardware planned Monday 21:00CST (that's 2:00GMT on Tuesday for our european users). Downtime will be around 1 hour.

2003-05-11T14:04:00.000-07:00

I posted a prerelease of 148 which you can get by right clicking this link and saving. I made a lot of changes to the queue management when we were testing the new decentralized network code, and some of them are not working out. The aforementioned prerelease uses the old queue management code from 139c and earlier. It seems to be working a lot better for me (no constantly cycling uploads and a lot less failures), so I'll be making this the next standard client download very soon.

2003-05-08T14:22:00.000-07:00

The new server has been delivered today: a very nice Pentium IV 2Ghz housed in a nicely designed case with good airflow. We are now busy testing heavily the memory and motherboard to insure good stability of the system. We are satisfied with the results, we will proceed to move the Soulseek server to the new computer. We will keep you informed.

2003-05-05T23:21:00.000-07:00

Right-click this link and choose Save to download the 3rd 147 prerelease. I've done a bit of indexing to further alleviate CPU consumption for file searches. The difference should be especially noticeable if you're normally sharing a very large number of files.

2003-05-01T23:44:00.000-07:00

Second prerelease of 147 features two improvements: an optimized search engine, which worked a lot better for me with 9000+ files shared, and the infamous Soulseek.exe stub loader, so old that I can't even find the source code for it anymore, no longer bundled. slsk.exe will run by itself, and a few people on the board said they got a more stable client that way. I'm thinking it may also help with the occasional loss of configuration that sometimes happens between upgrades. Right-click this link and choose save to get it.

2003-04-25T23:38:00.000-07:00

It looks like the wishlist changes I wrote about earlier today were pretty easy to do. But just to stay on the safe side I haven't posted it as an official release just yet. If you want to try it out, right click and choose save on this link. It already bears the benefit of having all your wishlist entries processed instead of just the maximum allowed by the server (see previous post for a detailed description of how it works). Let me know if you run into any problems with it. When this gets released, it's not going to be possible to log in with older versions.

2003-04-25T13:25:00.000-07:00

Next version of the client will handle wishlist searches in a round robin fashion, as per radfaraf's recommendation. Here's how it's going to work: the server will inform each client how long to wait between wishlist searches (the starting value is going to be somewhere between 2-4 minutes, which means 30-15 searches per hour, respectively). Your client will cycle over your wishlist, sending one search at a time, which would also help avoid congestion if your wishlist is particularly big. If you happen to have three entries on your wishlist and the server is configured to process one wishlist search every two minutes, each of your searches will be sent about 10 times an hour. If your wishlist has 60 entries, it would take a full two hours to process all of it once. That means all users who have any entries on their wishlist would create equal stress on the server, which may also mean we would have to stretch the wait period between searches further if the load is too high. It should take me a few days to implement these changes and release a new client. When I do, I might take the opportunity to make it the minimum allowable version, to make sure everyone logged on has the fix for that awful queue upload bug from 146c.

2003-04-23T15:52:00.000-07:00

System is too unstable with new motherboard. Since the chipset used is different, we tried to upgrade the kernel to a more recent release to no avail, still crashing at random for no apparent reason. Until we can figure what is the exact cause of all this mess, we are downgrading the server again to the old motherboard in the coming hours. Update: Downgrade completed! Server is up and running.

2003-04-22T16:54:00.000-07:00

I wanted to post an email I just got along with my response. I left the person's name out as I don't know if they want it mentioned:

> Nir Would you people get your stuff together.upgrade
> your sys and leave it the hell alone.alot of people are
> getting pissed off,every 2 min it seems as your server
> goes down.we are getting pissed and ready to go
> elsewhere.....get it together......i ask please

you know what, things are difficult enough as they are right now without people like you writing in emails to complain about the situation. we did upgrade, but the machine doesn't seem to be holding up very well, so we're doing everything we can to fix the problem. frankly, if all the people who were unhappy with soulseek right now and couldn't afford to wait actually left instead of whine, we probably wouldn't need this upgrade.

2003-04-22T11:41:00.000-07:00

System is unstable for now, you might have trouble to connect. We are investigating the issue.

2003-04-22T04:05:00.000-07:00

The server has finally been upgraded with a new CPU and the new motherboard recognize all the available memory. That's the good news. Unfortunately, after the upgrade completed more or less painlessly, the cabinet where the Soulseek server is hosted suffered some power breakdown. It is not completely clear yet if the problems are over for good or not. That's the bad news. The server is up'n'running for now, cross your fingers and stay tuned for more news.

2003-04-19T16:53:00.000-07:00

I didn't really know how important the wishlist feature was to users until I read the thread on the messageboard, since I myself have had a grand total of two entries on my wishlist in the last year. Here's what I'm doing now instead: I increased the maximum number of entries on the wishlist from 5 to 40. So far the server seems to be handling that fine, but if things start slowing down, I'm gonna turn search skipping on for wishlist entries, which would mean a certain percentage of all users, roughly 25%, will receive each wishlist entry (randomly picked users each time) instead of everyone. The CPU upgrade we tried a couple of weeks ago didn't go well, only half the memory was recognized, so we had to roll back. I talked to CIFNet and they're about to get suitable memory, so I hope we'll be able to move to that P4 soon.

2003-04-18T14:51:00.000-07:00

Starting today, the server will only accept up to five wishlist entries from each person. Some of you have been overusing the feature to the point where the server would repeatedly choke, disconnect users, throw away packets, etc etc. Alexbk, python soulseek's developer, offered the idea that we separate regular searches from wishlist searches in such a way that regular searches would be distributed to everyone, while only a certain percentage would receive each wishlist search. That gave us all the breathing room we needed but was also penalizing users who were using the wishlist to find two or three things they were badly looking for at the expense of those who took to individually input each track name of every album they were looking for to their wishlists.

2003-04-17T16:52:00.000-07:00

Posted 146c to the website. It fixes the much reported problem of new uploads not getting started if there are downloads coming from the same user. Also fixed a minor bug to slightly reduce bandwidth consumption on file transfer negotiation.

2003-04-17T02:30:00.000-07:00

Soulseek is broken. Please come back tomorrow.

2003-04-14T10:53:00.000-07:00

If you've suspected the announcement made on the old server about the availability of client v. 145 brought the server to its knees in a mad rush of downloads, you were right on the money. I temporarily shut the old server down to help the HTTP daemon out, but the whole system is running without a single CPU cycle to spare, so it's gonna be hairy for a short while. If you can't log on or download the new client, you should probably give up and come back in a few hours. Things should be much better then.

2003-04-13T22:17:00.000-07:00

The main server's been maxing the CPU out for a few days and there's a really good chance the distributed network changes in the test version will help with that, so I repackaged test 11 and posted it to the homepage as client version 145. This will log on to what was formerly the test server, but if for any reason you decide you want to go back to the old client and server after you've upgraded, I also kept a link to 139c on the download page. Just make sure to let the installer overwrite the newer files when it asks.

2003-04-12T22:59:00.000-07:00

A very important fix in (test 11), at the usual place, patches a problem that allows a user to crash a whole lotta clients by sending a malformed search request. Unfortunately, that doesn't mean there isn't another such bug in test 11, but your odds are probably much better with this one.

2003-04-11T17:56:00.000-07:00

A 9th test version posted to www.slsk.org (top of the page, you know where it is). This includes a bunch of small fixes, as well as the ability to see what search terms your client is routing. Also, the get DNet option now doesn't show users' IP addresses, so there's a very good likelihood this will become the minimum allowable version very soon.

2003-04-11T02:24:00.000-07:00

Third and last test version for the day, (test 8) just posted to www.slsk.org. Yet another little big fix to allow users behind a router to act as parents on the decentralized network.

2003-04-10T18:45:00.000-07:00

Second test version in an hour! As usual, the link is at the top of the soulseek homepage . Thanks to Mincer and radfaraf for helping the server see the error of its ways in automatically deducing users behind a router can't accept connections.

2003-04-10T16:46:00.000-07:00

If you've tried connecting to the test server and got a message saying your client is obsolete, you'd need to download (test 6) off of www.slsk.org (link at the top of the page). Sorry for the inconveniece... every once in a while it becomes impractical to keep testing because too many people are using an old test version and I can't tell if things that don't work actually still need to be fixed or if too many people don't have the fix :)

2003-04-10T12:42:00.000-07:00

Sixth test version posted , this one includes some important configuration tweaks to the decentralized network code.

2003-04-07T09:25:00.000-07:00

I need to ask everyone to be patient regarding their privileges activation; with all of the new client/server changes, things on that front have gotten a little bogged down. Not to worry, though, they will all be done very soon!

2003-04-07T05:06:00.000-07:00

Thanks to alexbk, python soulseek developer extraordinaire, for spotting a little big problem with the way clients kill their connections to their parent every five minutes. The fixed test version is here.

2003-04-06T16:31:00.000-07:00

Contributing further evidence that I'm an idiot, and despite Roz's repeated attempts to point my attention to the fact that the test server wasn't accepting any new connections, I just found out that the connections limit was set by default to 1024, and indeed, was met for a good number of hours. Apologies to those of you who tried to connect with the test client and couldn't. The problem should now be fixed.

2003-04-05T21:35:00.000-08:00

Third test version here. Fixes a problem where the client doesn't inform the server of its parenting capability after it reconnects. I bet you're sorry you asked now, huh?

2003-04-05T04:58:00.000-08:00

I screwed up with the test client. It reuses the release client's configuration and so changing stuff in the test client (like removing queue entries) will affect the release client. My sincerest apologies to the few of you I explicitly informed otherwise and to anyone else whom this incovenienced in any way. A fixed installer is at the same place.

2003-04-04T21:49:00.000-08:00

I've posted the first test version of 140, with the decentralized network changes I mentioned yesterday. We would need a decent number of people on the server to be able to see how well the system works, and it's very doubtful the first test version is going to be the last one. If you're interested in helping out, please download the test installer here. It won't overwrite any of your existing soulseek installation, and you can safely run it side by side with the release client. If you have any questions or problems, I'm gonna be on AIM practically constantly during the test period under the handle of soulseektest. Feel free to contact me for any purpose. Thanks.

2003-04-02T23:35:00.000-08:00

Getting the server working okay after the upgrade isn't going as smoothly as we expected. We're looking into it, will keep posting as the situation changes.

2003-04-02T23:23:00.000-08:00

Oh, and a heads up to the more technically minded among you, I just finished implementing a series of changes to the system's decentralized network model. The point of which is to better involve the server in the construction and management of the decentralized network. More specifically, nodes would no longer advertise themselves to the rest of the network when they're capable of taking on children, instead, the server keeps tabs on which client can support how many children and communicates that info to clients in need on a regular basis. This is the first step in making the decentralized network more intelligently constructed and managed using the server. The bottom line is that clients spend considerably less bandwidth on routing messages, and as I keep making the server's network management function smarter, we might also have faster, wider searches. I'm doing some basic testing on the aforementioned changes, after which I'll release a test client for those of you willing to help out.

2003-04-02T23:11:00.000-08:00

Our server just came back online after the cpu was upgraded to a 2.0ghz pentium 4. Hopefully this means we'll be able to distribute searches much more widely than before, in which case searches should start returning more results than usual.

2003-03-23T16:04:00.000-08:00

Yet another website redesign -- there were several unusual problems since we started using frames. So I redid what I could with tables.

2003-03-18T22:14:00.000-08:00

Instead of waiting until there's a whole bunch of stuff collected that I want to work on, I decided that I'm just gonna do whatever I feel like with the client, as small as that may be and release small maintenance updates to give you people the opportunity to try them out and maybe even tell me if they work any better (or any worse) for you. The first one is here (right click the link and choose save as...), and here's what's changed:

There was a huge memory leak that would keep going whenever the client gets disconnected. This is especially noticeable when the client stays disconnected for long periods of time of an hour or more, where the client could take hundreds of megabytes of memory. This should now be fixed.
Place in line is now not mentioned in the upload pane. Some users are using this information to systematically ban privileged users, so I've taken it off. For other people this information isn't really that useful.
Clients begin with a minimum child capacity in the distributed network of 1 instead of 0. That should help make the distributed network more efficient.

2003-03-18T00:31:00.000-08:00

Sorry for the recent server crashes and outages. I've been trying to get the server not to do search skipping for privileged users, and something seems to trip every hour or so. I'm working on it.

2003-03-13T18:45:00.000-08:00

Soulseek services were unavailable for the past 14 hours. Root cause was a filesystem corruption on the server. We tried all kind of weird black magic to bring it back. We finally managed to restore the corrupted journal and voila, server is back.

2003-03-05T03:10:00.000-08:00

A lot of users have been complaining that they couldn't get the new paypal button to work since we added the username field. I'm not sure if it was the way it was made to look nicer in belgo's redesign or if the extra field screws something up, but for now it's gone. I'd appreciate if anyone who's had a problem using it previously could tell me if it works any better for them now. Thanks.

2003-02-26T01:55:00.000-08:00

After two nonfat lattes and roz giving up on Metroid Fusion on the GBA SP in the course of a four hour sit at a starbucks I finally got to finish the search skip code I wanted to work on for so long. You've probably noticed that it hasn't always been easy to get on the server in the last few weeks. Arzenik looked at the server box logs today and figured out that the server was turning down connections by the pound because it was running out of processing time. Interestingly enough, we haven't even tickled our bandwidth limit as of yet. Most of this processing time was taken to distribute the many many search requests that go through the server. Here are the specifics: At any given time there are about 350-500 clients connected to the server as decentralized nodes. Whenever the server gets a search request, it hands it over to those 350-500 clients who in turn distribute it to the clients connected to them, and so on until *most* of the clients in the system receive the search request. In the olden days all the clients would receive each search request directly from the server. That became impractical as the system went from hosting dozens of users to hundreds and thousands. The decentralized network solution let us keep growing without worrying about bandwidth and processing power as much. Well, at least until I can get Basil at CIFNet to issue us a CPU upgrade, we've hit that limit again. This is where the search skip thingie comes in, and it's very simple: I can tell the server what the maximum number of distributions per search request is. Right now it's set at a hundred, so even if there are four hundred nodes connected directly to the server, only a hundred get the search request at a time. Each succeeding search request goes to the next hundred nodes. If that sounds as though this seriously limits the number of results you get back, well, it does. But we had to cut back on the distribution range eventually. Even at its prime a Napster server only handled about 8,000 connections. We've hit 50,000. We're seriously considering setting it up so that privileged users don't suffer from search skipping, which should be very easy to implement.

2003-02-24T04:47:00.000-08:00

belgo took what we tried to do with our website redesign and made it not look like crap. Thank you belgo!

2003-02-22T12:08:00.000-08:00

Services were unavailable today 22 february from 19h10 GMT to 19h45 GMT due to a Denial-of-Service attack aimed at the network where our server is co-located. Filtering has been applied by the uplink providers to restore connectivity.

2003-02-21T16:20:00.000-08:00

So if this isn't your first time at the Soulseek website, you've probably noticed we did a bit of redesign. We're hoping the extra username field over the donation button will result in a lot less angry emails from users who don't understand why their privileges weren't activated yet. Then of course there's this Blog, which we'll be using to post Soulseek related news and thoughts.