DC++

TasMan

Well he gave up his claim of writing the hub software and then disappeared. I haven't really thought about it since... It was kinda stupid though, claiming to have written the code without changing anything but one frame on the interface and posting screen shots on a forum I regularly visit along wi...

TasMan

By the way, I appreciate the comment about using the SDCH source...the last person who "borrowed" it wasn't so courteous and claimed to have written the entire thing themselves =p.

TasMan

Cool, somebody is actually used code made by me =). I'll be sure to keep an eye on updates...

TasMan

I've just got one question (and yes btw it's looking quite nice or rather it did when I skimmed through it =p); Would DC(H)++ support the old protocol in the event that the hub / client connecting does not support the new one? I would prefer it not to myself. It'd be bloody annoying to have to conve...

TasMan

Errr in the case above the client is obviously DC++ 0.305 =). Just need to know if the flaw is in the client or hub implementation.

TasMan

One question though....considering that the client does not add a "UserIP" menu item or anything, if the client supports UserCommand, should the hub send a UserCommand for UserIP? I would've thought the client would automatically create it but what do I know =p. No problem for me either way of course.

TasMan

Version 0.03 supports UserIP2 as well.

TasMan

Thanks...

Ok, so we've got various forms of U, B and L, as well as D and F for bandwidth limiting. O is different in NMDC2 and DC++...

Are there anymore conflicts between tag characters or unmentioned ones? I'm trying to make a list of things I need to support...

TasMan

What are the characters used by the various upload limiter mods for DC++?

I know L: and B: are used. How about U:? (I think D: is for download too no?) Also if they use different values (ie U gives a percentage or is in mb/s something), please tell me =).

TasMan

Anyways you're right too....I would say the message DOES get queued. However you need to yield the threads execution for a moment so that the message gets sent before you disconnect the user.

TasMan

VB's definition Function DoEvents() As Integer Member of VBA.Interaction Yields execution so that the operating system can process other events Perhaps "pause" was the wrong word, but that is what I was trying to say =p. DoEventsForMe is just a wrapper function so that VBScripts can access the DoEve...

TasMan

DoEventsForMe simpy suspends executation (ie pauses thread)...it is needed before disconnecting a user because sending messages, etc need a bit of time to get sent out.

TasMan

I can tell you I think will be out before December...I hope =). I won't make any promises though...they get me in trouble. Almost done the major bug fixing stage (as it was a complete rewrite so there were lots), now we're getting into more feature oriented scheme adding a little bit at a time.

TasMan

My only qualm : I think it should include the nickname. After all, many people do not want the hub to kick ops for failing to meet min share, etc. OR this should come after ValidateNick (which isn't a good idea, because if they aren't registered, they will be let right on in). Other than that...brin...

TasMan

SDC / SDCC = Shadows Direct Connect / Shadows Direct Connect Client = client

SDCH = Shadows Direct Connect Hub

I know the names lack imagination =)...but SDCH is a hub (I should know, I'm the project manager; tell me if I'm mistaken =).

TasMan

Question Sedulus : Assuming the hub has EXTENDEDPROTOCOL / Supports support, the UserCommand should be one of the params in Supports correct?

TasMan

I was just doing a test with the NMDCH 2 registration and for some reason it opens a UDP port for listening (if it's relavent, I can do it again to see if the port stays the same). Obviously this isn't a multi-hub feature or anything =p. So does anybody know what it is for?

TasMan

And as for my experiences.....0.01 looked like an underdeveloped word pad =)

TasMan

The first version I "used" was 0.01, but I didn't scrap my NMDC client (which could barely run on that machine used back then =) till about 0.03/4 (can't remember which....).

TasMan

Wouldn't it be much easier to implement a delayed nicklist? (i.e. do not send nicklist until MyINFO has been recieved and only if it was requested)

It would maintain backwards compatibility at least.

TasMan

I just whipped this little thing for you - you need to have the VB6 runtimes installed though......source included.

http://shadowdc.sourceforge.net/LockToKey.rar

TasMan

Well which VB hub? I probably could implement a quick-n-dirty scripting capability in about 15 min =) (mind you, I am in the beginning of exams atm and have my own hub project to take care off)

TasMan

There is mine =)....but the current release leaves a lot of be desired, so I'd wait for 0.02 before casting judgement.

There are others like :

ODCH
ODCHub

and there are dozens on others....search SF for "dc hub" and "direct connect hub" with "Require all words" and you'll get quite a few.

TasMan

Being modest is a good thing

Especially with the next version, because there are quite a few changes, most of which require changes in admin scripts only however. But as usual, there are classes provided which do the work for you, so it isn't THAT bad.

TasMan

Not exactly.....they aren't though mostly because I hate spelling mistakes, and some features (such as multi-hub search) are now redundant. I would say though that most scripts (aside from admin ones - they would need more) would need only 1 to 5% worth of changes. Also since some features are built...

TasMan

it is not known what the <pk> is for. and some client implementations skip the Pk= part altogether (DC++ can cope with this, presumably NMDC as well)

You need to have the Pk= with NMDC. The client won't be able to connect to the hub (or the client) if it isn't present.

TasMan

Btw you should mention in your documention that default port for registration servers (2501) and how often the NMDCH registers (to prevent getting banned from the server - the NM list anyways).

Does anybody know how long you stay banned for? Hours, days or permanently?

TasMan

Alright I figured out what's with the NMDCH registration server lock to key.....I set vandel405.dynip.com to 127.0.0.1 in my hosts file and generated random locks and logged the lock/key/port. As it turns out, you are right aDe. It is the local port used to connect to the registration server. Howeve...

TasMan

If you read ButterflySoul's entire post, what he's really annoyed about is the blatant posts about PtoKaX. Spamming is a thing nobody likes....(many posts ptokax are mentioned where it doesn't really have any relevance - even here! =) I agree with one point though. Stop the pointless flaming - and m...

TasMan

Hmmmmm I just noticed you can. Strange how I used to have problems.....it always gave me zero - must have been the timing I suppose. I've changed this in my personal test hub.....assuming I stay on the NMDCH list, I'll assume aDe was right (I was on before but I can verify it right now.....damn rand...

TasMan

But DCH++ is meant to be a hub for experienced users, and people who are comfortable in doing things without a GUI.

It would be cool though to see a "WebAdmin" plugin which allows connections from the local host to edit it.

Nice shiny "GUI" and not everybody has to use it.

TasMan

Hmmmmm I suppose I'll have to check it out. This weekend I suppose. Maybe I'm wrong, but I was sure I always got zero.....maybe not. It was a long time since I had to do anything in that area.

TasMan

Errr are you sure 'bout that aDe? Because with VB winsocks, you'd have to do some work to get the outgoing port (it always reads 0 unless you set it). Hmmmmm but I was on the NMDC list at one point (I've never registered a hub at this address before), with the correct amount of users. But I use the ...

TasMan

You need to install the NMDC client first (get it from the same website as you got the hub).

TasMan

Indeed Nev.....after realizing my own folly, I went and implemented a delay nicklist =).

Give me a shout if you get that featureset going - I'd probably support it.

TasMan

A bunch of issues have now been fixed (I didn't want to start a new thread - one's enough for SDCH in the DC++ forum =)

Once again, the download url is : http://sourceforge.net/project/showfile ... p_id=71384

TasMan

oh yes and download it from here

http://sourceforge.net/project/showfile ... p_id=71384

once again! Please don't expect this to be a mass edition or anything. Developers/scripters are the people I'm hoping right now to get feedback from to fix all those bugs created by late nights.[/code]

TasMan

There is hope for the universe....and SDCH isn't it. I admit it's all fraud! I tricked you all! :) Now assuming that got everybody's attention, you should read the rest before using this release (or looking at the source). 0.01 is done. Please kill me =). The entire hub was written in 7 days (starte...

TasMan

bOperator was included for script compatiability (returns true if they are an op) If you look at the values of the property "Class" (eClass), you have a bunch of choices and their numbers : ex Invisible = 3, Registered = 2, Admin = 8, Locked = -1, Normal (Unregistered) = 1, etc It's useful for scrip...

TasMan

Hmmmm so I'm guessing that the NickList request is queued and responsed to later? Hrumph. Though I had something there =)

TasMan

When DC++ sends two myinfo. I know why (to update the hubs where the user is registered/op/etc). A possible solution to this is to send MyINFO after the client recieves OpList. (After all the client sends "Version...GetNickList...MyINFO"). Since myinfo comes after GetNickList, it shouldn't cause a p...

TasMan

I'm still learning my C++ and now to to test things in VB I should go with Java?

*dripping with sarcasm*

TasMan

Alright SDCH is done. Bugs fixed. In probably about 8 hours from now, ButterflySoul will have done some tests himself. If there are no *major* problems, the release will go ahead, as scheduled, tonight (for me anyways). Once it is, I have a few comments to make before anybody should be using it, so ...

TasMan

Besides if you keep your system conditions fairly constant (i.e I run most tests on a comp running nothing Win98 - it's the only that thing running). Assuming you don't run anything like music or games, etc, the tests should remain fairly constant.

TasMan

What is the right way then? I've never had any problems with slowing down my programs testing this way...(it's better than guessing!)

TasMan

http://shadowdc.sourceforge.net/Help.script has nearly everything listed now.....just in case you decide to try your hand at a script, when the hub is out (probably tomorrow - need to test for bugs, etc)

TasMan

Well I haven't written the script yet =). But that last part about not forward is child's play. Consider it done! (But first I should release the hub soft

)

TasMan

I suggest having a new multi-hub chat put in SDCH. Using the wskScript events, it isn't so bad on performance (as Sub DataArrival is called many times :) which the script calls I'm sure) I'd be willing to write one later however....(which is compatiable with Stim's bot) I guaruntee it would be faste...

TasMan

Btw....you have direct access via colUsers to the NickList and OpList variables (I don't generate them on the fly - too slow). You don't even need (un)register bot name function now =) (it was included for compatiability and it's a nice function)

TasMan

errr the AddObjects should go before the AddCode

- otherwise I think an error occurs

DC++

Search found 194 matches

Bandwidth limiter tag characters

NMDCH 2 UDP

DC++ and Double MyINFO