Comment System

/images/_dae7dba8-98af-4e0a-9ceb-1a60c195de70.jpeg

Disqus was a disappointment. I last looked at it a couple of years ago, and found it to be serviceable then, but it seems to have taken a slide onto the slums of the web, and is now covered in ads and unresponsive web pages. Not the kind of image that makes me think they’ll value the privacy of my guests. But I’ve found a different solution…

◇◆◇◆◇◆◇◆◇◆◇◆◇◆◇◆◇◆◇

GraphComment looks like they’ve got a good solution and they say all the right things about security and privacy. So far, I’ve only hooked up a simple test, which puts a comment interface at the bottom of every article I post. Preliminary tests are fast enough and featureful enough that I can see myself using it, but I want to try at least one more before I commit.


Read More


/images/_e1b23d38-68ca-45eb-bf1b-56bd12ad0ce3.jpeg

Obsidian-fu

Refactoring the shadowmaker has become a bigger headache than I had originally anticipated, but it’s for the long-term health of the system, so I’m sticking to my guns. This weekend added further drama when I finally stopped running away from frontmatter and embraced it for all my metadata. Sure, scattering #ch-command directives throughout the body of the notes was insane, but fixing it is going to mean more than just adding a few metadata fields. I may have to completely change the way I use Obsidian.

/images/_e42c8a8a-b127-431f-b414-425c5d17a2dd.jpeg

Ontology-2.0

While trying to integrate the many episodes of CaveTV into the site, I realized that the ontology was getting cramped. It needs to be revised to better distinguish between internal projects, external brand identities, multiple deliverables within a brand, and distinct showrooms.

What follows is the scheme we devised for what the abstractions are, how they should be tagged in Obsidian, and how the files will be managed within Hugo.

/images/_2ef531ec-bc45-46fe-841b-6864301fa06c.jpeg

Cutting The Monster Into Pieces

Now that I’ve identified a useable hosting candidate, my final test of their service will be to roll out a full implementation of the websmith deployment scheme. But in contemplating how I’m going to do that, I’ve realized that I may not have broken the project into distinct repos properly. So I’m going to figure it out by explaining it to the rubber duck. (Meaning you. :-)