« first day (4346 days earlier)      last day (626 days later) » 

08:28
Hi all. This is just a small message to indicate to you that both forest and me have decided to go on strike. In case you don't know: we've been told by SE only to remove AI-generated posts if the poster has indicated that it has been generated by an AI. This means I cannot uphold our own established policy on AI generated content... continued...
7
This has been forced upon us out of the blue, and with no data to show that suspensions have been issued incorrectly, or to indicate that the drop of traffic (which has been happening) was due to these suspensions - correct or otherwise. This seems to be a panicked response by SE due to the sudden drop in site traffic... continued...
Most of these issues are discussed on the general Meta Stack Exchange site. Here is the open letter to SE. If you need more links please leave a comment here. I'll try and put this summary up on our Meta as well, when time permits. I've got a payed job as well :)
 
2 hours later…
10:36
@MaartenBodewes-onstrike Let's wait to see if our entire moderation team goes on strike before creating a meta post. I also suggest featuring two posts: One which describes the problem in general, and one which is an announcement of the strike itself. I believe Unix.SE took this approach. Even if we don't get the whole team on board, we can still feature a meta post explaining our own actions.
11:14
Not everybody reads chat, that's for me the main reason for posting on meta.
Good point.
 
9 hours later…
20:04
0
Q: Moderator strike due to SE forcing AI-moderation policy

Maarten Bodewes - on strikeWe've decided on our meta that we do not want AI-generated answers. However, due to falling views and participation (probably mainly on SO) Stack Exchange has explicitly forbidden us to suspend users unless they indicate voluntarily that they haven't used an AI such as ChatGPT. This change has be...

3

« first day (4346 days earlier)      last day (626 days later) »