It makes me really upset when I see someone, who is a limewire user, uploading from me, and I cant browse their files! If they are not sharing then I dont want to let them upload.
Limewire seems to be totally random when choosing who I cant browse from. I see it with limewire 4.0.5, 4.0.7pro, 4.1.1pro, bearshare, ... the list goes on. I see no consistency, because there are users that fit in this category that I can browse from. If the reason I cant browse is due to nothing to browse, WHY doesnt limewire say this!
I deserve the right to boot out freeloaders!!!!

__________________
Sailing the sea's and eating my lime's.
Yummy Yummy.
Wheres the beer??

Do not ban people or kick users who you can't browse from most are still shareing but are not listing files all at once or are busey listing files to other users and their slots are full.

Here is me as an example: I share over 150 gigabytes, but I don't let people browse my share list for because it would flood my machine and slow my already slow internet connection (2000/128 adsl), and when I would allow viewing of my shared list some people would to download too many files despite the full slots and or try filling up the que list not letting anybody else have a chance in line to recieve files from an single user.

I must admit as a dial-up user i simply can't afford the bandwidth to allow browsing on my system. It simply seems slows down everything. And yes I offer a large no. of files. That's the sacrifice that dialup users (& probably a high % of them) hav to make. Since on dialup there is no differentiation of upld/dwld (or least certainly not offered locally.) So keep in mind to allow browsing actually uses up bandwidth (with all the continual searches, etc.) I'm purely speaking from a dialup point of view, but there's still plenty of us out there.

I'm trying to understand a problem in browsing I saw over the weekend. I tried to browse my other machine, and it worked only sometimes, even when the other machine had empty upload slots available.

Most of the time it worked properly if there were empty upload slots.

If browsing is dependent on open upload slots, then that is reasonable.

Is there a way a non-coder can see what the conditions are supposed to be that cause a LW host to reject a browse request?

cheers

Does the ability to browse someone elses d/l folder tie in anywhere with whether or not they have chat activated or not?

You guys that don't allow browsing - are you just keeping your files in a separate folder? Or, is there a way within the program itself to deny rights to anyone else to browse? I sure as heck ain't finding it if there is. Pete

__________________
Compaq Presario 7110US, 1.3GHz ThunderBird, 2GB RAM, 160GB HD, WinXP Pro w/SP3

Correct me if I'm wrong anybody, but I was under the impression the way to allow browsing was to go to the LW Monitor window & tick 'Enable Incoming Searches'. If it's not ticked then they can't browse.

This check bix is just for displaying incoming searches. It has nothing to do with whether browsing is eanbled. And in LimeWire there is no way to turn browsing a host off.

Hmm, if browsing can not be shut off, then how come that the option to look throgh another LimeWire user found on my list of people DL from my extensive library is greyed out ?

I am only able to browse 1 in 10 if that many.

On the upload side, opting to browse a user is based on whether or not chat is enabled. This will be changed/fixed in the next beta release.