plogme 1.0.4 → 1.0.5

package/README.md

@@ -490,3 +490,71 @@ Review the included license before distributing applications built with `plogme`
 ## Support
 
 For implementation questions, include the Node.js version, `plogme` version, operating system, relevant error text, and a minimal reproducible example. Never include authentication state or private account data in an issue.
+
+
+## Ported WhatsApp Web protocol features
+
+The bundled WAProto schema is updated to WhatsApp Web version `2.3000.1047412487`, with the generated runtime, TypeScript declarations, and connection version updated together. Selected support includes newsletter follower-invite base/V2 fields, ACP2 receive-state extraction, animated wallpaper encoding, and nested audio in sticker messages. These remain experimental and client-dependent.
+
+### Animated wallpaper
+
+```js
+await sock.sendMessage(jid, {
+  chatTheme: {
+    animatedWallpaper: { id: 'wallpaper-id', dimLevel: 0.25 }
+  }
+})
+```
+
+### Sticker with audio
+
+```js
+await sock.sendMessage(jid, {
+  sticker: { url: './sticker.webp' },
+  stickerAudio: { url: './sound.ogg' }
+})
+```
+
+### Newsletter follower invites
+
+```js
+await sock.sendMessage(jid, {
+  newsletterFollowerInvite: {
+    newsletterJid: '123456789@newsletter',
+    newsletterName: 'My newsletter',
+    caption: 'Follow this channel'
+  }
+})
+
+await sock.sendMessage(jid, {
+  newsletterFollowerInviteMessageV2: {
+    newsletterJid: '123456789@newsletter',
+    newsletterName: 'My newsletter',
+    caption: 'Follow this channel'
+  }
+})
+```
+
+### Device-scoped relay options
+
+`relayMessage` supports `isSecret`, `protected`, and `me` for supported private-chat device fan-out paths. These select recipients and may add `device_fanout`; they are not encryption, access-control, or delivery guarantees and may not behave identically for groups, statuses, retries, or future clients. They are unrelated to the protobuf field `messageContextInfo.messageSecret`.
+
+```js
+await sock.relayMessage(jid, message, {
+  messageId: messageId,
+  isSecret: true
+})
+```
+
+### Explicit album wrapper
+
+Albums remain parent/child wire messages: one album header is relayed first, followed by separately encrypted image/video children associated with the parent key. The receiver must group them visually. The explicit wrapper accepts typed media objects and applies a caption to the first child:
+
+```js
+await sock.sendAlbumMessage(jid, [
+  { type: 'image', data: { url: './one.jpg' } },
+  { type: 'image', data: { url: './two.jpg' } }
+], { caption: 'Album caption' })
+```
+
+Rich HTML and bot-forwarded messages cannot be album children; send those separately. Album grouping is still dependent on WhatsApp server/client behavior.