Rather than distributing it evenly by point index, we want it distributed by time.
For example, if I have 3 timestamps 1 sec away from eachother, then a timestamp an hour later, we cannot distribute them evenly! The close timestamps should be right next to eachother.\
To verify this - manually upload data point many days later than comp data:
curl --request POST \
--url http://localhost:3000/api/telemetry \
--header 'Content-Type: application/json' \
--header 'User-Agent: insomnia/11.2.0' \
--header 'auth-key: c117eec400ae7e947745ba0306b2b345d7f76e22b841109c7f966436d29a550a' \
--data '{
"req": "note.add",
"received": 1751988417.735948,
"body": {
"battery": {
"main_bat_v": 60000
}
}
}'
Should SUPER shift timespan of graph and make comp data scaled TINY, but doesn't.

Rather than distributing it evenly by point index, we want it distributed by time.
For example, if I have 3 timestamps 1 sec away from eachother, then a timestamp an hour later, we cannot distribute them evenly! The close timestamps should be right next to eachother.\
To verify this - manually upload data point many days later than comp data:
Should SUPER shift timespan of graph and make comp data scaled TINY, but doesn't.