Page MenuHomePhabricator

We really should be able to give Tokens to comments
Closed, WontfixPublic

Description

This was a witty comment.


Event Timeline

chad raised the priority of this task from to Normal.
chad updated the task description. (Show Details)
chad added a project: Transactions.
chad added subscribers: chad, epriestley.
chad lowered the priority of this task from Normal to Wishlist.Aug 9 2014, 5:35 PM

Now that we have the context menu this is pretty feasible, technically. We could show a little:

[Most Recent Token] x 3

...to the right of the date, or between the "Via" and date:

Via Web · Aug 9 2014, 8:59 AM · ☃ x 3 | V

...and then notify the author.

I'm still overall not a huge fan of this because of how much comment "Likes" at Facebook rewarded me trolling threads instead of actually doing work or contributing anything productive, but it's now technically easy to implement and wouldn't get in the way of any product stuff. The interaction would also be much heavier than "Like" (Context MenuAward TokenSelect a Token) vs clicking "Like" which probably discourages the fluffier use cases.

Some previous discussion in T4385 and probably somewhere else that I can't immediately dig up.

Overall, my resistance to comment tokens has waned over time because of the lower technical and product barriers we now face to implementing them and the substantially constructive use we've seen of of object tokens.

How do you guys feel about this?

In T5834#7, @epriestley wrote:

I'm still overall not a huge fan of this because of how much comment "Likes" at Facebook rewarded me trolling threads instead of actually doing work or contributing anything productive...

Hahaha... I think you're a pretty rare beast who was in a pretty rare context, such that overall technical production won't be traded off for hilarity much in the wild... Rather, I think the average case will improve satisfaction for both token giver and token receiver.

My concern would be if these tokens were used to track performance, but there's nothing implicit in our product to make people want to do that / I don't think we can stop people who think that's a good idea anyway. I think we should just be careful moving forward to not encourage that and actively discourage it when appropriate.

A concern which is gone from your suggested implementation is UI bloat; this seems pretty clean.

I'm fine punting. Easy to pass now and if someone really want it later, seems there are reasonable solutions.

chad claimed this task.