Skip to content
This repository has been archived by the owner on Jul 17, 2020. It is now read-only.

Remove !!fuckable #114

Closed
benjamingr opened this issue Nov 12, 2013 · 16 comments · Fixed by #115
Closed

Remove !!fuckable #114

benjamingr opened this issue Nov 12, 2013 · 16 comments · Fixed by #115

Comments

@benjamingr
Copy link
Contributor

http://chat.stackoverflow.com/transcript/message/12900519#12900519

I don't think Fuckable should be a core command.

If we really want it we can add it with !!learnEval or somethng like that.

It can come off as rude to our 13+ crowd, and it's generally bad taste.

@ralt
Copy link
Collaborator

ralt commented Nov 12, 2013

👍

Kill it.

Dead or alive? My choice: 👎

Did I just learn about emojis? I did.

@ryankinal
Copy link

👍

@nderscore
Copy link

Kill 👎

@rlemon
Copy link
Collaborator

rlemon commented Nov 12, 2013

I made the original user taught command, I can't remember who convinced Zirak to bake it in, but yea. I'm cool with it being removed. It was fun for a few days but now I think it just idles anyways.

@FirstWhack
Copy link
Contributor

I think it was me and @rlemon that really pushed for it. Yeah, it's useless, but I wouldn't call it bad taste. Sex is a part of life. 

Anyway, I see no use for it, so if you want to remove it because of that, that makes sense.
All it does is tell you your maximum socially acceptable shagging age. No shame in that.

On Tuesday, November 12, 2013 12:54 PM, benjamingr notifications@github.com wrote:

http://chat.stackoverflow.com/transcript/message/12900519#12900519
I don't think Fuckable should be a core command.
If we really want it we can add it with !!learnEval or somethng like that.
It can come off as rude to our 13+ crowd, and it's generally bad taste.

Reply to this email directly or view it on GitHub.

@FirstWhack
Copy link
Contributor

I suppose I do probably have the highest acceptance rate of "taboo" things in the JS room. 
So there's probably shame in that, I guess, just not to me. 

On , Josiah South j.hawkinss@yahoo.com wrote:

I think it was me and @rlemon that really pushed for it. Yeah, it's useless, but I wouldn't call it bad taste. Sex is a part of life. 

Anyway, I see no use for it, so if you want to remove it because of that, that makes sense.
All it does is tell you your maximum socially acceptable shagging age. No shame in that.

On Tuesday, November 12, 2013 12:54 PM, benjamingr notifications@github.com wrote:

http://chat.stackoverflow.com/transcript/message/12900519#12900519
I don't think Fuckable should be a core command.
If we really want it we can add it with !!learnEval or somethng like that.
It can come off as rude to our 13+ crowd, and it's generally bad taste.

Reply to this email directly or view it on GitHub.

@9034725985
Copy link

Are you going to remove !!urban next?

@benjamingr
Copy link
Contributor Author

No, no reason to remove !!urban it has a use.

@ryankinal
Copy link

Yeah. The point is that things like !!urban, while they may be offensive when put to specific uses, are generally useful. There was a specific complaint about !!fuckable, and while not many chat users seem to be offended by the language and/or functionality, having it built into the bot seemed a little excessive.

So, to summarize:

!!fuckable is always profane
!!urban is only profane when used in specific ways

@9034725985
Copy link

How about replacing it with doable?

@ryankinal
Copy link

In the end, it still has to do with how young of a person you can have sex with. Which is a little creepy at best.

@9034725985
Copy link

Yeah, probably ok to remove.

@9034725985
Copy link

My only concern is a slippery slope. Someone has to actively invoke the
command so it is the person being creepy, not the bot.

@ryankinal
Copy link

In general, I think everybody is very aware of a slippery slope.

@mainerror
Copy link
Contributor

I'll make sure to merge the changes this weekend. The command will be removed.

@Shmiddty
Copy link
Contributor

We're talky about the slippery slopes of soapy asses, right?

@Zirak Zirak closed this as completed in 77498ce Nov 15, 2013
Zirak pushed a commit that referenced this issue Nov 15, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants