Expand on this thought a bit. It seems like what you are saying is that the trick to speeding up the page load time is for the client to put everything in a SQL database and then just dynamically keep...
A client using SQL is just caching data locally to make its own experience faster. That doesn’t help anyone else. Other clients aren’t reading from that database. They still go straight to relays to fetch data. So SQL doesn’t speed up the network or Nostr itself, it just means that one client doesn’t have to refetch everything every time.
On the WebSocket side, relays can't return unlimited data. If a client asks for too much in a single request, the relay will simply cap the response and not send everything. So WebSocket requests are kinds limited and they just stream whatever the relay is willing to send. If you want more data, you have to break your requests into smaller chunks.
On the WebSocket side, relays can't return unlimited data. If a client asks for too much in a single request, the relay will simply cap the response and not send everything. So WebSocket requests are kinds limited and they just stream whatever the relay is willing to send. If you want more data, you have to break your requests into smaller chunks.