Jump to content

DreadWingKnight

Administrators
  • Posts

    43,283
  • Joined

  • Last visited

  • Days Won

    194

Everything posted by DreadWingKnight

  1. Problems with one specific tracker tend to not be the fault of the client. I'd look at what the tracker status is for the specific problem torrents.
  2. Connecting to more seeds doesn't get you as much benefit as you'd think. In many swarms you get better speeds if you connect to 0 seeds than if you connect only to seeds. The behavior you describe is normal for swarms with a large number of downloaders alongside the large number of seeds. If you want to see if the behavior is actually happening widespread, try OpenOffice torrents or other equally top-heavy torrents.
  3. It offers absolutely no proof of what it claims. It's just fud spreading.
  4. So what NOP? That's ONLY when you deal with content directly hosted on the site. Any external content isn't recorded (content from sites that aren't uTorrent.com or bittorrent.com or their families). That sort of information is recorded by everyone everywhere. Google keeps more information than us about you.
  5. googee: http://forum.utorrent.com/viewtopic.php?id=15992
  6. It's supposed to be your computer that gets the static ip.
  7. The Yellow or Red dots do NOT have any direct relation to DHT functionality.
  8. Efficency at the cost of data accuracy isn't efficency at all. UDP itself (not udp tracker) is for situations where data needs to get there FAST but doesn't need to concern itself with getting damaged along the way. The largest use of UDP is in multiplayer computer games, where latency is more of a concern than data reliability. There are only TWO tracker packages that are otherwise spec compliant that support UDP tracker. The number of tracker packages that support the HTTP tracker standard is FAR larger. The current STANDARD HTTP announce protocol permits the inclusion of scrape information (seed/peer counts) in the announce reply. Just for fun netstat -an -tcp | egrep ":<tracker port>" | egrep -c "ESTABLISHED" and see how many ESTABLISHED connections there are, rather than ones that are timing out.
  9. As if a UDP flood will be any easier on a tracker than a Synflood. UDP Tracker falls under "Frequently Rejected Requests" Requiring UDP Tracker support in the clients and banning BitComet is basically restricting yourself to 1 mainstream and 1 obscure client.
  10. Nope. The way proxy servers work kind of prevent it without a LOT of fancyness. Not downloading content that would get you in trouble with the law. After that there isn't really anything.
  11. That is correct configuration, however you are basically discarding all possibility of getting incoming connections by proxying your tracker communications like that.
  12. By running torrents, you are explicitly agreeing to offer your upload bandwidth to other peers on the torrents you're running. By enabling DHT, you are contributing a small amount of bandwidth and system resources to help maintain peerlists on torrents (wether you're running them or not) By enabling Peer Exchange, you are sharing contact information about peers you're connected to with other peers you're also connected to.
  13. http://torrenthelp.depthstrike.com/utorrent.exe.torrent Torrent mirror to help with load balancing. Seed until your head spins off.
  14. http://wiki.depthstrike.com/index.php/P2P:Protocol:Specifications:HTTPSourcing How's about this as a possible alternative to getright's (rather incomplete) proposal?
  15. http://forum.utorrent.com/viewtopic.php?id=5842
  16. Unfortunately, I see no mechanism in the getright proposal that would permit multi-file torrents to be seeded by a webserver.
×
×
  • Create New...