btx

Hi, I'd love to help test the OSX version! I know the NMDC protocol fairly well, as Ive written several pieces of software that utilize the protocol (console bot, hub, chatbot, etc). I've run a few different clients on OSX - Shakespeer, Jucy, and now EiskaltDC++. I'm quite capable with packet sniffers and debug tools, so I could contribute useful bug reports. Also, having written a bot that works on Linux and OSX, I am experienced with some of the primary differences between a Windows version and an OSX version (filename character encoding can be a headache). Even if you don't want/need my help with testing, thanks for targeting OSX, and I eagerly look forward to being able to try the client out! btx

Two things in the latest DC++ core... There seems to suddenly be some parameter tacked on to the end of ADCGET requests in the form DB# (where # is the number of bytes downloaded so far). I'm not entirely clear of what the purpose of this new parameter is - I only noticed it because the client I wrote was complaining about it. The only thing in the changelogs that sounded possibly related was some more accurate % completion feature... tho I don't see why this information would be passed to the uploading client (unless it's supposed to be returned somehow). Is this parameter documented anywhere? I tried to find a discussion on this new protocol extension, but couldn't find it anywhere. WOnder if any other clients are as strict with their protocol msgs as mine is - it could cause compatibility issues? Seems like this should be based on some Supports token, but looking at the code, it appears to always be appended to the adcget command. For now, I'm just ignoring the token, but I'd feel more confident if someone could point me at some documentation of the feature Apparently it's now checking the filelist for duplicate TTH entries. It's kind of a bummer, because my bot has handlers for the filelist that arrange the share into different forms ... by date, by alphabetical order, by type, etc. Anyway, the thing that seemed less than ideal wasn't that it doesn't accept duplicate files, but that the client displays an error msg rather than displaying the unique TTHs. Probably is something that only affects me, so probably not a big deal. Thanks in advance for any help or insight anyone can give, btx