Consider adding end_id or end_time param to basic searches and browsing
When this is in production, I will likely have new records coming in fairly quickly, so a user might see their results overwhelmed. That is, if a chat is particularly busy, clicking on page 2 may have everything from page 1 pushed there by the time they scroll down. Adding an ending time or ID param to all browses and basic searches would allow the user to maintain their position without having results pushed back as new messages come in.
Should I do this, I will need to ensure basic searches and browses are still classified properly, rather than being classified as an advanced search.
Edited by Luna Lucadou