PSYCED TO-DO

• LMTP
  • Differentiate LMTP dialog from [[[SMTP]]
  • Implement permissive policy
  • Add MIME handling
  • Interpret bulk mail headers
• Twitter client library
  • Relocatable API URLs
  • Design Twitter library
  • Implement common functions
  • Demonstrate OAuth
• Deployment
  • Sign people up for the psyced Trac
  • Create a self-service wiki signup to add users to Trac and other Wikis from psyced
• Testing
  • Maintain two test servers that employ the |-syntax
  • Deliver a lightweight language description for the spec
  • Create test scripts
• DAIDE
  • DAIDE - >DPP detokenizer
  • Room logic for Diplomacy
• AI
  • PSYC powered neural net.
  • Filter logic for neuron controls
  • Integration with explicit learning engine

LMTP

This is part of a strategy to deploy psyced behind a full mail server. The LMTP interface is used by the mail server, while the SMTP interface remains available for legacy apps.

Twitter

This is a portability and maintainability enhancement.

As other apps copy the Twitter API, psyced rooms can reuse the Twitter Library for those sites as well.

Also, Twitter has indicated plans to version its API. A few #defines and psyced can keep up with development churn.

Deployment

Looks like Trac needs to-be moved to MySQL to make use of the conversion script. After that, we have some fun integrating it with a local psyced.

DAIDE

The Diplomacy AI Development Environment is an important piece of infrastructure in my hobby. The plan here is to build a psyced interface for it so that psyced can handle yet another odd protocol.

AI

My AI application here is a massive document classifier that can identify new concepts in input and become self training. The role of psyced is that of a neural net. Federation allows unlimited interconnections with concepts hosted on and offsite. Programmable contexts provide a place to put filter logic.