matterbridge-msglm - A fork of matterbridge with some patches.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix golint linter issues and enable it in CI (#593)	Duco van Amstel	2018-11-15	1	-3/+3
\|
*	Make config.Config more unit-test friendly (#586)	Duco van Amstel	2018-11-13	1	-6/+11
\|
*	Add support for mattermost matterbridge plugin	Wim	2018-11-11	1	-3/+4
\|
*	Make scopelint happy	Wim	2018-11-08	1	-0/+1
\|
*	Reconnect on quit. (irc) See #431 (#445)	Liam Stanley	2018-06-09	1	-1/+2
\| \| \| \| \|	* potential fixes for #431 * go: fix formatting/gofmt/goreturns
*	Do some small cleanups	Wim	2018-02-27	1	-5/+1
\|
*	Use prefixed-formatter for better logging	Wim	2018-02-21	1	-3/+3
\|
*	Move Sirupsen => sirupsen	Wim	2018-02-20	1	-1/+2
\|
*	Add initial support for an external mediaserver. #278	Wim	2017-11-24	1	-0/+1
\| \| \| \| \| \| \| \|	Add 2 extra options `MediaServerUpload` and `MediaServerDownload`, where the URL for upload and download can be specified. See https://github.com/42wim/matterbridge/wiki/Mediaserver-setup-%5Badvanced%5D for an example with caddy
*	Do not add messages without ID to cache	Wim	2017-08-29	1	-1/+1
\|
*	Add support for editing messages across bridges. Currently mattermost/discord.	Wim	2017-08-28	1	-1/+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.
*	Remove unused function	Wim	2017-07-30	1	-10/+0
\|
*	Handle same account in multiple gateways better	Wim	2017-07-30	1	-10/+9
\|
*	Refactor. Add tests	Wim	2017-07-25	1	-0/+117