gajim issueshttps://dev.gajim.org/gajim/gajim/-/issues2019-11-28T14:58:05Zhttps://dev.gajim.org/gajim/gajim/-/issues/9691Gajim does not send proxy activated to other clients2019-11-28T14:58:05ZPhilipp Höristphilipp@hoerist.comGajim does not send proxy activated to other clients## Versions
- Gajim version: 1.1.2
## Steps to reproduce the problem
1. Client sends something to Gajim
2. Gajims proxys is chosen
3. Gajim should send proxy activated to other Client## Versions
- Gajim version: 1.1.2
## Steps to reproduce the problem
1. Client sends something to Gajim
2. Gajims proxys is chosen
3. Gajim should send proxy activated to other Clienthttps://dev.gajim.org/gajim/gajim/-/issues/9774Windows: Close session on system shutdown2023-11-04T18:33:45ZGe0rGWindows: Close session on system shutdownWhen running Gajim on Windows, and shutting down the PC, Gajim will not properly close the server connection, so the server will remain under the impression that there is a 0198 hibernated session, caching MUC presence, pending messages ...When running Gajim on Windows, and shutting down the PC, Gajim will not properly close the server connection, so the server will remain under the impression that there is a 0198 hibernated session, caching MUC presence, pending messages etc, and causing issues for the user's contacts.
It would be great if Gajim could cleanly terminate the session (not just close the connection) on the server on system shutdown. On Windows, the [WM_ENDSESSION](https://docs.microsoft.com/de-de/windows/win32/shutdown/wm-endsession) event is fired and can be used - or maybe GTK has some portable way to detect it?
Similar work:
* https://dev.deluge-torrent.org/ticket/3011
* https://www.mail-archive.com/gtk-app-devel-list@gnome.org/msg12534.html
* https://github.com/syncthing/syncthing-gtk/issues/83https://dev.gajim.org/gajim/gajim/-/issues/9144Add support for XEP-0352: Client State Indication2021-01-02T20:04:19ZAndrey GurskyAdd support for XEP-0352: Client State IndicationChanges of status: available/not available, composing/paused and so on can generate more traffic than comes from useful real messages. Allow users to decide whether they need them at the moment.
Per default it can be controlled automati...Changes of status: available/not available, composing/paused and so on can generate more traffic than comes from useful real messages. Allow users to decide whether they need them at the moment.
Per default it can be controlled automatically by idle event (proposed by @lovetox). Additionally it would be useful to be able to enable/disable it manually.https://dev.gajim.org/gajim/gajim/-/issues/7123Allow sending messages while being disconnected (offline)2024-02-13T11:01:46ZMattJAllow sending messages while being disconnected (offline)XEP-0198 allows you to easily have a conversation even on unreliable connections, it makes the connections basically invisible to you and your contacts.
However in Gajim if you happen to be typing, and your connection dies, when you pre...XEP-0198 allows you to easily have a conversation even on unreliable connections, it makes the connections basically invisible to you and your contacts.
However in Gajim if you happen to be typing, and your connection dies, when you press enter you may not be connected. Gajim pops up a dialog box that says: "Your message can not be sent until you are connected".
If your connection is very unreliable, and you are trying to have a conversation with someone, this can get very annoying. Gajim could instead add the message to the stanza queue, and it would be sent to the server when the session resumed.
But with XEP-0198 you can "send" messages while disconnected by adding them to the send queue, they will get sent to the server when the session is resumed.https://dev.gajim.org/gajim/gajim/-/issues/9178MUC messages with OOB data but without body are discarded2021-04-01T06:47:03ZValdikSSMUC messages with OOB data but without body are discardedI use [Matterbridge](https://github.com/42wim/matterbridge) to link multiple chat rooms from different chat networks (messengers) together.
Some messengers have comments for file uploads, or can send message body and file in the same m...I use [Matterbridge](https://github.com/42wim/matterbridge) to link multiple chat rooms from different chat networks (messengers) together.
Some messengers have comments for file uploads, or can send message body and file in the same message.
Conversations XMPP client can show only either text or inline image in the message, that's why I can't send both message body and OOB data in a single message.
To workaround this issue, Matterbridge sends 2 XMPP messages when a message with image is sent: one with message body and a link to an image, and another is jabber:x:oob data without <body> tag.
This way XMPP clients without OOB support does not show second (blank) message, and clients with OOB support (Conversations, Psi+) show both message body and inline image.
Gajim ignores MUC messages with jabber:x:oob, but without <body> tag, so in my case it acts as a client without OOB support. It does not show inline image, it only shows first message with message body and link.
The code which discards messages without body: https://dev.gajim.org/gajim/gajim/blob/master/gajim/common/connection_handlers_events.py#L1222
Introduced in commit 81566df8a1f988c5820309ec2865b8ced895fc8f
Note that I can't send both body and OOB data in a single message, because inline message won't be shown in Conversations, and I can't include empty body tag because some clients would handle that as a blank message.
## Versions
- OS: Linux
- Gajim version: 1.0.3
- GTK version: 3.22.30
- Python-nbxmpp version: 0.6.6
## Steps to reproduce the problem
1. Join MUC
2. Send MUC message with a link to an image inside OOB data and without body tag
## Expected behavior
Inline image from OOB data is shown
## Actual behavior
Inline image from OOB data is not shownhttps://dev.gajim.org/gajim/gajim/-/issues/8606Don’t answer the same iq twice when a Jingle payload is unknown2019-08-16T17:58:06ZLink MauveDon’t answer the same iq twice when a Jingle payload is unknownDuring a Jingle session, sending e.g. <iq><jingle><unknown/></jingle></iq> will make Gajim answer an empty iq result first, followed by a <feature-not-implemented/>, both answering the same iq.During a Jingle session, sending e.g. <iq><jingle><unknown/></jingle></iq> will make Gajim answer an empty iq result first, followed by a <feature-not-implemented/>, both answering the same iq.https://dev.gajim.org/gajim/gajim/-/issues/8594Gajim advertises Service Discovery support for jabber:iq:gateway2021-02-10T12:27:57ZsingpolymaGajim advertises Service Discovery support for jabber:iq:gatewayBut shouldn't that mean that the entity supports `jabber:iq:gateway` queries? I know XEP-0100 doesn't specify anything about the Service Discover use at all, but it seems strange for a *client* to advertise support for this feature. I ...But shouldn't that mean that the entity supports `jabber:iq:gateway` queries? I know XEP-0100 doesn't specify anything about the Service Discover use at all, but it seems strange for a *client* to advertise support for this feature. I would expect that if I scan my roster for entities advertising support for this feature, I will find only entities which I can send queries to.https://dev.gajim.org/gajim/gajim/-/issues/8518Messages of type=headline are ignored if they have a data form child2019-04-10T07:45:53ZsingpolymaMessages of type=headline are ignored if they have a data form child```
<message to='MY_JID' type='headline'>
<body>Reply with "yes" to allow it</body>
<x xmlns='jabber:x:data' type='form'>
<title>Joogle Search</title>
<instructions>Fill out this form to search for information!</instruct...```
<message to='MY_JID' type='headline'>
<body>Reply with "yes" to allow it</body>
<x xmlns='jabber:x:data' type='form'>
<title>Joogle Search</title>
<instructions>Fill out this form to search for information!</instructions>
<field type='text-single'
var='search_request'>
<required/>
</field>
</x>
</message>
```
Does not even display the body to me on Gajim 0.16.5. Using type=chat shows only the body and ignores the data form. type=normal shows the data form as expected