1
0
Fork 0
Commit Graph

8 Commits

Author SHA1 Message Date
nicoco 4c88f75a88 doc: point to raver's dockerhub for arm64 containers 2024-02-17 14:50:01 +01:00
Alex Palaistras a0fb2a59bd Fix changes made by Copier update 2023-09-30 13:12:43 +01:00
nicoco f71e1598b3 chore: update copier 2023-09-28 22:12:22 +02:00
nicoco d74700fd83 chore: update copier 2023-08-12 11:52:08 +01:00
Alex Palaistras 5473f25a24 Implement on-the-fly outgoing media conversion
WhatsApp clients are set to accept only a specific set of media files as
image, audio, or video messages, specifically:

  - Images must be in JPEG (non-progressive) format.
  - Audio messages must be in Opus-encoded Ogg if sent as voice messages,
    otherwise may be in MP3 or AAC format if not (though client support
    may vary).
  - Video messages must be in h264-encoded MP4, with some additional
    constraints on color format and profile used.

Several edge-cases exist, e.g. with GIF files needing to be re-encoded
as MP4 in order to be animated (and requiring extra metadata in messages
to be called out as such).

This commit implements a somewhat comprehensive media conversion scheme,
built upon FFmpeg for audio and video, and native Go facilities for
images, based on the source format. Specifically:

  - Audio files in `audio/mp4` or `audio/aac` format (corresponding to
    formats commonly used in Android and iOS XMPP clients, respectively)
    are automatically re-encoded as Opus-encoded voice messages.

  - Audio files in `audio/mpeg` (i.e. MP3 files) or `audio/ogg` format
    are sent as plain audio files in their own format, with varying client
    support assumed.

  - Images in `image/png` or `image/webp` format are automatically
    re-encoded as JPEG image messages. Conversely, images in `image/gif`
    format are re-encoded as MP4 video messages with auto-play enabled.

  - Videos in `video/webm` or `video/mp4` format are automatically
    re-encoded as MP4 video messages (the latter is re-encoded to ensure
    option compatibility).

As stated above, all audio and video conversions require FFmpeg and
FFprobe to be installed, and, if missing, will leave attachments
unchanged (which may result these being sent as binary files). Image
conversions do not rely on any external functionality, however.

Current limits are: 10MiB for images and 20MiB for audio and video
files; above these conversions will fail and original files will be sent
instead.

Future commits may see compatibility improved, or semantics corrected
where these do not match expectations on the WhatsApp side.
2023-07-22 09:58:22 +01:00
nicoco 35918a627b update copier template 2023-06-23 23:24:29 +02:00
Alex Palaistras 868dd3f6ae Use local Slidge Core mount for development
Core changes are reflected in our development containers via a
locally-cloned `slidge` repository, adjacent to this repository.
2023-06-18 21:43:35 +01:00
nicoco f0ffdaa0be Initial commit (split from slidge core) 2023-05-02 16:35:30 +02:00