AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Soulseekqt everything queued8/27/2023 ![]() ![]() They will then receive an announcement from OrtaliGoddessOfPrivileges that they have received privileges, but they will not know who the privileges came from. Once you have the Paypal donation page up, put the other person’s username in the appropriate field. DO NOT donate through the client, or the privileges will go directly to you. ![]() If you wish to remain anonymous, you can go to the Paypal website and donate to Soulseek. You can then choose the number of days you wish to give them, and they will receive an announcement in a private message from you telling them that they have received “x” amount days of privileges from you. There will be a “gift privileges” option. Once you receive the privileges, go to your userlist and right click on the username that you wish to give privileges to. (In the Soulseek Qt client, you will only be given this option if you already have privileges). The easiest way is to donate through the client so that you receive privileges. There are two ways to go about doing this. To find out which port number your Soulseek client is listening on, go to Options->General options in the original Soulseek client, or Options->Login in SoulseekQt. Check this list of guides to see if one is available for your router brand. You can also try to manually configure your router to forward Soulseek's listening port. Although not very common, it's also possible that your Internet service provider has your connection set up in such a way that you can't accept incoming TCP connections. Both the original client and SoulseekQt use a protocol named UPnP to configure your router to recognize the listening port, but some routers (most notably Apple routers) don't support UPnP. If you're behind a router, your router might be blocking traffic to your listening port. As Soulseek attempts each peer connection in both directions, you should be able to connect to almost any other user if your listening port is accessible. Under certain fairly common circumstances, the listening port may not be accessible to the outside world. The Soulseek client sets up a listening port to accept incoming TCP connections. We both agree that 'unshare files from user' sounds better, though I admit that either one is on the awkward side.To browse a user's files, you need to be able to form a network (TCP) connection to that user, and not every two users on Soulseek can connect to each other. The 'to' would apply to the files themselves, currently being shared to the user, and that are to be unshared. The 'from' would apply to the 'unsharing', as if you're taking something away from the user. ![]() Roz and I talked about it and she made the point that either one seems correct, but that the two mean different things. 'unshare files from user' sounds better to me than 'unshare files to user'. ![]() As an example - here's a task from the pipeline that copies a small blob from a container to another container in the same storage account: Notice that it's queued for 58 seconds. I also want to have SoulseekQt memorize downloads that have been explicitly removed by the user to make sure they're not queued again when the uploading client retries them. SOULSEEKQT EVERYTHING QUEUED DOWNLOAD I have the first on my discogs wantlist, and as soon as it’s available on CD, i’ll buy it. I suppose there's no real reason not to offer a 'remove upload' feature for that scenario. While SoulseekQt has a way of differentiating between uploads that are requested by the downloader and uploads that are initiated by the uploader, the old client doesn't. My understanding is that the only situation in which your uploads can't easily be rid of by the downloader is when they're set to accept uploads from you. ![]()
0 Comments
Read More
Leave a Reply. |