Determine ConversationManager interface #645
Description
Right now the ConversationManager is a HookProvider/Plugin, but that contradicts our decision that we shouldn't be accepting that for higher level abstractions.
Didn't notice this before. Should this be a more specific Plugin base? Or maybe it should be a config to specify one of the built in managers? If someone wants a custom manager they can just pass through plugins right? I just worry because technically someone right now could pass in any plugin implementation to conversationManager and it could be one that doesn't even touch messages.
Originally posted by @pgrayy in #619 (comment)