AppFlowy-IO/AppFlowy

Choose upstream unless you specifically need this fork's custom build/localization work or are already committed to its altered behavior. This fork looks like a specialized, stale derivative with meaningful merge debt and at least one removed feature, not a safer general-purpose AppFlowy base.

Choose upstream unless you specifically need a fork namespace or a local starting point; this fork does not add product value and is already slightly behind.

Choose upstream unless you specifically need this fork as a personal or internal tracking branch. It adds no visible capability of its own and is already lagging upstream.

Choose this fork only if you want a near-upstream AppFlowy starting point. If you want unique capabilities or a clearly maintained downstream, there is no evidence this fork currently offers that.

Choose upstream unless you specifically need this old fork as a customization base. It has some fork-specific UI/workflow and localization changes, but the maintenance gap is too large for most adopters.

Prefer upstream unless you specifically need this older fork state or its CI customizations. For adopters, this fork is a poor default choice because it is materially behind and likely missing a lot of upstream capability and maintenance.

Choose this fork only if its added search, sharing, invite, and magic-link workflows are exactly what you need and you are prepared to maintain a large rebase gap. Otherwise, upstream is the safer choice because this fork is materially stale and likely misses a substantial amount of newer work.

Choose this fork only if you specifically want a frozen AppFlowy base for private customization. If you want an actively maintained fork or the newest AppFlowy fixes, upstream is the better choice.

Prefer upstream unless you specifically need this exact frozen snapshot. This fork does not add value on its own and is too far behind to recommend for most adopters.