@tink Please don't leave non-English comments, even if you're trying to be helpful. The rule that all content must be in English applies to everyone, no matter who "started" posting the non-English content.

Moderators will delete non-English posts on sight, including comments.

Yeah, that's possible. Unfortunately, there isn't a lot we can do to help people who are well and truly clueless.

I will generally close non-English questions as off-topic with a custom reason, instead of just "unclear what you're asking". (And especially now that the verbiage for that reason has been changed.)

Some people will suggest asking on es.so, but I don't do that because: (1) it's too hard for me to tell exactly which language is it (e.g., is it Spanish or Portuguese?), and (2) I won't recommend migration/re-asking for crap questions, and if I can't read the question, I don't know whether or not it's crap.

@EJoshuaS-ReinstateMonica There is no point in deleting a question that is "too broad" less than an hour after it was closed. The asker should have a chance to edit. That is, after all, the whole point of closure.

@JL2210 they are "soft" off-topic, if you will. The community has determined that, since they're not about programming but rather about law, and because we have a site specifically dedicated to law/legal compliance questions, that such questions are off-topic on Stack Overflow.

Ideally license or TOA, etc. questions should be asked directly of the company/organization, though.

@Vega IMO, installation of programming-related tools is not enough to fall under the 'programming-related' umbrella. That umbrella covers use of said tools. Installation is purely "general use" unless you're somehow programmatically installing it...

so I look and all I see are four holes in the motherboard itself, so I'm thinking "well maybe they screw in there and it's OK?" But I try a bit more and I'm like "no I can't get this to reach even with tilting that side of the heatsink/fan to reach it"

and at this point I'm worried that the wraith for the R3 has different requirements from the wraith for the R5 for how it attaches, because the picture in the little install booklet had the motherboard with two little plastic side mounts for the fan, like older mobos

so at this point I'm thinking "crap, I don't know if I have some of those at all, and if I do I don't know where I would've put them"

but then I look closer at the motherboard and I'm thinking "surely the R3 cooler was not just screwed into those wafer-thin holes... they wouldn't reach and even if they did they have no threads or anything to screw in to

luckily I have the idea to lift the case of my computer a bit and tilt it back and forth

Sure enough, I hear something sliding around a bit underneath the mobo

so I take everything out of the motherboard and then unscrew it from the computer and pull it out. Luckily the back plate is still perfectly intact. So I stick it back on the back of the mother board while it's still out of the case, and, while holding the two things together in one hand, screw down the heatsink/fan with my other hand

So I go back to Gigabyte's drivers webpage and look at the BIOS firmware list. I am on r40 (up from r6 before I bought the Ryzen 5) which is the minimum needed for Ryzen 3rd-gen support.

Turns out, revision 41 or 43 or something has listed "improved M.2 support" which I definitely read before hand, but at the time I thought "my M.2 SSD works just fine right now, I don't need that". Turns out they meant "M.2 support for 3rd gen Ryzen, period" instead.

Don't feel to bad. I have all my fans connected via commander pro's and I'm not liking that, I don't want to have to use iQue to adjust all my fans. I'm going to get PWM splitters and run them to the MB instead so I can use the ASUS fan expert.

though when I did initially upgrade to Ryzen I had to go buy a PS/2 keyboard to get through setup because I was still running Windows 7. And I had to hack the update process to still get updates for a while

@Das_Geek It is really nice. So many configuration options. Cable management is pretty good as well. My only suggestion is you might need longer power cables depending on how you route them. I'm ordering a set from cable mod and I'm going to get the EPS and 24 pin cables a little longer so they route better

@SecretAgentMan looks like they found it unsatisfactory that their question wasn't reopened after translating, and simply re-posted it. Simply flag as a duplicate. If the original is reopen-worthy, vote as such, if not: tell them how to improve it before reopening.

@NathanOliver-ReinstateMonica whoa, did I just observe you using proper units?

@Das_Geek No problem. The top of the case has a radiator tray and what you'll do it take that out, bolt the radiator to it, and then you can drop the whole thing into the case and reattach the radiator mount with 4 screws. This makes doing the cable management and fan install real easy.

@SecretAgentMan it's confusing; agree. The exception to "already has an answer" is a self-dupe, since that's usually the OP not understanding the system (either through on-purpose rule flaunting of reposting, or simple misunderstanding of the edit concept)

@NathanOliver-ReinstateMonica Looks like we have the same AIO. Did you buy any fans in addition to what came with the case? I read about the fancy "silent maglev" Corsair fans, but idk how much of that is gimmick jargon

I bought 9 LL fans. I wanted the ML but microcenter was out of them. AFAIK the ML fans are quiter and have the same performance. I took the 3 140mm fans out that came with the case since they were not RGB.

@NathanOliver-ReinstateMonica wierd, especially since it's not "Highly active" in this case, it's just protected :s Especially since the help centre still calls them "protected" and not "highly active"

@NathanOliver-ReinstateMonica Debating whether or not to embrace the RGB. The AIO and RAM I got have them, but I only got them because they were good deals. Something blue-related since my mouse/keeb combo is blue-backlit

@NathanOliver-ReinstateMonica nice. I have stock fans in my R5 (well, one replacement 140mm I think) on the back and side and two in the front, then I have the top two grill plates removed for air flow

@treyBake Both Needs more details or clarity and I'm voting to close this question because it is not English. are OK reasons to close non-English questions, see meta.stackoverflow.com/a/297680/3744182. With the recent description changes I sometimes forget which standard close reason to use, so I went with the allowed custom reason.

@Adriaan While I agree it's unlikely that the OP will come back to translate, I didn't see the harm in leaving that for the Roomba. Was there a reason it needed to be deleted now? After all, the point of having a 5 day period after closure where an edit puts the question in the reopen queue (i.e. what used to be called "on-hold") is to provide for the opportunity for the question to be edited into shape.

@Makyen to tell the OP, and specifically the person who answered, that it is not OK to ask/answer non-English content. Now it's still fresh in their memory, whereas when you leave this to roomba, tehy'll just ask/answer again in non-English

@Adriaan Given users aren't notified about posts being deleted, and once posts are deleted, they are significantly harder for OPs to find, I don't see deleting it now as sending much of a signal. More effective at sending a message would be a comment on the post. The user gets a notification of the comment in their inbox. If they haven't picked up the inbox notification within a period of time, they haven't disabled it, then they get sent an email. Deleting it just makes it quietly go away.

@treyBake Please note that, in the vast majority of cases, no comment is required. I'm not a big fan of auto-comment scripts, because they just end up creating more noise. If you're casting a vote to close, you should not leave a canned comment---the closure will already result in a canned notice. Only leave a comment if you're going to take the time to type up tailored advice that is specific to the post.

Canned comments are sometimes useful, like in cases where you're rolling back vandalism and asking the user not to do so in the future. But please think very carefully before you start posting automatic canned comments.

FWIW, I always close foreign-language questions using a custom reason, which will create an explanatory comment. "Unclear what you're asking" does fit the bill, but isn't nearly clear enough, especially not anymore after it's been reworded. Note that the auto-comments script will allow you to insert custom close reasons, which is nice for this.

@Dharman Generally, no. In 99% of cases where you're flagging something as NAA, it's patently obvious why it fails to answer the question. And remember that deleted answers get a system-inserted link to stackoverflow.com/help/deleted-answers, which is good enough.

Leaving the comment just means that, in the event that a post gets fixed, there's an obsolete comment hanging around.

I'd follow the same advice, and only post a comment on NAA if you are tailoring it to the actual answer, and giving specific advice on how it can be improved.

From my experience in SOBotics I arrived at a completely opposite conclusion. The canned comments often are useful. Sometimes OP does not realize that they broke some rules and posting a comment makes them realize that this should not be an answer and they delete it themselves without the queue or mods intervening

Sometimes they even reply and ask for extra information or what is even better the canned comments make them edit the answer into a proper post and I can retract my flag.

@Dharman This may be an example of the cases I referred to in a previous message as "borderline".

But that's also something that makes me uncomfortable about it. These canned comments basically empower a single person to make what appears to be an authoritative statement, and quite often in /review, single persons are wrong. I would hate to have a wrong reviewer's decision to leave a comment effectively bully someone into deleting a valid answer.

I would much prefer that a reviewer silently raise a flag, and then either allow a consensus to be reached or a mod to agree. The problem will then get resolved with a minimum amount of fuss.

@HovercraftFullOfEels For questions like that, where you're voting to close as "unclear", it is highly recommended to leave a comment explaining exactly what is unclear. It is rather unlikely that the asker is going to understand why their question is unclear.

@CodyGray I would temper your feelings of discomfort by assuring you that, at least through Natty and the SOBotics channel, reviewers rarely act alone; disputed posts are talked about and a consensus reached. These disputes are of course fairly rare, because as you stated posts which are caught by these filters are generally glaringly terrible.

I would also note that these autocomments contain links to established Meta or official FAQ pages, which can help guide a user to correct their post before being downvoted. While in many cases it ends up as useless noise and the post gets removed, I would submit that this noise is worth it for the times it proves helpful. Especially because they are only comments, and can be removed without a fuss.

@CodyGray Hm, maybe I didn't clarify properly. I was referring to the case raised by Dharman, mentioning the use of autocomments when going through the SOBotics queue. My point was to say that at least these comments weren't from some random user on a soapbox, but instead from a carefully-scrutinized list of feedback. Similar in nature to the /review queues.

I don't really know what to say to that. I must be misunderstanding something. There are auto comments in the review queues that reviewers can choose to insert. Given how often reviewers make the wrong decision, there is little reassurance to be found. I don't know how any of that interacts with SOBotics. If that's a separate channel outside of /review, then it doesn't really apply to this discussion.

@Machavity That queue is a completely different story. These reviews are very often conflicting and wrong stuff gets approved. LQP queue is generally handled better. I started randomly auditing the reviews and most of them I agree with.

@CodyGray My apologies, it appears I was misunderstanding the conversation. I had thought the topic had temporarily shifted to discussing the usefulness of autocomments from a particular source rather than in general

@Machavity I'm with Dharman on that one. From what I've seen, as I cannot access that queue directly and can only look at the contested edits detected by the bots, it's much easier to get away with robo-reviewing edits than it would be for other types of post.

That being said, I agree with your point. Especially considering the incentives that exist for completing review tasks.

You might be able to make the argument that the typical member of SOBotics is (A) more diligent, (B) more dedicated, (C) more familiar with our guidelines/expectations/standards, but I still don't think auto-comments are a good idea.

The thing about auto comments is, if they were such a good idea, they could be automatically generated by the system.

Which would mean that nobody would have to do any work, and you wouldn't have the problem of retaliation.

Auto-comments also bring more information to the /review. Consider this NAA Without any comments it is not clear why would anyone flag it, but If I said in the comments that this is supposed to be a comment under another answer then the reviewers know what to look for. I guess this falls under the borderline cases mentioned by Cody

I think the confusion is that there are multiple sets of "autocomments". There are some canned comments which the LQP review queue strongly implies users should select to leave on the post they are reviewing. The primary thing I find helpful about those comments is that they have a "From Review", which can be used when viewing the post to go directly to the review. Other than that, I find these comments to mostly not be helpful.

The main thing that I've seen called "autocomments" are comments people place on posts through the use of tools which give them a set of comments to use. The most common tool is autoreviewcomments. Such comments can be good or bad, depending on the comment and the post the user places it on. As always, each individual is responsible for the comments they make, regardless of if tools helped them do so.

Personally, I've had many instances where an autocomment I've placed has resulted in the post being edited by the OP to the point where it's good quality. There have been many times when I've been thanked by the OP for providing them with the information in the comment.

But, again, it's primarily about the actual comment, how it's used, and the circumstances of the individual post. It's certainly true that people do abuse autocomments. There are a significant number of them where the person who wrote them has put no care into it, at all. Some are even unfriendly/unkind.

Of course. I said as much in what started this conversation. And, like Makyen, when I said "autocomments", I was thinking of both the ones that can be automatically generated "From Review", and the ones that can be inserted via the use of a userscript. In the vast majority of cases, these are noise. But they can be used strategically, so I'm not trying to abolish the tool.

@CodyGray Without a comment, that now-deleted post could have been misconstrued as trying to say "Try this command. It worked for me". While not super borderline, I do agree with Dharman that there are cases where a comment is useful. That being said, the same argument could be made that it's less than useful, in the case that the initial reviewer was wrong

I agree. It's not explicitly asking for recommendations; it just happens to be that the answer is a vim plugin or similar. I would say 50% of the Vim answers I write include some link to a plugin; that's just how Vim be.

Because there are 2 different banners. One for closed that says edit to make better, and one for locked that says it's locked. Apparently the devs didn't think there were any closed locked questions where this would lead to issues ;)

I personally like not showing the user who voted to close or lock in the banner. It isn’t relevant, and just leads to retaliatory behavior. For transparency, it’s important that it be publicly available information, but it is. We all know how to find it if we need it.

But I saw and +1’ed Tyler’s bug report. There are a lot of issues with the post notices still. They really should have shown them to mods as a smoke test first.

Now that there is less traffic in this room, could we have another tag e.g. old and let some posts without recent activity in? If we dedicate a new tag for it, only people who have some spare votes at the end of UTC day can go focus on these requests.

@TylerH Honestly, if things were working as they should, they should defeat the point of this room. The close vote review queue should be solving this problem. This room could be recast into something that provides nothing more than advice from fellow quality-minded users and the occasional mod.

The fact that we need this room at all is an unfortunate consequence of (a) huge volumes and (b) ineffective tooling.

@Dharman If you're just looking for questions to close-vote, then there are lots of ways to find them. Even if you're out of CV-reviews, you can still work on the CV review queue. You can look at the review history and pick questions which you haven't VtC. This would help clear the queue. There are as many questions as you'd ever want in the history there.

There are also lots of searches that result in a high percentage of older, off-topic questions. Some searches I've used are "looking for" in combination with things like API, book, library,

module, plugin, open source, etc., etc. There are many other searches with other search terms which result in a high percentage of questions which are easy to see should be closed.

NOTE: Not all of the questions in the above searches, or any search, should actually be closed. Good searches for this purpose just have a high percentage of questions which should be closed, but not all. You still need to use judgement wrt. voting to close.

I've even done searches for various non-English words to find old non-English questions which were never closed. There are, unfortunately, a surprising number non-English questions still around, some from many years ago.