How I set up Pelican for blogging pt. 1

No, this blog still uses WordPress because of its convenvience and ease of use. But I needed a way to document my personal server that I use for Mumble, IRC and my small projects and I decided to test out static blog generators for that.

Normally people use Octopress (based on Jekyll) which labels itself as “A blogging framework for hackers” which is cool and all but I really don’t like Ruby and I had heard a lot of good stuff about Pelican so I went with that.

This post merely describes what’s different in my own approach and isn’t very detailed in itself, for a better tutorial in setting things up I recommend the documentation pages on how to get started. Continue reading


This surfaced on the web yesterday on Hacker News and today on Reddit. Someone made, for lack of a better explanation, a web browser that is a web page. The point is to allow the end user to modify the browser with basic HTML, CSS and JS skills which is actually really cool.

A lot of people have been discussing what Breach provides that Firefox doesn’t since both are open source, modular and “hackable”. I love Firefox and use it wherever I can but I do think that Breach has a more interesting approach by using HTML5 for UI and addons instead of the slightly more esoteric XUL that Firefox uses.

It will be interesting to see where this leads to in the future, this might just be a cool and alternative browser right now but it’s also another step to further blur the differences between desktop apps and the web.

The web browser is available here in an early alpha stage for Mac and Linux:

Tinfoil hat

I was just now browsing for network cameras, which are a special type of surveillance camera which handles a lot of the encoding and stuff in the camera instead of on the surveillance machine but I digress. While browsing for these cameras I checked out a lot of retailers, mostly to see what one adapted for industrial sized companies might cost.

Within minutes of this I receive a spam e-mail from a retailer of unknown origin, one I most certainly did not visit while browsing. The whole e-mail sounds like a sales pitch talking about features and pricing on network cameras which they provide. Incredibly suspicious.

The fantastically scary part about this ordeal is that I never once submitted my e-mail to any of these websites, I never submitted any form or entered any type of information. The amount of spam I receive is, while not negligible, very rare so the chance of spam even arriving this close to the event is unreasonable. The e-mail address which received the e-mail is also one I no longer use and is not connected to any social media platform that I know of.

What this means, basically, is that either did I receive a single spam e-mail about the very topic I was researching while I was researching it by pure chance. Or someone managed to identify me and what I was doing and link that information to my personal e-mail address (which they’ve probably lifted from elsewhere) through their competitors websites.

I’m putting on my tinfoil hat now.

The Heartbleed Bug or “Why you shouldn’t reuse passwords”

The Heartbleed Bug was discovered last week, which is a vulnerability in OpenSSL which powers the HTTPS services of most major websites today. The bug can be quite adequately explained by this XKCD comic.

This brings to light the importance of not reusing passwords. Even if your password is fairly impossible to guess and mathematically improbable to crack it’s still useless if you use it for multiple websites. Because it only takes one website to leak your password through a vulnerability like this to compromise all of your accounts where you reused the same password. So don’t, or at least enable two-factor authentication.


Facebook released Hack last week, which is a new language based on PHP that requires the use of their virtual machine,┬áHip-Hop (aka HHVM). But it’s important to remember that Hack is not PHP, while it understands PHP in much the same way that C++ understands C it isn’t always possible to migrate from the default interpreter to HHVM since they have chosen to not support all of PHP’s features, for better or worse.

There have been a lot of mixed sentiments on the internet over the new language, though the biggest concern appears to be that the naming choice will make it difficult to find anything actually related to the language. Imagine searching for “hack language” or “hack facebook” for example.

Personally I think the release of an independent version of PHP could be positive for the community, regardless of the name. PHP has always been quite careful about backwards compatibility and stability while leaving performance, consistency and, in a sense, security at the side. Hack have already introduced a lot of cool features (really just stuff that you would normally expect from a modern language) that PHP will probably never see the light of, type annotations and collections being my favourites so far. And HHVM have already made significant improvements to the performance of PHP.

I hope that Hack can become a platform for language features and changes that the core PHP language might not be ready for. Since Facebook uses PHP as a base for their new language they might be able to get a lot of traction from developers shifting their code bases to Hack, and maybe this shift can cause PHP to transform into something that not only gets the job done but also something that doesn’t allow “clever” code, inconsistent behaviour and other general headaches.

On the success of Flappy Bird

Apparently there’s a new mobile game called “Flappy Bird” which has taken over the mobile gaming market. I had honestly not heard of this game before I read that it’s being taken down by its creator for being too successful (what?).

IGN put up a review explaining the game concept which is so ridiculously basic it’s almost embarrassing. The fact that this game is so immensely successful only shows to prove what people like David Heinemeier Hansen have been talking about for a very long time which is to “underdo your competition“.

By removing as many features as possible you’re also making your product easier and more accessible to use by lessening the learning curve. This means that you can essentially expand your market by making your app smaller.

Flappy Bird might be an extreme example of “less is more” but it have also accomplished something that many app developers can only dream of.

Setting up two-factor authentication everywhere

I’m studying computer security this term and it has a way of making you very paranoid about security matters, and recent articles like this and this really doesn’t help either. Therefore I’ve decided to set up two-factor authentication everywhere possible to help protect myself to some degree for the uselessness of passwords.

Two-factor authentication essentially means that you use two authentication factors to log in instead of only one. An authentication factor is one of three things, something you know, something you have or something you are. A password is a good example of the first, while a card or cellphone is in the second category.

What this means is that for someone to hijack one of my accounts they will not only need to know my password but they also need my cellphone to generate a temporary one-time key to log in. While my phone can also be remotely tracked and locked down in case it’s stolen, and through backed up recovery keys I will still be able to access my accounts.

It might sound complex and difficult but it really isn’t, and the major security gain is a worthwhile tradeoff. To enable two-factor authentication you merely have to download an app (like Google Authenticator or Authy), use it to scan a QR code for the account you want secured and then you’re done. The next time you log in on a new computer you open your app, get a key to type in and you’re logged in as usual.

There’s a fairly comprehensive list of services which support two-factor here.