Melative is based in 3 areas of code, which are not part of the media core. A basic overview.
Nuclear API
First is the framework, Nuclear, which happens to be relatively stable, although there will be modifications. On it’s own, there are no templates to create the html of a basic site, but Nuclear isn’t about interface anyway. It is almost strictly for building API’s.
Context Service
Second is the nameless context service, which will also be open-sourced. It’s basic function is to semantically connect and identify type-name combinations (e.g. /manga/Kobato. and /manga/???? are the same when referenced by the service). Melative serves media-type contexts, but any types may be inserted rather quickly and easily (type being a single word “category”). It is a backend with a set of API methods for meta-organization. (It makes most of Melative’s features possible)
Micros
Third, is the micro-activity updater (Micros microblog). It is basically a command prompt for talking about specific titles or performing actions on them within the user’s library (rate, tag, etc). This module of the system will also be open-sourced as a type of open-micropublishing system.
My current task is making* it federated, such that installations may publish/subscribe (”follow”) to each other. Underneath, it will also allow link-in to Melative so that cataloging and organization still happens for a user (basically the Melative account will “follow” a user@domain.com’s activity and act accordingly).
Micros also enables Melative user’s to follow non-melative users, but again it has little do to with Melative. We’re opening up the socialsphere, so that service is arbitrary; users have entire control and access to their social data.
*In fact, this has been accomplished, but the Federation occurs within Nuclear and according to a drafted protocol. The requirement is mapping micro-publishing through Micros to the federated API.
