No /rooms/{roomId}/timestamp_to_event. Reading back to a particular day means scrolling to it.
Element's "jump to date" uses that endpoint, and this client already has the machinery either side of it - jumpToMessage and the history gap - so what is missing is the question, not the plumbing.
No `/rooms/{roomId}/timestamp_to_event`. Reading back to a particular day means scrolling to it.
Element's "jump to date" uses that endpoint, and this client already has the machinery either side of it - `jumpToMessage` and the history gap - so what is missing is the question, not the plumbing.
Forwards by default, because a date means "that day" rather than "whatever came before it": asking backwards from midnight lands on the last message of the day before. Backwards is kept for the case the parameter exists to answer — a date after everything in the room, where forwards finds nothing at all, so "take me to Tuesday" in a room that went quiet in March lands on the last thing anybody said.
Local midnight, not UTC: somebody picking the 3rd means the 3rd where they are, and a UTC midnight is still the 2nd across most of the Americas.
It sits under the search box, because it answers the same question by another route — and because an encrypted room cannot be searched at all, which leaves the date as the only way back into one. From there it is the path a search result already takes.
Finished.
Forwards by default, because a date means "that day" rather than "whatever came before it": asking backwards from midnight lands on the last message of the day before. Backwards is kept for the case the parameter exists to answer — a date after everything in the room, where forwards finds nothing at all, so "take me to Tuesday" in a room that went quiet in March lands on the last thing anybody said.
Local midnight, not UTC: somebody picking the 3rd means the 3rd where they are, and a UTC midnight is still the 2nd across most of the Americas.
It sits under the search box, because it answers the same question by another route — and because an encrypted room cannot be searched at all, which leaves the date as the only way back into one. From there it is the path a search result already takes.
[a73b011](https://git.salastil.com/Salastil/moho/commit/a73b011)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
No
/rooms/{roomId}/timestamp_to_event. Reading back to a particular day means scrolling to it.Element's "jump to date" uses that endpoint, and this client already has the machinery either side of it -
jumpToMessageand the history gap - so what is missing is the question, not the plumbing.Finished.
Forwards by default, because a date means "that day" rather than "whatever came before it": asking backwards from midnight lands on the last message of the day before. Backwards is kept for the case the parameter exists to answer — a date after everything in the room, where forwards finds nothing at all, so "take me to Tuesday" in a room that went quiet in March lands on the last thing anybody said.
Local midnight, not UTC: somebody picking the 3rd means the 3rd where they are, and a UTC midnight is still the 2nd across most of the Americas.
It sits under the search box, because it answers the same question by another route — and because an encrypted room cannot be searched at all, which leaves the date as the only way back into one. From there it is the path a search result already takes.
a73b011