Love that hyper-vigilance! We almost had a built-in policy of not
auto-rerailing if no data has been entered since the last derailment
but we decided that if you know that’s the automatic policy then
it’s too tempting of a weasel loophole. Stick your head even deeper in
the sand and the problem goes away!
Instead, since it’s rare, we just have the system send us an email and
we try to personally bug you to make sure you didn’t actually die or
something. We really don’t want to collect money from
dead/incapacitated people so for now you just have our personal
guarantee that we won’t let that happen. When it’s common enough that
we can’t personally deal with each case we’ll set up an automatic
policy.
Maybe the automatic policy could be that if there’s been no data for
too long then we uncheck the precommit-to-recommit for you, maybe each
day or each derailment we do so with some probability, so you never
know when the box will uncheck itself.
So, I have a question that will reveal my tendency towards
hyper-vigilance… I really like the idea, but am nervous about the
implications of something like a major personal crisis on my credit card
(…or if you turn “major” up quite a lot, on my estate!). What kind of
safety features are in place if someone just stops entering data? This has
been the reason that I’ve avoided ever checking that box.
On Tuesday, March 12, 2013 6:36:26 AM UTC-4, boardtc wrote:
Ahh! I can identify with the meta contract idea, I had not come up with it
myself but I knew I needed something.
For me this ties in with having a continue option when restarting a
derailment, as restarting is too cumbersome at the minute imho, and so I
have let some slide.
I would suggest the next level each time is adding another increment of
the initial pledge rather than a double/triple.
Tom.
On Monday, 30 April 2012 06:12:03 UTC+1, Daniel Reeves wrote:
You automatically advance to the next pledge level when you derail.
I.e., by default you automatically re-pledge (at triple the previous
pledge) unless you explicitly opt-out. Starting a yellow brick road
means you’re committed till you reach the goal or explicitly cry
uncle. [2]
We’re thinking this may be the Third Great Beeminder Epiphany… For
those keeping track:
First Great Beeminder Epiphany: The Yellow Brick Road [3]
Second Great Beeminder Epiphany: The Akrasia Horizon [4]
Tentative name for this one:
The Weasel Principle [6]
[6] So called because the heart of the epiphany is that Beeminder
users are distinctly unweasel-y (for example, they won’t falsify their
data to avoid coughing up a pledge). They don’t commit weasel-y acts
– they’re not weasels of commission – but they are surely weasels of
omission. The lightbulb moment was when a user set up a meta
commitment contract to impose penalties on themself for not unfreezing
derailed goals. I realized that that would probably only work if those
penalties were automated.
Maybe the eventual automatic could be if there’s no data on ~any~ goal that
day, hold off until the next time there’s data on something. So that if
someone’s not logging in at all (rather than just not entering data on a
single graph) that gets flagged as a “hold off” scenario. I suspect that
the people who are interested in clicking the auto-recommit probably have
more than one graph anyway, in most cases.
Meanwhile, knowing your policy, I’m heading to click auto-recommit on all
of my graphs this instant.
On Saturday, April 13, 2013 4:09:41 PM UTC-4, Daniel Reeves wrote:
Love that hyper-vigilance! We almost had a built-in policy of not
auto-rerailing if no data has been entered since the last derailment
but we decided that if you know that’s the automatic policy then
it’s too tempting of a weasel loophole. Stick your head even deeper in
the sand and the problem goes away!
Instead, since it’s rare, we just have the system send us an email and
we try to personally bug you to make sure you didn’t actually die or
something. We really don’t want to collect money from
dead/incapacitated people so for now you just have our personal
guarantee that we won’t let that happen. When it’s common enough that
we can’t personally deal with each case we’ll set up an automatic
policy.
Maybe the automatic policy could be that if there’s been no data for
too long then we uncheck the precommit-to-recommit for you, maybe each
day or each derailment we do so with some probability, so you never
know when the box will uncheck itself.
On Sat, Apr 13, 2013 at 12:45 PM, Essentiae <mary.d...@gmail.com<javascript:>>
wrote:
So, I have a question that will reveal my tendency towards
hyper-vigilance… I really like the idea, but am nervous about the
implications of something like a major personal crisis on my credit card
(…or if you turn “major” up quite a lot, on my estate!). What kind of
safety features are in place if someone just stops entering data? This
has
been the reason that I’ve avoided ever checking that box.
On Tuesday, March 12, 2013 6:36:26 AM UTC-4, boardtc wrote:
Ahh! I can identify with the meta contract idea, I had not come up with
it
myself but I knew I needed something.
For me this ties in with having a continue option when restarting a
derailment, as restarting is too cumbersome at the minute imho, and so
I
have let some slide.
I would suggest the next level each time is adding another increment of
the initial pledge rather than a double/triple.
Tom.
On Monday, 30 April 2012 06:12:03 UTC+1, Daniel Reeves wrote:
You automatically advance to the next pledge level when you derail.
I.e., by default you automatically re-pledge (at triple the previous
pledge) unless you explicitly opt-out. Starting a yellow brick road
means you’re committed till you reach the goal or explicitly cry
uncle. [2]
We’re thinking this may be the Third Great Beeminder Epiphany… For
those keeping track:
First Great Beeminder Epiphany: The Yellow Brick Road [3]
Second Great Beeminder Epiphany: The Akrasia Horizon [4]
Tentative name for this one:
The Weasel Principle [6]
[6] So called because the heart of the epiphany is that Beeminder
users are distinctly unweasel-y (for example, they won’t falsify their
data to avoid coughing up a pledge). They don’t commit weasel-y acts
– they’re not weasels of commission – but they are surely weasels of
omission. The lightbulb moment was when a user set up a meta
commitment contract to impose penalties on themself for not unfreezing
derailed goals. I realized that that would probably only work if those
penalties were automated.
–
You received this message because you are subscribed to the Google
Groups
“Akratics Anonymous” group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to akratics+u...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
