The first part introduced different ways of organising a P2P network. This part moves into the client: how eMule identifies a file, how credits work and why realistic transfer limits matter.
A client and a protocol are different things
The old article placed eMule in the history of eDonkey and described how an open-source project can produce modified clients. The important distinction is that a particular application can disappear while compatible software continues using a protocol.
A modified build may change features or behaviour, so obtain software from an identifiable project. Do not assume that a familiar name attached to a repackaged installer establishes its origin.
Credits are between particular clients
eMule rewards uploading through a credit mechanism. Uploading to a particular peer can improve your position in that peer's queue. It is not a universal score that buys priority with every participant on the network.
The original text also claimed that people who did not share would enter a blacklist and might receive corrupt data. Those claims have been removed. Credits affect queue behaviour; they do not make deliberately corrupted transfers a normal penalty.
A hash identifies bytes, not trustworthiness
A file identifier helps the client recognise the same file even when sources give it different names. A matching hash is useful for identification and integrity checks.
It does not tell you that the contents are safe, that the title is accurate or that you have permission to share the file. Use publisher information where available and inspect the actual extension and size. The file and shared-folder guide explains the distinction.
Set limits for your own connection
Know the difference between the connection rate sold by an Internet provider and the transfer units shown by an application. Measure the capacity available on the connection you actually use, then leave upstream headroom for normal browsing and connection control.
The old article gave a fixed upload recommendation for a particular broadband example. That figure is not a useful general default today. A conservative setting that you can test is better than copying a number from an unrelated installation.
Continue with part three for ports, servers and source availability, or use the download-speed checklist.
English edition of Daniel's original configuration article, updated to distinguish historical advice from current behaviour.