Skip to content

wamux-http 0.1.3

Latest

Choose a tag to compare

@github-actions github-actions released this 10 Nov 19:54
v0.1.3
e91648d

Added

  • POST /api/sendPollVote votes in a channel poll (#2). The poll is found by
    its message id in the channel's last 300 messages, or named directly by
    WAHA's pollServerId. Each option is sent as the hash of its name exactly
    as the poll spells it, so a name retyped without its emoji variation
    selector or ZWJ answers 400. Every vote carries the whole selection, and an
    empty votes removes the vote.
  • A reply (reply_to on sendText, the media sends and sendContactVcard)
    carries the quoted message's content when the edge stored it, so a
    receiver that does not hold the original still shows what was quoted, as
    GOWS does. Needs wamux v0.2.4.

Changed

  • The wamux contract is v0.2.4, and the reference compose.yaml runs the
    core v0.2.4, whose image ships its own /tmp.

Fixed

  • Starting a session again after a logout, from the API or from the phone,
    left it FAILED instead of asking for a QR: the core keeps a logged-out
    account's identity, logs it in, and WhatsApp answers 401. The edge now
    replaces such an account in the core with a new one under the same name.
  • A stop or a start could be overwritten by an event of the session's
    previous start handled at the same moment: a deleted session could end
    with FAILED after STOPPED (its own logout's LOGGED_OUT), and a
    session started right after a logout could be stopped again. What the
    session's follower writes, and the session.status it publishes, now
    apply only while the session is still in the start it serves.
  • A session whose QR codes ran out stayed SCAN_QR_CODE and retried, and
    between retries (up to a minute) it served the last QR, which the phone
    no longer takes ("couldn't link device"). It now ends FAILED, as GOWS
    ends its QR timeout, until it is started again. A route's 422 for a
    FAILED session now says FAILED, not STOPPED.
  • Starting a session could publish STARTING twice, when its follower read
    the session between the start and its status.
  • The message.ack of my own edit, revoke, reaction or poll vote named the
    peer's LID chat when its event had named the phone chat, because the
    receipt names the peer by LID (#3). Each ack now names the id its event
    went out under.
  • GET /api/contacts by phone number answered pushname: null for a peer
    whose push name the edge had under its LID only (#4), as a history sync
    or a message by LID leaves it. A lookup now fills a missing name from the
    peer's other id, resolved by the core, and a message's push name is kept
    under both of the sender's ids, as whatsmeow keeps it.
  • Logging out or deleting a session left the device in the phone's linked
    devices: the edge stopped the session before asking the core to log out,
    and the core logs out only a connected account. The logout now comes
    first, and a stopped session is connected for it.
  • A reply in a DM to a message stored under the peer's LID chat went out
    as a reply from another chat (the LID as remoteJid). Only a group
    message or a status is quoted from another chat now.
  • An event from the core over 4 MiB (a history sync, 4.67 MB measured)
    broke the session's event stream, losing it. The edge now takes up to
    256 MiB.

Run

Both images run the binary in the tarball below, as uid 10001, from scratch:

  • ghcr.io/llawli/wamux-http:v0.1.3: the binary alone
  • ghcr.io/llawli/wamux-http:v0.1.3-ffmpeg: plus ffmpeg and ffprobe, for voice and video conversion, waveforms and durations

Next to the core: the reference compose.yaml.

Licenses

MIT OR Apache-2.0. The tarball and both images carry THIRD-PARTY-LICENSES.md for the code the binary links. The ffmpeg and ffprobe of the -ffmpeg image are GPL-3.0-or-later: the image carries their licenses in /usr/local/share/doc/ffmpeg, whose SOURCE.md names the release that holds their complete corresponding source.

Verify

The tarball and both images carry a build provenance attestation; the images are published by a job that starts after this release, so they can appear a few minutes later.

gh attestation verify wamux-http-0.1.3-linux-amd64.tar.gz -R LLawli/wamux-http
gh attestation verify oci://ghcr.io/llawli/wamux-http:v0.1.3 -R LLawli/wamux-http