Today, we dive into two spaces on the federated social web, look at their history and the players behind them, and talk about their potential futures. [Plus protocols & interoperability.]
In this paper we analyze the mathematical foundations of IOTA, a cryptocurrency for the Internet-of-Things (IoT) industry. The main feature of this novel cryptocurrency is the tangle, a directed acyclic graph (DAG) for storing transactions. The tangle naturally succeeds the blockchain as its next evolutionary step, and offers features that are required to establish a machine-to-machine micropayment system.
The IOTA protocol is a Distributed Ledger Technology developed by the IOTA Foundation. It is a next-generation technology designed from the ground up to be the data and value transfer layer for the Machine Economy.
Ceptr is organized as a do-ocracy -- meaning that we want to empower those who will step forward to take action. Unlike a meritocracy which is based on the merit of one's past performance, a do-ocracy is based on empowering those who commit to "DO" things.
Ceptr is a platform for next-gen networking, providing a protocol for pluggable protocols, distributed data integrity on Holochains, and truly distributed application hosting
HTTP/2 is poised to eliminate much of the waste that developers deal with. Multiplexed connections will eliminate the need to bundle JavaScript libraries together. But is HTTP/2 a panacea to all our problems? What about WebSocket? Allan Denis tells us what HTTP/2 is good at and debunks some myths about what it can do.
Protocol buffers are a language-neutral, platform-neutral, extensible way of serializing structured data for use in communications protocols, data storage, and more.
A high-performance, open-source universal RPC framework. Client applications can directly call methods on a server application on a different machine as if it was a local object.
JSON-RPC is a stateless, light-weight remote procedure call (RPC) protocol. Primarily this specification defines several data structures and the rules around their processing. It is transport agnostic in that the concepts can be used within the same process, over sockets, over http, or in many various message passing environments.
Let’s start with an example. Say we have an amazing website with a login to protect some private data we made available to our users at /private. We won’t make this example too complicated, so let’s…
Cross-Origin Resource Sharing (CORS) is a specification that enables truly open access across domain-boundaries. If you serve public content, please consider using CORS to open it up for universal JavaScript/browser access.