eMuleBB 0.7.3-rc.1
Posted: 08.06.2026, 10:01
eMuleBB 0.7.3 RC1 is getting close - testers wanted
eMuleBB, also called eMule broadband edition, is back.
It is a maintained Windows eMule fork, not a new network and not a protocol fork. The goal is simple: keep stock-compatible eD2K/Kad behaviour, but make the client more suitable for today's broadband connections, large shared libraries, and long running Windows setups.
I am now getting close to the first public release candidate: 0.7.3-rc.1.
A lot of work has gone into this release. Not only new features, but also the boring quality work which matters in a client that may run for days or weeks: safer profile handling, long path support, better diagnostics, crash/hang evidence, package manifests, hashes, SBOMs, release test campaigns, and a proper CI/build system around the old codebase.
Some of the main work:
- stock-compatible eD2K/Kad behaviour kept as the baseline
- broadband-oriented defaults and upload/large-library improvements
- explicit profile support with -c, useful for clean testing
- trusted local REST API for automation and companion tools
- aMuTorrent and Arr/qBittorrent-compatible controller workflows
- Torznab/Prowlarr/Radarr/Sonarr integration work
- better diagnostics for network, disk, sharing, startup, shutdown, and REST
- WebServer/REST hardening, stricter request validation, safer auth boundaries
- many old stability bugs fixed around shutdown, background workers, sockets, lists, file writes, and malformed input
- release packages for x64 and ARM64, with GitHub evidence instead of "it built on my machine"
This is still eMule in spirit. The desktop app still owns the live eD2K/Kad state. The new API and controllers are there for trusted local automation.
Homepage:
emulebb.github.io
Releases/nightlies. You have to get the nightlies for now, until all gates will pass for RC1:
github.com/emulebb/emulebb/releases?q=nightly&expanded=true
Thanks to anyone willing to try it and report back. I am trying to get RC1 solid, not just "feature complete".
eMuleBB, also called eMule broadband edition, is back.
It is a maintained Windows eMule fork, not a new network and not a protocol fork. The goal is simple: keep stock-compatible eD2K/Kad behaviour, but make the client more suitable for today's broadband connections, large shared libraries, and long running Windows setups.
I am now getting close to the first public release candidate: 0.7.3-rc.1.
A lot of work has gone into this release. Not only new features, but also the boring quality work which matters in a client that may run for days or weeks: safer profile handling, long path support, better diagnostics, crash/hang evidence, package manifests, hashes, SBOMs, release test campaigns, and a proper CI/build system around the old codebase.
Some of the main work:
- stock-compatible eD2K/Kad behaviour kept as the baseline
- broadband-oriented defaults and upload/large-library improvements
- explicit profile support with -c, useful for clean testing
- trusted local REST API for automation and companion tools
- aMuTorrent and Arr/qBittorrent-compatible controller workflows
- Torznab/Prowlarr/Radarr/Sonarr integration work
- better diagnostics for network, disk, sharing, startup, shutdown, and REST
- WebServer/REST hardening, stricter request validation, safer auth boundaries
- many old stability bugs fixed around shutdown, background workers, sockets, lists, file writes, and malformed input
- release packages for x64 and ARM64, with GitHub evidence instead of "it built on my machine"
This is still eMule in spirit. The desktop app still owns the live eD2K/Kad state. The new API and controllers are there for trusted local automation.
Homepage:
emulebb.github.io
Releases/nightlies. You have to get the nightlies for now, until all gates will pass for RC1:
github.com/emulebb/emulebb/releases?q=nightly&expanded=true
Thanks to anyone willing to try it and report back. I am trying to get RC1 solid, not just "feature complete".