rmyndharis/OpenWA v0.2.7

on GitHub

A feature + fix release: typing simulation (anti-ban, on by default), a delete-chat endpoint, and a fix
for duplicate outgoing messages in the dashboard — plus engine-agnostic groundwork and the nginx/
singleton-lock container fixes.

Added

• Typing simulation before single sends (anti-ban), on by default. A text send now shows a "typing…"
  indicator and pauses briefly (length-scaled, jittered) before sending, so automated messages don't look
  instantaneous. Disable with SIMULATE_TYPING=false; cap the pause with SIMULATE_TYPING_MAX_MS
  (default 5000). Exposed engine-agnostically via IWhatsAppEngine.sendChatState and a new
  POST /sessions/:id/chats/typing endpoint (state: typing | recording | paused). Bulk sends are
  unaffected (they keep their own delayBetweenMessages throttle).
• The engine API (GET /infra/engines) and the dashboard Active Engine card now report the underlying
  engine library version (e.g. whatsapp-web.js 1.34.7), distinct from the adapter plugin version.
• Delete a chat from the chat list via POST /sessions/:id/chats/delete (e.g. to clear out groups
  you've left). OPERATOR role, engine-agnostic DTO. Thanks @tobiasstrebitzer (#261).

Fixed

• Duplicate outgoing messages in the dashboard Chats view. A race between the optimistic placeholder
  and the realtime message.sent echo could render a sent message twice. Reconciliation is now race-safe.
  (Display-only — the recipient always received exactly one message.)
• Dashboard (simple nginx image) proxied API/WebSocket requests to a openwa host that doesn't match the
  backend service name; dashboard/nginx.conf now targets openwa-api for both /api/ and /socket.io/,
  matching the production compose and Dockerfile.traefik. Thanks @Abhishekrajpurohit (#259).
• The container entrypoint now clears stale Chromium SingletonLock/SingletonSocket/SingletonCookie files
  from session profiles on start, so a session can re-launch after an unclean shutdown instead of failing with
  "profile appears to be in use by another Chromium process" (exit Code 21). Thanks @Abhishekrajpurohit (#259).

Changed

• mark-chat-read chatId validation is now engine-neutral (accepts any engine's JID scheme, e.g. a
  Baileys …@s.whatsapp.net) instead of hardcoding the whatsapp-web.js @c.us/@g.us/@lid format.