Jump to content
Comet Forums


  • Posts

  • Joined

  • Last visited

About mlewellyn

mlewellyn's Achievements


Newbie (1/14)



  1. I think most of us have done so, since so many major sites are starting to use features which were added to Firefox after the version CometBird uses (the Firefox version it's based on is about two years old at the date of this writing). It's a bit unfortunate, but que sera sera. They only have so much development time available, and they're a business, so a free browser which doesn't generate any income can't really rank highly (I can't recall any ways it tried to monetize me beyond the default home page anyhow).
  2. In my opinion, BitComet should allow hostname input (passing it to WinSock's resolver to obtain an IP address), rather than strictly IPv4-format IP addresses. Sometimes when manually adding a peer, they give you their hostname rather than their IP, which then has to manually resolved. These are computers, they should do the dirty work for us! B) Note that the Add Peer functionality would have to be revamped a bit anyhow, if my IPv6 feature request were to be implemented. It would be great if multiple birds could be knocked out by the devs at once (i.e. lay the foundation for future IPv6 support with this request, even if it's not all there yet). I envision the logic proceeding as follows: Input starts with: dotted decimal notation (all it currently accepts) - IPv4 colon-delimited hex pairs, enclosed by square brackets - IPv6 anything else - pass to resolver Since Add Peer isn't a huge performance bottleneck, due to it not being used on a constant basis, I can't foresee the additional processing causing inconvenience for users (indeed, for IPv4 addresses, any slowdown would likely be imperceptible and any other address type is currently unsupported, so slow is better than not at all). The only side-effect I can think of is if the resolver takes a while to respond for a hostname, but I'm sure BitComet handles this already for resolving other things (such as trackers). :) This is an issue as of BitComet 1.28.
  3. I do have to say that I do use IE (9, at that) and have never seen the issue that's described. I expect it's more than meets the eye. I haven't really looked into the registry change suggested above, nor do I have a "broken" BitComet to compare those settings (and my current settings) against. However, the registry settings indicate that affected systems have some messed up settings for Protected Mode. I would be curious from a purely academic view to know if there's a common thread between the IE installations having the issue. If nothing else, it might help people come up with a good workaround until the time it's fixed. Such questions as the following come to mind: Windows general: Windows version 32-/64-bit UAC enabled/disabled IE Security: Internet zone security level Whether BitComet's servers are in the Trusted or Restricted Sites (or neither) Protected Mode enabled/disabled Internet Options (Advanced): Security: Allow active content to run in files on My Computer (Now that I listed these, it strikes me that the data is potentially useful to the BitComet developers to allow the installer to offer to fix the settings or to make the program work around them...) My gut says that it's one or more of the options listed above that's at fault. Further, my gut is leaning toward the active content being disabled. For comparison with those having issues, on my working BitComet installs, I run 64-bit Windows Vista/2008/2008R2/7 with UAC enabled across the board. I leave the Internet zone set to Medium-High, I don't have any BitComet servers listed in any zones, and have Protected Mode enabled. I also allow active content to be run from files on My Computer. Of course, my gut might be wrong. It may well be that some people have gotten unlucky and somehow their registry settings differ from mine and the previous poster's registry changes may shed light on the issue. However, since he did not describe which value in particular is likely in error, and what the value means, it's really hard to know for sure. Personally, I wouldn't make unknown changes to my security zones. It seems very... insecure. :rolleyes:
  4. Oh, I dunno... 匍匐同輩 works for me... And it almost even conveys what was meant! :D (Plus, I like way the phrase sounds. B) ) Also, I've seen this behavior for quite some time in BitComet. I always assumed I was doing something wrong, or was misinterpreting something, or was missing some piece of the puzzle. <_<
  5. I thought I should provide a brief run-down on IPv6 for those who might not be familiar with it outside of (usually mostly-accurate, at best) news reports. I sincerely hope that the devs don't need this post... :lol: I just think it's only fair that the rest of the users are aware of exactly what they're likely to start seeing at a fairly rapid pace. IPv6 is a whole new addressing system for the entire Internet. About 15-20 years ago, some bright people foresaw that the Internet was growing very rapidly. Of course, rapid growth with a limited number of addresses logically means that you'll run out at some point (this is called "exhaustion"). So, they came up with a replacement for the IPv4 addressing scheme, while at the same time coming up with novel ways to postpone exhaustion so that software and hardware vendors would have sufficient time to educate their users and implement the new IPv6 scheme long before exhaustion became an issue. Unfortunately, the novel ways of postponing exhaustion, alongside the proliferation of underpowered consumer gear, worked too well. The IPv4 address space officially hit exhaustion very early this year, so once the various geographically-based numbering authorities run out for their areas, there really are no more addresses coming. On the bright side, larger ISPs worldwide are in the midst of large-scale IPv6 testing and deployment. Operating systems from the previous decade or so should have no problem with the change to IPv6, and even Windows 2000 has a IPv6 component still available from Microsoft (even though the OS is unsupported these days, and the experimental IPv6 "stack" moreso). Even most consumer gear has IPv6 options these days, even if they're hidden away since IPv6 manages to simplify networking enough for the average Joe to be able to just plug it in and it "works". As for the torrent front, more and more private communities are ending up hosting their servers in facilities which are desperately feeling the crunch of IPv4 exhaustion. More and more facilities are asking for "justification" forms which get sent to the numbering authority before giving out more addresses to each customer. In fact, I've started seeing facilities which give 4 addresses per server rack, without a justification form. If you're able to fit at least 8 machines into that rack, and you're doing things like a private filesharing community, I can see why you might be interested in making those 4 (or fewer) IPv4 addresses go further. Also, IPv6 has many features which manage to enhance privacy a bit, plus the companies who use questionable tactics ("We THINK we saw this IP on a torrent we used DCMA takedown on! Cut their internet, matey!") have not yet been seen on the IPv6 trackers. There are more than a few people who are quite pleased about the idea that they are able to change IPv6 addresses extremely often, knowing that if they DO get a bogus report to their ISP, that IP will no longer be valid at that time. (Nevermind that the few IPv6-ready ISPs are probably not yet ready to even track their customers' IPv6 habits.) If you want to play with IPv6 now, it may be as simple as turning on "6to4" with the default options in your router. Otherwise, there are sites like Hurricane Electric's Tunnelbroker service which are able to let you wet your feet in the new Internet waters. Just keep in mind that you won't be able to use BitComet yet to connect to IPv6 peers (there are few IPv6-only trackers; you would know by now if you were using one). Chances are that much of the Internet you already visit is also IPv6-ready. They just haven't abandoned the IPv4 Internet yet. Sooner, rather than later, IPv6-only content will start appearing more and more. We've had a decade to get ready, now the snowball effect is going to happen. B) Also, Microsoft actually has a pretty good IPv6 page that manages to hit pretty much every type of person, from businessman to developer to curious consumer: http://technet.microsoft.com/en-us/network/bb530961.aspx Hopefully this will help those who only have heard about IPv6 in passing understand why I'm asking for this functionality now, rather than when the poo hits the spinny blades for a large chunk of users. :P
  6. Now that ISPs are starting to roll out native IPv6 support, and Toredo/6to4 being almost ubiquitous and almost well-supported even in the lowest-grade consumer gear, I'm seeing more IPv6 trackers and peers. Unfortunately, BitComet is not yet able to connect to these resources. :( Quite notably, trackers which only have an AAAA record (no A record and thus no direct IPv4 connectivity) give an "Tracker connection error: 11004 DNS error" in BitComet (verified that this is still an issue in 1.28). A public tracker which only has an AAAA record, for testing purposes, is Ubuntu's IPv6 tracker: http://ipv6.torrent.ubuntu.com/ Note that if you do not have IPv6 (native, tunneled, 6to4, Teredo, or otherwise) connectivity, you won't be able to view the page (and therefore download the torrents). Note that this particular tracker provides torrents which have both IPv4 and IPv6 trackers listed (though it is trivial to just remove the IPv4 tracker for testing purposes). There are some private communities already which do not: it's IPv6 for their communities or bust. Considering that many communities still have misgivings over allowing BitComet due to the missteps of years ago (0.6x and 0.85 come to mind), offering superb IPv6 torrenting on Windows would likely help BitComet's image amongst those who have closed their minds toward it bar any reason of reconsidering. At the moment, uTorrent is the only viable choice for IPv6-only trackers on Windows.
  • Create New...