

telemetry and a reverted privacy policy change that lost some goodwill, but i agree
[He/Him, Nosist, Touch typist, Enthusiast, Superuser impostorist, keen-eyed humorist, endeavourOS shillist, kotlin useist, wonderful bastard, professinal pedant miser]
Stuped person says stuped things, people boom
I have trouble with using tone in my words but not interpreting tone from others’ words. Weird, isn’t it?
Formerly on kbin.social and dbzer0
telemetry and a reverted privacy policy change that lost some goodwill, but i agree
…through what i mentioned. audacity for now!!
i’ve never had noticeable lag in audacity besides a niche crash that got fixed. though the cloud storage thing never ever worked for me. it’s nice though and you still save locally instead of to cloud by default. plusi think the musehub thing is kinda explainable with the proprietary effects marketplace they added to musehub, and it’s not like audacity plugins were always foss anyways
i mean they were using the rather old wxwidgets
they backtracked on the privacy policy and said they had really overzealous lawyers that they somehow mistrusted lawyers doing so “out of an abundance of caution” so i’m still giving them one final chance here since that issue was resolved rather quickly (within two weeks, which is why i’m not absolving them and giving them a chance, but it’s been uneventful since 2021 so i think that strike’s gonna expire in a year)
and i don’t think the telemetry was every an issue since it was always going to be opt-in
tenacity does not have the rally useful beats and measures feature for some reason
i’ve yet to meet a single person who uses tenacity
TL;DR: Competitors in integrating with Atlassian are not allowed to incorporate code after the change because they used it in free add-ons, which caused the official integration (a paid add-on that is the sole source of funding) to be labeled a scam by a review in late August.
Plus, the thing was never really open source anyway:
draw.io is also closed to contributions, as it’s not open source. We follow a development process compliant with our SOC 2 Type II process. We do not have a mechanism where we can accept contributions from non-staff members.
(for package management, not weird concerns like “they’re adding an entire http library to audacity for this so they must be in the process of using it for something else”)