44

Gratitude on the Stack Exchange network is provided by means of voting (bestowing reputation). We have a Text building block dedicated to this, which perhaps explains it best: Welcome to TeX.sx! Usually, we don't put a greeting or a "thank you" in our posts. While this might seem strange at first, it is not a sign of lack of politeness, but rather part of ...


44

The StackExchange model is based round the idea that the sites are not forums, but that questions and answers should have some element of generality. As such, 'good' questions should be focussed on the matter in hand, ideally without many things that might make good forum posts. That's one reason that 'thanks' is discouraged and why community edits are ...


40

I don't think there's any particular time that one should start answering questions, and as the site become more mature, it may be harder to find questions to answer at your level that don't already have answers on the site. But there are various other ways in which you can contribute, without directly answering questions: Vote! Voting for both questions ...


32

You're dealing with people here, and some people are just different. They may not like other's removing their signatures, their "Thank You's", correcting their CaPiTaLiZaTioNS, ... Having been here for a while, I have grown accustomed to the communal attitude and nature - something that most likely guided you in your edit. That's honourable, and that's that....


30

I would suggest you first edit your question to clearly state why the answer does not solve the problem. That will bring the question to the front page again, and people who click on it will see that the issue is not resolved. If that doesn't get you better answers, you can assign a bounty. This is much more expensive than downvoting, but also a much more ...


30

I am one of those users who consistently reject removing thanks edits. The Stackoverflow people started an utopia to make the questions anonymized and general as much as possible. Thanking is considered to be somehow useless in terms of know-how. But time showed that every SE site has a different flavor and similarly we have developed a different path in ...


30

A good practice is to avoid flooding the front page. Besides that, time doesn't matter much - however if you put effort in writing a good question, and in investigating if it was already asked or not, the time period would probably not very short. Avoiding duplicates is an art which costs time, both the OP and potential answerers.


29

Adding to Werner's great explanation (coincidentally, it actually was me who wrote the text building block that he's quoting :)), here's another angle: One of my favorite aspects about tex.sx and the Stack Exchange system in general is its Wiki-like quality: (We're the asterisk in the middle!) We prefer a quite particular style of questions and asking – ...


27

A clear approach doesn't mean that everybody does it the same way, such things can happen. It also depends on who reviewed your edit: possibly the questioner rejects it, because he posted the "thanks" and wants to keep it. An experienced reviewer may accept it, because a "thanks" below the question doesn't add know-how value to the site in the long sight. ...


26

I note you have answered a question previously but had 0 votes. I just checked and your answer seemed correct so I just voted, but it was harder to check than it could have been. As for questions, it often helps to put a complete document in the answer, and to put a picture in (I just took the liberty of adding the image to your answer). If people see the ...


25

If you see a question which can be improved, go ahead and edit it. Community editing makes our site outstanding and is a reason for its quality. Of course we all should edit sensibly. And we should not edit too much in a row to not flood the front page. Btw. I don't see that it's urgent to remove a friendly "Thanks" in a new question of a new user to avoid ...


22

Every so often this sort of question comes up, and although it gets posed usually as 'etiquette' it's often more about 'policing' or 'teaching people a lesson'. Personally I think such 'policing' behaviour is never productive for the site. As others have noted in the comments, most things can be figured out by reading the documentation or Googling. But ...


22

It's OK to ask on chat but you should not expect an answer (although you may get one anyway). The Q&A site is designed for asynchronous help, you ask a question and it stays visible and can be answered by anyone at any time that they feel convenient. If you ask in chat then although the archives are available, the default site mechanics will mean that ...


21

While I can see the merit of Alan's answer, I'd like to present the opposite view: The upvote button's hover text says: "This question shows research effort; it is useful and clear [...]". There are questions that are answerable, often because missing information can be guessed or inferred, but that don't show any effort of the OP to find the answer ...


21

I don't know the details of the specific case you have in mind, but there are a few general principles that can guide you. Do not answer your question in the question Answering in the question is potentially confusing (why is there an answer already in the question? is it not good enough ...? are the answers in the answer section better than this answer?), ...


18

Ultimately, which answer is accepted is down to you, so in a sense you decide on this. That said, I would normally expect to wait 24 h after posting a question to see if there are multiple answers. Once a question is marked as 'accepted', there will be slightly less interest in checking it over from other users. At the same time, remember that you can change ...


18

Not being able to find something has its root with searching on the site. However, this itself provides a catch-22-type problem: You need to know what to and how to search properly in order to find something meaningful. Sometimes a direct Google search (appending it with the site: tag, as in site:tex.stackexchange.com) is more effective than using the ...


17

It's true that questions seem to come in clusters. When someone is starting a new latex project (designing a package, writing a thesis) they tend to have a series of questions. Recent examples are: xport and Peteris Krumins. This is not a bad thing. Nevertheless, I think 1 question per day limit (averaged) is reasonable and forces people to think carefully ...


16

I prefer that the edit isn't just "removed thanks"; however, the first thing I look at when I review an edit is the time when the message was posted. If it's less than a couple of hours I usually don't bother and accept (or improve) the edit, because the edit follows the guidelines (right or wrong, they exist). If the message is older, I accept the edit only ...


16

Here's my take on the options you give. A. Downvoting: No, as has been commented in the comments to the question, more downvoting doesn't really help. A downvote to -1 (with comments) should be enough to spur the OP to edit their question. If it doesn't the extra downvotes won't spur them on more. B. Close as unclear: No. Or certainly not immediately. It's ...


15

I think the general answer to this question is Yes: if a question is worth your while to answer, then it's worth an upvote as well.


15

We don't follow the Thanks removal rule. It is a SO thing. Some of us approve Thanks removing edits. Some don't. I don't. Some notes for future reference and responding to a hypothetical SO user arriving here. I'm not bothered with Thanks word. It's a word. Why don't we get equally bothered by those voting arrows next to the question or those colorful ...


15

Such etiquette has two main issues that I think render it useless before it makes it to the user's attention. First, we don't have an access gate before the site. So there is no way that they can know about stuff before they actually do annoying things (in your point of view :P) Had we had that kind of thing then it would be meaningful to blame them for ...


15

This happens occasionally, and the results have also been varied. In some cases, users provide multiple solutions in a single answer (example). In other instances, users may provide multiple answers, each of which provide a distinct solution approach (example query). The former scenario is more the norm in my opinion. The original question may request each ...


13

I'd like to share my two cents. One day, while answering Why were my edits rejected?, I said: Since every site is community-driven, we try to adapt things to our reality and not the other way around. Our methods would probably not work in other sites, say Math.SX or Spanish.SX. Sometimes, when I hear the words "SE policy" said in the wild, the walking ...


12

Being relatively new to the TeX.SX I have been impressed by the constructive and positive atmosphere. This reply is perhaps not directly a response to the first question but more of an extension to the discussion. I totally agree that any new question should have been preceded by some research on this site and others before being posed. Another aspect is ...


12

In my experience, the OP does not always choose a title relevant to the problem s/he's facing. Example: Tex doesn't work A poorly chosen title is, of course, forgivable in many cases; the origin of the problem may not be obvious. However, someone posting an answer that solves the OP's problem, or any subsequent visitor to the page who is savvy enough, ...


12

I think the other answers have addressed the reasons for voting to close. I would like to discuss the timing of it. There have been a couple of questions that have been closed recently that I don't think should have been closed. In both cases, it seemed that one person cast a vote to close almost as a 'knee jerk reaction'. Some people may not know that as ...


12

Recently, I couldn't come to terms with latexmk. After reading the available documentation and searching for a solution on the Internet, I posted a question here, to make sure that I wasn't missing anything. This way, I could avoid bothering the package author with a stupid question -- turned out it wasn't: When even a bounty couldn't get me an answer that I ...


Only top voted, non community-wiki answers of a minimum length are eligible