Change Details

Follow up to: https://phab.comm.dev/D5875#inline-39619, but instead of deleting session it refuses to create it, or allow any connection. Reason to that change is in solution suggester in previous comment we will not receive any data, but after connection reset (like reload on web app) socket will cause `FULL_STATE_SYNC` action, and modal will still be visible but data will be fetched in background, and we want to avoid that. After accepting initializing socket will cause fetching all needed data.

Follow up to: https://phab.comm.dev/D5875#inline-39619, but instead of deleting the session it refuses to create it and forbids any communication via socket. The reason for that change is the fact, that in the solution suggested in the linked comment we will not receive any data, but after the connection reset (like reloading on web app) socket will cause `FULL_STATE_SYNC` action, modal will still be visible but data will be fetched in the background, and we want to avoid that. After accepting terms by user initializing the socket will cause fetching all needed data.

Follow up to: https://phab.comm.dev/D5875#inline-39619, but instead of deleting the session it refuses to create it, or allow any connection.it and forbids any communication via socket. The reason for that change is the fact, Reason to that change is inin the solution suggesterd in previousthe linked comment we will not receive any data, but after the connection reset (like reloading on web app) socket will cause `FULL_STATE_SYNC` action, and modal will still be visible but data will be fetched in the background, and we want to avoid that. After accepting terms by user initializing the socket will cause fetching all needed data.