• mysql-like command line EDB interface
  • e2 synching w/ htmlcode and nodetypes (e2 <=> e2)
  • script to render a document structure to html pages (starting at default, and crawling it, saving each node as an html file)


  • embed nodes
  • Everything API
  • htmlcode list/descriptor
  • Create User Node


    Links are designed to provide a way to relate two nodes to each other. Links are created when users traverse from one node to another. However, not all links are "good" or wanted. We want to create a system where the less useful links die off.

    To do this, we will think of links as living organizms. Link get "food" by users searching or clicking on a link. Links use the food at some specified rate. If they run out of food, they starve to death and die.

    What this provides is a system where links live and die by how the users use the system. A kind of genetic algie. The links that live will, in general, be more useful as more users will use them. Less useful inks will evenually starve to death and go away. This way the system evolves to provide useful links as determined by the way the system is used.

    Link specifics


    Themes or "skins" allow users or system admins to set the look and feel of the site. The basic parameters that we could allow them to change are colors (bgcolor, text, etc) and perhaps even auto generate images.

    This could be a very powerful feature that would allow third parties to modify the site such that it resembles their site. This would allow them to link to our site while making the end user believe that they are still at their site. They get the exposure, we get the ad revenues.

    Also, this would allow us to change the look of a site instantly by modifying the theme of the site, which would be extremely useful when developing a new site. We may even want to allow users to specify a theme so they can make the site look how they want it to.

    User Notes

    User notes are kind of like alerts at etrade. Users can send notes to eachother. We could have an "note" nodelet that would tell the user when they have new notes. The user could then go to their user page and read the notes that they have, delete them, or even reply to them. We may want to implement notes as actual email. That would allow users to read their email from the site and send email to other sites, but that may be a little too much for right now. Just a thought...


  • Letting htmlcode operate as HTML as well as PERL
  • also, htmlcode should have a description
  • htmlcode groups?
  • Full nodetype functionality (restrict, extends, etc)
  • restrict dupes default ON
  • restrict searching on readable types