saledjenic
commented
1 year ago It's hard to say if the fetch is not successful in decentralized network. In this case you run fetch more messages and you expect that missing messages will show up, let's say after X seconds, if your peers have them, but if they do not have them, they may arrive after any time Y (Y > X) or don't arrive at all.
So based on the description of this issue, what I want to say is that if fetch was successful user will see new messages in the list, if not, then if we want to notify user we should display appropriate message like "we're searching your nodes for a certain messages, this may take a while", otherwise if we display a message like "we're unable to fetch more messages" we will trick/confuse him since messages may arrive in any moment after that even while that notification is displayed.
"Fetch more messages" button is used to fetch historical messages from store nodes. Messages are fetched in chunks, each chunk represents sync period. When the given period is fetched and it has no messages we are interested in, there is no feedback to the user whatsoever. "Synced to" date stays the same, the user doesn't have a clue if the fetch was successful or not.
https://user-images.githubusercontent.com/33099791/207569225-f72fe98f-3957-434b-9045-221ef6a9f04a.mp4