(note, times are CEST.)
Code:
--- SNIP ---
[21:11:36] * u4euc453wZ599zQ has quit (K-Lined)
[21:11:37] * u4mZRTtQwC6NskZ has quit (K-Lined)
[21:11:37] * x398030675 has quit (K-Lined)
[21:11:37] * u4m5AmvGVaM8MNU has quit (K-Lined)
[21:11:37] * x92119461 has quit (K-Lined)
[21:11:38] * u4iQ9mpGopGTd6D has quit (K-Lined)
[21:11:39] * u4iqow5D1WqBmPH has quit (K-Lined)
[21:11:39] * u4qsjyU6VRAtfRD has quit (K-Lined)
--- SNIP ---
[21:11:36] * u4euc453wZ599zQ has quit (K-Lined)
[21:11:37] * u4mZRTtQwC6NskZ has quit (K-Lined)
[21:11:37] * x398030675 has quit (K-Lined)
[21:11:37] * u4m5AmvGVaM8MNU has quit (K-Lined)
[21:11:37] * x92119461 has quit (K-Lined)
[21:11:38] * u4iQ9mpGopGTd6D has quit (K-Lined)
[21:11:39] * u4iqow5D1WqBmPH has quit (K-Lined)
[21:11:39] * u4qsjyU6VRAtfRD has quit (K-Lined)
--- SNIP ---
Anyhow, this leaves the bitcoin network unable to operate.
I see some clients getting back slowly.
But this worries me.
I suggest we apply what ever other bootstrapping mechanism we have right now, and release 0.3 ASAP.
Someone in #freenode suggested this:
Code:
<gwillen> Xunie: as a potential user of bitcoin, I would suggest that if your project is going to connect to IRC in the background, you should document that fact somewhere. I'm suddenly much more wary of using it now that I know that it does this.
This does make Bitcoin seem a bit... malicious to say the least...