Well, for real, there is still a requirement of the user's concession to show these files to the public. This related idea, though a marvellous 'tool' for sure, would be more than questionable. It should NOT be confused with some hackish "peeking button" solution you could imagine on a large vBulletin sort of forum, revealing all private sub-forums in there. This seems one of the most important things that Nir wrote. "The files in this folder will be returned as search results, but only be processed by other SoulseekQt clients ( no users of the original client ) Scarlet wanna see what ppl are hiding behind their backs. Well, it actually is, and all the lotta text that thescarletfire wrote in their initial post can be summarized in one sentence: ![]() I'm rather excited about this and will try to get something going by the end of the next weekend! ![]() These should hopefully keep everyone happy. They will clearly be marked as files that are shared privately, and the user will have the option of turning off the display of private results if they're not interested in seeing them at all. The files in this folder will be returned as search results, but only be processed by other SoulseekQt clients (as I have no desire to confuse users of the original client with files that are not readily available to them and can't be marked as such.) When received by your client, these private files will by default be displayed below publicly shared files, but in cases where something rare is only shared privately, these results should still be immediately visible. ![]() The way I envision the system is this: when you share a specific folder, you'll get the option of making the folder visible if it is shared privately. Letting them offer what they have on their own terms, while somewhat inconvenient, may open up people to a vast number of choices they haven't had before. There are people out there with incredible collections who are effectively cut off from everyone because they're sharing privately. Thank you! I most definitely agree there's potentially something big here that could really strengthen the network. Thanks man, you deserve a prize for all the work you do on this project! Forgive me if I'm rambling, I've had a wee bit of scotch this fine evening. Honestly, I would love to see SoulseekQt continue to progress in ways (like this) so that it will stand out among all other sharing communities out there (clients). I mean, worst case, it makes people talk to each other lol, no? If it was me and I was looking high and low for a certain file, and found it in a search, and had the list-only file remote error message, you bet I'd be messaging that other person :) Let the files show all in one mega-search results, (list only+open sharers) that really wouldn't be that much of a bother to those searching. That way, people could "see" the files they want during their normal searching, and when they download and see the error in the queue, it only motivates them to say hello and network - :) Thus, sharing makes the world go 'round and people's lists grow longer and longer. I truly feel that, once mapped out and if it could be implemented, it would allow a greater sense of community and encourage interaction between list-only's and the other folks. Interesting - I forgot about the 0 upload slot thingy, that's most likely the case. Just curious if there is a setting in Qt that I missed perhaps that will allow this.Īh, hmm. I hope there is a way to go back to the old way of "everyone can see everyone's shares but still have list-only downloads resulting in "file not shared" where applicable." Is this possible currently in the Qt client?Ĭan someone search for a term, see my file in their results and browse my files to see my shares, even if I'm list only? Or are they totally 100% blocked to even see my shares once I set to list-only? It helped those 'list only' sharers meet new people while still not blocking people's searches when they try to browse shares. I really enjoyed being able to see the entire shares of a user, even if they were list only, because from a networking perspective, I found it to be incredibly helpful when communicating and negotiating (for lack of better word) with said list-only user to maybe have a mutual "add me" to our lists. So back a few years when I was using the older client NS, I noticed that if someone was sharing "list only" files, when I went to browse their files, I could still at least see their files - and only when I went to try downloading from them did my queue reflect and say "file not shared" (or something like that.)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |