Two public eD2K/Kad client lanes

Rust is the active beta. MFC is the stable maintenance line.

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

Try the Rust beta or use the stable MFC 0.7.3 client.

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.

Historical MFC 0.7.3 suite bundle
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

A smaller, explicit product portfolio

Active

emulebb-rust

The published beta is the only active product-development lane. It is experimental and not yet production-ready.

Stable

eMuleBB MFC

The published 0.7.3 Windows client continues as a long-term 0.7.x maintenance line for bugs and bounded low-risk changes.

Reference

Experiments stay labeled

qBittorrentBB is paused, aMuTorrent is frozen, TrackMuleBB is archived, and the server forks have bounded harness or reference roles.

Stable MFC capabilities

What the maintained MFC client already provides

These are shipped 0.7.3 capabilities, not a promise of renewed broad MFC development. Maintenance remains compatibility- and risk-bounded.

eD2K/Kad

Păstrează eD2K și Kad practice

eMuleBB păstrează fluxul clasic eMule și adaugă limite clare, diagnostic, REST API și dovezi de release.

Upload

Control mai clar pentru upload și rețea

Un eMule pentru upload rapid, biblioteci partajate mari, sesiuni Windows lungi și control local.

REST

Automatizare REST fără a înlocui aplicația desktop.

Automatizare REST fără a înlocui aplicația desktop. /api/v1, JSON, X-API-Key.

VPN

VPN/interface binding

Control mai clar pentru upload și rețea

Kad

Kad

Păstrează eD2K și Kad practice

Testing

Dovezi înainte de pachete publice

Dovezi înainte de pachete publice

Documente

Ghiduri detaliate și documente sursă.

01

Start with the Rust beta

Use the published beta for experimental testing and report reproducible issues in emulebb-rust.

02

Use MFC for the stable Windows lane

Version 0.7.3 remains the supported stable package while 0.7.x receives maintenance fixes.

03

Check repository lifecycle first

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.

  • Transfers
  • Searches
  • Servers
  • Kad
  • Shared files
  • Uploads
  • Logs
  • Preferences

Istorie de proiect cu umor tehnic discret.

Istorie de proiect cu umor tehnic discret.

Cartoon mule carrying an upload arrow and a clipboard. 01

Control mai clar pentru upload și rețea

Control mai clar pentru upload și rețea

Cartoon mule carrying connected Kad nodes across a trail. 02

Kad

Păstrează eD2K și Kad practice

Cartoon mule hauling release packages and checks. 03

Dovezi înainte de pachete publice

Dovezi înainte de pachete publice

Published releases

Use the release that matches the lane

Rust 0.1.0-beta.1

The first public Rust beta is available for experimental testing. It is the active development lane, but it is not production-ready.

MFC 0.7.3

The stable Windows package remains published with manifests, hashes, SBOMs, and diagnostics assets.

Historical Suite bundle

The MFC 0.7.3 release keeps its suite installer and aMuTorrent artifact. “Suite” describes that shipped bundle, not an active umbrella roadmap.

Evidence stays lane-specific

Capabilities, platform support, and network-safety claims must be proven by the repository and release that owns them.

Repo

Repozitoare publice.