laurent22/joplin

Prefer upstream unless you specifically need this fork as a private staging area or mirror. As provided, it offers no visible feature advantage and is materially behind upstream.

Choose this fork only if its performance-focused desktop changes are the point. For most adopters, upstream Joplin is the safer choice because this fork is materially behind and appears to have stopped active maintenance.

Prefer this fork only if the Tomcat WebDAV and fork-specific behavior are important enough to justify falling behind upstream. If you want the most stable, current Joplin, upstream is the safer choice.

Choose this fork only if you need its repo-specific workflow and are willing to own merge debt. If you mainly want the latest stable Joplin experience, upstream is the safer choice.

Choose this fork if voice typing and deep customization matter more than staying close to upstream. Choose upstream if you want the latest fixes, easier maintenance, and lower merge risk.

Choose this fork only if voice typing is the point of adoption and you are prepared to own maintenance. If you want a stable Joplin base with current fixes, upstream is the safer choice.

Choose this fork only if voice-typing is the main requirement and you are prepared to own a long-lived divergence. For most adopters, upstream Joplin is the safer default because this fork is materially stale and much harder to maintain.

Choose this fork if you need the server/container and deployment changes it adds. Avoid it if you want the safest path to current upstream Joplin, because it is significantly behind and likely costlier to rebase.

Choose this fork if voice typing is the feature you need and you are comfortable carrying a stale, heavily diverged Joplin branch. If you want the most current Joplin fixes and broad platform stability, upstream is the safer base.