Posted February 26, 2006 1. transferring files via UDP protocol (if it isn't done already) 2. "hidden shares": don't show specified files in the user's filelist, but answer to the corresponding search request that the file is present and allow to download it - semihidden files (not present in filelist, but present in the answer to search request) - fully hidden files (not present ever in the answer to search request) - for specified hubs/users only Maybe this should be specified on per-hub basis or ever per-user basis? 3. links to the directories 4. disconnecting peer with share size less then X by the client (wery desired) 5. maybe mirroring functionality 6. PeerGuardian in the box 7. filelist sharing (download user's filelist from enother user on the hub) 8. must use saved filelists preforming the search 9. client-client enscryption (not only client-server) Sorry if I've posted any duplicate features. Share this post Link to post Share on other sites
Posted February 26, 2006 1. transferring files via UDP protocol (if it isn't done already) 2. "hidden shares": don't show specified files in the user's filelist, but answer to the corresponding search request that the file is present and allow to download it - semihidden files (not present in filelist, but present in the answer to search request) - fully hidden files (not present ever in the answer to search request) - for specified hubs/users only Maybe this should be specified on per-hub basis or ever per-user basis? 3. links to the directories 4. disconnecting peer with file size less then X by the client (wery desired) 5. maybe mirroring functionality 6. PeerGuardian in the box 7. filelist sharing (download user's filelist from enother user on the hub) 8. must use saved filelists preforming the search 9. client-client enscryption (not only client-server) Sorry if I've posted any duplicate features. numbers 2,5,6,7,8 are certainly no, and 9 is not likely, oh and i don't understand request 4 Share this post Link to post Share on other sites
Posted February 26, 2006 Request 4 is a leeching feature. Request 7 is pointless, filelist hashes change all the time... you'll have too many different hashes of the same username. What do you mean by request 3? Share this post Link to post Share on other sites
Posted February 26, 2006 Request 4 is a leeching feature. Request 7 is pointless, filelist hashes change all the time... you'll have too many different hashes of the same username. What do you mean by request 3? maybe an ability to make some kind of link to directory or then an ability to convert links in directory names clickable... edit: currently it's possible to do links like: dchub://hub-addy.no-ip.net/SomeUser Share this post Link to post Share on other sites
Posted February 26, 2006 Only that can crash the client :mellow: Share this post Link to post Share on other sites
Posted February 26, 2006 ...and cannot be done by it's context menu. One thought: links to the directories should NOT be hard-specified as dchub://some-hub/... because more then one similar directory can exist on enother clients. I think, that it can be done just as magnet links with the checksum & search: some kind of shecksum of the corresponding directory is calculated from all file's and subdirectory's checksums and their names in it. Subdirectory's chechsums are calculated as well. When user gets such a link, the client preforms the search with a special option (searching directories by the checksum) and finds a number of unique directories (more then one hardcoded and it's great!!!) Filelists (7) may be separately shared by the user's name. Share this post Link to post Share on other sites
