emulebb-rust
The published beta is the only active product-development lane. It is experimental and not yet production-ready.
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 | iexThe 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
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.
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.
Breitband-Upload-Kontrolle
Begrenzte Slot-Ziele, Recycling schwacher Slots, Ratio-Anzeigen und Seeding-Kontrollen halten schnelle Upload-Anschlüsse nützlich, ohne das eD2K-Upload-Protokoll zu ändern.
Binding, NAT und Expositions-Policy
Interface-bewusstes Binding, UPnP/NAT-Mapping-Validierung, HTTPS, Allowed-IP-Regeln und separate WebServer-Bind-Einstellungen halten entfernte Oberflächen explizit und testbar. Binding ist kein VPN-Kill-Switch.
Aktuelle Defaults für große Sitzungen
Größere Socket-Buffer, Queue/Source-Limits, File-Buffering, Timeout-Defaults, rekursive Freigabe-Synchronisierung, Startup-Cache-Arbeit und Long-Path-Hinweise zielen auf aktuelle Windows-Systeme und große Bibliotheken.
eD2K und Kad bleiben zuerst
Server-, globale und Kad-Suche bleiben die native Grundlage, mit Kad-Identitätsverfolgung, Bad-Node-Behandlung, Cleanup und Timing-Arbeit innerhalb der Kompatibilitätsgrenzen.
REST- und Controller-Workflows
Authentifizierte JSON-Endpunkte decken Übertragungen, Suchen, freigegebene Dateien, Server, Kad, Logs, Kategorien, Uploads, Statistiken, Preferences und kontrolliertes Herunterfahren von vertrauenswürdigen lokalen Tools ab.
Nachweise vor Labels
0.7.3 ist veröffentlicht – mit GitHub-Actions-Packaging, Manifesten, SHA-256-Nachweisen, SPDX-SBOMs, Diagnostics-Assets und Bootstrapper-Hash-Nachweisen.
Dokumentation
Guides, API und Release Notes
Start with the Rust beta
Use the published beta for experimental testing and report reproducible issues in emulebb-rust.
Use MFC for the stable Windows lane
Version 0.7.3 remains the supported stable package while 0.7.x receives maintenance fixes.
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.
- Übertragungen
- Suchen
- Server
- Kad
- Freigegebene Dateien
- Uploads
- Kategorien
- Logs
- Statistiken
- Preferences
Product portfolio
Current lifecycle and support status for every eMuleBB repository.
eMuleBB Roadmap
Active Rust beta work, MFC maintenance, and bounded supporting lanes.
eMuleBB Produktguide
Setup, Tuning, Automatisierung, release-bewusste Nutzung, Tests und SBOM-Nachweise.
Setup-Guide
Installationsmodell, First-Run-Profilverhalten und praktische Startnotizen.
0.7.3 Release-Dashboard
Aktuelle RC-Gates, automatisierte Testnachweise, SBOM-/Paketnachweise und Readiness-Regeln.
Projekt-Lore
Das Maultier-Team hinter der P2P-Werkstatt
01
Upload-Maultier-Bändiger
Hindert Breitband-Upload-Slots daran, die Stalltür einzutreten, und schiebt die langsamen mit einem sehr offiziellen Klemmbrett zurück in die Reihe.
02
Kad-Pfad-Maultier
Trägt Bootstrap-Nodes, Routing-Tabellen und sture eD2K/Kad-Folklore über raues Netzwerkgelände, ohne die Protokollkarte zu verlieren.
03
Release-Lastmaultier
Schleppt Pakete, Hashes, SBOMs, Logs, Live-Checks und gerade genug Attitüde durch das Gate, bevor irgendetwas als fertig gilt.
Published releases
Use the release that matches the lane
The first public Rust beta is available for experimental testing. It is the active development lane, but it is not production-ready.
The stable Windows package remains published with manifests, hashes, SBOMs, and diagnostics assets.
The MFC 0.7.3 release keeps its suite installer and aMuTorrent artifact. “Suite” describes that shipped bundle, not an active umbrella roadmap.
Capabilities, platform support, and network-safety claims must be proven by the repository and release that owns them.
eMuleBB Ökosystem
Primäre Repositories
emulebb-rust
active experimental beta and current product-development lane
emulebb
Flaggschiff-Desktop-App und Produktquelle
emulebb-tooling
Roadmap, Backlog, Policy, Audits und Referenzdocs
emulebb-build
Build-, Validierungs- und Release-Orchestrierung
emulebb-build-tests
native, Python-, UI-, REST- und Live-E2E-Tests
goed2k-server
fixed-purpose eD2K harness server with no product evolution planned
ed2k-server
reference fork for analysis and possible upstream contributions
aMule Windows builds
Windows-Build- und Validierungslinie für aMule-Nutzer
amutorrent
Fork für eMuleBB-Verwaltung und Controller-Workflows
qbittorrentbb
paused BitTorrent experiment retained for reference