WordPress MU

I know that banning IPs isn't the best solution in the world but it does stop a % so here's my list of IPs to ban from your WPMU site:

217.160.171.20
81.181.209.3
68.190.197.172
70.162.85.46
70.132.133.30
83.19.66.122
66.176.187.129
69.232.186.155
69.109.160.202
213.164.102.68
209.112.221.17
59.93.56.73
24.182.244.131
68.87.71.183
68.157.43.60
68.18.52.131
195.8.175.8
62.253.32.8
203.200.97.181
207.177.195.196
24.205.161.39
192.153.163.63
192.153.163.63
205.250.8.172
125.23.0.253
220.186.0.0
202.47.247.117
202.47.0.0
59.40.198.47
220.186.26.58

Happy splog blocking!

Hey!
What's the purpose for banning these IPs?

i may also add those:
217.160.171
65.35.112.144
24.16.124.143
61.3.200.32
210.211.255.19

ps. samchung, usually banning is the fastest thing to do when one day you wake up and see 400 new blogs created overnite which is nothing but bots created blogs. uhmm btw, now that I am thinking about it, isn't there a way to use image verification with wpmu registration?

Yeah, image registration would be perfect! :)

Okay, on the topic of image verification, I have looked into this before. It would be very easy to implement, but you'd have to end up modifying the newblog.php file everytime you update MU. The reason being that the action hook for newblog.php comes after the submit button. You'd have to manually move it up. Other then that a simple MU plugin can be made. If people don't mind this, i'll try throwing something together soon.

Thanks fimion! It would be a great plugin nonetheless.

Here's mine. Any line missing the last group is a Class c that's hit me more than a couple of times from different IPs within that block.

Note: I like keeping mine in order so I can find them quickly. Other may want to follow up on that idea. :)

deny from 24.62.47.148
deny from 58.169.92.229
deny from 58.169.93.111
deny from 58.169.101.123
deny from 58.169.128.147
deny from 58.169.129.4
deny from 58.169.140.20
deny from 66.97.174.196
deny from 66.207.210.226
deny from 69.0.96.103
deny from 69.0.97.144
deny from 69.0.99.89
deny from 69.37.24.
deny from 69.37.25.
deny from 69.37.45.99
deny from 69.37.120.75
deny from 69.37.231.131
deny from 71.196.7.135
deny from 80.57.62.146
deny from 80.178.150.85
deny from 85.31.186.61
deny from 88.1.150.47
deny from 143.238.237.102
deny from 150.101.105.107
deny from 150.101.106.
deny from 150.101.110.
deny from 150.101.111.
deny from 195.225.176.84
deny from 212.37.39.59
deny from 213.93.153.233

Wondering if anyone got image verification working in MU yet?

I couldn't use it as I have too many clients who have vision issues.

And how woudl it stop manually created spam blogs? We've had exactly one but would like to prevent any we could.

They created a blog, waited a few days, then posted a half a dozen posts within a short time. I monitor the site all the time, and caught it right away.

Andrea, most splogs are created by scripts. If they had to read a series of characters within a graphic image, they would hopefully be stopped.

What about an activation triggered system? On my system I'd like to acknowledge all new blogs before they become active. Maybe this could be a multi-pass step.

1. image verification -> email to use
2. email verification -> create request to admin
3. site admin activates blog

Gwagen, easiest method would be to use the invite method. Have new users email you requesting them and then you send them the invite. That way you approve the signup as well as verify the email address.