Months (and years) don’t last the same amount of time (neither do days/weeks because of DST, but I think that might be ignorable), so I am just curious how beeminder defines them.
Most saliently, if your goal is to do something X times per month, does the slope of the road adjust up/down slightly every month, or is beeminder using a different static definition of “month”? (and if it is, how long is a month? or a year?)
I’m just curious, this isn’t impacting usability for me at all.
I doubt it means ‘calendar month’ as in the fluctuating duration of Gregorian calendar months and may be amount desired / 30 to produce a daily rate. The Beeminder tick is daily, afaik.
I’m sure the answer will be posted soon, in the meantime my guess is m_{b} = \frac{365.24}{12}, i.e. an average year in days, divided into twelve equal-sized beeminder months.
I was too young to worry about stuff like this in Y2K. And there’s a high likelihood I’ll be too old in 2400 AD. So I must conclude that my set of leap year rules was sufficient for all practical purposes.
Yeah, 365.25 days is what physicists use, for example in defining a light year, so that’s what we went with! A Beeminder month is 365.25/12 = 30.4375 days.