Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audacity's team is censoring legitimate questions #1346

Closed
AntiSol opened this issue Jul 21, 2021 · 0 comments
Closed

Audacity's team is censoring legitimate questions #1346

AntiSol opened this issue Jul 21, 2021 · 0 comments

Comments

@AntiSol
Copy link

AntiSol commented Jul 21, 2021

Describe the bug
I asked a legitimate question here:
#889 (comment)

and was blocked for it.

I read through the guidelines I was linked to, but I don't see how this post violated them.

It should be noted that I was legitimately asking a question when I made this post - I wrote this question with this wording because I was wondering whether I was being too paranoid. The response would seem to indicate pretty clearly that I wasn't.

But perhaps the Audacity team can elaborate on how this wasn't an act of censorship.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Actions we propose to take on PR #835 #889'
  2. Ask a legitimate question that questions the integrity of the scumbags who have tried to turn audacity into apyware
  3. Wait a while
  4. Scroll down to the message saying 'you have been blocked from contributing to the audacity project for this comment'
  5. Try to fork, observe "You have been blocked from forking" message.
  6. Chuckle at the irony in all the comments from apologists saying "nobody is preventing you from forking"
  7. Go find an audacity fork and donate to them

Expected behavior

  • Good-faith responses to the question raised.
  • Mature and open discussion with the project maintainers.

Screenshots
audacity_discussion_blocked

audacity_cannot_fork

Additional information (please complete the following information):

  • OS: All?
  • Version: Any after the hostile takeover
  • Sound Device: All?

Additional context
I expect I'll be permanently blocked from the audacity repo for raising awareness of this. And I'm sure that somehow that action will also not be censorship according to musescore.

Luckily I've already got a copy of the pre-spyware codebase, so that's not much of a problem. But If you'd like to find me and discuss, I've enabled issues on the github fork I just made now that I'm temporarily unblocked from the audacity repo.

@audacity audacity locked and limited conversation to collaborators Jul 21, 2021
@crsib crsib closed this as completed Jul 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants