Brimstone is the code I use to run this website. You can find the code on Gitlab and, for the time being, on Github. I want to keep this post as a living post, and keep adding to it. That way I hope this post acts like a philosophy.txt.
The code isn't anything special. I write it for several reasons:
The goal of this software is to provide a simple, lightweight, option for publishing text content online that allows a user (me) to:
And allows others to view my content in a way that suits them. So far this includes:
The name is derived from the old achemical name for Sulphur. I have a bit of a Satanic streak in me, and I decided to call it Brimstone because I see Satanic practice as providing a challenge to established orthodoxies that are potentially harmful. In this case, the centralisation of the web into silo'd content. In these silos, there's also all sorts of features that are designed to keep your focus on the site -- such as notifications, games, etc. 'Features' that, in people like me, encourage the development of twitches that distract them from their other goals and habits. This is also often combined with harmful anti-privacy policies that are used to monetise your involvement in the site by spying on you.
In this way, I see the act of producing a tool that might help myself (and maybe others) from separating themselves from that as Satanic. Hence the name Brimstone. Also, Sulphur is used as a pesticide and I like that imagery when used in the context of dealing with the corporate web.
Equally as important, I wanted to play and develop a few skills.
The current version of Brimstone is built on the Symfony PHP Framework. To run the current version you will need PHP 7.1, and Composer to install the vendor packages.
It's released under the GPL 3. This means that if you fork Brimstone or use any of my code in projects, you're also obliged to release under the GPL. Symfony code is released under the MIT License which, thankfully, allows me to use MIT components inside of a GPL'd project.
It does pretty much what any home-brew blog software can do, but specifically:
2018-09-02T10:37:42+01:00 Last Modified: 02 Sep 2018, 10:37
I have a bit of a weird relationship with the Indieweb. I'm not really sure where I stand in that nexus as I've made no attempts to connect with the community, but draw inspiration heavily from Indieweb user Rhiaro and often look on the wiki when I've got work-paralysis on Brimstone and want to procrastinate by adding another half-finished feature and not fix muh bugs. Anyway, from the Indieweb I learned of the term "Silo". Defined as
A silo, or web content hosting silo, in the context of the IndieWeb, is a centralized web site typically owned by a for-profit corporation that stakes some claim to content contributed to it and restricts access in some way (has walls).
They share characteristics such as preventing easy export of content in standard formats, and requiring you to use an identity exclusive to that site (ie your Facebook account. Since I recently underwent evaluations of my Facebook use, and subsequently began my tactical withdrawal from the platform, I thought I'd evaluate my current state of play. It's coming up a year since I started development over here.
Here's the state-of-play when it comes to my use of Silos
Here's the state-of-the-art when it comes to my indieweb software
I'm not too bad in the way of Silo use. There's a lot to do on Brimstone but now I actually have myself a TODO list. Should be a fun year.