Hard-committing to the next batch of autodata integrations


A vote for Gleeo Time Tracker. It’s a modetely popular Android time tracker app at 100-500k downloads and rating of 4.7 stars on average. It’s strikes a really good balance between featureset and simplicity. Interface is really well thought out too. Would be perfect for Beeminder :slight_smile:




I see the first derail has occurred! Have you worked out those payment details?

I also wanted to make a note that I’m really interested in having the Beeminder IFTTT integration go both ways. I’m actually more excited about having things happen when I add data to my goals rather than having things add data to my goals. I think I’m more motivated to log things in Beeminder because I’ll get charged if I don’t but I still want those things recorded in other places. IFTTT would make that nice and easy.

If you supported tags in the data comments then umbrella goals like productive time could feed subdata into subgoals. So I log all my time in the productive time goal with comments tagged with the subcategory. “If I add data tagged with #project1 to Beeminder goal ‘productive time’ then update Beeminder goal ‘project 1’”


We have! We actually paid the first $5 twice, once to the first person to reply to my beemail about it and once to the person who dibs’d it on the Skritter forum. (I felt bad about not having nailed down the rules so I just paid it double. From now on it’s the first one to call us out!)

Great point about IFTTT triggers as well as actions. Did you know you can do this now with our webhook/callback feature (nerdery required)? As far as I know, @philip is the only one currently hardcore enough to have Beeminder goals automatically feeding other Beeminder goals. You’re right that IFTTT triggers+actions would open up such hardcore-itude to the masses! Really glad you mentioned this!


How? I’m currently doing this by having the API enter the point in all of the relevant goals on entry, but if there is a post-api, more Beemindery way to do this, I’d love to know it. Have had layered goals for a long time and this would make them easier to manage would be great.

(Sorry for the temporary hijack)


See this thread: Webhook/Callback documentation?


Ah, yes, @chipmanaged gets special mention here even if it doesn’t technically count as automatically populating one Beeminder goal from another. (Or does it? I’d like to know about the details!)

But as @philip’s pointing out (by pointing to that other thread), I have in mind using Beeminder’s webhook/callback feature to trigger a program of your own when data is added to a Beeminder goal, and then that program in turn adds data automatically to another Beeminder goal.

Actually, it sounds like @chipmanaged’s system is even more sophisticated and doesn’t need Beeminder’s callback feature simply because she has her own custom interface for entering data.

In any case, @chipmanaged and @philip are both harder core beeminders than me!

  1. there’s $40 of unclaimed derailments on my autod goal… I’m up to $90 pledged now, with two unclaimed derails.

  2. If you were paying close attention to this road (which apparently you’re not, see (1) :-P) you’d notice that I’ve got a section of shallower road coming up. That’s because I’m going on a trip and I’ve dialed my meta road down by half, and consequently my autod road as well. I figure this is legit since I’m fairly sure what I originally agreed to with Danny was: “I’ll spend half of my time on auto data stuff.”

  3. Danny and I had some small bit of debate about whether I ought to count time spent maintaining existing integrations toward this goal. I’m certain that I want to know how much total time is spent on autodata code, including maintaining existing ones, so I definitely do want to track that time, but I guess it’s still an open question whether it should count toward this commitment. What do you think?


Time spent maintaining existing integrations does not make progress toward new integrations so I would not count it as part of this goal.

However I’m not sure it’s fair that the list of new integrations keeps growing, so dialling down the new integration time after you’ve finished the initial 25(?) seems allowable.

Measuring total time spent on integrations is probably a job for tagtime and need not necessarily be minded.


Time spent making sure that integrations actually work totally counts. q.v. our commitment to not putting ourselves on the hook for any big features. Beemindees have a high utility for a stable working service, particularly (I suspect) when it comes to the dark and mysterious edges of integrating with other data sources.

The alternative seems to be a slippery slope of new-for-new’s-sake, quality agnosticism, and inefficient work practices (because we’re counting time, not outcomes). Not that any of those seem likely, but this commitment may as well get the benefit of, say, time spent streamlining and refactoring autod, seeing as it’s impacted by the malefit (from the perspective of wanting-to-take more time) of smoother future integrations.

Bottom line: I think we’ll churn through the wish-list faster if we include everything auto-data-related in this goal.

PS: “half of my time” sounds perfectly reasonable. Let this example of related road changes be a spur to getting Beeminder-as-autod-source on the wish-list.


Since you’re all too polite to yell dibs on Bee’s money we’ll take @insti as having done so, being the first to reply and obviously up to speed on this whole thread. [And done, $40 on the way to @insti.]

I’m not sure how I feel about this “20 hours/week actually meant half whatever my total time is” thing. I mean, yes, I’m sure Bee’s correct, but we already claimed one telephone game exemption and this time the telephone game problem was entirely our fault.

On the other hand, I know there was a bunch of time on old autodata bugfixes and maintenance that Bee didn’t count initially so maybe it’s all working out fairly. In any case the spirit of the commitment seems intact.

PS: The bmndr.com/b/autod commitment is just for Garmin, IFTTT, Misfit, and Skritter (and Epson, now launched). We’ll keep forging ahead after that too but may reassess the steepness of the yellow brick road or put more focus on making it easier for third parties to contribute integrations.


Hey Dan! While I would much rather have the Skritter integration…as a trade off I would love to claim your money (@joeymac1981 on Beeminder and @马洲屹 on Skritter). Here is hoping that the $90 acts as a sufficient motivation :smile:…Good luck!/加油!


(: To be clear, it’s the first person to notice after we derail. $5, $10, and $30 have been paid and we’re skating the edge (bmndr.com/b/autod) on the $90!


Cool – I am happy with that – I’ll keep an eye out :slight_smile:

However, as much as I love money…I don’t want you to derail!


Where should my script I report the derail to get the money?


Right here, as a new comment!


@dreev and I just discussed and have decided to stick with the spirit of the original commitment: only time spent on the listed new integrations counts toward http://beeminder.com/b/autod – so keep an eye on things. I’ve got a bunch of distractions on my immediate horizon (like Google discontinuing support of OAuth V1, necessitating a bunch of refactoring in the GmailZero code), so it’s gonna be tight staying on track on the autod goal!



I think this goal derailed today.
I’ll claim the bounty if it did.

Update: There’s definitely a red dot on the graph. and the pledge has increased, so I’m pretty sure it did.


Confirmed! $90 paid to @insti! I think @bee got $90 of value from that just in the surge of productivity last night as she stayed laser focused right up to midnight hoping for that last TagTime ping. (: [1] (And arguably the perverse incentives of a time-based goal showed through here as she spent a good chunk of the evening making a Beeminder+Misfit logo mashup for the landing page. But it’s pretty hilarious.)

[1] We watched the probability suspensefully tick down at tminder.meteor.com.


Hey, check it out! Soft-launched Skritter over here in the forum thread, including a pretty reasonable blog draft, due to be published Monday at the latest.

So, with that, I think I’m off the hook on autodata.