-
-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6.1.0 #998
Merged
Merged
6.1.0 #998
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
tmolitor-stud-tu
commented
Feb 5, 2024
- Add video call support
- Allow local video to be "muted" by doubletapping onto local image
- Fix handling of resources containing slashes
- Fix various crashes
- Add share button to image viewer
- Fix sync errors not being displayed when having no connectivity
- Fix crashes when receiving files not decryptable
- Fix slow connection establishment on some STARTTLS connections
- Fix sporadic "bad-format" xml errors
- Faster connection times by using TCP fast open
- Retry to reconnect more often in bad connectivity scenarios
- Show notification if a new omemo device was added to your account
- Handle transient muc join errors as such
6.0.4rc1
Neither "goog-remb" nor "remb" are registered at iana: https://www.iana.org/assignments/sdp-parameters/sdp-parameters.xhtml#sdp-parameters-14 It seems, webrtc uses "goog-remb" while the mozilla sdp-lib uses "remb".
TODO: missing camera switching
This adds some security checks for double @ symbols in the bare jid, too (should be already filtered by server, though).
Both will trigger a roster push and sending "subscribe" before "subscribed" will recreate the notification asking for contact approval, when the roster push for "subscribe" arrives. While the roster push for "subscribed" should in theory remove that notification a few ms later, a race condition of these two notification related actions might explain why this sometimes does not happen. Reversing the order, should fix this race condition.
This reverts commit d9a6072.
This reverts commit b692f7b.
6.1.0.b1
This should fix those big delays
We use a semaphore to make sure we only always have one call to nw_connection_receive() or nw_framer_parse_input() in flight. We can't use a mutex so be careful to not increment the semaphore to more than 1!
- Fix rotation of local video in calls - Allow local video to be "muted" by doubletapping onto local image - Fix crashes when receiving files not decryptable - Fix slow connection establishment on some STARTTLS connections - Fix sporadic "bad-format" xml errors
6.1.0rc1
Sometimes joining a muc can fail with an error presence even after successful discovery (like with biboumi). Handle transient errors as such in these cases (like already done with discovery errors). Thanks leon.
- Faster connection times by using TCP fast open - Retry to reconnect more often in bad connectivity scenarios - Show notification if a new omemo device was added to your account - Handle transient muc join errors as such
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.