eliot_cougar

Established Members
  • Content Count

    42
  • Joined

  • Last visited

Community Reputation

1 Neutral

About eliot_cougar

  • Rank
    Advanced Member
  1. A small update on the issue: I have deleted BitTorrent Speed folder and re-imported my wallet... The "Historical Stats" button is no longer greyed out, and the real-time graphs now show some activity (they were empty before)... I will monitor the situation for a couple of days, but it seems that I'm getting BTT for seeding...
  2. 3.5.5 build 45838 BTT is the cryptocurrency used for BitTorrent Speed... The idea is that you spend it to get some extra download speed from BTT-enabled peers, and you get it by seeding torrents to BTT-enabled peers... The problem I see here is that for some reason, when you only seeding, you still get incoming traffic, supposedly from BTT-peers, for which you pay even if they don't download from you... And if all torrents are paused, there is constantly a small incoming traffic with non-zero BTT price... As a result, when you are seeding, or when the client is paused, BTT balance slowly goes down, because you're being charged for the overhead traffic...
  3. I've been noticing that even without downloading anything, and only seeding, my BTT balance had never go up... Since now we have more details displayed on BitTorrent Wallet, I can see why that is... I've been running uTorrent for a while, seeding about 40 torrents... For a while a client was paused so I could do other stuff... I had not downloaded any torrents... The result is 265MB downloaded with a huge price of 6272 BTT/GB, and 1.59TB seeded for a price of... ummm... approximately zero?????? That looks a bit broken doesn't it?.. Again, I didn't download anything... All that outward traffic is just overhead for all the uploads...
  4. Oh, yes... This bug is very annoying... I guess it was there since first 3.0 alpha, and it is still there... However it happens only with some torrents, not all... It happens almost all the time with big torrents which contain long list of files (e.g. All seasons of some TV series in one torrent)...
  5. Bug: bt.transp_disposition have been defaulted to 15 somehow...
  6. It took me 2 minutes to find this option even if I use uTorrent for 2 years... What is the meaning to have two very closly named options in two settings tabs?.. PS: The option says: When adding torrents show that window... Why doesn't it do so?.. That's problem - inconsistence between expectancy and fact...
  7. Bandwidth limiting: "Apply rate limit to uTP connections" state is not remembered - Check it, press OK/Apply, Open the window again, still unchecked... Silent torrent adding: uTorrent does not open Add Torrent dialog no matter what is the state of the option "Show a window that displays the files inside the torrent"... Upgraded using the auto-update... I expect fixed revision soon... Very soon...
  8. Ofcourse it's enabled... I'm talking about this bug: http://forum.utorrent.com/viewtopic.php?pid=469446#p469446 It's Windows-specific, if you try to get FQDN for your own machine like this: socket.gethostbyaddr('your.own.ip.addr') or this socket.getfqdn('your.own.ip.addr') Windows will return your NETBIOS name instead... We have found that you have to set additional flag DNS_QUERY_WIRE_ONLY to force Windows to bypass cache and do real DNS request... Greg has wrote some advanced code to make that work, but it still doesn't seem to be included in the latest revisions...
  9. I still don't see the BEP22 fix Greg Hazel has made long ago... It prevents Windows to use its DNS cache system which returns NETBIOS name on FQDN request... (Stupid Win)
  10. I feel a bit of misunderstanding here... A lot of people DO NOT understand what the overhead is... I'm sure most of them think that overhead should be ZERO in the very ideal case, and any high number means simply "uTorrent behaves bad and can't use the full potential of the connection"... It'll be better to hide actual overhead numbers somewhere and not display them in the main window... UPD: The simple rule: NEVER set your UL limit less than 10% of your DL limit and vice versa...
  11. And once again, do you have any downloads active?.. Downloads DO generate upload overhead and vice versa... (Oh my...)
  12. Ofcourse I know that... You just missed what I was trying to say... To make measurements precise enough uTP has to keep DATA packets smaller... But that's not good if you make EVERY AND ALL data packets smaller to do those measurements... Read my post again, keep in ming that those I call "measurement packets" are actually DATA packets small enough to do precise delay measurements and all other packets are DATA packets large enough (MTU) to make overhead smaller... PS: This forum is strange, Where's "quote" button?.. Where's BBcode editor or RichText editor?.. I have only nacked textfield to write my post and I have to do all BBCode formatting manually...
  13. How many delay samples per second does uTP need to do it's congestion control efficiently... Does it really need delay measurements for every packet?.. Maybe it can send "small" (measurement) packets only sometimes (e.g. every 10th or every second) and send MTU-sized packets most of the time?.. Keyword: sampling interval ISPs, along with online gamers and VoIP users, are really angry on current implementation of uTP... Our ISP started to block uTP traffic after recieving complaints (high ping and packet loss) from online gamers...
  14. BEP22 still behaves the same for me, using Netbios name but not DNS name... What was fixed then?..
  15. It may be useful for small networks with a couple of different IP ranges, but what about big ISPs with much more subnets/ip ranges?.. How many users are really that technically educated to know how to customize that "list of local IP ranges" and take benefits?.. The simpliest solution I imagine: You have local tracker - right click - mark as local... Then the client treats all peers reported via that tracker as local and loose speed cap for them... You can even have an option in preferences, text field to enter the address of your local tracker... BEP22 seems good, but I've heard that not all users can make SRV DNS requests, or something like that, I'm not sure, I've never had such problems... And simple A/AAAA record is good too... Let's make an agreement to always treat http: // retracker.local / announce as local tracker... Some ISPs are using that already, anyway... And it works well... It's better than multicast-based LPD we have at the moment... The last thing we must think about is announcing "private" torrents on local trackers: allow or deny?.. Speed and traffic internalization or supporting stupid concerns about ratings, UL/DL ratios, "top-seeder" statuses and all such pointless crap we have on "private" torrents now...