2017 has been a wild ride, but I have a lot to be very grateful for. I am honored and privileged to be surrounded by my lovely Mastodon friends, and to be in a position that I can give back a little to our community. Thank you for being a bright light in an otherwise challenging year.
In the spirit of continued transparency, and because I haven’t remembered to do this in a while, this is an accounting of Free Radical’s hosting costs for November 2017:
The DigitalOcean CPU usage graph runs consistently at about 5%. Memory is always at about 70%, with most of it used by PostgreSQL for caching. Disk usage is at about 0% except during hourly backups. Bandwidth averages about 20Kbps except during those same offsite backups.
https://freeradical.zone/ is way #under1000.
I’ve had a hard time going cold turkey with birdsite but it gets easier by the day. I still think of it as the early service that was new and different and exciting and wasn’t being used as a machine for spreading hate. I need to break that habit, but it’s hard.
This morning I drank deeply of that cesspool and was shocked at how horrible it is. Was it always that bad and I was just used to it, or has it taken a recent and sharp turn for the worse? I don’t know. Either way, here we are.
Free Radical is now on Mastodon v2.0.0.
Free Radical celebrates its 200th verified user.
The victory parade was well attended.
Free Radical is now on Mastodon v1.6.1.
The Free Radical Ansible repo commit 76a0107 fixes two problems:
certbot renew cron jobs complete successfully
Several times I’ve compared this instance to my living room. I think that’s a powerful and accurate analogy and I’d like to explain what I mean by that.
The server was down from about July 5, 2017 11:30AM PDT to about July 6 8:15AM PDT. I rushed off an apt-get update and didn’t check its results before rushing off to something else. Sorry for any inconvenience!
I’ve set up monitoring with Uptime Robot to notify me about any future outages so you won’t be sitting in the dark.