Gajim - 2023-11-15

What is the most recent version of gajim supporting pango 1.48?

It should be 1.4.7. But you might want to use a newer version, as for example 1.5.0 contained a security fix. If your distro doesn't provide the necessary dependencies, I suggest using Gajim via flatpak.

hello, is it possible on gajim to go to last-read message in a groupchat ?

it shows n unread messages but goes directly to the end

intelfx, why do you need to build Gstreamer in the flatpak? Is the version in the runtime too old?

You might get away with much fewer enabled plugins though.

looks like passwords don't get removed from they keychain after account deletion?

This is with the update to store passwords under the JID, never verified before that

Link Mauve: the Mr depends on not merged gstreamer changes

fjklp: I tested this and they do get removed ✏

Except you see errors in the console

seahorse is showing it still being there, even after restarting seahorse, I'll investigate more later

Oh, makes sense.

Would these also improve Dino?

It’s been my go-to phone client lately.

Link Mauve: no idea i don't understand the changes

Link Mauve, the changes to gstreamer were done for farstream. and the farstream MR says: > This MR plumbs gstreamer's dtlssrtp{enc,dec} modules to fsrtpsession, and plumbs the necessary properties to fsrtpconference, allowing creation of RTP conferences that use DTLS-SRTP as per RFC5763. if that helps

> intelfx, why do you need to build Gstreamer in the flatpak? Is the version in the runtime too old? there are patches to gstreamer ↺

> Would these also improve Dino? no, Dino does not use gstreamer's RTP implementation and negotiation parts AFAICS ↺

hmm. now i wonder what they use

but OT for here

>> intelfx, why do you need to build Gstreamer in the flatpak? Is the version in the runtime too old? > there are patches to gstreamer yes and I guess we should raise a topic why this patches are neccessarry, is it upstream bug etc ↺

1) there is a bug in gstreamer's rtp opus payloader pad capabilities declaration which prevents farstream's codec negotiation machinery from working (and breaks pipeline setup if opus is negotiated)

2) there is missing RT(C)P demultiplexing functionality in gstreamer's RTP implementation; given that RTP and SRTP are implemented on gstreamer level, it makes most sense to implement this functionality in gstreamer

3) there is missing functionality in gstreamer's DTLS and SRTP implementation that prevents the DTLS+SRTP combo from being used together with gstreamer's RTP session implementation (now, _this_ one I worked around on farstream's level, but it will make sense to move this to gstreamer's level)

thanks for your great work and contributing upstream \o/

> thanks for your great work and contributing upstream \o/ +1 🎉

I will be doing (3) once I fix the remaining outstanding issues in multiplexing and multiplexed candidate signaling, because it might affect the inter-module interfaces (pad names and templates)

happy to work with the upstream :)

hi, don't checked if fixed or known issue, but contact status in circle is always gray when you click on your account which display contact list. gajim on windows, version 1.8.1

another thing: if omemo blind trust is disabled, then new keys are added, it's not possible to send message while these keys are not reviewed. it's expected ?

sounds sensible to me

asterix lovetox cal0pteryx chud intelfx With my Debian packaging hat on, I expect slightly less work for me when using gstreamer than libdatachannel. Just because the latter is not packaged yet, while gstreamer only needs a new version at some point. Given, that the patches/fixes will be accepted by upstream soon. I'm not sure about other distributions, though. Maybe at least libdatachannels is already packaged elsewhere.

there's also a new release of farstream that will be needed

how to make that release _happen_ is another story though :-) farstream seems to be basically unmaintained

I'll probably have to do an xorg

intelfx, whats a xorg?

there was an incident some months(?) ago when some branch or a subproject of xorg has accumulated a lot of fixes over the years, but no one wanted to make a release of code not related to xwayland. so the guy who needed those fixes in a release the most, had to assume the release manager duties and arrange a release himself

I believe phoronix had an article on it

intelfx, your merge request on gstreamer seems to have over 500 commits, i suspect something gone wrong

yeah, I created the MR against a wrong branch

I'll fix that shortly

intelfx, did you test the code against other clients? like dino and conversations?

franck-x, yes thats expected, you need to decide if you want messages sent to that new device or not

of course we could treat undecided as simply "dont send anything to it" but then we are in the situation how can we remember the user to later do the decision?

will he forget? and only notice if his contact tells that they receive no messages?

lovetox, yes, this code is supposed to work against itself, dino, conversations and siskin (the ios client)

"supposed" in the sense of "I tested it and it worked for me, but other people who tested it for me reported issues that I'm still debugging"

hi lovetox, alright. i was used to other client solution "this message was not encrypted for this device"

yes, your contact would receive this if we let you sent the message

and then you would need to trust and send again, and then you would tell me, why did gajim not tell me there is a new device

intelfx: that sounds very promising :)

at lease one of the issues is likely related to RTCP multiplexing (the existing rtcp mux negotiation code that I wrote is hacky and I'm reworking it as we speak)

other issues are probably pre-existing issues in Gajim's Jingle state machine that were uncovered by testing against other clients that was previously impossible due to missing dtls-srtp

> other issues are probably pre-existing issues in Gajim's Jingle state machine that were uncovered by testing against other clients that was previously impossible due to missing dtls-srtp That's quite likely ↺

I see the logic, it's fine. but now you need to forbid the key, ask your contact if the new key is legit, then maybe trust it instead of displaying a hint "new key found, blocked because of your choice", be able to ask and maybe trust it not a big deal, but in my case, i got severals keys to review, and my message was delayed. but here come a new thing: because of my lazyness, i decided to renable blind trust, it was still mandatory to review these keys, and I guess that should not be expected

its called blind trust before verification

means the moment you decide on any key, it is expected that you care about verifying keys

you can go back from that state with setting all keys to blind trusted

what the current UI does is, it notfies you and forces you to do a decision

and you can not trust it, or set it to blind trust, or trusted

got it

hello, when trying to join a server channel on biboumi, i get: ValueError: Trying to add GroupchatContact irc.rizon.net@biboumi.example.com, but contact already exists as irc.rizon.net@biboumi.example.com (example.com) (in roster: Falpse)

that's false and not falpse :D

thats not a groupchat thats a server

the syntax is #channel%irc.server.net@irc.xmppserver.net

Philipp Hörist pushed 1 commit to branch _refs/heads/master_ of _gajim_ < https://dev.gajim.org/gajim/gajim >: *29b77367* < https://dev.gajim.org/gajim/gajim/-/commit/29b7736708c18b9e0caea7a12647e47a352f6aab > cfix: Passwords: Don’t fail when password does not exist Fixes #11686

intelfx, works when I tested it in my local network, that's great :)

\o/

Gajim <> Conversations is what I tried, both directions, both A and V

does the "V" part work?

it "works" but latency from gajim is quite high, which is due to codec issues I think. Dino has lots of "realtime" tweaks I saw

aha, I'll see what I can do wrt. stealing ideas from dino

anyway that's nice to hear, I only tested video with siskin

the stream coming from Conversations is smooth

ann, ^

roger

> hi, don't checked if fixed or known issue, but contact status in circle is always gray when you click on your account which display contact list. gajim on windows, version 1.8.1 it's all good on debian 1.8.3

franck-x, thanks for your feedback :)

🤙️

is there any way to export the chat history?

does not need to be beautiful. Text only is ok

matthias, account settings > privacy

cal0pteryx, top, thx!

intelfx, do you think the changes to farstreamer are also necessary to get normal unencrypted RTP working again?

"working again" as in...?

hm it worked only for very few people and only gajim to gajim, though that may be not the fault of farstreamer

so i take your answer as you did not touch anything regarding normal rtp in farstream?

I did touch opus payloader in gstreamer

_that_ one also matters for unencrypted RTP

it is a regression from november 2020

farstream changes only matter for DTLS-SRTP

and for compat with other clients

it's a complex web of bugs :-)

yeah actually some clients support RTP also, i think dino