pear-devs/pear-desktop

Choose this fork if the bundled extras are the point; choose upstream if you want broader maintenance, faster updates, and less divergence.

Prefer this fork if you want bundled convenience features and a narrower, more opinionated experience. Prefer upstream if you want the full plugin ecosystem, fresher maintenance, and lower divergence risk.

Choose this fork if you want the added fullscreen, lyrics, and adblocker-focused behavior and are okay with trailing upstream by a substantial margin. Choose upstream if staying current with the latest fixes and releases matters more than the fork's extras.

Choose this fork if you want a customized dev base with specific behavioral patches and expect to maintain it yourself. Choose upstream if you want the latest fixes, lower maintenance risk, and a cleaner upgrade path.

Choose this fork if your priority is automated nightly/dev builds and release workflow experimentation. Choose upstream if you want the broadest feature set, freshest fixes, and lower regression risk.

Prefer this fork if you want a more permissive, privacy-leaning Pear Desktop with explicit ad-blocking and login changes. Prefer upstream if you want the latest fixes, test coverage, and lower-maintenance stability.

Choose this fork only if the bundled extras matter more than staying current. If you want the latest fixes, packaging, and maintenance, upstream is the safer choice.

Choose this fork only if you want its bundled extras and do not need to stay current with upstream fixes; otherwise, the upstream project is the safer default.

Choose this fork if your priority is adblocker restoration and a couple of targeted runtime fixes; avoid it if you want the most current upstream Pear Desktop experience, because it is substantially behind and appears to track only a small subset of the parent project's ongoing work.