WirelessPhreak.com

Mr. Robot, a show on the USA network is one of the most accurate representations of technology I have seen on TV. Hollywood has always dumbed down computers, coding or even technology in general, but Mr. Robot is changing the game.  Lets be real almost everyone in modern society is on a computer, smartphone or at the very least using credit cards. Much of the workforce use computers daily...Mr. Robot should scare the crap out of all of us.

The show's technological accuracy is extraordinary. The tools and techniques are hyper-accurate, and their use of social engineering really exposes what's going on in todays world. Sure the show feeds into some Hacker stereotypes with the socially inept black hoodie wearing main character, but it probably helps sell it to the masses.

Beyond the technology the acting, writing, and production stands on its own as one of the best psycho thrillers I have seen on TV. You are the imaginary friend made up by Elliot the lead character.  This immerses you into his world, and with House of Cards level inner monologue, you become an active part of his life. His paranoia becomes your paranoia as you are looking for clues or hints of whats going to happen next.

What should happen next? Everyone should watch this show. Mr. Robot shines a light onto real life events set in a fictional world. Evil Corp, fsociety these are fictional representation of companies and groups that are in our headlines every week. The genius of this show is its position to not only create this fictional world but draw on real life events as they happen, and I can't wait to see what happens next.

Links to other articles about the show:

• USA Network http://www.usanetwork.com/mrrobot?cid=ps_Mr-Robot__Launch_2015Q2_
• Wired Article http://www.wired.com/2015/07/mr-robot-fact-check/ 
• Forbes talks with Show Consultant http://onforb.es/1HiC4tN

For some reason I thought to myself it would be cool to have an emoji URL for my site. So I searched the web to see if anyone had done it before and, sure enough, an app developer named Panic registered 💩.la in 2011. After that, emoji URLs never really picked up steam.  There were a few tutorials - none of which worked. Then on February 23rd The Washington Post wrote an article about Coke's ad campaign in Puerto Rico using Emoji URLs. In response to The Washington Post article Kaleigh Rogers at Motherboard wrote a post outlining the brief history of  emoji URLs and how to register one.  The only thing she left out was which registrars allowed non Latin character URLs.  I tested Go Daddy and Hover neither of which would allow me to register my fancy new emoji URL.  Finally after searching the web I found a legit Domain Registrar that would allow the unicode URL: name.com.  There may be others but name.com was painless and simple.  Finding the Domain Registrar was the most difficult part of the process.

1. Go to punycoder.com and generate the unicode that you are going to register.

• The Unicode will be translated by the browser and present the emoji if your device and browser support it.

2.  Go to Name.com and search for the unicode string, example "xn--bw8h.tk" and register it.

From LARPing to competitive scrabble, here is a list of a few documentaries I have enjoyed on Netflix.

With HTML5 and other modern web technologies IE has not aged gracefully. If your client base is an enterprise many times clients are locked into an older version of IE, and aren't allowed to install an auto-updating browser like Chrome or Firefox.

This iRule is strait forward, I am redirecting clients accessing a website using an older versions of IE to a browser friendly version. This is done by evaluating the HTTP request and identifying the browsers user-agent string. As part of the redirect the F5 presents a web page that informs the users their browser is unsupported instead of blindly redirecting them. It will auto redirect after a pre determined count down, this example is set for 15 seconds.

Disclaimer Microsoft does not make this easy, Compatibility modes and Document modes in IE can send a different user-agent string.  For example IE 11 users running in Compatibility mode may still be redirected because their browser sends an MSIE 7.0 user-agent string. I am sure your could right variables that would check for compatibility in the user agent string, but iI chose not to.

Here is the iRule:

when RULE_INIT {
    set static::refresh_time 15
set static::notification_page {
        <html lang=\"en_US\">
<head><title>System Notification</title>
<meta http-equiv=\"Content-Type\" content=\"text/html; charset=us-ascii\">
<meta http-equiv=\"CACHE-CONTROL\" content=\"NO-CACHE\">
<meta http-equiv=\"PRAGMA\" content=\"NO-CACHE\">
<meta http-equiv=\"refresh\" content=\"15;URL=http://myspace.com">
</head>
<body>
<h1>System Notification</h1>
<hr>
<p>You are using an unsupported browser and will be redirected to Myspace.com</p>
<p>Wait $static::refresh_time seconds to continue, or click <a href=\"http://myspace.com\">here to continue.</a></p>
</body>
</html>
}
}
when HTTP_REQUEST {
 switch -glob [ string tolower [HTTP::header User-Agent]] {
   "*msie 10.0*" -
   "*msie 9.0*" -
   "*msie 8.0*" -
   "*msie 7.0*" -
   "*msie 6.*" {
     HTTP::respond 200 content [subst $static::notification_page] Mime-Type "text/html"
     log local0. "Client  IP:[IP::client_addr]  has been redirected with user agent :[HTTP::header User-Agent]"
   }
   default {
     # go to a default location if nothing matches
   }
 }
}