Here are the ideas we’ve thought of for dealing with emergencies or
other reasons you may want to flatten your yellow brick road
immediately, ie, pause your commitment contract:
Tweet or post to facebook your reason for pausing (if you’re
willing to say it publicly it’s probably legit)
Pre-specify a couple friends who have to corroborate your excuse in
order to pause your road
Explain your reason to the Beeminder founders (status quo)
Just type your excuse in a box on your graph page
The point of Beeminder of course is to bind your impetuous future
self, yet to retain as much flexibility as possible – blog.beeminder.com/flexbind – so anything that you don’t think your
future self would be inclined to abuse should suffice. At least for
the kind of users Beeminder has attracted so far – over 5000 of them
– we have learned that the SOS clause is beyond overkill. We’ve
assumed all along that #4 was a highly nonscalable stopgap, but we’re
ramen-profitable now and unfreezing people’s graphs when they derail
illegitimately takes (or could take, with slightly more streamlined
admin tools) mere minutes a day. And no one is abusing it!
So we’re inclined to stick with #4 indefinitely. What do you think?
Here are the ideas we’ve thought of for dealing with emergencies or
other reasons you may want to flatten your yellow brick road
immediately, ie, pause your commitment contract:
Tweet or post to facebook your reason for pausing (if you’re
willing to say it publicly it’s probably legit)
Pre-specify a couple friends who have to corroborate your excuse in
order to pause your road
Explain your reason to the Beeminder founders (status quo)
Just type your excuse in a box on your graph page
The point of Beeminder of course is to bind your impetuous future
self, yet to retain as much flexibility as possible – blog.beeminder.com/flexbind – so anything that you don’t think your
future self would be inclined to abuse should suffice. At least for
the kind of users Beeminder has attracted so far – over 5000 of them
– we have learned that the SOS clause is beyond overkill. We’ve
assumed all along that #4 was a highly nonscalable stopgap, but we’re
ramen-profitable now and unfreezing people’s graphs when they derail
illegitimately takes (or could take, with slightly more streamlined
admin tools) mere minutes a day. And no one is abusing it!
So we’re inclined to stick with #4 indefinitely. What do you think?