chen08209/FlClash

Prefer this fork if you want an Android-oriented FlClash build with bundled model handling, Firebase support, and a custom release pipeline. Prefer upstream if you want the most neutral multi-platform distribution and less package-level divergence.

Choose this fork if your priority is a maintained Android-centered FlClash with startup and VPN fixes. Stay with upstream if you need the broadest cross-platform release and build workflow coverage.

Choose this fork if you care about its build/release maintenance and LM-Firefly-specific project setup. Choose upstream if you want the freshest app behavior and the broadest compatibility with upstream Android integration.

Prefer this fork if you want Russian Windows packaging and a more opinionated deployment setup. Prefer upstream if you want the latest fixes, broader release support, and less risk from fork-specific defaults.

Choose this fork if you value the Android/Windows fixes and workflow additions more than staying current with upstream. Avoid it if you want the latest FlClash releases, broad compatibility, or lower maintenance risk.

Prefer this fork if you want a maintained FlClash build with privacy-oriented logging changes and practical platform fixes. Stick with upstream if you need maximum feature parity or depend on the removed system time check.

Choose this fork if you want upstream FlClash with targeted Windows/UI/release adjustments. Choose upstream if you value the fuller default documentation, release workflow, and a more standard out-of-the-box experience.

Prefer this fork if automatic network-based policy switching is the main feature you want; stick with upstream if you want the broadest, most conservative FlClash baseline.