Gajim - 2023-09-28

Is there anything wrong with this stanza? ``` <message type="groupchat" id="1758461952" from="-608413854@zg.94.177.207.80/D/K (1382500964)" to="bqdiscord@94.177.207.80"><subject>1758461952 | D/K (1382500964) | 18 Sep 2023 04:51:17 | хрк</subject><delay xmlns="urn:xmpp:delay" from="-608413854@zg.94.177.207.80" stamp="2023-09-18T04:51:17Z"></delay><x xmlns="jabber:x:delay" from="-608413854@zg.94.177.207.80" stamp="20230918T04:51:17"></x></message> ```

bodqhrohro, this is jdev@ material, and I think `from="-608413854@zg.94.177.207.80/D/K (1382500964)"` is not a valid JID because `/` can only be once in a JID, to mark the start of the resource part?

nicoco: I suspected that too before, but found no confirmations it's actually prohibited, any symbols seem to be valid in resourcepart.

Actually, it's a Prosody issue as such stanzas don't even reach clients, so I investigate it there already.

> any symbols seem to be valid in resourcepart. Far from it! I'm not 100% sure about a second `/` being forbidden, but the rules of what's a valid resource part are actually quite nightmare-ish. For instance, I know for a fact that 🎉️ is not allowed in a resource part. Cheogram worked around that by punycoding the nicks in the resource part and using a <nick> element with a punydecoded nick when necessary. But we're really OT, the jdev or XSF MUCs are the right places to discuss that. ✏

Hi. I came across something really weird today. I've added some notifications to Gajim (using Gdk.Notify) for my own use case. These notifications show fine in GNOME 42.9 (although notification timeouts are ignored by the system, thanks to the developer's decision). But Gajim's own notifications appear as "Launch.py <line break> "Gajim" is ready ". Why might it behave this way?

kurion: "Gajim is ready" is not coming from gajim, but from your DE

bodqhrohro: nbxmpp.protocol.JID.from_string() will tell you if it's valid

cal0pteryx: Yup. I asked about this on GNOME Shell's matrix room. They said the following: "App is ready usually means the app tried to activate itself without an activation token, which triggered the focus stealing prevention" ✏

and the following: "no idea really. gio.notification is implemented in glib/, that's what I know"

I am feeling kind of lost here.

since I am running gajim from a python venv, the fact that gajim is not yet installed _in_ the system; could it be the reason for not having an activation token?

kurion: you can stop this by setting use_urgency_hint=Disabled in the advanced configuration editor

we should probably put this in the FAQ

fjklp: Thanks for chipping in. :)

I disabled that setting

But it seems all notifications stopped after I disabled it. :P

in gnome?

yup

it works for me in ubuntu

do you have Gajim installed?

yes

what version is yours?

my `Notify.Notification` notifications are working as intended though

version of what?

gajim is nightly

> gajim is nightly was asking about Gajim.

fjklp: did you face similar issue when the setting was enabled?

yes

that's how I fixed it

How did you find about it?

I don't remember, I know I spent hours on it

> we should probably put this in the FAQ +1

> kurion: "Gajim is ready" is not coming from gajim, but from your DE actually, I was responding to this. Is this what you are experiencing?

yup

It seems with that setting enabled, Gajim tries to flash the screen on a new notification, but is lacking something called an ActivationToken. So GNOME shell shows this weird notification and stops Gajim from stealing focus.

Can you link doc for activation token

The most pain for the lowest price!