Systems, methods and media for a distributed social media network and system of record

Provided herein are exemplary distributed architectures including a platform system communicatively coupled to a network, a social media system communicatively coupled to the network and configured for interaction by one or more users, and a social media application communicatively coupled to the network and configured for interaction by one or more users. Further exemplary embodiments include a third party service communicatively coupled to the network, a public auditor communicatively coupled to the network, and a public archivist communicatively coupled to the network. The one or more users may include any of individuals, businesses, charities and non-profit organizations, and government organizations.

FIELD OF THE TECHNOLOGY

The present technology relates generally to distributed social media networks and systems of records.

SUMMARY OF THE PRESENT TECHNOLOGY

Provided herein are exemplary distributed architectures including a platform system communicatively coupled to a network, a social media system communicatively coupled to the network and configured for interaction by one or more users, and a social media application communicatively coupled to the network and configured for interaction by one or more users.

Further exemplary embodiments include a third party service communicatively coupled to the network, a public auditor communicatively coupled to the network, and a public archivist communicatively coupled to the network. The one or more users may include any of individuals, businesses, charities and non-profit organizations, and government organizations.

The social media system, in certain exemplary embodiments, may be communicatively coupled to system modules, the system modules communicatively coupled to platform modules and core modules, the platform modules and the core modules communicatively coupled to each other and to platform services, the platform services communicatively coupled to a social media system API, the social media system API communicatively coupled to the network, and the network communicatively coupled to the platform systems, the social media application, the third party service, the public auditor and the public archivist.

The distributed architecture may also include the platform system communicatively coupled to platform system modules, the platform system modules, communicatively coupled to system modules, platform modules, and core modules, the system modules, the platform modules and the core modules communicatively coupled to each other and to platform services, the platform services communicatively coupled to platform system APIs, the platform system APIs communicatively coupled to the network and the network communicatively coupled to the social media system, the social media application, the public archivist, the public auditor, and the third party service.

The distributed architecture, in further exemplary embodiments, may further comprise the social media application communicatively coupled to app modules, the app modules communicatively coupled to an App module client proxy and core modules, the core modules communicatively coupled to the App module client proxy, both the App module client proxy and core modules communicatively coupled to the network, and the network communicatively coupled to social media system APIs, platform system APIs, the public archivist, the public auditor, and the third party service.

Provided herein are also exemplary chronicle records including a record header, further comprising Id, version, timestamp, previous record hash, record nonce, record hash, record header graph and record signature, graphs, all of which descend from a base graph, the base graph further comprising base graph schema, base graph hash, base graph signature, base graph estimated work, base graph actual work, a graph collection further comprising a node and an edge, a hash algorithm further comprising a Merkle tree, object graph hash algorithm and a graph schema hash algorithm.

Exemplary chronicle records may further include a chronicle header further comprising Id, timestamp, chronicle nonce, chronicle header graph, version, previous chronicle hash, chronicle hash, chronicle header graph hash, a chain of chronicle records each comprising a chronicle record with a previous record hash and record hash linked to one or more other chronicle records, each chronicle record comprising a set of data for a specific predetermined period of time, one or more record hashes being associated with a previous record hash via a directional acyclic graph, one or more chronicle header graphs and one or more chronicle graph hashes providing traceability and visibility into what happened to data on its way to becoming immutable, the chronicle header being associated with a chronicle hash that is derived from different data being hashed, further comprising a chronicle being a construct that is highly scalable and allows for parallelism across a platform, with all chronicles being worked on simultaneously.

Also provided herein are a plurality of chronicles aggregated into annals, the annals further comprising an annals header including Id, timestamp, annals nonce, annals header graph, version, previous annals hash, annals hash, annals header graph hash, a chain of chronicles each comprising a previous chronicle hash and chronicle hash linked to one or more other chronicles, the annals comprising a set of data for a predetermined period of time, and further comprising one or more chronicle hashes being associated with a previous chronicle hash via a directional acyclic graph.

Further exemplary embodiments include a chronicle collection including a chronicle and annals, the chronicle including a plurality of chronicle records and the annals including a plurality of chronicles, platform system modules communicatively coupled to the chronicle collection, the platform system modules including chronicle platform system modules, a chronicle aggregation platform system module, a chronicle archive platform system module, a chronicle audit platform system module, chronicle management module, and platform systems including a chronicle system and system modules including chronicle system modules communicatively coupled to the platform system modules.

Exemplary methods for making a post on a distributed social media network include a user maintaining ownership and control of content and associated metadata, the user posting a message and content stored on their own social media system, the user using a social media app to compose a post, including using a message board app module to create to create a post, the user using a connection app module to designate who the user is going to share the post with, before sending the post, the user using a signing core module to digitally sign the post, transmitting the post by a posting app module that sends the post to their own social media system via a network, ensuring by a compliance system module that the post conforms to a platform's compliance standards and rules, storing the post inside of the user's chronicle, using a system module to create a URI to data in the user's chronicle, encrypting and passing the user's chronicle to a distribution system module, so the post can be distributed to its designated recipients via the network, one or more users accessing the post on their respective social media apps aided by a message board app module, and the user optionally deleting the post at any time while maintaining control of the post and associated metadata in an external data center.

Also provided herein are exemplary methods for publishing on a distributed social media network, including a user selecting a publisher on a network, the user using a social media app to publish, the user using a message board app module to compose publishable content, the user signing the publishable content using a signing core module, the user paying any fees associated with publishing via a payment app module, the user sending via a publishing app module the publishable content to their own social media system via a network, processing the publishable content with a compliance system module, storing the publishable content as a new chronicle record, sending the new chronicle record to a publisher across the network to a publisher's social media system, upon receipt of payment via payment modules, notifying a workflow system module of pending content item being published for the user, upon the sending of the new chronicle record, either the entire chronicle record with all its bits, including every bit of content is transmitted, or an optimization is sent with URIs to content bits, determining whether the new chronicle record has content and if it does not, obtaining the content via a URI, upon receiving the content and verifying it by a workflow system module, verifying the content meets the publisher's compliance rules, accepting, rejecting or flagging by the workflow system module for next steps of workflow, applying data transformations to a content graph, including copyright, subject headings, subdivisions, classification or catalog, upon completing processing of the content, the new chronicle record is submitted to chronicle system modules, including a chronicle workflow system module for consensus by a consensus algorithm, upon completing the consensus, the new chronicle record is either accepted or rejected, if the new chronicle record is accepted, saving it to a chronicle system module, if the new chronicle record is rejected, sending a rejection notice to the user, upon saving the new chronicle record, sending the new chronicle record to a publishing system module for a final check, sending the new chronicle record to a distribution module and placing it in a distribution event grid module, and distributing the new chronicle record over a network with the distribution event module.

INTRODUCTION

Social media today is highly centralized, controlled by a few huge companies whose primary objective is profit. Their heavy dependence on algorithms and big data to appease shareholder demands as well as their size and market dominance have led to some serious negative consequences. Users have lost privacy and control because they are the product. A small number of biased gatekeepers now decide which ideas and opinions are seen and shared. And bad actors are weaponizing these networks at scale.

Furthermore, users on existing platforms create almost all the content without compensation, while the social media companies capture all the economic value from that content through advertising sales. The news business especially is suffering—not because people don't want news, but because the money generated by online news audiences flows mostly to companies like Facebook, instead of publishers who are at a huge technological disadvantage.

Various embodiments of the present technology utilize a distributed architecture to return social media, including news and content distribution, to the original idea of the internet: a very decentralized and egalitarian system that levels the playing field and balances profit with social good. Furthermore, the platform is highly scalable with multi-dimensional parallelism and inherent sharding.

Users can post content to their connections. Posted content can be deleted at any time because users maintain total ownership and control. This type of sharing is private. Users can also publish content to a permanent public record. Published content can be edited, corrected, retracted or recanted, but never deleted. It is vetted by publishers, audited by auditors, and held in the public trust by archivists outside of the network. This type of sharing is public.

Various embodiments of the present technology also utilize a unique system of record which leverages the foundational technologies of hashes, Merkle trees and blockchain to bring integrity and civility back to social media networking. There are no bots or fake accounts because every user is known and verified. There is no censorship or shadow banning because the distributed network is user directed and filtered. There is no fake news or shit posting because the distributed network maintains a traceable, immutable, permanent public record of all published workflows and content using blockchain. There is no fraud because the distributed network facilitates and verifies all transactions for data integrity and message authenticity using hashing functions and consensus.

The surface area of any potential attack by bad actors is greatly diminished with the distributed architecture. Profit for few becomes profit for many as publishers and content creators are paid for their content, advertising dollars are distributed across a wide range of media properties, and no one intermediary controls the user or the data. Privacy and control are restored as all users are now the authority over their own data as well as what is seen, shared, and monetized on their own social media network.

DETAILED DESCRIPTION

FIG. 1is a block diagram of Distributed Architecture100whereby User104integrates with Social Media System106, Social Media App(s)110and Platform Systems102via Network(s)108. What makes this architecture unique is that User104has their own Social Media System106and their own Social Media App(s)110. In one embodiment of the invention where User104is a business, User104might have many Social Media App(s)110pointing to their own Social Media System106. In another embodiment of the invention where User104is an individual, User104might have an iOS application as their Social Media App(s)110and their own Social Media System106.

By comparison, all existing social media platforms have centralized architectures. (See reference article, “On Distributed Communications Networks” by Paul Baran, published September1962, for illustration of differences between centralized and distributed networks.) Users of centralized social media networks such as Facebook or Twitter are essentially interacting with a single, monolithic social media system for that specific business. Data is being transferred to and from centralized data centers that users do not own or control. These central authorities use algorithms and big data to determine what is seen and shared based on what will generate them the most profit.

With Distributed Architecture100, User104has total authority over their own data as well as what is seen, shared and monetized on their own social media network. Furthermore, the platform is highly scalable, with multi-dimensional parallelism and inherent sharding, as well as a significantly reduced surface area for attacks.

FIG. 2is a block diagram of Platform Systems102which is comprised of API System200, Archive System202, Audit System204, Chronicle System206, Directory System208, Identity System210, Ledger System212, Onboarding System214, Payment System216, Platform Management System218, Search System220, Third Party Systems222, Account System224, Telemetry System226, User Verification System228, Connection System230, Consensus System232, SDK System234, AI System236, Analytics System238, Machine Learning System240, Trending System244, Endorsement System246, Ad System248, Content Verification System250, Index System252. All of these sub-systems affect the entire platform and are cross-cutting in their impact on both Social Media System106and Social Media App(s)110introduced inFIG. 1.

API System200manages APIs for the platform. Archive System202manages archiving for the platform. Audit System204manages auditing for the platform. Chronicle System206manages chronicles for the platform. Directory System208manages the directory for the platform. Identity System210manages identity for the platform. Ledger System212manages ledgers for the platform. Onboarding System214manages onboarding for the platform. Payment System216manages payments for the platform. Platform Management System218is the main system that manages and integrates with all other platform systems on the platform. It composes, deploys, configures, updates, and decommissions Social Media System106and Social Media App(s)110inFIG. 1which are both dynamically created to deliver a unique set of features and functionality for User104based on user type and requirements.

Search System220manages search for the platform. Third Party Systems222manages third parties for the platform. Account System224manages accounts for the platform. Telemetry System226manages telemetry for the platform. User Verification System228manages user verification for the platform. Connection System230manages connections for the platform. Consensus System232manages consensus for the platform. SDK System234manages software development kits for the platform. AI System236manages AI for the platform. Analytics System238manages analytics for the platform. Machine Learning System240manages machine learning for the platform. Trending System244manages trending for the platform. Endorsement System246manages endorsements for the platform. Ad System248manages ads for the platform. Content Verification System250manages content verification for the platform. Index System252manages indexing for the platform.

FIG. 3is a block diagram of Distributed Social Media Network300which further illustrates that every User104has their own social media system and their own social media app in Distributed Architecture100detailed inFIG. 1. User104-1has Social Media System106-1and Social Media App(s)110-1. User104-2has Social Media System106-2and Social Media App(s)110-2. User104-N has Social Media System106-N and Social Media App(s)110-N. The ellipse between Social Media System106-2and Social Media System106-N illustrates that there are N number of social media systems for every user on the network. The ellipse between Social Media App(s)110-2and Social Media App(s)110-N illustrates that there are N number of social media app(s) for every user on the network. Platform Systems102services all social media systems and all social media apps across Network(s)108. All of the sub-systems available in Platform Systems102are available to all social media systems and all social media apps across Network(s)108. Third Party Services112represents third party services available to Platform Systems102as well as all social media systems and all social media apps across Network(s)108. Public Auditors114provide auditing services for the platform and interact with Platform Systems102as well as all social media systems and all social media apps across Network(s)108. Public Archivists116provides archiving services in the public domain outside of the platform and interact with Platform Systems102as well as all social media systems and all social media apps across Network(s)108.

FIG. 4is a use case diagram that illustrates individuals and entities as they relate to users of Distributed Social Media Network300inFIG. 3. It further defines User104inFIG. 1and utilizes the classification system of the United States Internal Revenue Service. In another embodiment of the invention, other classification systems could be used to define User104. Here User104is comprised of Individuals402which may be users of Distributed Social Media Network300inFIG. 3, and in the case of the IRS classification, are defined as U.S. citizens or residents. Individuals402may also have associations with Businesses404, Charities & Non-Profits412, and Government424. Businesses404may be users of Distributed Social Media Network300inFIG. 3and include Self Employed406, Small Businesses410, and Corporations408. Charities & Non-Profits412may be users of Distributed Social Media Network300inFIG. 3and are comprised of Charitable Organizations414, Churches & Religious Organizations416, Political Organizations418, Private Foundations420, and Other Non-Profits422. Government424may be users of Distributed Social Media Network300inFIG. 3and are comprised of Federal426, State428, Local430, and Indian Tribal432.

In one embodiment of the invention, user accounts will be created by Distributed Social Media Network300inFIG. 3for elected and appointed government positions at all levels of Government424, specifically Federal426, State428, Local430, and Indian Tribal432. Access will be given to each elected or appointed Individual402, or their designated appointees, for official government use during their term or appointment. These user accounts are not owned by Individual402and are in no way associated to their personal user account. In another embodiment of the invention, user accounts are created for elected and appointed government positions byFIG. 1, Platform Systems102. In another embodiment of the invention, user accounts are created for elected and appointed government positions byFIG. 1, Social Media System106.

FIG. 5is a block diagram of Platform Services500which is comprised of IaaS and PaaS502. Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) are used to describe basic cloud computing constructs that include cloud platforms such as Microsoft Azure or AWS Cloud Services. The entire platform is built on top of these foundational services which sit on servers interconnected on networks and all the individual servers comprised of operating systems, memory, and CPU. IaaS and PaaS502is comprised of Networking504, Compute518, Management530, Storage542, Security558, and Integration566. Networking504consists of DNS506, Firewall508, Virtual Network510, Load Balancer512, Content Delivery Network514, and VPN516. Compute518consists of Virtual Machines520, API Servers522, Containers524, Functions526, and Jobs528. Management530consists of Monitoring531, Telemetry532, Diagnosis534, Backup536, Analytics538, AI539, and Machine Learning540. Storage542consists of Blob544, Disk546, Queue548, Table550, SQL Database552, Document Database554, and Cache556. Security558consists of Directory Services560, Two-Factor Authentication562, and Key Vault564. Integration566consists of Service Bus568, Event Hubs570, Catalog572, Notification574, Third Party APIs576, and API Management578.

FIG. 6is a block diagram of Platform Modules600which is comprised of Compute Module602, Integration Module604, Management Module606, Networking Module608, Security Module610, and Storage Module612. Each of these modules represents the high-level cross-cutting programming and configuration needed to manage all of the corresponding services of Platform Services500inFIG. 5. Compute Module602represents all of the programming and configuration needed to manage Compute518inFIG. 5. Integration Module604represents all the programming and configuration needed to manage Integration566inFIG. 5. Management Module606represents all the programming and configuration needed to manage Management530inFIG. 5. Networking Module608represents all the programming and configuration needed to manage Networking504inFIG. 5. Security Module610represents all the programming and configuration needed to manage Security558inFIG. 5. Storage Module612represents all the programming and configuration need to manage Storage542inFIG. 5.

FIG. 7is a block diagram of Core Modules700which is comprised of Exception Handling Core Module702, Extensions Core Module704, Cryptography Core Module706, Identity Core Module708, Logging Core Module710, Merkle Tree Core Module712, Telemetry Core Module714, Utilities Core Module716, Validation Core Module718, Consensus Core Module720, and Signing Core Module722. Core Modules700interacts with Platform Systems102and Platform Modules600.

Core Modules700provides all the cross-cutting functionality for Platform Systems102and Platform Modules600, including but not limited to exception handling, cryptography, identity, logging, telemetry, validation, consensus, and signing. Every Social Media System106and every Social Media App(s)110on Distributed Social Media Network300inFIG. 3requires these cross-cutting features in terms of application logic, configuration and storage. This low-level code also manages all of the Platform Services500inFIG. 5, specifically Networking504, Compute518, Management530, Storage542, Security558and Integration566.

Exception Handling Core Module702captures exception handling and works with the other modules in Platform Modules600to ensure exceptions are logged and put into a process to be mitigated. Extensions Core Module704represents extensions to core functionality so that there is reuse across the systems and applications. Cryptography Core Module706represents cryptography programming, ciphers, and hashing algorithms that are leveraged by both the systems and applications. Identity Core Module708manages core identity functions that are used by both the systems and applications. Logging Core Module710provides the ability to log debug, error and critical information in the system and application layers. Merkle Tree Core Module712enables the ability to work with Merkle trees across the systems and applications. Telemetry Core Module714collects telemetry data in both the system and application layers. Utilities Core Module716provides utility functionality, programming, and configurations that can be used across both the systems and applications. Validation Core Module718provides validation functionality and configurations that can be applied in the system and application layers. Consensus Core Module720manages consensus across the systems and applications. Signing Core Module722manages signing in the system and application layers.

FIG. 8is a block diagram of System Modules800which is comprised of Ad System Modules802, AI System Modules804, Analytics System Modules806, Archive System Modules808, Audit System Modules810, Chronicle System Modules812, Connection System Modules814, Content System Modules816, Directory System Modules818, Distribution System Modules820, Identity System Modules822, Ledger System Modules824, Licensing System Modules826, Machine Learning System Modules828, Message Board System Modules830, Onboarding System Modules832, Payment System Modules834, Posting System Modules836, Publishing System Modules838, Search System Modules840, Subscription System Modules842, Third Party System Modules844, Wallet System Modules846, Endorsement System Modules848, Compliance System Modules850, Consensus System Modules852, Notary System Modules854, Certified Email System Modules856, Workflow System Modules858, SDK System Modules860, Copyright System Modules862, Rhetoric System Modules864, User Verification System Modules866, Trending System Modules868, Account System Modules870, Content Verification System Modules872, and Index System Modules874. System Modules800interacts with Core Modules700which provides all the cross-cutting functionality for System Modules800.

Each of these system modules represents the high-level cross-cutting programming and configuration needed to manage all of the corresponding services of Social Media System106inFIG. 1. Social Media System106-1to106-N on Distributed Social Media Network300inFIG. 3is comprised of one or more or all of these system modules depending on user type and requirements. While generally intended for the system layer, these system modules could also be used by Platform Systems102inFIG. 1across the entire platform or by Social Media App(s)110inFIG. 1in the application layer. These system modules can work alone or be combined. They are combined by either compilation or as separate systems by networks or by sitting in the same operating system and communicating via API or SDK.

Ad System Modules802provides the system modules for managing the advertising features and functionality of the platform. AI System Modules804provides the system modules for managing the AI features and functionality of the platform. Analytics System Modules806provides the system modules for managing the analytics features and functionality of the platform. Archive System Modules808provides the system modules for managing the archiving features and functionality of the platform. Audit System Modules810provides the system modules for managing the auditing features and functionality of the system. Chronicle System Modules812provides the system modules for managing the chronicle features and functionality of the platform. Connection System Modules814provides the system modules for managing the connection features and functionality of the platform. Content System Modules816provides the system modules for managing the content features and functionality of the platform. Directory System Modules818provides the system modules for managing the directory features and functionality of the platform. Distribution System Modules820provides the system modules for managing the distribution of posted and published content across Distributed Social Media Network300inFIG. 3. Identity System Modules822provides the system modules for managing the identity features and functionality of the platform. Ledger System Modules824provides the system modules for managing the ledger features and functionality of the platform. Licensing System Modules826provides the system modules for managing the licensing features and functionality of the platform. Machine Learning System Modules828provides the system modules for managing the machine learning features and functionality of the platform. Message Board System Modules830provides the system modules for managing the message board features and functionality of the platform. Onboarding System Modules832provides the system modules for managing the onboarding features and functionality of the platform. Payment System Modules834provides the system modules for managing the payment features and functionality of the platform. Posting System Modules836provides the system modules for managing the posting features and functionality of the platform.

Publishing System Modules838provides the system modules for managing the publishing features and functionality of the platform. Search System Modules840provides the system modules for managing the search features and functionality of the platform. Subscription System Modules842provides the system modules for managing the subscription features and functionality of the platform. Third Party System Modules844provides the system modules for managing the third-party features and functionality of the platform. Wallet System Modules846provides the system modules for managing the wallet features and functionality of the platform. Endorsement System Modules848provides the system modules for managing the endorsement features and functionality of the platform. Compliance System Modules850provides the system modules for managing the compliance features and functionality of the platform. Consensus System Modules852provides the system modules for managing the consensus features and functionality of the platform. Notary System Modules854provides the system modules for managing the notary features and functionality of the platform. Certified Email System Modules856provides the system modules for managing the certified email features and functionality of the platform. Workflow System Modules858provides the system modules for managing the workflow features and functionality of the platform. SDK System Modules860provides the system modules for managing software development kits to build additional features and functionality on the platform. Copyright System Modules862provides the system modules for managing the copyright features and functionality of the platform. Rhetoric System Modules864provides the system modules for managing the rhetoric features and functionality of the platform. User Verification System Modules865provides the system modules for managing the user verification features and functionality of the platform. Trending System Modules868provides the system modules for managing the trending features and functionality of the platform. Account System Modules870provides the system modules for managing the accounting features and functionality of the platform. Content Verification System Modules872provides the system modules for managing the content verification features and functionality of the platform. Index System Modules874provides the system modules for managing the index features and functionality of the platform.

FIG. 9is a block diagram of Social Media System Layers900which is comprised of Social Media System106which is integrated with System Modules800. System Modules800is integrated with Platform Modules600, Core Modules700, and Platform Services500. Platform Modules600is integrated with Core Modules700and Platform Services500. Core Modules700is integrated with Platform Modules600and Platform Services500. Platform Services500is integrated with Network(s)108via Social Media System APIs902, which are the sum composite of all the application programming interfaces that are exposed by Social Media System106. Social Media Systems106interfaces with Platform Systems102, Social Media App(s)110, Third Party Services112, Public Auditors114, and Public Archivists116across Network(s)108. This diagram illustrates the constituent foundational layering of Social Media System106that is derived vis-a-vis System Modules800in their relationship with Platform Modules600, Core Modules700, and Platform Services500and as well as the interaction across Network(s)108with Platform Systems102, Social Media App(s)110, Third Party Services112, Public Auditors,114and Public Archivists116. In short, one sees the N-tiered architecture from the point of view of System Modules800inFIG. 8.

FIG. 10is a block diagram which illustrates one possible Social Media System106for User104inFIG. 1who is Business404inFIG. 4. It is comprised of System Modules800which consists of Chronicle System Modules812, Posting System Modules836, Publishing System Modules838, Subscription System Modules842, Distribution System Modules820, Ad System Modules802, Content System Modules816, Connection System Modules814, Payment System Modules834, Licensing System Modules826, Analytics System Modules806, and Onboarding System Modules832. This collection of twelve system modules is a subset of the total possible system modules dynamically created and delivered by Platform Management System218inFIG. 2based on user type and requirements. System Modules800interfaces with Platform Modules600, Core Modules700and Platform Services500. Platform Modules600interfaces with Core Modules700and Platform Services500. Core Modules700interfaces with Platform Modules600and Platform Services500. Social Media System APIs1002represents all the application programming interfaces for interfacing with System Modules800, Platform Modules600, Core Modules700and any of the specific system modules. All of these comprise the sum total application programming interfaces for this specific version of Social Media System106. Platform Services500is integrated with Network(s)108via Social Media System APIs1002.

FIG. 11is a block diagram which illustrates another possible Social Media System106for a User104inFIG. 1who is Individual402inFIG. 4. It is comprised of System Modules800which consists of Chronicle System Modules812, Posting System Modules836, Subscription System Modules842, Distribution System Modules820, Content System Modules816, Connection System Modules814, Wallet System Modules846, Licensing System Modules826, Analytics System Modules806, and AI System Modules804. This collection of ten system modules is a subset of the total possible system modules dynamically created and delivered by Platform Management System218inFIG. 2based on user type and requirements. System Modules800interfaces with Platform Modules600, Core Modules700and Platform Services500. Platform Modules600interfaces with Core Modules700and Platform Services500. Core Modules700interfaces with Platform Modules600and Platform Services500. Social Media System APIs1102represents all the application programming interfaces for interfacing with System Modules800, Platform Modules600, Core Modules700and any of the specific system modules. All of these comprise the sum total application programming interfaces for this specific version of Social Media System106. Platform Services500is integrated with Network(s)108via Social Media System APIs1102.

FIG. 12is a block diagram of App Module1200which is comprised of View1202, View Model1204and Model1206. View1202is the UI and also comprised of Smart Contract View Elements and Logic1224. View1202interfaces with View Model1204which is also comprised of Smart Contract Presentation Logic1222. View1202and View Model1204interact via Notifications1210, DataBinding1216, and Commands1218. View Model1204integrates with Model1206by Notifications1208, Read1212, and Update1214. Model1206is also comprised of Smart Contract Business Logic1220. Client Proxy1226represents the application's integration into Network(s)108. This diagram introduces the concept of an app module, which is designed to be an application whether an iOS or Android app downloaded from an app store or a thick client for Mac OS, Linux or Windows. It represents user interfaces that provide a certain set of features and functionality for users and exemplifies a typical MVVM (Model, View, View Model) software development pattern for UI design.

FIG. 13is a block diagram of App Modules1300which is comprised of Ad App Module1302, AI App Module1304, Analytics App Module1306, Archive App Module1308, Audit App Module1310, Chronicle App Module1312, Connection App Module1314, Content App Module1316, Directory App Module1318, Distribution App Module1320, Identity App Module1322, Ledger App Module1324, Licensing App Module1326, Machine Learning App Module1328, Message Board App Module1330, Onboarding App Module1332, Payment App Module1334, Posting App Module1336, Publishing App Module1338, Search App Module1340, Subscription App Module1342, Third Party App Modules1344, Wallet App Module1346, Endorsement App Module1348, Compliance App Module1350, Consensus App Module1352, Notary App Module1354, Certified Email Module1356, Workflow App Module1358, SDK App Module1360, Copyright App Module1362, Rhetoric App Module1364, User Verification App Module1366, Trending App Module1368, Account App Module1370, and Content Verification App Module1372, and Index App Module1374. App Modules1300interacts with Core Modules700which provides all the cross-cutting functionality for App Modules1300.

Each of these app modules represents the high-level cross-cutting programming and configuration needed to manage all of the corresponding services of Social Media App(s)110inFIG. 1. Social Media App(s)110-1to110-N on Distributed Social Media Network300inFIG. 3are comprised of one or more or all of these app modules depending on user type and requirements. While generally intended for the application layer, these app modules could also be used by Platform Systems102inFIG. 1across the entire platform or by Social Media System106inFIG. 1in the system layer. These app modules can work alone or be combined. They also represent the programming and configuration necessary to integrate with Social Media System106and Platform Systems102inFIG. 1on the application side.

Ad App Module1302manages the advertising features and functionality of the app(s). AI App Module1304manages the AI features and functionality of the app(s). Analytics App Module1306manages the analytics features and functionality of the app(s). Archive App Module1308manages the archive features and functionality of the app(s). Audit App Module1310manages the audit features and functionality of the app(s). Chronicle App Module1312manages the chronicle features and functionality of the app(s). Connection App Module1314manages the connection features and functionality of the app(s). Content App Module1316manages the content features and functionality of the app(s). Directory App Module1318manages the directory features and functionality of the app(s). Distribution App Module1320manages the distribution features and functionality of the app(s). Identity App Module1322manages the identity features and functionality of the app(s). Ledger App Module1324manages the ledger features and functionality of the app(s). Licensing App Module1326manages the licensing features and functionality of the app(s). Machine Learning App Module1328manages the machine learning features and functionality of the app(s). Message Board App Module1330manages the message board features and functionality of the app(s). Onboarding App Module1332manages the onboarding features and functionality of the app(s). Payment App Module1334manages the payment features and functionality of the app(s). Posting App Module1336manages the posting features and functionality of the app(s).

Publishing App Module1338manages the publishing features and functionality of the app(s). Search App Module1340manages the search features and functionality of the app(s). Subscription App Module1342manages the subscription features and functionality of the app(s). Third Party App Modules1344manages the third-party features and functionality of the app(s). Wallet App Module1346manages the wallet features and functionality of the app(s). Endorsement App Module1348manages the endorsement features and functionality of the app(s). Compliance App Module1350manages the compliance features and functionality of the app(s). Consensus App Module1352manages the consensus features and functionality of the app(s). Notary App Module1354manages the notary features and functionality of the app(s). Certified Email App Module1356manages the certified email features and functionality of the app(s). Workflow App Module1358manages the workflow features and functionality of the app(s). SDK App Module1360manages the software development kit features and functionality of the app(s). Copyright App Module1362manages the copyright features and functionality of the app(s). Rhetoric App Module1364manages the rhetoric features and functionality of the app(s). User Verification App Module1366manages the user verification features and functionality of the app(s). Trending App Module1368manages the trending features and functionality of the app(s). Account App Module1370manages the accounting features and functionality of the app(s). Content Verification App Module1372manages the content verification features and functionality of the app(s). Index App Modules1374manages the index features and functionality of the app(s).

FIG. 14is a block diagram which illustrates one possible Social Media App(s)110for User104inFIG. 1who is Business404inFIG. 4. In this embodiment of the invention, Social Media App(s)110utilizes Runtime1400such as the Java virtual machine (JVM) or .Net Framework Common Language Runtime (CLR). Runtime1400is comprised of App Module Manager1402which has App Module Factory1404which can create N number of app modules (one, more, or all) represented in this case by App Module1406-1, App Module1406-2, and App Module1406-N. App Module Manager1402via App Module Factory1404can create and run one or more or all of App Modules1300dynamically. Runtime1400is also comprised of App Module View1408, App Module Controller1410, and App Module Model1412(an MVC pattern) as well as the cross-cutting Core Modules700. App Module Client Proxy1414interfaces with Network(s)108which in turn integrates with Social Media System APIs1002introduced inFIG. 10.

FIG. 15is a block diagram which illustrates another possible Social Media App(s)110for User104inFIG. 1who is Individual402inFIG. 4using an iOS app or Android app. In this embodiment of the invention, Social Media App(s)110includes Operating System1500which is the basis for all these app modules that get compiled and distributed through an app store. Operating System1500is comprised of Message Board App Module1330, Chronicle App Module1312, Posting App Module1336, Publishing App Module1338, Subscription App Module1342, Distribution App Module1320, Content App Module1316, Connection App Module1314, Wallet App Module1346, Licensing App Module1326, and Analytics App Module1306, Core Modules700and App Module Client Proxy1414. App Module Client Proxy1414interfaces with Network(s)108and enables the cross-cutting Core Modules700to get to Social Media System APIs1102introduced inFIG. 11.

FIG. 16is a block diagram of Platform System Modules1600, which is comprised of API Platform System Modules1602, Archive Platform System Modules1604, Audit Platform System Modules1606, Chronicle Platform System Modules1608, Directory Platform System Modules1610, Identity Platform System Modules1612, Ledger Platform System Modules1614, Onboarding Platform System Modules1616, Payment Platform System Modules1618, Platform Management System Modules1620, Search Platform System Modules1622, Third Party Platform System Modules1624, Account Platform System Modules1626, Telemetry Platform System Modules1628, User Verification Platform System Modules1630, Connection Platform System Modules1632, Consensus Platform System Modules1634, SDK Platform System Modules1636, AI Platform System Modules1638, Analytics Platform System Modules1640, Machine Learning Platform System Modules1642, Trending Platform System Modules1644, Endorsement Platform System Modules1646, Ad Platform System Modules1648, Content Verification Platform System Modules1650, Index Platform System Modules1652, and Content Platform System Modules1654. Platform System Modules1600interfaces with Core Modules700which provides all the cross-cutting functionality for Platform System Modules1600.

Each of these platform system modules represents the high-level cross-cutting programming and configuration needed to manage all of the corresponding services of Platform System102inFIG. 1. They can work alone or be combined. They are combined by either compilation or as separate systems by networks or by sitting in the same operating system and communicating via API or SDK. Many of these platform system modules are platform specific implementations of System Modules800inFIG. 8, thereby adding platform specific functionality for the platform as opposed to system modules that provide functionality scoped specifically for Social Media System106inFIG. 1. These platform system modules are designed primarily for the server side, however could also be used to extend the functionality of App Modules1300inFIG. 13on the client side as part of an N-tiered architecture.

API Platform System Modules1602manages API features and functionality across the entire platform. Archive Platform System Modules1604manages archive features and functionality across the entire platform. Audit Platform System Modules1606manages audit features and functionality across the entire platform. Chronicle Platform System Modules1608manages chronicle features and functionality across the entire platform. Directory Platform System Modules1610manage directory features and functionality across the entire platform. Identity Platform System Modules1612manage identity features and functionality across the entire platform. Ledger Platform System Modules1614manage ledger features and functionality across the entire platform. Onboarding Platform System Modules1616manages onboarding features and functionality across the entire platform. Payment Platform System Modules1618manages payment features and functionality across the entire platform. Platform Management System Modules1620represents the main set of system modules that manages and integrates with all other platform system modules on the platform. Search Platform System Modules1622manages search features and functionality across the entire platform. Third Party Platform System Modules1624manages third-party features and functionality across the entire platform. Account Platform System Modules1626manages account features and functionality across the entire platform.

Telemetry Platform System Modules1628manages telemetry features and functionality across the entire platform. User Verification Platform System Modules1630manages user verification features and functionality across the entire platform. Connection Platform System Modules1632manages connection features and functionality across the entire platform. Consensus Platform System Modules1634manages consensus features and functionality across the entire platform. SDK Platform System Modules1636manages the software development kits used to provide any additional features and functionality across the entire platform. AI Platform System Modules1638manages AI features and functionality across the entire platform. Analytics Platform System Modules1640manages analytics features and functionality across the entire platform. Machine Learning Platform System Modules1642manages machine learning features and functionality across the entire platform. Trending System Modules1644manages trending features and functionality across the entire platform. Endorsement Platform System Modules1646manages endorsement features and functionality across the entire platform. Ad Platform System Modules1648manages ad features and functionality across the entire platform. Content Verification Platform System Modules1650manages content verification features and functionality across the entire platform. Index Platform System Modules1652manages index features and functionality across the entire platform. Content Platform System Modules1654manages content features and functionality across the entire platform.

Note that third parties who offer Software as a Service (SaaS) could provide functionality across the entire platform via Third Party Platform System Modules1624, or just on Social Media System106inFIG. 1via Third Party System Modules844inFIG. 8, or just on Social Media App(s)110inFIG. 1via Third Party App Modules1344inFIG. 13. The same can be said for software development kits (SDKs) which could be used to extend platform functionality via SDK Platform System Modules1636, system functionality via SDK System Modules860inFIG. 8, or application functionality via SDK App Module1360inFIG. 13.

FIG. 17is a block diagram of Platform System Layers1700which is comprised of Platform Systems102which is integrated with Platform System Modules1600. Platform System Modules1600is integrated with System Modules800, Platform Modules600, Core Modules700, and Platform Services500. System Modules800is integrated with Platform Services500. Platform Modules600is integrated with Core Modules700and Platform Services500. Core Modules700is integrated with Platform Modules600and Platform Services500. Platform Services500is integrated with the Network(s)108via Platform System APIs1702, which are the sum composite of all the application programming interfaces that are exposed by the Platform Systems102. Platform Systems102interfaces with Social Media Systems106, Social Media App(s)110, Public Archivists116, Public Auditors114, and Third Party Services112across Network(s)108. This diagram illustrates the constituent foundational layering of Platform Systems102that is derived vis-a-vis Platform System Modules1600in their relationship with System Modules800, Platform Modules600, Core Modules700, and Platform Services500and as well as the interaction across Network(s)108with Social Media System106, Social Media App(s)110, Public Archivists116, Public Auditors114, and Third Party Services112. In short, one sees the N-tiered architecture from the point of view of Platform System Modules1600inFIG. 16.

FIG. 18is a block diagram of Social Media App Layers1800which is comprised of Social Media App(s)110which is integrated with App Modules1300. App Modules1300is integrated with App Module Client Proxy1414and Core Modules700. App Modules Client Proxy1414is integrated with Core Modules700and Network(s)108. Core Modules is integrated with App Module Client Proxy1414and Network(s)108. Social Media App(s)110interfaces with Social Media System APIs902, Platform System APIs1702, Public Archivists116, Public Auditors114, and Third Party Services112across Network(s)108. This diagram illustrates the constituent foundational layering of Social Media App(s)110that is derived vis-a-vis App Modules1300in their relationship with App Module Client Proxy1414and Core Modules700as well as the interaction across Network(s)108with Social Media System APIs902, Platform System APIs1702, Public Archivists116, Public Auditors114, and Third Party Services112. In short, this diagram illustrates the N-tiered architecture from the point of view of App Modules1300inFIG. 13.

FIG. 19is a block diagram of Platform Management System Modules1900which is comprised of System Management Module1902, App Management Module1904, Lifecycle System Modules1906, Alert System Module1916, Performance System Module1918, Job Scheduling System Module1920, Monitoring System Module1922, Reporting System Module1924, Inventory System Module1926, and Security System Module1928. Lifecycle System Modules1906consists of Deployment System Module1908, Configuration System Module1910, Update System Module1912, and Decommission System Module1914. Platform Management System Modules1900interacts with Core Modules700which provides all the cross-cutting functionality for Platform Management System Modules1900. This diagram illustrates the functionality required for managing all Platform System Modules1600inFIG. 16, all System Modules800inFIG. 8, and all App Modules1300inFIG. 13. Platform Management System Modules1900provides the cross-cutting services, such as alerts, performance, job scheduling, monitoring, security and lifecycle management, that one would expect in any complex N-tiered architecture across all layers. This functionality is critical given that the platform will ultimately support a multitude of users, systems, and apps across Distributed Social Media Network300inFIG. 3.

FIG. 20is a block diagram of Chronicle Record2000which is comprised of Record Header2002. Record Headers2002consists of Id2004, Version2006, Timestamp2008, Previous Record Hash2010, Record Nonce2012, Record Hash2014, Record Header Graph2016, and Record Signature2018. Chronicle Record2000is further comprised of a number of additional graphs, all of which descend from Base Graph2050. Base Graph2050consists of Base Graph Schema2052, Base Graph Schema Version2054, Base Graph Hash2056, Base Graph Signature2058, Base Graph Estimated Work2060, and Base Graph Actual Work2062as well as Graph Collection2070which consists of Node(s)2072and Edge(s)2074.

Source Graph2020, Contracts Graph2022, Content Graph2024, Workflow Graph2026, Index Graph2028, State Graph2030, Audit Graph2032, Directory Graph2034, Conference Graph2036, and Other Graph2038all inherit the properties and graph collection of Base Graph2050.

Source Graph2020documents any individuals or entities associated with Chronicle Record2000. Contracts Graph2022contains smart contracts data associated with Chronicle Record2000. Content Graph2024contains the content for Chronicle Record2000as well as individuals, entities or other data associated with the content. Workflow Graph2026contains the workflow data associated with Chronicle Record2000. Index Graph2028contains data used for indexing Chronicle Record2000. State Graph2030contains state information about Chronicle Record2000. Audit Graph2032contains data pertaining to auditing Chronicle Record2000. Directory Graph2034contains directory data associated with Chronicle Record2000. Conference Graph2036contains conference data associated with Chronicle Record2000. Other Graph2038contains any other data associated with Chronicle Record2000.

These graphs may contain programming logic in addition to the data. In one embodiment of the invention, the data and programming logic is encrypted. In another embodiment of the invention, the data and programming logic is not encrypted. These graphs may be used in conjunction with one another and by other workflows outside of Chronicle Record2000. In one embodiment of the invention, Record Signature2018and Base Graph Signature2058are required. In another embodiment of the invention, these signatures are not required for Record Header2002and Base Graph2050. Also note that Node(s)2072and Edge(s)2074can be a part of multiple schemas.

Hash Algorithms2080are used to determine hashes for Chronicle Record2000as well as Previous Record Hash2010, Record Hash2014, and Base Graph Hash2056for each graph included in the record. Merkle Tree2082is used for Previous Record Hash2010and Record Hash2014. The data included in the Merkle tree includes all the base graph hashes and is used in combination with the header fields to determine the Merkle root. Base Graph Hash2056for all graphs in Chronicle Record2000uses either Object Graph Hash Algorithm2084or Graph Schema Hash Algorithm2086. Object Graph Hash Algorithm2084dynamically analyzes nodes and edges in the object data base, sorts them alphanumerically, and generates a schema which is then used to calculate a root hash. Graph Schema Hash Algorithm2086uses the predetermined Base Graph Schema2052for each graph to determine the hashes.

In sum, Chronicle Record2000is a unique collection of data and programming which provides complete traceability and visibility into what's in the record, how it came to be, every individual or entity that touches it, and every change that is made to it.

FIG. 21is a block diagram of Chronicle2100which is comprised of Chronicle Header2102as well as chains of chronicles records. Chronicle Header2102consists of Id2104, Version2106, Timestamp2108, Previous Chronicle Hash2110, Chronicle Nonce2112, Chronicle Hash2114, Chronicle Header Graph2116, and Chronicle Header Graph Hash2118. Chronicle Header2102is analogous to a blockchain header, but different because it contains Chronicle Header Graph2116and Chronicle Header Graph Hash2118which provides complete traceability and visibility into what happened to the data (and how it came to be) on its way to becoming immutable. The other distinguishing aspect of Chronicle Header2101is that Chronicle Hash2114is derived from different data being hashed.

The chaining of chronicle records in Chronicle2100is represented by Chronicle Record2120-1with Previous Record Hash2122and Record Hash2124linked to Chronicle Record2120-2with Previous Record Hash2126and Record Hash2128linked to Chronicle Record2120-N with Previous Record Hash2130and Record Hash2132. This chain is analogous to a blockchain, but different in two ways. First, it comprises a set of data for a specific 24-hour time period. It is not a never-ending chain of blocks. Second, each block contains exactly one Chronicle Record2000fromFIG. 20. It is not a block of multiple transactions.

Each Chronicle Record2000is also chained via a directional acyclic graph. The chaining of Chronicle Record2160with Previous Record Hash2162and Record Hash2164, Chronicle Record2166with Previous Record Hash2168and Record Hash2170, and Chronicle Record2172with Previous Record Hash2174and Record Hash2176is designed specifically with state changes in mind. This directional acyclic graph chain enables Chronicle2100to record state changes of chronicle records and provide quick access to a complete history of all changes to a Chronicle Record2000inFIG. 20.

Chronicle2100as a construct is highly scalable and allows for parallelism across the platform. Every Social Media System106inFIG. 1has its own Chronicle2100, and all chronicles are being worked on simultaneously. Every 24 hours, the platform is designed to generate a new genesis block and start a new Chronicle2100for that day. Every Social Media System106does the same thing with its primary Chronicle2100. Social Media System106may or may not have a Chronicle2100for every other Social Media System106. Social Media System106and Platform System102inFIG. 1may choose to aggregate chronicles. Chronicles are made available to Public Auditors114, Public Archivists116and Third Parties112within Distributed Social Media Network300inFIG. 3.

This construct also greatly reduces the surface area for attacks. If something bad happens to Social Media System106inFIG. 1, such as a catastrophic event, hack, or denial of service attack, it does not impact the whole system or all chronicles. Additionally, there is inherent sharding in this approach, solving the problem of large scale data across a really complex ecosystem and its ability to be quickly saved, retrieved and updated. With a multitude of separate chronicles, created every 24 hours, one only needs a point in time and source to get to a much smaller data set very quickly. Sharding also alleviates the problem of hotspots. If there is a lot of activity on a centralized social media network (e.g. something is trending), it creates a hot spot in the monolithic social media system which consumes lots of resources and requires triage. Various embodiments of the present technology address hot spots because data is massively distributed with multiple chronicles stored across Distributed Social Media Network300inFIG. 3. If something starts trending for a specific Social Media System106inFIG. 1, the social media system is already set up for handling increased demand at any moment because 1) it is geo-redundant, 2) Platform Management System218inFIG. 2will auto-scale to meet demand, and 3) much of the Chronicle2100associated with that social media system can actually be cached for the day.

In sum, Chronicle2100is a system of record that stores chronicle records in chronological order with specific details. In one embodiment of the invention, Chronicle2100stores data or URIs as part of its system. In another embodiment of the invention, Chronicle2100stores data in traditional data storage like SQL, NoSQL, files, object databases, document databases, etc. By using the foundational technologies of hashes, Merkle trees and blockchain, whether it is straight chaining or done inside of a directional acyclic graph, Chronicle2100brings integrity back to social media networking with full, complete, and accurate data and information sharing that is highly scalable, searchable, and secure.

FIG. 22is a block diagram of Annals2200which is comprised of Annals Header2202as well as chains of chronicles. Annals Headers2202consists of Id2204, Version2206, Timestamp2208, Previous Annals Hash2210, Annals Nonce2212, Annals Hash2214, Annals Header Graph2216, and Annals Header Graph Hash2218.

The chaining of chronicles in Annals2200into a blockchain is represented by Chronicle2220-1with Previous Chronicle Hash2222and Chronicle Hash2224linked to Chronicle2220-2with Previous Chronicle Hash2226and Chronicle Hash2228linked to Chronicle2220-N with Previous Chronicle Hash2230and Chronicle Hash2232. Additionally, Annals2200includes the chaining of Chronicle2260with Previous Chronicle Hash2262and Chronicle Hash2264to Chronicle2266with Previous Chronicle Hash2268and Chronicle Hash2270to Chronicle2272with Previous Chronicle Hash2274and Chronicle Hash2276via a directional acyclic graph to record state changes.

This diagram illustrates that chronicles can be aggregated into Annals2200, which is a record of events for a whole year. Annals2200has basically the same composition as Chronicle2100inFIG. 21, but chronicles are now being chained instead of chronicle records. As data moves from hot storage in the form of Chronicle2100per day(s), it is placed in cold storage in the form of Annals2200. This makes searching, organizing, and locating records and state changes very easy, again reinforcing the traceability and visibility of data as well as the transparency of activity on Distributed Social Media Network300inFIG. 3.

FIG. 23is a block diagram of Chronicle Platform System Modules1608which is comprised of Chronicle Aggregation Platform System Module2300, Chronicle Archive Platform System Module2302, Chronicle Audit Platform System Module2304, and Chronicle Management Module2306. Chronicle Platform System Modules1608interacts with Core Modules700which provides all the cross-cutting functionality for Chronicle Platform System Modules1608. These modules represent the different functional sets that make up the Chronicle Platform System Modules1608which work across the entire platform. The platform uses one, many or all of these modules to work with Chronicle2100inFIG. 21. Chronicle Aggregation Platform System Module2300manages the functionality required for aggregating chronicles and creating annals. Chronicle Archive Platform System Module2302manages the functionality required for facilitating archiving as a service with third parties or actually archiving chronicles outside the platform with entities such as the Library of Congress. Chronicle Audit Platform System Module2304manages the functionality required to facilitate auditing in the public domain. Chronicle Management Module2306manages a general set of functions required for managing chronicles on the platform.

FIG. 24is a block diagram of Chronicle System Modules812which is comprised of Chronicle Aggregation System Module2402, Chronicle Archive System Module2404, Chronicle Audit System Module2408, Chronicle Blockchain System Module2410, Chronicle Content System Module2412, Chronicle Contracts System Module2414, Chronicle Core System Module2416, Chronicle Directed Acyclic Graph System Module2418, Chronicle Graph Encryption System Module2420, Chronicle Graph Hash System Module2422, Chronicle Graph Query System Module2424, Chronicle Graph System Module2426, Chronicle Index System Module2428, Chronicle Other System Module2430, Chronicle Source System Module2432, Chronicle State System Module2434, Chronicle System Module2436, Chronicle Workflow System Module2438, Chronicle chron URI System Module2440, Chronicle Directory System Module2442, and Chronicle Search System Module2444. Chronicle System Modules812interfaces with Chronicle2100as well as Core Modules700which provides all the cross-cutting functionality for Chronicle System Modules812. These modules represent the different functional sets that make up Chronicle System Modules812that serve Social Media System106inFIG. 1. Every Social Media System106uses one, many or all of these system modules to work with their local chronicle(s) represented by Chronicle2100inFIG. 21.

Chronicle Aggregation System Module2402manages the aggregation features and functionality required for chronicles. Chronicle Archive System Module2404manages the archive features and functionality required for chronicles. Chronicle Audit System Module2408manages the audit features and functionality required for chronicles. Chronicle Blockchain System Module2410manages the blockchain features and functionality required for chronicles. Chronicle Content System Module2412manages the content features and functionality required for chronicles. Chronicle Contracts System Module2414manages the contracts features and functionality required for chronicles. Chronicle Core System Module2416manages the core features and functionality required for chronicles. Chronicle Directed Acyclic Graph System Module2418manages the directed acyclic graph features and functionality required for chronicles. Chronicle Graph Encryption System Module2420manages the graph encryption features and functionality required for chronicles. Chronicle Graph Hash System Module2422manages the graph hash features and functionality required for chronicles. Chronicle Graph Query System Module2424manages the graph query features and functionality required for chronicles. Chronicle Graph System Module2426manages the graph features and functionality required for chronicles. Chronicle Index System Module2428manages the indexing features and functionality required for chronicles. Chronicle Other System Module2430manages other features and functionality required for chronicles. Chronicle Source System Module2432manages source features and functionality required for chronicles, Chronicle State System Module2434manages state features and functionality required for chronicles. Chronicle System Module2436is the top-level module that contains all the functionality required for managing all chronicle system modules. Chronicle Workflow System Module2438manages the workflow features and functionality required for chronicles. Chronicle chron URI System Module2440manages the chron URI features and functionality required for chronicles. Chronicle Directory System Module2442manages the directory features and functionality required for chronicles. Chronicle Search System Module2444manages the search features and functionality required for chronicles.

FIG. 25is a block diagram of Chronicle Record2000which is comprised of Directory Graph2034. Directory Graph2034, which descends from Base Graph2050inFIG. 20, consists of Directory Graph Schema2502, Directory Graph Schema Version2504, Directory Graph Hash2506, and Directory Graph Signature2507. Directory Graph2034also consists of Directory Graph Collection2508which contains Node(s)2510and Edge(s)2540. Node(s)2510consists of Person2512, Location2514, Profile2516, Reputation2518, and Group2520. Edge(s)2540consists of Lives At2542, Related To2544and Member Of2546. Person2512may contain the properties Full Name2560, Claimed Timestamp2562, Verified Timestamp2564, and Public Key2566; there may be other properties as well. Distributed Social Media Network300inFIG. 3utilizes a directory which is a phone book type listing of each and every User104inFIG. 1, namely Individuals402, Businesses404, Charities & Non-Profits412, and Government424inFIG. 4. In one embodiment of the invention, User104's listing could include name, contact details, profile information, reputation, group affiliations, etc. In another embodiment of the invention, User104could elect to just have their name listed and additional details unlisted. This diagram illustrates that each directory listing exists in Chronicle Record2000, making the information easily accessible and searchable as well as any state changes visible and traceable. Unlike existing social media platforms, User104inFIG. 1owns and controls their listing details, not the network. All the functionality needed to work with the directory, which is put into Chronicle2100fromFIG. 21, is encapsulated by various platform, system and app modules.

FIG. 26is a block diagram of Chronicle Record2000which is comprised of State Graph2030. State Graph2030, which descends from Base Graph2050inFIG. 20, consists of State Graph Schema2600, State Graph Schema Version2602, State Graph Hash2604, and State Graph Signature2607. State Graph2030also consists of State Graph Collection2606which contains Node(s)2608and Edge(s)2640. Node(s)2608consists of State2610. State2610has the properties State Enumeration2660, State Timestamp2662, and State Signed2664. State Graph Signature2607is used to do the signing at State Signed2664. State Enumeration2660consists of Submitted2670, Updated2672, Distributed2674, Verified2676, Signed2678, Published2680, Posted2682, Archived2684, and Rejected2686. This diagram provides another example of how the platform is using chronicle records as a construct to manage and run the platform. State Graph2030is used everywhere on the platform that state is needed. It tracks the state changes of data, workflows, and transformations and saves them in Chronicle Record2000. However, State Graph2030may or may not be in any given Chronicle Record2000. Unlike blockchain transactions, chronicle records are dynamic and do not always have the same composition.

FIG. 27is a block diagram of Directory Platform System Modules1610which is comprised of Directory Aggregation Platform System Module2700, Directory Archive Platform System Module2702, Directory Audit Platform System Module2704, and Directory Management Module2706. Directory Platform System Modules1610interacts with Core Modules700which provides all the cross-cutting functionality for Directory Platform System Modules1610. This diagram illustrates the required functionality for working with directories, including aggregation, archiving, auditing, and overall directory management across the platform. Every Social Media System106inFIG. 1has its own directory which contains listings of individuals or entities that User104is connected to, either by extending an invitation or accepting an invitation. Directories can also be aggregated across Distributed Social Media Network300inFIG. 3, whereby the data may or may not be replicated to every other Social Media System106inFIG. 1.

FIG. 28is a block diagram of Directory System Modules818which is comprised of Directory Claim System Module2802, Contact Directory System Module2804, Directory System Module2806, Directory Keys System Module2808, Directory listing URI System Module2810, Directory Name System Module2812, Directory Reputation System Module2814, Directory Profile System Module2816, Directory Verification System Module2818, and Group Directory System Module2820. These system modules represent the functionality required for Social Media System106inFIG. 1to work with a directory data set which consists of Chronicle Record2000along with Directory Graph2500and State Graph2030inside Chronicle2100. Given the platform's Distributed Architecture100inFIG. 1, every User104via its own Social Media System106is potentially contributing to the directory. All new listings are stored in Chronicle Record2000, specifically in Directory Graph2500, which is able to track state via State Graph2030. Any additions or changes to listings in the directory results in additional chronicle records. Directory System Modules818also interacts with Core Modules700which provides all the cross-cutting functionality for Directory System Modules818.

Directory Claim System Module2802provides the system modules for managing the claiming of listings in the directory. Directory Contact System Module2804provides the system modules for managing the contacting of listings in the directory. Directory System Module2806provides the system modules for managing the general features and functionality of the directory. Directory Keys System Module2808provides the system modules for managing keys in the directory. Directory listing URI System Module2810provides the system modules for managing listing URIs in the directory. Directory Name System Module2812provides the system modules for managing names in the directory. Directory Reputation System Module2814provides the system modules for managing reputation in the directory. Directory Profile System Module2816provides the system modules for managing profiles in the directory. Directory Verification System Module2818provides the system modules for managing verification in the directory. Directory Group System Module2820provides the system modules for managing groups of listings in the directory.

FIG. 29is a block diagram of Chronicle Record2000which is comprised of Content Graph2024. Content Graph2024descends from Base Graph2050inFIG. 20and consists of Content Graph Schema2902, Content Graph Schema Version2904, Content Graph Hash2906and Content Graph Signature2907. Content Graph2024also consists of Content Graph Collection2908which is comprised of Node(s)2910and Edge(s)2940. Node(s)2910consists of Content2912, License2914, Copyright2916, Subject Headings2918, Subdivisions2920, Classification2922, and Catalog2924. Content2912consists of Id2950, Timestamp2952, Distribution Release Timestamp2954, Public Release Timestamp2956, Audit Release Timestamp2958, and Archive Release Timestamp2960. This diagram illustrates that Content System Modules816inFIG. 8uses Chronicle2100inFIG. 21for data storage, access and search. In essence, all content is stored in Chronicle Record2000with Content Graph2024and Content Graph Collection2808, which in addition to the content, provides critical properties such as license and copyright as well as ways to search the content. The various content timestamps are used by workflows to determine what to do with the content and when.

FIG. 30is a block diagram of Account Platform System Modules1626which is comprised of Access Control Account System Module3002, Account Management Module3004, Analytics Account System Module3006, Compliance Account System Module3008, Helpdesk Account System Module3010, Invoice Account System Module3012, Partner Account System Module3014, Payment Account System Module3016, Quota Account System Module3018, and Usage Account System Module3020. Account Platform System Modules1626interacts with Core Modules700which provides all the cross-cutting functionality for Account Platform System Modules1626. This diagram details the platform system modules that enable all the functionality required for accounting on the platform.

FIG. 31is a block diagram of Distribution System Modules820which is comprised of the Distribution System Module3100, Distribution Event Grid Module3102, Distribution Notification Hub Module3106, and Consensus Event Grid Module3110. Distribution Event Grid Module3102is connected to Distribution Event Grid3104. Distribution Notification Hub Module3106is connected to Distribution Notification Hub3108. Consensus Event Grid Module3110is connected to Consensus Event Grid3112. Distribution System Modules820interacts with Chronicle2100as well as Core Modules700which provides all the cross-cutting functionality for Distribution System Modules820. This diagram details that information is distributed across Distributed Social Media Network300inFIG. 3using both pull and push techniques.

In one embodiment of the invention, Distribution Event Grid3104managed by Distribution Event Grid Module3102is used for information distribution on the platform. Here User104tells its Social Media System106inFIG. 1, “Hey, I want to know about certain things. Let me know when you have new data for a specific topic, and I'm going to give you an address for you to use. I'm going to go do other things while I wait. You can always use this address whenever you have something for me.” Social Media System106fulfills on its promise to User104by returning with the requested data. Using event grids on Distributed Social Media Network300inFIG. 3allows the social media systems to communicate in parallel on a massive scale, thereby creating tremendous efficiencies.

In another embodiment of the invention, Distribution Notification Hub3108managed by Distribution Notification Hub Module3106is used. Here Social Media App(s)110-1to N and Social Media Systems106-1to N fromFIG. 3who are all waiting for the same data can now efficiently distribute that data to Users104-1to N at the same time. Again, embodiments of the present technology leverage parallelism for distributed communication without a centralized server managing information flow on the network.

In another embodiment of the invention, Consensus Event Grid3112managed by Consensus Event Grid Module3110uses an event grid for consensus.

FIG. 32is a block diagram of Search System Modules840which is comprised of Search System Module3200(there could be others) and interacts with Chronicle2100as well as Core Modules700which provides all the cross-cutting functionality for Search System Modules840. This diagram details the system module(s) that enable all the functionality required for User104inFIG. 1to do searches of Chronicle2100inFIG. 21.

FIG. 33is a block diagram of Connection System Modules814which is comprised of Connection System Module3300(there could be others) and interacts with Chronicle2100, Directory System Modules818, and Core Modules700which provides all the cross-cutting functionality for Connection System Modules814. Social Media System106inFIG. 1uses Connection System Module3300to store directory listings of connections via Directory System Modules818into their Chronicle2100. This diagram demonstrates how various system modules can interact with each other. For example, it would also be possible to layer in Search System Module3200inFIG. 32to quickly find the directory listings User104inFIG. 1wants to add to their Chronicle2100.

FIG. 34is a block diagram that illustrates how Post3400is made on Distributed Social Media Network300inFIG. 3. Posts can be deleted at any time. User104maintains total ownership and control of the content and associated metadata. This type of sharing is private. User104can post messages plus content that is stored on their Social Media System106, such as photos, videos, PDFs, etc., provided it meets the terms of service (and video time limits) of the network. User104uses Social Media App(s)110to compose a post. They have at their ability all App Modules1300. They use Message Board App Module1330to create a post and may also use other app modules in the creation of the post, such as Connection App Module1314inFIG. 13to designate who they are going to share it with. Before they send the post, User104uses Signing Core Module724to digitally sign the post. The post now goes into Posting App Module1336which sends the post to Social Media System106via Network(s)108.

Social Media System106is composed of all System Modules800. These system modules can all work together or stand on their own to provide functionality for Social Media System106. First the post goes into Compliance System Modules850to ensure the message conforms to the platform's compliance standards and rules. This may or may not include scanning the message, sending an image to a learning machine to determine its contents, or opening up the message for third party analysis with functionality represented by AI System Modules804, Machine Learning System Modules828, and Third Party System Modules844inFIG. 8. While data scraping is a possibility, it is not the intent. Ideally the message is read for analysis, but never stored off. Next the post is stored inside User104's own Chronicle2100inFIG. 21via Chronicle System Modules812. Because posting allows User104to own, control, and delete content, the actual content does not leave their Social Media System106. Connection System Modules814creates a URI to the data in Users104's Chronicle2100which is then encrypted and passed onto Distribution System Modules820, so the post can be distributed to its designated recipients via Network(s)108.

User104-1accesses the post on their Social Media App(s)110-1aided by Message Board App Module1330. User104-2accesses the post on their Social Media App(s)110-2aided by Message Board App Module1330. User104-N accesses the post on their Social Media App(s)110-N aided by Message Board App Module1330. The ellipse between Social Media App(s)110-2and Social Media App(s)110-N illustrates that there are N number of social media app(s) for every user on the network that could potentially receive User104's post. Core Modules700provides all the cross-cutting functionality for Social Media App(s)110and Social Media System106and their associated App Modules1300, System Modules800, Platform System Modules1600required to Post3400.

In sum, Distributed Social Media Network300inFIG. 3facilitates a truly unique form of posting not possible with existing centralized social media networks. User104creates their own specific instance of a social media network where they have total ownership and control of the content they post as well as the connections they send it to. All intended connections receive all intended posts. There is no algorithm or centralized authority filtering the posts or the recipients, and User104can delete a post at any time without fearing the content and associated metadata remains stored off in an external data center, vulnerable to malicious misuse.

FIG. 35is a use case diagram of Publishers3500. It introduces a new subset to the superset User104inFIG. 1and illustrates that Individuals402, Businesses404, Charities & Non-Profits412, and Government424can all be Publisher3502on Distributed Social Media Network300inFIG. 3.

FIG. 36is a block diagram of Platform Tenets3600which is comprised of Complete Traceability3602, Complete Transparency3604, Fair Intrinsic Value3606, Integrity is the Currency3608, Level Playing Field3610, Permanent Public Record3612, Platform Anti-Counterfeiting Measures3614, Public Archiving3616, Public Auditing3618, Records are Signed3620, Right of First Refusal3622, Users are Known3624, Users are Verified3626, Users Get Paid for their Content3628, and Content is Verified3630. This diagram details the main tenets of the platform that are essential to addressing the problems with existing social media options and delivering a transformed social media experience based on integrity, civility and fairness.

FIG. 37is a block diagram of Publishable Content Types3700which is comprised of Announcements3702, Broadcast3704, Business3706, Calendar of Events3708, Circular Ads3710, Comics3712, Crossword Puzzles3714, Classified Ads3716, Display Ads3718, Editorial/Opinion3720, Features3722, Medium Based3724, News3726, Notifications3728, LANA Media Type Based3730, Recantation3732, Retraction3734, Rhetoric3736, Streaming3738, Sports3740, Subject Based3742, Other3744, This Day in History3746, and Advice3748. This diagram illustrates that many of Publishable Content Types3700follow the lexicon of a traditional newspaper, transformed for the digital age: News3726, Business3706, Sports3740, Features3722(such as home and garden, cars, travel, cooking, technology, special focused reports), Editorial/Opinion3720, Announcements3702, Notifications3728, Calendar of Events3708, Classified Ads3716, Display Ads3718, Circular Ads3710, Comics3712, Crossword Puzzles3714, and Advice3748. Publishable content can also be Subject Based3742(such as faith/inspiration or comedy/satire), Medium Based3724(such as magazines, books, music, movies, or art), IANA Media Type Based3730(such as text, photo, etc.), Broadcast3704(includes live curation), Streaming3738(includes self-curation), Other3744(such as a daily diary), or This Day in History3746(a summary of key events from each daily Chronicle2100inFIG. 21). Publishable content cannot be deleted once published, but User104inFIG. 1can publish a Recantation3732or Retraction3734.

FIG. 38is a block diagram of Consensus by Conference3800which is required for publishing on the platform. It is comprised of Conference Consensus Categories3802, Conference Consensus Preconditions3810, Conference Consensus Settings3822, and Consensus by Conference Proof of Stake3850. Consensus by Conference3800is used to generate protected consensus within a protected network as every User104, Social Media System106and Social Media App(s)110in Distributed Social Media Network300inFIG. 3is known, authenticated and authorized.

Conference Consensus Categories3802consists of Conference Consensus Machine Learning3804which is based on a training set of data containing instances whose features and assigned category membership is known, Conference Consensus Features3806which are derived from system composition profiles and their resulting performance metrics from telemetry data managed by Telemetry System226inFIG. 2, and Conference Consensus Classifier3808which is a classification algorithm that maps a new instance's system profile data to a category.

Conference Consensus Preconditions3810consists of Platform System Category Conference Topics3812, Platform System Category Attendee Topics3814, Publisher Consensus System Category Classification3816, Publisher Consensus System Category Conference Event Subscription3818, and Publisher Consensus System Category Attendee Event Subscription3820.

Platform System Category Conference Topics3812and Platform System Category Attendee Topics3814, along with other Conference Consensus Preconditions3810, utilize Consensus Event Grid3112inFIG. 31which is managed by Consensus Event Grid Module3110inFIG. 31. Event grids are incredibly efficient in terms of a Publish-Subscribe model and massively scalable. To use this as a basis for triggering consensus requests adds to the scalability and parallelism of Consensus by Conference3800.

Each Publisher3502inFIG. 35has their own Social Media System106inFIG. 1which placed into a specific Publisher Consensus System Category Classification3816by Consensus by Conference Machine Learning3804, Consensus by Conference Features3806, and Consensus by Conference Classifier3808. Category classifications are used to implement the platform tenets Level Playing Field3610and Fair Intrinsic Value3606inFIG. 36because not every Publisher3502's Social Media System106inFIG. 1has the same composition or workload. For example, it is not level or fair to expect a small publisher with a small system footprint that generates four pieces of content a week to be able to meet the consensus requirements of a really large publisher with a really large system footprint that generates thousands of pieces of content a day. As a result, Publisher3502inFIG. 35is put into a population with other publishers that have similar performance capabilities and workload capacities. Publisher Consensus System Category Classification3816also uses machine learning to dynamically self-tune itself so when Publisher3502inFIG. 35changes their system footprint and/or produces more or less content, they actually shift though different classifications on the network.

The use of Consensus by Conference Categories3802, Consensus by Conference Preconditions3810, and specifically Publisher Consensus System Category Classification3816, enables the platform to create a multitude of consensus networks based on classification which in turn allows the platform to scale and process consensus requests in parallel. Additionally, each Social Media System106inFIG. 1within their Publisher Consensus System Category Classification3816is configured to utilize thread pools to individually handle multiple consensus requests resulting in multiple dimensions of scalability and parallelism as well as incredibly low latency.

Conference Consensus Settings3822consists of Category Conference Attendee Count3824, Category Conference Session Count3826, and Category Conference Attendees Per Session Count3828. Each category conference has an attendee count, session count, and attendees per session count which enable degrees of parallelism. These settings are dynamically generated by each Publisher Consensus System Category Classification3816and used by Consensus by Conference Categories3802to fine tune scalability.

Consensus by Conference Proof of Stake3850is at the heart of Consensus by Conference3800and based on the platform tenet Integrity is the Currency3608inFIG. 36. A hash is a pure mathematical equation, and it is in every publisher's best interest to do the calculation right. If they don't, it is reported in Conference Graph2036inFIG. 20which provides Complete Traceability3602and Complete Transparency3604within Permanent Public Record3612inFIG. 36. Bad actors can be called out and held accountable, so there's really no upside to being a notorious Publisher3502inFIG. 35on the network. This is why Consensus by Conference Proof of Stake3850works within a protected consensus requirement.

In short, Consensus by Conference3800represents a really efficient, highly scalable, massively distributed communication protocol designed to bring integrity back to social media networking.

FIG. 39is a block diagram Chronicle Record2000which is comprised of Conference Graph2036. Conference Graph2036descends from Base Graph2050inFIG. 20and consists of Conference Graph Schema3902, Conference Graph Schema Version3904, Conference Graph Hash3906, and Conference Graph Signature3907. Conference Graph2036also consists of Conference Graph Collection3908which contains Node(s)3910and Edge(s)3940. Node(s)3910include Conference3912, Coordinator3916, Attendees3918and Graphs3920. Edge(s)3940include Results3942. There could also be other nodes and edges. Conference3912has the properties Conference Id3960and Conference Timestamp3962. Coordinator3916has the properties Coordinator Id3964and Coordinator Address3966. Attendees3918has the properties Attendee Id3968and Attendee Address3970. Results3942has the properties Result Timestamp3972, Result Hash3974, and Result Signature3976. This diagram illustrates that when consensus is requested, a conference is created, and the result of that conference is basically a binary whereby consensus is affirmed or not affirmed. The whole consensus process is captured in Chronicle Record2000. All Users are Known3624and all Users are Verified3626as detailed inFIG. 36. Conference Graph2036stores off all the information about the conference including when it is set up, who the coordinator is, who the attendees are, and the result. Because Chronicle2100is a system of record, at the end of Consensus by Conference3800inFIG. 38, there is an immutable record of that consensus which provides Complete Traceability3602and Complete Transparency3604as detailed inFIG. 36.

FIG. 40is block diagram detailing the workflow for Generate Conference Coordinator4002which is triggered by New Chronicle Record4000submitted by Publisher3502inFIG. 35for Consensus by Conference3800inFIG. 38. Conference creation starts with the designation of a conference coordinator who is responsible for setting up and coordinating the conference. Core Modules700connected to Generate Conference Coordinator4002provide all the cross-cutting functionality for the workflow.

The first step of Generate Conference Coordinator4002is Create Coordinator Invitation4004which requires Create Coordinator Invitation Metadata4006comprised of Coordinator RSVP Id4008, Coordinator RSVP Timestamp4010, Coordinator RSVP Address4012, and Coordinator RSVP Key4014. Create Coordinator Invitation Metadata4006also interfaces with RSVP Timestamp Calculator4016. Coordinator RSVP Timestamp4010represents the window for possible coordinators to respond to the request and generates efficiencies for responding. The conference only needs one coordinator who is selected randomly and in a timely fashion. This workflow doesn't wait for all potential coordinators to respond, nor do they have to respond if they are busy working on consensus for other requests and don't see this request until after the specified date/time. RSVP Timestamp Calculator4016represents the functionality needed to determine the RSVP window to respond. This setting is dynamic and adjustable for maximum efficiency. Coordinator RSVP Address4012is the address that potential coordinators have to respond to with their RSVP. Coordinator RSVP Key4014is used to validate that a respondent is responding to the correct request, which eliminates potential mischief and hacking.

The next step is Add Coordinator Invitation to Queue4018, which links to Coordinator Invitation Queue4020and Coordinator Registration Service4022which is listening on the address that was specified in Coordinator RSVP Address4012for respondents who want to be the coordinator. Then it is time to determine Coordinator Invitation Event Source4024. The correct Category Coordinator Topic4026is selected, and then the invitation is added to Consensus Event Grid3112. Category Coordinator Event Subscription4028represents all the other publishers in that category who received that event. Any publisher who has a subscription to that topic and has a thread available to service the request submits Coordinator RSVP4030. Coordinator RSVP4030has a relationship to Coordinator Registration Data4032. A publisher on submitting their RSVP is going to submit Coordinator RSVP Id4008plus Coordinator RSVP Hash4038of Coordinator Registration Data4032by using Coordinator RSVP Key4014. If they are the first to respond where everything checks out (no hackers or bad actors), Coordinator RSVP4030presents them to Coordinator Registration Service4022.

Finally, Coordinator Registration Service4022responds back to Coordinator RSVP4030with New Chronicle Record4000. In one embodiment of the invention, the entire chronicle record is passed to the coordinator. In another embodiment of the invention, a URI to the chronicle record in the chronicle that resides in Publisher3502's Social Media System106inFIG. 1is passed to the coordinator using Chronicle System Modules812inFIG. 8. Because only one coordinator is selected for each conference, if anyone else talks to Coordinator Registration Service4022within Coordinator RSVP Timestamp4010, no record or URI is passed to them. Coordinator4040is then returned to Publisher3502inFIG. 35who initiated the consensus. This workflow also consists of Coordinator Request Retry Setting4034which is responsible for determining the number of retry attempts to enlist a coordinator for the conference and Coordinator Request Transient Fault Policy4036which is used to mitigate technical exceptions that happen during the workflow. Both generate additional efficiencies in the distributed parallel communications and help ensure the coordinator position is filled in a timely manner.

FIG. 41is a block diagram detailing the workflow for Generate Conference Attendees4102which is triggered by New Chronicle Record4000submitted by Publisher3502inFIG. 35for consensus. After Generate Conference Coordinator4002inFIG. 40is complete, it is the job of Coordinator4040inFIG. 40to gather attendees for the conference to determine consensus utilizing Category Conference Attendee Count3824inFIG. 38. In another embodiment of the invention, Coordinator4040can generate sessions as well utilizing Category Conference Session Count3826inFIG. 38. Core Modules700connected to Generate Conference Attendees4102provide all the cross-cutting functionality for the workflow.

The first step of Generate Conference Attendees4102is Create Attendee Invitation4104which requires Create Attendee Invitation Metadata4106comprised of Attendee RSVP Id4108, Attendee RSVP Timestamp4110, Attendee RSVP Address4112, and Attendee RSVP Key4114. Create Attendee Invitation Metadata4106also interfaces with RSVP Timestamp Calculator4016. Attendee RSVP Timestamp4110represents the window for possible attendees to respond to the request and generates efficiencies for responding. This workflow doesn't wait for all potential attendees to respond, nor do they have to respond if they are busy working on consensus for other requests and don't see this request until after the specified timestamp. RSVP Timestamp Calculator4016represents the functionality needed to determine the RSVP window to respond. This setting is dynamic and adjustable for maximum efficiency. Attendee RSVP Address4112is the address that potential attendees have to respond to with their RSVP, and Attendee RSVP Key4114is used to validate that a respondent is responding to the correct request, which eliminates potential mischief and hacking.

The next step is Add Attendee Invitation to Queue4118, which links to Attendee Invitation Queue4120and Attendee Registration Service4122which is listening for and accepting invitations to be an attendee for the conference up to Category Conference Attendee Count3824. Then it is time to determine Attendee Invitation Event Source4124. The correct Category Attendee Topic4126is selected, and then the invitation is added to Consensus Event Grid3112. Category Attendee Event Subscription4128represents all the other publishers in that category who received that event. Any publisher who has a subscription to that topic and has a thread available to service the request submits Attendee RSVP4130. Attendee RSVP4130has a relationship to Attendee Registration Data4132. Attendee Registration Data4132consists of Attendee RSVP Id4108, Attendee RSVP Hash4138, Attendee Id and Address4140, and New Chronicle Record4000. A publisher on submitting their RSVP is going to submit Attendee RSVP Id4108plus Attendee RSVP Hash4138of Attendee Registration Data4132by using Attendee RSVP Key4114. If they respond before Category Conference Attendee Count3824has been met and everything checks out (no hackers or bad actors), Attendee RSVP4130presents them to Attendee Registration Service4122.

Finally, Attendee Registration Service4122responds back to Attendee RSVP4130with New Chronicle Record4000. In one embodiment of the invention, the entire chronicle record is passed to the attendees. In another embodiment of the invention, a URI to the chronicle record in the chronicle that resides in Publisher3502's Social Media System106inFIG. 1is passed to the attendees using Chronicle System Modules812inFIG. 8. If anyone else talks to Attendee Registration Service4122after Attendee RSVP Timestamp4110or after Category Conference Attendee Count3824has been met, no record or URI is passed to them. Attendees4142is then returned to Publisher3502inFIG. 35who initiated the consensus. Coordinator4040inFIG. 40and Attendees4142are both needed to determine consensus for New Chronicle Record4000. This workflow also consists of Attendee Request Retry Setting4134which is responsible for determining the number of retry attempts to enlist attendees for the conference and Attendee Request Transient Fault Policy4136which is used to mitigate technical exceptions that happen during the workflow. Both generate additional efficiencies in the distributed parallel communications and help ensure the attendee positions are filled in a timely manner.

FIG. 42is a block diagram of Consensus by Conference Algorithm4200which illustrates a workflow for consensus. Consensus by Conference Algorithm4200is associated with New Chronicle Record4000, Chronicle System206, System Modules800, and Core Modules700which provide all the cross-cutting functionality required for the consensus workflow.

The first step is Generate Consensus by Conference Coordinator4002which yields Coordinator Results4208. The second step is Generate Consensus by Conference Attendees4102yields Attendees Results4210. The third step is Distributed Minimum Spanning Tree4212which represents the processes associated with setting up a communications network for the publisher, coordinator and attendees where nodes communicate by message passing. The fourth step is Telephone Gossip4214which represents the gossiping protocol utilized for consensus. It is initiated between publisher, coordinator and attendees. Telephone Gossip4214is associated with Publisher and Coordinator Are Listeners Only4220. During the process of gossip, the publisher and coordinator listen only. Graph Schema Hash Algorithm2086illustrates the algorithm by which the coordinator and the attendees calculate the graph hashes for New Chronicle Record4000. In another embodiment, the coordinator and attendees utilize Object Graph Hash Algorithm2084inFIG. 20to calculate the hashes for New Chronicle Record4000. Graph Schema Hash Algorithm2086is associated with Verification Exchange4216.

The fifth step is Verification Exchange4216which illustrates that as each attendee calculates a hash for a graph in New Chronicle Record4000, they exchange that information utilizing Telephone Gossip4214. Verification Exchange4216is also associated with Publisher and Coordinator Are Listeners Only4220. The sixth step is Coordinator Confirms and Saves Results4218which illustrates that all of the attendees' results used to confirm the hash for each graph in New Chronicle Record4000are saved by the coordinator into their copy of New Chronicle Record4000. As Coordinator Confirms and Saves Results4218, if any of the calculations do not match then Disagreement4221is reached, and Consensus by Conference Algorithm4200terminates with no consensus. Coordinator Confirms and Saves Results4218is also associated with Publisher and Coordinator Are Listeners Only4220. The seventh step is Coordinator Record Hash and Record Signature4222which represents the steps to calculate Record Hash2014inFIG. 20. The coordinator sorts the hashing results by graph name alphanumerically and then applies Merkle Tree2082inFIG. 20to determine Record Hash2014for New Chronicle Record4000. In another embodiment of the invention, the coordinator also determines Record Signature2018which is added to New Chronicle Record4000. Additionally, each Base Graph Signature2058onFIG. 20is also determined and added to New Chronicle Record4000.

At this point in the workflow process, New Chronicle Record4000is committed to the publisher, coordinator and attendees' Chronicle2100inFIG. 21. In another embodiment of the invention, New Chronicle Record4000is propagated to every Social Media System106on Distributed Social Media Network300inFIG. 3. The final step is Coordinator Sends Platform New Chronicle Record4224whereby the coordinator sends the platform New Chronicle Record4000.

FIG. 43is a block diagram of Chronicle Workflow System Module2438which is comprised of Create Chronicle Record4302, Clone Chronicle Record4330, and Consensus by Conference Algorithm4200. Create Chronicle Record4302consists of Generate Record Nonce4304, Save Record Nonce4306, Calculate Graph Hashes4308, Save Graph Hashes4310, Calculate Estimated Work4312, and Save Estimated Work4314. Clone Chronicle Record4330consists of Copy Chronicle Record4332, Save Chronicle Record Clone4334, Confirm Clone Hashes4336, Calculate Estimated Work4338, and Save Estimated Work4340. Both Create Chronicle Record4302and Clone Chronicle Record4330require Estimated Work Calculation4360which is an algorithm to estimate the amount of work required to complete the hashing algorithms for a Chronicle Record2000inFIG. 20. Chronicle Workflow System Module2348interacts with Core Modules700which provides all the cross-cutting functionality for Chronicle Workflow System Module2348.

FIG. 44is a block diagram which illustrates how User104can Publish4400on Distributed Social Media Network300inFIG. 3. This process differs from Post3400inFIG. 34. Published content can be edited, corrected, retracted or recanted, but never deleted. It becomes part of Permanent Public Record3612inFIG. 36, audited by Public Auditors114and held by Public Archivists116inFIG. 3outside of the network. Past versions are always visible. This type of sharing is public. While User104may retain ownership and all the rights associated with ownership including copyright and licensing, the content and associated metadata does not reside exclusively in their Social Media System106inFIG. 1. It is published out to the distributed system and released to the public. When crafting a message to Publish4400, User104must go through a publisher they select on the network or be a publisher (see Publisher3502inFIG. 35). In one embodiment of the invention, Distributed Social Media Network300inFIG. 3sets limits on the number of connections User104can post to before User104must go through a publisher or become a publisher to reach a larger group of connections.

User104uses Social Media App(s)110to Publish4400. They have at their ability all of the App Modules1300and may use one, some or all of the modules in their Social Media App(s)110. In this example they use Message Board App Module1330to compose the publishable content. Once the publishable content is ready, User104must sign the content using Signing Core Module724, select Publisher3502, and pay any fees associated with publishing via Payment App Module1334. In another embodiment of the invention, Payment App Module1334may pull from funds already held in an account between User104and Publisher3502. Then the publishable content is sent to Social Media System106-1across Network(s)108via Publishing App Module1338.

Social Media System106-1is composed of all System Modules800. These system modules can all work together or stand on their own to provide functionality for Social Media System106-1. First the publishable content goes into Compliance System Modules850to ensure it conforms to the compliance rules for Publisher3502and the platform. Next the publishable content is stored as New Chronicle Record4000inFIG. 40via Chronicle System Modules812. Search System Modules840is also associated with Social Media System106-1.

New Chronicle Record4000inFIG. 40is then sent to Publisher3502across Network(s)108to their Social Media System106-2which is comprised of all System Modules800or some subset of system modules. When payment is received via Payment System Modules834, Workflow System Modules858is notified of the pending content item being published for User104. When New Chronicle Record4000inFIG. 40is sent, either the entire record with all its bits, including every bit of content is transmitted, or an optimization is sent with URIs to content bits. The workflow upon receiving New Chronicle Record4000inFIG. 40determines if it has the content, and if it doesn't, it goes and gets the content via the URIs. Once the content is received and verified by Workflow System Modules858, Compliance System Modules850verifies that the content meets Publisher3502's compliance rules. Workflow System Modules858then either accepts the content for the next steps of the workflow or rejects the content. Alternately content may be flagged for review. In some cases, the content will need to be manually inspected by Publisher3502.

Workflow System Modules858may also invoke other system modules as part of the workflow to publish the content. Content may be submitted to AI System Modules804or Machine Learning System Modules828inFIG. 8for analysis. Content may be submitted to Licensing System Modules826inFIG. 8for content that is determined to be licensed. Content may be submitted to Third Party System Modules844inFIG. 8where additional attribution or data transformations can be applied to Content Graph2024, such as Copyright2916, Subject Headings2918, Subdivisions2920, Classification2922, and Catalog2924inFIG. 29. Additionally, other content properties may be set by Workflow System Modules858, including Distribution Release Timestamp2954, Public Release Timestamp2956, Audit Release Timestamp2958, and Archive Release Timestamp2960inFIG. 29. When the content is complete, New Chronicle Record4000inFIG. 40is then submitted to Chronicle System Modules812and specifically Chronicle Workflow System Module2438inFIG. 24for consensus using Consensus by Conference Algorithm4200inFIG. 42.

When consensus is complete, New Chronicle Record4000inFIG. 40is either accepted or rejected. If accepted, it is saved to Chronicle System Module812. If rejected, a rejection notice is sent back to User104. Once saved, New Chronicle Record4000inFIG. 40goes to Publishing System Modules838for final checks. Then it goes to Distribution System Modules820and is placed in Distribution Event Grid Module3102. Distribution occurs over Network(s)108with Distribution Event Grid3104inFIG. 31. In another embodiment of the invention, User104-N can request chronicle records from Publisher3502automatically through their Social Media App(s)110-N as a refresh via a setting within Message Board App Module1330. When published content gets committed to Chronicle2100inFIG. 21, it is distributed out to Distributed Social Media Network300inFIG. 3. Chronicle Platform System Modules1608stores New Chronicle Record4000fromFIG. 40in the platform chronicle. It also monitors Audit Release Timestamp2958and Archive Release Timestamp2960inFIG. 29, so that when Publisher3502says New Chronicle Record4000inFIG. 40can be released to audit or archive, it can either be sent or picked up via the Audit System Modules810and the Archive System Modules808inFIG. 8. Core Modules700provide all the cross-cutting functionality for all Social Media App(s)110and all Social Media Systems106and their associated App Modules1300, System Modules800, Platform System Modules1600required to Publish4400.

Distributed Architecture100inFIG. 1and these unique publishing features provide the opportunity to address the problem of fake news in ways that centralized social media networks cannot. User104does not have the ability to publish to the public network without the content being vetted. Every Publisher3502is responsible for the content that is published through their Social Media System106. There is an inherent financial incentive for the publisher to vet the content, because if the content is incorrect, has some negative social impact, or does not meet community or journalistic standards, then the publisher incurs the cost by association. Because Distributed Social Media Network300inFIG. 3is made up of a multitude of independent publishers, vetting can be done efficiently and effectively at scale. Because all Users are Known3624, all Users are Verified3626, and all published content becomes part of Permanent Public Record3612inFIG. 36, there is no wondering where it came from, what happened during the publishing workflow, plus any state changes, which provides Complete Traceability3602and Complete Transparency3604inFIG. 36. The net result is a level of transparency and accountability about published content that is not possible in the existing paradigm. Publishers provide a valuable service to the platform and its tenet that Integrity is the Currency3608inFIG. 36. They also help ensure the primacy of Chronicle2100inFIG. 21as an institution.

Distributed Social Media Network300inFIG. 3allows for many different publishing use cases, many of which involve financial transactions. Any number of financial clearing types can be used to clear these transactions, including credit cards, ACH, PayPal, public cryptocurrencies like Bitcoin, or a private cryptocurrency created by the network. In one embodiment of the invention, Publisher3502publishes content they have designated premium. Money is paid to the publisher by User104if they are connected and want to receive the premium content.

In another embodiment of the invention, User104publishes Notifications3728or Announcements3702inFIG. 37. Money is paid to the selected publisher, unless User104is a government agency or elected official. With various embodiments of the present technology, government data can now be recorded with decentralized authorities at the local, state and national level. Distributed Social Media Network300inFIG. 3will be able to describe what government is outside of government itself and save the data out for public consumption within the context of social media. This makes government more accessible and accountable as Announcements3702and Notifications3728are now part of Permanent Public Record3612inFIG. 36.

In another embodiment of the invention, User104publishes Rhetoric3736inFIG. 37in response to published content, and money is paid to the selected publisher. Publisher3502(and AI) moderates this content, following established ground rules for constructive and civil dialog.

In another embodiment of the invention, User104submits content such as News3726or Features3722inFIG. 37for publication by a selected publisher. If accepted, money is paid to User104by Publisher3502.

In another embodiment of the invention, User104places Classified Ads3716inFIG. 37by selecting a publisher based on location or subject who vets the ad and facilitates the placement. Distributed Social Media Network300inFIG. 3makes the transaction possible with financial clearing touchpoints via email and a workflow that will not distribute the ad until confirmation of payment. It also facilitates the use of smart contracts to initialize a transaction between two users on the network within the ad itself.

In another embodiment of the invention, User104and Publisher3502go back and forth about denials, edits, etc. to content submitted for publishing. There is no exchange of money during these transactions, but there is a protocol where both sides track the data. Validation and agreement is required at every step, and if both parties agree, the contract is good.

In another embodiment of the invention, User104purchases video or music (Medium Based3724inFIG. 37) from Publisher3502. A transaction ID, plus copyright and owner, is injected into the content, and a hash is used to create dynamic encryption. Digital rights become public, instead of stored in a centralized database, and form a searchable repository of who owns what hashes. User104must own the rights to a song or a movie to be able to play it. No one else will be able to access (or hack) the file.

In another embodiment of the invention, User104publishes an academic paper (Other3744inFIG. 37) and makes it available for peer review with specified rules, thereby providing accountability and accelerating an oftentimes lengthy review process.

Consistent with creating a Level Playing Field3610inFIG. 36, Publisher3502keeps any subscription, publishing or advertising fees generated from these publishing use cases. The platform takes a small transaction fee for facilitating the financial transactions with User104. Profit for few in the existing centralized social media paradigm become profit for many on Distributed Social Media Network300inFIG. 3as publishers are paid for their content and advertising dollars are distributed across a wide range of media properties.

Note that published content is read only by default. User104and Publisher3502can then determine additional user rights, such as post comment to connections, publish rhetoric to permanent public record, re-share as a post to connections, download, or print. Distributed Social Media Network300inFIG. 3allows for ways to maintain publisher exclusivity and may also have different rights for publishers or businesses that want to group or share content for publication on the network.

FIG. 45is a block diagram of Connections and Groups4500which illustrates the connections and groups functionality of the platform. User104uses Social Media App(s)110to work with Message Board App Module1330, Directory App Module1318, and Chronicle App Module1312. Social Media App(s)110connects to Social Media System106via Network(s)108. Social Media System106for User104connects to Chronicle System Modules812and Directory System Modules818. Directory System Modules818interfaces with Contact Directory System Modules2804and Group Directory System Module2820. Social Media App(s)110and Social Media System106also connect via Network(s)108to Directory System208and Chronicle System206as well as any Platform Systems102. Directory System208utilizes Directory Platform System Modules1610. Chronicle System206utilizes Chronicle Platform System Modules1608. Chronicle2100represents the use of the chronicle and any Chronicle Record2000, Directory Graph2500, and State Graph2030that Social Media System106, Social Media App(s)110, and Platform Systems102may interact with. Group Directory System Module2820enables User104to work with Directory Graph2034and Group2520node inFIG. 25. Using Group Directory System Module2820, User104can create groups in Group2520node inFIG. 25. User104may also use Contact Directory System Module2804to establish contact with other users in Directory System208. Contact Directory System Module2804can also be used to facilitate connection requests that other users may have for User104. Core Modules700are used for any cross-cutting concerns across Social Media App(s)110, Social Media System106, Platform Systems102, App Modules1300, System Modules800, and Platform System Modules1600as well as all functionality specific to Connections and Groups4500.

This diagram illustrates how User104works with the directory to make connections and create groups. User104makes connections with other users that they want to interact with on Distributed Social Media Network300inFIG. 3, either by extending or accepting an invitation to connect. User104can place these connections in groups that may include one, few, many or all of their connections, such as spouse group, family group, best friends group, church group, co-worker group, customer group, subscriber group, etc. These groups are then used to designate recipients of a message when User104wants to Post3400inFIG. 34or Publish4400inFIG. 44.

FIG. 46is a block diagram of Identity4600which illustrates the identity functionality of the platform. User104uses Social Media App(s)110to work with Message Board App Modules1330, Directory App Module1318, Chronicle App Module1312, and Identity App Module1322. Social Media App(s)110connects to Social Media System106via Network(s)108. Social Media System106for User104utilizes Identity System Modules822, Chronicle System Modules812, and Directory System Modules818. Directory System Modules818interfaces with Contact Directory System Module2804and Group Directory System Module2820. Social Media App(s)110and Social Media System106also connect via Network(s)108to Identity System210, Directory System208, and Chronicle System206as well as any Platform Systems102. Identity System210utilizes Identity Platform System Modules1612. Directory System208utilizes Directory Platform System Modules1610. Chronicle System206utilizes Chronicle Platform System Modules1608. Chronicle2100represents the use of the chronicle and any Chronicle Record2000, Directory Graph2500, and State Graph2030that Social Media System106, Social Media App(s)110, and Platform Systems102may interact with. Core Modules700are used for any cross-cutting concerns across Social Media App(s)110, Social Media System106, Platform Systems102, App Modules1300, System Modules800, and Platform System Modules1600as well as all functionality specific to Identity4600.

This diagram illustrates that Identity System210and its utilization of Identity Platform System Modules1612is distinct and separate from Directory System208and its utilization of Directory Platform System Modules1610. Identity System210and Identity Platform System Modules1612are responsible for authentication and authorization of all users, systems, and apps as well as the interconnections of Platform Systems102, App Modules1300, System Modules800, and Platform System Modules1600.

FIG. 47is a block diagram of Data Analysis4700which illustrates the data analysis functionality of the platform. User104utilizes Social Media App(s)110to work with Chronicle App Module1312, AI App Module1304, Third Party App Modules1344, Analytics App Module1306, and Machine Learning App Module1328. Social Media App(s)110connects to Social Media System106via Network(s)108. Social Media System106for User104utilizes Machine Learning System Modules828, Third Party System Modules844, Analytics System Modules806, AI System Modules804, and Chronicle System Modules812. Social Media System106and Social Media App(s)110also connect via Network(s)108to AI System236, Machine Learning System240, Analytics System238, Third Party Systems222, and Chronicle Systems206as well as any Platform Systems102. AI System236utilizes AI Platform System Modules1638. Machine Learning System240utilizes Machine Learning Platform System Modules1642. Analytics System238utilizes Analytics Platform System Modules1640. Third Party Systems222utilizes Third Party Platform System Modules1624. Chronicle System206utilizes Chronicle Platform System Modules1608. Social Media System106, Social Media App(s)110, and Platform Systems102may interact with Chronicle2100, Chronicle Record2000, Content Graph2024, and Publishable Content Types3700for data analysis. Additionally, Content Graph2024illustrates that Content2912, License2914, Copyright2916, Subject Headings2918, Subdivisions2920, Classification2922and Catalog2924nodes inFIG. 29can also be included in data analysis. Core Modules700are used for any cross-cutting concerns across Social Media App(s)110, Social Media System106, Platform Systems102, App Modules1300, System Modules800, Platform System Modules1600, as well as all functionality specific to Data Analysis4700.

FIG. 48is a block diagram of Trending4800which illustrates the trending functionality of the platform. Social Media System106-1for User104-1utilizes Analytics System Modules806and Chronicle System Modules812to generate Publisher Trending4802-1, Hashtag Trending4804-1, and Mention Trending4806-1. Social Media System106-2for User104-2utilizes Analytics System Modules806and Chronicle System Modules812to generate Publisher Trending4802-2, Hashtag Trending4804-2, and Mention Trending4806-2. Social Media System106-N for User104-N utilizes Analytics System Modules806and Chronicle System Modules812to generate Publisher Trending4802-N, Hashtag Trending4804-N, and Mention Trending4806-N. The ellipse between Social Media System106-2and Social Media System106-N illustrates that there are N number of social media systems for every user on the network. Social Media System106-1to Social Media System106-N connects to Platform Systems102via Network(s)108. Platform Systems102utilizes Analytics System238and Chronicle System206to generate Publisher Trending4802, Hashtag Trending4804, and Mention Trending4806. Social Media System106-1to Social Media System106-N and Platform Systems102may interact with Chronicle2100, Chronicle Record2000, Content Graph2024and Publishable Content Types3700for trending. Additionally, Content Graph2024illustrates that Content2912, License2914, Copyright2916, Subject Headings2918, Subdivisions2920, Classification2922and Catalog2924nodes inFIG. 29can also be included in trending. Core Modules700are used for any cross-cutting concerns for Social Media System106-1to Social Media System106-N, Platform Systems102, App Modules1300, System Modules800, and Platform System Modules1600as well as all trending functionality.

Given the distributed nature of the platform, every Social Media System106inFIG. 1is able to generate its own trending data, allowing for unique trending that is bottom up. All published content and their related Publishable Content Types3700can be used for trending analysis as well as the location of Social Media System106and any relevant metadata about Social Media System106's content. This approach is superior to current approaches because the algorithms that centralized social media networks utilize to determine content distribution skew the user's knowledge of and interaction with the content that the algorithms display to them as well as the content that is not displayed to them. Distributed Social Media Network300inFIG. 3enables users to view all of the content from all social media systems that they have a connection with, therefore users see all the content and have a choice about what content they want to interact with. This provides for a much more accurate trending analysis. Furthermore, since trending can be aggregated by combining trends from all social media systems in Distributed Social Media Network300inFIG. 3, the inherent flaw of trending feedback loop in existing trending technologies is mitigated. Current social media networks have demonstrated a bias in promoting trends that propagate “right” think and punish “wrong” think. They also use trending to suppress freedom of speech. With Trending4800, a true representation of user interaction with content is captured, and Chronicle2100inFIG. 21ensures Complete Transparency3604inFIG. 36.

FIG. 49is a block diagram of Audit and Archive4900which illustrates the audit and archive functionality of the platform. Social Media System106-1for User104-1utilizes Archive System Modules808, Audit System Modules810, and Chronicle System Modules812. Social Media System106-2for User104-2utilizes Archive System Modules808, Audit System Modules810, and Chronicle System Modules812. Social Media System106-N for User104-N utilizes Archive System Modules808, Audit System Modules810, and Chronicle System Modules812. The ellipse between Social Media System106-2and Social Media System106-N illustrates that there are N number of social media systems for every user on the network which connect via Network(s)108. Social Media System106-1to Social Media System106-N also connect to Platform Systems102, Public Auditors114, and Public Archivists116via Network(s)108. Platform Systems102utilizes Audit System204, Archive System202, and Chronicle System206. Social Media System106-1to Social Media System106-N and Platform Systems102may interact with Chronicle2100which contains Chronicle Record2000and Content Graph Collection2908for auditing and archiving. They also interact with Content2912which contains the properties Public Release Timestamp2956, Audit Release Timestamp2958, and Archive Release Timestamp2960. Core Modules700are used for any cross-cutting concerns for Social Media System106-1to Social Media System106-N, Platform Systems102, App Modules1300, System Modules800, and Platform System Modules1600, as well as all interactions and functionality with Public Auditors114and Public Archivists116.

Public Release Timestamp2956, Audit Release Timestamp2958, and Archive Release Timestamp2960are critical to this workflow because they are used to determine when content is released to public, released for auditing, and released for archiving by Platform Systems102via Audit System204and Archive System202as well as by Social Media System106-1to Social Media System106-N via Audit System Modules810and Archive System Modules808. When content is released to public, all social media systems on Distributed Social Media Network300inFIG. 3have access to the content. When content is released for audit, Public Auditors114can audit the content. When content is released for archive, Public Archivists116can archive the content.

During a public audit, each Chronicle Record2000and its Content Graph Collection2908are inspected and hashing calculations are verified. Since each Chronicle Record2000is fully traceable, all users associated with the content plus all additions and changes to the content are known. The calculated hashes contained therein lend immutability to each of the graphs and each property of the record. Published content is also released to Public Archivists116, such as governments, libraries, and religious organizations that used to be the keepers of important public information before the digital revolution. This creates a permanency to all content that is published on Distributed Social Media Network300inFIG. 3.

These unique features of embodiments of the present technology illustrate how Chronicle2100inFIG. 21is a source of record which can be used to instill integrity of data within the public trust. Published content that is traceable and immutable, confirmed by Public Auditors114and stored permanently with Public Archivists116outside of the platform, creates a level of transparency and accountability that is not possible with current social media networks.

FIG. 50is a block diagram of Chronicle Record2000which is comprised of Certified Email Graph5000. Certified Email Graph5000, which descends from Base Graph2050inFIG. 20, consists of Certified Email Graph Schema5002, Certified Email Graph Schema Version5004, Certified Email Graph Hash5006, and Certified Email Graph Signature5008. It also consists of Certified Email Graph Collection5010which contains Node(s)5012and Edge(s)5040. Node(s)5012consists of Certified Email5014. Certified Email5014has the properties Certified Email Id5060, Certified Email Timestamp5062, Email Timestamp5064, Email From Address5066, Email To Address5068, Email CC Address5070, Email Message5072, Certified Email Key5074, Email Hash5076, and Certified Email Verified5078. This diagram illustrates that email certification exists within Chronicle Record2000.

FIG. 51is a block diagram of Certified Email5100which illustrates the certified email functionality of the platform, specifically certifying the authenticity of an email from one user to another. Certified Email5100is comprised of Chronicle2100which contains Chronicle Record2000which consists of Certified Email Graph5000which contains Certified Email5014. It is also comprised of Certified Data5102which contains Certified Email Id5060and Certified Email Hash5108as well as Core Modules700which provides all the cross-cutting functionality for Certified Email5100. Social Media App(s)110-1for User104-1utilizes Message Board App Module1330, Payment App Module1334, and Certified Email App Module1356. Certified Email App Module1356utilizes Certified Data5102and Email Message5072. Email Message5072is associated to Source SMTP Server5104which is connected to Destination SMTP Server5106which is associated to Certified Data5102. Social Media System106-1for User104-1utilizes Chronicle System Modules812, Payment System Modules834, and Certified Email System Modules856. Certified Email System Modules856utilizes Certified Data5102. Social Media System106for Publisher3502utilizes Chronicle System Modules812, Payment System Modules834, and Certified Email System Modules856. Certified Email System Modules856utilizes Certified Data5102and Publisher Certified Email Address5110. User104-1's Social Media App(s)110-1and Social Media System106-1interface with Publisher3502's Social Media System106, Source SMTP Server5104, and Destination SMTP Server5106via Network(s)108.

User104-1uses their Social Media App(s)110-1and its connected Payment App Module1334and Certified Email App Module1356to arrange payment via Publisher3502's Social Media System106and its connected Payment System Modules834and Certified Email System Modules856. Once payment is arranged, Certified Email System Modules856generates Certified Email5014containing Certified Email Id5060inFIG. 50, Certified Email Timestamp5062inFIG. 50, and Email Timestamp5064inFIG. 50. Then it creates Certified Data5102with Certified Email Id5060inFIG. 50and calculates Certified Email Hash5108of Certified Email Id5060inFIG. 50, Certified Email Timestamp5062inFIG. 50, and Email Timestamp5064inFIG. 50. Certified Email System Modules856then sends Certified Email5014back to User104-1with Publisher Certified Email Address5110. User104-1then takes Certified Data5102and appends it to Email Message5072. User104-1adds Publisher Certified Email Address5110to the cc: or bcc: address of Email Message5072which is then sent to the destination email address(s) via the associated Source SMTP Server5104to Destination SMTP Server5106. Publisher3502's Certified Email System Modules856upon receiving the email, adds the email timestamp to Email Timestamp5064inFIG. 50, any email to addresses to Email To Address5068inFIG. 50, the email from address to Email From Address5066inFIG. 50, and any email cc: addresses to Email CC Address5070inFIG. 50. The email message data is added to Email Message5072. Certified Email Graph5000and its associated Chronicle Record2000onFIG. 50are then submitted for Consensus by Conference3800inFIG. 38and added to Chronicle2100.

FIG. 52is a block diagram of Chronicle Record2000which is comprised of Notary Graph5200. Notary Graph5200, which descends from Base Graph2050inFIG. 20, consists of Notary Graph Schema5202, Notary Graph Schema Version5204, Notary Graph Hash5206, and Notary Graph Signature5208. Notary Graph2200also consists of Notary Graph Collection5210which contains Node(s)5212and Edge(s)5240. Node(s)5212consists of Notary5214. Notary5214has the properties Notary Id5260, Notary Timestamp5262, Email Timestamp5064, First Party Email Address5266, Second Party Email Address5268, Email CC Address5070, Email Message5072, and Notary Key5274. This diagram illustrates that a notarized transaction exists within Chronicle Record2000.

FIG. 53is a block diagram of Notary Email5300which illustrates the notary services functionality of the platform. User104-1and User104-2are entering into an agreement and need the use of a notary service. Because chronicle records are immutable, traceable and part of the permanent public record, publishers can perform notary services over email. In one embodiment of the invention, the data is encrypted and not available for public access. In another embodiment of the invention, the data is not encrypted and available for public auditing and archiving.

Notary Email5300is comprised of Chronicle2100which contains Chronicle Record2000which consists of Notary Graph5200which contains the node Notary5214. Notary Email5300is also comprised of Notary Data5302which contains Notary Id5260and Notary Email Hash5310as well as Core Modules700which provides all the cross-cutting functionality for Notary Email5300. Social Media App(s)110-1for User104-1utilizes Message Board App Module1330, Payment App Module1334, and Notary App Module1354. Notary App Module1354utilizes Notary Data5302which is associated to transitional element5308which is associated to Email Message5072. Email Message5072is associated to Source SMTP Server5304which is connected to Destination SMTP Server5306which is associated to Notary Data5302. Social Media App(s)110-2for User104-2utilizes Message Board App Module1330, Payment App Module1334, and Notary App Module1354. Notary App Module1354utilizes Notary Data5302which is associated to Email Message5072. Email Message5072is associated to Source SMTP Server5304which is connected to Destination SMTP Server5306which is associated to Notary Data5302. Social Media System106for Publisher3502utilizes Chronicle System Modules812, Payment System Modules834, and Notary System Modules854. Notary System Modules854utilizes Notary Data5302and Publisher Notary Email Address5312. User104-1's Social Media App(s)110-1and User104-2's Social Media App(s)110-2interface with Publisher3502's Social Media System106, Source SMTP Server5104, and Destination SMTP Server5106via Network(s)108.

User104-1utilizes Payment App Module1334and Notary App Module1354to arrange payment with Publisher3502which utilizes Payment System Modules834and Notary System Modules854. After payment is made, User104-1uses Notary App Module1354to submit First Party Email Address5266inFIG. 52and Second Party Email Address5268inFIG. 52to Publisher3502via Notary System Modules854. Notary System Modules854then generates Chronicle Record2000, Notary Graph5200, and Notary5214consisting of Notary Id5260inFIG. 52, Notary Timestamp5262inFIG. 52, and Notary Key5274inFIG. 52. It also generates Notary Email Hash5310. Notary Data5302containing Notary Id5260and Notary Email Hash5310along with Publisher Notary Email Address5312is sent back to User104-1's Notary App Module1354. User104-1then takes Notary Data5302and appends Email Message5072via5308. Email Message5072contains the content of the email and any associated attachments such as executed documents. User104-1ensures that the “from” address on the email message is First Party Email Address5266inFIG. 52. User104-1puts Second Party Email Address5268inFIG. 52into the “to” address on the email message and Publisher Notary Email Address5312into Email CC Address5070inFIG. 50. The email is then sent via Source SMTP Server5304to Destination Server5306along with Notary Data5302appended to Email Message5072. Publisher3502upon receiving Email Message5072then appends the email message data and attachments to Email Message5072.

Publisher3502then submits Chronicle Record2000containing Notary Graph5200with the completed Notary5214node to Consensus by Conference3800inFIG. 38. Upon consensus, the first party and second party are both notified of the first party's notarization via Notary App Module1354or by email. Upon receiving the email confirming the notarization of the first party's content from Publisher3502, the second party arranges payment and proceeds to notarize their executed documents through the same process utilized by User104-1for notarization. After consensus is reached for User104-2's Chronicle Record2000, then the first party and second party are sent confirmation of notarization by Publisher3502and the process is complete. Chronicle2100contains two Chronicle Record2000, one for the first party and one for the second party as evidence of the notarization.

FIG. 54is a block diagram of Chronicle Record2000which is comprised of Rhetoric Graph5400. Rhetoric Graph5400, which descends from Base Graph2050inFIG. 20, consists of Rhetoric Graph Schema5402, Rhetoric Graph Schema Version5404, Rhetoric Graph Hash5406, and Rhetoric Graph Signature5408. It also consists of Rhetoric Graph Collection5410which contains Node(s)5412and Edge(s)5440. Node(s)5412consists of Rhetoric5414, Debate5416, Participant5418, Judge5420, and Prize5422. Edge(s)5440consists of Score5442and Award5444. Rhetoric5414consists of Rhetoric Id5460, Rhetoric Timestamp5462, Ethos5464, Pathos5466, and Logos5468. Debate5416consists of Debate Id5470, Debate Timestamp5472, Past5474, Present5476, and Future5478. This diagram illustrates that rhetoric exists within Chronicle Record2000.

FIG. 55is a block diagram of Rhetoric System Modules864which is comprised of Rhetoric System Module5500, Debate System Module5502, Participant System Module5504, Judge System Module5506, Prize System Module5508, Score System Module5510, and Award System Module5512. These system modules represent the functionality required for Social Media System106inFIG. 1to work with a rhetoric data set which consists of Chronicle Record2000along with Rhetoric Graph5400, State Graph2030and Content Graph2024inside Chronicle2100. All new rhetoric is stored in Chronicle Record2000, specifically in Rhetoric Graph5400, which is able to track state via State Graph2030and is associated to Content Graph2024. Rhetoric System Modules864also interacts with Core Modules700which provides all the cross-cutting functionality for Rhetoric System Modules864.

FIG. 56is a block diagram of Rhetoric5600which illustrates the rhetoric functionality of the platform. User104inFIG. 1has two options for responding to published content on Distributed Social Media Network300inFIG. 3. They can post comments to their connections and groups via Post3400inFIG. 34. This type of response is informal and can be deleted since the comments reside exclusively on User104's Social Media System106inFIG. 1. User104can also respond to published content by publishing Rhetoric3736inFIG. 37. This type of response is formal and can be recanted, but not deleted, as it becomes part of the permanent public record. Rhetoric must inform, persuade or motivate in a civil manner. No shit posting or trolling is allowed. Rhetoric is managed by publishers, which creates economies of scale and distributed monitoring at the micro level. This stands in stark contrast to what exists with centralized social media networks, namely ineffective use of AI, bots and cubicles full of millennials trying to monitor speech at the macro level.

Rhetoric5600is comprised of Chronicle2100which consists of Chronicle Record2000which contains Rhetoric Graph5400, State Graph2030and Content Graph2024. User104-1has Social Media App(s)110-1which utilizes Message Board App Module1330, Payment App Module1334, and Rhetoric App Module1364. User104-2has Social Media App(s)110-2which utilizes Message Board App Module1330, Payment App Module1334, and Rhetoric App Module1364. User104-N has Social Media App(s)110-N which utilizes Message Board App Module1330, Payment App Module1334, and Rhetoric App Module1364. The ellipse Social Media App(s)110-2and Social Media App(s)110-N illustrates that there are N number of social media apps for every user on the network. Social Media App(s)110-1, Social Media App(s)110-2, and Social Media App(s)110-N connect to Social Media System106for Publisher3502via Network(s)108. Social Media System106utilizes Chronicle System Modules812, Payment System Modules834, and Rhetoric System Modules864. Rhetoric5600is also comprised of Core Modules700which is used for any cross-cutting concerns across for Social Media App(s)110-1to Social Media App(s)110-N, Social Media System106, App Modules1300, System Modules800, and Platform System Modules1600as well as all rhetoric functionality.

This diagram illustrates how User104-1to User104-N to can connect to Publisher3502's Social Media System106to engage in rhetoric or debate that becomes part of the permanent public record via Chronicle2100. Publisher3502may or may not charge users to participate. The intention is to create a structure for civil discourse and further solve the problem of fake news in a unique way. Users have the opportunity to express points and counterpoints as well as actually document their points and counterpoints as part of their participation. All rhetoric is vetted by Publisher3502as part of Publish4400inFIG. 44, so sources matter. Users are not able to just throw out unsupported or unsubstantiated information. In another embodiment of the invention, Publisher3502can utilize gamification features and introduce Judge5420, Prize5422, Scoring5442and Awards5444inFIG. 54.

FIG. 57is a block diagram of Chronicle Record2000which is comprised of Subscription Graph5700. Subscription Graph5700, which descends from Base Graph2050inFIG. 20, consists of Subscription Graph Schema5702, Subscription Graph Schema Version5704, Subscription Graph Hash5706, and Subscription Graph Signature5708. It also consists of Subscription Graph Collection5710which contains Node(s)5712and Edge(s)5740. Node(s)5712consists of Subscription5714, Subscription Pricing5716, Subscription Payment5718, Content2912, and License2914. Edge(s)5740consists of Subscribes To5742. This diagram illustrates that subscriptions exist within Chronicle Record2000.

FIG. 58is a block diagram of Subscription System Modules842which is comprised of Subscription System Module5800and Pricing System Module5802. These system modules represent the functionality required for Social Media System106inFIG. 1to work with a subscription data set which consists of Chronicle Record2000along with Subscription Graph5700, Content Graph2024, and State Graph2030inside Chronicle2100. All new subscriptions are stored in Chronicle Record2000, specifically in Subscription Graph5700, which is able to track state via State Graph2030and is associated to Content Graph2024. Subscription System Modules842also interacts with Core Modules700which provides all the cross-cutting functionality for Subscription System Modules842.

FIG. 59is a block diagram of Subscription5900which illustrates the subscription functionality of the platform. Subscription5900is comprised of Chronicle2100which consists of Chronicle Record2000which contains Subscription Graph5700, Directory Graph2034, and State Graph2030. User104-1has Social Media App(s)110-1which utilizes Message Board App Module1330, Payment App Module1334, Subscription App Module1342, and Account App Module1370. User104-2has Social Media App(s)110-2which utilizes Message Board App Module1330, Payment App Module1334, Subscription App Module1342, and Account App Module1370. User104-N has Social Media App(s)110-N which utilizes Message Board App Module1330, Payment App Module1334, Subscription App Module1342, and Account App Module1370. The ellipse between Social Media App(s)110-2and Social Media App(s)110-N illustrates that there are N number of social media apps for every user on the network. Social Media App(s)110-1, Social Media App(s)110-2, and Social Media App(s)110-N connect to Social Media System106for Publisher3502via Network(s)108. Social Media System106utilizes Chronicle System Modules812, Payment System Modules834, Subscriptions System Modules842, Directory System Modules818, Account System Modules870, and Connection System Modules814. Subscription5900is also comprised of Core Modules700which are used for any cross-cutting concerns across Social Media App(s)110-1to Social Media App(s)110-N, Social Media System106, App Modules1300, System Modules800, and Platform System Modules1600as well as all subscription functionality.

Social Media App(s)110-1for User104-1utilizes Message Board App Module3404, Payment App Module1334, and Subscription App Module1342. Subscription App Module1342interfaces with Subscription System Modules842which provides subscription options and their prices to User104-1for Publisher3502. If User104-1decides they want a subscription, then Payment App Module1334interfaces with Payment System Modules834to make a payment to Publisher3502. Once payment is made, then Subscription System Modules842associates User104-1with access to paid content. The same goes for User104-2to User104-N.

This diagram illustrates that publishers can publish both free and paid content on Distributed Social Media Network300inFIG. 3. The platform provides a way for them to offer and manage subscriptions, consistent with Level Playing Field3610and Users Get Paid for their Content3628inFIG. 36. Struggling independent news organizations or content providers can actually run a business on the platform as they now have the technical infrastructure and support necessary to compete with centralized social media networks. This diagram also illustrates that not all chronicles have to go out to the public domain. They can be used for managing aspects of business functionality, like subscriptions, where a publisher needs to have a source of record.

FIG. 60is a block diagram of Chronicle Record2000which is comprised of Connection Graph6000. Connection Graph6000, which descends from Base Graph2050inFIG. 20, consists of Connection Graph Schema6002, Connection Graph Schema Version6004, Connection Graph Hash6006, and Connection Graph Signature6008. It also has Connection Graph Collection6010which contains Node(s)6012and Edge(s)6040. Node(s)6012consists of Connection6014and Group6016. Edge(s)6040consists of Member of6042. This diagram illustrates that connections exist within Chronicle Record2000.

FIG. 61is a block diagram of Connection System Modules814which is comprised of Connection System Module6100. This system module represents the functionality required for Social Media System106inFIG. 1to work with a connection data set which consists of Chronicle Record2000along with Connection Graph6000, Directory Graph2034, and State Graph2030inside Chronicle2100. All new connections are stored in Chronicle Record2000, specifically in Connection Graph6000, which is able to track state via State Graph2030and is associated to Directory Graph2034. Connection System Modules814also interacts with Core Modules700which provides all the cross-cutting functionality for Connection System Modules814.

FIG. 62is a block diagram of Connection6200which illustrates the connection functionality of the platform. Connection6200is comprised of Chronicle2100which consists of Chronicle Record2000which contains Connection Graph6000, Directory Graph2034, and State Graph2030. User104-1has Social Media App(s)110-1which utilizes Message Board App Module1330, Directory App Module1318, and Connection App Module1314. User104-2has Social Media App(s)110-2which utilizes Message Board App Module1330, Directory App Module1318, and Connection App Module1314. User104-N has Social Media App(s)110-N which utilizes Message Board App Module1330, Directory App Module1318, and Connection App Module1314. The ellipse between Social Media App(s)110-2and Social Media App(s)110-N illustrates that there are N number of social media apps for every user on the network. Social Media App(s)110-1, Social Media App(s)110-2, and Social Media App(s)110-N connect to Social Media System106for Publisher3502via Network(s)108. Social Media System106utilizes Chronicle System Modules812, Directory System Modules818, and Connection System Modules814. Connection6200is also comprised of Core Modules700which are used for any cross-cutting concerns across Social Media App(s)110-1to Social Media App(s)110-N, Social Media System106, App Modules1300, System Modules800, and Platform System Modules1600as well as all connection functionality.

This diagram illustrates how User104inFIG. 1can create connections, which are stored in Connection6014inFIG. 60. User104-1to User104-N uses Message Board App Module1330, Directory App Module1318, and Connection App Module1314to create connection requests. This workflow is further detailed in Connections and Groups4500inFIG. 45. Social Media System106using Directory System Modules818and Connection System Modules814for Publisher3502can also create connections. There are three use cases for creating connections: user to user, publisher to user, and user to publisher. The connection functionality of the platform is distinct and separate from directory, accounts, and subscriptions. Each function stands on its own with its own set of system modules and app modules. Connections are not stored in the platform's directory. Each User104inFIG. 1stores their connections in their own local Chronicle2100inFIG. 21on their own Social Media System106inFIG. 1. Users own and control all their connections, which means they can delete them at any time, as part of Distributed Social Media Network300inFIG. 3.

FIG. 63is a block diagram of Chronicle Record2000which is comprised of Ad Graph6300. Ad Graph6300, which descends from Base Graph2050inFIG. 20, consists of Ad Graph Schema6302, Ad Graph Schema Version6304, Ad Graph Hash6306, and Ad Graph Signature6308. It also has Ad Graph Collection6309which contains Node(s)6310and Edge(s)6340. Node(s)6310consists of Ad6312, Ad Campaign6314, Ad Performance6316, Content2912, State2610, Ad Purchase6318, Ad Feature6320, and Ad Category6322. Edge(s)6340consists of Ad Belongs To6342, Ad Metrix Of6344, and Ad Contains6346. Ad6312has the properties Ad Id6350, Ad Timestamp6352, Ad Subject6354, Ad Location6356, Ad Size6358, and Ad Cost6360. This diagram illustrates that ads exist within Chronicle Record2000.

FIG. 64is a block diagram of the properties of Ad Campaign6314and Ad Performance6316nodes introduced inFIG. 63. Ad Campaign6314has the properties Ad Campaign Id6470, Ad Campaign Timestamp6472, Ad Campaign Duration6474, Ad Campaign Reach6476, Ad Campaign Frequency6478, Ad Campaign Targets6480, Ad Campaign Rotation6482, and Ad Campaign Cost6484. Ad Performance6316has the properties Ad Performance Id6485, Ad Performance Timestamp6486, Ad Performance Impressions6488, Ad Performance Cost Per Impression6490, Ad Performance Click Thru Rate6492, Ad Performance Cost Per Click6494, Ad Performance Actions6496, Ad Performance Cost Per Action6498, and Ad Performance Return on Spend6499.

FIG. 65is a block diagram of Ad Algorithms6500which is comprised of Ad Campaign Frequency Algorithms6502, Ad Campaign Reach Algorithms6504, Ad Campaign Rotation Algorithms6506, Ad Performance Impression Algorithms6508, Ad Performance Click Thru Rate Algorithms6510, Ad Performance Action Algorithms6512, and Ad Performance Return on Spend Algorithms6514. Ad Algorithms6500is associated with Machine Learning System Modules828, AI System Modules804, Analytics System Modules806, Third Party System Modules844, and Core Modules700. Ad Categories6516includes Ad Machine Learning6518, Ad Features6520, and Ad Classifier6522. Ad Categories6516is associated with Machine Learning System Modules828. Chronicle2100includes Chronicle Record2000which consists of Connection Graph6000, Ad Graph6300, Content Graph2024, and State Graph2030. Chronicle2100is associated with Machine Learning System Modules828, AI System Modules804, Analytics System Modules806, Third Party System Modules844, and Ad Algorithms6500.

Ad Campaign Frequency Algorithms6502utilizes Ad Campaign Frequency6478inFIG. 64in conjunction with Machine Learning System Modules828and Ad Categories6516. Ad Campaign Reach Algorithms6504utilizes Ad Campaign Reach6476inFIG. 64in conjunction with Machine Learning System Modules828and Ad Categories6516. Ad Campaign Rotation Algorithms6506utilizes Ad Campaign Rotation6482inFIG. 64in conjunction with Machine Learning System Modules828and Ad Categories6516. Ad Performance Impression Algorithms6508utilizes Ad Performance Impressions6488and Ad Performance Cost Per Impression6490inFIG. 64in conjunction with Machine Learning System Modules828and Ad Categories6516. Ad Performance Click Thru Rate Algorithms6510utilizes Ad Performance Click Thru Rate6492and Ad Performance Cost Per Click6494inFIG. 64in conjunction with Machine Learning System Modules828and Ad Categories6516. Ad Performance Action Algorithms6512utilizes Ad Performance Actions6496and Ad Performance Cost Per Action6498inFIG. 64in conjunction with Machine Learning System Modules828and Ad Categories6516. Ad Performance Return on Spend Algorithms6514utilizes Ad Performance Return on Spend6499inFIG. 64in conjunction with Machine Learning System Modules828and Ad Categories6516.

Ad Algorithms6500could also work in conjunction with AI System Modules804, Analytics System Modules806, and Third Party System Modules844which may provide additional functionality that can be integrated into Ad Algorithms6500. Core Modules700provides the cross-cutting functionality for Ad Algorithms6500. In particular, all interactions with the elements inFIG. 65utilize Telemetry Core Module714, Logging Core Module710, and Exception Handling Core Module702inFIG. 7. Telemetry Core Module714inFIG. 7provides auditing insight into every interaction that can be audited and reported on vis-a-vis Audit System Modules810onFIG. 8. Machine Learning System Modules828utilizes Ad Categories6516consisting of Ad Machine Learning6518which is based on a training set of data containing instances whose features and assigned category membership is known, Ad Features6520which are derived from system composition profiles and their resulting performance metrics from telemetry data managed by Telemetry System226inFIG. 2, and Ad Classifier6522which is a classification algorithm that maps a new instance's system profile data to a category.

This diagram illustrates how machine learning and AI can be used at various touch points on Distributed Social Media Network300inFIG. 3. Here Machine Learning System Modules828utilizes Ad Algorithms6500, Chronicle2100, and Ad Categories6516to monitor and optimize ad performance on the platform. In another embodiment of the invention, Machine Learning System Modules828and AI System Modules804can be used to verify that ad content conforms to the agreements of the network and ad standards. In another embodiment of the invention, Machine Learning System Modules828and AI System Modules804can be used to add another dimensionality to ad analysis by looking at performance metrics across other populations, categories, and features. For example, assume User104publishes a circular flier for a small grocery co-op in Boise, Id. Because this co-op is in a certain population and category, its ad performance could be compared to those of a similarly sized grocery co-op in Portland, Oreg., giving User104a much more robust analysis as well as additional insights for ad optimization not currently available.

FIG. 66is a block diagram of Ad System Modules802which is comprised of Ad System Modules6600, Ad Campaign System Modules6602, Ad Performance System Module6604, Ad Purchase System Module6606, Ad Connection System Module6608, Ad State System Module6610, and Ad Content System Modules6612. Ad System Modules802interfaces with Platform Systems102, Chronicle2100, Ad Algorithms6500, and Core Modules700. Platform Systems102, which consists of Ad System248and Ad Platform System Modules1648, utilizes Chronicle2100as well as Ad Algorithms6500. Ad Algorithms6500interfaces with Ad System Modules802, Platform Systems102and Chronicle2100. Chronicle2100is comprised of Chronicle Record2000which consists of Connections Graph6000, Ad Graph6300, Content Graph2024and State Graph2030. Core Modules700is used for any cross-cutting concerns across Ad System Modules802and Platform Systems102. This diagram illustrates Ad System Modules802as it relates to Platform Systems102, Ad Algorithms6500, Core Modules700, and Chronicle2100.FIG. 66also illustrates Platform Systems102's relationship to Ad Algorithms6500, Chronicle2100, and Core Modules700.

FIG. 67is a block diagram of Ad6700which illustrates the ad functionality of the platform. Ad6700is comprised of Chronicle2100which consists of Chronicle Record2000which contains Connection Graph6000, Ad Graph6300, Content Graph2024, and State Graph2030. User104-1has Social Media App(s)110-1, User104-2has Social Media App(s)110-2, and User104-N has Social Media App(s)110-N, all of which utilize Message Board App Module1330to see ads. The ellipse between Social Media App(s)110-2and Social Media App(s)110-N illustrates that there are N number of social media apps for every user on the network. Social Media App(s)110-1, Social Media App(s)110-2, and Social Media App(s)110-N connect to Social Media System106for Publisher3502via Network(s)108. Social Media System106utilizes Chronicle System Modules812, Directory System Modules818, Connection System Modules814, Ad Algorithms6500, and Ad System Modules802. Ad6700is also comprised of Core Modules700which is used for any cross-cutting concerns across Social Media App(s)110-1to Social Media App(s)110-N, Social Media System106, App Modules1300, System Modules800, and Platform System Modules1600as well as all ad functionality.

This diagram shows that publishers are responsible for the advertising that appears on Distributed Social Media Network300inFIG. 3, and unlike existing centralized options, they keep the bulk of any ad revenue. The network makes the transaction between User104and Publisher3502possible with workflows that leverage Chronicle2100and select system modules to create, publish and pay for ads all through Social Media App(s)110. All ads run by the day. Most will be local or subject specific given the distributed nature of the network. The network will make a select number of ads available at the regional and national level, whereby some national placements will be available for delivery to 100% of users every day. In one embodiment of the invention, every user gets every ad that has been placed with a publisher that they are connected to. In another embodiment of the invention, Publisher3502can micro target ad content for User104.

FIG. 68is a block diagram of Ad Purchase6800which illustrates the ad purchase functionality of the platform. Ad Purchase6800is comprised of Chronicle2100which consists of Chronicle Record2000which contains Connection Graph6000, Ad Graph6300, Content Graph2024, and State Graph2030. User104-1has Social Media App(s)110-1which utilizes Message Board App Modules1330, Ad App Module1302, and Payment App Module1334to purchase an ad to run with Publisher3502. Publisher3502has Social Media System106which utilizes Ad System Modules802, Payment System Modules834, Connection System Modules814, and Chronicle System Modules812to accept payment for User104's ad. Publisher3502also has Social Media App(s)110, which utilizes Message Board App Module1330and Ad App Module1302to manage ads. Publisher3502's Social Media System106connects to their Social Media App(s)110and User104-1's Social Media App110-1via Network(s)108. Ad Purchase6800is also comprised of Core Modules700which is used for any cross-cutting concerns across Social Media App(s)110, Social Media App(s)110-1, Social Media System106, App Modules1300, System Modules800, and Platform System Modules1600as well as all ad purchase functionality.

This diagram shows how User104-1can purchase an ad from any Publisher3502they select on Distributed Social Media Network300inFIG. 3. Both parties work inside their own social media app(s) to facilitate the ad purchase, and Publisher3502uses select system modules and Chronicle2100to manage the process. In another embodiment of the invention, User104calls or emails Publisher3502to make an ad purchase.

FIG. 69is a block diagram of Ad Distribution6900which illustrates the ad distribution functionality of the platform. User104-1has Social Media App(s)110-1, User104-2has Social Media App(s)110-2, and User104-N has Social Media App(s)110-N, all of which utilize Message Board App Module1330. The ellipse between Social Media App(s)110-2and Social Media App(s)110-N illustrates that there are N number of social media apps for every user on the network. Social Media App(s)110-1, Social Media App(s)110-2, and Social Media App(s)110-N connect to Social Media System106for Publisher3502via Network(s)108. Social Media System106utilizes Chronicle System Modules812, Directory System Modules818, Connection System Modules814, Ad Algorithms6500, and Ad System Modules802. Ad Distribution6900is also comprised of Distribution System Modules820which consists of Distribution System Module3100, Distribution Event Grid Module3102, and Distribution Notification Hub Module3106. Distribution Event Grid Module3102is connected to Distribution Event Grid3104. Distribution Notification Hub Module3106is connected to Distribution Notification Hub3108. Distribution System Modules820interacts with Chronicle2100as well as Core Modules700which provides all the cross-cutting functionality for Distribution System Modules820. Core Modules700is also used for any cross-cutting concerns across Social Media App(s)110-1to Social Media App(s)110-N and Social Media System106. This diagram shows that ads (new content plus any state changes) can be distributed across Distributed Social Media Network300inFIG. 3using both pull and push techniques as detailed inFIG. 31.

FIG. 70is a block diagram of Chronicle Collection7000which is comprised of Chronicle2100and Annals2200. Chronicle2100consists of Chronicle Record2120-1, Chronicle Record2120-2, and Chronicle Record2120-N. The ellipse between Chronicle Record2120-1and Chronicle Record2120-N indicates that there are N number of chronicle records in Chronicle2100. Annals2200consists of Chronicle2020-1, Chronicle2020-2, and Chronicle2020-N. The ellipse between Chronicle2020-2and Chronicle2020-N indicates that there are N number of chronicles in Annals2200. Platform Systems102is comprised of Chronicle System206. Platform System Modules1600is comprised of Chronicle Platform System Modules1608which consists of Chronicle Aggregation Platform System Module2300, Chronicle Archive Platform System Module2302, Chronicle Audit Platform System Modules2304, and Chronicle Management Module2306. System Modules800is comprised of Chronicle System Modules812. This diagram illustrates how Platform Systems102, System Modules800, and Platform System Modules1600interface with Chronicle Collection7000.

FIG. 71is a block diagram of Chronicle Record2000which is comprised of User Verification Graph7100. User Verification Graph7100, which descends from Base Graph2050inFIG. 20, consists of User Verification Graph Schema7102, User Verification Graph Schema Version7104, User Verification Graph Hash7106, and User Verification Graph Signature7108. It also consists of User Verification Graph Collection7110which contains Node(s)7112and Edge(s)7140. Node(s)7112consists of User Verification7114, User Verification Feature7116, User Verification Category7118, User Verification Purchase7120, State2610, and Connection6014. Edge(s)7140consists of User Verification Probability7142. User Verification7114has the properties User Verification Id7150, User Verification Timestamp7152, and User Verification Cost7154. This diagram illustrates that user verification exists within Chronicle Record2000.

FIG. 72is a block diagram of Chronicle Record2000which is comprised of User Verification Features7200. User Verification Features7200consists of Password Confirmation by Email7202,2FA Enabled7204, Email Source7206, Device Type7208, Device Count7210, Mobile Network7212, Verification Location Match7214, Verification Purchase7216, Verification Payment Method7218, ACH Authorization Verification7220, In-Person Verification7222, In-Person Verification Id Type7224, In-Person Verification Id Check7226, In-Person Verification Photo Taken7228, SSN Verification7230, EIN Verification7232, Credit Soft Inquiry7234, and Background Check7236. All users on the platform must be verified for their safety as well as for the integrity of Distributed Social Media Network300inFIG. 3. This diagram details the User Verification Features7200used by Machine Learning System Modules828inFIG. 8to verify users. User104inFIG. 1has a number of ways that they can prove they are who they say they are. They are able to choose how they want to be verified and at what expense. The platform aims to significantly increase the probability that User104is who they say they are before making all platform functionality available for use. For example, the bar required to Post3400inFIG. 34is not as high as it is to Publish4400inFIG. 44.

FIG. 73is a block diagram of User Verification Algorithms7300which contains User Verification Identity Algorithms7302, User Verification Device Algorithms7304, User Verification Network Algorithms7306, User Verification Financial Algorithms7308, User Verification In-Person Algorithms7310, and User Verification Credit and Background Algorithms7312. User Verification Algorithms7300is associated with Machine Learning System Modules828, AI System Modules804, Analytics System Modules806, Third Party System Modules844, and Core Modules700. User Verification Categories7314includes User Verification Machine Learning7316, User Verification Feature7200, and User Verification Classifier7320. User Verification Categories7314is associated with Machine Learning System Modules828. Chronicle2100includes Chronicle Record2000which consists of Connection Graph6000, User Verification Graph7100, Directory Graph2034, and State Graph2030. Chronicle2100is associated with Machine Learning System Modules828, AI System Modules804, Analytics System Modules806, Third Party System Modules844, and User Verification Algorithms7300.

User Verification Identity Algorithms7302utilizes Password Confirmation by Email7202,2FA Enabled7204, and Email Source7206features inFIG. 72. It is intended to be used with features involving identity and data around authentication and authorization for user verification in conjunction with Machine Learning System Modules828and User Verification Categories7314. User Verification Device Algorithms7304utilizes Device Type7208and Device Count7210features inFIG. 72. It is intended to be used with features involving device(s) related data in conjunction with Machine Learning System Modules828and User Verification Categories7314. User Verification Network Algorithms7306utilizes Mobile Network7212and Verification Location Match7214features inFIG. 72. It is intended to be used with features involving network related data in conjunction with Machine Learning System Modules828and User Verification Categories7314. User Verification Financial Algorithms7308utilizes Verification Purchase7216, Verification Payment Method7218, and ACH Authorization Verification7220features inFIG. 72. It is intended to be used with features involving financial related data in conjunction with Machine Learning System Modules828and User Verification Categories7314. User Verification In-Person Algorithm7310utilizes In-Person Verification7222, In-Person Verification Id Type7224, In-Person Verification Id Check7226, and In-Person Verification Photo Taken7228features inFIG. 72. It is intended to be used with features involving in-person related data in conjunction with Machine Learning System Modules828and User Verification Categories7314. This data is collected when User104inFIG. 1goes to Publisher3502inFIG. 35and gets verified by them in person. User Verification Credit and Background Algorithms7312utilizes SSN Verification7230, EIN Verification7232, Credit Soft Inquiry7234, and Background Check7236features inFIG. 72. It is intended to be used with features involving credit and background related data in conjunction with Machine Learning System Modules828and User Verification Categories7314.

User Verification Algorithms7300could also work in conjunction with AI System Modules804, Analytics System Modules806, and Third Party System Modules844which may provide additional user verification systems or functionality that can be integrated into User Verification Algorithms7300. Core Modules700provides the cross-cutting functionality for User Verification Algorithms7300. In particular, all interactions with the elements inFIG. 73utilize Telemetry Core Module714, Logging Core Module710, and Exception Handling Core Module702inFIG. 7. Telemetry Core Module714inFIG. 7provides auditing insight into every interaction that can be audited and reported on vis-a-vis Audit System Modules810onFIG. 8. Machine Learning System Modules828utilizes User Verification Categories7314consisting of User Verification Machine Learning7316which is based on a training set of data containing instances whose features and assigned category membership is known, User Verification Features7200which are derived from system composition profiles and their resulting performance metrics from telemetry data managed by Telemetry System226inFIG. 2, and User Verification Classifier7320which is a classification algorithm that maps a new instance's system profile data to a category.

This diagram illustrates how Machine Learning System Modules828looks at User Verification Features7200inFIG. 72, puts weight on different features, creates probability for authenticity of user verification, and put User104inFIG. 1into User Verification Classifier7320regarding identity. Existing centralized social media networks have very flat onboarding experiences. Various embodiments of the present technology are very dynamic. Depending on what path User104inFIG. 1chooses to take, there is a higher probability of user verification. The platform also has User104inFIG. 1re-verify at different times (e.g. annually) since it is critical that Users are Known3624and Users are Verified3626inFIG. 36to maintain user safety and network integrity. Because Publisher3502inFIG. 35can verify users as part of Distributed Social Media Network300inFIG. 3, there are economies of scale and increased probability of accuracy not possible with central authorities.

FIG. 74is a block diagram of User Verification System Modules866which is comprised of User Verification System Module7400, User Verification Features System Module7402, User Verification Category System Module7404, User Verification Purchase System Module7406, User Verification Connection System Module7408, User Verification State System Module7410, User Verification Content System Module7412, and User Verification Probability System Module7414. User Verification System Modules866interfaces with Platform Systems102, Chronicle2100, User Verification Algorithms7300, and Core Modules700. Platform Systems102, which consists of User Verification System228and User Verification Platform System Modules1630, utilizes Chronicle2100as well as User Verification Algorithms7300. User Verification Algorithms7300interfaces with User Verification System Modules866, Platform Systems102, and Chronicle2100. Chronicle2100is comprised of Chronicle Record2000which consists of Connection Graph6000, User Verification Graph7100, Directory Graph2034, and State Graph2030. Core Modules700is used for any cross-cutting concerns across Verification System Modules866and Platform Systems102. This diagram illustrates User Verification System Modules866as it relates to Platform Systems102, User Verification Algorithms7300, Core Modules700, and Chronicle2100.FIG. 74also illustrates Platform Systems102's relationship to User Verification Algorithms7300, Chronicle2100, and Core Modules700.

FIG. 75is a block diagram of User Verification7500which illustrates the user verification functionality of the platform. User Verification7500is comprised of Chronicle2100which consists of Chronicle Record2000which contains Connection Graph6000, User Verification Graph7100, and State Graph2030. Platform Systems102utilizes Chronicle System Modules812, User Verification System Modules866, User Verification System228, and User Verification Platform System Modules1630. Platform Systems102connects to Social Media System106-1for User104-1, Social Media System106-2for User104-2, and Social Media System106-N for User104-N via Network(s)108. User104-1's Social Media System106-1utilizes Chronicle System Modules812, User Verification System Modules866, and Connection System Modules814. User104-2's Social Media System106-2utilizes Chronicle System Modules812, User Verification System Modules866, and Connection System Modules814. User104-N's Social Media System106-N utilizes Chronicle System Modules812, User Verification System Modules866, and Connection System Modules814. The ellipse between Social Media System106-2and Social Media System106-N illustrates that there are N number of social media systems for every user on the network. User Verification7500is also comprised of Core Modules700which are used for any cross-cutting concerns across Platform Systems102, Social Media System106-1to Social Media System106-N, App Modules1300, System Modules800, and Platform System Modules1600as well as all user verification functionality.

This diagram illustrates how User Verification System Modules866is utilized by Platform Systems102and all social media systems on Distributed Social Media Network300inFIG. 3for user verification. Any other System Modules800can also be used in conjunction with User Verification System Modules866if appropriate to facilitate various workflows, such as Onboarding System Modules832, Payment System Modules834, or Subscription System Modules842inFIG. 8.

FIG. 76is a block diagram of Chronicle Record2000which is comprised of Trending Graph7600. Trending Graph7600, which descends from Base Graph2050inFIG. 20, consists of Trending Graph Schema7602, Trending Graph Schema Version7604, Trending Graph Hash7606, and Trending Graph Signature7608. It also consists of a Trending Graph Collection7610which contains Node(s)7612and Edge(s)7640. Node(s)7612consists of Trend Billboard7614and Content2912. This diagram illustrates that trending information exists within Chronicle Record2000.

FIG. 77is a block diagram that illustrates Trending System Modules868and its relationship to Platform Systems102, Trending4800, Core Modules700and Chronicle2100. Trending System Modules868consists of Trending System Module7700and Trending Billboard System Module7702. Platform Systems102consists of Trending System244and Trending Platform System Modules1644. Trending4800consists of Publisher Trending4802, Mention Trending4806, Hashtag Trending4804, and Publishable Content Types3700. Chronicle2100consists of Chronicle Record2000, which contains Directory Graph2034, Content Graph2024, Trending Graph7600, State Graph2030, and Connection Graph6000. Trending System Modules868interfaces with Platform Systems102, Chronicle2100, Trending4800, and Core Modules700. Platform Systems102utilizes Chronicle2100, Trending4800, and Core Modules700. Trending4800interfaces with Trending System Modules868and Platform Systems102. Core Modules700is used for any cross-cutting concerns across Trending System Modules868and Platform Systems102.

FIG. 78is a block diagram of Trending Billboard7800which illustrates the trending billboard functionality of the platform. Trending Billboard7800is comprised of Chronicle2100which consists of Chronicle Record2000which contains Directory Graph2034, Content Graph2024, Trending Graph7600, State Graph2030, and Connection Graph6000. Platform Systems102utilizes Chronicle System Modules812, Trending System Modules868, and Trending Billboard7802. Platform Systems102connects to Social Media System106-1for User104-1, Social Media System106-2for User104-2, Social Media System106-N for User104-N via Network(s)108. User104-1's Social Media System106-1utilizes Chronicle System Modules812, Trending System Modules868, and Trending Billboard7802-1. User104-2's Social Media System106-2utilizes Chronicle System Modules812, Trending System Modules868, and Trending Billboard7802-2. User104-N's Social Media System106-N utilizes Chronicle System Modules812, Trending System Modules868, and Trending Billboard7802-N. The ellipse between Social Media System106-2and Social Media System106-N illustrates that there are N number of social media systems for every user on the network. Trending Billboard7800is also comprised of Core Modules700which provides the cross-cutting functionality for Platform Systems102, Social Media System106-1to Social Media System106-N, App Modules1300, System Modules800, and Platform System Modules1600as well as all trending billboard functionality.

All of the trending functionality ofFIG. 78builds on the trending functionality detailed inFIG. 48. This diagram shows that Trending Billboard7800is essentially a roll up of the trending for each Social Media System106as well as for Platform System102, which represents a complete aggregation of all trending across Distributed Social Media Network300inFIG. 3. Each trending Billboard7802lives in Chronicle2100. The platform will provide pre-canned trends for each day as well as unique tools that give User104the ability to find and consume trending data that is important to them. There is no algorithm, such as those utilized within existing centralized social media networks, that tells User104what they are interested in or provides trends that are skewed or biased based on some complex promotional scheme. Instead User104gets to explore the content for themselves and see what is trending across multiple domains such as the content metadata detailed inFIG. 29, the type of content or publisher detailed inFIG. 37, and location (city, state, region, national, global). So not only does User104own and control their content, they can actually consume it in unique and customized ways.

FIG. 79is a block diagram of Chronicle Record2000which is comprised of Endorsement Graph7900. Endorsement Graph7900, which descends from Base Graph2050inFIG. 20, consists of Endorsement Graph Schema7902, Endorsement Graph Schema Version7904, Endorsement Graph Hash7906, and Endorsement Graph Signature7908. It also consists of Endorsement Graph Collection7910which contains Node(s)7912and Edge(s)7940. Node(s)7912consists of Endorsement7914, Content2912, State2610, and Connection6014. This diagram illustrates that endorsements exist within Chronicle Record2000.

FIG. 80is a block diagram of Endorsement System Modules848which is comprised of Endorsement System Module8000. Endorsement System Modules848interfaces with Platform Systems102, Chronicle2100, and Core Modules700. Platform Systems102, which consists of Endorsement System246and Endorsement Platform System Modules1646, utilizes Chronicle2100and Core Modules700. Chronicle2100is comprised of Chronicle Record2000which consists of Directory Graph2034, Content Graph2024, Endorsement Graph7790, State Graph2030, and Connection Graph6000. Core Modules700is used for any cross-cutting concerns across Endorsement System Modules848and Platform Systems102. This diagram illustrates Endorsement System Modules848as it relates to Platform Systems102, Core Modules700, and Chronicle2100.FIG. 80also illustrates Platform Systems102's relationship to Chronicle2100and Core Modules700.

FIG. 81is a block diagram of Endorsement8100which illustrates the endorsement functionality of the platform. Endorsement8100is comprised of Chronicle2100which consists of Chronicle Record2000which contains Directory Graph2034, Content Graph2024, Endorsement Graph7900, State Graph2030, and Connection Graph6000. Platform Systems102utilizes Chronicle System Modules812, Endorsement Platform System Modules1646, and Endorsed Content8102. Platform Systems102connects to Social Media System106-1for User104-1, Social Media System106-2for User104-2, Social Media System106-N for User104-N via Network(s)108. User104-1's Social Media System106-1utilizes Chronicle System Modules812, Endorsement System Modules848, and Endorsed Content8102-1. User104-2's Social Media System106-2utilizes Chronicle System Modules812, Endorsement System Modules870, and Endorsed Content8102-2. User104-N's Social Media System106-N utilizes Chronicle System Modules812, Endorsement System Modules848, and Endorsed Content8102-N. The ellipse between Social Media System106-2and Social Media System106-N illustrates that there are N number of social media systems for every user on the network. Endorsement8100is also comprised of Endorsement Engine8104and Core Modules700which provides the cross-cutting functionality for Platform Systems102, Social Media System106-1to Social Media System106-N, App Modules1300, System Modules800, and Platform System Modules1600as well as all endorsement functionality.

This diagram illustrates that every Social Media System106has the ability to generate endorsed content for Distributed Social Media Network300inFIG. 3. All content, including ads, can be endorsed. In one embodiment of the invention, endorsements are free. One sample use case is an Editorial/Opinion3720inFIG. 37that is endorsed by academics or politicians who want to lend their name to the notion expressed in the content. In another embodiment of the invention, endorsements are paid for utilizing Payment System Modules834and Payment App Module1334. One sample use case is a content producer who uses Endorsement Engine8104to have their content matched with celebrities, noted sports figures, etc. who want to be paid for their endorsement. Note that an endorsement that appears inside of a message as Endorsed Content8102is different from Display Ads3718as a Publishable Content Type3700inFIG. 37. Various embodiments of the present technology support both.

FIG. 82is a block diagram of Certified Business Email8200which illustrates the business certified email functionality of the platform. Business Certified Email8200is comprised of Chronicle2100which contains Chronicle Record2000which consists of Certified Email Graph5000which contains Certified Email5014. It is also comprised of Certified Data5102which contains Certified Email Id5060and Certified Email Hash5108.FIG. 82also contains the Publisher Email Address8206and Core Modules700which provides all the cross-cutting functionality for Business Certified Email8200. Social Media System106-1for User104-1utilizes Chronicle System Modules812, Payment System Modules834, and Certified Email System Modules856. Certified Email System Modules856utilizes Certified Data5102. Email Message5072is associated to Source SMTP Server5104and Destination SMTP Server5106. Social Media System106-2for User104-2utilizes Chronicle System Modules812, Payment System Modules834, and Certified Email System Modules856. Certified Email System Modules856utilizes Certified Data5102. Social Media System106for Publisher3502utilizes Chronicle System Modules812, Payment System Modules834, and Certified Email System Modules856. Certified Email System Modules856utilizes Certified Data5102and Publisher Certified Email Address8240. User104-1's Social Media System106-1and User104-2's Social Media System106-2interface with Publisher3502's Social Media System106, Source SMTP Server5104, and Destination SMTP Server5106via Network(s)108.

Business Certified Email8200inFIG. 82illustrates how Certified Email System Modules856integrate with SMTP to facilitate secure email exchanges for business so that source email addresses, content and attachments are captured as an immutable, traceable hash that enable recipients to verify email sources, content and attachments, and thereby thwart email security hazards such as viruses, trojan horses, phishing, spear-fishing, etc. Business Certified Email8200verified email reduces security risks inherent with emails containing malicious URI and attachments.

Certified Email System Modules856for Social Media System106-1integrates with Source SMTP Server5104to capture outgoing email messages. Once an email is captured, a Merkle root is calculated from the email addresses, content and attachments. The Merkle root, email timestamp, from address, to addresses, cc addresses are sent to the Certified Email System Modules856for the Publisher3502which creates a Certified Email5014node fromFIG. 50for a new Chronicle Record2000.

The Merkle root is stored in Email Hash5076, email timestamp is stored in Email Timestamp5064, from address is stored in Email From Address5066, to addresses is stored in Email To Address5068, and cc addresses is stored in Email CC Address5070of Certified Email5014.

Certified Email Timestamp5062, Certified Email Id5060, and Certified Email Key5074are then generated and stored in Certified Email5014. Certified Email Hash5108is a Merkle root generated from Certified Email5014properties. Certified Data5102containing Certified Email Id5060and Certified Email Hash5108are then sent back to Certified Email System Modules856for the User104-1. Certified Data5102and Publisher Email Address8206are added to outgoing email messages as the final processing step before being sent.

Upon receipt of the email, Certified Email System Modules856for Publisher3502utilizes Certified Data5102to locate Chronicle Record2000, and then encrypts and stores the email to the Email Message5072property of Certified Email5014. Certified Email System Modules856then calculates a Merkle root from the received email addresses, content and attachments. The hash value is used to verify the stored value in the Email Hash5076property of Certified Email5014. The verification result is stored in the Certified Email Verified5078property of Certified Email5014.

Upon receipt of the email, Certified Email System Modules856for the User104-2associated with Destination SMTP Server5106, intercepts the incoming email, removes the Certified Data5102data and calculates a Merkle root from the received email addresses, content, and attachments. The resulting hash, Certified Email Id5060, and Certified Email Hash5108is then sent to Certified Email System Modules856for Publisher3502to certify the email.

Upon determining the certification results, Certified Email System Modules856for Publisher3502returns Certified Email Verified5078to Certified Email System Modules856for User104-2. If Certified Email Verified5078is true, then the email is delivered to the recipients, else it is sent to a “hazard” email box for further processing or inspection.

In one embodiment of the invention Certified Email System Modules856is a proxy server for Source SMTP Server5104and Destination SMTP Server5106. In another embodiment of the invention, Certified Email System Modules856is integrated into Source SMTP Server5104and Destination SMTP Server5106.

Payment System Modules834for Publisher3502, User104-1and User104-2can be used to setup payments for certified email processing. Core Modules700provides all cross-cutting functions for systems and system modules.

FIG. 83is a block diagram of Chronicle Record2000which is comprised of Content Verification Graph8300. Content Verification Graph8300, which descends from Base Graph2050inFIG. 20, consists of Content Verification Graph Schema8302, Content Verification Graph Schema Version8304, Content Verification Graph Hash8306, and Content Verification Graph Signature8308. It also consists of Content Verification Graph Collection8310which contains Node(s)8312and Edge(s)8340. Node(s)8312consists of Content Verification8314, Content Verification Feature8316, Content Verification Category8318, State2610, and Connection6014. Edge(s)8340consists of Content Verification Probability8342. Content Verification8314has the properties Content Verification Id8350and Content Verification Timestamp8352. This diagram illustrates that content verification exists within Chronicle Record2000.

FIG. 84is a block diagram of Chronicle Record2000which is comprised of Content Verification Features8400. Content Verification Features8400consists of Content Type8402, Content Meta Data8404, Source Location8406, Content Size8408, Associated Content8410, Content Source Frequency8412, Content Device8414, Content Filter Scan8416, Video Sound Analysis8418, Video Text Analysis8420, Video Object Analysis8422, Video Subject Analysis8424, Picture Text Analysis8426, Picture Object Analysis8428, Picture Subject Analysis8430, Source Hash Analysis8432, Text Subject Analysis8434, and Text Key Word Analysis8436.

This diagram details the Content Verification Features8400used by Machine Learning System Modules828inFIG. 8to verify content. Content Type8402is the type of content. Content Meta Data8404is the content metadata. Source Location8406is where the content originates from, specifically what device plus the location metadata on the content. Content Size8408is the content size. Associated Content8410is what other content is submitted with the content in question. Content Source Frequency8412is how frequently the source is submitting content. Content Device8414is the kind of device the content originated from. Content Filter Scan8416is a scan of text, looking for key words that might require flagging. Video Sound Analysis8418is analysis of video sound. Video Text Analysis8420is analysis of video text. Video Object Analysis8422is analysis of video objects. Video Subject Analysis8424is analysis of video subject. Picture Text Analysis8426is analysis of picture text. Picture Object Analysis8428is analysis of picture objects. Picture Subject Analysis8430is analysis of picture subjects. Source Hash Analysis8432is analysis of source hash and searching for same hash for known offensive or illegal material. Text Subject Analysis8434is analysis of text subject. Text Key Word Analysis8436is analysis of text key words.

FIG. 85is a block diagram of Content Verification Algorithms8500which contains Content Verification Source Algorithms8502, Content Verification Context Algorithms8504, Content Verification Meta Data Algorithms8506, Content Verification Video Algorithms8508, Content Verification Picture Algorithms8510, and Content Verification Text Algorithms8512. Content Verification Algorithms8500is associated with Machine Learning System Modules828, AI System Modules804, Analytics System Modules806, Third Party System Modules844, and Core Modules700. Content Verification Categories8514includes Content Verification Machine Learning8516, Content Verification Features8400, and Content Verification Classifier8520. Content Verification Categories8514is associated with Machine Learning System Modules828. Chronicle2100includes Chronicle Record2000which consists of Connection Graph6000, Content Verification Graph8300, Directory Graph2034, and State Graph2030. Chronicle2100is associated with Machine Learning System Modules828, AI System Modules804, Analytics System Modules806, Third Party System Modules844, and Content Verification Algorithms8500.

Content Verification Algorithms8500utilizes Content Verification Features8400inFIG. 84. It is intended to be used with features involving source, context, metadata, video, picture and text related data in conjunction with Machine Learning System Modules828and Content Verification Categories8514. Content Verification Algorithms8500could also work in conjunction with AI System Modules804, Analytics System Modules806, and Third Party System Modules844which may provide additional content verification systems or functionality that can be integrated into Content Verification Algorithms8500. Core Modules700provides the cross-cutting functionality for Content Verification Algorithms8500. In particular, all interactions with the elements inFIG. 85utilize Telemetry Core Module714, Logging Core Module710, and Exception Handling Core Module702inFIG. 7. Telemetry Core Module714inFIG. 7provides auditing insight into every interaction that can be audited and reported on vis-a-vis Audit System Modules810onFIG. 8. Machine Learning System Modules828utilizes Content Verification Categories8514consisting of Content Verification Machine Learning8516which is based on a training set of data containing instances whose features and assigned category membership is known, Content Verification Features8400which are derived from system composition profiles and their resulting performance metrics from telemetry data managed by Telemetry System226inFIG. 2, and Content Verification Classifier8520which is a classification algorithm that maps a new instance's system profile data to a category.

This diagram illustrates how Machine Learning System Modules828looks at Content Verification Features8400inFIG. 84, puts weight on different features, creates probability for authenticity of content verification, and puts the content in question into Content Verification Classifier8520.

FIG. 86is a block diagram of Content Verification System Modules872which is comprised of Content Verification System Module8600, Content Verification Features System Module8602, Content Verification Category System Module8604, Content Verification Connection System Module8608, Content Verification State System Module8610, Content Verification Content System Module8612, and Content Verification Probability System Module8614. Content Verification System Modules872interfaces with Platform Systems102, Chronicle2100, Content Verification Algorithms8500, and Core Modules700. Platform Systems102, which consists of Content Verification System250and Content Verification Platform System Modules1650, utilizes Chronicle2100as well as Content Verification Algorithms8500. Content Verification Algorithms8500interfaces with Content Verification System Modules872, Platform Systems102, and Chronicle2100. Chronicle2100is comprised of Chronicle Record2000which consists of Connection Graph6000, Content Verification Graph8300, Directory Graph2034, and State Graph2030. Core Modules700provides all the cross-cutting functionality for Content Verification System Modules872and Platform Systems102. This diagram illustrates Content Verification System Modules802as it relates to Platform Systems102, Content Verification Algorithms8500, Core Modules700, and Chronicle2100.FIG. 86also illustrates Platform Systems102's relationship to Content Verification Algorithms8500, Chronicle2100, and Core Modules700.

FIG. 87is a block diagram of Content Verification8700which illustrates the content verification functionality of the platform. Content Verification8700is comprised of Chronicle2100which consists of Chronicle Record2000which contains Connection Graph6000, Content Verification Graph8300, and State Graph2030. Platform Systems102utilizes Chronicle System Modules812, Content Verification System Modules872, Content Verification System250, and Content Verification Platform System Modules1650. Platform Systems102connects to Social Media System106-1for User104and Social Media System106-2for Publisher3502via Network(s)108. User104's Social Media System106-1utilizes Chronicle System Modules812, Content Verification System Modules872, and Connection System Modules814. Social Media System106-1connects to Post3400. Publisher3502's Social Media System106-2utilizes Chronicle System Modules812, Content Verification System Modules872, and Connection System Modules814. Social Media System106-2connects to Publish4000. Content Verification8700is also comprised of Core Modules700which are used for any cross-cutting concerns across Platform Systems102, Social Media System106-1, Social Media System106-2, App Modules1300, System Modules800, and Platform System Modules1600as well as all content verification functionality.

This diagram illustrates that all content on Distributed Social Media Network300inFIG. 3, whether posted or published, goes through Content Verification System Module872and Content Verification Platform System Modules1650for verification before distribution. Every Chronicle Record2000and its associated Connection Graph6000, Content Verification Graph8300, and State Graph2030are inspected to ensure the content meets with network terms of service, including compliance with state and federal laws, as well journalistic or ad standards. If content is rejected for posting, User104can be notified via Content Verification App Module1372working in conjunction with Message Board App Module1330. If content is flagged before publishing, Publisher3502can use Content Verification App Module1372inFIG. 13to actually inspect the flagged content and either inform User104that the content has been edited and needs to be re-submitted or that the content has been rejected. Publisher3502can also use Third Party System Modules844to integrate third party systems for content verification, which is especially useful if a government agency, for example, has a warrant to investigate and document suspected unlawful activity of bad actors on the network.

In sum, Distributed Architecture100inFIG. 1enables the examination and verification of content, both automatically and manually, in ways that are highly scalable, processed through parallelism, and far more efficient and effective at the micro level than the approaches being attempted by centralized social media networks at the macro level. Furthermore, the use of Chronicle2100with its traceability, visibility, and immutability holds both users and publishers to a much higher standard of content quality because they are held accountable for what is ultimately distributed on the network.

FIG. 88is a block diagram of Message Board8800which illustrates Message Board Boundary8802which contains Message Board Header8804, element “P”8846, element “G”8848, Hamburger Menu8806, Message Content Border8808, Message Board Scroll Bar8810, and Message Board Footer8820. Message Content Border8808contains Message Header8812, Message Footer8818, and Message Border8814. Message Border8814contains Message Content8816.

The figure also illustrates Posting App Menu Item8822, Publishing App Menu Item8824, Search App Menu Item8826, Customize Menus8828, App Menu Items8830, System Menu Items8832, and Platform System Menu Items8834. Customize Menus8828references Sort8860, Filter8862, Hide8864, Pin8866, Prioritize8868, Group8870, Ignore8872, and Trend8874menus.

Message Board8800contains one or more messages. Each message has Message Header8812, Message Border8814, Message Content8816, and Message Footer8818. Message Border8814may utilize different colors or graphics to illustrate Publishable Content Types3700inFIG. 37.

Each menu illustrates buttons or links to user interface screens that enable application features and functionality. Hamburger Menu8806illustrates a button or link to display dropdown items for Posting App Menu Item8822, Publishing App Menu Item8824, Search App Menu Item8826, and Customize Menus8828menus. Element “P”8846illustrates a button or link to display dropdown items for Posting App Menu Item8822and Publishing App Menu Item8824menus. The element “G”8848illustrates a button or link to display dropdown items for Sort8860, Filter8862, Hide8864, Pin8866, Prioritize8868, Group8870, Ignore8872, and Trend8874menus.

Activating Posting App Menu Item8822menu displays the screen for Post Message9100inFIG. 91.

Activating Publishing App Menu Item8824menu displays the screen for Publish Message8900inFIG. 89or the screen for Publish Message Smart Contracts9000inFIG. 90.

Activating Search App Menu Item8826menu displays the search screen to search Message Board8800content.

Activating Sort8860menu displays the sort screen for sort customization of Message Board8800content. Sort customizations can also be stored in Social Media System106inFIG. 1and utilized by Social Media System106inFIG. 1for sorting content.

Activating Filter8862menu displays the sort screen for filter customization of Message Board8800content. Filter customizations can also be stored in Social Media System106inFIG. 1and utilized by Social Media System106inFIG. 1for filtering content.

Activating Hide8864menu displays the hide screen for hide customization of Message Board8800content. Hide customizations can also be stored in Social Media System106inFIG. 1and utilized by Social Media System106inFIG. 1for hiding content.

Activating Pin8866menu displays the pin screen for pin customization of Message Board8800content. Pin customizations can also be stored in Social Media System106inFIG. 1and utilized by Social Media System106inFIG. 1for pinning content.

Activating Prioritize8868menu displays the prioritize screen for priority customization of Message Board8800content. Priority customizations can also be stored in Social Media System106inFIG. 1and utilized by Social Media System106inFIG. 1for prioritizing content.

Activating Group8870menu displays the group screen for group customization of Message Board8800content. Group customizations can also be stored in Social Media System106inFIG. 1and utilized by Social Media System106inFIG. 1for grouping content.

Activating Ignore8872menu displays the ignore screen for ignore customization of Message Board8800content. Ignore customizations can also be stored in Social Media System106inFIG. 1and utilized by Social Media System106inFIG. 1for the ignoring content.

Activating Trend8844menu displays the trend screen for trend customization of Message Board8800. Trend customizations can also be stored in and utilized by Social Media System106inFIG. 1.

Activating Connection8846menu displays the connection screen for connection management and settings. Connection management and settings can also be stored in and utilized by Social Media System106inFIG. 1.

The figure is not drawn to scale. In one embodiment of the invention, the elements illustrate their location relative to other elements. In another embodiment of the invention, the elements may have different locations.

FIG. 89illustrates the Publish Message8900user interface elements for a published message.

The Message Header8812contains the mention @User104at element8902, the user type “U” element8904, the user type “U” element8904, the user associations “A-1” element8906, the user associations “A-2” element8908, the user associations “A-N” element8910, the content difference notification “D” element8912, the publisher icon “P” element8914, the content type “C” element8916, the pinned “Z” element8918, and the priority “S” element8919.

The ellipse between element8908and element8910indicate that there can be an unlimited list of user associations. User associations have a graphic illustrating the type association. User associations include employer, professional, union, civic, etc. membership or relationships. As an example, a graphic illusion for an employer association could be the employer's logo.

Content difference notification “D” element8912indicates that content has changed. Different graphic illustrations indicate the type of change. Activating the content difference notification “D” element8912causes the Message Board8800to display an overlay or difference screen that displays the history of the content changes, the details for each change, and comparison tools.

Pinned “Z” element8918indicates a “pinned” message that is placed on top of all unpinned messages in the Message Board8800and has a graphic illustrating a pushpin emoji. Priority “S” element8919indicates a “priority” message that is placed on top of all pinned and unpinned messages in the Message Board8800and has a graphic illustrating a sparkling emoji. The more sparkles, the higher the priority. Ignored “I” element8921indicates an “ignored” message and is illustrated by a “talk to the hand” emoji.

Message Content8816illustrates content elements and content changed elements. Element8920illustrates text content, and element8922illustrates text content with a double strikethrough. Element8922gives a visual indicator in the content to the reader that the content text has changed. Element8922is actionable. If a user clicks on the strikethrough text, the Message Board8800displays an overlay or difference screen that displays the history of the content changes, the details for each change, and comparison tools.

Element8924illustrates a picture for content, and element8926illustrates a circle that encompasses the changes in the picture. The graphic area has the word “Changed” or an icon as a graphics overlay to indicate to the user that the content has changed. Element8926is actionable. If a user clicks on or in the circle, the Message Board8800displays an overlay or difference screen that displays the history of the content changes, the details for each change, and comparison tools.

Element8928illustrates a video for content, and element Video Play Back Bar8930illustrates a common video play back bar to control playback. The vertical line segment at element8932in the video playback bar indicates the location of changes in the video content. Clicking on element8932takes the user to the location of the video content change. The changed video content has the word “Changed” or an icon as a graphics overlay to indicate to the user that the content has changed. Clicking the video player element8928while “changed” content is in context causes the Message Board8800to display an overlay or difference screen that displays the history of the content changes, the details for each change, and comparison tools.

Message Footer8818illustrates trending “T” element8934, rhetoric “R” element8936, and endorsement “E” element8938. Element8934is actionable. If a user clicks on element8934, the Message Board8800displays an overlay or trending screen that displays the trending information about the content. Trending “T” element8934is illustrated by a trend emoji.

Element8936is actionable. If a user clicks on element8936, the Message Board8800displays an overlay or rhetoric screen that displays the rhetoric information about the content or enables the user to participate in the rhetoric features and functions. Rhetoric “R” element8936is illustrated by a rhetoric emoji.

Element8938is actionable. If a user clicks on element8938, the Message Board8800displays an overlay or trending screen that displays the endorsement information for the content. Endorsement displays are actionable and the provide analytics data. Endorsement “E” element8938is illustrated by an endorsement emoji. Message Content8816displays the endorsement popup banner as a graphic overlay.

Some elements allow for hard press or context menus to provide additional features.

A hard press of the mention @User104at element8902causes the Message Board8800to display the profile screen for User104inFIG. 1.

A hard press of the user associations “A-1” element8906, the user associations “A-2” element8908, or the user associations “A-N” element8910causes the Message Board8800to display the profile screen for the association.

A hard press of the content difference notification “D” element8912toggles on and off the differencing display features for content in the Message Content8816display area.

A hard press of the publisher icon “P” element8914causes the Message Board8800to display the profile screen for the publisher.

A hard press of the content type “C” element8916causes the Message Board8800to display the content details screen to provide complete traceability and transparency about the content as well as content type, seeFIG. 7, Publishable Content Types3700, license, copyright, subject headings, subdivisions, classifications and catalog information. SeeFIG. 29, License2914, Copyright2916, Subject Headings2918, Subdivisions2920, Classification2922, and Catalog2924.

A hard press of the pinned “Z” element8918toggles on and off the pinned status of the Published Message8900.

A hard press of the priority “S” element8919enables users to select the number of sparkles to indicate the relative priority status of the Published Message8900.

A hard press of the Ignored “I” element8921toggles on and off ignore status of the Published Message8900. A soft press of the Ignored “I” element8921toggles on and off the Message Content8816display area. This action is customizable, whereby all ignored messages are affected or a single ignored message is affected.

FIG. 90illustrates the Publish Message Smart Contracts9000user interface elements for a published message with smart contract elements.

The Message Content8816element contains the Smart Contracts9002element. The Smart Contracts9002element contains the Smart Contract Forms9004, Smart Contract Validation9006, Smart Contract Workflow9008, Smart Contract Payments9010, Smart Contract Third Party9012, Smart Contract Markup9014, Smart Contract Scripts9016, Smart Contract Data9018, Smart Contract Events9020, and Smart Contract Core9022elements.

The Smart Contracts9002element enable smart contract features and functionality in the Message Board8800.

FIG. 91illustrates the Post Message9100user interface elements for a post message.

The Message Header8812contains the content version “V” element9102.

The read only “R” element9104indicates that the post message is read only. The message cannot be re-shared, downloaded or commented on.

The re-share “S” element9106indicates that users can re-share the post message.

The bump “B” element9108indicates the post message to be redistributed to users.

The download “D” element9110indicates that users can download the post message.

The “for your eyes only” “E” element9112is an indicator that lets users know that the post message contains private, confidential, or sensitive information.

The “set time limit” “T” element9114enables users to set a delete timestamp wherein the message is auto deleted by theirFIG. 1, Social Media System106.

FIG. 92illustrates the Ad Content Display9200user interface elements for an ad message.

Ad Smart Contract9202enables users to initialize a transaction within the ad itself.

Ad Action9204enables users to take an action within the ad, such as flagging or printing a circular ad for their next visit to the grocery store.

Advertiser Profile Access9206enables users to see the advertiser's profile in the directory.

FIG. 93is a block diagram of Social Media App(s)110which is comprised of App Modules1300, Publishable Content Types3700, App Module Client Proxy1414and Core Modules700. App Modules1300consists of Message Board App Module1330which contains Message Board8800. App Modules1300interacts with Publishable Content Types3700, App Module Client Proxy1414and Core Modules700. App Module Client Proxy1414interacts with Core Modules700. App Module Client Proxy1414and Core Modules700connect to Social Media System APIs902, Platform System APIs1702, Public Archivists116, Public Auditors114and Third Party Services112via Network(s)108. Social Media System APIs902and Platform System APIs1702utilize Chronicle2100which is comprised of Chronicle Record2000which consists of Connection Graph6000, Ad Graph6300, Content Graph2024, and State Graph2030.FIG. 93also includes Content2912, License2914, Copyright2916, Subject Headings2918, Subdivisions2920, Classification2922, and Catalog2924.

This diagram illustrates Message Board8800and its relationship to Message Board App Module1330, App Modules1300, and Social Media App(s)110. It illustrates Social Media App(s)110's relationship to Publishable Content Types3700, App Module Client Proxy1414, and Core Modules700. It illustrates how Chronicle2100and its contents are accessed by Social Media System APIs902and Platform System APIs1702which are then accessed by App Module Client Proxy1414and Core Modules700via Network(s)108. It illustrates how App Module Client Proxy1414and Core Modules700via Network(s)108interface with Public Archivists116, Public Auditors114, and Third Party Services112.

FIG. 94is a block diagram of Chronicle Record2000which is comprised of Index Graph9400. Index Graph9400, which descends from Base Graph2050inFIG. 20, consists of Index Graph Schema9402, Index Graph Schema Version9404, Index Graph Hash9406, and Index Graph Signature9408. It also has Index Graph Collection9410which consists of Node(s)9412and Edge(s)9440. Node(s)9412contains Index9414, Index Feature9416, Index Category9418, Meta Data Index9420, Context Index9422, Distinction Index9424, Hashtag Index9426, Mention Index9428, Full-Text Index9430, and State2610. Edge(s)9440contains Index Probability9442. Index9414has the properties Index Id9450, Index Timestamp9452, and Index Cost9454. This diagram illustrates that each time a new Chronicle Record2000is created, post consensus, an Index Graph9400is generated as part of the Chronicle Record2000before being added to Chronicle2100inFIG. 21.

FIG. 95is a block diagram of Chronicle Record2000which is comprised of Index Features9500which consists of Hashtag Trending9502and Mention Trending9504. This diagram details two possible features utilized by Machine Learning System Modules828inFIG. 8to create Index Probability9442in relationship to Distinction Index9424inFIG. 94.

FIG. 96is a block diagram of Index Algorithms9600which is comprised of Index Meta Data Algorithms9602, Index Context Algorithms9604, Index Distinction Algorithms9606, Index Hashtag Algorithms9608, Index Mention Algorithms9610, Index Full-Text Algorithms9612. Index Algorithms9600is associated with Machine Learning System Modules828, AI System Modules804, Analytics System Modules806, Third Party System Modules844, and Core Modules700. Index Categories9614includes Index Machine Learning9616, Index Features9500, and Index Classifier9620. Index Categories9614is associated with Machine Learning System Modules828. Chronicle2100includes Chronicle Record2000which consists of Content Graph2024, Index Graph9400, Directory Graph2034, and State Graph2030. Chronicle2100is associated with Machine Learning System Modules828, AI System Modules804, Analytics System Modules806, Third Party System Modules844, and Index Algorithms9600.

Index Algorithms9600utilizes Index Features9500and select Node(s)9412within Index Graph Collection9410inFIG. 94. It is intended to be used with data related to metadata, context, distinction, hashtag, mention, and full-text in conjunction with Machine Learning System Modules828and Index Categories9614. Index Algorithms9600could also work in conjunction with AI System Modules804, Analytics System Modules806, and Third Party System Modules844which may provide additional index systems or functionality that can be integrated into Index Algorithms9600. Core Modules700provides the cross-cutting functionality for Index Algorithms9600. In particular, all interactions with the elements inFIG. 96utilize Telemetry Core Module714, Logging Core Module710, and Exception Handling Core Module702inFIG. 7. Telemetry Core Module714inFIG. 7provides auditing insight into every interaction that can be audited and reported on vis-a-vis Audit System Modules810onFIG. 8. Machine Learning System Modules828utilizes Index Categories9614consisting of Index Machine Learning9616which is based on a training set of data containing instances whose features and assigned category membership is known, Index Features9500which are derived from system composition profiles and their resulting performance metrics from telemetry data managed by Telemetry System226inFIG. 2, and Index Classifier9620which is a classification algorithm that maps a new instance's system profile data to a category.

This diagram illustrates that Index Algorithms9600collectively can be used by Machine Learning System Modules828, AI System Modules804, Analytics System Modules806, and Third Party System Modules844. All of these modules have access to Chronicle2100and its contents. Machine Learning System Modules828also utilizes Index Categories9614.

FIG. 97is a block diagram of Index System Modules874which is comprised of Index System Module9700, Index Features System Module9702, Index Category System Module9704, Index Meta Data System Module9706, Index Context System Module9708, Index Distinction System Module9710, Index Hashtag System Module9712, Index Mention System Modules9714, Index Full-Text System Module9716, Index State System Module9718, and Index Probability System Module9720. Index System Modules874interfaces with Platform Systems102, Chronicle2100, Index Algorithms9600, and Core Modules700. Platform Systems102, which consists of Index System252and Index Platform System Modules1652, utilizes Chronicle2100as well as Index Algorithms9600. Index Algorithms9600interfaces with Index System Modules874, Platform Systems102, and Chronicle2100. Chronicle2100is comprised of Chronicle Record2000which consists of Content Graph2024, Index Graph9400, Directory Graph2034, and State Graph2030. Core Modules700provides all the cross-cutting functionality for Index System Modules874and Platform Systems102. This diagram illustrates Index System Modules874as it relates to Platform Systems102, Index Algorithms9600, Core Modules700, and Chronicle2100. It also illustrates Platform Systems102's relationship to Index Algorithms9600, Chronicle2100and Core Modules700.

FIG. 98is a block diagram of Index9800which illustrates the indexing functionality of the platform. Index9800is comprised of Chronicle2100which consists of Chronicle Record2000which contains Content Graph2024, Index Graph9400, and State Graph2030. Platform System102utilizes Chronicle System Modules812, Index System Modules874, Index System252, and Index Platform System Modules1652. Platform Systems102connects to Social Media System106-1for User104-1, Social Media System106-2for User104-2, Social Media System106-N for User104-N via Network(s)108. User104-1's Social Media System106-1utilizes Chronicle System Modules812, Index System Modules874, and Chronicle System Modules812. User104-2's Social Media System106-2utilizes Chronicle System Modules812, Index System Modules874, and Chronicle System Modules812. User104-N's Social Media System106-N utilizes Chronicle System Modules812, Index System Modules874, and Chronicle System Modules812. The ellipse between Social Media System106-2and Social Media System106-N illustrates that there are N number of social media systems for every user on the network. Index9800is also comprised of Core Modules700which provides the cross-cutting functionality for Platform Systems102, Social Media System106-1to Social Media System106-N, App Modules1300, System Modules800, and Platform System Modules1600as well as all indexing functionality.

This diagram illustrates how Index9800is utilized by Distributed Social Media Network300inFIG. 3. Oftentimes, the topic of indexing gets collapsed with searches, especially since searches have an indexing component. However, various embodiments of the present technology separate indexing from searching, because indexing happens when the content is committed to Chronicle2100inFIG. 21. As a result, index information is always current and does not need to be merged. If a content item changes, a new Chronicle Record2000inFIG. 20is created, and therefore new index information is created and added to the new record.

Indexing is distributed because every Social Media System106inFIG. 1has an indexing service. This reinforces the overarching theme of scaling and parallelism in Distributed Architecture100inFIG. 1and solves the problems often found when searching web content.

Indexing on the platform also benefits from the scalability and parallelism of Consensus by Conference3800inFIG. 38, specifically the utilization of Publisher Consensus System Category Classification3816, the multitude of consensus networks, and the multi-threading processing ability of Social Media System106inFIG. 1. It is actually in the economic interest of Publisher3502inFIG. 35to document specific aspects of their content for review, because if they make the content relevant and easy to find, they will sell more of it. See Users Get Paid for their Content3628inFIG. 36.

In sum, the platform utilizes Index System252, Index Platform System Modules1652, and Index System Modules874in conjunction with Chronicle2100and a multitude of users to offer indexing that is uniquely accurate and deep. This enables users to locate content with great efficiency and speed.

FIG. 99is a block diagram of Chronicle Record2000which is comprised of Search Graph9900. Search Graph9900, which descends from Base Graph2050inFIG. 20, consists of Search Graph Schema9902, Search Graph Schema Version9904, Search Graph Hash9906, and Search Graph Signature9908. It also has Search Graph Collection9910which consists of Node(s)9912and Edge(s)9940. Node(s)9912contains Search9914, Search Location9916, State2610, and Index9414. This diagram represents the Chronicle Record2000information for Search Graph9900. Note that Search Graph9900is not separate or on its own. State2610and Index9414can pull in other nodes from other graphs.

FIG. 100is a block diagram of Search System Modules840which is comprised of Search System Module3200, Search Location System Module10000, Search State System Module10002, and Search Index System Module10004. Search System Modules840interfaces with Platform Systems102, Chronicle2100, and Core Modules700. Platform Systems102, which consists of Search System220and Search Platform System Modules1622, utilizes Chronicle2100. Chronicle2100is comprised of Chronicle Record2000which consists of Directory Graph2034, Content Graph2024, Search Graph9900, State Graph2030and Connection Graph6000. Core Modules700provides all the cross-cutting functionality for Search System Modules840and Platform Systems102. This diagram illustrates Search System Modules840connecting to Platform Systems102and Core Modules700. It also illustrates how Search System Modules840Platform Systems102relate to Chronicle2100.

FIG. 101is a block diagram of Search10100which illustrates the search functionality of the platform. Search10100is comprised of Chronicle2100which consists of Chronicle Record2000which contains Directory Graph2034, Content Graph2024, Search Graph9900, State Graph2030, and Connection Graph6000. Platform System102utilizes Chronicle System Modules812, Search Platform System Modules1622, and Search Content10102. Platform Systems102connects to Social Media System106-1for User104-1, Social Media System106-2for User104-2, Social Media System106-N for User104-N via Network(s)108. User104-1's Social Media System106-1utilizes Chronicle System Modules812, Search System Modules840, and Search Content10102-1. User104-2's Social Media System106-2utilizes Chronicle System Modules812, Search System Modules840, and Search Content10102-2. User104-N's Social Media System106-N utilizes Chronicle System Modules812, Search System Modules840, and Search Content10102-N. The ellipse between Social Media System106-2and Social Media System106-N illustrates that there are N number of social media systems for every user on the network. Search10100is also comprised of Chronicle Search Engine10104as well as Core Modules700which provides the cross-cutting functionality for Platform Systems102, Social Media System106-1to Social Media System106-N, App Modules1300, System Modules800, and Platform System Modules1600as well as all search functionality.

This diagram illustrates the use of Search System Modules840and Search Platform System Modules1622for Search10100. Platform System102also uses Search System220inFIG. 2and Search App Module1340inFIG. 13. All search related modules and systems utilize Chronicle2100for search as well as for their own storage use. Search10100is optimized for easy indexing, using Index System252inFIG. 2, Index Platform System Modules1652inFIG. 16, Index System Modules874inFIG. 8, and Index App Module1374inFIG. 13. These index modules also facilitate the searching of Chronicle2100. Search Content10102to Search Content10102-N represents all the different search content accessed by User104-1to User104-N.

FIG. 102is a block diagram of Consensus by Virus Algorithm10200which illustrates another workflow for determining consensus. Consensus by Virus Algorithm10200is associated with New Chronicle Record4000, Chronicle System206, System Modules800, and Core Modules700which provide all the cross-cutting functionality required for the consensus workflow. The workflow for Consensus by Virus Algorithm10200begins with Precondition10202, which includes Each Publisher in Category Classification10204, Calculate Nearest Neighbors10206which is associated with Nearest Neighbor Count10208, Distributed Minimum Spanning Tree of Nearest Neighbors10210, and Setup Telephone Gossip Network with Nearest Neighbors10212which is associated to Max Network Count10214. Consensus Request10216leads to Generate Conference Coordinator4002and Coordinator Generates Virus and Virus Hash10218. Virus Hash10224consists of Record Hash10226and Vaccine Key10228. Next Coordinator Generates Sessions and Attendees for Each Session10222which is associated with Session Count10220. Then Attendees Spread Virus Networks10230, Infected Attendees Calculate Record Hash10232, and Infected Attendees Exchanges Correct Record for Vaccine Key10234. This diagram illustrates that Consensus by Virus Algorithm10200utilizes elements from Consensus by Conference4200inFIG. 42and introduces a virus to compel consensus, whereby all attendees are infected with a virus. In order for attendees to get a vaccine key to disable the virus, they have to calculate and exchange the correct record hash.

FIG. 103is a block diagram of App Menu Items8830which is comprised of Ad App Menu Item10302, AI App Menu Item10304, Analytics App Menu Item10306, Archive App Menu Item10308, Audit App Menu Item10310, Chronicle App Menu Item10312, Connection App Menu Item10314, Content App Menu Item10316, Directory App Menu Item10318, Distribution App Menu Item10320, Identity App Menu Item10322, Ledger App Menu Item10324, Licensing App Menu Item10326, Machine Learning App Menu Item10328, Message Board App Menu Item10330, Onboarding App Menu Item10332, Payment App Menu Item10334, Posting App Menu Item8822, Publishing App Menu Item8824, Search App Menu Item8826, Subscription App Menu Item10342, Third Party App Menu Items10344, Wallet App Menu Item10346, Endorsement App Menu Item10348, Compliance App Menu Item10350, Consensus App Menu Item10352, Notary App Menu Item10354, Certified Email Menu Item10356, Workflow App Menu Item10358, SDK App Menu Item10360, Copyright App Menu Item10362, Rhetoric App Menu Item10364, User Verification App Menu Item10366, Trending App Menu Item10368, Account App Menu Item10370, Content Verification App Menu Item10372, and Index App Menu Item10374. This diagram details all of the App Menu Items8830that become user interface screens, libraries, configurations, settings, etc. These menu items essentially represent all of the user interface features and functionality required to work with all aspects of Social Media App(s)110inFIG. 1.

FIG. 104is a block diagram of System Menu Items8832which is comprised of Ad System Menu Item10402, AI System Menu Item10404, Analytics System Menu Item10406, Archive System Menu Item10408, Audit System Menu Item10410, Chronicle System Menu Item10412, Connection System Menu Item10414, Content System Menu Item10416, Directory System Menu Item10418, Distribution System Menu Item10420, Identity System Menu Item10422, Ledger System Menu Item10424, Licensing System Menu Item10426, Machine Learning System Menu Item10428, Message Board System Menu Item10430, Onboarding System Menu Item10432, Payment System Menu Item10434, Posting System Menu Item10436, Publishing System Menu Item10438, Search System Menu Item10440, Subscription System Menu Item10442, Third Party System Menu Item10444, Wallet System Menu Item10446, Endorsement System Menu Item10448, Compliance System Menu Item10450, Consensus System Menu Item10452, Notary System Menu Item10454, Certified Email System Menu Item10456, Workflow System Menu Item10458, SDK System Menu Item10460, Copyright System Menu Item10462, Rhetoric System Menu Item10464, User Verification System Menu Item10466, Trending System Menu Item10468, Account System Menu Item10470, Content Verification System Menu Item10472, and Index System Menu Item10474. This diagram details all of the System Menu Items8832that become user interface screens, libraries, configurations, settings, etc. These menu items essentially represent all of the user interface features and functionality required to work with all aspects of Social Media System106inFIG. 1.

FIG. 105is a block diagram of Platform System Menu Items8834which is comprised of API Platform System Menu Item10502, Archive Platform System Menu Item10504, Audit Platform System Menu Item10506, Chronicle Platform System Menu Item10508, Directory Platform System Menu Item10510, Identity Platform System Menu Item10512, Ledger Platform System Menu Item10514, Onboarding Platform System Menu Item10516, Payment Platform System Menu Item10518, Platform Management System Menu Item10520, Search Platform System Menu Item10522, Third Party Platform System Menu Item10524, Account Platform System Menu Item10526, Telemetry Platform System Menu Item10528, User Verification Platform System Menu Item10530, Connection Platform System Menu Item10532, Consensus Platform System Menu Item10534, SDK Platform System Menu Item10536, AI Platform System Menu Item10538, Analytics Platform System Menu Item10540, Machine Learning Platform System Menu Item10542, Trending Platform System Menu Item10544, Endorsement Platform System Menu Item10546, Ad Platform System Menu Item10548, Content Verification Platform System Menu Item10550, Index Platform System Menu Item10552, and Content Platform System Menu Item10554. This diagram details all of the Platform System Menu Items8834that become user interface screens, libraries, configurations, settings, etc. These menu items essentially represent all of the user interface features and functionality required to work with all aspects of Platform Systems102inFIG. 1.

It will be understood that like or analogous elements and/or components, referred to herein, may be identified throughout the drawings with like reference characters. It will be further understood that several of the figures are merely schematic representations of the present disclosure. As such, some of the components may have been distorted from their actual scale for pictorial clarity.

It is noted at the outset that the terms “coupled,” “connected”, “connecting,” “electrically connected,” etc., are used interchangeably herein to generally refer to the condition of being electrically/electronically connected. Similarly, a first entity is considered to be in “communication” with a second entity (or entities) when the first entity electrically sends and/or receives (whether through wireline or wireless means) information signals (whether containing data information or non-data/control information) to the second entity regardless of the type (analog or digital) of those signals. It is further noted that various figures (including component diagrams) shown and discussed herein are for illustrative purpose only, and are not drawn to scale.

While specific embodiments of, and examples for, the system are described above for illustrative purposes, various equivalent modifications are possible within the scope of the system, as those skilled in the relevant art will recognize. For example, while processes or steps are presented in a given order, alternative embodiments may perform routines having steps in a different order, and some processes or steps may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or sub-combinations. Each of these processes or steps may be implemented in a variety of different ways. Also, while processes or steps are at times shown as being performed in series, these processes or steps may instead be performed in parallel, or may be performed at different times.