From 47ea8527fd175c55a6d0128b91aced13ea442135 Mon Sep 17 00:00:00 2001 From: Hazelnoot Date: Sat, 29 Mar 2025 09:44:38 -0400 Subject: [PATCH] fix wsmessage rate limit definition --- packages/backend/src/server/api/StreamingApiServerService.ts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/packages/backend/src/server/api/StreamingApiServerService.ts b/packages/backend/src/server/api/StreamingApiServerService.ts index c7db4549d3..d86deef1d7 100644 --- a/packages/backend/src/server/api/StreamingApiServerService.ts +++ b/packages/backend/src/server/api/StreamingApiServerService.ts @@ -160,8 +160,9 @@ export class StreamingApiServerService { // Rather high limit because when catching up at the top of a timeline, the frontend may render many many notes. // Each of which causes a message via `useNoteCapture` to ask for realtime updates of that note. return this.rateLimitThis(limitActor, { + type: 'bucket', key: 'wsmessage', - max: 4096, // Allow spikes of up to 4096 + size: 4096, // Allow spikes of up to 4096 dripRate: 50, // Then once every 50ms (20/second rate) }); };