LambdaConf Crockford Disinvitation
The cluster centers on the disinvitation of Douglas Crockford from LambdaConf due to other speakers' discomfort with his views, fueling debates on conference inclusivity, free speech, deplatforming, and codes of conduct.
Activity Over Time
Top Contributors
Keywords
Sample Comments
It seems like most comments here (and in previous times this has been discussed) are avoiding the actual reason why Crockford was disinvited - it is because a number of speakers said they would be uncomfortable with him speaking and would not speak and attend the conference. The comments appear to be looking for facts, reasons, examples of past behaviour of Crockford to see if these facts can justify the decision. HN'ers are looking to understand the reasons why someone has an emotional re
If your conference will dis-invite / "de-platform" people based on their opinion about topic {foo}, you are in fact hosting a conference about {foo}, regardless of what your name, official agenda, or spokespeople say.Kudos to LambdaConf for actually keeping on focus in the face of dissent.
Where's the option for "Conferences should allow whomever they wish to speak, but don't come crying to me when it all ends in tears, as it will if you court controversy by focusing on technical merit over personal behaviour."
After reading the "code of conduct" on their homepage I would assume that you have unknowligly broken something like> "Using gendered terms like “dude” or “guys” to address a mixed-gendered group of people contributes to furthering exclusion of underrepresented individuals."The fact that they included an option to "make an anonymous" report furthers the assumption that you just got under the political wheels of the conference.
I don't believe they were arrogant chauvinist pigs. I believe that they wanted to make sure this important issue was covered in their conference, which is their right and not a bad thing, overall. I did find it weird that my offer for a talk about diversity in tech wouldn't work for those purposes.
I have no idea. The conference organizers said people privately voiced concerns and other speakers threatened to pull out over his presence.I was addressing the parent comment's point about inclusiveness in general.
There's no free speech on hackernews. People get moderated all the time! If hackernews can moderate its comments, then can't a conference moderate its speakers?
Wow, an important talk was pulled because of this? There is a continuum of disagreeable statements and a corresponding continuum of appropriate responses. The response from the conference organizers was grossly disproportionate to Crockford's behavior which was clearly not malicious and probably not even deliberate. A reasonable alternative would have been to privately contact him and express concern about his past choice of words. Removing him outright is unfair to both Crockford an
> petty, deranged peopleThat has not been established. Without knowing the author’s history or any background the only thing I can conclude from the conference’s organisers is that they are disorganised and with misplaced priorities: if a potential speaker alleges they’ve been incorrectly blacklisted (and shows no obvious warning signs) then investigating and rectifying the situation as necessary should be a high priority: that’s just good customer service and community leadership - especi
Just to note, your first and third links are the same article under two different aliases. So it is two people who have publicly declared this. Though there may be more who have unspoken dislike of the man.I can certainly imagine myself to be drawn to a conference where Douglas Crockford was speaking (in fact, I'd be likely to attend if he were the only speaker), but having "lightly googled" the other two I'm not sure their contributions to the community would be enough t