Make peer connection retries less aggressive
- Retries degenerate into infinite loop (for 24 sek.) if SimplePeer throws error right after constructor is called
- Retries cause too much CPU/network usage in completely standard situations like some peer leaving
There needs to be some notion of: should I retry? Is it worth retrying?
Possible fix: Only do retries if general network interruption is detected. That should cover the main use cases for retries: recover from smartphone app freezing / walking out the door (wlan -> mobile) / train going through a tunnel