A few things, however, it solves a problem I have now in Amethyst, which is that many notes are only "seen" by one or two relays (and without connecting to many more relays listed via NIP-65 for contacts).
Once complete, Amethyst connects to that private relay (and a few others) and it will stream and sync from many hundreds to thousands of relays. Much more than just a few as it is currently.
> a problem I have now in Amethyst, which is that many notes are only "seen" by one or two relays
This should not be a problem, it is how the Outbox model works. Any other additional relay comes from a broadcast from users that interact with the event and this organically increase the decentralization and reachability of user's content.
It seems that you want to create an hybrid client/really, that actually could be useful in edge cases to support "thin clients", especially on mobile.
Right, however in my case, I noticed the relay was either a paid relay that we happen to share (single point of failure) or a wot relay that uses someone elses pubkey (not including my contacts, even if I'm in theirs) and will probably only store notes temporarily.
Yes that is part of it. With many different clients; short notes, git collaboration, long notes, video, audio, markets (desktop or mobile) and etc. (desktop or mobile), it could get quite complex for each separately to do all the heavy lifting of communicating with thousands of relays, etc. etc.
