Moderation Strike: Results of Negotiations
meta.stackexchange.com
meta.stackexchange.com
It's always easier to have a dictator come in and tell people what to do, but people complain about it.
(We known dang moderates us out of the goodness of his paycheck, which means he’s free to love us all :)
that is an interesting argument, but i don't understand how it is relevant here.
as far as i can tell the moderators were acting with good intentions as a force for good as it were. if anything the problem was not that but that the company seemed to think that they can dictate what volunteers do. but really, they can't. reddit is doing the same, and if they don't listen to the volunteers they will eventually pay the price.
I'll try to lead by example here: I'm glad they established its okay to moderate answers flagged as AI and that moderation rules should be public.
in short what they achieved is that the company can't just override the moderators at will, which is think is reasonable. if i volunteer somewhere i want to be respected, not be treated as a lackey that does their bidding.
Very mysterious.
Judging by how your comment appears to already have been flagged by other users though, you may want to include your actual point after the punchline.
Yup. SE Inc. gonna SE Inc. Not coming back this time either.
It may be actually in the interest of OpenAI to start paying SO for the data and make sure it flows to the community in some way. Otherwise they will be starved.
It’s a bit like browsing through a book vs. interviewing a random person who read the book.
rm -rf $INSTALL_DIR/*
this line of code has at least two gotchas. if you run it to test it out, there is a good chance you will destroy your data. It is otherwise a valid line of code.This is not a theoretical problem: https://github.com/valvesoftware/steam-for-linux/issues/3671
> With code interpreter, ChatGPT can check that it's code at least runs without errors
is not a solution to gotchas/caveats that build up over time that ChatGPT won't know about. ChatGPT can warn about caveats from that line of code because it's old code. It does not have a magical defense that will allow it to warn about caveats, errors, security risks, or deprecations that are introduced after its knowledge cutoff.
The best solution that we've been able to find so far is for ChatGPT to do a search and feed the results into its context. But that has its own problems, and importantly it only works if the underlying search engines are still returning up-to-date relevant results and documentation from sites like StackOverflow.
Two things SO could do to beat ChatGPT as it exists now:
1) Require all questions and answers to include the names of tools and their version numbers. Hide Qs and As until those are added. This is so critical, I have no idea why it wasn't required since day 1.
2) Discourage answers that don't answer the question, through moderation. If you don't know the answer, don't post, or at least leave your notes as a comment.
Bonus: Stop removing chats. The number of times we see someone link to a chat that 404s is too damned high. Cf: complaints from folks about the unsearchability of Discord chats wrt software tools.
i like your idea of including versions.