summaryrefslogtreecommitdiffstats
path: root/bridge/mattermost/mattermost.go
Commit message (Collapse)AuthorAgeFilesLines
* Add support for mattermost v6Wim2021-10-161-13/+81
|
* Refactor "msg-parent-not-found" to config.ParentIDNotFound (#1347)Qais Patankar2020-12-311-1/+1
|
* Add threading support with token (discord) (#1342)Wim2020-12-311-0/+9
| | | | | | | | Webhooks don't support the threading yet, so this is token only. In discord you can reply on each message of a thread, but this is not possible in mattermost (so some changes added there to make sure we always answer on the rootID of the thread). Also needs some more testing with slack. update : It now also uses the token when replying to a thread (even if webhooks are enabled), until webhooks have support for threads.
* Handle unthreaded messages (mattermost). Fixes #803Wim2019-04-191-0/+6
|
* Add support for mattermost threading (#627)Patrick Connolly2019-01-091-2/+2
|
* Refactor mattermost bridge (#622)Wim2018-12-011-344/+10
| | | | | * Split up in different files * Decrease complexity * Fix linting issues
* Update direct dependencies where possibleDuco van Amstel2018-11-251-1/+1
|
* Fix golint linter issues and enable it in CI (#593)Duco van Amstel2018-11-151-7/+7
|
* Fix goconst linter failureWim2018-11-131-3/+5
|
* Disable Connect(), JoinChannel(), Send() for mattermost.pluginWim2018-11-111-0/+9
|
* Make scopelint happyWim2018-11-081-0/+1
|
* Make goconst linter happyWim2018-11-081-4/+5
|
* Make gocritic linter happierWim2018-11-081-7/+9
|
* Add better support for multiperson DM (mattermost)Wim2018-10-271-4/+4
|
* Split up cookie token and personal token (mattermost). Fixes #530 (#540)Wim2018-10-261-1/+1
|
* Fix panic by using matterclient calls in the right place. Related to ↵Wim2018-08-301-3/+5
| | | | cb7278eb (mattermost). Closes #491
* Fix avatar uploads to work with MediaDownloadPath. Closes #454Wim2018-07-111-1/+1
|
* Use nickname instead of username if defined (mattermost). Closes #452Wim2018-07-031-0/+3
|
* Handle slack attachments sent to mattermost. Closes #447Wim2018-06-161-0/+12
|
* Reconnect on quit. (irc) See #431 (#445)Liam Stanley2018-06-091-1/+2
| | | | | * potential fixes for #431 * go: fix formatting/gofmt/goreturns
* Fix iconurl regression (mattermost,slack,rocketchat). Closes #430Wim2018-05-271-2/+4
|
* Use uuid instead of userid. Fixes #429Wim2018-05-271-3/+6
|
* Make our callbackid more unique. Fixes issue with running multiple ↵Wim2018-04-131-3/+3
| | | | matterbridge on the same channel (slack,mattermost)
* Add support for NoSendJoinPart. Closes #382Wim2018-03-061-0/+3
|
* Remove debug messsage (mattermost)Wim2018-03-051-1/+0
|
* Use viper (github.com/spf13/viper) for configurationWim2018-03-041-41/+42
|
* Improve debug messagesWim2018-02-281-4/+4
|
* Refactor using factoryWim2018-02-271-41/+34
|
* Make gometalinter happierWim2018-02-271-5/+5
|
* Skip events for webhookWim2018-02-271-0/+5
|
* Refactor mattermostWim2018-02-271-176/+206
|
* Make matterclient work with prefixed logWim2018-02-211-0/+3
|
* Use prefixed-formatter for better loggingWim2018-02-211-1/+1
|
* Move Sirupsen => sirupsenWim2018-02-201-1/+1
|
* Download (and upload) avatar images from mattermost and telegram when ↵Wim2018-02-201-2/+45
| | | | | | | | | | | | | | mediaserver is configured. Closes #362 An extra avatarMap (cache) is created for mattermost and telegram. If MediaServerUpload is configured, the avatar images of users are downloaded the first time a user sends a message. If this download succeeds a message with EVENT_AVATAR_DOWNLOAD is sent to the originating protocol. This message also contains a SHA field (in msg.Extra["file"]), if this is not empty, the sha will be added to the avatarMap. (so we now have a userid-sha cache) Next time this user sends a message, the MediaServerUpload/sha/userid.png URL will be used as the avatar field.
* Send chat notification if media is too big to be re-uploaded to MediaServer. ↵Wim2018-02-031-0/+12
| | | | See #359
* Download files and reupload to supported bridges (mattermost). Closes #357Wim2018-02-021-2/+18
|
* Add URL to message in webhook if available (mattermost). See #356Wim2018-01-311-1/+12
|
* Fix regression in mattermost bridge (mattermost). Closes #327Wim2018-01-011-4/+1
|
* Refactor and add MediaDownloadSize to GeneralWim2017-12-191-5/+3
|
* Add support for comments from slack file uploads (slack)Wim2017-11-131-2/+2
|
* Fix loop, make megacheck happyWim2017-09-211-11/+16
|
* Download files from slack and reupload to mattermost (slack/mattermost). ↵Wim2017-09-211-3/+18
| | | | | | | | | | | | Closes #255 Refactor message.Extra to a map[string][]interface{} to have a bit more flexibility for stuffing extra stuff. For attached files from slack, files < 1MB size get downloaded (in memory), and get put into Extra["file"][]config.FileInfo (containing a pointer to the buffer and the filename). This is not async so slack channels with lots of attached files may suffer a slowdown. (the download timeout is set at 5 seconds).
* Fix loop from webhook by adding matterbridge prop (mattermost). Closes #261Wim2017-09-181-0/+7
|
* Relay attachments from mattermost to slack (slack). Closes #260Wim2017-09-181-2/+8
|
* Use override username if specified (mattermost). #260Wim2017-09-181-0/+6
|
* Add support for deleting messages across bridges.Wim2017-09-111-2/+12
| | | | | | | | | | | | Currently fully support mattermost,slack and discord. Message deleted on the bridge or received from other bridges will be deleted. Partially support for Gitter. Gitter bridge will delete messages received from other bridges. But if you delete a message on gitter, this deletion will not be sent to other bridges (this is a gitter API limitation, it doesn't propogate edits or deletes via the API)
* Send images when text is empty regression. (mattermost). Closes #254Wim2017-09-081-0/+1
|
* Fix private channel joining bug (mattermost). Closes #248Wim2017-08-301-1/+6
|
* Add support for editing messages across bridges. Currently mattermost/discord.Wim2017-08-281-3/+7
| | | | | | | | | | | | | | | | | | | | | | Our Message type has an extra ID field which contains the message ID of the specific bridge. The Send() function has been modified to return a msg ID (after the message to that specific bridge has been created). There is a lru cache of 5000 entries (message IDs). All in memory, so editing messages will only work for messages the bot has seen. Currently we go out from the idea that every message ID is unique, so we don't keep the ID separate for each bridge. (we do for each gateway though) If there's a new message from a bridge, we put that message ID in the LRU cache as key and the []*BrMsgID as value (this slice contains the message ID's of each bridge that received the new message) If there's a new message and this message ID already exists in the cache, it must be an updated message. The value from the cache gets checked for each bridge and if there is a message ID for this bridge, the ID will be added to the Message{} sent to that bridge. If the bridge sees that the ID isn't empty, it'll know it has to update the message with that specific ID instead of creating a new message.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-28 03:14:14 +0000