# It looks like Beeminder is stealing a minute

**URL:** <https://forum.beeminder.com/t/it-looks-like-beeminder-is-stealing-a-minute/6944>\
**Category:** Bugabee\
**Created:** [June 26, 2020, 5:29pm UTC](https://forum.beeminder.com/t/it-looks-like-beeminder-is-stealing-a-minute/6944 "2020-06-26T17:29:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![phi](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/phi/32/2586_2.png) [@phi](https://forum.beeminder.com/u/phi)\
**Post date:** [June 26, 2020, 5:29pm UTC](https://forum.beeminder.com/t/it-looks-like-beeminder-is-stealing-a-minute/6944/1 "2020-06-26T17:29:44Z")

</div>

I entered three data points in the advanced entry form of my goal `work`. One of them was 6:53.  
It then briefly showed up as 6:52 (!) in the list of data points, then it changed into 6.883333333333333. It changing alone is a bug already, but this is not about this. This is about it showing 6:52 instead of 6:53.

Where did the other minute go?

Also, see the discussion about a rational datatype for modelling fractions that are not subject to the whims of the IEEE 32 bit float and JS’ Number datatype:

> [@Option to show all times in HH:MM:SS instead of HH:MM](https://forum.beeminder.com/t/option-to-show-all-times-in-hhss-instead-of-hh-mm/6234):
>
> I have a goal where the seconds actually matter a lot. I need to know if today I actually have 1 minute to do or just 5 seconds. Whether I need to do 5 seconds or 59, the interface still shows 00:01 to go for the day. What ends happening in my specific use case (which I can’t elaborate further on in this thread) is that sometimes I run short of a few seconds and I just add in a “fake” “padding” datapoint for those few seconds, because it would be impractical to actually do the task again and l…