Proxies are great, but the problem to solve there is the IP based banning, which can be only solved by paying for reading a small amount of money and delegation.
What I'm doing (rbr.bio) is a way to at least know where to read from: you can get the metadata or even just the write relays (just added now as JSON :) ).
It means that the clients just have to read from a few of the write relays to get the data.
Ah that’s clever, def going to experiment with rbr.bio later.
There’s so much potential for this kind of “indexing” service to greatly improve the nostr experience for casual non-technical users.
Are you working on putting it into @npub1wnwwcv0a8wx0m9stck34ajlwhzuua68ts8mw3kjvspn42dcfyjxs4n95l8is? Or what kind of experiment are you thinking about?
My top priorities are:
- Data freshness (right now data is about 1 hour old)
- Data availability (some of my followers seem to be missing, I don't know why)
- Latency (already have an EU server at eu.rbr.io, I did't set up load balancer yet)
- Example on how to use it / putting into RelayPool library for easier integration ito clients
#[4]
