Planned PIE Updates

PIE (Pixel to Image Encoding) Planned Updates, Additions and Research

Planned

• Client Request : Coding : XML Based Configuration
  Build the configuration for encoding and decoding using xml.
• Client Request : Coding : JSON Based Configuration
  Build the configuration for encoding and decoding using JSON. As no dependencies are allowed, this is a challenge but will build a simple JSON Parser.
• Client Request : Optional Additional Pin Code
  Along with the encryption an optional pin code will be added for command line and Coding. Can also be used if encryption is not used. Just incase the certificate falls into the wrong hands.

Research

• Optional MAC Address
  When the certificate is created, the mac address of the device is located and stored inside the certificate and added to the encoded files encryption system. Therefore, if the encoded files are compromised any attempt to decode on any other device will fail. More Research is needed for this project.
• Allow Unidentified Byte Array As Encode Source
  The idea is to allow the user encoding to use a byte array with no identified file or type. This will then be detected at decode time and the same byte array will be output for the user to use with in their own software.
• Allow More Encoding Sources
  The idea is to allow the user encoding to use inputstreams like urls and integrations. This will then be detected at decode time and the same streams will be output for the user to use with in their own software. Will also be optionally identifiable.
• Allow More Encoding Modes
  There are currently 2 encoding modes. Semi-Transparent, Fully Transparent. Requests have been made for more options. Including single colour, boundary and hidden within image.