Skip to content

Commit b040334

Browse files
committed
fix: blinded msg request should rely on ts check of communities
1 parent 50d65da commit b040334

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

ts/receiver/contentMessage.ts

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -386,7 +386,11 @@ export async function innerHandleSwarmContentMessage({
386386
window.log.info('innerHandleSwarmContentMessage');
387387

388388
const content = SignalService.Content.decode(new Uint8Array(contentDecrypted));
389-
if (!shouldProcessContentMessage(envelope, content, false)) {
389+
// This function gets called with an inbox content from a community. When that's the case,
390+
// the messageHash is empty.
391+
// `shouldProcessContentMessage` is a lot less strict in terms of timestamps for community messages, and needs to be.
392+
// Not having this isCommunity flag set to true would make any incoming message from a blinded message request be dropped.
393+
if (!shouldProcessContentMessage(envelope, content, !messageHash)) {
390394
window.log.info(
391395
`innerHandleSwarmContentMessage: dropping invalid content message ${envelope.timestamp}`
392396
);

0 commit comments

Comments
 (0)