summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Fix panic by checking slice bounds in handleEntities (telegram). Fixes #857 ↵Wim2019-07-081-3/+9
| | | | | | (#858) Besides the bound checking, this now also use utf16 as suggested by https://github.com/go-telegram-bot-api/telegram-bot-api/issues/231
* Support webhook message deletions (discord) (#853)Qais Patankar2019-07-083-9/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Support webhook message deletions (discord) Messages sent via webhook can now be deleted. It seems it can do this without any special permissions. This copies discordgo.WebhookExecute and makes it support the returning of discordgo.Message. A pull request has been sent upstream, so we should use that if @bwmariin accepts the pull request: https://github.com/bwmarrin/discordgo/pull/663 Changes in behaviour (webhook mode only): - Previously messages *edited* on other platforms would just be retransmitted as a brand new message to Discord. - Message *edits* will now be ignored. - Debug: message edits will now print out a "permission error". In the future it may be good to send an "message edited" react to those webhook messages, so at least people know that the message was edited on other platforms. (Even though it can't actually show the new message.) Alternatively, message edits could just send a brand new message with a link back to the old one. This is a little ugly but it would ensure that Discord users are able to see the edited message. These "message edit notifications" would be sent from the bot user (not from a webhook), so we could edit the "edit notification" if subsequent edits to the original message are made.
* Update changelogWim2019-06-301-0/+2
|
* Update to golanci-lint v1.17.1Wim2019-06-301-1/+1
|
* Keep connection state. Fixes #856Wim2019-06-301-0/+23
| | | | | | | | Actually check if we're connected when trying to Send() a message. Messages now will get dropped when not connected. TODO: Ideally this should be in a ring buffer to retransmit when the connection comes back up.
* Update readmeWim2019-06-161-2/+7
|
* Update vendor (#852)Wim2019-06-16294-6856/+71442
|
* Add .gitignore (#850)Qais Patankar2019-06-161-0/+5
|
* Update documentation and changelogWim2019-06-162-0/+12
|
* Add an option to skip the Mattermost server version check (#849)Joona Hoikkala2019-06-164-14/+21
| | | Adds SkipVersionCheck bool option for mattermost
* Support bulk deletions (discord)Qais Patankar2019-06-162-0/+22
|
* Bump versionWim2019-06-161-1/+1
|
* Release v1.15.0v1.15.0Wim2019-06-143-2/+30
|
* Verify TLS against JID domain, not the host. (xmpp) (#834)Nick2019-06-141-1/+1
| | | | | Partially fixes #820. A full fix requires patching https://github.com/matterbridge/go-xmpp to use DNS SRV records.
* Fix logic (xmpp)Wim2019-06-141-1/+1
|
* Fix regression in autojoining with legacy tokens (slack). Fixes #651 (#848)Wim2019-06-142-2/+18
|
* Allow messages with timestamp (xmpp). Fixes #835 (#847)Wim2019-06-141-1/+1
|
* Fix noisy whatsapp error loggingWim2019-06-141-0/+4
|
* Update github.com/Rhymen/go-whatsapp vendor. Fixes #843Wim2019-06-1412-58/+213
|
* Revert xmpp to orig behaviour. Closes #844Wim2019-06-131-1/+1
|
* Make config parse errors readableWim2019-06-021-2/+2
|
* Fix go mod issue by removing whatsapp-extWim2019-06-0216-1484/+32
|
* Forward only user-typing messages if supported by protocol (#832)Duco van Amstel2019-05-302-30/+45
| | | | | | | | | | Fixes issue #814. This is a somewhat hacky way of achieving the required goal but it seems like this is the least problematic way of getting there. We might want to redesign some bridge information later such that we have a standardised way of specifying what is and what isn't supported by each chat protocol / bridge.
* Clean-up XMPP handling code (#831)Duco van Amstel2019-05-301-77/+129
|
* Use upstream whatsapp again (#809)Wim2019-05-3089-1257/+2145
|
* Linter fixesDuco van Amstel2019-05-271-7/+11
|
* Update channels of all teams (mattermost)Wim2019-05-021-9/+24
|
* Allow messages from other bots (discord). Fixes #816Wim2019-05-011-1/+1
|
* Add msg event to tengoWim2019-04-242-2/+4
|
* Update README with v1.14.4Wim2019-04-231-1/+1
|
* Update changelogWim2019-04-231-0/+10
|
* Disable user lookups on delete messages (slack) (#812)Wim2019-04-231-11/+11
|
* Add lacking clean-up in Slack synchronisation (#811)Duco van Amstel2019-04-231-4/+5
|
* Use paging in initUser and UpdateUsers (mattermost)Wim2019-04-202-9/+31
|
* Handle unthreaded messages (mattermost). Fixes #803Wim2019-04-191-0/+6
|
* Fix panic on nil message.Post (mattermost). Fixes #804Wim2019-04-191-0/+6
|
* Add Id to EditMessage (mattermost). Fixes #802Wim2019-04-191-1/+1
|
* Add scripting (tengo) support for every outgoing message (#806)Wim2019-04-197-7/+383
| | | | | | | | | | | | | | | | | | Adds a new key OutMessage under [tengo] table, which specifies the location of the script that will be invoked on each message being sent to a bridge and can be used to modify the Username and the Text of that message. The script will have the following global variables: read-only: inAccount, inProtocol, inChannel, inGateway outAccount, outProtocol, outChannel, outGateway read-write: msgText, msgUsername The script is reloaded on every message, so you can modify the script on the fly. The default script in https://github.com/42wim/matterbridge/tree/master/internal/tengo/outmessage.tengo is compiled in and will be executed if no script is specified.
* Bump versionWim2019-04-191-1/+1
|
* Update changelogWim2019-04-191-0/+5
|
* Remove deprecated TengoModifyMessageWim2019-04-191-23/+0
| | | | This has become InMessage under [tengo]
* Add verbose IRC joins/parts (ident@host) (#805)chotaire2019-04-183-2/+13
| | | New configuration setting: VerboseJoinPart (default is false)
* Fix deadlock on reconnect (irc). Closes #757Wim2019-04-152-2/+5
|
* Remove hipchatWim2019-04-142-93/+2
|
* Update READMEWim2019-04-141-3/+7
|
* Add remotenickformat-zerowidth.tengo to contrib (#799)Qais Patankar2019-04-141-0/+16
|
* Send channel_created and deleted event through message channel (mattermost)Wim2019-04-131-1/+4
|
* Add useraction support (rocketchat). Closes #772 (#794)Wim2019-04-081-0/+5
|
* Add tengo support to RemoteNickFormat (#793)Wim2019-04-084-0/+98
| | | | | | | | | | | | | | | | | | | This commit add support for using the result of a tengo script in RemoteNickFormat using {TENGO} Also adds a new toml table [tengo] with key RemoteNickFormat and value location of the script. This also moves the TengoModifyMessage from [general] to Message in [tengo] Documentation: RemoteNickFormat allows you to specify the location of a tengo (https://github.com/d5/tengo/) script. The script will have the following global variables: to modify: result to read: channel, bridge, gateway, protocol, nick The result will be set in {TENGO} in the RemoteNickFormat key of every bridge where {TENGO} is specified The script is reloaded on every message, so you can modify the script on the fly. Example script can be found in https://github.com/42wim/matterbridge/tree/master/contrib/remotenickformat.tengo [tengo] RemoteNickFormat="remotenickformat.tengo"
* Build on every branch (travis)Wim2019-04-071-0/+1
|