Yes, this is how we do this at Primal.
Not sure if this approach will be more widespread. I sure hope so, which is why we open sourced our caching service.
I assume primal.net is doing it using their backend caching layer which aggregates data from all known public relays and offers a more wide view of the numbers and the possibility to notify when something changes. I wonder what this caching strategy means more generally for nostr as the protocol. And if it will be widespread used by other clients. nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr
Discussion
No replies yet.