Beeminder
Reminders with a sting
OpenAI’s Deep Research tool was made available to premium users the other day and I tried it out with the following prompt:
“What does the science say about Beeminder’s efficacy?”
It asked a couple followup questions (Beeminder specifically? No. Any specific outcome measures in mind? Also no.) and then it thought for 6 minutes and churned out a report. I’m quoting it in its entirety (for Science!) with my reactions interspersed. But I’m mercifully collapsing most of it so you can mostly just read my comments and reactions. (The only edits I’ve made to the AI’s words is replacing repeat citations with “[ibid.]”.)
See the Beeminder blog for the rest.
This is actually a tiny feature, but we've been neglecting updates here on IndieHackers so we're just diving back in with the latest thing we've done. Excerpt from the blog post:
In a recent poll of most annoying things about Beeminder graphs there was a surprise winner. People really want to specify the plot range of their graphs using relative dates. Like always showing just the most recent month of data on the graph. Well, your wish is (sometimes, when we feel like it) our command.
Imagine if signing up for Beeminder meant committing to use Beeminder. As part of signing up, you’d create a meta goal measuring the number of total datapoints added on all your other goals. Now the clock would be ticking to get an object-level goal created and to start adding data to it!
That vision may be reality soon, now that we have a rough version of a Beeminder Meta integration. In the meantime, we’ll let you power users set up such goals yourselves if you want them. We do think it makes for a nice Quantified Self metric, to see a graph of the total number of datapoints you’re adding across all your goals.
Backing up, the Meta integration means treating Beeminder itself as an official integration where the metric is “number of datapoints added on any of a list of Beeminder graphs”.
Read more at https://blog.beeminder.com/metamind/
We killed weaselproofing and introduced No-Excuses Mode instead.
The whole story is on the blog -- https://blog.beeminder.com/noexcuses/ -- but here's the very short version of what No-Excuses Mode means:
- You can’t call non-legit on a derailment unless there was a Beeminder bug
- The closing of various loopholes with autodata
- You can’t delete the goal even in the first week
Official announcement and overview of both Beeminder and Focusmate at https://blog.beeminder.com/focusmate/
Next will probably be FreeCodeCamp!
Help us prioritize other autodata integrations at Candidates for next integrations at https://beeminder.consider.it
The latest of our dozens of autodata integrations.
More on our blog: https://blog.beeminder.com/codecombat/
Previous integrations include: Strava, RescueTime, Complice, GitHub, Gmail, Habitica, Todoist, Duolingo, Zapier, IFTTT, Withings, Twitter, Trello, Skritter, Pocket, Runkeeper, Sleep As Android, Draft, Fitbit, Garmin, Apple Health, Slack, Toggl, Clozemaster, Project Euler, TaskRatchet, Boss As A Service, and Integromat.
Candidates for next integrations at https://beeminder.consider.it
Beeminder's origin story: In 2005 when I was scrambling to get my PhD thesis written and Bee Soule, who I had recently met and, obviously, fallen head-over-heels for, concocted what she dubbed the Voluntary Harassment Program to keep me churning out chapters. That was a smashing success and we continued to experiment on ourselves with crazy incentive schemes and productivity hacks until 2008 when we started getting friends and family in on the fun, with what we called Kibotzer -- the kibitzing robot -- which was an early incarnation of Beeminder...
1 Comment
Hey would you like to connect?