Deploying DeadLetter Learn DeadCL DeadCL Tutorials Trusted Domains Publishers

Walk throughs

Author Keys Conversations Libraries Arrays

Network Status Community Hub Contact Us



Inputs & Outputs


DeadLetter was designed to be an engine to both existing and new applications, as a result deadCL is engineered to use plain text files located on your domain for input(s).

Here you'll find all the information relevant to understand DeadLetter's I/O.


Basic - Inputs

All inputs are defined within Conversations. DeadLetter is only capable of receiving information in plain text files, without encoding or foreign syntax.

Input sources should employ Secure Sockets Layer although this is not a prerequisite.

All inputs must use the syntax *input,

Your input source must be accessible without, obstruction.


            

*input, @INPUT-ADDRESS


Advanced - Inputs

DeadLetter, requires your inputs to be publicly accessible, for some this raises a security risk, for this reason it is possible to add a further layer of abstraction.

All inputs must use the syntax *input,

To disguise your input we'll use your do-ID along with an authorised name. @do-ID+{input_name}

"input_name" must be defined within your AK.


            

*input, @do-ID+{input_name}





Basic - Output

Output address(es) should only ever be defined within your Author Key. This improves redundancy, simplifies sharing and administration.

Output should be defined using the syntax ?DRP -- [email protected]+Cnvrstn$

This instructs DeadLetter to use the address;

https://post.deadletter.io/Do-ID+CONVERSATION_URL

for it's output(s) providing a unique address for each Conversation automatically upon publication of each Conversation named within the Author Key.


            

?DRP -- [email protected]+Cnvrstn$