Michael Mulligan

My feedback

  1. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Michael Mulligan commented  · 

    If possible, could we generalize the title to something like "Implement Support for Slackline"? This way it is more about increasing the productivity of Mattermost, and less about pulling users from Slack (which is the goal, don't get me wrong). I just feel like supporting Slackline in general is a good/great idea, even if all nodes are Mattermost. The fact that this also allows transition from Slack for some firms is an added bonus.

    My 2 cents.

  2. 882 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    41 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Michael Mulligan commented  · 

    Keep in mind: particularities, like how you configure multiple chat web components and their behaviors, is beyond the scope of the Mattermore development team. Unless, of course, they want to develop it from the ground up.

    It is much more advantageous if they build the functionality needed to do such a thing, and someone else makes the specific plugin.

    An error occurred while saving the comment
    Michael Mulligan commented  · 

    I kind of dig this, and could see it generalized a little bit to allow for more flexability. Instead of specifically webchat, what kind of things would Mattermost be able to do that would be general enough, but in the same vein...

    The general idea is two parts, a website component that the user uses to hit Mattermost, a Mattermost plugin that handles the special functionality on it's end.

    Ignoring the website component, what does the Mattermost component do?

    It receives a chat initiation and establishes a Chat Session ID and associates a name with that (we will need to track the name somehow and inherently link the two). It sends the Mattermore chat to the user.

    What does Mattermore need to do this?

    1) Plugin Support
    2) Incoming Webhook that can hit the plugin.
    3) Bot Support (the external user will be represented by a bot, you can close the chat, but the chat will be archived, and can be picked up later on if the same user with the same chat session id pings you again).
    4) Action Links for messages (when you configure the plugin you can tell it to automatically create a private group with a user, OR have it post to a channel. If it posts to a channel, a action link could be available like "I'll Take It" which triggers the bot to then invite you to the private group).

    So, to summarize, the 4 features required for a 3rd party to make a Chat Web Component would be:
    1) Plugins
    2) Webhooks
    3) Bots
    4) Action Links

    Of these I think Bots are the only thing yet-to-be implemented. Someone correct me.

Feedback and Knowledge Base