/colophon1

this page details the more technical aspects of how this website is built

the presentation layer is discussed in theme, and the structure in /ia

tech stack

no LAMP here.

its LBKVG

os
Linux web server
bespoke (writtten in Go) database
key-value persistent store (written in Go) services programming language
Golang

services

the tech stack provides a trilogy of services (not just www)

IdP
it acts as an identity provider; this is nerdy technology: IndieAuth
www
it acts as a web site, serving up html pages of wisdom (like this very page you are reding now).

pages are store in a variety of formats (e.g. html, md, mf2+json, txt) and converted2 as needed.

social
it acts as an ActivityPub server for participation in that nebulous thing called the fediverse

$LastModified: 2024-10-31 08:51:18Z (Thu, 31 Oct 2024) $


  1. from the greek meaning designer talks bollocks ↩︎

  2. Using HTTP’s content-negotiation facility. It tantek or any of his IndieWebOrg acolytes read this, they are probably having a absolute cow now because they are so against it. Seriously, just get over it. Conneg has been in the HTTP spec since day 1 (ask tbl), and sure, in the early days people have fluffed the implementation. But, if after 20 years you still can’t program conneg they you don’t have the right to call yourself a senior programmer, or even a programmer. ↩︎