- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 19 2024
Simplify the code
Improve validation
Rebase
Rebase
Rename
Rename
Rebase
Rename
In D10667#309741, @marcin wrote:I am confused by this differential. I have two questions:
- What is the purpose of deleting and recreating notifications sessions at least every time app starts (session creation is not idempotent - it overwrites previous session)? Session is created on login and via socket if the keyserver happens to be missing session.
- In its current state this differential doesn't guarantee that session on the client is in sync with session on the keyserver - initialEncryptedMessage returned from session creator is not used. If this differential is intentionally breaking the app and you plan to fix it later in the stack then it should be explicitly stated in summary or in a comment.
In D10662#309232, @kamil wrote:Using deviceID everywhere makes me sometimes confused which ID it is, so in places like this I would prefer recipientDeviceID or targetDeviceID but curious about what other reviewers think.
I did the same here D10381 so going to update next time touching this code.
Jan 18 2024
Reverse providers order
Simplify
Jan 17 2024
Jan 15 2024
Jan 12 2024
Jan 11 2024
Avoid console logging the keys
Rebase
Readonly
Rever import ordering change
Address review
It's unfortunate how different native and web are, but I think it makes sense given the technical decisions we've made
When we receive the version we compare it, if it's different this tab is old, we refresh it - download the newest web app version, and connect to the new worker.
Are there any risks here? Can the refresh fail, or be stopped by a user?
Jan 10 2024
Rebase
Format
Rebase
Rebase
Improve error handling
Use event emitter
Jan 9 2024
Fix Flow