Skip to content

fix: improve chat storage scaling and privacy#10

Merged
shakkernerd merged 1 commit into
mainfrom
db-scale-hardening
May 11, 2026
Merged

fix: improve chat storage scaling and privacy#10
shakkernerd merged 1 commit into
mainfrom
db-scale-hardening

Conversation

@shakkernerd
Copy link
Copy Markdown
Member

Summary

  • add private durable event storage with events.is_private and event_recipients
  • tighten DM access for replay, search, threads, reactions, edits, deletes, uploads, and read receipts
  • add root-message-only paging/read semantics for DMs so thread replies do not affect timeline unread counts
  • add event pruning with retention bounds and safe timestamp cutoff handling
  • batch DM member and attachment hydration, plus add indexes for message paging, replay, and hydration hot paths
  • update docs, OpenAPI, SDK search helper, and embedded web assets

Verification

  • go test ./apps/api/internal/store/sqlite -run 'TestMessagePrivacyScaling' -count=1\n- go test ./apps/api/internal/store/sqlite -run 'TestMessagePrivacyScalingEventPruningUsesTimestampCutoff' -count=1 -v\n- pnpm check\n- pnpm coverage\n- git diff --check

@shakkernerd shakkernerd merged commit 4d52642 into main May 11, 2026
4 checks passed
@shakkernerd shakkernerd deleted the db-scale-hardening branch May 11, 2026 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant