spieglt/FlyingCarpet: README-based editorial guide

spieglt/FlyingCarpet describes itself in the README as "Cross-platform AirDrop. File transfer between Android, iOS, Linux, macOS, and Windows over ad hoc WiFi. No network infrastructure required, just two devices with WiFi chips (and optionally Bluetooth) in close range.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "Version 10 adds a Shared Network mode, for when you want to use a preexisting WiFi or wired network rather than create a hotspot.", the README says: Version 10 is a breaking change: devices running version 10 cannot transfer with version 9 or earlier , you'll get a version-mismatch message instead. Update Flying Carpet on every device you transfer between.. That establishes the project's stated boundary, not a production test.

The README's "Compilation Instructions:" section gives a useful starting point for deciding whether the project fits: For Linux, install dependencies. Ubuntu 20 example:. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Run cargo install tauri-cli to install Tauri.. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "Download for iOS:". The source evidence includes: Or search the App Store for "Flying Carpet File Transfer".. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: README 没有给出可直接复制的安装命令。 When the README contains no runnable command, this article does not invent one. Open its "Download for Android:" section and confirm system dependencies, default ports, and first-run initialization before using a public server.