GUI Improved: Torrent maker dialog changed to modeless window
GUI Improved: supports edit Tracker URL for Magnet URI task before torrent downloaded
GUI Improved: new command in Tools menu: enable eMule plugin, show/hide plugin window
GUI Improved: support set task tags in BT/HTTP task properties dialog
GUI Improved: move downloaded files to tag associated folder optionally when add task tag using task context menu
GUI Improved: supports switch input focus to list control inside task tabs by Tab key
GUI Improved: add icons to task context menu
GUI Improved: display "not supported" in ed2k link field of file list for private torrents
GUI Improved: new setting in advanced page of option dialog: system.show_debug_info
GUI Bugfix: can't drag&drop download links to floating windows from IE8 in Win7
GUI Bugfix: the save path edit-box in BT/HTTP task properties dialog doesn't support mouse wheel
GUI Bugfix: Web interface doesn't support to download Magnet URI
GUI Bugfix: the last task in task list doesn't get refreshed in some situation
Core Improve: support BitTorrent Extension Protocol of peer exchange, compatible with BitTorrent mainline
Core Improve: new eMule plugin (based on Xtreme 7.2 mod)
Core Bugfix: after removing tasks without removing files, the Long-Time Seeding for these files won't stop immediately
Core Bugfix: after disable LT Seeding in option dialog, running tasks won't stop downloading from Long-Time Seeding immediately
Core Improve: support BitTorrent Extension Protocol of peer exchange, compatible with BitTorrent mainline
I want to especially salute this one. It was a huge thing on my wish-list.
This means that now BitComet can exchange peers not only with BitComet clients but with every other client out there which implemented this. And there are quite a lot of them!
I just have to ask so that we all are clear about this:
Is this version of BitComet still supporting the old PEX protocol too, so as to be backwards compatible with older clients, or was the old PEX replaced by the new one?
Is this version of BitComet still supporting the old PEX protocol too, so as to be backwards compatible with older clients, or was the old PEX replaced by the new one?
Following please go:
The lastested BitComet communicates with other BitTorrent mainline by new/offical BitTorrent Extension Protocol and communicate with older clients by old/BitComet’s own BitTorrent Extension Protocol. In this way, it will be compatible with both of other BitTorrent clients and BitComet older versions.
I’ve added the post above, since this topic is referenced as the discussion topic for the beta announcement all over the forum.
But the announcement contained the changelog of the v.1.18 version instead of the changelog of the beta version.
So I’ve changed the title of the announcement to the last beta number (20100203 instead of 20100201), put inside the changelog of both beta versions and added this one here above, too.
:rolleyes: :rolleyes: Hello One thing I would like to see is what is being uploaded. I have some stuff I don’t want some smart hacker to get into. Probably in wrong place again. Oh well. 6_wheeler :lol:
All that is being uploaded is in your Task List. Nothing more or less.
As for a hacker, if s/he really is a hacker s/he doesn’t need you to run a BitTorrent client to access your computer. There are smarter, faster way to pick your system than this.
If you’re not running a firewall and/or anti-malware scans regularly, you’re very likely to be a zombie already.
Bittorrent is nothing like other P2P applications that you may be used to – such as eD2K, or gnutella or Ares. The whole concept of a “shared directory” has no application in bittorrent. People don’t look over what you’ve got, pick and choose from the contents, any of that.
Quite the contrary, there are only those items that you pick and choose to actively share with the swarm. You decide, “I’ll share THIS one”, then you create a task for seeding it, and run that task when you want, for as long as you want.
The seeding task uploads, not to a particular peer, but to a swarm of peers, sending a piece here and a piece there, tending not to send two pieces to the same peer sequentially and trying to spread out its distribution as much as possible. When you stop the task, your computer is no longer sending any of it out, nor can be made to start doing so by anyone but you.
Anything else on your disk that you didn’t create a torrent for, and start that task running (both very deliberate steps (which you could not do by accident – they’re too complex for that) cannot be obtained from you via bittorrent.
People who learned, say, LimeWire or BearShare have a difficult time with bittorrent, and vice-versa because the protocols are so conceptually different. If you’re coming from one world into the other, then “everything” you know from that other world is wrong.
