January 15, 2004:  Site Master Concept complete.  I have come up with a suitable logo-ish banner for the Engine and a template to contain the Engine.  This can be viewed at http://www.phoenixpo.com/ce/template.aspx.  Any comments or suggestions (anyone online is welcome) can be emailed to Kaine (at) PhoenixPo.com.  I will begin to incorporate this template into the Engine on the 16th or 17th--after I break it apart into little pieces for include files.

January 12, 2004:  Encoder work stable.  The encoder alpha version is finished and it's stable and working fairly well with most, if not all, codesets.  I will continue adding codesets and the database work for user account code storage.  I will try to allow people to retrieve their codes for display on their personal sites via JavaScript.  If you update them here, you update them on your site.  That's the idea, at least.

December 18, 2003:  Encoder work begins.  No updates will be posted until January 7th.  I will begin work on an alpha version of the encoder and hope to have a beta up for a period of "steady state" around the 7th.  Watch here to see if I make it.

December 13, 2003:  Finalized the web service.  It is now where we want it and will not change for a long while.

Dates here may be older than the update.

What is it?

The Codic Engine decodes any code set, like the Geek Code, from a single web interface.  "Code Sets" (aka "codesets") are lists of questions and answers possible for a person filling making a code.  Codes can be made to help give introductions to people when on web sites, list services, or bulletin boards. 

Every codeset is made up of some questions (usually 12-30) and a list of possible answers for each question.  Every question has a unique letter or character associated with it, as well as every answer under that question.  For instance, the code set may ask, "What state are you from?" with the letter "St" standing for the question.  One person's answer may be "North Carolina," so he writes "StNC" in his code.

A complete code might look something like: GIT(CS) d- s: a+ P[vg,sx,ms] c+>++(+) !z-- StNC.  The Engine is capable of decoding codes like this, provided the codeset is entered into it. 

Some codesets make me wonder what people do with their free time.  However, it is my official stance to say PhoenixPo.com and I do not officially support or condone the contents of or beliefs expressed within the codesets themselves.  Our purpose is simply to add them to the Engine, unless we feel very strongly a codeset not be entered.

What are Code Sets good for?

Using code sets, and making codes, groups can identify themselves at the end of an email post (supposedly to a list service) or on a bulletin board.  This way, those familiar with the code set know a bit about the person without an introduction or such given in each post.  This facilitates group interaction and helps people find a others with similar interests (and really helps those just joining the list/board to get acquainted with those already on it).

The problem with Code Sets now:

Some code sets are complicated and it is difficult for anyone but those intimately familiar with the 2code set to translate codes made by it.  This problem actually makes code sets, which were supposed to benefit the group, a hindrance to newbies or novices with the set.  Add to this the time it takes to decode the code by hand against a code set, and you have an impractical system.

How Far Are We?

Decoder looks great; I am 95% finished with the programming--enough for a working version.  I have to add a little more than 21 code sets, some which I have listed on this site.  During and only during that time will the other 5% be added to the Engine.

The encoder is in alpha and seems to work pretty well.  I'll roll it to beta once I'm fairly confident.

The Engine is tested in another location--the Kaine/MAGE Server Project @ UNCG.  What you see here is the working version.  If you go to the Codic Engine.Net link, you will see the stats on the main page.  My example code sets are also listed on the page.  If you want to see the code set information, there is a link for that. 

All available code sets and the percent complete are shown on the Engine's page.  If it's above 90% complete, the Engine has the code set, but I will only put 100% when I am extremely confident--97~99% is about as high as it usually gets because I cannot possibly test for every single possible input.

Who is Doing the Project?

Christopher, the owner of PhoenixPo.com Web & Design, has pieced together this project from concept idea, through programming, and to its implementation.  For more information about how this project is coming together, please visit the How This Is Done page.

The testing grounds for the Engine is the Kaine/MAGE Server Project @ UNCG.  I own this server, so it is perfect for trial runs and such.  "Kaine" is my other alias, of which I will make known starting with this project.  "PhoenixPo" was my previous one, so when I refer to either handle, it's just me.

Objectives of the Codic Engine.Net:     (objectives discussion)

Outlook:

A very ambitious plan.  The Codic Engine will take a while to develop.  It currently resides on our development server at the Kaine/MAGE Server Project.  A copy of it is frequently uploaded to www.phoenixpo.com/ce.  Please refer to it there.

How can I help?

Contact me at Kaine (a) PhoenixPo.com.  I can always use people who will show me where new code sets are.  If they are familiar with programming, I may give them an example class for them to learn how to add code sets to the Engine.  Believe me; it's VERY easy to add code sets, but if the metadata is not documented correctly, that would screw the Engine up.