Mortan

They should definitely bring this back. It is the best feature other clients have compared to BitComet. BitComet downloads way faster, but you have to do all the stuff manually, when most torrent sites have RSS to let you automatize it.

That's what I do, but it's always better to have somebody else to do stuff for you.

Although the disk space is minimal, so many files do something worse: enlarge the MFT. The bigger the MFT is, the more chances it has to be fragmented. But I also like to have them around for some time, so I don't download the same torrent several times. A checkbox to disable it it's fine for those that don't want it altogether. But I think it would be even better if we could schedule their deletion after some time. Something like: "Delete from the archive torrents older than X days"

Exactly my point. It doesn't matter if this site had the announcement, since this site is not related to all these others, the other sites should have had the announcement too. All those sites share the passport, so if something is going to be done to the passport sever, all sites that use the passport should announce it.

Well... let's se... Tocomet and comet blogs. Playcomet and all its games. MComet AtComet Not everyone is a frequent visitor of the forum. Most people get information about a site in that site. I tried to login several times in my blog with no success. The only way to see this announcement would be to come to the forums. But NOT everyone comes to forums. Those that play, for example, Zero Online, will check the Zero Online page to see why can't they login. And in all those pages there are no links to this forums. All of them link to tocomet pseudo-forums. So there is no way for them to know anything about this from each of those pages.

The only warning in the entire Comet newtwork I saw was the one in this forum. The other Comet passport sites didn't have any kind of warning until today, now that everything seems to work again.

Things like this happen more frequently than one would think. This happened to me with a certain torrent that was replaced by a new one after a while. I had downloaded most of the files of the old torrent, and then downloaded a new one. In the new torrent all the old files were the same, but extra files were added. So I copied the files to the location of the new torrent, deleted the old torrent, and performed a hash check. I had then the new torrent almost fully downloaded, and started uploading the data I already had, while downloading the new. I can't recall much of the info, but I do remember that I had much more upload and download than I should in the column.

Best news I heard since they split the max number of tasks between HTTP/FTP and BT.