Update: A commenter suggests using InsuFixer which simplifies this process greatly.

A few weeks ago Google Play started throwing an error the error "Insufficient storage available." I looked at my phone storage and saw ~4gb available. Annoyed, I googled around for fixes. Most forums suggest clearing caches, repairing permissions, or deleting random things out of /data/app. Of course, none of which fixed my issues.

I decided to poke around with adb shell to see what was going on and discovered a great tool that ships with the SDK called monitor.

Running monitor gives a live view (LogCat) of whatever is going on while the error condition is happening.

I assume you don't have android sdk on OS X so here are the steps, you can watch them too.

In this article, I’m going to show you a few methods to separate your public site from the vulnerable parts of your administration area. What you need is an effective way to keep your site locked and secure, and protected from attacks, while still leaving your site editable for trusted users.

Methods for securing the admin section of your site

One of the things that is often overlooked when setting up and securing a Drupal site is the administrative sections. Sure, Drupal protects these paths with access controls but you can do a lot more to protect your site, especially if your site doesn’t require public login.

If the public has no business accessing /user, they shouldn’t be able to. This path is an attack vector for denial of service (DDoS), brute force password guessing, and it drastically increases attack surface of the site.

Last weekend I gave my session at the second annual Capital Camp, as you may have gathered from my last blog post. It was really well attended, despite the attendance being down due to Metro track work. The session went really well, there were a lot of great questions and follow-ups. I'm still answering emails, actually.

I think this goes to show that not a lot of people are well-versed in what to do when faced with a DDoS. I hope that other people pick up the torch here and I'd be glad to help anyone that is interested. I also plan on advance-ifying the session for PNW or BadCamp.

Slides for OMG DDoS - Drupal lessons learned the hard way
Video for OMG DDoS - Drupal lessons learned the hard way

You never know where and when you might land your dream job working at Twitter, Google, GitHub, the White House, etc.

Modern web browsers put a cap on the number of connections they make to a host. This means if you've got a lot of assets on one hostname the browser will queue the remaining assets, while the ones in front download. This is referred to as blocking.

One way around blocking is to create multiple subdomains, for instance, assets0.davidstoline.com and assets1.davidstoline.com to increase the number of resources downloaded in parallel. This is method is called domain sharding and it is recommended by both Google's PageSpeed and Yahoo's YSlow.

I can't exactly afford a high quality CDN like Akamai but I can still leverage some of the benefits and fun of using a CDN. My friend Wim Leers wrote the Drupal CDN module, which you can leverage to do a little home grown sharding of your own.