@foo_dogsquared Step 1: Collect software.
Step 2: ???
Step 3: Profit.

Hot take: people with bad attitudes write bad code.

@meena I've seen some ugly code before, but this is a whole other level.

@meena I wouldn't even work on this code base if someone offered me a ton of money to do it.

@meena or use an alternative program with reasonable and responsible maintainers like Ardour 馃し

Aaaaaaaaaaaaaaaaaaaaaahhhhhhhhhhhhhhhhhhhhhhhhhhdacity

@meena forking this isn't even worth it. Write a new application from scratch.

Be :fedora: :pine64: boosted

@meena I cannot recommend that anyone use Audacity knowing this.

@meena I cannot recommend that anyone use Audacity knowing this.

@meena and they were trying to vendor libcurl into this

@meena Remember that recent blog post from the lead developer of Signal exploiting a vulnerability in an old version of FFmpeg? Well Audacity was using a vendored version of FFmpeg 2.2.2, which was released 2014-05-04, until 4 days ago. Then that update was reverted yesterday without explanation. I asked for an explanation and none has been provided. github.com/audacity/audacity/c

@iooioio I don't think so. I'm pretty sure they own the trademark and copyright to the logo.

@meena There's nothing remotely sensible going on here.

Be :fedora: :pine64: boosted

@meena The only way for Audacity's mismanagement to stop being Mixxx's problem is for distributions to build their Audacity packages with Audacity's fork of PortAudio... unless someone does the work to clean up a lot of technical debt, which doesn't seem likely. Fuck.

@meena The only way for Audacity's mismanagement to stop being Mixxx's problem is for distributions to build their Audacity packages with Audacity's fork of PortAudio... unless someone does the work to clean up a lot of technical debt, which doesn't seem likely. Fuck.

Show older
Fosstodon

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.