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

保持 eD2K 與 Kad 實用

eMuleBB 保留經典 eMule 流程,並加入明確限制、診斷、REST API 與 release 證據。

Upload

更清楚的 upload 與網路控制

面向高速 upload、大型共享庫、長時間 Windows 工作階段與本機控制器流程的 eMule。

REST

不取代桌面應用程式的 REST 自動化。

不取代桌面應用程式的 REST 自動化。 /api/v1, JSON, X-API-Key.

VPN

VPN/interface binding

更清楚的 upload 與網路控制

Kad

Kad

保持 eD2K 與 Kad 實用

Testing

公開套件之前先有證據

公開套件之前先有證據

文件

詳細指南與來源文件。

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

專案裡的技術冷幽默。

專案裡的技術冷幽默。

Cartoon mule carrying an upload arrow and a clipboard. 01

更清楚的 upload 與網路控制

更清楚的 upload 與網路控制

Cartoon mule carrying connected Kad nodes across a trail. 02

Kad

保持 eD2K 與 Kad 實用

Cartoon mule hauling release packages and checks. 03

公開套件之前先有證據

公開套件之前先有證據

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.

倉庫

公開倉庫。