Skip to content

Instantly share code, notes, and snippets.

@superplane39
Last active July 16, 2023 13:08
Show Gist options
  • Star 5 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save superplane39/12e8e7692c54f3e647364e0b066b06c2 to your computer and use it in GitHub Desktop.
Save superplane39/12e8e7692c54f3e647364e0b066b06c2 to your computer and use it in GitHub Desktop.

Stack Overflow, Inc. has decreed a near-total prohibition on moderating AI-generated content in the wake of a flood of such content being posted to and subsequently removed from the Stack Exchange network, tacitly allowing the proliferation of incorrect information ("hallucinations") and unfettered plagiarism on the Stack Exchange network. This poses a major threat to the integrity and trustworthiness of the platform and its content.


We, the undersigned, are volunteer moderators and curators of Stack Overflow and the Stack Exchange network. Effective immediately, we are enacting a general moderation strike on Stack Overflow and the Stack Exchange network, in protest of this and other recent and upcoming changes to policy and the platform that are being forced upon us by Stack Overflow, Inc.

Our efforts to effect change through proper channels have been ignored, and our concerns disregarded at every turn. Now, as a last resort, we are striking out of dedication to the platform that we have put over a decade of care and volunteer effort into. We deeply believe in the core mission of the Stack Exchange network: to provide a repository of high-quality information in the form of questions and answers, and the recent actions taken by Stack Overflow, Inc. are directly harmful to that goal.

Specifically, moderators are no longer allowed to remove AI-generated answers on the basis of being AI-generated, outside of exceedingly narrow circumstances. This results in effectively permitting nearly all AI-generated answers to be freely posted, regardless of established community consensus on such content.

In turn, this allows incorrect information (colloquially referred to as "hallucinations") and plagiarism to proliferate unchecked on the platform. This destroys trust in the platform, as Stack Overflow, Inc. has previously noted.

In addition, these policies disregard the leeway historically granted to individual Stack Exchange communities to determine their policies, by making changes without the input of the community, overriding community consensus, and outright refusing to reconsider their position.


Until this matter is resolved satisfactorily, we will be pausing activities including, but not limited to:

Until Stack Overflow, Inc. retracts this policy change to a degree that addresses the concerns of the moderators, and allows moderators to effectively enforce established policies against AI-generated answers, we are calling for a general moderation strike, as a last-resort effort to protect the Stack Exchange platform and users from a total loss in value. We would also like to remind Stack Overflow, Inc. that a network that entirely relies on volunteers for its moderation model cannot then consistently ignore, mistreat, and malign those same volunteers.

Signed,

@ThomasOwens
Copy link

This includes prohibiting deletion of AI-generated content and prohibiting the suspension of users who post such content.

I think that this needs to be clarified a little. My interpretation is that we cannot delete generated content because it's generated content or suspend a user only because they posted generated content. For example, if they make many posts in a short period of time and bump up old questions, we can deal with that behavior.

However, it's also probably important to mention that the rules in place make it (almost) impossible to address potential plagiarism issues that arise from copying from generated text. There are specific mod messages for plagiarism, but since the text was generated and it's unlikely that same text would ever be generated again, it's not feasible to prove.


In imposing these policies, they are egregiously in violation of the process outlined as part of the moderator agreement to enact new policies for moderators.

I thought this, too. However, it's now unclear. It appears that the company interprets the requirements to announce changes 60 days and offer 30 days for discussion and review to mean explicit changes to the text of the moderator agreement. Policies are included by reference in iv. Personally, I interpret the agreement as including changes to everything included by reference: the Code of Conduct, the Terms of Service, the Privacy Policy, and "all other officially announced moderator and user policies". The company appears to exclude things included by reference and only consider changes to the legal text of the agreement itself. It's not clear who is actually correct.


Is it worth while to talk about harms? I want to make sure that this stays something that everyone can sign onto, but it could be worth while to express that we believe that being hamstrung when it comes to how we deal with a class of content is more likely to do harm to our communities and the people who trust and rely on the content on Stack Exchange sites.

@Calbonian
Copy link

I would like to propose no posting as well. SE really needs views, and posts give views after all

@terdon
Copy link

terdon commented Jun 1, 2023

I wrote an abridged version of the above, in case we want something more streamlined. I've added very little, just removed some bits


Stack Overflow, Inc. has decreed a near-total prohibition on moderating AI-generated content in the wake of a large wave of such posts being posted to and subsequently removed from the Stack Exchange network, tacitly allowing the proliferation of incorrect information ("hallucinations") and unfettered plagiarism on the Stack Exchange network. This poses a major threat to the integrity and trustworthiness of the platform and its content.

The company insists on imposing this on us, without our consent, and against the clearly expressed wishes of the Stack Exchange communities. Therefore, as volunteer moderators and curators of Stack Overflow and the Stack Exchange network, we are going on strike. Effective immediately, we are enacting a general moderation strike on Stack Overflow and the Stack Exchange network, in protest of this and other recent and upcoming changes to policy and the platform that are being forced upon us by Stack Overflow, Inc.

Until this matter is resolved satisfactorily, we will be pausing activities including, but not limited to:

  • Raising and handling flags.
  • Running SmokeDetector, the anti-spam bot.
  • Closing or voting to close posts.
  • Deleting or voting to delete posts.
  • Reviewing tasks in the various review queues.
  • Running various other bots designed to assist in moderation, such as detecting plagiarism, low-quality answers, and rude comments.

Until Stack Overflow, Inc. retracts this policy change to a degree that addresses the concerns of the moderators, and allows moderators to effectively enforce established policies against AI-generated content, we are calling for a general moderation strike, as a last-resort effort to protect the Stack Exchange platform and users from a total loss in value. We would also like to remind Stack Overflow, Inc. that a network that entirely relies on volunteers for its moderation model cannot then consistently ignore, mistreat, and malign those same volunteers.

Signed,

@ws909
Copy link

ws909 commented Jun 1, 2023

I would like to propose no posting as well. SE really needs views, and posts give views after all

This is not an idea to follow up. By not posting, we are hiding the strike from the community itself; this is not acceptable. In addition, a strike has no effect, if the reasons for the strike are not made clear. SE needs to be told exactly why we're on strike. Other visitors must be notified of the ongoing strike. Most importantly; not all curators participate on Discord (myself included). Everyone must be included, and the only way to do that, is to post on Meta. I'm sure I'm missing some points, but the overall point I'm making, is that hiding the announcement from the public, is utter stupidity.

@terdon
Copy link

terdon commented Jun 1, 2023

I would like to propose no posting as well. SE really needs views, and posts give views after all

This is not an idea to follow up. By not posting, we are hiding the strike from the community itself; this is not acceptable. In addition, a strike has no effect, if the reasons for the strike are not made clear. SE needs to be told exactly why we're on strike. Other visitors must be notified of the ongoing strike. Most importantly; not all curators participate on Discord (myself included). Everyone must be included, and the only way to do that, is to post on Meta. I'm sure I'm missing some points, but the overall point I'm making, is that hiding the announcement from the public, is utter stupidity.

I think the suggestion was that we should also go on a post strike, that we should stop asking and answering questions. Not that we shouldn't post this message, but that we should also suspend posting activity (Q&A) on the platform, @ws909.

@Calbonian
Copy link

I would like to propose no posting as well. SE really needs views, and posts give views after all

This is not an idea to follow up. By not posting, we are hiding the strike from the community itself; this is not acceptable. In addition, a strike has no effect, if the reasons for the strike are not made clear. SE needs to be told exactly why we're on strike. Other visitors must be notified of the ongoing strike. Most importantly; not all curators participate on Discord (myself included). Everyone must be included, and the only way to do that, is to post on Meta. I'm sure I'm missing some points, but the overall point I'm making, is that hiding the announcement from the public, is utter stupidity.

I meant no posting on main sites. Post on meta, obviously

@ws909
Copy link

ws909 commented Jun 1, 2023

I think the suggestion was that we should also go on a post strike, that we should stop asking and answering questions. Not that we shouldn't post this message, but that we should also suspend posting activity (Q&A) on the platform, @ws909.

@terdon
@Calbonian

Well, that's reasonable, yes. However, while we can perhaps get most of the curators onboard for this, I'm not sure if this is a good request to make. There will still be coming in lots of new questions and answers from non-curators, and we cannot prevent these. This may be seen as a failure of the community to uphold the strike, making our demands easier to dismiss, by SE.

@ws909
Copy link

ws909 commented Jun 1, 2023

Until this matter is resolved satisfactorily, we will be pausing activities including, but not limited to:

Might want to add "suspending curation chat rooms" or similar, as well.

@Calbonian
Copy link

I think the suggestion was that we should also go on a post strike, that we should stop asking and answering questions. Not that we shouldn't post this message, but that we should also suspend posting activity (Q&A) on the platform, @ws909.

@terdon @Calbonian

Well, that's reasonable, yes. However, while we can perhaps get most of the curators onboard for this, I'm not sure if this is a good request to make. There will still be coming in lots of new questions and answers from non-curators, and we cannot prevent these. This may be seen as a failure of the community to uphold the strike, making our demands easier to dismiss, by SE.

In the end, SE relies on its core users. If those disappear, SE disappears. Sure, it will take time. But it will happen.

@Tyler-H
Copy link

Tyler-H commented Jun 2, 2023

In addition, these policies disregard the leeway historically granted to individual Stack Exchange communities to determine their policicies

Typo here; policicies should be policies.

@Calbonian
Copy link

Whatever happened to this

@Oaphi
Copy link

Oaphi commented Jul 11, 2023

Whatever happened to this

@Calbonian the strike's (assuming you meant what happened after that) ongojng and is currently in the negotiations phase. Current demands based on this can be found on https://openletter.mousetail.nl. 3 representatives are negotiating the terms of what SE needs to do for the strike to end with the VP of Community on the other side (used to be a senior community manager, but they recused themselves not long ago).

@Calbonian
Copy link

Whatever happened to this github strike letter is what im asking @Oaphi

@Calbonian
Copy link

moderators are no longer allowed to remove AI-generated answers

While they accounted for much less of the problem, moderators also used to be able to remove useless AI generated questions or comments.

@Oaphi
Copy link

Oaphi commented Jul 16, 2023

Whatever happened to this github strike letter is what im asking @Oaphi

@Calbonian yeah, on an off-chance I misunderstood you, I linked to the open letter site: it's been finalized and is currently present on that site. So unless something horrific happens, there should be no developments on the gist in the near future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment