Timeline for Prevent questions on the Hot List from being upvoted by casual visitors (only rep is from association bonus)
Current License: CC BY-SA 3.0
33 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2017 at 20:39 | history | edited | Fiksdal | CC BY-SA 3.0 |
deleted 2 characters in body
|
| Sep 5, 2017 at 9:05 | history | edited | Fiksdal | CC BY-SA 3.0 |
added 14 characters in body; added 200 characters in body; added 8 characters in body
|
| Sep 5, 2017 at 7:33 | history | edited | Fiksdal | CC BY-SA 3.0 |
deleted 36 characters in body; added 23 characters in body
|
| Sep 5, 2017 at 7:27 | history | edited | Fiksdal | CC BY-SA 3.0 |
added 622 characters in body; added 68 characters in body; added 17 characters in body
|
| Apr 13, 2017 at 12:52 | history | edited | CommunityBot |
replaced http://travel.stackexchange.com/ with https://travel.stackexchange.com/
|
|
| Mar 20, 2017 at 10:30 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Oct 25, 2016 at 9:51 | history | edited | Fiksdal | CC BY-SA 3.0 |
added 1 character in body
|
| Oct 3, 2016 at 23:10 | history | edited | Fiksdal | CC BY-SA 3.0 |
deleted 10 characters in body; deleted 8 characters in body
|
| Oct 1, 2016 at 11:21 | history | edited | Fiksdal | CC BY-SA 3.0 |
added 49 characters in body; deleted 5 characters in body; added 4 characters in body
|
| Sep 30, 2016 at 9:05 | history | edited | Fiksdal | CC BY-SA 3.0 |
added 9 characters in body
|
| Sep 30, 2016 at 7:57 | comment | added | Fiksdal | @gnat I have a response in this discussion that's too long for a comment, so I posted it as an answer to the proposal you started this discussion by linking to. | |
| Sep 8, 2016 at 19:04 | history | edited | Fiksdal | CC BY-SA 3.0 |
deleted 1 character in body
|
| Aug 30, 2016 at 0:47 | history | bounty ended | DVK | ||
| Aug 25, 2016 at 21:48 | history | edited | Fiksdal | CC BY-SA 3.0 |
added 2 characters in body
|
| Aug 25, 2016 at 19:36 | comment | added | Fiksdal | @gnat Sure. I'm sure it massively increases traffic on the various sites, and drives in a bunch of new users. For example, if it wasn't for HNQ, it's possible that the only site I would be using today would be Ask Ubuntu. Increased traffic is.... uhm... good for SE. Would our suggestions limit this effect? Maybe. Or probably? But would it also enhance the credibility of the reputation system? I think yes. And I think the reputation system is extremely important to SE. But I agree with you that it probably won't be implemented. | |
| Aug 25, 2016 at 19:33 | comment | added | gnat | no suggestions are going to be implemented as long as SE management is happy about HNQ... and they told me a month or two ago that they are | |
| Aug 25, 2016 at 19:31 | comment | added | Fiksdal | @gnat Fair enough. While I still believe that the main reason for the difference in votes is because users recognize the HNQ rep problem, and are willing to sacrifice a little bit (I.E. not being able to vote on HNQs when you have never contributed at all) to solve it, I can't really prove that this is indeed the reason for the difference in votes. And neither does it matter. I have a feeling neither suggestion is going to be implemented. | |
| Aug 25, 2016 at 18:58 | comment | added | gnat | not exact details of how it works but many meta readers understand that mechanics of hot questions are complicated, many posts in hot-questions tag covered that there are lots of tricky details and changes to these are usually complicated | |
| Aug 25, 2016 at 18:52 | comment | added | Fiksdal | @gnat Oh, you are taking about the inner workings of the site. Alright, I have no idea about how that works. So you think the reason for the difference in votes is that people understand the inner workings of SE and believe this suggestion is technically unfeasible? | |
| Aug 25, 2016 at 18:49 | comment | added | gnat | current way is more like "fire and forget". Flow is rather simple, system makes the list and shoots it to main page, and further only sidebar takes shuffled questions from the page. In order for this to protect questions, system would have to do much more. At every update of the list it would have to query and update questions at every site, clean "hot mark" and reassign it. That's more complicated and involves more components (150+ sites in network and this number is constantly growing) | |
| Aug 25, 2016 at 18:40 | comment | added | Fiksdal | @gnat Uhm... What? The system knows which questions are currently in the HNQ list, because it displays them on the main page. I'm not sure I understand what you're saying. | |
| Aug 25, 2016 at 18:39 | comment | added | gnat | quoting self, "how does one tell question which is currently in hot list from one that just left it?" | |
| Aug 25, 2016 at 18:37 | comment | added | Fiksdal | @gnat All that may be the case, except for this suggestion being complicated to implement. It's quite simple to make a rule which prevents people who have never contributed a single post with a positive score from voting on HNQ. | |
| Aug 25, 2016 at 18:33 | comment | added | gnat | that's a good question. Possibly upvotes to this request more reflect sympathy than real desire to see it done. Readers may think that it's quite complicated technically and is unlikely to be implemented because of that (how does one tell question which is currently in hot list from one that just left it?). And they vote this request like an unrealistic dream, "would be cool to have but unlikely to happen". Other request is totally doable and easy to implement and that is scary. "Be careful what you dream; it really could come true" | |
| Aug 25, 2016 at 18:27 | comment | added | Fiksdal | @gnat Then why are the vote scores so different between this post and the one you linked to? I think people recognize how HNQ poses a problem to the rep system. Also, under this suggestion, you'd still be able to comment. | |
| Aug 25, 2016 at 18:22 | comment | added | gnat | I know. Unfortunately this will hardly help. Per my observations vast majority of Stack Overflow lemmings want it exactly for hot questions and they want it now. Delaying granting them privileges only in hot questions will likely make them just as unhappy as delaying on all questions at all | |
| Aug 25, 2016 at 17:56 | comment | added | Fiksdal | @gnat Interesting. I think the key difference is that this suggestion is only for questions that are currently in the HNQ. So the vast majority of questions would be just like normal. It's a targeted remedy for a specific problem. | |
| Aug 25, 2016 at 17:53 | comment | added | gnat | "- is it too much to visit site for for a day or two to unlock privileges - Yes, yes it is." (At smaller graduated sites, delay granting association bonus until at least after 2-3 days visited) | |
| Aug 25, 2016 at 13:47 | history | edited | Fiksdal | CC BY-SA 3.0 |
edited body; added 7 characters in body; added 4 characters in body; added 1 character in body
|
| Aug 25, 2016 at 12:14 | history | edited | Fiksdal | CC BY-SA 3.0 |
added 61 characters in body; edited body
|
| Aug 25, 2016 at 10:30 | history | edited | Fiksdal | CC BY-SA 3.0 |
added 293 characters in body
|
| Aug 25, 2016 at 9:43 | history | edited | Fiksdal | CC BY-SA 3.0 |
added 305 characters in body
|
| Aug 25, 2016 at 9:35 | history | answered | Fiksdal | CC BY-SA 3.0 |