eMule broadband edition, compactly known as eMule BB, is a power-user eMule line for modern Windows systems, fast upload links, large shared libraries, and trusted local automation.

It keeps the familiar stock eD2K/Kad protocol and classic eMule workflow: servers, Kad search, shared files, upload queues, categories, known clients, and long-running desktop control. Around that foundation it adds broadband-aware upload policy, safer large-library operation, authenticated REST automation, and release validation that can be inspected.

The first beta release line is planned as 0.7.3. It is not yet released.

• named interface binding for IPv4-capable adapters
• explicit separation between interface targets and address overrides
• live validation profiles that bind the P2P stack through a VPN interface
• WebServer/REST exposure controlled by existing bind, HTTPS, and allowed-IP behavior
• external VPN kill-switch design kept separate from the app instead of being over-claimed as built in

• higher half-open and connection burst defaults for modern Windows
• higher per-client upload cap for broadband slots
• larger UDP receive and TCP send buffers
• SSD/NVMe-friendly file buffering defaults
• larger queue and source limits for busy sessions
• shorter, fixed timeout defaults where old values were too conservative
• advanced Tweaks exposure for important fixed limits

• configured upload slot target instead of legacy high-slot drift
• finite upload budget model for modern broadband links
• weak-slot recycling with warm-up, cooldown, and queue refill behavior
• session transfer and session time rotation controls
• large socket send buffer and disk prefetch behavior tied to slot targets

• all-time and session ratio readouts for shared files and upload decisions
• low-ratio file boost controls for stricter seeding
• optional LowID score deboosting
• cooldown visibility in upload and queue lists
• upload queue actions exposed through desktop and REST-oriented workflows

• recursive share sync work
• startup cache and known.met lookup improvements
• long-path guidance and follow-up work for deep Windows libraries
• stable sorting and large-tree UI responsiveness work
• share-ignore and filename hygiene tracked as product behavior

• SafeKad and FastKad work in the current Kad paths
• Kad identity tracking and bad-node handling without protocol incompatibility
• bounded cleanup for long-running Kad state
• response-time sampling for Kad timeout behavior
• standalone TCP error-flood protection for pre-handshake abuse
• peer friend, ban, unban, source, upload, and queue operations exposed through REST

• UPnP/NAT mapping behavior kept in release validation
• PCP/NAT-PMP backend work tracked in the current code line
• WebServer HTTPS and allowed-IP behavior inherited by REST
• bind-policy and socket adversity gates included in beta proof
• no weakening of native eMule exposure rules for controller adapters

eMule BB exposes an authenticated JSON REST API from the existing WebServer listener for trusted local controllers. The /api/v1 surface is designed around native eMule behavior, not a generic downloader model.

Covered areas include:

• transfers and transfer details
• searches and search-result downloads
• servers and Kad controls
• shared files and shared directories
• uploads and upload queue actions
• categories, logs, statistics, preferences, and app status
• qBittorrent-compatible subset routes where Arr clients need them
• Torznab-compatible search adapter behavior for Prowlarr

The controller direction includes aMuTorrent-style workflows and practical Prowlarr, Radarr, and Sonarr validation lanes while keeping the native desktop app in charge.

The workspace is built around evidence, not guesswork:

• native tests
• Python harnesses
• REST contract and smoke checks
• UI automation
• live eD2K/Kad scenarios
• aMuTorrent and Arr integration validation
• malformed request and WebServer hardening checks
• network socket, UDP, WebSocket, HTTPS, bind-policy, and NAT adversity gates
• x64 and ARM64 package rehearsal evidence before public tagging

• prepare the first beta, 0.7.3
• keep public release status honest until the beta gates are complete
• finish REST completeness and typed error behavior
• validate UI, REST, eD2K/Kad, and controller scenarios
• keep VPN/interface binding, NAT, and WebServer exposure behavior tested
• improve user-facing setup, tuning, automation, and troubleshooting docs

Start with the public site and the maintained source docs:

• emulebb.github.io - concise product overview and guide links
• Product guide - setup, tuning, automation, and release-aware use
• Setup guide - install model, first-run profile behavior, and startup notes
• Network guide - eD2K, Kad, binding, UPnP, firewall, and diagnosis
• Sharing guide - shared directories, monitored shares, large libraries, and policy files
• Downloads and search guide - search modes, result trust, categories, and file workflows
• Controllers and REST guide - trusted local controllers and automation boundaries
• REST API contract - authenticated JSON control surface
• REST adapter contracts - qBittorrent-compatible and Torznab adapter surface
• Troubleshooting guide - symptom-led checks for network, sharing, and automation issues
• 0.7.3 release dashboard - current planned beta gates, evidence, and readiness rules

• eMule - desktop app and product source
• eMulebb-setup - reproducible workspace setup
• eMule-build - build, validation, and release orchestration
• eMule-build-tests - native, Python, UI, REST, and live E2E tests
• eMule-tooling - roadmap, backlog, policy, audits, and reference docs
• emulebb.github.io - public product page

• Keep stock eD2K/Kad protocol compatibility as the default.
• Improve the classic desktop app instead of replacing it with a rewrite.
• Make power-user features observable, testable, and documented.
• Treat REST and controller support as product features.
• Prove behavior with automated and live testing before calling a beta ready.