|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
New Feature Requests Your idea for a cool new feature. Or, a LimeWire annoyance that has to get changed. |
| LinkBack | Thread Tools | Display Modes |
| |||
PLEASE- GET MORE PROGRAM's: E.X. ILLEGAL ACTIVITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Edited to comply with the House Rules. Warez, copyright violation, or any other illegal activity may NOT be linked or expressed in any form. Last edited by murasame; March 16th, 2005 at 12:14 PM. |
| |||
Enable resume/find sources button with "Try Again" caption for files with the status es Complete and File Corrupt. In the latter case you want to reattempt getting it, preferably while the source is still online, and should not need to explicitly search for it. In the former case, the file might prove on examination to have been substituted with an ad or other junk, or otherwise damaged without the damage being detected resulting in File Corrupt status. In that case you want it to delete the file and attempt to get it again, but you might want to block the host that sent the bogus/substitute file so you have greater odds of getting the real McCoy next attempt. (There's some files I've been trying to get for ages that turn up frequently in search results but never seem to download right -- one I've gotten six or seven times and it's never shown a status of File Corrupt, but it's also been broken beyond use in every single instance!) This brings me to another matter: finer grained detection of corruption. Really, each time a chunk of file arrives and the progress meter notches forward a bit, it should be possible to check that one chunk against some check bits tacked onto the end and rerequest just the one chunk if it's damaged. This will reduce accidental file corruption to nearly nil without having to reget entire files, only pieces. That leaves intentional corruption by hostile nodes that join the mesh for a file and send garbage or advertisements, corrupting and vandalizing the file. This is simple -- all files participating in a mesh need to have the same exact file, with the same SHA1. When downloading from a newly-discovered source begins, Limewire can request a random chunk of the file that it already has and compare it with the version it already has of that chunk. If the new chunk doesn't match and does have proper check bits, it's probably a hostile node trying to pollute the download, and should be dropped rather than downloaded from. Your node also won't refer other nodes to the hostile node. If it matches, it then requests chunks it does not have from that source in order to download part of the file from it. Downside is, if the first source to send any chunk of a file was hostile, it will download from only the bad actors! But at least the mesh for a file with bad nodes in it will get divided into two disjoint chunks, one sharing a bogus file and one the real file, and if you got the right one to begin with you will get the entire correct file and not a partially corrupt file. This could also use Bitzi-like reputation management features, in which not only whole files but just chunks have reputations. The version of a chunk with majority representation in the mesh might rule; or volunteers can preview chunks (for some formats this should be possible) and vote them up/down. |
| |||
multiple playlists It would be nice if you could have multiple playlists in the library like in kazaa, so if more than one person uses it, you don't have to sift through a massive list to find your favourite songs. Thanks. |
| |||
User definable connection speed due to the fact that the given choices do not include anything that resembles my connection. I am on 3mb Down and 364Kbs up if I select any of the given choices I either end up seriously restricting my download speed from what it is capable of or choking my connection as to get decent down load the lowest I can possibly put the upload slider is still higher that the max my connection will allow. yes I know there are unlimited settings but I like to hold back a certain amount of bandwidth so I can still surf and do other things on the net. And since I share 35Gig+ of files in limewire and always leave it running yes this becomes a problem as there are always people getting stuff from me |
| |||
Just a little tiny and probably amazingly easy feature request... this would cut down on the number of crap results of a search: On start up generate a random 32 byte string (like MD5 encode the thread ID and systime or something). Do a search for it in the background. Automatically blacklist the IPs of anything that returns a result to that search. While running, preodically do this search again, and add any results to that blacklist. Optionally, also give the user the ability to add obviously BS results to this blacklist, and possibly even allow this blacklist to be auto-shared, so you can choose another user and import their blacklist if you want. I'm hoping these features are significantly easier than what I really want, which are features that get you a beer whether there's any left or not, and make the cat not decide to take a really stinky crap every time you have a girl over. B^) |
| |||
Hell, yeah! Quote:
|
| |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
*feature requests | hugacloud | Shareaza (Windows) | 7 | July 8th, 2002 10:37 PM |
A couple more feature requests | Unregistered | New Feature Requests | 0 | May 10th, 2002 12:58 PM |
Phex feature requests | Unregistered | General Discussion | 5 | March 23rd, 2002 10:33 PM |
2 feature requests | dorksport@wp0.cjb.net | New Feature Requests | 0 | September 7th, 2001 07:14 PM |