{"type":"rich","version":"1.0","author_name":"semisol (npub122…cgrkj)","author_url":"https://nostr.ae/npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj","provider_name":"njump","provider_url":"https://nostr.ae","html":"Have both. They solve their own use cases. \n\nWhen you want to search the world’s largest library that’s the tradeoff you are making.\n\nBut once you find it, or get a book from a friend for example, you put it in your indexedDB database and congrats.\n\nI personally envision the hierarchy ad follows\n- Indexers, that have almost everything. They are the Google of Nostr. People push their events here and others find them.\n- Large relays, which serve large communities. Think Nostr.land, Damus, etc. These are hubs for retrieving content in bulk.\n- Community relays. These can be self-hosted or hosted in the cloud. People push from here to large relays and from large relays to here, what they care about.\n- Local cache. This is the user’s own space and that is it.\n\nThe ideal relays would be:\n- indexer: custom software\n- large relays: strfry on medium end, NFDB and possible other options at large end\n- community relays: could be a mix of strfry, NFDB, realy, nostrdb-based\n- local relays: nostrdb, indexedDB-based"}