I’ve just finished moving my website over from WordPress to GitHub Pages. It’s something I’ve been meaning to do for a while now. Despite using WordPress for years, I’ve found it to be rather excessive for my personal needs as far as resource usage and maintenece goes.

Although I never personally had any security issues with WordPress, it’s definitely a high-profile target and switching to static content definitely helps mitigate some attack vectors. Not to mention the inherent load time decrease because of said static content.

Having already used Jekyll/GitHub Pages many times before, the move wasn’t terribly painful. There were a few ‘gotchas’ here and there, but with a little hacking, things were ironed out. I’ll probably post some of those solutions in later posts.

I took advantage of the migration to redesign the site and perform some general maintenece on posts and the like.

Additionally, all comments have been moved to Disqus.

There may still be a few quirks here and there that I haven’t noticed yet, but overall things are working smoothly.

So I’m about 8 months late to posting this. Granted, I’m quite behind on posting a lot of developments (sleep deprivation puns). Anyway, Seachem Doser is an Android app that I developed a while ago that serves as a “dosage/quantity calculator” for various products Seachem offers.

Seachem, for those who don’t know/have lives, is a company that offers various products geared towards maintaining freshwater and marine aquariums. Personally, I use a lot of their products for my high-tech planted aquariums.

They offer calculators on their site that allow you to calculate how much you should dose specific fertilizers, buffers, conditioners, the amount of gravel needed per a specific volume, etc. Sadly, these calculators are all Flash-based. So I decided to make one that’s a bit more flexible. I should note that all of the values for these calculations were pulled from their official calculators, after a bit of reverse-engineering. At first I just made a Windows-based calculator/library that you can find on GitHub. Eventually the issue of convenience took hold and I decided to make it mobile.

As of today, I just updated it to work on tablets and polished things up a bit since I had some free time.

As with the Windows version, the Android version is also open source on GitHub.

If you happen to be somebody who will find it useful, feel free to download it through the Play Store.



Recently, there has been an article circulating around with a pretty damning accusation. To summarize the post, they claim Dropbox is transferring data on the entire computer, not just folders that are designated to be synced.

This is clearly a bold accusation, with seemingly little evidence to back it.  This speculation is based entirely on filesystem events and unverified network traffic..yep.

At the time of writing this, the author has not disclosed what “unnamed DLP agent” software he is using nor has he provided any real evidence to support his claims.

Let’s explain the filesystem activity:

Just to run a simple test, I’ll be using Process Monitor and setting basic filters to check Explorer and Dropbox filesystem events.

After creating a new file outside of my designated Dropbox directory, you can see it fires filesystem events to query the file. In particular, QueryDirectory operations which involve checking the file path to see if it belongs to a synced directory.

I’d expect another culprit to the the shell integration. Personally, I don’t use the sync indicators myself, as I have other programs that use shell integration and it can cause conflicts. However, I’d imagine that the shell integration in Explorer requires the files/directories to be queried as well to check for sync status.

As for the network activity…the author has not even bothered to check the length of the data and compared it to the suspected files nor has he compared the timestamps between the two. Keep in mind that network activity from a program such as Dropbox is perfectly normal, how else would it be able to sync things in realtime?

So no, based off the limited (see: hardly any) “evidence” provided by the original author, it does not appear that Dropbox is transferring data outside of the designated dirctories.