Why would I want codex's programs when I could make my own?
You don't need Neocodex programs then if you can make your own.

QUOTE
Codex's activity is nothing compared to what it was a year or so ago. In the past codex was an active and helpful community, but now the older members are dicks to the newer ones, so the new ones leave.
Well, if we dismiss the spiky curves in my google analytics window telling me that activity is actually
higher this year

, helpfulness in general may have went down. Right now it seems everyone is concentrating on school so it may not seem very active right now. I can't really comment on the helpfulness since I haven't been around much lately though.
QUOTE
When codex becomes a decent community again, I will release my programs here.
Perhaps I can help explain our policy to you, and the reasoning behind it all:
Every program submitted here requires that the Neocodex checks be installed on the programs. I'm sure you've heard that from many people already. The reasons for this are:
- It allows staff to have proper inventory of all programs being hosted. Everytime a program connects to Neocodex to authorize, usage statistics are recorded and are used by programming staff to determine usage trends in our programs. When I was staff, I very much liked using this information to determine which programs needed the most attention (based on use), and the total usage counter was useful in seeing how many users were running our programs at any given time. It doesn't get any more invasive than that though.
- Back in a day when there used to be many submissions, not every program could be determined to meet the site's standards right at approval time (though I don't think this happens very much anymore) If ever the program needed to be disabled by either the programmer or the staff at the site, it could be done very fast, and without having to remove the program completely from the downloads section. For example: if someone (perhaps not from here and who doesn't like us or something) wanted to be really bad, they could submit a program that didn't show it's evil effects right away. In a few weeks time, the program starts doing some bad things and the staff need to stop everyone else from using the program. Holding everyone (even "non-outsiders") to this standard just ensures that things are consistent and not that anyone is being doubted. Another example: After a few months, a program goes fubar because Neopets changes something in their code and the program can no longer emulate being a person. To save a bunch of people getting frozen from any ill-effects of a program, the program can be disabled everywhere it is being used.
- Contrary to the policy of other sites, Neocodex allows the programmer to retain all intellectual property rights to their programs, on the condition that the copy here follows our standards. What you submit here does not become the property of Neocodex. To give you a real life example, 3volutionize had a clause in their rules (not sure if it's still there though), saying that all submitted content becomes the property of 3volutionize. There is no such thing here, and you can release your program wherever you want. If say you choose to submit your program to three competing sites of ours, so be it. The copy you post here must have the checks, but we are indifferent towards whatever you do at other sites.
- It shows that you can put a bit of effort to brand your program with the Neocodex name, and if it ever gets leaked, all it does is promote the site and not pose a danger.
If you don't agree with any one of these points, then submitting programs here is unfortunately not for you.

So basically, the checks gives you the ability to ban users, only allow some, view usage logs, pass dynamic information into your program from the server (ex. making version updates pop up, or updating GetStringBetween criteria remotely). It gives the staff the ability to have an accessible inventory of programs hosted on the site, and more control in times when programs may get leaked to areas where they should not be, or if the program is eventually deemed unsafe.