With this synced, what can you do with it?
Your own backend to serve results quicker and more reliably than querying the relays?
Discussion
That's the idea, yes. It's got a very basic API for fetching common data and getting aggregated stats (like follower count, etc). It's part of the stack that nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg runs on.
TBH, I'm not sure what I will use it for but I wanted to get it up and running and explore it.
This is good, as it’s important to improve user experience.
I was thinking, we could make a shared/common instance like this.
Where a few developers can build it together to build endpoints.
One example of an endpoint could be, given an event ID, to fetch a conversation for a note, where it will fetch from the root note down to every replies, and attach all user information, every zap amount, reaction count.
nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr Do you have npubs for some of the primal team? Sounds like there's so interest in potentially contributing to the API on top of the caching service.