> I'm not sure I understand why these forks exist exactly.
A large part of it is mistrust of Muse, over the initial opt-out nature of the new telemetry and over other past decisions, unrelated to Audacity, that people have found questionable.¹ Fool me once, and all that.
> Looking at the git tree, it's clear that these forks have diverged significantly from upstream Audacity
That in itself would be a reason, certainly from a dev's PoV, on top of that trust thing. If both projects fit what they want, but the downstream ones do it in a way they prefer, that is enough difference even if
> [sic] the marketing does not make clear the difference from upstream
implies that there is no major difference² from an end-users PoV³ at this point.
--
[1] I've not looked into the latter in much detail, my use of Audacity is so infrequent currently that I don't think I've updated (or, obviously, switched to something else) since before the hoo-hah.
[2] Yet, at least.
[3] beyond the telemetry and potential trust issues
A large part of it is mistrust of Muse, over the initial opt-out nature of the new telemetry and over other past decisions, unrelated to Audacity, that people have found questionable.¹ Fool me once, and all that.
> Looking at the git tree, it's clear that these forks have diverged significantly from upstream Audacity
That in itself would be a reason, certainly from a dev's PoV, on top of that trust thing. If both projects fit what they want, but the downstream ones do it in a way they prefer, that is enough difference even if
> [sic] the marketing does not make clear the difference from upstream
implies that there is no major difference² from an end-users PoV³ at this point.
--
[1] I've not looked into the latter in much detail, my use of Audacity is so infrequent currently that I don't think I've updated (or, obviously, switched to something else) since before the hoo-hah.
[2] Yet, at least.
[3] beyond the telemetry and potential trust issues