Another misstep for Audacity
Another misstep for Audacity
Posted Jul 9, 2021 9:14 UTC (Fri) by excors (subscriber, #95769)In reply to: Another misstep for Audacity by willy
Parent article: Another misstep for Audacity
"felt their safety was risk" also seems pretty mild, when the Tenacity maintainer says (in the linked GitHub issue) "I was slit in the arm" and "It was attempted murder with an illegal butterfly knife" as the result of a 4chan harassment campaign.
(Pseudonymous GitHub comments aren't necessarily proof of anything, but the maintainer does have a long history there and on other social media and doesn't hide his real identity and sounds like a reasonable person, and provides links to 4chan threads full of wildly offensive abuse against him (which seemingly started when he rejected 4chan users' vote for a stupid meme name for the fork), so his claims seem plausible. Even without the assault, the online harassment is totally unacceptable.)
Posted Jul 9, 2021 11:32 UTC (Fri)
by ale2018 (guest, #128727)
[Link] (1 responses)
The dummy sneedacity repository advertised on 4chan features James Crook, an Audacity author, as a main contributor. If that's where the harassment originated, perhaps it's safe to drop Audacity irrespective of any telemetry features.
Posted Jul 9, 2021 12:45 UTC (Fri)
by excors (subscriber, #95769)
[Link]
I think you're misinterpreting GitHub's contributor list - it's just showing the authors of all commits in the master branch since the beginning of time. The last of James Crook's commits in that repository are from April 13, i.e. they are from the main Audacity repository before it got forked, so he has zero involvement with the fork or the harassment.
Another misstep for Audacity
Another misstep for Audacity
