not gonna lie, this triggered me because actually the main reason i didn't publish the nostr client i've been playing with for the last 2 years is that i am still not satisfied about how DB hydration process worked the problem isn't specific to DMs, this is just an example scenario the scenario: lets say Bob is DM-ing Alice, in some DM down the conversation Bob sends "The Complete Epstien List: 1-some jew 2-some goy 3-....etc", then they continued DM-ing months later Alice wants to retrieve that list so Alice open its conversation with Bob and searches words "The Complete Epstien List:" The Problem -retrieving the whole conversation is super heavy/slow -imperatively handling this specific case to the best (maybe by batched retrievals or else) then updating the search result creates loads of imperative handling HELL everywhere we get in contact with our DB