siyuan-note/siyuan

Choose this fork only if you want its specific customizations and can accept being far behind upstream. If you want the latest SiYuan releases, bug fixes, and lower maintenance risk, upstream is the safer choice.

Choose this fork only if you already know you need its specific repackaged/customized build. For normal SiYuan use, upstream is the safer choice: this fork is stale, far behind, and likely to miss important fixes and compatibility work.

Choose this fork only if its custom behavior is specifically useful to you and you are comfortable owning a stale, highly divergent codebase. If you mainly want current SiYuan features and low maintenance risk, upstream is the better choice.

Choose this fork only if its specific local tweaks matter more than staying current with upstream. For most adopters, upstream SiYuan is the safer default because this fork is materially stale and likely missing a large amount of recent work.

Prefer this fork only if you need its custom behavior and are willing to own the maintenance burden. For most adopters, upstream SiYuan is the safer choice because this fork is old, heavily diverged, and likely missing a lot of recent fixes.

Choose this fork only if its localization and workflow changes match a specific need and you are comfortable carrying a significant upstream gap. If you want the latest SiYuan fixes and features, upstream is the safer choice.

Choose this fork if your priority is removing account friction and using SiYuan with S3/WebDAV and Android support; avoid it if you want current upstream fixes, compatibility, and a lower-maintenance base.

Choose this fork only if you need its specific customizations and are prepared to maintain a stale, heavily diverged codebase. If you want the latest SiYuan features, fixes, and compatibility, upstream is the safer choice.

Choose this fork only if you specifically want its local customizations and are prepared to live without recent upstream fixes; otherwise upstream looks much safer and more current.