For a while now Kevin B has been working on writing a library for communication using the NRF24l01 radio with the Arduino’s. The idea is to use them for home automation purposes. But of course that’s only one piece of the puzzle… what good is home automation unless it’s also internet ready?
I took it upon myself to start looking into that portion, since it’s right up my alley (between server-side scripting such as PHP along with a database such as MySQL, and the API needing to working with Android of course).
As some of you may (or may not) know, by default apache2 allows something called “Directory Listing”. Essentially what this means is that when you visit your web server, if you browse to a directory within your www folder that does not contain an index page (index.php, index.htm, index.html, etc.), apache2 will actually spit out (or list) the entire contents of that folder. This should be a concern for anyone running a production server, and unless there is a specific need for directory listing its always a good idea to disable it. There is tonnes of different opinions on whether or not its a security issue to leave it enabled, and to this I have to say to each their own. Personally I feel it is a security risk, but at best disabling it is simply security by obscurity.
I stumbled upon a post on a blog run by David Lehman (NowhereLAN) the other day that caught my attention. It was regarding changing the page content area in WordPress’ TwentyFourteen theme.
Like David, I used TwentyFourteen as the base for my theme, and have been editing it to suit my needs. One of the things that bothered me was the excessive padding around the content area. As David points out in his post, its not so much a padding issue as it is the max-width set in the css file.
Today was time to install Google Analytics onto this blog. As you can imagine, there is far more than a “handful” of WordPress plugins to enable something as simple as GA Tracking.
I wanted to go for something a little more lightweight. Let’s face it, a plugin is a little overkill for two reasons. First of all, without tearing down into the source code of each plugin, you really don’t know what all its doing in the background. And second of all, Google gives you the Analytics code, so why make it harder than it has to be?
It recently came up where I wanted to force users visiting the IdleDev page to use a secure connection (https) domain wide (mostly for the development of Zero Day to ensure a secure connection is used at all times).
Unfortunately this was something that did not appear to be directly supported by my host. Luckily they do allow .htaccess and mod_rewrite, so from there it was easy.
By placing that text into your .htaccess file, and replacing “www.exampledomain.com” with your own domain, it will redirect the user to use an secure connection throughout the entire domain (essential for sending encrypted passwords, or any other data over the web that requires a secure connection).