| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
Signed-off-by: Gary Kim <gary@garykim.dev>
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
| |
* Add Dockerfile with tgs to png conversion support
* Add .dockerignore to keep cache busts while testing low
|
| |
|
| |
Fixes #1047
|
| |
|
|
|
| |
* Fix another whatsapp panic
* Update whatsapp vendor
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is half a fix for #874
This patch introduces a new config flag:
- MediaConvertTgs
These need to be treated independently from the existing
MediaConvertWebPToPNG flag because Tgs→WebP results in an
*animated* WebP, and the WebP→PNG converter can't handle
animated WebP files yet.
Furthermore, some platforms (like discord) don't even support
animated WebP files, so the user may want to fall back to
static PNGs (not APNGs).
The final reason why this is only half a fix is that this
introduces an external dependency, namely lottie, to be
installed like this:
$ pip3 install lottie cairosvg
This patch works by writing the tgs to a temporary file in /tmp,
calling lottie to convert it (this conversion may take several seconds!),
and then deleting the temporary file.
The temporary file is absolutely necessary, as lottie refuses to
work on non-seekable files.
If anyone comes up with a reasonable use case where /tmp is
unavailable, I can add yet another config option for that, if desired.
Telegram will bail out if the option is configured but lottie isn't found.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
When there is a valid HTML formatting then remove this in the cleartext
field of the matrix client. This leads to nicer push messages on
smartphone apps.
Fix #1188
|
| | |
|
| |
|
|
| |
Add option to have all events send to the messagechan
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Fix #1177
Signed-off-by: Gary Kim <gary@garykim.dev>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Signed-off-by: Gary Kim <gary@garykim.dev>
|
| |
|
| |
Use Logfile option in the `[general]` section
|
| | |
|
| |
|
| |
Co-authored-by: Qais Patankar <qaisjp@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Before returning an empty string, we refresh the WhatsApp contacts and if we found the one we wanted, we can return a real name. Fixes #796
|
| | |
|
| |
|
|
| |
By default, gIRC rate limits all outgoing messages.
Since matterbridge already implements message throttling, this is extra layer of throttling is not necessary.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This change would be required for the Docker image to actually read `RELOADABLE` config options from the `matterbridge.toml`.
This edit would require https://github.com/42wim/matterbridge/wiki/Deploy:-Docker to be updated as well to mention that mounting would have to change to mounting a ***directory*** not a file. inotify inside Docker cannot read directly mounted files, only directories, for whatever reason.
This will preserve setups that were configured to run the old way without breaking them and new configs can be setup "correctly" without issue.
|
