Sounds like we need to go through an retag as many as is reasonably possible then blackhole the tags. OTOH, it's humerus when people say they're using "VMWare" to do XYZ, and when you ask them what software they repeat "VMWare".

I agree on preferring with hyphen

Yep, a Mod will be along to take care of this.

@balpha, yes, now if I could get a link from the front page it'd be perfect.

@Jscott, I personally like the vote to close room; It'd be nice if we just had a page that filtered all the questions with a vote to close in the last day, so we could review them easily. It would be nice if there was a 'featured' flag, or if rooms with <3 people were excluded from the list.

How about calling it SQL-SSMS or MSSQL-SSMS?

@Coredump, we've talked about code highlighting in the past and decided to leave it off as detecting the language/syntax is very error prone without the user explicitly picking.

+1 Sounds like it would fit squarely on SF; even if it belongs somewhere else, we'll move the question as appropriate.

@Robert Moir, I agree. Chopper put it best when he compared users finding us in chat to following your Banker into Walmart. The users in the examples above (in the Q) showed an obvious lack of fundamental understanding and effort. SF is by SAs for SAs (et al). When it becomes obvious the user doesn't have the most basic understanding, it's time to close or migrate (as appropriate). I'm sure would disagree, just as we get users who try to force SF into a Forum, or however they envision the site should be. Troubleshooting in chat isn't necessarily bad; these examples are medium independent.

That's it. (has to be 15)

Not seeing it now, maybe they fixed it but forgot to tag this question.

+1, and for the TL;DR crowd: Don't do it! Upvote, or if you asked the question then accept the correct answer.

Adding to John's comment, the tools and review sections are quite useful for finding outliers and helping to cleanup. Otherwise they're nothing special, anyone could collect the relevant statistics and crunch the same numbers.

Users at 15k can protect questions now too (though they have to be a certain age; maybe Mods can do it even for new questions?), not just mods (as the blog suggests). Otherwise; thank you for the updated and authoritative article!

we've mentioned several times now: This is not a forum! This is a Q&A Site, if you're looking for a forum, look elsewhere. There's an FAQ that explains all this too.

I think that would work perfectly. I'd still include some character to 'not obfuscate' it in the source code. It might also be nice if it caught strings that match (\w{5}-){4}\w{5} and changed a few random characters (or warned the user, or something...).

this has been brought up many times already; I suspect we'll see it eventually. It's just not there yet.