summaryrefslogtreecommitdiffstats
path: root/gateway/bridgemap/bridgemap.go
Commit message (Collapse)AuthorAgeFilesLines
* Add initial Microsoft Teams supportWim2020-03-011-0/+2
| | | | Documentation on https://github.com/42wim/matterbridge/wiki/MS-Teams-setup
* Add UserTypingSupport (discord) (#914)Qais Patankar2019-10-041-1/+2
| | | | | | | | * Add Discord to UserTypingSupport * discord: start typing in a channel on EventUserTyping receive * discord: emit EventUserTyping to gateway
* Add initial Keybase Chat support (#877)cori hudson2019-08-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * initial work on native keybase bridging * Hopefully make a functional keybase bridge * add keybase to bridgemap * send to right channel, try to figure out received msgs * add account and userid * i am a Dam Fool * Fix formatting for messages, handle /me * update vendors, ran golint and goimports * move handlers to handlers.go, clean up unused config options * add sample config, fix inconsistent remote nick handling * Update readme with keybase links * Resolve fixmie errors * Error -> Errorf * fix linting errors in go.mod and go.sum * explicitly join channels, ignore messages from non-specified channels * check that team names match before bridging message
* Forward only user-typing messages if supported by protocol (#832)Duco van Amstel2019-05-301-30/+36
| | | | | | | | | | 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.
* Add initial WhatsApp support (#711)Krzysiek Madejski2019-02-211-0/+2
|
* Extract bridgeMap into own package to improve testability (#601)Patrick Connolly2018-11-301-0/+35