AtomicFifteen.com

Emanuel William Fludd

Linux/Android/Windows Server/FreeBSD/OSX Software Programmer
MySQL/PostgreSQL Database Architect and Manager
Audio/Video Producer/Director
Marketing and Graphic Design
Internet/WWW/Open Source Design and Programming
Software, Robotics, Artificial Intelligence, Networking, Design

RFC FM001: TELEDYN PROTOCOL

Decentralized Dynamic IP-Address Resolve/Lookup System for the World to share HyperText Universal Resource Locators

Concept:
Where the rise of Social Networks; the key function of which can be abridged into a simple link-sharing paradigm. With massive investments in centralized service providers and political leanings of such organizations taking a toll on their respective user-bases it has become increasingly apparent for a need to move away from centralized architecture. This is just a natural reflex of innovation itself and in no way acts as a method to compete with said services.

If we take away what we have learned from the Social Networking experiment it is simply that Link Sharing is the true innovation of these services. With the concept of HashTags, HyperText URL Sharing, et. all. taking the lead as the crux of these services. Aside from their insatiable Network Effect building their communities the fact remains they do not OWN those users or communities. These Social Network web-sites are simply borrowing their member's relationships and rendering as commodity.

The time has come to actually derrive useful modes of exchange in a decentralized way to swing the power back into the hands of the true technology companies providing access to Internet Services and out of these walled off gardens called Social Networks. This RFC Paper serves as a starting point for this discussion.

To Submit Changes:
Also to request compiled binaries for your hardware platform of choice...
Please contact Col. Emanuel William Fludd
Phone: 1 (202) 888 - 1173 [USA]

TeleDyn Protocol Version 3

Protocol: TCP/IP Socket
Port: 7770
Encoding: UTF-8

Notes:
Each command instantiated must be appended with a semi-colon (;) and Return Character (\n). Individual command delimiter is the Pipe Symbol (|).

Commands are signified with single ASCII characters:
* - Ping
@ - Login
~ - Get Messages
# - Send Message
$ - Register New Account

Login Proceeding:
@User|Pass;

During login please note you must supply either a Clear-Text, MD5, or BCrypt Hash (Auto-detected). Depending upon the client you use all are compatible. User-names are limited to 11 characters. Passwords are limited to 33 characters.

Registration Procedure:
$User|Pass;

During registration the password will be fed back to the socket connection in the form of a hashed string for storage on the client. Further access to the system will require this password be in the form of either Plain-Text, MD5, or BCrypt. All of which are automatically detected by the system.

Messaging Procedure:
#To|Message;

Messages are stored on the device until retrieved by the receiving party.

Message Retreival Procedure:
~

Messages are displayed in bulk delimited by Return Characters (\n) headed in the following format:

FROM:NAME
MESG:MESSAGE BODY
[Return Character]

To Maintain an Active Session:
Please Ping (*) every 60 seconds or your connection will be timed-out.