#general channel disappears from pidgin about slack-libpurple HOT 4 OPEN

It happens for me as well. It seems to be triggered only in channels with too large membership (200+ members?), and usually general & random are very large because they are auto-joined. In slack projects with small membership, general and random channels work fine for me.

from slack-libpurple.

I still find it strange that is_member is false. What the API docs say is that "almost every user" is a member of general, not that is_general implies is_member. However, I'm happy to treat is_general as is_member if we think that's the right thing to do. It just means we won't additionally try to join the channel. I guess I'll do that and then you can let me know if it fixes it, or causes a different problem.

from slack-libpurple.

@bezirg I had the theory that it had something to do with how the general channel was configured (read only vs not, etc). I created a dummy slack with a couple of members just to test this, but there the general channel worked fine (and both is_general and is_member was true) regardless how I configured the channel. So, roster size seems like a likely suspect. Since it all works fine in Slack's web client, I assume they're handling the general channel separately (or not using their own API).

@dylex The fix worked. At least for the general channel. We don't have a random channel, so I can't speak for that.

from slack-libpurple.

The problem with general channel is fixed now for me.

from slack-libpurple.