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

Removed the retard option to close #107 #109

Closed
wants to merge 1 commit into from
Closed

Removed the retard option to close #107 #109

wants to merge 1 commit into from

Conversation

robotmachine
Copy link

No description provided.

@robotmachine robotmachine mentioned this pull request Nov 4, 2015
@jungshadow
Copy link

👍

(Personally, I'm sad this even had to happen @robotmachine, but thanks for doing it)

@karenetheridge
Copy link

👎

@SwooshyCueb
Copy link

👍

@shadowcat-mst
Copy link

So, shall we replace it with 'moron'? Or 'idiot'? Or 'slow'? How far back do we need to go along the euphemism treadmill before we're safe?

Should we remove 'bad' as well because its etymology apparently involved criticising men for being effeminate a few centuries ago?

@SwooshyCueb
Copy link

I'm not currently inclined to debate this sort of thing in a github pull request, but personally I'd like to stay away from 'slow' as well.

I vote in favor of replacing 'Fucktard' with 'Fucknugget'. Doesn't contribute to any negative social stigmas that I'm aware of.

@dha
Copy link

dha commented Nov 5, 2015

Although I'm not convinced this isn't a slippery slope as indicated by @shadowcat-mst, I don't think replacing Fucktard with Fucknugget is terribly problematic as, in this context, it appears to convey the same sentiment.

@jungshadow
Copy link

I'm fine with @SwooshyCueb's idea of replacing the endpoint with /nugget or similar, but that could be handled in a separate PR. Would this be fine to purely cover the removal?

@SSederberg
Copy link
Contributor

This operation can be changed to mean something else that doesn't ruin the context and your feelings. The idea @SwooshyCueb put is acceptable.

Edit: Wrong User, not enough caffeine...

@philip2156
Copy link
Contributor

I'd also vote for /dumbfuck to repalce it hah

@theromulans
Copy link

👍 Would be nice to have a replacement rather than a straight up removal.

@philip2156
Copy link
Contributor

I would not only vote for /dumbfuck as the replacement (unless its offensive as well? I'm Australian, not a lot offends me.) but I will merge it if changed in this PR

@barnumbirr
Copy link

👎 really people? really?

@robotmachine
Copy link
Author

I have no desire to replace this with anything. Someone else is welcome to take up that task.

@robotmachine
Copy link
Author

I wrote too many feelings out on the issue here.

@jungshadow
Copy link

I think this removal requires the addition of some documentation of the guidelines for political correctness. For instance, we'd need to make it clear not to add the word "idiot", as well.

@v6 Not to speak for @robotmachine, but my impression is that this PR isn't about creating guidelines–which should be a longer discussion in another issue and I agree that it would be helpful–it's purely about removing one endpoint that is offensive to a community of people. There may be other instances of overtly offensive references, but, for the time being, it should be fine for these updates to happen organically.

Plus, it would need regression tests to see whether more offensive words have been reintroduced.

While testing for overtly offensive words may be beneficial, I believe catching many of these sorts of issues is going to be a human process.

For instance, I understand that the words "master," "dumb" and "slave", while used innocuously in the technical community as words for replication, are also quite offensive to the disadvantaged.

Possibly more evidence why the technical community feels exclusionary and isolating to many people.

I'm really surprised and disheartened that anyone is willing to push back on this change. It fine to be irreverent and humorous, but not hurtful/hateful.

@robotmachine
Copy link
Author

@jungshadow The purpose of v6's comment is to prove that any effort to make a change like this would require loads of back-end work and process because if it is worth removing now then we must ensure it never happens again.

It is identical to the argument that banning guns won't work because criminals don't follow the law. ie. if it isn't going to be 100% effective then it has failed and shouldn't be attempted.

@SSederberg
Copy link
Contributor

"... any effort to make a change like this would require loads of back-end work and process because if it is worth removing now then we must ensure it never happens again."

Well, it would be nice to not have to repeat this process every time someone is offended or wants an operation removed. Better now than later.

@kvannotten
Copy link

👎 this PC stuff is getting out of hand tbh

@atomboulian
Copy link

👎 "Fuck off" is offensive to everyone. It is meant to be an offensive service. It does not discriminate against any particular type of person; it treats every person the same. Certain persons are not exempt from mean comments directly or indirectly. I'm with @kvannotten.

@karenetheridge
Copy link

is "fuck off" discriminatory against asexual people?

@atomboulian
Copy link

well played @karenetheridge 😏

@philip2156
Copy link
Contributor

@atomboulian @karenetheridge 👍

@surdu
Copy link

surdu commented Feb 5, 2016

@RealDolos
Copy link

👎
I identify as a retard and feel offended that people say my identify is offensive.
My pronouns are: tard/tardo

On an unrelated note, @jungshadow looks too white to have a nick name like this, I smell some sweet, sweet cultural appropriation

@robotmachine
Copy link
Author

Are you fucking kidding me with this shit, @RealDolos? https://twitter.com/dolosthegreat/status/696198317848526848

I'm sorry that you are so fragile that the slightest disagreement makes you go ragepost on Twitter.
http://foaas.com/bucket/robotmachine

@RealDolos
Copy link

@robotmachine Some people just cannot take a "thank you" I guess...
Also look who is raging now xD

PS

I'm sorry that you are so fragile that the slightest disagreement makes you go ragepost on Twitter.
http://foaas.com/bucket/robotmachine

Oh wait, that's homophobic I suppose. You should file an issue to have it removed...

@robotmachine
Copy link
Author

You're right, @RealDolos. Thank you for being you. It would be nice if you'd at least be good enough <3 my tweets or something you adorable little fucknugget, you.

Oh wait, that's homophobic I suppose. You should file an issue to have it removed...

I didn't say it had to be gay cocks you were choking on. They can be fake for all I care. My main concern is just that several cocks or cock-like implements find their way in to your general esophageal area.

@ChlorideCull
Copy link

I didn't say it had to be gay cocks you were choking on. They can be fake for all I care. My main concern is just that several cocks or cock-like implements find their way in to your general esophageal area.

Well, @robotmachine, as a homosexual, i find it offensive that you believe such a thing is a punishment.

In all seriousness though, 👎, this is a service meant to offend everyone, and it clearly does.

@ghost
Copy link

ghost commented Feb 29, 2016

This is pretty fucking ironic. I would like to direct people in favor of this change to kindly fuck off.

@tomdionysus
Copy link
Owner

All things considered, foaas.com isn't PC, and as has been repeatedly pointed out, it's meant to be offensive in a lighthearted and ironic way, and if you're easily offended you probably shouldn't be anywhere near it, so I think i'll keep it as it is.

@v6
Copy link

v6 commented Aug 21, 2018

// , Apparently my thoughtful, correctly languaged, supportive comment, with helpful suggestions for how to work out such problems by protecting the gentle denizens of Github from hate speech, has been removed from the record.

I can't imagine what anyone would think we'd gain by its removal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet