There's no almighty attitude.. It's just that anybody who has been seriously programming for some time and who read other peoples' article can write a PHP security article of his own... And he/she does not have to be necessarily qualified by a higher standing proffessional..

And I am not saying that I know everything - I am saying that I can write what I know about...

Aha! A support (ticket) system for hacks, pehaps? ;)

That would mean individual support.
But by keeping it public, everybody could see the responses and maybe have his questions/problems covered too.

Why make it complicated?

DV, do you know what a HiJack log is? A BHO? Do you know what this line of code means: 40D41A8B-D79B-43d7-99A7-9EE0F344C385 or how to find out whether it's good or bad? Can you do a regedit? Or what this is: hpB4EA.tmp? I do. Liz

I am going to close this thread as well before it gets out of hand.

While we appreciate your concerns Dark Visor, continually beating a dead horse is not going to get you your way. Like or not, that is for you to decide.

This site has its own internal level of standards, comraderie and set ways in things are done. Making suggestions is one thing but making demands are going to fall on deaf ears.

Every person who releases a hack, add-on, plugin or extension can have it elevated to a premium status. Here the label is on the modification, not the author. They have both premium and non-premium add-ons. It isn't about labeling community members but giving the community additional resources where needed. If you were truly set on improving the community, you would see that. If you have further arguments, then take them up with me in private. Any further "response threads" on these topics and you will lose your forum privileges here permanently.