This seems to be about the right place to post a response to what happened in the chat room today, and in the past 6 weeks or so.
Since various names have come up, and people have posted here too, I won't make it all anonymous, but will use concrete examples instead.
I also want to stress that this is my perception of things, mine, personally, so if you ...
Although it may seem daunting to start talking in an unfamiliar room or site, The 2nd Monitor is a great room, and the friendly regulars will help you to feel right at home.
Some questions you may have:
How do I ask questions or get help with a post on the site using chat? What topics are appropriate for chat?
In The 2nd Monitor, site business always ...
Stack Exchange chat rooms are an informal discussion area that have few rules in general, and some 'rooms' have room-specific requirements as well.
In general (from the FAQ):
This site is an extension of The Stack Exchange Network, so discussion should more or less revolve around the same topics you'd find at The Stack Exchange Network — but in an ...
The 2nd Monitor
We all [hopefully - if not you're missing out!] work with at least two monitors. I noticed I keep the chat window open on my 2nd monitor [almost] all the time.
Having a 2nd monitor is also quite handy during an actual peer review. I think it makes a perfectly suited name for our chatroom: representative of our site and of how we're [I'm?] ...
I'd say that the following could be an non-exhaustive list about what's on-topic and off-topic for the CR chat, which also includes the idle chatter we should tolerate and which we should not tolerate.
The good things
Being in the room as a new user to ask a question about CodeReview, or to discuss a question/answer/comment that has been placed on the main ...
Keep the one-boxing user-like feed
This is how it works at the time of this writing. The RSS feed receives new questions every few minutes (usually around 10-15 minutes it seems), and posts each individual question link as if the feed were a regular chat user:
Easy to get a bird's eye summary of the question which allows for easier handling for ...
From the Chat FAQ (emphasis mine):
This site is an extension of The Stack Exchange Network, so discussion should more or less revolve around the same topics you'd find at The Stack Exchange Network — but in an interactive, less strictly Q&A focused way. Do have fun, but please keep it professional and always be respectful of your fellow community ...
Continue the story!
We proved it, many things can happen in a relatively short period of time. Let's first rename this chatroom to The CRonicles, and then use it to conceal various meta-things:
Links to noteworthy posts for the annual "Best-of" meta-party, using [tag:best-of-2015] for easy searching of the transcript.
Links to featured and beta-progress ...
Wait a bit longer.
11 days is not enough time to start evaluating a long-term experiment. Wait 2 more weeks and let's see if we have more cases at that time.
It could be a fluke, after all the newest of new users may not even realize what post comments are for, or how chat works, let alone the intricacies of what is on or off-topic on Code Review.
I think The Mission is about bringing down the zombie count. That's a much smaller subset than all the answers. I think all the answers would be too much. On days when users pimp several answers, that already feels too much sometimes.
Keep in mind that the main purpose of the 2nd monitor is to discuss site business. All the answers would be surely too ...
I really feel like point 4 of @Rolfl's Chat Policy is what gives way to what has been happening.
When conversation starts to get way off-topic, then the messages are moved to keep other users from thinking that The 2nd Monitor is a watercooler chat room, because it leads to a slippery slope where the "incident" may occur again.
The more users that we ...
How much idle chatter do we tolerate in the 2nd Monitor? Nearly all of it.
Unless there is site business or a programming discussion occurring. Then there is absolutely no idle chatter tolerated. None. Anything not relevant to the conversation needs to go unsaid, or be said elsewhere.
Is that an awful extreme swing? Yes. It is, but in the year that I've ...
I can think of a few reasons:
Code Review is still in its early days.
People are concentrated on the main site, don't expect much from secondary aspects of the site. If one thing is worrying is that not many people seem to participate on Meta (as the site is still shaping). Chat, I don't care about.
Code Review overlaps (in expertise & interests) with ...
According to the Talk in Chat privilege page:
When should I visit chat?
for real time collaboration
to meet the fellow members of your community in a more social environment
for less structured, casual (but still roughly on-topic) conversation
As this primarily pertains to this specific room, yes, I'd avoid going too off-topic. From what ...
Chat bot kill switch
Give room owners the ability to stop the bot by typing some key phrase. It should then either exit, or at the very least, be quite for a long time. This will allow room owners to limit the damage if a bug causes the bot to go crazy and the bot's owner is not available to take care of things.
For a phrase, pick something easy to ...
Register for Pings
Allow users to send a chat message in order to register with the bot so that the bot will alert the user when certain posts are made.
!follow tag:Objective-C -- This would register myself with the bot as following everything posted to the Objective-C tag and the bot should ping me any time a question or answer is posted ...
IMO the rules/guidelines are good like they are. I usually (like most regulars) have a browser tab open for the second monitor chat. If I am away from my desk and I see wow in the last 30 minutes there are 100 messages posted I am disappointed if I check and see sports/politics/etc. posts.
I would like to see more often a message like: We should discuss ...
I have already contacted SE regarding this concern, and this is the exact response I've received from Tim Post, an SE community manager (important points bolded by me):
To the extent that it doesn't at all annoy others in chat, we tolerate
it. Bots shouldn't send automatic greetings, say inappropriate things
(or accept inappropriately named commands) ...
The 2nd monitor improves productivity (or does it?)
Some nasty stuff which humanity is suffering from them in this very moment, actually started with good intentions.
I know English language says "The Devil is in the detail" but I have learned from experience that sometimes the Devil is the detail itself.
I honestly don't think we should propose a ...
From the Meta post that you linked to as related but not duplicate, we can see that there is a pattern in chat.
We float off-topic and need to be reigned in once in a while, roughly about once a year.
The reason for this is that there is a constant influx of new users that don't have the history that the revivalists have on our site (Code Review), so they ...
Before you read ...
Personally, I follow @TimPost's ideology:
My 'razor' for such things (well, actually most things) "When in doubt, don't."
I would even say I've deleted or stopped writing what I was going to post more times than I've actually posted.
As @rolfl pointed out, I've been off-topic more than once or twice, but I just step out:
Why don't you visit The 2nd Monitor and find out for yourself?
Alongside idle chit-chat, it is indeed an effective method of helping each other with code reviews. Granted, they are small (most of it has to be done on the main site), but they usually involve extended conversations that wouldn't be ideal for post comments. If a particular question requires ...
I think that you can go as far as you want in chat, assuming nobody there complains.
Otherwise, I don't see any harm in being off-topic there.
And if somebody complains, just move the discussion to another room.
Users who are regulars here are going to know other users who are regulars, and may feel strongly obliged to vote on another regular's answer if they seed it come up in the feed. This leads to falsely-earned reputation.
Chat is a privilege, not a right. It is a system in place for the civil discussion of whatever the topic is for the chat room (as long as it fits in the general "be nice policy" too).
You were repeatedly flagging a specific user's posts as spam/offensive, and the posts were not. This is considered to be flag abuse.
Sure, you could have been warned, which ...
I believe one-boxing occurs when it is being posted by one of the chat feed bots. But one-boxing when it is something you post yourself does not happen.
It is not the blog post itself that oneboxes, but the RSS-feed item posted by the chat feed bots.