Skip to main content
Super User

Timeline for Bounty system : case of bounty awarded but no acceptance

Current License: CC BY-SA 3.0

8 events
when toggle format what by license comment
Mar 20, 2017 at 10:32 history edited CommunityBot
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Apr 23, 2014 at 13:35 history edited CommunityBot
Fixup of bad MSO links to MSE links migration
Apr 23, 2014 at 9:11 history edited CommunityBot
Migration of MSO links to MSE links
Jul 12, 2012 at 5:29 comment added harrymc I do not suggest placing any restrictions - just making the bounty process more user-friendly. "Accepted→Bounty" is one way that SU corrects mistakes, double-checking this by using the grace-period. My point is that there is another possible mistake in the "Bounty→Accepted" direction. I have suggested one solution and @DMA57361 has suggested another. Whatever solution is accepted, this will only improve the user-experience on the SU site.
Jul 11, 2012 at 21:03 history edited Shog9 CC BY-SA 3.0
added 917 characters in body
Jul 11, 2012 at 20:53 comment added Shog9 @harrymc: the "accepted->bounty" concept you're referring to only applies when the bounty offerer doesn't accept a bounty and an answer is accepted during the bounty period. It certainly doesn't mandate accepting an answer, or put any other restrictions on when / how an answer can be accepted.
Jul 11, 2012 at 18:34 comment added harrymc I think you forgot that (1) bounties are subtracted up-front, and (2) this later bounty system also had problems and was re-calibrated by adding the "Accepted→Bounty" concept and the grace-period. It's very easy to create a confusing UI and lay the blame for mistakes on the stupid user - this called "read the FAQ" (RTF). It's much harder to create a UI that helps not to make the mistake in the first place - this is called "user friendly".
Jul 11, 2012 at 15:24 history answered Shog9 CC BY-SA 3.0