I propose that when you create a new autodata goal, Beeminder should fetch the last week of data and show it to you like this, where your actual bright red line doesn’t start till today, when the goal was created:
- It reassures you that autofetching works
- It gives you guidance on how to dial your red line, since you can see what you’ve averaged over the past week
- It’s consistent with the rule we want to adopt/universalize, that every autofetch syncs the last week of autodata, treating the autodata source as ground truth
- If there’s no data to fetch, it might look weird? Would it be too magical to set the tmin (aka x-min) conditional on if there’s past data to show? Probably. Dynagraphs may make such questions moot.
- Should step 1 be to make sure we do this consistently and correctly for all autodata integrations without showing the pre-creation week (ie, tmin=today) and then we can worry about the tmin question? This one is pretty much answering itself.
- Would something similar to this be nice for restarting archived goals?
PS: You can already make your graph look like the above example for some autodata goals just by setting your x-min (aka tmin) to a week before you created the goal.
PPS: Or better yet, go to graph.beeminder.com and just zoom out a little.