the white stuff, part 2

Looks like the Daily Stormer (neo-Nazi white supremacists and KKK website) was booted by their hosting provider GoDaddy on Sunday for violating its terms of service after an article regarding Heather Heyer was published on the site.  The former then transferred their content to Google Domains (Monday)… after which Google booted them as well for the same reason around midnight of that same day.

After a day or two of being offline, the site appears to have surfaced again in the “dark web” of the Tor anonymity network.  (In Harry Potter terms, they lost their lease on Diagon Alley and were forced to move to Nockturn Alley which seems to suit them better.)

The Dark Web

As if the Internet itself weren’t scary enough in the light of day sometimes, we now have an even darker, hidden version of it which is only accessible with specialized software.

Dark web: that portion of the web which cannot be easily reached from the public Internet, and usually requires specialized software to access. Examples of the dark web are the Tor network and hidden services, the I2P network and its eepsites, and the RetroShare network.

Almost sounds like a stroll in the woods when you say it like that.  Only this would be the Black Forest or the Forbidden Forest or the Suicide Forest maybe.

Onion Routing

But how does one attempt to navigate in such a place?  It looks like communications are wrapped in layers and layers of encryption much in the same way that onions have layers.  Each network node in this communication either adds another layer or peels one away, depending upon its direction.

Oddly enough, this method was developed by the Navy to protect U.S. intelligence communications online back in the ’90s.  I suppose it’s sad when your own tax dollars eventually provided the means by which child pornography, for example, enjoys its anonymity on the dark web at this time.

unseen complications

Don’t you hate the unseen complications that rear their ugly heads somewhere down the line?  Today’s drama involved the inclusion of a very cool fullscreen api by Vincent Guillou.  Of course, it worked great in development and then failed silently on production.  Here is an overview of what makes my production site a little different.

Production Site Overview

GoDaddy domain name hosting with option “forwarding with masking” —>—based hosting site

GoDaddy does this technically by serving up a single HTML page which simply frames the remote content.  By its nature, it uses the HTTP protocol and cannot use HTTPS. In its configuration it allows you to set either HTTP/HTTPS for the framed content, however.  You’d think that you would have plenty of room to make something work. And it did work just fine up until the latest add to the project:  a button which allows the browser to go full screen and back again.

Unfortunately, the first push to production then failed silently. The button was there but didn’t seem to work. Entering the development area of the browser I saw that the browser had to block the content because the framing page was HTTP and the framed content was HTTPS and this isn’t allowed.

Okay, so I thought I could then adjust GoDaddy’s settings so that I could frame the content as HTTP to match the parent document. Unfortunately I see that Firebase always uses HTTPS and does not support HTTP. Since I can’t mis-match the content and combined with the fact that I can’t easily promote GoDaddy to HTTPS on the framing page or demote Firebase on the framed page, I was screwed.

To make a long story short, I either had to pay for hosting at Firebase (which allows you to bind your domain name to their hosting server) or I could abandon the cool  feature. Since I’m trying to highlight the cool new features of the latest browsers I decided that’s it’s better to just pay Firebase in this case.

It was still a bit technical in getting all this to work since Firebase only bound a single entity (www) to the website using my domain. This means that if someone just puts in my domain name only then they’re stuck at a GoDaddy-parked page. To work around this problem, I set up a redirect to deal with this situation. This time it looked like: -> Problem solved.

So now, the cool new feature is working on production and the implementation is slightly simpler, not that anyone else would necessarily know.

use your domain name not theirs

There are times when you want to use a service provider like Gmail, WordPress, Firebase, Heroku or OpenShift but you don’t necessarily want to keep advertising their domain name with your business, blog or website.

Converting to

This one is easy enough, assuming that you know your way around your domain registrar’s configuration.  I usually park things at GoDaddy these days so I’ll use them as an example. Likewise, I’ll assume that you have a free mailbox at Google’s Gmail.


  • Mailbox:
  • Domain:
  • Registrar: GoDaddy


  1. Write down the collection of email entities that you would like to forward to your mailbox
  2. Log into GoDaddy, visit the Manage My Domains page
  3. Choose the Manage Email link associated with your domain
  4. If you haven’t already, setup email forward for your domain
  5. Choose the Create Forward link
  6. Type in the first email entity from step one above, for example, support
  7. When you type the @ symbol you next get to select
  8. In the next field, enter your mailbox name of
  9. In the next field, choose the Free email forwarding with domain:
  10. Click the Create button
  11. Repeat for each of the entities you’d like to be:,,, etc

It’s best at this point to wait a couple of minutes and then send a test email out to one of these entities to see if it arrives into your mailbox.  Once you’ve verified that it works you may begin to use it confidently.

I routinely create multiple mailboxes for notification apps so that they can have their own email queue.  Again, email forwarding hides the Gmail mailbox name.

Converting to

Again, this is easy enough using a feature called forwarding with masking.


  • Blog:
  • Domain:
  • Registrar: GoDaddy


  1. Log into GoDaddy, visit the Manage My Domains page
  2. Choose the gear icon associated with your domain and then choose thee Manage DNS link
  3. Choose the Settings tab
  4. Under Forward -> Subdomain choose the Manage link
  5. Click the Add Subdomain Forwarding button
  6. Enter blog as the subdomain
  7. Select http as the protocol
  8. Enter in the next field
  9. Select 301 as the Redirect Type
  10. Under forward settings choose Forward with Masking
  11. Click the Add button

Give it a couple of minutes before giving this a try to see if it works.

The same technique works for your website.  For example, I’m hosting a website at, another at Heroku, yet another at, etc.  Each of these hosting providers would probably love it if I allowed the world to see their domain name in the URL.  But I’d rather not since that’s free advertising to them.  Don’t these examples look better? -> -> ->

Honestly, domain names cost you year after year.  You might as well take advantage of the many free services which are included with your domain registration.