I stated the problem with the server before, proto has nothing to do with it, but only stops some of us from protecting this nation.

The message box needs to gather all updates up until your post to send to you before it closes the msg box. Just because it say it times out doesn't mean shit, that is a programmers generic message for anything that goes wrong or delayed. That post function should be a series of asynchronous functions run in the background. The best way to handle this is to cache the last update into a data structure+1 size and then conj the next post and then cache that while locking. The server should be a msg queue that caches result sets and invalidates while counting # of posts. This way when 750 comes, it locks board, creates new bread with old notables, scans for new notables, processes them together, then post 751 should always be the new board. Use kafka.