In reply to Rushtin.

That's pretty close to what happened. Except Scott targeted Plugin Organizer in earlier versions by reindexing the $_POST array incorrectly. Which wasn't malicious but still created a bug. I asked him to fix it and he refused. So I released a version of Plugin Organizer that grabbed the $_POST array early on before his plugin re-indexed the it and I could get the data that had been posted in the correct format.

He responded by releasing a version of his plugin that specifically targeted Plugin Organizer and deleted the files from it as well as changed the options. So I released a version that deactivated his plugin in the MU component of Plugin Organizer to prevent him from doing that. In response he released a version that introduced an MU plugin file of his own named so that it would load before mine that contained the code to delete Plugin Organizer and change the database options.

That is when the Wordpress admins got involved. They asked both of us to remove the code that targeted the others plugin. Which I was happy to do since all I wanted in the first place is for his plugin to stop targeting and breaking mine. I removed the lines of code that deactivated his plugin. He removed the lines of code that deleted mine. But he left in the code that changed the database options. I notified the admins after waiting two weeks for him to remove that code. That's when they removed WP Spamshield. They had also been waiting for him to do something about it apparently and just got sick of it all.

He won't give up on this crusade he has embarked on. He will release his plugin from a different source eventually. But he will never admit his role in WP Spamshield being removed from the repository. That would be damaging to his ego. Before you run the new version of WP Spamshield you should take a look at the code to see what other things it is doing without your knowledge. I'm sure you'll be surprised what you find. I was.