Releases: mautrix/whatsapp
Releases · mautrix/whatsapp
v0.1.8
N.B. Docker images have moved from dock.mau.dev/tulir/mautrix-whatsapp to dock.mau.dev/mautrix/whatsapp. New versions are only available at the new path.
- Added very basic support for bridging MSC3245 voice messages into push-to-talk messages on WhatsApp.
- Added support for Matrix->WhatsApp location messages.
- Renamed
whatsapp_message_ageandwhatsapp_messageprometheus metrics toremote_event_ageandremote_eventrespectively. - Fixed handling sticker gifs from Matrix.
- Fixed bridging audio/video duration from/to WhatsApp.
- Fixed messages not going through until restart if initial room creation attempt fails.
- Fixed issues where some WhatsApp protocol message in new chats prevented the first actual message from being bridged.
- Fixed some media from WhatsApp not being bridged due to file length or checksum mismatches. WhatsApp clients don't seem to care, so the bridge also ignores those errors now.
v0.1.7
- Added option to disable creating WhatsApp status broadcast rooms (#166).
- Added option to bridge chat archive, pin and mute statuses from WhatsApp.
- Moved Matrix HTTP request retrying to mautrix-go (which now retries all requests instead of only send message requests).
- Made bridge status reporting more generic (now takes an arbitrary HTTP endpoint to push bridge status to instead of requiring mautrix-asmux).
- Updated error messages sent to Matrix to be more understandable if WhatsApp returns status code 400 or 599.
- Fixed encryption getting messed up after receiving inbound olm sessions if using SQLite.
- Fixed bridge sending old messages after new ones if initial backfill limit is low and bridge gets restarted.
- Fixed read receipt bridging sometimes marking too many messages as read on Matrix (and then echoing it back to WhatsApp).
- Fixed false-positive message send error that showed up on WhatsApp mobile for messages sent from Matrix.
- Fixed ghost user displaynames for newly added group members never getting set if
chat_meta_syncis false.
v0.1.6
- Added support for broadcast lists.
- Added automatic re-login-matrix using login shared secret if
/syncreturnsM_UNKNOWN_TOKEN. - Added syncing of contact info when syncing room members to ensure that WhatsApp ghost users have displaynames before the Matrix user sees them for the first time.
- Added bridging of own WhatsApp read receipts after backfilling.
- Added option not to re-sync chat info and user avatars on startup to avoid WhatsApp rate limits (error 599).
- When resync is disabled, chat info changes will still come through by backfilling messages. However, user avatars will currently not update after being synced once.
- Improved automatic reconnection to work more like WhatsApp Web.
- The bridge no longer disconnects the websocket if the phone stops responding. Instead it sends periodic pings until the phone responds.
- Outgoing messages will be queued and resent automatically when the phone responds again.
- Added option to disable bridging messages where the
msgtypeism.notice(thanks to @hramirezf in #259). - Fixed backfilling failing in some cases due to 404 errors.
- Merged the whatsapp-ext module into go-whatsapp.
- Disabled personal filtering communities by default
- Updated Docker image to Alpine 3.13
v0.1.5
- Renamed device name fields in config from
device_nameandshort_nametoos_nameandbrowser_namerespectively. - Replaced shared secret login with appservice login (MSC2778) when logging into bridge bot for e2be.
- Removed webp conversion for WhatsApp→Matrix stickers.
- Added short wait if encrypted message arrives before decryption keys.
- Added bridge error notices if messages fail to decrypt.
- Added command to discard the bridge's Megolm session in a room.
- Added retrying for Matrix message sending if server returns 502.
- Added browser-compatible authentication to login API websocket.
- Fixed creating new WhatsApp groups for unencrypted Matrix rooms (#209).
- Changed provisioning API to automatically delete session if logout request fails.
- Changed CI to statically compile olm into the bridge executable.
- Fixed bridging changes to group read-only status to Matrix (#228, thanks to @rreuvekamp in #232).
- Fixed bridging names of files that were sent from another bridge.
- Fixed handling empty commands.
v0.1.4
- Added better error reporting for media bridging errors
- Added bridging for own read receipts from WhatsApp mobile when using double puppeting
- Added build tag to disable crypto without disabling SQLite
- Added support for automatic key sharing
- Added option to update
m.directwhen using double puppeting - Made read receipt bridging toggleable separately from presence bridging
- Fixed the formatter bridging all numbers starting with
@on WhatsApp into pills on Matrix (now it only bridges actual mentions into pills) - Fixed handling new contacts and receiving names of non-contacts in groups when they send a message
v0.1.3
- Added command to create WhatsApp groups
- Added command to disable bridging presence and read receipts
- Added full group member syncing (including kicking of users who left before)
- Allowed creating private chat portal by inviting WhatsApp puppet (#110)
- Fixed bug where inaccessible private chat portals couldn't be recreated with
pmcommand (#188)
v0.1.2
- Added option to disable notifications during initial backfill
- Added bridging of contact and location messages
- Added support for leaving chats and kicking/inviting WhatsApp users from Matrix
- Added bridging of leaves/kicks/invites from WhatsApp to Matrix
- Added config option to re-send bridge info state event to all existing portals
- Added basic prometheus metrics
- Added low phone battery warning messages
- Added command to join groups with invite link
- Fixed media not being encrypted when sending to encrypted portal rooms