[VAN]

Interesting concept, but I'd like to add a little...err..a lot.

When posting a new hack, offer an option to the hack writer to have it "certified". This would basically be the in-depth inspection mentioned in the first post..but it wouldn't be free. If someone writes a hack and wishes for it to be "certified" as functional and secure, they can have it looked over by by a qualified person for a small fee...a couple bucks. This fee would go to the person who certifies the hack via Paypal. Perhaps smaller fees for super simple hacks.

The couple bucks is a small amount to pay to have a hack certified, but for someone who knows what they are doing, they could certify a few hacks a month and earn some spending money, or money to pay for their cable internet. Of course in order to be able to certify hacks, you would have to prove yourself a worthy coder.

So here's how I think it should work...

Member goes to post a new hack...
They choose whether or not to have it certified by a "professional".
If they choose yes, then the hack gets posted to an area only accessible to those members that have been designated to be able to certify new hacks, and an overview of the hack gets posted to a "waiting for cert" section viewable by all members. (this would prevent someone from attempting to code something that is already in the pipeline for release)

Those people that are able to certify hacks would have a section that lists all hacks currently requiring certification, and they can then choose which hack they want to work on. They would only be able to certify one hack at a time. The person who certifies a hack would also be responsible for providing support for that hack, since during the inspection process, they would know the code as well or better than the original writer. After the hack is certified, they are paid via Paypal and the hack gets posted with a "certified" icon. Payment not sent? Hack not posted. Simple.

If the hack writer chooses to not have his work certified, it gets posted immediately with an "as is" and "not certified" warning, and people can download and install it at their own risk, with support offered when possible.


This pay-for-certification system would benefit everyone. The hack writer would get piece of mind knowing that his hack is worthy of a "certified" icon, and can begin work on new projects while support for his certified hacks is provided by someone else.

The certifier benefits financially for his time and work.

The end user benefits by having the choice to only install certified hacks and gets piece of mind knowing that certifed hacks will always be supported.

Additionally, it would be great if anyone could pay to have a hack certified. For example...

Member XXX posts a really great hack, but for whatever reason chooses not to pay to have it certified. Member ZZZ loves the hack concept, but is nervous about installing a non-certified hack, so member ZZZ can "sponsor" the certification process by paying for it himself.

Just my thoughts. I for one would have no problem in paying a small amount for the piece of mind in knowing that what i'm about to install wont cause security issues or conflicts.