DC++

In another thread I briefly touched the subject on what is protocol compliant and what's not. I'd like to extract some key notes from that thread, bake it with some other thoughts I have, and make it a topic on its own. As there are many hubsofts in progress but still very few clients, with dc++, an...

There is no solution to the double MyINFO thingy as there is no problem with it. dc++ connects to one or more hubs and after some initial handshaking eventually send a correct MyINFO to the hub. If it receives a $LogedIn from any hub it is connnected to it recalculates the H: for the description and...

I almost fell out my chair until I read angelfusbars reply. Even though GetNickList is sent before MyINFO I stall the NickList until the client have gone through all possible checks. Like ISP-IP check, ban-check and dc++ description scan and so fourth. This ensures that ASH does not generate and sen...

This is a somewhat old topic that I would like to shine some light on. One excellent feature in dc++ is the autoreconnect feature making dc++ very reliable when a hub is restarted or you loose your socket or whatever. The same feature is also OPs worst nightmare. As you can tell by the title the rec...

ASH can also detect users tunneling. However, for hubs that uses isp-check this is a serious issue. The problem is not to detect a guy tunneling. Problems arrise when you try to deal with it. With so many networks using only one single outgoing IP in conjunction with DHCP, banning one single user of...

I think this is an excellent idea