whateverthing.com

☰

I've created a new Sculpin extension called "Icelus". You can use it to automatically generate thumbnails of images on your Sculpin-based website or blog. I chose the oddball name because Icelus is a genus of fish otherwise known as “Scaled Sculpin”, and thumbnails are scaled images (it's imaginative, dammit!).

For those who haven't heard of it, Sculpin is a static site generator like Jekyll or Octopress (or many others). Instead of acting as a dynamic application on a web server, it takes your blog posts or website pages and outputs them as a set of simple HTML files that can be hosted on any web server.

Cyberspace. The freshest frontier.¹

These are the voyages of the cybership n00b, on its continuing mission to seek out new synergies and explore new business relationships. To boldly go where no information security model has gone before.

If companies don't smarten up and start taking security seriously, they might find that the tech frontier can burn them worse than they can possibly imagine.

This is what happened to Sony Pictures². This is what happened to Lenovo³. And if it happened to those companies, it can happen to yours.

There are a few things your company can do that might help prevent a catastrophic embarrassment.

It's no secret that I'm a fan of the Twig templating system. I like the syntax and flexibility far more than Smarty, PHP Templates, and other solutions I've worked with. I also like that it has minimal outside dependencies, so I can quickly add it to any project.

One of Twig's more interesting features is that it converts template files to PHP classes. This can really save processing power, because it only has to happen once and future references to that template can just invoke the saved PHP class.

However, if you forget to enable Twig caching, the compiled PHP classes are discarded after each page load - this burns a ton of resources and slows down your site.

Enabling Twig caching only requires a few magical incantations, and as luck would have it, I'm happy to demonstrate two common scenarios.

It started with a simple question:

Ever come across a suspicious short URL and wanted to know where it really goes?

I'd just encountered one too many bit.ly links, and decided that I wanted to know where it went before I clicked on it. It's a simple exercise to find out (you can probably do it in one line in Linux, for example), but I thought I'd use it as a way to learn something new.

AngularJS is a framework for single page web applications, and I've been wanting to learn a bit more front-end technology for a little while. Anything to give my javascript knowledge a boost would be helpful, too.