Contents: Use or develop · Repositories · Support
eMuleBB Rust is an eD2K/Kad client for Windows, Linux and macOS, operated through a browser console and authenticated REST API.
Active beta. CI-gated nightly builds are the public testing channel. Beta 3 is the next development target.
| Use eMuleBB Rust | Develop with eMuleBB Rust |
|---|---|
| First launch and daily use | Contribute to the client |
| Choose a platform and package | Build against the REST API |
- Browser operation: search eD2K/Kad, manage transfers and monitor chosen shared folders from the packaged console.
- Automation: use authenticated REST requests and the documented API contract.
- Explicit network controls: review interface settings, connection status and diagnostics.
- Identifiable builds: inspect source-bound package manifests, checksums and provenance.
See the platform guide for package checks, network-validation scope and the limits of the published proof.
| Repository | Role |
|---|---|
emulebb-rust |
Active Rust beta and current product-development lane. |
emulebb-tooling |
Public roadmap, lifecycle policy, product docs, and engineering references. |
emulebb-build |
Workspace, build, validation, packaging, and release orchestration. |
emulebb-build-tests |
Shared Rust and MFC diagnostics, compatibility, live-network, and parity harness. |
eMuleBB Rust is the active product-development lane. The MFC client remains the stable Windows diagnostic baseline and may receive critical fixes and bounded, low-risk maintenance.
- Stable maintenance downloads: Version 0.7.3 remains published while the 0.7.x line provides diagnostics, critical fixes, and bounded maintenance.
Test infrastructure and compatibility references
emulebb: Stable 0.7.x Windows client, diagnostic baseline, and critical-fix maintenance lane.ed2k-server: Sole local deterministic eD2K server, maintained as a minimal upstream-aligned Rust fork.- aMule upstream (
master): Actively developed upstream client used for analysis and future interoperability. - eMule stock 0.72 (
v0.72a): Stock compatibility baseline for protocol and state-machine parity.
Please report issues in the repository that owns the affected code.