Active Entries
- 1: Advent, day 5
- 2: Today's programming silliness
- 3: The highly inaccurate guide to the Eurovision Song Contest 2022 results!
- 4: Bang!
- 5: How not to get people to use a new feature
- 6: Misty creek and eerie fog
- 7: Remember...
- 8: Brexit means arrows?
- 9: boggyb's highly inaccurate guide to Eurovision: Shine a Light 2
- 10: Brighton again
Style Credit
- Style: Neutral Good for Practicality by
Expand Cut Tags
No cut tags
no subject
Date: 2006-01-22 01:37 am (UTC)(oh, and the attacks are on the game servers, not the listservers).
What appears to have happened is a complete breakdown in communication (communication between the listserver admins and the community, and communication among the listserver admins). Currently, B is taking the stance that C is not co-operating and so he may be 'forced' to de-peer with C (which would cause all sorts of fun problems, given the mixture of listserver settings in use). I would probably be happy with a continued ban, as long as there was actual communication about it (and it was suitably justified).
I'll ignore the uselessless of an IP ban against getting server lists when there exist multiple independent web interfaces (along with official ways to embed said interface into a php script or similar), and where the attack involves UDP.