why is it that so many veteran users are set on putting down questions from new users?
Let me counter that with a question for you to answer: Why do so many new users assume bad faith of veteran users?
Within the first five minutes of me asking a question(and this might be someone else's experience), mods and veteran users immediately downvote and mark ...
I do apologise.
The question was brought to my attention and while investigating it I spotted that there were a number of obsolete comments on the answer which I deleted.
I then noticed that the other comments replied using your old name which I thought might not be a good idea so I edited them to use your current name. It was only after I'd done it that ...
According to SO developer Adam Lear (ref), this was not an intentional change. The devs were doing some work in that area which introduced an error in permission checks. Apologies for the inconvenience; this should be fixed shortly.
The thing to focus on is not that the other question is 10 years old, but do the answers to that question solve my problem.
If they do then great, you've got what you came for. If not edit your question to explain why so we can get it reopened and try again.
Try to remember we're here to help and also we're here to try to create a library of great ...
No, that's not where comment upvotes are for:
When you vote up, you are moving that content "up" so it will be seen by more people.
If it's really helpful, the relevant information should be edited into the question or answer, and the comment should be deleted, not upvoted.
Upvoting comments only has benefits when there are many of them
Upvotes on ...
If a question or answer still needs improvement then I do not think that it matters how old it is when the next comment is made there.
I would rather see the odd unseen comment made, rather than have a comment discouraged from being made where a clarification sought belatedly might lead to a post becoming more upvoted due to its having been improved.
I want to answer a question,
but I need clarification from the author first.
Yes, we're sorry. Not all questions that get posted are of substantial quality and the guidance we have for users is either scattered around, inconclusive, presented after the fact and unclear on how to proceed. The work to get that fixed has been started but might ...
The original poster of the question, a bone fide "New contributor", used an answer to reply to questions asked in comments. This is pretty common. What they had also done, which I just glanced at, was try to ping multiple other users in the question, like:
@bob: Yeah the widget is defunct. @trace-E: I don't understand.
@themaster: Thanks for the tip!
This is a user-script bug.
The "Purge all" button and the way it updates the UI is different from how the moderator menu does it.
When the moderator menu purges comments, it follows it with a call to StackExchange.moderator.loadAllComments($post) which is mostly just a wrapper around StackExchange.comments.loadAll($post, '?includeDeleted=true'). This ...
Fixed by Aaron: Question's first two line and the upvote arrow are clamped
The root cause here was a different change made to temporarily prevent scrolling at small screen sizes. The root cause of the scrolling was the new Share pop-up. With that identified (albeit not yet fixed), the temporary fix can be removed (and a small pile of related bugs ...
To me it seems like the Comments table has information about the parent PostId such that we can make it work like this:
COUNT(a.Id), a.PostId AS [Post Link], b.Score
FROM Comments a inner join Posts b ON b.Id = a.PostId
WHERE a.creationdate >= '8/1/2010'
GROUP BY a.PostId, b.Score
ORDER BY COUNT(a.Id) DESC
What you want to do is use the STRING_AGG() function to concatenate the comments together.
Select posts.id, STRING_AGG(comments.text,' | ') from posts
join comments on postid =posts.id
where posts.id = 17406
group by posts.id
The second parameter of the STRING_AGG() function is the separator between the comments.
You can create a pivot query. The first column will be the postid and then every next column will hold the comments. To make this work you'll need as much columns as the maximum number of comments under one post. This query
select max([commentcount]) [max comment count]
shows we need 157 columns to cover all those comments.
Here is the SEDE ...
This is a privilege escalation attack, plain and simple. Using this, a non-moderator user can instruct the Community ♦ user to take disciplinary action against other users. In fact, they can probably answer ban other users under the right conditions. It's also difficult for moderators to detect when this is going on unless they're specifically looking for it ...
Comments have a different markdown from answers, which serves to make things more difficult to learn and remember. If you want to show multiple spaces it can be difficult for the reader to count them, because they are different widths when different fonts are used.
One solution is to replace multiple spaces with the blank (␣ or ␣) character.
So, first, "lively discussion" shouldn't be sticking around for years. Comments are intended to be temporary notices for improving the post and then removed after their usefulness is done. So, generally, this whole problem case doesn't occur if cleanup is happening regularly.
The age of the answer/comments is not going to be a good predictor of how likely ...