{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/fc30c45f8dc54762bb78d9cb4f26bd9a\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/fc30c45f8dc54762bb78d9cb4f26bd9a-a698d829073020e0.gif","duration":300.1269,"title":"Fixing Message Exchange and State Calculation Issues 🔧","description":"In this video, I walk through the process of handling message exchanges on the home server side after a local RC host shutdown. I demonstrated how the system requests missing messages when it detects gaps in the message history, specifically between the 19th and 20th messages. This ensures that the state can be accurately calculated before processing any new messages. I also noted that the system postpones the processing of messages until all necessary events are retrieved. Please review the logs for further insights and let me know if you have any questions or suggestions for improvements."}