blog@melative

As previously noted, Micros is the microblogging running inside Melative, and one of the major goals is cross-domain compatibility and fluidity; aka Federation. Rather than build something similar to OpenMicroBlogging protocol, we decided to design a specification protocol which the microblog will use to solve this problem of cross-domain following. (Just for reference, any publishing software can use the specification, it’s open and being fleshed)

Here, I’d like to address 4 aspects of the service to help enrich the understanding of this Federated specification, as well as the solution and benefits it provides.

What problem does Federated micro-publishing solve?

• Social services may only be used with valid usership
• Social relations may not be established without mutual usership (centralization)
• Social services are closed, by nature (one must have an account)
• Social services are centralized (e.g. thedomain.com)
• Users are following other rules (e.g. site agreements)
• There is no freedom, as there are always requirements (e.g. usership)

How is this a unique solution?

• Decentralized (users on any domain may be part of the social-sphere)
• Federated (users may establish relations without regard for central usership)
• It’s a specification
• It’s an open protocol
• It’s adaptable and customizable

We are only implementing a version of what is possible through the API specification. Other developers may create their own platforms which will interact in the same fashion. The aim with Micros is a publishing platform, similar to a blog, but extensible through theming and plugins. The core of Micros will be a hooking environment in which 3rd party scripts may execute.

Is there evidence that this works?

• The Nuclear platform currently supports the core specification
• The specification fully uses OAuth, an established technology
• Runs on any scriptable web host (no req. for full server control)

What sort of business model does it cater?

• No central ownership
• Specification provides an infinite platform
• Open development
• 3rd party applications
• 3rd party features
• Potentially massive user-base (the Internet)

The importance in the business model is that the specification allows developers/vendors to create their own pay/private services, which still enables interaction with the social-sphere. Also open is the area of customizations, similar to Wordpress’s flourishing theme/plugin base.

In summary, we are modularizing the microblog to fit this specification in hopes of building a larger, open social publishing network that may be used regardless of usership and domain.

• • Comments [2]
  • Tags [federation, microblogging, specification]
  • Categories [feature, technical]