Sergej Pupykin

PS: It was from spectrum2 transport From pidgin MUC looks working

Latest (2683ee186f7b5186be6c604f0a2ccf32afa66448) does not segfault but it looks like that this plugin does not work with spectrum2. When I join channel it passes just channel name. Then it fails to...

May be it is because of only roomlist information passed up and only roomlist info can be used by xmpp clients.

@ylluminate mattermost-server dropped API v3 support since version 5.0, so you cannot use this plugin until API v4 supported.

Works for me with private messages in spectrum2 as jabber transport, but https://github.com/EionRobb/purple-mattermost/issues/60 still occurs.

Previously I used adapted for spectrum2 and xmpp own fork: https://github.com/p5n/purple-mattermost It works slightly better with xmpp, but I did not port it to v4 yet. This fork has fixed...

I've just opened https://github.com/EionRobb/purple-mattermost/issues/64, that maybe similar to this.

Regarding muc support for spectrum2: - purple_roomlist_room_new must be called with teamid^id^chatname---team as name, so correct string will be passed on join and correct jid will be used - spectrum2...

Also to show tree of chats for spectrum2 mm_roomlist_expand_category() implementation looks required. Now team categories and chats displayed as plain list.

I've made quite dirty patch yesterday which makes it usable with spectrum2. I did not make PR because of there is a change to channel_id as primary identifier. I dropped...