Yes, it's also a reader. The retrieved content is base64-encoded text/html, ready to be base64-decoded and dumped into QtWebView (if you want it in the wallet) or into the html document if it's on an externally-hosted ACME.

The blog posts will go to whichever ACME you want. Maybe you run your own, locally or remotely, maybe you share one with some other people, maybe you took out a subscription to a commercial offering...

Riffing again, ACMEs could differentiate themselves by offering enhanced content presentation or specialising in themed or topic-related content. Or you can have one dedicated to your own content.

There'll probably need to be already-paved cowpaths so that people who opt to gain the advantage of signed graphs are assisted by automatically embedding non-text content as base64-encoded resources because otherwise, the common model of referencing external resources would defeat the purpose of a signed graph - to attest to the integrity of the RDF statements by validating the hash of the serialised graph. With external references, you're basically saying “It was over there, the last time I looked.” Which is a valid statement to make but rather a weak one with little purpose that I can discern. I'm fairly confident that Fuseki's back-end persistence takes advantage of compression and base64-encoded resources suitable for web presentation aren't all that luxurious, so it does seem do-able.

I'm not making any claims for the approach other than it's a means of publishing indexes to signed RDF graphs, with the overall expressive power that brings.


Cheers

Graham