emulebb-rust
The published beta is the only active product-development lane. It is experimental and not yet production-ready.
Two public eD2K/Kad client lanes
emulebb-rust 0.1.0-beta.1 is published for experimental testing. eMuleBB MFC 0.7.3 remains the stable Windows release and receives bugs and bounded low-risk improvements.
Published releases
Rust is the active experimental product lane and is not yet production-ready. MFC 0.7.3 remains the stable Windows release and continues on a long-term maintenance track.
irm https://emulebb.github.io/install.ps1 | iex
The one-line installer is retained for the shipped MFC 0.7.3 suite artifact; it is not an active cross-client roadmap.
eMuleBB now has two clear public entry points: the active experimental Rust beta and the stable MFC 0.7.x Windows client. Other repositories are supporting harnesses, reference forks, paused experiments, or release history—not additional active products.
Lifecycle
The published beta is the only active product-development lane. It is experimental and not yet production-ready.
The published 0.7.3 Windows client continues as a long-term 0.7.x maintenance line for bugs and bounded low-risk changes.
qBittorrentBB is paused, aMuTorrent is frozen, TrackMuleBB is archived, and the server forks have bounded harness or reference roles.
Stable MFC capabilities
These are shipped 0.7.3 capabilities, not a promise of renewed broad MFC development. Maintenance remains compatibility- and risk-bounded.
eMuleBB iżomm il-fluss klassiku ta' eMule u jżid limiti ċari, dijanjostiċi, REST API u prova tar-release.
eMule għal links ta' upload veloċi, libreriji kbar maqsuma, sessjonijiet twal ta' Windows u kontroll lokali.
Awtomazzjoni REST mingħajr ma tissostitwixxi l-app desktop. /api/v1, JSON, X-API-Key.
Kontroll aktar ċar tal-upload u n-netwerk
Żomm eD2K u Kad prattiċi
Provi qabel pakketti pubbliċi
Dokumenti
Use the published beta for experimental testing and report reproducible issues in emulebb-rust.
Version 0.7.3 remains the supported stable package while 0.7.x receives maintenance fixes.
The product portfolio and roadmap identify which repositories are active, maintained, frozen, paused, archived, harness-only, or reference-only.
The stable MFC client retains its authenticated /api/v1 automation surface. Controller forks and qBittorrent-compatible experiments are not forward product priorities.
Ħajja tal-proġett b'umoriżmu tekniku.
01
Kontroll aktar ċar tal-upload u n-netwerk
02
Żomm eD2K u Kad prattiċi
03
Provi qabel pakketti pubbliċi
Published releases
The first public Rust beta is available for experimental testing. It is the active development lane, but it is not production-ready.
The stable Windows package remains published with manifests, hashes, SBOMs, and diagnostics assets.
The MFC 0.7.3 release keeps its suite installer and aMuTorrent artifact. “Suite” describes that shipped bundle, not an active umbrella roadmap.
Capabilities, platform support, and network-safety claims must be proven by the repository and release that owns them.
Repos