@decentnetwork/peer 0.1.21 → 0.1.23

package/dist/peer.js

@@ -768,6 +768,7 @@ export class Peer {
                 return;
             }
             catch (error) {
+                const emsg = error.message;
                 // Mirrors Carrier C SDK behavior: when an in-session send fails
                 // (no transport accepted the encrypted packet), fall through to
                 // the express offline relay rather than dropping the message
@@ -775,7 +776,20 @@ export class Peer {
                 // express pull. Without this the message is just lost when the
                 // friend's NAT briefly forgets us — observed when iPad rebinds
                 // its TCP relay slot, or when UDP and TCP relay both blip.
-                this.#debugLog(`sendText: in-session send failed for ${pubkey}, falling back to express: ${error.message}`);
+                //
+                // EXCEPT a "payload too big" failure (>1373 bytes), which is
+                // PERMANENT, not transient: it fails identically every retry, so
+                // queuing it to express just piles undeliverable oversized blobs
+                // into the recipient's offline queue. A dora's oversized roster
+                // reply re-sent every 60s produced a 69k-message backlog that made
+                // every pull time out — starving real friend-requests. Oversized
+                // payloads must be chunked by the caller (the dora now paginates),
+                // not flooded through express; drop to the caller instead.
+                if (/1\.\.1373 bytes|payload must be 1/i.test(emsg)) {
+                    this.#debugLog(`sendText: oversized payload for ${pubkey} (${emsg}) — NOT queuing to express (would flood); caller must chunk`);
+                    throw error;
+                }
+                this.#debugLog(`sendText: in-session send failed for ${pubkey}, falling back to express: ${emsg}`);
             }
         }
         // Offline / fallback path via Carrier express HTTP store-and-forward.
@@ -1759,6 +1773,16 @@ export class Peer {
         catch {
             return;
         }
+        // Already an established friend? Ignore this (re-)request. Auto-friend
+        // re-sends and reconnect retries pile up offline friend-requests on the
+        // express relay; once we've accepted them, re-emitting would re-run the
+        // accept path and churn. The express pull still ack-deletes the stale R
+        // via its timestamp watermark — we just don't act on it again.
+        const existingFriend = this.#friends.get(fromUserId);
+        if (existingFriend?.acceptedAt || existingFriend?.status === "online") {
+            this.#debugLog(`ignoring offline friend-request from already-accepted friend ${fromUserId}`);
+            return;
+        }
         if (this.#pendingFriendRequests.has(fromUserId)) {
             return;
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@decentnetwork/peer",
-  "version": "0.1.21",
+  "version": "0.1.23",
   "description": "Pure TypeScript port of Elastos Carrier (toxcore-derived) P2P messaging. DHT, onion routing, TCP relay, FlatBuffers app payloads, Express offline relay. Wire-compatible with iOS Beagle and the Carrier C SDK.",
   "type": "module",
   "main": "./dist/index.js",