aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2025-11-01Use AdwAboutDialog instead of AdwAboutWindowMarvin W
2025-11-01Files: Use GFile instead of uri/path stringsMarvin W
In some situations (like VFS or other abstractions), the file reference can have an invalid or unusabe path. Passing the GFile instead and opening it directly increases probability we can actually access it.
2025-11-01Fix tick iconsMarvin W
2025-11-01Fix incoming message corrections in MUCsfiaxh
2025-11-01Store occupant ids for all incoming MUC messagesfiaxh
2025-10-17CI: Add build with Vala nightly compilerMarvin W
2025-10-16Remove invalid declaration modifiersMarvin W
Fixes #1728
2025-10-14History: Fix sync issues when resuming from partial syncMarvin W
2025-10-14Fix inconsistent values for conversation.active_last_changedMarvin W
This could result in Dino not fetching the archive of rooms for the time an account was disabled.
2025-10-13Update translationsTranslations
2025-10-07UI: Adopt new design for chat inputMarvin W
2025-10-06Handle issues with libsoupMarvin W
Workaround https://gitlab.gnome.org/GNOME/libsoup/-/issues/473 and https://gitlab.gnome.org/GNOME/glib-networking/-/issues/20
2025-10-06SFS: Prefer announced media type over application/octet-stream from HTTPMarvin W
2025-10-06device: Request 30 fps in absence of framerate negotiationRobert Mader
Sources not capable of negotiating framerates, most notably the libcamera Pipewire plugin, might still be able to honor a value requested and otherwise usually just ignore it. Thus setting a value that we can reasonably assume to be supported has several benefits: 1. It potentially prevents the source from producing much higher fps than useful for the usecase, causing resource waste. 2. It decreases the chances of running into fallback code paths which are often badly optimized performance-wise. One example is that currently the implicitly set framerate values cause regular renegotiations (including buffer re-allocations) in pipewiresrc. Another is the internal get_target_bitrate(), currently returning uint.MAX. 3. If the source can only produce e.g. 15 fps, that's usually handled without major issues. Thus follow the example of Snapshot, which has been doing this for a while and gets more testing with libcamera, and set framerate to 30/1.
2025-10-06device: Target resolution of 720p on libcamera devicesRobert Mader
Most cameras needing the fallback path are provided by libcamera, which does not yet provide framerates. At the same time many such cameras support very high resolutions - often in the 4K category - and are paired with rather weak CPUs. Examples for this are popular mobile phones such as the PinePhone Pro or the OnePlus6. In order to archive a somewhat stable FPS count in such scenarios, target a resolution of 720p as a compromise of quality and performance.
2025-10-06Only support SystemMemory caps for videoRobert Mader
An increasing number of video device providers, such as `pipewiresrc` (in the upcoming 1.6 release) and `v4l2src` (since Gst 1.26), support `memory:DMABuf` caps using the special `DMA_DRM` caps. This is not expected and handled properly, thus filter out any non-default features.
2025-10-06Use AdwDialog for conversation details and preferencesfiaxh
2025-10-06Conversation details: Move room configuration to separate tabfiaxh
2025-10-05Cleanup: Remove LabelHybrid, conversation details preferencesfiaxh
2025-10-05Adjust to Adw 1.4: Use specialized ActionRowsfiaxh
2025-10-05Fix reference id being used for message corrections in MUCsfiaxh
2025-10-05Use AdwNavigationSplitView instead of AdwLeaflet for main windowfiaxh
2025-09-17Message correction: Use occupant ids, handle correction-before-messagefiaxh
2025-09-17Fix message id used for message corrections in MUCsfiaxh
2025-09-17Fix setting server_id for MAM messages from MUCs (#1763)bodqhrohro
2025-07-20Fix version.py for old python argparseMarvin W
2025-07-20CI: Add missing build dependencyMarvin W
2025-07-20Meson: Add legacy support for Meson 1.3Marvin W
This is for compatibility with Ubuntu 24.04 LTS
2025-07-20Improve checking whether MUC messages will be referencablefiaxh
related #1714
2025-07-20User Avatar: Correctly handle multiple avatar sourcesMarvin W
2025-07-20Meson: Improve plugin buildingMarvin W
Make relevant plugins enabled by default (instead of auto-enabling them if dependencies are met). Also make disabled plugins explicit in the summary.
2025-07-20Meson: Fix path to version.py in certain buildMarvin W
2025-07-20Fix checkmark icon not being availablefiaxh
2025-07-19Add keyboard shortcut to close conversation (#1434)eerielili
closes #876 Co-authored-by: fiaxh <git@lightrise.org>
2025-07-09SFS: Fix datetime formatingfiaxh
fixes #1729
2025-06-15Conversation details: Allow topic edits for moderatorsfiaxh
2025-06-14File Send Dialog: Make file widget staticfiaxh
2025-06-14Add basic support for BOB thumbnails in SFSfiaxh
2025-06-14Support media elements in data formsfiaxh
2025-06-14Support media elements in data formsfiaxh
2025-06-14xmpp-vala: Add basic BOB supportfiaxh
2025-06-14xmpp-vala: Fix SFS mime_type wire-formatfiaxh
2025-06-13Disregard SFS fallback messages even without source attachment given a ↵fiaxh
full-body fallback indication
2025-06-13Add support for whole body fallbacksfiaxh
2025-05-23Voice processor: add back call to set stream delayJacques Comeaux
2025-05-23FileTransfer fix store sourcefabrixxm
Store source in db and add sources to `sfs_sources` is divided in two functions. `persists()` now calls `store_source`, because the sources it want to persist are already added to `sfs_sources`.
2025-05-23Fix parse incoming stateless file sharing sourcesfabrixxm
2025-05-05Conversation details: Show used account if multiple are activefiaxh
2025-05-05Account details: Make own jid selectablefiaxh
2025-04-18Remove pixbuf from libdino api surface and xmpp-valafiaxh