Gather Details about API Spamming Issue

Around "GetComment" or batched, ~50req/sec

Don't know how to reproduce, @Untitled Contact reproduced with an existing db/node.

Maybe the issue is the frontend invalidation loop

Recent Optimizations

Improved rendering and data loading for query blocks

@Untitled Contact Feed rework and other minor perf improvements

Removed extra webrtc address storage.

Magical unexplained performance improvement since 5.5 to main

Logging aggregation - loggingsucks.com

Trace context

React-Virtualized (or similar) for document rendering

Document pagination for super-fast rendering of large documents

Show dependency trace in syncing panel

Migrate away from daemon sync subscriptions

Peer Store + Domain Store - suspected culprits of DB write contention

Burdi working on a golang single-connection sqlite DB writer, should avoid db locking issues

as seen by many and reported by Sofia

@Untitled Contact says that the document content is getting unmounted and remounted when RQ doc changes. [will file a GH issue]

Selected comment is renderd off the bottom of the screen - Horacio will fix

# Product Market Fit

@Untitled Contact will get us PMF in June