Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

more intro improvements

  • Loading branch information...
commit 33dcb8948850d1195b97e7f345ed581dba6f8e64 1 parent 30bf627
@quartzjer authored
Showing with 6 additions and 6 deletions.
  1. +6 −6 org/v2.md
View
12 org/v2.md
@@ -5,9 +5,11 @@ telehash v2 (draft)
(note: this is the second major version of the telehash protocol, the first one is deprecated and was a minimal experimental spec to create a distributed hash table)
-Telehash is a protocol enabling applications to find, identify, and communicate directly with each other. It is built on public-key security (PKI) and includes the ability to create peer-to-peer (P2P) connections as well as form a distributed hash-table (DHT) for decentralized architectures.
+Telehash is a protocol enabling applications to find, identify, and communicate directly with each other. It is built on public-key security (PKI) and includes the ability to create peer-to-peer (P2P) connections as well as form a distributed hash-table (DHT) for decentralized architectures. As a protocol it doesn't provide direct end-user functionality but is primarily a tool for developers to use in creating modern apps that require rich experiences and interconnectivity at scale.
-The design principles are based on using JSON as the core data format in an extensible way and keeping the minimum requirements simple and lightweight enough to support apps running on networked devices and sensors. The goals include not forcing any particular architecture design such as client-server, centralized/federated/distributed, polling/push, REST, streaming, publish-subscribe, or message passing, any can be used as telehash simply facilitates creating the bi-directional connectivity between any two or more apps.network
+The principle idea that drove the creation and development of telehash is the belief that any app should be able to easily and freely talk to any other app, enabling the same freedom for the people using them. The challenges and complexity in doing this now with other technologies such as APIs, OAuth, and REST is only increasing, often forcing centralized and closed/gated communication platforms. By adopting telehash in any app it immediately has a rich open foundation for not only its own needs, but also the ability to integrate and share functionality with other apps easily.
+
+The foundation of the protocol builds on JSON as the core extensible data format with a requirement to keep it simple and lightweight enough to support apps running on networked devices and sensors. The design goals include not forcing any particular architecture design such as client-server, centralized/federated/distributed, polling/push, REST, streaming, publish-subscribe, or message passing, any can be used as telehash simply facilitates creating the bi-directional connectivity between any two or more apps.
There's some high level concepts that are important to understand when talking about anything using telehash, and the first one is that of a "network", the term describing how all telehash apps are organized. A network is identified by a hostname (such as "telehash.org") and it represents one way for apps and services to find and talk to each other. Each network can be open or closed in allowing apps to connect to it, closed networks are managed by "operators" who facilitate access to the resources in their network and who can connect.
@@ -15,11 +17,9 @@ Every app has a unique public id on each network it's connected to that is calle
# Getting Started
-In order to use telehash in an app it will need to include a switch (below), generate an RSA key-pair (every unique instance of an app has it's own), and connect to a network. Once it's connected it can find and access other hashnames on that network as well as provide services to back out to anyone. Typically a network has operators that manage it's own names/ids and what services are available unique to what apps are connected to it, most apps have their own network for access to their back-end, user management, profiles, notifications, APIs, etc facilities.
-
-To create a new network you simply need to add a DNS SRV record to the hostname for your network, identifying one or more hashnames of operators that manage it.
+In order to use telehash in an app it will need to include a switch (below), generate an RSA key-pair (every unique instance of an app has it's own), and connect to a network. Once it's connected it can find and access other hashnames on that network as well as provide services to back out to anyone. Typically a network has operators that manage it's own names/ids and what services are available unique to what apps are connected to it, most apps have their own network for access to their back-end, user management, profiles, notifications, etc facilities.
-(in progress...)
+Most apps will use their own network to provide custom services and manage access to it. To create a new network you simply need to add a DNS SRV record to the hostname for your network that identifies one or more hashnames of operators that manage it. (todo show example operators, software and patterns)
## Telehash Switches
Please sign in to comment.
Something went wrong with that request. Please try again.