@dreev said in another topic:
My own view is that the whole point of Beeminder is to disincentivize akratic derails by charging you for them. So non-akratic derails shouldn’t be charged; they’re not legit. If you know that a derail was non-akratic - that is, it’s genuinely what you wanted long-term, and you would have specified it in the fine print if you had been asked about the situation originally - why should you be charged? (I don’t believe anything will ever completely quash akrasia; there will always still be plenty of genuinely akratic derails that Beeminder will get paid from. And I’m Beemium so Beeminder is still getting paid regardless.)
The counterargument, of course, is that it’s not always easy to know if a derail is non-akratic, you can’t always trust yourself, and it’s very easy to fool yourself so you end up not meeting your goals.
But if I have to pay every single time I don’t do the task, I’m less likely to set the goal up in the first place, because that’s more of a commitment than I want to make. I don’t actually want to commit to doing the task every day - I want to commit to doing it most days, but not when there’s a non-akratic reason not to.
For me, Beeminder helps me be a little bit better, and it’s better to do the task 50% of the time - and call non-legit the other 50% - then to not set up the goal and do it at all.
You might well ask - why not just lower the rate by 50%, if I only want to do the task 50% of the time?
But I’m too akratic for that. It’s hard for me to do a task unless it’s the last possible moment, so I use up whatever buffers I have as soon as I get them. It’s beemergencies that get me to do something. Maybe there’s a way to use a meta-goal to fix that - but that doesn’t address non-akratic derails.
What are people’s thoughts? Are you ok calling non-legit when a derailment was not due to akrasia?