(http://www.bitcomet.com/images/title.gif)
BitComet es uno de los tantos clientes para la red Bitorrent existentes. Entre sus principales características se encuentran su facilidad de uso, downloads simultáneos, cola de bajada, download de archivos seleccionados dentro de un torrent, límite de velocidad, uso de ip-filter, y bajo consumo de recursos de sistema. Es multilenguaje.
:arrow: Última versión: 0.70
:arrow: Descargar (http://download.bitcomet.com/achive/BitComet_0.70_setup.exe.torrent)
:arrow: Sitio Web oficial (http://www.bitcomet.com)
Les hago una pregunta.
Me venia bajando como piña el Bitcomet ;D pero ahora nuse!! me kiero bajar 2 peliculas y 2 soft y me dice "no se conecta al servidor", cuando la pagina me dice q hay seeds y leechers.
q onda? :S :shock:
seguramente es porque en Muchos trackers prohibieron el Bitcomet en todas sus versiones por un problema en el DHT. ej: BTarg,tracker x,etc
yo te recomiendo cambiar al Utorrent :wink: ,es liviano,no come nada de recursos y es facil de configurar y te baja con un caño
solanet ?
donde encuentro un tutorial de utorrent
gracias
Con una conexion de speedy de 512 a cuanto puede bajar??
Cita de: agustín2501solanet ?
donde encuentro un tutorial de utorrent
gracias
:arrow: Tutorial (Datafull) (http://www.datafull.com/infotech/nota.php?id=1235)
Cita de: Chris88Con una conexion de speedy de 512 a cuanto puede
bajar??
:arrow: No soy un experto, pero sé que depende de la cantidad de "seeds" y "leechers" que tenga el archivo. El máximo posible es 64KB (512Kb/8=64KB).
:arrow: Para los que seguimos apreciando el BITCOMET, a pesar de haber sido prohibido en muchos trackers cerrados, acá va la última versión
Changes from BitComet 0.60 to BitComet 0.61 :
- GUI Improved: enhance BCTP link command to lunch preview window
- GUI Improved: support xp themes in the embedded browser
- GUI Improved: no longer popup script error message in the embedded browser
- GUI Bugfix: the clip board can work in some user interface
- Core Improved: support wmv/asf file in the preview window
- Core Bugfix: fix the bug that DHT is added for the 'private' torrent after task begins
- Core Bugfix: fix the bug that UDP port mapping is not released when bitcomet exit:!: ¿Por qué corno están excluyendo este cliente los trackers cerrados?
The advent of DHT (Distributed Hash Tables) has been a valuable asset to the BitTorrent community. Most newer BitTorrent clients now support this network layer, which boosts the efficiency of the already capable BitTorrent protocol.
The first BitTorrent client to establish a DHT layer was Azureus, followed by the official BitTorrent client. Although similar, the two DHT networks are not compatible. The DHT layer supported by the official client would be known as Mainline DHT network. Soon after, most BitTorrent clients would release versions with Mainline DHT support, such as the popular BitComet.
The DHT layer works by creating a virtual network on top of the BitTorrent protocol. Each node that participates in the DHT layer indexes a small portion of files on the network and helps with network communications. This works great for public trackers as it puts less of a burden on centralized server resources, helps distribute files more efficiently, and saves bandwidth. It’s an underappreciated quantum leap that has been overshadowed by more visible advances such as BitTorrent or eDonkey2000.
On the other side of this spectrum are private trackers. Private trackers are not looking to widely distribute their files. These communities are designed to only allow sharing within this closed community by assigning each registered member’s IP address with a passkey. In addition, a ‘private’ flag within the torrent file tells the BitTorrent client not to share on the DHT network.
However, BitComet does not honor the flag. Instead, the torrent is shared and those who do not belong to the private tracker can freely leech off the resources of that community. For example, let’s say an individual is banned from a private tracker for leeching. In that period of time, he managed to download 50 torrent files. Since he is also using BitComet, the client ignores the flag and shares the torrent on the public DHT network.
This is highly frowned upon in private communities. To ensure sharing and save bandwidth, many trackers have tight download/upload ratio policies and enforce them strictly. Since the neither the DHT network nor BitComet have any concept of ratios, the torrent is traded freely. This situation has especially been a kick in the µTorrent for those donating to private trackers in return for higher status and more privileges.
The solution? Ban BitComet. Fuente (http://www.p2pcore.com/stories/305.php)
Versión castellana- traducción google (pedorrísima) (http://translate.google.com/translate?hl=es&sl=en&u=http://www.p2pcore.com/stories/305.php&prev=/search%3Fq%3D%2522bitcomet%2522%2B%25220.60%2522%2B%2522dht%2522%2B%2522bug%2522%2B%26hl%3Des%26lr%3D)
Thread actualizado, v0.70. :up:
que bueno el cometa :palmas: ahora tengo que usar el utorrent porque no lo admiten :'(