Use user's relay list

[jb55]

We should fetch a users relay list if we don't have it. We can use our current hardcoded list as our bootstrap list.

Some open questions:

• What relay list should we use when we have multiple users?
• We could use a union of the lists for the alpha release
• Future releases may add them all as active connections, and simply subscribe to the correct ones based on context?

[ksedgwic]

On startup, we use the bootstrap relay list to try and fetch the users k:10002 record.

Do we block other progress while we wait? Or should we proceed w/ setting up the timelines w/ the bootstrap list while we wait?

[ksedgwic]

Another question: do we union in the k:3 relays with the k:1002? Are there other sources of relays I should be considering?

[alltheseas]

@ksedgwic has a proposal for a method

@jb55 to review soon :tm:

@ksedgwic advises just thumbs up is sufficient; complete review not needed. Hardening work remainaing, plenty to do with thumbs up.

[alltheseas]

@ksedgwic added:

-bootstrapping (if nothign else is working) -local relays will always be used. set added with advertised relays (solely from network) -forced relays - if see in command; doesnt update

[alltheseas]

@ksedgwic maybe there is a need for "fixed relays" down the road

[alltheseas]

@jb55 - overlapping relays sets - might make sense to have transiently maintained relays list. maintain relays, but dont reconenct all the time.

Multiple profiles may require use of different relays.

@ksedgwic - when adding subscription over available relays - "this subscription does not go over this relay".

Subscriptions need an additional argument - "what kind of subsription is this - read, write etc."

Easy to add