Should only auto(re)connect to peers we have a channel or some other business with

[delbonis]

Because right now we try to connect to every peer we've ever known about, including Lit-AF instances that aren't listening and don't exist anymore.

This would probably involve a lot of changing how we load/track channels, so maybe worry about this then.

[Varunram]

Maybe we could have some kind of activity bool, (only) on trigger of which we store the peer in the db.

[delbonis]

I was thinking have separate tables/collections/buckets/whatever for "peers we know about" and "peers we actively should connect to". And the former of which we can use to drive the DHT when we get around to that.