Well, just hitting M1 isn't going to be that easy. As I noted, Datacoin had all the right elements in place but few people were interested, even with the comparative luxury of 128Kb per tx. My sense is that the UX was too fragmentary to offer much appeal and, in consequence, failed to present a coherent narrative. The crux of the issue is metadata. Metadata tells you what's stored and how to access it. Without that metadata, all you can do is serially guess. The adaptation of ACME for Datacoin can use the RDF graph to carry the metadata, the blockchain carries the content. The adaptation of ACME for Slimcoin uses the RDF graph to carry both the metadata and the content, the blockchain carries only an index into the graph.

ACME is just a web app that marshals and presents data obtained by talking to the coin's JSON-API and Fuseki's SPARQL endpoint. The web app component can be relatively trivially re-implemented in a Javascript framework such as Angular or Vue.js and the functionality (i.e. ACME as you see it right now) embedded in a wallet tab. ACME in the wallet, with a configurable whitelist of publishers' addresses plus whatever metadata is retrievable to convey information about the author, title, topic, tags, need, I, go, on. Publishing is ... let's riff on this ... in ACME via a javascript-implemented interface, could even offer in-wallet blogging, hitting “post” submits the content for javascript processing - the content and associated metadata are rendered as RDF, signed and pushed up to the configured ACME SPARQL UPDATE endpoint to be stored in the graph - and the ACME publication API updated. You don't even have to make the inscription, that's done automatically. All you need as a Slimcoin user is an ACME API key and off you go. At some stage archiving and migration functionality can be added but it amounts to little more than hooking up buttons to a few SPARQL queries.

I guess torrent serving could also be made (an optional) part of the package, torrenting does hook into a substantial propagation community, although RDF definitely carries the day when it comes to the extent of the metadata and so can be readily “discovered”.

Which is why ACME will be a self-deploying, as-hands-off-as-I-can-make-it package. I suppose, with a following wind, this might be reasonably mistaken for the raw material for a masternode system an overlay network administered by hoomans instead of an algorithm. It'll have it's pros and cons but it might see some use.

Cheers

Graham