http://bitmsgdy44b7kwtsjbsbvl4r2j7gqpjx6kiqrvbh56phc6pyai5uzmyd.onion/index.php?title=Feature_request_list&printable=yes
When Bitmessage is run, if the local client needs a lot of time to sync with the message backlog, there should be a progress bar or a time indicator (much like Bitcoin-QT, estimating how much time is necessary to get sync'd). Perhaps Bitmessage could query other nodes, asking how big the current message store is (message.dat file size), and then provide a progress bar comparing local message.dat size against the average response from connected nodes, as a measure of the backlog.