Yayaka Protocol and Highly Distributed Social Blogging
Yayaka Protocol is a yet another protocol for distributed social blogging. I explain “Why I create”, “Why we love”, and “Why you will love” in this article.
Yayaka Protocol has following purposes roughly:
- Participation with minimum servers
- High extensibility with layered protocols
Decentralization is the first step to get our freedom. Monopolized platform may take your freedom.
Democratization is the second step to do that. It means Yayaka Protocol doesn’t divide a monopoly service into many authoritarian services.
Participation with minimum servers means we don’t have to implement all functions of distributed social blogging for each server. Each server can have a minimum implementation.
High extensibility with layered protocols means we can extend our web services uniquely in cooperation with other services which have a common view.
Here are the features of Yayaka Protocol to perform the purposes.
- Easily migration between servers.
- Each server only has to implement a partial set of functions of distributed social blogging.
- Any way to connect two different hosts is allowed. (Socket, HTTPS with token, etc.)
- Additional profile attributes, type of social blogging events, and types of contents are specified in higher-level protocols.
There are 4 yayaka services, identity service, repository service, social graph service, presentation service. Each user registers themselves with identity services and authorizes other services to use. Repository services store events like posts, favorites, reposts, etc. Social graph services store users’ relations and deliver events properly. Presentation services provide interfaces to be used by users like front-end UI, API, etc. Each user can have multiple repository services to post, social graph services to broadcast, and presentation services to use UIs which match for each purpose. If a repository service censors unjustifiably or a presentation service regress its UI or API, each user can exit right away.
Yayaka Meta/Messaging Protocol
Yayaka Meta/Messaging Protocol (YMP) is a messaging protocol for distributed Web applications. Each server can implement multiple connection protocols and message protocols as higher-level protocols of YMP. Connection protocols specify how to establish a connection between two different hosts and message protocols specify how the application works with messaging between services. Yayaka Protocol is a message protocol of YMP (Yayaka Meta/Messaging Protocol).
How Yayaka Protocol works
- A user chooses a server to register him/herself.
- The user enters registration information on one of presentation services trusted by the server.
- The presentation service sends a message to the identity service of the server.
- The identity service creates a user.
- A user enters who to follow on a presentation service.
- The presentation service sends a message to one of social graph services authorized by the user.
- The social graph service sends a message to target social graph.
- Both two social graph services store the following relation.
Creating an event
- A user enters data to submit on a presentation service.
- The presentation services send a message to one of repository services authorized by the user.
- The repository service stores the data.
- The repository service broadcasts the event to social graph services which subscribe the repository service.
- The each social graph services broadcast the event to services which subscribe them.
Writing the YMP specification is almost finished. Currently, I’m simultaneously writing Yayaka Protocol specification and a reference implementation with Elixir.
Here are the plans of Yayaka Protocol and YMP:
- Create a first connection protocol
- Create a message protocol for distributed registry to register higher-layer protocols of YMP.
- Create a message protocol for distributed git hosting service.
How to contribute to Yayaka Protocol
There is an organization of Yayaka Protocol Suite. Please feel free to open issues.