upload supervisor capability (Limewire 4.0.8 pro)
 

Does anybody know how to only allow hosts who share files to have access to your files? I do not want non participating freeloaders to have access to what I have bought.

I don't mind sharing with those who are also supporting the cause.

You can try the freeloader settings in the preferences (tools/options), but that code may be disabled.

btw--some people act as ultrapeers and may share very few files, but are helping out by sharing gigabits of bandwidth to keep the network going. I wouldn't want to hurt those folks :)

You can do it by going to your preferences.

Ivan
In the dark we make a brighter light

I set 100 files / rarely but continue to get freeloaders/nonbrowser hosts. I did apply.

There's lots of users out there that you can't browse. It doesn't mean they're freeloaders. eg: I rarely allow people to browse me (despite sharing over 1k files) b/c I'm on a dial-up connection. If I allow browsing it affects my connection (continual search info coming in & going out.)

I have spent thousands of dollars and 20 years to build my library. I enjoy sharing my musical soul with others and I look to other peoples songs to broaden my view. Not to participate is to slite the sharer an opportunity to grow. If all you are doing is sharing a download file or the CD of the artist, you are freeloading the sharing community.

That said, setting preferences to not allow freeloaders does not work. Any other ideas folks? I am now killing non-browsing uploads while I am on line and disconnecting when done.

I would think a software program that promotes sharing would allow the sharer some protection.

nice articulation of filesharing--thanks.

As for the settings, There are a few coders around who would know how to test an uploader for browsability and only allow those folks to upload.

I'll ask around. Are you on a Mac or PC?

For what it's worth - Dial-up users
 

LOTR--"Enable" incoming searches should really say "show" incoming searches"

Like all the other graphical displays, the data is still flowing (whether we look at it or not).

Dial up is a great way to learn how to conserve resources though. Perhaps unchecking the enable button freed up some resources. . . . or maybe it just triggered a "watched pot never boils" response.

Anyway, broadband sure is addictive :p

I'm a little lost here. If not enabling the incoming searches checkbox doesn't control the ability of people to browse your files then how is it controlled & why is it that we can browse some but not all people's shared files?

Also, doesn't the Files must share not to be a freeloader option work? Ok the freeloader 'always/rarely' slide doesn't work, as far as I can understand here. If the minimum no. of files 'does' work then that is in effect a freeloader control. When I increased this no. over a period, I noticed a great many less people were attempting to dwnld my files. Instead of having a dozen queueing up for eg, it dropped back significantly (just 2-3.) I'd like to know about what the situation is with Connection Preferencing.

"Browse Host" and connection preference settings are in flux. I've been trying to figure out what the situation is on and off for several months.

For example:

-When running 2 LW's on the LAN, sometimes I can browse one but not the other. Too, the same machine is sometimes browsable from the Monitor page, was once browsable from the connections page, sometimes from downloads and sometimes from the search results. Sometimes not. I can't figure out the conditions that determine when the other host on a controlled LAN is browseable.
:confused:

-too, attempting to browse an outside host will sometimes partially load results (I can start downloading a file from it), then suddenly the search results pane will quit and the tab will close.

Huh?

So, I figure the code is in flux, probably has some bugs, and is awaiting attention. I suspect the freeloader settings are just as unreliable.

Sorry I can't be more precise, but until the browse code is reliable, permanent blocking of unbrowsable hosts looks to be premature.

Short answer: I've set up everything I can to allow browsing, but sometimes one of my LW's will think the other is unbrowseable. That's not fair, so don't block me :p

Just tonight I browsed somebody's files & it reached 3.5 k of files (about 3/4 way thru) & then cancelled itself saying it could not browse host.

This area obviously needs more work by the programmers. (probably not a high priority for them.) Highly underestimated as to its importance by them if that's the case!!! Too many peoople pay a lot of attention to this detail!!! Java also potentially holding out some perfection of art.