5 Commits

Author	SHA1	Message	Date
Qais Patankar	ba6759010b	Add UserTypingSupport (discord) (#914) ... * Add Discord to UserTypingSupport * discord: start typing in a channel on EventUserTyping receive * discord: emit EventUserTyping to gateway	2019-10-04 00:18:56 +02:00
cori hudson	921f2dfcdf	Add initial Keybase Chat support (#877) ... * 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	2019-08-26 21:00:31 +02:00
Duco van Amstel	b79bf7d414	Forward only user-typing messages if supported by protocol (#832) ... 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.	2019-05-30 15:00:40 +02:00
Krzysiek Madejski	55e79063d6	Add initial WhatsApp support (#711)	2019-02-21 20:28:13 +01:00
Patrick Connolly	f2088a687e	Extract bridgeMap into own package to improve testability (#601)	2018-11-30 23:53:00 +01:00