| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0004994 | Site | forum | public | 2015-11-11 11:34 | 2016-06-07 17:07 | ||||
| Reporter | gajop | ||||||||
| Assigned To | gajop | ||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||
| Status | resolved | Resolution | fixed | ||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0004994: Add post (up)voting system | ||||||||
| Description | A post upvoting system would be useful. I'd limit it to upvoting only as it should be used to encourage a positive atmosphere which downvotes never do. In case of disagreements it would probably be best to write it anyway. A voting system also reduces "spam" posts that just agree with previous opinion or express amazement/encouragement. Recent examples: - https://springrts.com/phpbb/viewtopic.php?f=12&t=34024#p573898 - https://springrts.com/phpbb/viewtopic.php?f=1&t=34026#p573919 - https://springrts.com/phpbb/viewtopic.php?f=1&t=34026#p573921 - https://springrts.com/phpbb/viewtopic.php?f=1&t=34026#p573924 These are of course not damaging as it is, but it's likely more people would do upvotes instead as it doesn't disrupt discussions as posts do. At the minimum, it should provide the same functionalities as most modern Social Network upvoting systems do. The list of requirements would be: - Upvote any visible post once (when logged in). - It's visible how many upvotes were received per post, and who issued them. - There's a notification for each upvote. I did some research and found it that "Post Love" extension does just that: https://www.phpbb.com/community/viewtopic.php?f=456&t=2246576 and https://github.com/satanasov/postlove . It seems relatively stable despite being in testing for very long (apparently the author is reluctant to go through the arduous acceptance process). Here are some of the screenshots demonstrating example usage: - Upvoted post: http://i.imgur.com/ewU32UH.png - User that upvoted it showed as popup: http://i.imgur.com/nWyF0xE.png - PHPBB notification received by the poster user: http://i.imgur.com/uv6HrKG.png - Additional ability to see all likes sent/received by a user in their profile: http://i.imgur.com/1OZ85f4.png Thoughts? | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
2015-11-13 18:31 |
If you want to show your agreement to something then at least post WHY you agree. If you are unable to express your thoughts in more detail than "lol +1" why should anyone care what you think? Votes have even less meaning, others might assume you are just clicking random buttons without thought. Imo superfluous and step in wrong direction. It is better to explain WHY you agree, or show your agreement by using [thing] or posting an idea how to further improve it. If the whole post can be summarized as "+1" then there is no thought in it, no use to post it, and 'upvoting' is hollow and meaningless. > "Additional ability to see all likes sent/received by a user in their profile" That is simply a secondary postcounter that always increases. Use? The first step in optiziming is looking where to optimize. (The "+1 posts" make up the smallest part of user-posted spam and distrubtions.) |
|
abma (administrator) 2015-11-16 11:39 |
@knorke: you didn't read what gajop wrote: > These are of course not damaging as it is, but it's likely more people would do upvotes instead as it doesn't disrupt discussions as posts do. vs. > It is better to explain WHY you agree, or show your agreement by using [thing] or posting an idea how to further improve it. > If the whole post can be summarized as "+1" then there is no thought in it, no use to post it, and 'upvoting' is hollow and meaningless. nobody will prevent you from replying when you want to give additional info. "Post Love" just additionally allows to agree without disrupting conversations. if it works well or not must be tested as there are no good arguments for or against it imo. > The first step in optiziming is looking where to optimize. thats exactly whats tried with "post love". personally i would like to see a downvote, too but... it must be tested. :) |
|
gajop (developer) 2015-11-16 14:46 |
Sorry, forgot to respond to your initial post, but I mostly agree with abma. I think it's often redundant to say why you agree with the OP as the pros are self evident (most usually being the content itself). Downvotes is what I think need more explanations, and I really don't want it to be used for forum fueds or noob bashing which I think would be the majority of use cases in springrts. Filtering low-quality posts that you may want on large news feed sites like Slashdot is simply not our domain nor I'd it on our scale. |
|
2015-11-16 16:34 |
I read everything, but I see no use. If it is a trick to prevent "+1 spam" then what is the use to keep count of the votes in profiles? At best there is no use, at worse it gets used to show off. (like postcount or reg date) If you want to stop spam (of all kind) then remind users of forumrules/etiquette. (https://springrts.com/wiki/Forum_Etiquette#Just_because_you_spam => "me too") This is ineffective eyewash. |
|
gajop (developer) 2015-11-16 22:56 |
You still want +1s as they are used to encourage/support people's work/ideas. The history is useful for a variety of reasons, such as not being able to remember what you last upvoted or who last upvoted something of yours. I don't feel I need to provide any stronger arguments for something that is commonly used throughout the Web. I'm however willing to discuss slight modifications to the proposed system. |
|
abma (administrator) 2016-06-07 17:07 |
https://github.com/spring/spring-website/commit/92f82c99d263a5b0c5573179f31f52a9038279b1 |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-11-11 11:34 | gajop | New Issue | |
| 2015-11-13 18:31 |
|
Note Added: 0015328 | |
| 2015-11-16 11:39 | abma | Note Added: 0015331 | |
| 2015-11-16 14:46 | gajop | Note Added: 0015332 | |
| 2015-11-16 16:34 |
|
Note Added: 0015333 | |
| 2015-11-16 22:56 | gajop | Note Added: 0015334 | |
| 2016-06-07 17:07 | abma | Note Added: 0016408 | |
| 2016-06-07 17:07 | abma | Status | new => resolved |
| 2016-06-07 17:07 | abma | Resolution | open => fixed |
| 2016-06-07 17:07 | abma | Assigned To | => gajop |
| Issue History |