eMuleQt

Post Reply
User avatar
hooligan
Posts: 20227
Joined: 11.04.2021, 19:26
Has thanked: 178 times
Been thanked: 420 times
Sweden

eMuleQt

Post by hooligan »

Image

Features
  • ED2K & Kademlia — Server-based and decentralized DHT networks for maximum source availability
    Usenet — NZB downloading with multi-provider failover, PAR2 repair and unpacking, plus newznab indexer search and feeds that queue new releases on their own
    Cross-Platform — Runs natively on Windows, macOS, and Linux
    Daemon/GUI Split — Headless daemon (emulecored) + Qt GUI (emuleqt), connect remotely or run on a server
    IPv6 — Dual-stack ED2K across clients, servers, source exchange and links, so IPv6-only and CGNAT users take part as full peers
    Encrypted HTTP Cache — When several peers want the same part, upload it once and hand the rest an encrypted URL
    Automatic Port Mapping — PCP, NAT-PMP and UPnP raced at startup, graded on whether your exact port was really granted
    Protocol Obfuscation — TCP/UDP encryption enabled by default
    AICH Verification — Chunk-level integrity checks with automatic corruption recovery
    Queue & Credit System — The proven eMule reward system for fair sharing
    Built-in Web Server & REST API — Remote control from a browser, plus a JSON API and CLI for scripts
    Advanced Search — Expression-based queries across multiple networks
    IRC Chat & Messages — Built-in IRC client and peer-to-peer messaging
    IP Filtering — Dynamic blocklists with automatic updates
    Media & Archive Preview — Preview video files and browse archives before download completes, on ED2K and on Usenet
    Statistics — Real-time bandwidth graphs, connection metrics, and Kademlia visualization
    Nothing Is Lost on Restart — Download sources, upload-queue positions and statistics history all survive a restart
    Internationalization — 9 languages out of the box
    Read more about what makes eMule Qt different.


Roadmap
  • NAT Traversal — Many users sit behind NATs and firewalls that prevent incoming connections, limiting them to “Low ID” status and reduced source availability. We plan to implement NAT traversal based on the work by DavidXanatos.
    QUIC Transport — We are exploring QUIC (the transport protocol behind HTTP/3) as an alternative to TCP for peer connections. QUIC offers built-in encryption, multiplexed streams without head-of-line blocking, faster connection establishment (0-RTT), and better performance on lossy networks. It also traverses NATs more gracefully than TCP since it runs over UDP. This will allow previous “Low ID” clients to connect with each other seamlessly without relay/buddy.
GitHub

Download eMuleQt v0.5.3


Post Reply