Skip to main content

Changelog

Every notable change of njMule, newest first, as kept in the repository's CHANGELOG.md. The format follows Keep a Changelog and the versions Semantic Versioning.

All notable changes to this project are documented here. The format follows Keep a Changelog and the project uses Semantic Versioning.

[Unreleased]​

[0.3.1] - 2026-11-03​

Fixed​

  • Uninstalling closes njMule if it still runs, once it has saved its state, rather than leaving it running: the Windows installer, the macOS disk image's Uninstall njMule (which asked to quit it first) and the removal of the deb and rpm packages.

[0.3.0] - 2026-11-01​

Added​

  • Delete takes the search highlighted out of the list of the searches typed before.

Fixed​

  • The web interface frees its port as soon as it stops: changing its settings no longer fails, now and then, to start it again on the same port.
  • Kad whose UDP port another program holds at start tries the port again every 10 seconds and starts once it is free, with a banner saying so, rather than staying off until started by hand.
  • The browser's own suggestions, or the desktop window's, no longer cover the searches typed before, the command palette's list or the boxes of the messages.
  • The Type column of the search results and of a client's shared files names the type in the interface's language, such as Archive or Program, rather than the network's code (Pro).
  • The Stop icon is a filled square, as on a player: the empty one looked like a check box.
  • More results, as the search's More button is now called in every language, is enabled only while the server holds more results, rather than doing nothing when pressed; a search that waits for them no longer shows as running.

[0.2.0] - 2026-11-01​

Added​

  • One interface for the desktop app and the web interface (njmule-ui, Vue 3 and TypeScript), which reaches njMule only through its remote-control API, and a desktop window for it built with Tauri 2 (njmule-desktop) that starts the native engine.
  • In that interface: the program's own icon beside every file name in the desktop window, Ctrl+V to add the eD2K links on the clipboard in Transfers, Enter to download the search results chosen, the downloads reordered by dragging them, Browse for the preview player and the event programs, and the flag and code of each source's country under an opened download.
  • The remote-control API answers what the interface needs: the folders and network interfaces of njMule's computer, the check of a folder and of a search, the defaults of the preferences and whether each password is set, the first start's questions, the web interface's settings and API token for the desktop window, the data of a download for a player, server.met and nodes.dat files sent from a browser, the country of servers and Kad contacts, the searches and server list addresses typed in the eMule imported, and, for the desktop window, the ed2k links and the start at login of njMule's computer.
  • --webui-guest-password-file and --webui-no-guest set or remove the web interface's guest on a headless njMule, and the Synology wizard and the Docker Compose file offer a guest password.

Changed​

  • The desktop packages carry the new desktop window in place of the JavaFX app, beside the headless engine, which is also the command line: the MSI, the deb, rpm and tar archives and the macOS app. The window shows the interface in the system's web view: WebView2 on Windows, WebKit on macOS, and WebKitGTK 4.1, which the deb and rpm packages depend on, on Linux.
  • The web interface is the desktop app's interface in the browser: the same screens, menus, dialogs and colours, with the browser's ways for what needs njMule's computer, such as folders typed.
  • The country of other clients, servers and Kad contacts is shown by default (geo.countries); its database is fetched as soon as the option is on.
  • Changed from the desktop window, the web interface follows its settings at once, without a restart.
  • The browser only shows the web interface's own settings: its host names and the guest password are set, like the rest, in the desktop app on njMule's computer.

Removed​

  • The JavaFX desktop app and the former browser app of the web interface, which the one interface replaces, with their native build and their dependencies (OpenJFX, AtlantaFX, RichTextFX).

[0.1.3] - 2026-10-31​

Fixed​

  • The desktop app's Updates window shows the note on what the check sends above its buttons, as a readable paragraph, and is as wide as the buttons need, in every language.
  • Firewalled on Kad with a LowID, njMule keeps the firewalled Kad sources that have a buddy and take uTP, and meets them through the routers, instead of leaving them out before the rendezvous.

[0.1.2] - 2026-10-27​

0.1.1 was tagged but its packages were never released, only its Docker image: the Windows service did not stop cleanly when uninstalled (see Fixed). This version carries the changes of 0.1.1 too.

Added​

  • The notes of each release link VirusTotal's report of every package.

Fixed​

  • njmule --service=uninstall stops the Windows service before it takes its account's rights away, so that njMule saves and stops, instead of being ended a minute later without saving.

[0.1.1] - 2026-10-27​

Added​

  • A documentation website (website/, Docusaurus) for GitHub Pages: a user guide for the desktop app, the web interface and servers, a developer guide and the remote-control API's reference, in the brand's colours, with screenshots taken by the build; its text is under CC BY-SA 4.0.

Fixed​

  • With --webui-password-file at each start, as in the Docker image, only the password is set again: LAN access, host names, trusted proxies and the API keep their saved values, such as the host names added in the browser, unless the command line gives them.
  • njmule --service=install takes --webui-lan and the other web interface options without a password option, keeping the service's password, and restarts a service that runs so that it takes them; the MSI's NJMULE_WEBUI_LAN=1 opens the service's web interface to the network.
  • The update panel of the web interface offers Download and install where njMule installs itself, tells how to install the new version for each kind of installation (the package manager's command, the Docker image to pull, the Synology Package Center) and no longer offers a download that cannot work.
  • Kad tells that clients reach us through the routers (uTP, QUIC) only where we take such connections, no longer with obfuscation required, and follows a change of obfuscation or proxy without a restart.
  • A Kad search no longer drops every result when the complete sources filter is set: Kad counts none, so the filter is left out there; the filters' note says so instead of claiming that Kad ignores size and type.
  • A download waiting for disk space offers to pause instead of a resume that did nothing, and its note says that it goes on by itself once there is room.
  • A part found corrupt is told in the app's log too, not only in the log file.
  • The dialog that adds links finds them inside other text too, as it says, and its paused box wins over the option that adds downloads paused; the remote-control API takes paused when it adds downloads.
  • A desktop window on a remote njMule marks spam through it, tells that a preview and the folders of the other njMule are on its own computer instead of opening this computer's, and turns Open Folder and Open Incoming Folder off.
  • A desktop app started while a headless njMule runs on the same profile says that the links went to it, instead of closing without a word.
  • njmule --restore-links, which the Windows uninstaller runs and now the macOS one too, also turns the start at login off; njmule --remove-profile does both before it deletes the profile, which keeps the program the ed2k links go back to. A Linux start at login whose program was removed is skipped.
  • The import no longer copies eMule files njMule does not read (statistics.ini, AC_BootstrapIPs.dat, AC_IPFilterUpdateURLs.dat), and the first start no longer says that it takes eMule's statistics over.
  • On Windows the completed downloads go to the Downloads folder where the user moved it.
  • The Ports card tells what the router answered through UPnP instead of whether UPnP is on, and the UDP port while Kad runs, which listens on it; the port test is Test Ports everywhere.
  • In the options of the desktop app a long name wraps instead of running under its control, and each row of the Proxy and Notifications pages is marked and reset by what it shows, no longer by the whole page.
  • The options of the web interface name the proxy's port, user and password and the mail password as such, without a placeholder in the text; its sign-in page names the password field in sight.
  • On a phone the details of a download in the web interface show only once one is chosen, after the list instead of over it.
  • The smileys :-p, :-O, :-o, :-| and :-* show as emoji too.
  • The macOS app carries the license and the notices, as the other packages do.

Removed​

  • The Use secure identification and Use the credit system switches: njMule always uses both and never read them. Their keys stay in njmule.properties.

Security​

  • The profile of the Windows service, %ProgramData%\njMule, is closed to the other users of the computer before its web interface password is written; a service installed before gets it at its next njmule --service=install.
  • njmule.properties, which holds the proxy and mail passwords, and its backup are readable by their owner only on Linux and macOS.
  • Our public IPv6 address is no longer told to other clients and to Kad while a proxy carries the connections.
  • E-mail and web hook notifications go through the proxy of the preferences and from the network interface chosen, and are not sent while that interface is gone.

[0.1.0] - 2026-10-26​

The first release of njMule, a new client for the eD2K and Kad networks written in Java 25, which works with eMule and the other clients of the network.

Added​

eD2K​

  • Servers kept in server.met, starting from the list shipped with njMule and updated from server.met addresses: static servers, priorities, ping times, file limits and versions, names asked for over UDP, dead servers dropped after failed attempts. Login with a HighID or a LowID, plain or obfuscated, two servers tried at once, a lost connection replaced at once, and connection at start.
  • Searches on the connected server, on every known server over UDP (encrypted where the server takes it) and on Kad, or picked automatically, with eMule's parameters (type, size, availability, complete sources, extension). Results are merged by hash with every name their sources give, their media details and the AICH root Kad tells, show what we did with them (downloading, shared, downloaded, cancelled) and lead to related files where the server supports it.
  • A spam filter for search results that learns from the files marked as spam (their names, similar names, size and the servers that gave them), kept in eMule's SearchSpam.met; the search tabs left open come back at the next start (StoredSearches.met) and the words searched are offered again.
  • Clients: a hello naming njMule and its version, secure identification (RSA-384) and credits in clients.met, source exchange (versions 1 to 4), re-asks over UDP, A4AF sources moved between downloads by themselves or by hand, the shared files of a client browsed (ours shown to everybody, friends or nobody), file comments and ratings, and chat with CAPTCHA, a friends list, the friend slot and spam filters.

Kad 2​

  • A Kad 2 node: routing table, iterative lookups, keyword, source and note searches and publishes, and an index of what others publish to us, kept across restarts; publishing spares loaded nodes and takes turns between keywords.
  • TCP and UDP firewall checks. Firewalled, njMule takes a buddy and is called back through it, or directly over UDP; open, it serves a firewalled node as its buddy.
  • Joining from the contacts shipped with njMule, a nodes.dat from an address or a file, a known node or the Kad clients met over eD2K; the status bar estimates the users and files of the network.
  • Lookups trust no single node: a node must prove its id at its address, and a contact only one node tells of is asked last.

Downloads​

  • Part files in eMule's .part.met format: the rarest parts first, parts already begun preferred, every part checked against its hash, bad blocks repaired from AICH recovery data or as soon as the bad block comes again, sources that send corrupt data banned, and an endgame that asks the last blocks of more than one source.
  • Sources from links, from the connected server and the others over UDP, from Kad, source exchange and by hand, at IPv4 or IPv6 addresses; the best ones are remembered across restarts, and each shows what it does as a coloured dot.
  • Priorities (Low, Normal, High, Auto), categories with an incoming folder, a tint and name patterns of their own, pause, stop and resume, a paused download started when another ends, new downloads paused if asked, downloads that wait while the temp disk is short of space, preview with the first and last parts first, and file names taken from the sources, tidied or typed.
  • Cancelling asks first and can be undone; completed downloads stay listed until cleared; downloads that receive nothing for a number of days can be deleted by themselves (off by default).
  • ed2k links pasted, dropped on the window, given on the command line, opened in a browser or copied in another program (off by default) become downloads, shown first when several come at once or one is known already.

Uploads and sharing​

  • Shared folders, with their subfolders if asked, watched for new and changed files and hashed once into known.met and known2_64.met. Personal and system folders and the files other programs keep beside their work are never shared, and sharing a drive or a personal folder asks first.
  • An upload queue scored by waiting time, credits and file priority (Very low to Release, or Auto), slots by the upload limit, compression only where it helps, bans for clients that ask too often or abuse their slots, and statistics for each shared file.

Connections​

  • IPv6 alongside IPv4: our IPv6 address in the hello, the Kad publishes and source exchange, sources reached directly over IPv6, and the router's IPv6 firewall opened to our ports.
  • Firewalled clients connect to each other through their routers, over QUIC (TLS 1.3) or uTP.
  • Port forwarding with UPnP, NAT-PMP or PCP, and a port test through the server and Kad nodes; new ports apply without a restart.
  • SOCKS 4/5 and HTTP CONNECT proxies, with UDP through a SOCKS 5 relay, and binding to one network interface, such as a VPN, which keeps njMule offline while it is gone.
  • An IP filter from ipfilter.dat, PeerGuardian or P2B files, with levels, a whitelist and up to 16 lists updated from the web; LAN addresses are left out unless allowed.
  • A weekly scheduler for the speed limits, the connections and the categories.

Coming from eMule​

  • Import of an eMule profile, which is only read: preferences, servers, Kad contacts, known files, shared folders, categories, the IP filter, friends, comments, spam marks and open searches, each file checked first and a manifest kept of what became of it; on request the identity (user hash, credits, Kad id) and copies of the unfinished downloads. Offered at the first start when an eMule is found, and from the desktop and web apps and njmule --import-emule (with --dry-run).
  • eMule's files read and written as eMule does: server.met, known.met, .part.met, clients.met, emfriends.met, nodes.dat, StoredSearches.met, SearchSpam.met and the others.

Desktop app​

  • A JavaFX app with AtlantaFX themes (Nord light or dark by default, following the system), the system's colours under Windows high contrast, text and marks held to WCAG AA contrast in every theme, and its controls named for screen readers; its own line icons and Manrope titles.
  • 36 languages with eMule's translations, mirrored for Arabic, Persian and Hebrew, with the sizes, rates and durations in each language's units.
  • A sidebar of places and a top bar with the rates, the state of eD2K and Kad and a command palette (Ctrl+K) that also searches the network or takes eD2K links: transfers with chips, sources under each download and a details pane; searches in tabs with filters; shared files by folder; conversations and friends; the network with its servers, Kad, log and our info; statistics; options on thirteen pages with a search.
  • A first-start wizard, an icon in the Windows notification area with a small status window and speed sliders, the ed2k link handler on Windows, Linux and macOS, start at login and keeping the computer awake while files are transferred (both off by default), and a window onto another njMule, on a NAS or a server, through its API.

Web interface​

  • The desktop app in the browser (Vue 3, Element Plus), in its 36 languages and with a layout for phones: transfers, searches, shared files, messages, network, statistics, settings and the import.
  • Behind a password (PBKDF2) with session cookies, form tokens, origin and host checks, a login lockout and a strict Content-Security-Policy; on this computer only unless asked, answering to the host names listed and through reverse proxies, also under a path, and to a guest with a password of its own who can only look.

Remote control and command line​

  • A JSON API under /api/v1 with the engine's events as server-sent events, behind a token, described by an OpenAPI 3.2 document that also routes and checks every request.
  • njmule runs the engine headless or does one task (search, download, share, hash, import, exit the running njMule, look for updates), and njmule --remote drives a running njMule, here or on another computer.

Statistics and notifications​

  • Rates over the last ten minutes, hour or day, session and all-time totals with the protocol's overhead, a tree of every figure, the history of the clients met (90 days) and, optionally, the country and flag of each client (IP Geolocation by DB-IP).
  • A completed or failed download, a chat message or a temp disk short of space, told by e-mail (always encrypted), a web hook (ntfy, Gotify), a program of the user's or a sound (off by default).

Packages and updates​

  • Native executables that need no Java: for Windows an MSI, per user or for every user with the Windows service, and a zip (arm64 through emulation); for Linux x64 and arm64 deb and rpm packages with a systemd user unit and archives, and a static headless executable for any x64 Linux; for macOS a disk image for Apple silicon; a Docker image for amd64 and arm64; a Synology DSM 7 package. A portable.flag file keeps the data beside the programs.
  • Uninstalling can delete the profile too; the completed downloads always stay.
  • njMule tells when a new version is out, and downloads and installs it where it may replace itself, trusting only update information signed with a key built into it; each release carries a signed SHA256SUMS, build attestations and a CycloneDX bill of materials.
  • The configuration is backed up as a dated zip at each exit and once a day.

Security and robustness​

  • Size-limited parsers for everything read from the network and from disk, bounded send queues, and crash-safe saves that never leave a file missing or half written.
  • Abuse held back: limits on the connections of an address and on new connections, bans for clients that ask too often, hold idle slots, send corrupt data or claim another client's identity, and credits, slots and the friend slot bound to the proven identity.
  • Names from the network lose their control characters and direction overrides, file names are made safe for every file system, and the files holding keys and settings are readable by their owner only (Linux and macOS).

For contributors​

  • A Gradle build with locked and verified dependencies, Spotless, Checkstyle, Error Prone, SpotBugs and JaCoCo; golden vectors from an independent implementation, property-based tests, a test kit of fake servers and peers, JMH benchmarks, and REUSE-compliant licensing.