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.]
Ceptr is a platform for next-gen networking, providing a protocol for pluggable protocols, distributed data integrity on Holochains, and truly distributed application hosting
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…
User agents commonly apply same-origin restrictions to network requests. These restrictions prevent a client-side Web application running from one origin from obtaining data retrieved from another origin, and also limit unsafe HTTP requests that can be automatically launched toward destinations that differ from the running application's origin. In user agents that follow this pattern, network requests typically include user credentials with cross-origin requests, including HTTP authentication and cookie information.
Seems that most still believe Google Wave primarily uses XMPP to pass data around. Turns out, XMPP is only used for server to server federation. Joe Gregorio has a good overview of the actual APIs and protocols used in Wave, but I still found it easier to create a diagram