| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
See https://blog.gitter.im/2023/02/13/gitter-has-fully-migrated-to-matrix/
|
| | |
|
| |
|
|
|
|
| |
Harmony is a relatively new (1,5yo) chat protocol with a small community.
This introduces support for Harmony into Matterbridge, using the functionality
specifically designed for bridge bots. The implementation is a modest 200 lines
of code.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add vk bridge
* Vk bridge attachments
* Vk bridge forwarded messages
* Vk bridge sample config and code cleanup
* Vk bridge add vendor
* Vk bridge message edit
* Vk bridge: fix fetching names of other bots
* Vk bridge: code cleanup
* Vk bridge: fix shadows declaration
* Vk bridge: remove UseFileURL
|
| | |
|
| |
|
| |
Signed-off-by: Gary Kim <gary@garykim.dev>
|
| |
|
|
|
|
|
|
| |
By default all bridges are available.
You can turn off certain bridges by providing
e.g. "nodiscord" as a build tag.
go build -tags nomsteams,noapi
|
| |
|
|
| |
Documentation on https://github.com/42wim/matterbridge/wiki/MS-Teams-setup
|
| |
|
|
|
|
|
|
| |
* Add Discord to UserTypingSupport
* discord: start typing in a channel on EventUserTyping receive
* discord: emit EventUserTyping to gateway
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
