FAQ

1. Why was FearDC launched?
2. How is FearDC different to DC++?
3. Does DC++ keep up with FearDC changes?

1. Why was FearDC launched?

FearDC was launched only for one reason - to extend and improve NMDC protocol support, as the official DC++ team seems to have frozen the feature set and stopped improving it completely. Since both official and unofficial NMDC features and extensions appear at different places, there is also a need for a client to support these. The main such feature is TLS-encryption support for NMDC hubs, in case these hubs provide that support to the clients.

2. How is FearDC different to DC++?

FearDC is an exact fork of DC++, our code is always merged with latest DC++ code before being compiled. We only provide a few improvements and features to DC++ in form of a client with different name, mainly to the NMDC protocol part of it. Our second goal is to keep up-to-date with libraries included with DC++, and even replace the deprecated ones, when ever possible.

3. Does DC++ keep up with FearDC changes?

Actually DC++ team does implement some improvements and bug fixes initially made in FearDC. Sometimes they do it in a different way, which allows us to merge back with DC++ code, in order to keep number of changes in FearDC as small as possible.