Just recently I noticed a significant number of ignored peers. They all appear to be Vuse 5.3 clients. Just curious if this is just me or are others seeing the same?

You're not alone, I've been noticing it this week too. The Vuze clients in question were 5.3.0.1_B06 and 5.3.0.0 .

I have seen this today with a couple of clients with this peerid: -AZ5300- . This is from peer's log:

[20:04:14]  going online
[20:04:16]  initiating connection
[20:04:16]  securing connection
[20:04:19]  sending handshake
[20:04:20]  logged in OK
[20:04:20]  sent bitfield
[20:04:21]  Stopped: Invalid incoming message size
[20:04:21]  going offline

same here its always vuse 5.3

I suppose it is not a surprise it is recent as Vuze release date was early Feb for this version. I posted in their forum to see if they noticed anything. Obviously a fault in their program.

I see the same message size problem first, but that does not get them "ignored". They will, it appears connect on the second try and send data. Most often they get ignored within the first couple hundred Kb but some I have noticed get a couple M sent before being ignored.

Strangely they can be seeded to for the most part. That said some might be ignoring us as I have seen a few without the RI lit after I have sent them some data.
Thanks for letting me know I am not alone and do not have to start readjusting my setup.

I also got this message logged on connection with Vuze 5.3.0:

Stopped: Bad protocol id in handshake

Last thing I have noticed about this problem. On the first attempt to connect and the wrong message size error, this is an encryption error. Then the connection goes again but unencrypted and a connection is made. If you keep the incoming speed to less than 20 you will likely get a few packets. I got up to 10 M from 1 peer before they went bad data. That said this does not appear anything like the bad data ignored from super fast seeders.

Speaking of that is there any work around discovered for that or is it just a find and manually limit seed?