Considering that a couple of times now I've been a proponent of using an RSS reader, I figured it was time I wrote a tutorial on how to install Tiny Tiny RSS, using Nginx as the server and PostgreSQL for the database. While as with any piece of software there are a number of tutorials and guides already out there, I've found that none of them provided a complete instruction set that didn't have me running into and searching for solutions to multiple errors. To that end, this tutorial aims to both provide as complete a set of fool-proof instructions as I can make, both for newbies to self-hosting, and simply as a reference for my future self should I need to do this again.
I've spent a few hours over the last few days reading Butterick's Practical Typography, which I felt might be a good idea considering that I enjoyed his rant about Web Design that I posted a while back. I feel that in some ways I damn myself as the worst (or best, depending on how twisted your perceptions are) type of geek for being interested in and recommending a book on the intricacies of typography. Though really, much as there is on the site, it's still only a primer, and I don't think I'm going to go much farther down the rabbit hole than this.
After playing with Meteor for the past week or so, which overall I really enjoyed, the one thing that really bugged me was how to use node.js modules in a Meteor app. There are plenty of instructions out there that sort of tell you what to do, but I found all of them to be variously confusing and unclear. Of course, this isn't helped by the fact that at the time of writing Meteor is only version 0.6.5.1, so things are still in flux. The aim of this post is therefore to provide a comprehensive and clear guide to how I was able to get Meteor to work with Node modules.
A really interesting talk by Matthew Butterick about the state of Web Design.
It’s now or never for the web. The web is a medium for creators, including designers. But after 20 years, the web still has no culture of design excellence. Why is that? Because design excellence is inhibited by two structural flaws in the web. First flaw: the web is good at making information free, but terrible at making it expensive. So the web has had to rely largely on an advertising economy, which is weakening under the strain. Second flaw: the process of adopting and enforcing web standards, as led by the W3C, is hopelessly broken. Evidence of both these flaws can be seen in a) the low design quality across the web, and b) the speed with which publishers, developers, and readers are migrating away from the web, and toward app platforms and media platforms. This evidence strongly suggests that the web is on its way to becoming a second-class platform. To address these flaws, I propose that the W3C be disbanded, and that the leadership of the web be reorganized around open-source software principles. I also encourage designers to advocate for a better web, lest they find themselves confined to a shrinking territory of possibilities.
I really sympathise with his views on this. The design of most major websites is crap. Unfortunately, he's correct in his assertion that this is largely to do with the fact that advertising drives most of the web. It's going to take a lot of work to find ways around this.
As I'm currently working on plans for my new idea for a useful site, so this kind of thing is something that I'm doing a lot of thinking about lately. It's so easy to just copy the base format that most sites use without thinking about whether that design is the best for your current situation.
There's an article in the New Zealand Herald today, highlighting the ridiculousness of the current government's intervention in the broadband market. Feel free to skip the rest of this post if you wish, but I recommend you at least read the article. It does a good job of going over the issues from a technical, legal, and governmental angle, but there is one area it doesn't cover, which journalists mostly seem to shy away from, and that is the ideological angle.
So, I guess it's time I started to write a blog. I've always read that it's recommended in IT to write a blog, or maybe in any industry these days, in order to have some sort of recognisable professional presence. Or, at the very least, to keep your rants off Facebook.
At any rate, there are plenty of things I could talk about, and I will. I tend mostly to have strong opinions on Politics, Information Technology, Economics, the Environment, and any intersection between the bunch, though not necessarily in that order. I think I'll start off properly with a politics post next.