The following is a draft of the specification required to understand what ‘F3D’ will be as implemented

‘F3D’ is a temporary name, and may be changed with minimal notice until declared otherwise

ยง1 Definitions

’namespace’ in this document to be interpreted as a isolated network in which users may treat each instance as its own environment

‘DNS’ in this document is to be interpreted as ‘Domain Name System", a system which will in this case be a custom implementation focusing on the location of servers without knowledge of their physical location

‘hostname’ in this document is to be interpreted a URI meant to easily direct users within a custom DNS system

‘website’ in this document is to be interpreted as any web browser compatible server offering web services such as, but not limited to, nor required to be:

‘ddrp’ in this document is to be interpreted as the standard behind F3D hostname based websites, which will be the basis

NOTICE this draft is provided as is to display the following

As the author of this protocol I have found most current backing sig protocols, which I was planning on relying on, to be either bad today, or with the possibility of insecurity in the future, as this project is intended to be future proof, I’m going to pull a PGP and start researching and building my own pubkey algorithm, this will be independant and rely on fundamentals as I find them in my local spaces to avoid contamination from outside sources, this means the protocol will take longer than expected to even be fully drafted, but hopefully it will come with the peace of mind that this protocol will not need band-aid fixes within any forseable future…

Blessed be the code, for its short nature reign supreme over he who increment thy failures