Live data from Hacker News

When software offends, the pantyshot package controversy

zdnet.com

41–50 of 78 posts

Re: When software offends, the pantyshot package controversy

#41
post #40

Seems relatively simple. This Frank Smit guy loves anime in a borderline-creepy way and is, like the original developer, not a native english speaker. [1]: http://61924.nl/04-11-2011/ubuntu-10-dot-10.html [2]: http://61924.nl/about.html

Just curious, but how is this borderline creepy?

Re: When software offends, the pantyshot package controversy

#42

Sexism and Racism: two cards people play all the time for ever-annoying reasons. They're the kind of arguments you "can't be against" because, how can you be against stopping racism/sexism? They're also the kind of arguments that keep sexism/racism happening. We should focus on the important parts: Are you offended by it? - Deal with it or don't use it or politely make your opinion known to the author. Be an adult an…

It's not at all an analogous situation. You're talking about offending people with the name of a package you wrote. This is talking about offending the person who originally wrote the package by suggesting a name, the connotations of which she didn't fully understand. Her name is now associated with it. This isn't a problem of someone childishly over reacting.

Re: When software offends, the pantyshot package controversy

#43
post #13

Serious question: can we fork the library, s/pantyshot/somethingelse/g, submit it to PyPI, and then just nobody use the original?

No, because it would be hypocrite to rate the importance of the name higher than the value of the code, and then nevertheless try to steal the code from the guy who spent all the time developing it.

The guy wrote the code and gave it a tongue in cheek name. Deal with it. What the hell is wrong with this world? Moral outrage in the sub-urbian latte crowd? Pillows not fluffed enough?

Re: When software offends, the pantyshot package controversy

#44
post #4

I look at the choice of "Misaka" after "pantyshot" and think this is unambiguously an example for talking about the recent topic of not tolerating assholes in open source software.

Man spends hours developing free software for the world and gives it a tongue in cheek name. World judges man and software by name, wants the software out of repository and the man gone from the planet. I think John Cleese would like to send you all to the front line of a gruesome war – in panties, of course – to learn to deal with an actual problem.

That's a big brush you're painting with, but the core is true: this is about judging how they chose to name their project.

Re: When software offends, the pantyshot package controversy

#45

Sexism and Racism: two cards people play all the time for ever-annoying reasons. They're the kind of arguments you "can't be against" because, how can you be against stopping racism/sexism? They're also the kind of arguments that keep sexism/racism happening. We should focus on the important parts: Are you offended by it? - Deal with it or don't use it or politely make your opinion known to the author. Be an adult an…

It's not at all an analogous situation. You're talking about offending people with the name of a package you wrote. This is talking about offending the person who originally wrote the package by suggesting a name, the connotations of which she didn't fully understand. Her name is now associated with it. This isn't a problem of someone childishly over reacting.

Agree! It's a problem of /many/ people childishly overreacting :p

Re: When software offends, the pantyshot package controversy

#46
post #9

Earlier quoted context omitted.

You're asking people not to have a knee-jerk reaction to offensive language, but you're having a knee-jerk reaction to people being offended. Some people might choke on their morning coffee when reviewing a pull request for "pantyshot", but the majority of us just want a bit of civility (not unlike the rules of HN).

Nobody chokes on their morning coffee when reviewing a pull request for "pantyshot". Such people ought to be sent to the front line in all-out war to learn to deal with some real issues in life. Besides, men wear panties too. I've seen them do it.

I don't see the connection to being sent to war: It seems like you are trying to say "because this (war) is more unpleasant, you have nothing to complain about", which makes no sense.

Re: When software offends, the pantyshot package controversy

#47

Earlier quoted context omitted.

Nobody chokes on their morning coffee when reviewing a pull request for "pantyshot". Such people ought to be sent to the front line in all-out war to learn to deal with some real issues in life. Besides, men wear panties too. I've seen them do it.

I don't see the connection to being sent to war: It seems like you are trying to say "because this (war) is more unpleasant, you have nothing to complain about", which makes no sense.

I think he was trying to say that experiencing high magnitude discomfort puts low magnitude discomfort in perspective.

Also, knowing several Iraq veterans before and after, it seems to get you very comfortable with offensive language :p

Re: When software offends, the pantyshot package controversy

#48
post #13

Serious question: can we fork the library, s/pantyshot/somethingelse/g, submit it to PyPI, and then just nobody use the original?

No, because it would be hypocrite to rate the importance of the name higher than the value of the code, and then nevertheless try to steal the code from the guy who spent all the time developing it. The guy wrote the code and gave it a tongue in cheek name. Deal with it. What the hell is wrong with this world? Moral outrage in the sub-urbian latte crowd? Pillows not fluffed enough?

Since when is forking open source code 'stealing' it?

Oh boy, what can of worms am I opening here...

Re: When software offends, the pantyshot package controversy

#49
post #9

Sexism and Racism: two cards people play all the time for ever-annoying reasons. They're the kind of arguments you "can't be against" because, how can you be against stopping racism/sexism? They're also the kind of arguments that keep sexism/racism happening. We should focus on the important parts: Are you offended by it? - Deal with it or don't use it or politely make your opinion known to the author. Be an adult an…

You're asking people not to have a knee-jerk reaction to offensive language, but you're having a knee-jerk reaction to people being offended. Some people might choke on their morning coffee when reviewing a pull request for "pantyshot", but the majority of us just want a bit of civility (not unlike the rules of HN).

>You're asking people not to have a knee-jerk reaction to offensive language, but you're having a knee-jerk reaction to people being offended.

Uh, yeah, and that invalidates his point in exactly what way? It's still true that people are overreacting. If somebody is offended by the name of a freaking software package, I'd wager that this person has other problems to work out.

It's also true that "sexism" (and various other *isms) is a completely abused term that simply serves as an "argument" that nobody can counter, since if anybody does, he must be a sexist.

Besides, I think that "civility" includes not whining to everyone over being personally offended by something.

Re: When software offends, the pantyshot package controversy

#50
post #38
post #31

Earlier quoted context omitted.

[I] had no idea this was something that would be interpreted this negatively. So perhaps the authors didn't either. The original author, when challenged, renamed the package to 'Misaka', an Anime character portrayed as an 11-year old who is often depicted graphically from an upskirt angle (its all pretty unsavory, frankly) . Point is... original author clearly knew what he was doing with these package names.

Point is... original author clearly knew what he was doing with these package names. That seems very likely, but from what I have read so far, all the evidence is circumstantial and guilt is being inferred. So it is still possible it's a stupid mistake. Seriously. (Perhaps there is damning, definitive evidence out there. But what I have read so far contains no smoking gun.)

Possible, yes. But so absurdly unlikely that I find it strange to seriously suggest the package maintainer did not know what he was doing.
Post reply on HN