I’ve been beeminding for a long time, and I have many goals have a long history with lots of road changes and derails under my belt. This causes two issues: 1) loading can be very slow, and 2) it’s hard to see recent trends.
What I’d love would be a batch option, similar to the current Reminders setting page, that lets me change the x-start date for multiple goals at once. Even better would be if those hidden dates are “archived” and not calculated, so it doesn’t slow down the loading of the graph (not sure if it’s already implemented this way). Seems like it could just be another column on the Reminders page, although maybe Reminders wouldn’t be an appropriate title anymore.
Not sure (and apologies for not searching in order to give proper credit!) who shared this script in the forum, but here’s what I use #!/bin/sh # replace XXXXX with token from https://www.beeminder.com/api/v1/auth_token.json AUTH_TOKEN=XXXXX USER=apolyton for GOAL in $( curl https://www.beeminder.com/api/v1/users/$USER.json?auth_token=$AUTH_TOKEN | sed -e 's/[^[]*//; s/^.//; s/].*//; s/[",]/ /g' ) do echo $GOAL curl -X PUT -d '{"tmin":"2020-01-26","tmax":"2020-02-19"}'https://www.beeminder.com/api/v1/users/$USER/goals/$GOAL.json?auth_token=$AUTH_TOKEN --header "Content-Type: application/json" > /dev/null done
Save this as beeminder.sh , run from command line ( = terminal on OSX). I guess you can do this on Windows 10 which has bash (?)
I like this, buuuut what’s the general version of this? I’ve been pitched probably six or seven unique versions of “these are the settings I need to change in bulk, and they have to have these other settings on the same screen too” in the recent past. Is there a reasonable way we can solve this whole class of wants?
I can imagine a generalized version of this, where the user picks a field and we auto-generate the edit table. It’d be ugly but functional. The ones that get used would guide us to implement a more consumable, specialized version.
I’m thinking, either have a huge table with every possible setting, or have checkboxes for each setting which the user can check, and then the table gets populated with the checked settings.