search

tigase / beagle-im

(M) XMPP client for macOS based on TigaseSwift XMPP library
GNU General Public License v3.0
181 stars 21 forks source link

Add MUC Icon Description #106

Closed adamflott closed 2 years ago

adamflott commented 2 years ago

I run my own XMPP server and while learning to properly configure it I occasionally have an yellow/orange dot on 2 head icon near the top of a MUC (on OSX). I know when it's green things are working, but when it is yellow/orange I have no idea what that means. However I do know that I can not send messages in the chat when it is yellow.

I would like either a description(notification?) on hover or even under the icon to indicate something isn't set up correctly.

hantu85 commented 2 years ago

The yellow dot means that reconnection is in progress (there was no failure yet, so there is nothing we can tell you).

In some cases, it may happen that the server will return an error but the type of the error would indicate that it is a temporary error, in this case, BeagleIM will just try to reconnect (and the account would still be marked with an orange dot - as reconnection is still in progress).

If you are troubleshooting issues with your XMPP server, you should hold Option key and click on the main menu item Window > XML Console > account. This will open an XML console with the full log of XML exchange between BeagleIM and the XMPP server since the console window was opened. This should help you investigate the issue and fix it.

adamflott commented 2 years ago

Thanks for the tip, however I don't see anything obvious in the log.

There is something definitely wrong with my server/setup. pidgin has no problem, yet BeagleIM (OSX) and Siskin IM (iPhone) both show problems with connecting/retaining the connection. They all reside on the same network (nehind a NAT).

In BeagleIM I currently have the orange dot, but can receive MUC messages just fine (can't send them). I'm trying to upgrade my ejabberd installation to something other than 21.04, but having trouble.

hantu85 commented 2 years ago

I do recall having a yellow dot near the MUC icon, if the MUC itself was not sending the correct presence to the clients, notifying them the room was properly joined. If I recall correctly, it was related to the missing <presence> from the MUC containing status code 110 and it might be related to the case when more than one client was joining the same MUC room from the same account.

I also do recall, that the issue was somehow related only to the rooms with a lot of messages and caused message throttling kicking in (on our local server).

adamflott commented 2 years ago

I changed from ejabberd 21.04 to prosody 0.12 and all my connection issues have vanished. Closing.