summaryrefslogtreecommitdiffstats
path: root/vendor/github.com/pelletier/go-toml/benchmark.yml
diff options
context:
space:
mode:
authorescoand <escoand@users.noreply.github.com>2020-08-26 22:27:50 +0200
committerGitHub <noreply@github.com>2020-08-26 22:27:50 +0200
commit58b6c4d277d4577baadc376deee7d306c332f420 (patch)
tree43a2220c110a2c250fe8a7f1975656ae363858c9 /vendor/github.com/pelletier/go-toml/benchmark.yml
parent27c02549c870680ea57a05757810ade80db42929 (diff)
downloadmatterbridge-msglm-58b6c4d277d4577baadc376deee7d306c332f420.tar.gz
matterbridge-msglm-58b6c4d277d4577baadc376deee7d306c332f420.tar.bz2
matterbridge-msglm-58b6c4d277d4577baadc376deee7d306c332f420.zip
Handle broadcasts as groups in Whatsapp (#1213)
The current way to get the correct JID of a WhatsApp group is to dump all JIDs to the log and grab the right one. This is working for for groups fine but not for broadcast, as they are not print out. According to https://www.npmjs.com/package/@noamalffasy/js-whatsapp we have these possibilities: * Chats: `[country code][phone number]@s.whatsapp.net` * Groups: `[country code][phone number of creator]-[timestamp of group creation]@g.us` * Broadcast Channels: `[timestamp of group creation]@broadcast` But the bridge does currently interprets (and prints) the only second option.
Diffstat (limited to 'vendor/github.com/pelletier/go-toml/benchmark.yml')
0 files changed, 0 insertions, 0 deletions