Say I want to build a ceramic data explorer(data indexer) for my app. I could access the live update of data throughout my application by subscribing to the relevant libp2p topics.
But what if my subscribing node goes down and recover? Is there a way for me to read historical messages before continuing to listening to the new updates? How does ceramic node itself handle down time and recovery? How to scale my node if the app got some traction?