Big Muscle

Member
 View profile  See their activity

  • Content count

    702

  • Joined

  • Last visited

Posts posted by Big Muscle

  4. Posted

    a block user optin if you can do that, so if this activatet a selected user could not download from me, or a black list :)

    ok, so when it is implemented, I'll block only you :thumbsup:

  6. Posted

    If revconnect revised their code to disable downloading/uploading of private hub users then we'd consider this. ;)

    I think you don't understand matter of Kademlia. It has nothing to with hubs, so you can't disable it for certain hubs.

  7. Posted

    <-- no problem running VS 2005 builds, altho haven't tried StrongDC++ code. And I haven't updated to STLPort 5 yet. (old fashion, why update if it's not broken).

    interesting, but STLPort 4 doesn't work under VS2005. Actually I use my modded STLPort where's fixed bug which is there since version 4.

  8. Posted

    why would it be banned?

    I have alredy said that this could be done in a way that it'd:

    a) be detectable via tag or description for example...

    :D be disabled when using DC++ emulation (only would apply to mods with emulation cababilities)

    and i understand why CraKteR is against this, but i won't understand why you are as you have added many eh.. questionable features to SDC++ before (limiter & segmented downloading) and this features have alredy caused SDC++ to get banned in countless of hubs, though thanks to your efforts with DC emulation SDC is still usable in public hubs...

    but as i have alredy said this discussion is pretty much pointless....

    and what would it write in tag/description ? Something like "Hub A: XXX GB, Hub B: YYY GB, Hub C: ZZZ..." I think it's weird :-P People are lazy so they would share only minimum what they can.

  10. Posted

    MSVS 2005 also supports these optimizations =] but most of them can't be set manually but it's done automatically (e.g. vectorization). But just remember that no optimization can really improve your program, it can be done only using by optimized algorithm.

  12. Posted

    Maybe I understand what you're talking about - losing slot when chunk is finished.

    I don't know exactly how it's done in PWDC, but if it's like in StrongDC++ then there's possibility to lose slot only when you have enabled DC++ emulation for hub you're downloading from...

    When emulation is disabled, then you can't lose slot :D In next version of StrongDC++ there will be feature that if user speed is known then chunk position will be assigned according to the speed :)