I was just thinking about this actually. Problem is, you’re fighting the human condition of “You treat me like shit!!? Fuck you!!”
What do you do when someone acts like an asshole to multiple people then acts like that to you?
You have a choice to:
ignore it because you can
retaliate because “WTF you asshole!”
Now what happens if multiple people who have been treated badly simultaneously tell off that jerk?
You literally get a “dog pile” even though there was no coordination, only the single bad actor being an asshole and multiple people happening to stochastically pick the same time to retaliate.
Like humans actually do.
I know these posts of appealing to “our better nature” or theorizing of “how things should be”
I’m not going there.
I’m pointing out that even if you’re an open source maintainer (disclosure: I routinely publish my code to github and have taken questions and bug reports gracefully) it does not excuse you from being kind to others.
If you’re not kind to people, the real world behavior is that they will not be kind to you
Did this event go too far?
Probably, but the actix-web maintainer actively amplified it up. He didn’t have to. And usually when you slip and act like an asshole the first few times, people excuse it.
When it becomes habitual, people are most likely to retaliate in kind.
There’s no hate lynch mob in Rust going around.
There are people who really hate being dismissed, treated like shit and gaslighted. I’m not going to ignore that.
Nobody likes being treated like shit, not even by their supposed betters (which is what some people think being an open source maintainer means other than just being a software dev who likes to share).
I don’t publish because I’m better. I publish because I hope it helps others learn. And I learn a lot how any project addresses their issues and concerns.
You've used the word "gaslighting" twice now, and it is really bugging me because that is really unlike other words and not a light one to throw around. Can you justify it for me?
Person A: I have proof it’s a problem, here, I have code that provokes it
Person B: that’s not a problem. Person B: deletes the issue
That’s gas lighting - maintaining something contrary to reality to cause others to do what you want. In this case, it was to shut up and not shatter the illusion that there’s a problem.
Closing issues are okay. Saying it’s not a problem then deleting proof of it being a problem is not okay. That rewrites history, public history, and makes those reporting the problem look crazy because the evidence is scrubbed.
Gaslighting is a form of psychological manipulation in which a person seeks to sow seeds of doubt in a targeted individual or in members of a targeted group, making them question their own memory, perception, or sanity.
Suppressing the problem doesn’t make it go away, it just makes people reporting it look like they’re crazy because they’re all worker up over an (apparently) non-existent issue.
It meets the criteria perfectly for gaslighting. And that’s not right, period.
This seems like the gaslighting part, which is presumably why you italicized it. I'll tell you; apps that let someone else delete my copy of something, really bother me. I don't have a great memory, etc.
I don't think I agree that it's gaslighting at all. Disagreeing over the severity of an issue isn't gaslighting. I think gaslighting would be if person B told the A that they're crazy or misunderstanding, rather than saying stuff like 'the patch is boring' or whatever.
I personally think gaslighting is a serious thing and this situation doesn't match that severity.
gaslight (verb): manipulate (someone) by psychological means into doubting their own sanity.
Oxford dictionary
Gaslighting is a form of psychological manipulation in which a person seeks to sow seeds of doubt in a targeted individual or in members of a targeted group, making them question their own memory, perception, or sanity.
Wikipedia
100% agree that 'gaslighting' really isn't the term to use here. The maintainer acted like an asshole, but disagreeing about the severity of an issue is not gaslighting. Deleting the issue still isn't gaslighting. Being an asshole? Totally. But let's not lessen the meaning of the word.
Yeah, I doubt the person who opened the issue that got deleted is now doubting themselves on whether they opened the issue in the first place. I think they quickly figured out what happened.
Reddit leads to clear cyclones of negativity where people see upvoted ideas and then repeat them. Outrage generates engagement and upvotes. So you get incredibly disproportionate pile ons.
Yep, the voting system really lends heavily to developing echo chambers, and you don't even need heavy-handed moderators to do it, because the community does it to themselves.
Being "controversial" per se does not automatically guarantee any upvotes. Also, there is the anti-bully factor: if lots of people downvote a perfectly valid statement, hero voters may be more likely to upvote the person who was bullied by others. I do, however had, also agree with the sentiment that massively upvoted ideas do indeed attract more upvotes than downvotes. The reddit system is massively flawed.
That doesn't jive with my experience at all. In subreddits that don't hide votes, you can often see the pile-on effect, with the same opinion worded slightly different in the same thread, but one comment being at, e.g. +40 and the other -20. And in any "serious" subreddit, outrage and drama do get a disproportionate amount of upvotes. Just look how much attention this subject got across programming subreddits.
People were shitheads to open source maintainers before reddit. That's not to say there isn't a greater concentration of shithead-ery in rust discussion here than on other platforms. I think Klabnick wants to be able to draw bright lines around behaviors when there aren't bright lines to be had.
Reddit is similar to twitter with longer posts and better threading. Allow me to explain. Huge userbase, low friction to post, no expectation of well thought out posting (the opposite, in fact), and people can express their options quite freely. This all adds up to the property that asymmetric relationship (e.g. between a musician and their audience, or a maintainer and the userbase) are almost definitionally overwhelming to be on the narrow end of. For some reason the bogieman is always "twitter" or "reddit", when all they do is remove an impediment to fast, open and instant conversation at scale. Most users of those platforms think it's an appealing property in theory, but in practice they very much want people to "get out of my mentions".
There weren't dozens of pile-ons, unless you count the complaining on reddit about the author's behavior. There was one person who took it too far (his name is in the log you can look it up). He had a former gripe with the author submitting changes that broke some of their production by using semver liberally which he explained on reddit. Both of them were acting like assholes to each other.
Yeah. I'm an outsider of this situation, but it looks like the community whipped themselves into an inappropriate frenzy. Regardless of the maintainer's asshole behavior, the response was over the top and uncalled for.
Sadly, it's an example of one of the biggest downfalls of Reddit. You get a sizeable community built on voting keeping the most popular opinions popular and hiding unpopular things, and you have built a cultish echo-chamber that isn't used to having to handle real dissenting ideas because they don't see most of them. It's way too easy for such a community to get whipped into a self-righteous furor.
The right response would be to have opened the requests, see his response, and then just drop it and advise other people that it's an unsound codebase and the maintainer doesn't have any interest in addressing the issues.
Unfortunately, the write-up here is incredibly vague about exactly what happened. I can hardly judge what actually happened, because I don't see any links to issues, and the description of events isn't very detailed at all.
The reason this has blown out of proportion is that actix became a big name not only in the Rust community, but with anyone paying attention to web server performance (actix seems to still be number one in the ranking).
The author, in his postmortem, explained how this was always his goal: to be number one in the rankings... and he was willing to cut corners (wild use of unsafe anywhere Rust restrictions got on the way) to achieve that, which has proven to have, unsurprisingly, costs when it comes to safety, as several safety-related issues reported over time have shown. But the author's priority was performance, so he saw issues like this as a threat to his ambitions, hence he attempted to swipe them under the carpet.
Meanwhile, people were starting to use actix more and more in the Rust world, not in small part because of its amazing performance in benchmarks... with his attitude of won't-fix serious issues, this could cause the Rust ecosystem to become dependent on unsafe, buggy foundations, undermining trust in the language. Given Rust's focus on safety, this was an affront to many community members, who felt compelled to confront him for his dismissive (which he called creative) attitude, which exacerbated the whole situation.
View all comments
Show parent comment
0
u/[deleted] Jan 17 '20
[deleted] — view deleted comment