[Feature Request] Adjusting "start of next day" time

[Terrance]

Is your feature request related to a problem? Please describe.
Days currently run from midnight to midnight, which means any journeys crossing midnight are split across two days.

Describe the solution you'd like
An option to set a different hour of the day as the point where the next day begins, i.e. the hour you're most likely to be asleep / least likely to be travelling, e.g. 4am.

Describe alternatives you've considered
Looking at a wider timespan would show a whole late night journey, but also the next day which I might not need right now.

Additional context
Prior art from study apps Anki and Kanji Dojo which solve a similar problem in a "daily task" context:

[dgraf-gh]

Hi @Terrance,

sorry it took me that long to react to your request.

That is a really nice idea and would improve the usefulness of reitti by a lot. Since this will be a rather big task, I will put it in one of the next or maybe next bigger version.

I think we can put this on the user settings. So every user can set this on its own on an instance. Basically we would start a day in the UI not at midnight but your set time.

Should this also carry on into memories when we split the time frame up into days?

[Terrance]

Probably makes the most sense to apply this everywhere things are partitioned into days? I don't think I'm likely to have parts of a memory spanning the reset time, though they may still cross midnight; there are cases for it though e.g. sleeper trains, overnight flights (I note memories are shown in server time rather than location-local time though, so currently any times are possible).

[dgraf-gh]

I note memories are shown in server time rather than location-local time though, so currently any times are possible

That is actually not what should happen. The memory on its own should be displayed in your local time. They do not have a location, so this is the only thing we can do. The trips and visits should be displayed in the local time they are happened at their location. For trips, we take the start.

At least that was the plan but timezones are f**** up and I need to double check that.

[Terrance]

Looks like selecting the memory redirects to e.g. /memories/1?timezone=Europe/London despite it not being in Europe; changing that to the right timezone still doesn't look quite right but this was just a test memory so the splits might be off.

In any case, looks like only the start date is reported on the individual times e.g. Aug 10, 2026 23:00 ‐ 01:00, so if one starts past midnight then it's probably dubious to use the previous date there. The Day 2 etc. headings should be placed based on the cutoff though.

[dgraf-gh]

Looks like selecting the memory redirects to e.g. /memories/1?timezone=Europe/London despite it not being in Europe;

That would be fine, as long as this is your timezone. For the memories on its own we do not have a location, and therefore are not able to put them into a timezone other than the one you have selected or your browser reports it.

Yeah, that needs a little bit of thinking on my side how this would fit into the memories. I like the idea a lot and will try to make it happen.