Now: a spiced static generator
After spending months on arguing with myself, I finally decided to write my static generator and walk away from WordPress. It took me a long while, but I'm more or less ready.
Summary and reasoning: Going Static
Now, to be honest: it's not completely static. It does generate a static site indeed, which can be copied/ported on the filesystem level, but it also generates and handles webmentions and search which can't be static.
I rarely ever POSSE these days: I decided to consider silos as one-to-many messaging systems and never post anything "valuable" there. This can be forced by actively deleting old entries there.
If I do need to, I'll just ping bridgy; the links needed for it to POSSE will be generated in the HTML.
Currently I'm reconsidering to start doing PESOS for a few things. I already pull data from places like last.fm, but they go into an archive instead of my site.
I used WordPress between 2007 and 2016, but in the end I was running a version where I had to apply patches to the core - I tried submitting them but most of them got neglected.
Former WordPress projects
Consider these as abandoned or on hold projects.
- wp-webmention-again - an alternative webmentions plugin for WordPress. It's most probably broken by now.
- Blogroll2email- turns the Blogroll part of WordPress to feed (atom, rss, mf2) parser to send entries as mail; supports granary json-mf2 format
- wp-shortslug - use pubdate epoch converted to base36 (0-9a-z) as short permalink
- wp-flatbackups - an auto-exporter for WordPress, creating a flat, directory based copy of YAML + Markdown (and/or HTML) of every post. This can't be imported, just servers as a fallback plan for longevity.
- wp-url2snapshot - to have a backup copy of a linked website, the plugin pulls in an html-only version of every link it can find in any post content and stores it for potential future use. In case a link is not snapshotted yet and is not available on the web anymore, it tries to fall back to the last available version on archive.org.
- Keyring Social Importers a reactions (like, fav, comment, etc ) importer for various silos
Eons ago ( as in internet-eons, so ~16 years ) I FTPd my first static site to a free hosting provider ( long dead since ). Due to being inexperienced and due to the lack of generic computing knowledge, I'd never heard of version controlling that time, so up until 2002, all my changes were lost. I only realized this somewhere around 2014, when I decided to rake every single content I ever did together, and to be honest, it's not a good feeling to realize there is no way to get that content back, ever.
Since '99, lots of things had changed, and for a little while, I offered hosting solutions myself. That required hosting all the actual web stack, including, for example, mail. This resulted that even today I'm running my own mail stack, and despite the growing number of insane security loops needs implementing, I want to keep it that way. I can do backups of everything, and if I lose my website, I'm sad; but if I can't access my mailing, I'm going to lose much more. I'm not willing to take chances of Google locking me out from my own account suddenly, or a random provider accidentally loosing 10+ years of mails. If I lose it, it's my fault.
I know many who are not willing to take responsibility of hosting their own stuff - "it's too much trouble". In this era of computing, it's really not, if you're a power user, it shouldn't even take long - but then you'd need to take responsibility for it, which, I believe, the real problem is.
Don't be afraid of owning your web presence.