This is the home of eMuleBB, the compact public name for eMule broadband edition.

eMuleBB is its own product: a broadband-focused Windows eMule line for people who still care about eD2K, Kad, rare files, deliberate sharing, long-running desktop sessions, and local automation that respects native eMule behavior.

The organization around it is a practical P2P workshop. We build the desktop client, the release and test machinery, the public documentation, controller workflows, Windows build tracks for adjacent tools, and exploratory eD2K/Kad projects that keep the protocol knowledge sharp. More is coming. Stay tuned.

The first public release candidate, 0.7.3-rc.1, is published on GitHub Releases with matching suite bootstrap and aMuTorrent controller packages.

RC1 is published on GitHub Releases. Choose one install path:

Use this path when you only want the eMuleBB desktop app.

1. Open emulebb-v0.7.3-rc.1.
2. Download emulebb-0.7.3-rc.1-x64.zip.
3. Extract the ZIP into a new version-specific folder, for example C:\Apps\eMuleBB\0.7.3-rc.1.
4. Run emulebb.exe.

Keep each version in its own application folder. Use a backed-up or disposable profile for RC testing and support testing.

Use this path when you want eMuleBB plus aMuTorrent, Prowlarr, Radarr, and Sonarr integration out of the box.

irm https://github.com/emulebb/emulebb/releases/download/emulebb-v0.7.3-rc.1/Bootstrap-eMuleBBSuite.ps1 | iex

The bootstrapper downloads and verifies the matching release package, extracts the suite installer, resolves the matching aMuTorrent RC1 package, and starts the install flow. Advanced options and verification details are in the Setup guide.

All RC1 builds and packaging happen in GitHub Actions and are published through GitHub Releases. The release includes ZIPs, manifests, SHA-256 evidence, SPDX SBOMs, diagnostics packages, the suite bootstrapper, and the bootstrapper SHA-256 asset. The bootstrapper verifies package hashes from the release manifests before installing.

We are open for testers now. Use the published RC1 packages if you want to help shake out real Windows profiles, large libraries, controller/API workflows, package contents, startup/shutdown behavior, and public-network regressions.

Use a disposable or backed-up profile when testing RC builds. Report crashes, freezes, broken packages, UI regressions, REST/controller problems, and repeatable live-network issues in emulebb/issues.

Useful reports include the package name, architecture, Windows version, profile type, exact launch command, repro steps, logs, diagnostic snapshots, and dumps for crashes, hangs, or memory-growth cases.

eMuleBB keeps the familiar desktop workflow at the center: servers, Kad search, shared files, upload queues, categories, known clients, and long-running control. Around that foundation it adds broadband-aware upload policy, safer large-library operation, authenticated REST automation, performance-minded defaults, and release evidence without creating an incompatible network fork.

The eMuleBB ecosystem includes an aMuTorrent fork focused on managing eMuleBB and validating controller-style workflows. It sits beside the desktop app instead of replacing it, and it keeps the native /api/v1 contract as the source of truth.

We also provide Windows build and validation work for aMule and MiniUPnP/miniupnpc. Those are ecosystem builds and distribution artifacts for users who want these tools in the same Windows P2P workflow.

The exploratory side includes the goed2k fork/server work and a full headless Rust eD2K/Kad client direction inside the p2p-overlord suite. This is where deeper protocol, automation, and server-oriented P2P ideas can mature without pretending every experiment is already a stable end-user product.

eMuleBB is being built as a tested desktop product, not a patched source tree. Public claims stay tied to evidence: hosted fast CI, native tests, REST contracts, UI and resource checks, live eD2K/Kad scenarios, controller lanes, package provenance, GitHub Actions release packaging, GitHub Releases assets, SBOMs, SHA-256 hashes, manifests, diagnostics packages, and explicit operator gates.

Performance work is treated the same way. Claims are tied to concrete operating surfaces: upload-slot policy, queue/source limits, socket and file buffers, startup behavior, large shared libraries, long paths, controller responsiveness, and long-running Windows sessions.

The result is a focused P2P organization: conservative where compatibility matters, aggressive about validation, and serious about making classic eMule usable on modern broadband systems.

• emulebb - flagship desktop app and product source
• emulebb-setup - reproducible workspace setup
• emulebb-build - build, validation, and release orchestration
• emulebb-build-tests - native, Python, UI, REST, and live E2E tests
• emulebb-tooling - roadmap, backlog, policy, audits, and reference docs
• amutorrent - fork used for eMuleBB management and controller workflows
• goed2k-server - eD2K server work for deterministic tests and ecosystem services
• p2p-overlord-agents and p2p-overlord-be - exploratory headless/server-oriented P2P work

• aMule - Windows build and validation track for aMule users
• emulebb-miniupnp - Windows build and validation track for MiniUPnP/miniupnpc

• eMuleBB is the product identity; eMule broadband edition is the full product name.
• Keep stock eD2K/Kad protocol compatibility as the default.
• Improve the classic desktop app instead of replacing it with a rewrite.
• Treat REST and controller support as product features.
• Make Windows packages, build evidence, and release gates inspectable.
• Keep exploratory P2P work visible, useful, and clearly labeled.
• Sell the expertise by proving the work.