Hi fefelov,

what are the matters of your tests?

Regards,

  Frank

Maybe Neos requires the server to support JEP-55 for browsing?  It''s known that Messenger doesn''t support that.

On my side, I''ve had success with Gaim 1.0.3.  A colleague had problems with Gaim 1.1.  But then he built an older version and had the same problem with that one, so now I wonder whether it''s not a problem with one of the libraries Gaim uses rather than Gaim itself.  Whatever it is, something changed between Messenger 2.0.1 and 2.1.0 that triggered the problem because they had no issues with the earlier Messenger and didn''t change anything on the client side when I installed 2.1.0.

Its like 6 months later but I thought that I should reply to this thread anyway. (i am searching the forums for posts related to neos)

Neos versions previous 1.0.100 only supported jabber:iq:browse which is a deprecated protocol. Neos 1.0.100 and later versions supports service discovery which fixes the issue mentioned on this thread.

ok. neos 1.0.100 + JM 2.2.0 beta 2

when trying to get User Info in MUC room i get error:

Error fetching chatroom@conference.server/username info (400)

Psi 0.9.3 gives error with blank reason. Maybe this is a JM issue.

And not a bug, but neos still doesnt show user kick/ban/exit/enter messages in MUC

And not a bug, but neos still doesnt show user

kick/ban/exit/enter messages in MUC

I will check it.

 

side note: Your mails at feedback@neosmt.com that you

sent back in April I did receive but all my responses

came back due some error I don''t remember now.

 

Regards

hm.. well, nevermind, i''m glad if my reports were useful