connection/disconnection messages have inconsistent %messageClasses%

[mathuaerknedam]

formerly described in #10189.

• When my buddy connects (to yahoo) %messageClasses% = "status online".
• When my buddy disconnects (from yahoo) %messageClasses% = "status offline".
• When I connect (to yahoo) %messageClasses% = "outgoing status connected".
• When I disconnect (from yahoo) %messageClasses% = "outgoing status disconnected".

I get the same results with xmpp and IRC.

Besides the inconsistent online/offline vs connected/disconnected classing, I think that the "outgoing" on my messages should not be there, at least until we start classing *all* status messages as either incoming or outgoing (which we may never do).

[mathuaerknedam]

Patch to remove "outgoing" class from events

[mathuaerknedam]

I've added a patch that resolves part of the issue mentioned here, the presence of "outgoing" on the local user's connected/disconnected messages. This is an extension of David's changeset [23296], which already removed "status" and "incoming" from events. The issue of online/offline vs connected/disconnected remains.

[Zachary West <zacw@…>]

(In  29c166695832) Patch from mathuaerknedam to remove outgoing (on top of incoming) for AIContentEvents. Fixes #11588.

[Zachary West <zacw@…>]

(In  1b04b22253d4) Patch from mathuaerknedam to remove outgoing (on top of incoming) for AIContentEvents. Fixes #11588.