And here we go again.....
Hello! I'm not sure how many actually enter this blog anymore, but to those passing by; Hi! Nice to meet you. :-)
And to those who have been here before: Welcome Back!
I must say it's quite some time ago I posted something on this blog, but I'm still available if you have any questions regarding the BitComet Client. Always remember that.
Summer has finally gotten it's hands around my part of the world (Denmark), which is incredibly nice. Some don't like the summer; however, I'm one of those persons who absolutely love the Sun and warmth. And in the Winter-months I can almost get into a depression, when several months have gone past without just a little "kiss" from the Sun (also in the Winter months I wake up when it's dark and I get home when it's dark.). So I enjoy these days a lot. I hope you do too.
I found it as a very funny coincidence when BitComet V. 1.02 got released RIGHT on my birthday! (June 3rd.)
The developers couldn't have picked a better day to release that version, which I would almost call "a milestone". V. 1.02 is exactly how V. 1.0 should've been (with a little extra tweaks here and there - and of course, the customisation of the User-agent.)
Anyway, as you have probably noticed: The BitComet forums have moved to a new platform; BitComet Postbar. And I've been very irritated about that, not just because of the shift - but because the admins absolutely said nothing about it in advance. That meant several of highly important PMs, with information I should use for the arguments for unbanning BitComet and so forth.
PMs from persons I admire (like funchords; Robb Topolski) and my good Chinese friend oioi21. All gone, thanks to the sudden shift - and I've tried to get them back, the admins re-opened the old boards, but the PMs were gone.
I know, it is no use crying over spilt milk, but still.
The other annoyance is the platform; BitComet Postbar. It's just NOT designed for this kind of usage, due to lack of categories, comment-limitations (about 2000 characters) & moderating options. That has made me so annoyed, that I don't visit the boards that often anymore, because I like to give adequately and thought-through answers, which in some cases easily can exceed 2000 characters. I tried that once, it took me a whole hour to write an explanation of something technically a user asked me about. When I clicked "Submit" 80% of my message was deleted without warning. What a waste of time.
Of course, it has one great thing about it; Every BitComet user can use their passport to read & write, but that just can't make up for the badly developed script. I know it's a very new system, but it simply can't be used as a forum as it is right now. It HAS to get a category-system implanted and remove the annoying limitations before it can be used as a good forum - the Chinese boards are running on the same script, but in some level, it seems like the Chinese boards are better developed. They don't have those before-mentioned limitations.
Well, as you've probably read, the developers are working on the customisation of the "User-agent". When that's done, which will be in V. 1.03, BitComet is finally "Complete". It respects every security aspect; It is compatible with every tracker and follows the BitTorrent specifications 100%!
Have you also noticed the increadible speeds you get with BitComet on open trackers due to the "Long-time seeding" (HTTP/FTP Sources) feature?
Well, I have! It's amazing!
However, I've noticed it has a bug.
The Long-time seeding feature is a new system, but BitComet lacks one feature. It doesn't block "Bad-peers" in the long-time seeding swarm!
What does that mean?
That means: You can download a torrent, and when your torrent reach about 90-99%, your client keeps downloading data, but the torrent will never reach 100%! Maybe it will, but with the cost of having downloaded several of extra data (in some instances; Gigabytes.).
Why does it do that? I haven't analyzed it technically, but after what I can observe, the high-speed long-time peers drown the good BitTorrent-peers in the swarm. That means BitComet will prioritize the "high-speed long-time seeder peers" in advance of the "normal" BitTorrent swarm.
The problem is just that some of these "high-speed long-time seeder-peers" are sending BAD DATA to you. When it does that, BitComet will continually fail the hash-check of a downloaded piece and re-download it in an infinite loop until that bad peer disconnects (and if it's a server; it'll never disconnect, and BitComet will never finish the download.).
A work-around when you encounter the problem described above is to, of course, disable the feature. You do that like this:
Right-click on your task --> Choose "Properties" --> Now, on that screen, remove the mark from: "Search for HTTP/FTP Download Source". Now, click OK and do a "Manual Hash-check". (Right-click on your task and choose: "Manual hash-check") Now, continue your task. It should now finish within short time.
I've reported this directly to the developers, and they've responded that they'll look through the code and improve the hash-check algorithm. Let's hope it gets fixed in BitComet V. 1.03 as well. ;-)
Well, I hope you're doing well and enjoying life. I'll post more updates in the future.
Thanks for reading!
Best regards,
XSTREM - The unofficial BitComet ambassador, user and supporter.
