Yes, it is. All decryptable packets (messages, both group and DM) are saved to the backend, and adverts and path packets update contact routing etc., but ultimately, the remainder are not functional. So, the correct/necessary effects of the packets are persisted, but it does not retain ALL raw packets it hears. The packet display on the frontend is just a streaming version of what the backend processes, and is not persisted in its raw form.
Yes, it is. All decryptable packets (messages, both group and DM) are saved to the backend, and adverts and path packets update contact routing etc., but ultimately, the remainder are not functional. So, the correct/necessary effects of the packets are persisted, but it does not retain ALL raw packets it hears. The packet display on the frontend is just a streaming version of what the backend processes, and is not persisted in its raw form.
<!-- github-comment-id:3874671119 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The packet feed and its visualization do not persist when the frontend is reloaded. Is this the expected behavior?
Yes, it is. All decryptable packets (messages, both group and DM) are saved to the backend, and adverts and path packets update contact routing etc., but ultimately, the remainder are not functional. So, the correct/necessary effects of the packets are persisted, but it does not retain ALL raw packets it hears. The packet display on the frontend is just a streaming version of what the backend processes, and is not persisted in its raw form.