This cropped up when we changed Purple.Message:author to a
Purple.ConversationMember. It's valid for event messages to not have an author
and the old code was okay with that, but we didn't realize that during the
conversion. So now we just do some instance checks before calling the
functions.

Joined an IRC channel and had another client join and part and verified the assertion warnings were gone.