Release v3.7.5

📦 Which file should I download?

• If you want a single file that runs everywhere, across OSes? choose APE (ffl.com / fflo.com).
• If you want platform-optimized size/perf, choose a native build. 🙂
• On Linux and unsure about glibc (or on musl)? -> APE ffl.com is the safest choice.

ℹ️ On the first run of a native build, the app performs an internal extraction step (by pyapp), so startup is temporarily slower once.
The install scripts pre-warm this step; manual downloads will see the one-time delay.
APE builds (ffl.com / fflo.com) are single-file and do not have this first-run warmup.

---

Windows (native)

• x86_64 → ffl-v3.7.5-x86_64-windows.zip
  Unzip to get ffl.exe.

Linux (native)

We publish two glibc baselines. Pick the highest baseline that does not exceed your system glibc:

• glibc 2.39+ — smaller & faster

  • ffl-v3.7.5-manylinux_glibc2.39-x86_64-linux.tar.gz
  • Best for newer distros (e.g., Ubuntu 24).

• glibc 2.28+ — widest compatibility

  • ffl-v3.7.5-manylinux_glibc2.28-x86_64-linux.tar.gz
  • Works on older distros (e.g., Ubuntu 20); larger due to additional internal linking.

⚠️ If your system is musl-based (e.g., Alpine) or you’re unsure about glibc, prefer APE ffl.com.

macOS (native)

• Apple Silicon (arm64) → ffl-v3.7.5-aarch-darwin.tar.gz
• Intel (x86_64) → ffl-v3.7.5-x86_64-darwin.tar.gz

The archive unpacks to a single ffl binary.

🧰 APE (cross-platform single file, zero external deps)

• ffl.com — Single-file build that runs natively on Linux, macOS, Windows, FreeBSD, OpenBSD 7.3, NetBSD, BIOS, and Android (Termux).
• fflo.com — Alternative APE build that is exactly aligned with the open-source repo (no additional/proprietary addons).
  As a result, features that require closed-source components—such as upload to server (e.g., --upload)—are not available.

For a deeper comparison between native and APE, see the README’s notes.