I can accept worse-is-better decisions (in theory, hehe), but in this case I think there might be reason to think that, if it was once better, it might no longer be the case.
Things have changed.
"This is very much what people expect in night-owl mode (cf “it’s still the 30th to me!” and “I want to define when my day ends!”)."
When that was the typical use of deadlines, I could sort of understand it, even if I didn’t prefer it. I mean, I personally still used the actual date, but I got the reasoning behind it. Given the “Chasing Waterfalls” use of deadlines is (I presume) on the rise, though, I think this is no longer clearly better.
Timestamps aren’t all that helpful
It doesn’t matter so much that timestamps remain unaltered, because whether they’re available in the API or not (I haven’t checked, tbh), they don’t export to CSV, and so the real data remains trapped for non-API users. But what’s worse is that sometimes I make a note of something and don’t enter it until the next day if it’s not a potential derailment day (I often do that with sleep, for e.g., taking a screenshot of the time when I shut things down and just entering that time retroactively in the morning – or if I forget to enter something that I’ve noted and enter it the next day, when I see it on my list of things to enter). So working exclusively with timestamps (assuming you’re an API user to begin with) doesn’t work either. I could, if both are exposed in the API, create something that rewrites the date to the timestamp’s date for all datapoints where timestamp < date, while ignoring all datapoints where timestamp > date (to protect the “oops, I forgot” cases), but I think needing to write an API-aided extension just to have the real data is suboptimal.
This doesn’t need an explanation. If the data isn’t accurate, it’s unusable for QS purposes.
Wise people who have put a lot of thought into Beeminder agree
"Beeminder is foremost a Quantified Self tool, so it feels really wrong and counterproductive to falsify your data. People take a lot of pride in their graphs since it’s a meaningful visualization of their progress, and they’d rather pay the occasional penalty than mess that up."
“serious beeminder users know that fake data is anathema to the whole concept”
(I should add that the last one is taken out of context, and “fake data” is really referring to datapoints you didn’t actually complete)