Folder Camera Receiver 1.1.0

Folder Camera Receiver 1.1.0 adds a headless mode and a local pairing API, and keeps the receiver reachable when the PC changes network.

• Headless mode: --headless runs the receiver with no window and no tray icon. It uses the same state folder, single-instance lock and --state/--root/--bind/--port options as the desktop app, and stops cleanly on SIGINT/SIGTERM.
• Local control API: other apps on the same PC can ask the receiver for a fresh pairing code and draw the QR themselves. The loopback listener (127.0.0.1 only, bearer token from desktop-instance.json, browser requests refused) gains GET /status and POST /pairing. It cannot revoke phones, change folders or stop the receiver. See docs/desktop-receiver.md.
• Following the PC's address: with automatic binding, the receiver now moves to the PC's new LAN address by itself (the CLI checks every 10 s, the desktop app every 5 s), keeping its certificate, identity and port. A stalled transfer can no longer block that restart.

Existing receiver identities, paired phones and saved photos are kept.

Downloads:

• Windows x64 and native ARM64: per-user MSI installers, with the standard WebView2 runtime.
• macOS Intel and Apple Silicon: DMG applications.
• Linux x64 and ARM64: AppImage applications. The WebKitGTK 4.1/GTK 3 system libraries are required; the tested Linux baseline is Ubuntu 24.04.

Built with Deno Desktop 2.9.7. Windows installers are unsigned and macOS apps have an ad-hoc signature, without Apple notarization.

Automated acceptance runs the 24 receiver tests on every target, launches the rendered native GUI and requires a clean exit, then repeats startup from the actual AppImage/MSI/DMG. The Linux x64 AppImage was also run headless on a Fedora 44 PC, where GET /status and POST /pairing returned a valid code. See the accompanying checksums and source/CI manifest.

Android 1.0.4, released separately, pairs even when a VPN such as Tailscale is on, and says why a pairing failed.

Source and license: GPL-3.0-or-later.