Four releases in one year. Who would have thought? aMule 3.2.0 is here, and this one comes with a clear message: please upgrade.

Security first​

This is, before anything else, a security release. We fixed 15 vulnerabilities that were responsibly reported to us, and 11 of them are also present in the old 2.3.3. Some of them could let other eD2k or Kad users, a device on your local network or anyone who can reach the remote-control port crash aMule, peek into its memory or reach files and programs outside it.

So if you are still on 2.3.x or on any earlier 3.x release, this is the one to install. A big thank you to the security researchers who took the time to find and report these problems. The changelog has the full list.

A smoother everyday experience​

Security is not the only thing that changed. Here is what you will notice when using aMule:

• No more freezes from a slow disk. If aMule uses a slow, busy or sleeping disk, you probably know the feeling: the GUI freezing for several seconds, sometimes over 20. That is gone. aMule now stays responsive, and uploads from your other disks keep going at full speed.
• Faster uploads, less CPU. Uploads are up to 16% faster and use about half the CPU at low speeds, and aMule no longer wastes time compressing videos and other files that are already compressed. Upload slots are also shared more fairly, because one machine can no longer grab most of them by pretending to be many users.
• New downloads start sooner. When you add or resume a download, aMule asks the servers for sources within seconds, instead of waiting up to 22 minutes for the next round.
• Search both networks at once. A new "All" search looks in eD2k and Kad at the same time.
• Less chat spam. The spam filter and chat CAPTCHA now protect amuled and every client connected to it, not just the desktop app, and they are on by default.
• Damaged files are caught and not spread. aMule remembers the result of Verify Local Data, stops offering parts it found damaged so others don't download bad data from you, and can recheck your shared files every few days if you want.
• A better server list. aMule can combine server lists from several sources you choose, and ignores a broken list instead of importing it.

A nicer desktop app​

The desktop app got plenty of love too. In the Windows and macOS packages you can now choose Light or Dark mode, or let it follow the system (after a restart). You can set bandwidth with sliders and an Mbit/s calculator. Preferences follow the order eMule users already know. On Windows and macOS, tray icons and speed bars look sharp at any screen scale, and on Linux the tray icon now shows the connection state.

The Web UI speaks seven languages​

The Web UI that ships with amuleapi is now available in Catalan, Italian, Dutch, Portuguese (Brazil) and Russian, on top of English and Spanish. Its translations live on Weblate with the rest of aMule, so if your language is missing, you can help.

And much more​

That's just the tip of the iceberg. This release also brings a long list of smaller improvements and bug fixes all over aMule. A few of our favorites:

• Change ports on the fly. TCP and UDP port changes apply without a restart, even from remote clients.
• Proxies and Tor. SOCKS5 proxies such as ssh -D and Tor work again, and SOCKS4/4a through Tor works for the first time.
• Delete files from disk. Remove completed files from disk right from Downloads and Shared Files, in aMule, amulegui and the Web UI.
• A failing disk no longer loses a download. If saving a download's progress fails, aMule keeps the previous progress file, so the download survives.
• Faster startup with big libraries. The splash screen shows up right away, and scanning large shared folders is many times faster.
• Magnet links and reverse proxies. amuleapi and the Web UI accept magnet links, and can now run behind a reverse proxy on a sub-path.
• amulecmd improvements. For example, you can download a search result without listing the results first.
• Smaller Windows packages. The portable zip went from 48.6 MB to 32.7 MB.

Before you upgrade​

For most people, upgrading is a drop-in: install it and carry on. But a few defaults changed for safety, so take a minute to read Before you upgrade, especially if you use aMule remotely (amulegui, amuleapi, amuleweb or your own scripts). The most important change is that remote clients can only set download and shared folders inside a list you choose on the aMule machine, so a leaked password no longer exposes your whole disk. The list starts empty, but folders you already use keep working.

As always, all the details are in the changelog, and you can get the new version from the download page.

Thanks to everyone who coded, tested, translated and reported bugs for this release. Happy sharing!

And here we are again, the third time this year!

We have an immense amount of work done here, thanks to everyone involved.

The largest release since the 3.0.0 rebirth: 893 merged PRs on top of 3.0.1. The headline is a new way to drive aMule - amuleapi, a REST + Server-Sent-Events daemon shipping a complete new Web UI that covers the same ground as the desktop GUI. Around it landed transfer-performance work that lifts real-world throughput, authenticated encryption for External Connect, a top-to-bottom modernization of the GUI list controls, media metadata that now travels end to end, searches that survive a restart, a dedicated Clients page, and a sweep of memory and CPU work across the daemon, the remote GUI and the API.

Upgrading is a drop-in. No config migration, and nothing an older build cannot read back: the new per-peer metadata rides in an appended clients.met trailer that every existing reader ignores (#902), and EC encryption is negotiated per session and off by default, so older amulegui / amulecmd clients keep connecting untouched (#714).

Full details in the changelog.

Don't forget to check our new website and documentation.

Hey, we're back again to set a new aMule all time record. Two releases in the same month. Don't be fooled by the .0.1 suffix. We have huge updates. Promise us your won't get spoiled!

Version 3.0.1 is out — the first point release after the 3.0.0 rebirth, and the first cut entirely on the new amule-org/amule repository. 147 merged PRs of post-launch work: a new IP2Country preferences panel, remote-GUI (amulegui) improvements over EC, smarter search, AICH request rate-limiting, a top-to-bottom WebUI / WebServer modernization and security pass, a Weblate-driven translation pipeline, and a one-click release process. No on-disk format or config changes — a drop-in upgrade from 3.0.0.

Full details in the changelog.

Don't forget to check our new website and documentation.

aMule is back after 5 years. Version 3.0.0 is out — the first release since 2.3.3 in February 2021. Full details in the changelog.

We also have a brand new website and documentation.

Hi! We are back. We went through hard times, we missed programmers and maintainers. There were doubts whether aMule could reemerge. People called aMule a dead project. But eD2k still has users, and those users need working software. So here we are — back to bring you the best eD2k client.

One unfortunate thing happened: Gonosztopi, one of aMule's most prolific devs, who has been the maintainer for many years, is missing. We have no news from him (we hope you are well, man!). And he was the only owner of the original GitHub repo. The other members left in amule-project do not have enough rights on the organization to properly manage the project. So we were forced to create a new one. New org, new repos, but the same folks.

You can find the new aMule site here. But you know that, since you are reading this :D

You will find everything there: the home page, complete documentation, download links, news and links to the source code.

Where to find us​

All development has moved to the new amule-org GitHub organization. Here is a quick reference:

Get involved​

Our community is growing fast! There are many ways to help:

• Report bugs: use the issue tracker — see the bug report guide for tips on writing a good report.
• Contribute code: browse the open issues and submit a pull request.
• Improve the docs: the documentation is open source too — find it at github.com/amule-org/amule-org.github.io.
• Translate: we depend upon translators to reach users around the world. If you are interested in collaborating, get in touch on GitHub.

Thank you all for keeping aMule alive!