Monthly Archives: August 2013

This pair of headphones and I have a long, convoluted history. I bought it on the recommendation of two of my friends who have the non TI model (and they bought it based off my research when I was looking at replacing my ATH M50). Lets start with the trivial stuff.


This alone is epic. BEST WARRANTY CARD EVER.


The headphones came in a nice fabric case, with 2 different headphone cups (leather and velor), a headphone cable that connected to either cup and the headphones, in a nice shaped foam insert. Pretty awesome *usable* packaging.






This is how it was packaged. The other cups are below and are pretty easy to swap out. Embarassingly, I haven’t tried them yet.





Build quality is nice and solid – the cable is easily replaceable (and apparently there’s clones of this with different cable lengths) and it feels sturdy, and comfortable on my head (but I don’t have a monster noggin).

Sound quality is excellent. Sound quality is also highly subjective I guess. I’m not one of those folk who can wax lyrical about a pair of headphones but there’s a few things I can say. Its crystal clear, has good, tight bass, and I occasionally hear something off these phones and assume its someone behind me. I’d initially assumed my laptop onboard sound card struggled to power it but a few experiments later, I realised it just sounded ‘off’ compared to my better gear – the FA003 is SLIGHTLY unforgiving of totally crap soundcards – but unless you’ve got some badly designed one, or something off a laptop that dosen’t sound all that great anyway, its a non issue. I do regularly use it for non audiophile things like gaming and youtubery off my desktop. I generally pair it up with a desktop amp, and a external DAW for music, and run it off the amp and my onboard soundcard for everything else. These work *great* with a nice amp and sound card, and they don’t need to be terribly expensive.

One final note – I special ordered it. The other two guys I know who have it got it online. Its a pain in the ass to get – unless you can find someone to shut up and take your money

I used to be a google reader user before they shuttered. I then switched to the old reader – they had one hell of a site, but had scaling issues, the poor dears, and decided that they couldn’t handle us refugees. Lets be honest here. I could move again, but at this point of time, I have trust issues. I want a reasonable amount of control, the option to move to another server, taking my feeds with me, and the knowledge that I won’t have to switch providers for reasons I can’t control.

The alternative thats currently the best loved, and maintained is ttrss. While it will run on a standard LAMP stack, apparently it works better on postgres – so I figured I’d go with ubuntu, lighttpd, postgres and php. I also decided to document the whole process. The web stack setup is based off howtoforge’s guide on setting up a lighttpd/myql/php stackĀ  I’ve modified the instructions to use the things I use, and streamlined it a bit. I *do* assume you’re building off a barebones VM – you’ll need to adjust the instructions if you’re running or planning to run something like Apache or Ngnix.

Firstly, the packages you’ll need

sudo apt-get install lighttpd php5-fpm php5 php5-pgsql php5-curl php5-cli postgresql

Lets break this up into what these packages are for. You have your web server, and the varient of php its running – in this case lighttpd and php5-fpm, with php5 being a prerequisite for pgp. You have the postgres related packages postgresql and php5-pgsql, and finally you have php5-curl and php5-cli – the latter is a suggested prerequisite for ttrss and the latter is needed to run the update script for ttrss. Naturally, if you’re running another web browser, switch the appropriate group of packages for alternatives.

The default configuration for lighttpd assumes you use spawnfgi rather than fpm for php. You will need to make two changes to the config files to make sure things work fine. These are identical to what is done on howtoforge’s tutorial.

First, you need to enable cgi.fix_pathinfo in /etc/php5/fpm/php.ini. To do this, open up /etc/php5/fpm/php.ini with your favourite editor, find a line that says


and remove the semicolon to enable it.

Next, to set up php-fpm

sudo su
cd /etc/lighttpd/conf-available/
mv 15-fastcgi-php.conf 15-fastcgi-php-spawnfcgi.conf
nano 15-fastcgi-php.conf

Then paste in – for ubuntu 12.04. Annoyingly this will fail horribly for ubuntu 13.04 and you need to look up the appropriate, sockets based alternative here

The rest of the instructions are identical, so meh, do your homework ;p

# /usr/share/doc/lighttpd-doc/fastcgi.txt.gz

## Start an FastCGI server for php (needs the php5-cgi package)
fastcgi.server += ( ".php" =>
                "host" => "",
                "port" => "9000",
                "broken-scriptfilename" => "enable"

Now that the configuration is done, we need to enable our new configurations and reload lighttpd and php-fpm

lighttpd-enable-mod fastcgi fastcgi-php 
/etc/init.d/lighttpd force-reload
/etc/init.d/php5-fpm force-reload

at this point, our environment should be ready for the install to start. A good way to check is to create a php information script, and take a peek

Create a file in /var/www/ called info.php and paste in


Go to your webserver and check if it works – if it does, check for entries saying ‘pgsql’. If they are there, we’re ready to create the database.

sudo -u postgres psql postgres

should throw you into the postgres shell
It looks something like


You need to create a new user


then create a new database with the new user as an owner

postgres-# CREATE DATABASE ttrss WITH OWNER ttrss;

and just to play it safe


Download and unpack ttrss from
I tend to do this using sudo wget url, since I have had little luck doing it any other way. Probably not best practice. You’ll likely also want to change the folder name to something friendlier, and change ownership to www-data (so you can automatically have ttrss set the config file it generates)

At this point, go to the website, set some sane defaults and get cracking – you can pretty much coast through the rest of this.

Upgraded my VPS (which this runs on) to a newer ubuntu LTS – this was suprisingly simple. My database is hosted elsewhere so that was a non issue (I need to do a test of the migration process at some point). As such all I needed to do was copy /var/www and /etc/ (though I didn’t copy over everything), dump a copy of my installed packages (which i ended up not using ;p) reinstalled, and copied over what was needed – in my case web server configs and pretty much nothing else.


Suprisingly painless!