While we are discussing this change, this feature could be better applied only to lower-rep users instead of everyone (but this should probably be a feature-request).
In the meantime, I have created a temporary fix for those who are already familiar with the comment action icons and wish for them to remain hidden until the comment is hovered upon:
The DAG team says it's an intentional change, to make it more obvious especially to new users that they can flag comments. I expect it will also help with touch interfaces.
From the DAG team announcement for July:
Comment flagging improvements: To align with the new CoC we will be making various changes in how comment flagging works.
As a moderator on four subjective sites, this would be extremely helpful on subjective sites. It is a common occurrence for extended discussions to crop up on artistic and subjective sites where the end result is likely to meaningfully improve the answer, but comments is not the right place to do this.
My only option when cleaning up these discussions is ...
You have two different questions here, but the first one has an excellent reply from Robert already.
I'll address the second one, which isn't really a question at all... but it should be:
I could edit the question or write a really good answer, but that's not quite the same thing as letting someone know they handled something in a way I don't agree with.
This argument seems to be based on preventing users from trying to get easy badges (targeting the robo-reviewers) rather than making reviewing better. You have to accept that as long as there is an award, there are some people who are going to take the path of least resistance to get that badge. We will always have robo-reviewers, you can't stop or prevent ...
I started writing up this request myself before seeing it had been asked before.
This would be great.
Some people have already pointed out that stars and comment upvotes don't mean the same thing. Fair enough.
A reasonable solution might be to distinguish migration-chats as a different class of chats, with upvotes there too rather than stars.
Although I ...
The other answers are busy offering per-site solutions so I thought I could offer a networkwide SEDE query.
The query takes the top 1000 comments from each site and then presents the top 1000 of those. This top 1000 is needed to limit the time it takes to process all the records.
declare @sql nvarchar(max)
create table #result (site sysname
I'm against it for a reason that I believe hasn't been mentioned yet, but I also will present a compromise.
While the difference of up- and downvotes is a useful indicator for the quality of a post, the number of upvotes alone is also. That is simply because often people are strongly disagreeing with each other.
On top of that, a downvote is often given ...
Can users see their own comment upvote number somewhere?
Unfortunately, there is no way programmed into StackExchange, that allows you to view your comment upvotes directly. However, you can still do it by using a MySQL query that I just wrote for this purpose.
Go to your user profile on the site you wish to view comment upvotes:
In the search box on the ...
You're free to vote however you want. If you want the site to be as clutter-free as possible, then don't upvote them. If you want to reward the comment/answer an upvote since it made you smile or laugh, upvote it. The decision is yours, and the mods have no power to control how you vote or why you vote the way you do.
As for me personally, I wouldn't upvote ...
While there is some difference between stars and comment upvotes, the benefit of retaining the information about comment upvotes while transferring them to chat outweighs the drawbacks:
the information is not lost in the first place.
the comment votes are an essential part of a [supposedly healthy] discussion which happened to be in the comments, and if ...
Yes it is being recorded somewhere, but only SE developers with direct access to the database can see who really upvoted a comment. (and obviously, they won't do it without a good reason)
Same goes for questions and answers: moderators do not have access to see who voted, only to see patterns, which can help detect serial voters. Only SE devs can dig and ...
Upvoting a comment shouldn't be a sign of simply liking it. I'll let the comment upvote tooltip from the website explain:
While in practice comments are often upvoted simply because they are "liked," we shouldn't be making the association between upvoting and the intended meaning that the comment is useful any weaker. Changing the up-arrow to a ...
My bad, we should have posted something on this when we rolled it out.
As mentioned by Monica, this is an intentional change to make flagging more discoverable. We can all agree it definitely does that.
This is a work in progress and we are working on some additional changes to improve the layout of comments. These changes will build on the changes we ...
There are two problems with your proposal.
First, a star in chat does mean something different than up-voting a comment. A comment vote means usefulness, while chat votes can just mean it was important for some reason or maybe just fun.
The second thing is: not all users have an account on chat, or have the privilege to chat. That means votes aren't as ...
If you can't wait for a week for the comments to make it into SEDE you can use the StackAPI that has an endpoint on the user for comments.
If you run that with the sort on Votes, sort order descending and the filter I created to also show the body of the comment this will be the output (partial) for you:
This is true with all page state that does not force a refresh -- post votes, comment votes/flags, and new comments. If you navigate away and then use the browser back button, you don't see those latest updates even though they're there. Your browser is caching this state; there's nothing SE can do about it. (I thought we had this question, but I can't ...
Here is why I think down-voting comments could be a good idea.
I have just experienced a flame war in the comments section. A lot of answers here are arguing that a simple counter-comment is more useful than a down-vote. However, counter-comments can also lead to arguments over the two opposing views. By being allowed to down-vote, people could register ...
Every time, when moderator converts my upvoted comment into chat, it feels like I lost something important.
Community votes is like money here, it's just not nice to refuse it.
According to our CoC, we should find a way to not disturb our participants with that sort of losing.
Comment upvotes are one of the least important parts of SE's functionality, so officially it doesn't matter - you definitely won't get in any kind of trouble for upvoting these kinds of comments on your own posts. And your conscience is your own affair: you'll need to decide for yourself whether or not you'd feel bad about upvoting such comments.
What is ...
Based on the link below I am assuming that comments do not affect reputation.
Can administrators or more "powerful" users for lack of a better term affect a users reputation more than "regular" users?
(Well, some employees can manually invalidate votes that have been determined to have been cast for the wrong reasons - for example, by ...
My understanding was always that up-votes on comments was intended to be a way to represent the fact that multiple people would have written that same comment, essentially, it would prevent "me too" comments.
I came to this understanding due to the way automatically-generated comments from the review queues worked. Certain reviewing actions would leave a ...
The example is something of an old relic, but I don't think it would fly nowadays ;-)
Upvotes, however, are totally a personal and subjective matter. I mean the choice, however the officially sanctioned "rules" of upvotes are exactly what the screentip tells you -
This answer is useful
So if was useful to you, by all means up-vote.
That said, be more ...
Comment upvote may be reasonable action no matter if it's a good or bad post, because it helps to bring readers attention to important clarifications and suggestions related to the post.
On the other hand, senseless upvoting of comments in review isn't really harmless - for example, couple "robotic" votes in real bad post would pull it off the queue and ...
If you can wait till sunday, because that is when SEDE gets updated, you can run this query
select id as [Comment Link]
, postid as [Post Link]
where userid = ##userid##
order by score desc
Notice the two Magic Link columns I used, [Comment Link] and [Post Link], to have SEDE generate links to the comment and your post.
You only have 60 seconds to un-vote on a comment, as stated in this post:
1.You can un-upvote a comment within the first 60 seconds, provided you did not navigate away.
2.Once you un-upvote a comment you can not upvote it again
So this is not a bug in the Android app, it's something that all users regardless of platform, are subject to.