Foobar

Member
 View profile  See their activity

  • Content count

    7

  • Joined

  • Last visited

Posts posted by Foobar

  1. Posted

    I would like Apex DC++ to become an UTF-8 programme. I don't know if it's possible, but it would be really nice.

    Yes it's possible. NMDC is ASCII, which is a subset of UTF-8. It's just that DC++ and its derivatives seem to have so limited capabilities regarding the different character set codings - can you even choose the set you'd like to use? In Valknut I have been using UTF-8 successfully.

  2. Posted

    Version 1.4.1

    Last Update 11/29/03

    ^^ dead fish in the water

    It's the original protocol, so of course it's old. And that is good; it's stable and functional.

    time to realize adc is the future and clients that doesnt fix adc is dying so i hope valknut fixes that or linuxdc++ gets the better parts of linux users

    Maybe ADC is the future (maybe not), but it doesn't mean that DC as such should be killed. They can co-exist.

  3. Posted

    DC protocol specification you post is not the real specification. It's just because no specification for DC protocol exist. So we can't talk about compatibility with DC specification.

    Yes it is the real specification. How could have the hub and client coders ever been able to code new DC software, if there hadn't been any specification. The specification defines the protocol.

    True; it was not an open specification by the author of DC, but it was reverse engineered afterwards.

    True; it is not a real standard, but more like a de-facto standard.

    DC compatibility means that the client is able to connect to DC hubs and is able to cooperate with clients in there. And I have no problem with DC++ (and its mods).

    Right, and to be able to co-operate, a certain protocol has to be followed. Definitively a single client programmer (the author of DC++) should not have broken the DC compatibility with other clients. I just wonder when he's going to remove the capability to connect to DC hubs. He's going for ADC...

  4. Posted

    If they get it up to DC++ Standards and get it stable last versions i tested died for me totaly thats why i dont like it at all

    Well, in DC world I like to prefer DC compatible clients. Valknut is fully compatible with DC so it's a good choice.

    DC++ is leaning towards ADC and is not DC compatible anymore. Same with ApexDC++; does not fulfill the DC specification.

    Here's the DC protocol specification: http://kjarni.cc/files/dc/dcprot.htm

    If a client is not compatible with DC, it should not be allowed on DC hubs... plain and simple. DC as DC, ADC as ADC, why should they be mixed?

  7. Posted

    Pedja is correct. (He already explained it quite well.)

    This whole "fixed character set" issue is maybe a fault in DC++ itself, and not directly ApexDC++ related.

    Just like in IRC, a DC client should include an option to choose the character set to be used, because the used protocol (DC) does not define it in any way. For example Valknut has this option.