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.
Breedband-uploadcontrole
Begrensde slotdoelen, recycling van zwakke slots, ratio-uitlezingen en seedingbediening houden snelle uploadverbindingen nuttig zonder het eD2K-uploadprotocol te wijzigen.
Binding, NAT en blootstellingsbeleid
Interface-bewuste binding, validatie van UPnP/NAT-mapping, HTTPS, allowed-IP-regels en aparte WebServer-bindinstellingen houden externe oppervlakken expliciet en testbaar. Binding is geen VPN-killswitch.
Moderne standaarden voor grote sessies
Grotere socketbuffers, queue/source-limieten, file buffering, timeout-standaarden, recursieve sharesynchronisatie, startup-cachewerk en long-path-richtlijnen richten zich op huidige Windows-systemen en grote bibliotheken.
eD2K en Kad blijven voorop
Server-, globaal en Kad-zoeken blijven de native basis, met Kad-identiteitstracking, afhandeling van slechte nodes, opschoning en timingwerk binnen de compatibiliteitsgrenzen.
REST- en controllerworkflows
Geauthenticeerde JSON-endpoints dekken overdrachten, zoekopdrachten, gedeelde bestanden, servers, Kad, logs, categorieën, uploads, statistieken, voorkeuren en gecontroleerd afsluiten vanuit vertrouwde lokale tools.
Bewijs vóór labels
0.7.3 is gepubliceerd met GitHub Actions-packaging, manifesten, SHA-256-bewijs, SPDX-SBOM's, diagnostics-assets en bootstrapper-hashbewijs.
Documentatie
Gidsen, API en 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.
- Overdrachten
- Zoekopdrachten
- Servers
- Kad
- Gedeelde bestanden
- Uploads
- Categorieën
- Logs
- Statistieken
- Voorkeuren
Product portfolio
Current lifecycle and support status for every eMuleBB repository.
eMuleBB Roadmap
Active Rust beta work, MFC maintenance, and bounded supporting lanes.
eMuleBB productgids
Setup, tuning, automatisering, release-bewust gebruik, tests en SBOM-bewijs.
Setup-gids
Installatiemodel, gedrag van het eerste profiel en praktische opstartnotities.
0.7.3 release-dashboard
Huidige RC-gates, geautomatiseerd testbewijs, SBOM-/pakketbewijs en gereedheidsregels.
Projectfolklore
Het muildierteam achter de P2P-werkplaats
01
Upload-muildiertemmer
Voorkomt dat breedband-uploadslots de staldeur intrappen en duwt de trage exemplaren weer in het gareel met een zeer officieel klembord.
02
Kad-pad-muildier
Draagt bootstrap-nodes, routeringstabellen en koppige eD2K/Kad-folklore over ruw netwerkterrein zonder de protocolkaart te verliezen.
03
Release-lastmuildier
Sleept pakketten, hashes, SBOM's, logs, live checks en net genoeg karakter door de poort voordat iets klaar wordt genoemd.
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-ecosysteem
Primaire repository's
emulebb-rust
active experimental beta and current product-development lane
emulebb
vlaggenschip-desktop-app en productbron
emulebb-tooling
roadmap, backlog, beleid, audits en referentiedocs
emulebb-build
build-, validatie- en release-orkestratie
emulebb-build-tests
native, Python-, UI-, REST- en 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- en validatielijn voor aMule-gebruikers
amutorrent
fork voor eMuleBB-beheer en controllerworkflows
qbittorrentbb
paused BitTorrent experiment retained for reference