Website security is something that every single webmaster has to worry about during their endeavours, nobody is entirely safe from the big bad world of hackers the internet has become a safe-haven for. Whether you have login credentials, some sort of information pertaining to accounts or even location information, all of this stuff is up in the “virtual air” to be grabbed by somebody whom is sinister. People might find themselves in need of support when it comes to securing their websites, which is why this article has come to fruition. When it comes to securing the likes of your important information (whatever kind of information it may be), there’s a few different things you can do to improve your website security protocols. When you’re worried about your information being stolen or tampered with in some way, shape or form it’s going to leave a sour taste in your mouth. There have been numerous technological scares regarding security breaches recently, the most recent one being the whole “Heart bleed Bug” debacle. Even though people are well aware that their information could be stolen at any given time it seems as if they don’t make the changes needed. People are still shopping online with their credit cards, leaving their information out in the open just waiting for somebody unethical to get their hands on it. Not every single site is going to operate like this, and not every single site is going to be entirely flawed when it comes to its security; the fact of the matter is that hackers do exist, and they are stealing information from people (online fraud is rather prevalent in London).

Something you might have seen plenty of times is actually doing a wonderful job of treating this “virtual plague”, have you ever been to a site and noticed a little padlock in the URL? This means that the site is entirely encrypted, the information that is being used on the site and sent to other resources is entirely untraceable. This leads to the information being harder to maintain by hackers, which of course is a good thing! If you don’t see this peculiar little padlock in the address bar of the website you’re on, don’t take any chances with the transfer of information. This means that any shopping sites or anything else along the lines of that (as in sites that require personal information, most of the time it’s important personal information) that don’t sport the padlock shouldn’t be trusted. The padlock is simply an SSL certificate, which is something webmasters all across the globe should be getting their hands on. Not only will it give the customers some peace of mind, but it will also give your site another piece of “legitimacy” to add to its traits.

How Might you use HTTPS

So now that you’re aware of what HTTPS is, it’s time to learn how to actually implement it within your site. The fact of the matter is that HTTPS only works if both communicating parties are making use of it. When it comes to the client side, the HTTPS selection can be made by simply typing “https” (as opposed to the original http) into the address bar before you type in your URL. Another way to implement it would be to install an extension on your browser that forces every single site to load in HTTPS (there are plenty of add-ons available for this, one of the more common ones being “HTTPS Everywhere” as it works for both Firefox and Chrome). When you’re using HTTPS you’re going to know it, there should be some sort of indication (whether it’s a green bar, a pad lock, a thumbs up, etc.) in your address bar. One thing to keep in mind is the fact that HTTPS can only be used if the web server you’re connecting to supports it, if you’re the one who wants to make HTTPS available to your website users than you’re going to need to go down a different path (as that would require an SSL/TSL Certificate).

SSL/TLS

If you’re a webmaster and aren’t completely sure as to what SSL is that’s alright, but it’s crucial that you learn about it sooner rather than later. When you’re using the web the data is transferred with the use of HTTP, which is Hypertext Transfer Protocol. This process is the sole reason why every webpage starts with either “http://” or “https://”. If you aren’t sure why the “S” is added onto the latter, than you’re about to have your mind blown; it’s strictly for security. HTTP isn’t a particular part of the URL itself, it’s actually the language that is used between the computer and the server to communicate. The language itself is “universal”, so it’s essentially used all across the globe for every single web-sever communication process completed. This is convenient in a sense, but it also has its cons (as anything positive usually does). It doesn’t matter whether you’re in London or Africa, the chances of you stumbling across the HTTP term is almost set in stone. There are three particular cons that come with the HTTP server communication process, those being:

People have the ability to intercept the data being transferred and “eavesdrop” on your activities.

People can intercept the data and then pretend to be you from the initial transfer process.

People can even change up the data being transferred so the message that is communicated isn’t the one you had originally intended.

Hackers tend to use a combination of the three exploits above to get into your transfer processes and learn more about you, from there they can do whatever they please with the data they’ve obtained. This means that if you were to transfer data regarding your bank account (or credit card) and it was intercepted, the hackers could have access to your personal finances. Scammers make relevant use of these tactics as well, a perfect example would be the “switcheroo”. Let’s say you’ve transferred a message stating you want “$100 to be paid to my phone company”. A hacker can take this information and mould it to their benefit. It goes from the original message to “$1,000 to be paid to my good friend, Hacker”. It’s as low-ball and sleazy as you could get online, but just like everything else on this planet there are people who do it. All of these problems (and even more) could be solved with the implementation of an S, turning the HTTP server into an HTTPS server.

The S is actually derived from the SSL protocol (Secure Sockets Layer), or even from the newer process known as TLS (Transport Security Protocol). HTTPS servers are ideal for webmasters who like to keep their information private, the service automatically encrypts information so that hackers can’t get their grubby little hands on it. On top of that is also offers server authentication and message authentication, which is there to ensure that the person using the site really is who they claim to be. This is the type of support that brings tears to my eyes!

How Can I Get an SSL Certificate?

If you want your own webpage to have HTTPS available to users you’re going to need an SSL certificate, but what if you aren’t sure what it is? Or even how to go about getting one? Your web server has to have the SSL/TSL Certificate installed on it in order to be “secure”, think of it as a form of ID for your website. Whenever there’s a browser making use of HTTPS on your website, it goes through a communication process similar to a handshake. The client computer (the user on your site) asks for your SSL/TSL Certificate before they make the connection, if you’re a trusted webpage and have these certificates implemented they will be able to progress to your page. This process is simply there to verify that the user is actually the user, and the web server is secured for the clients use. Most well-known companies make use of SSL/TSL Certificates as it adds a layer of reputability, it’s always nice to be known as the “safe site” when it comes to your user base. If the SSL/TSL Certificates don’t check out, or the site simply doesn’t have one, your browser will warn you that the site might have something up its sleeve (your browser will warn you that the identity of the site couldn’t be established). We’ve all gotten those warnings from random sites on Google, so it isn’t anything particularly new.

Doing Your Research (SSL Certificates)

When you’re getting into the final process of implementing an SSL Certificate on your site there are plenty of things to look at. The CA (Certificate Authority) would be one of the main variables to take into account. This is the company that will actually give you your certificate, they will also be the ones that actually validate your security every time a visitor makes their way to your web site. Each SSL provider is going to have their own way of doing things, the prices and features are going to vary as you look at different companies. Although this is the case there’s only one thing you should really be worried about when you’re getting the SSL certificate, which would be the question of whether the certificates are pre-installed on the most common browsers available. If your certificate company doesn’t have a compiled list of the browsers they have SSL Certificates available on than users are going to get “false warnings”, which is never a good thing. Many people don’t bother with false warnings, they would simply see the initial warning and think that the site was bad news no matter what.

Although sometimes your certificate isn’t going to be listed on the major browsers “set list”, it usually doesn’t happen. The major browsers have massive lists regarding pre-installed CA’s, so if this happens to you chances are you didn’t select the proper Certificate provider. If you’re making use of the larger brand names (GoDaddy, Thawte etc.) than you have nothing to worry about. If you still aren’t completely sure you can actually check your browsers settings and see which pre-installed CA’s are available, here’s how to go about doing that:

The use of an SSL Certificate is supposed to help identify the website you’re sending your information to. You’d be surprised to know that plenty of people make use of “phony” SSL Certificates for domains they don’t even own themselves. This is where the CA (Certificate Authority) comes in, as they make sure that the person whom is demanding a certificate for the site is actually the domain names owner. The easiest way that this is accomplished is through either an e-mail or a phone call, the first option containing an account confirmation link for you to click on. Many don’t know the term for this, but it’s actually a domain validated SSL Certificate. The greatest thing about this entire process would be the fact that SSL certificates can be issued to sites much quicker than they usually would, to be honest you could probably get your domain SSL Certified quicker than washing your care would be. The SSL Certificate would allow you to put that extra little touch on your website, encrypting the data and giving you that padlock of reassurance.

When it comes to domain validated SSL certificates they have their pros like any other. They are much faster and a lot more efficient, they’re also quite cheap to obtain. Although this is a positive, this is also a con as well. When you put an automated system into place (which is what the cheaper types usually are) it could allow for a little more wiggle room regarding hackers, after all they are pretty smart to begin with. It’s best to have your SSL Certificate service ran by humans that verify credentials, automated services can be duped more often than you would think. Phishers make use of this process when it comes to automated SSL certification, it’s pretty much like obtaining a fake identity to use for sites. They could take your name and such and open up a PayPal account, maybe even a Facebook account if they were feeling somewhat social. Phishers have created websites to look like they were any other, secured and everything of that sort, yet they’re still able to obtain your information through the data transfer process. Obviously these types of scams would be rather blatant and easy to see if you were a human, robots have a harder time deciphering between the two.

In order to combat these particular “openings” in the SSL and validated SSL Certificates, there has been a new standard introduced amongst the industry. It’s known as an “Extended Validation Certificate”, which is useful for specific reasons we’re about to go through. If you want to get an EV certificate you need to pass a checklist first, you must have a company (or an organisation of sorts), there’s also an incredibly draw out process on top of that. You need to make sure you’re government is aware that you control the domain, as well as put in an application to make sure you have a good relationship with your local governors (you need to be reputable in order to qualify for an EV certificate). These go through a human verification process, so it’s going to take a longer time (as well as cost you more money in the long run).

Some people may be in need of an EV certificate simply because it’s the industry standard amongst their project. If this isn’t the case though, you should take into account that the only benefit pertaining to EV certificates is what the visitors can recognise. If they are just an everyday browser than the difference between your site and another are very minimal. Not only would you receive a padlock icon in the address bar but the entire bar turns green and actually has the name of your company on there. From there you can see that the company itself has been completely verified through and through, which is always something nice to put in the trophy case!

Remember, an EV certificate might not even be worth your while if you aren’t in a particular industry. If you aren’t the owner of a business or an organisation you can’t even qualify for one, this is something that the much larger companies usually look into. Even though EV is somewhat useful, most of the HTTPS sites we come across today are actually non-EV. I guess plenty of other people don’t see that much benefit in the EV certificate either. If you aren’t completely sold on either of the certificates we’ve talked about so far there’s one final solution left for you, which would be the “organisation validated certification” (sometimes referred to as the “business validated certification”). It still goes through a process of domain validation that is much more thorough than the automated one, but it isn’t quite as thorough as the EV certification process. When you’re looking to get a business validated certification it’s going to cost you more, as well as take a longer time to go through, yet it doesn’t give you the green address bar (or even the verified company info). It’s somewhat pointless, which is why many people tend to stay away from this option, I know I do.

Private SSL vs. Shared SSL

Webhosts usually have a shared SSL service, which tends to be better for those who are economically efficient (aka cheap!) than the other option, being private SSL. The price is one things to look at, but shared SSL’s also have no need for a dedicated host or private IP address in order to properly function. You may not get to use your domain name in its entirety, but that’s what happen when the term “you get what you pay for” comes into play. If you’ve got a site that is in the public facing field (such as a social networking site) then this is obviously a rather large blow to your online presence. It appears as if you’ve been redirected from the main site, which is never something a webmaster likes to see! Shared SSL is ideal for other areas though, things like an administration area or even an online mail system.

Many CA companies actually let you place trust seals on your webpage if you’ve been confirmed for one of their certificates. It gives you the same type of information that you would usually be exposed to by clicking on the padlock, but it’s always nice to have something visually appealing to back up your credentials. The trust seal itself isn’t exactly necessary, as it doesn’t do anything to boost your security (but it will leave your visitors with that gooey, gushy feeling they get inside whenever something reputable is presented to them!).

Identifying your domain is important, but many people are interested in verifying multiple different subdomains as well. If you wanted to achieve this, you would actually have to purchase three different certificates, that’s just the way it is! There is a point, however, where the choice is based solely on your finances (in which case a wildcard SSL certificate is ideal). One certificate to cover all of your subdomains really is a dream come true. CA’s can be as reputable as they come and still be vulnerable, it’s just the society that we live in today. Hackers are vicious, and with every technological advancement we grow with they grow with as well. The perfect example of a massive CA being targeted by hackers would be the breach VeriSign had to deal with in 2010, although that went unreported to the public (which sounds kind of shady, oddly enough). On top of being vulnerable there are also reputable CA’s that join the dark side in a sense, which was seen in 2011 when DigiNotar bit the bullet. Anything to do with SSL can make somebody uneasy, it’s the fact that they could be playing with personal information that really bothers me. Due to this, CA’s have certain warranties in place to compensate those who deal with any SSL attacks (or anything that would fall along the lines of that). There haven’t been many stories regarding SSL claims and such, but nevertheless they are there to be purchased if you feel the need to do so.

How to Install an SSL Certificate

The actual installation process of the SSL Certificate is somewhat of a mystery to a few people, it’s important that you properly install it on your website in order to actually be authenticated. Webhosts that are reputable and of the higher quality tend to do this for you, but if you find yourself in the situation where you must deal with it yourself there’s no need to worry. Some of the better webhosts actually take it upon themselves to purchase the SSL Certificate for you, which is obviously just the cherry on top of everything. Although these are usually the cases you might find yourself in the position of installing it yourself, which isn’t always the easiest thing to do for certain people. It’s a rather thorough process, so it’s recommended that you ask your webhost for help, but it consists of creating a SSL CSR (Certificate Signing Request) amongst other things.

Advantages and Disadvantages of HTTPS

There are plenty of pros and cons to take into consideration when it comes to the HTTPS argument, but everybody seems to be completely content with the service so far (every website you visit that is authenticated and verified is usually sporting a HTTPS URL). Although there are some downsides to it (the fact that it’s more expensive, the fact that is could slow down your server, as well as the fact that it could have a drastic impact on your SEO endeavours), it’s still the best we’ve got available at the moment. Many people tend to just lean on PayPal or any other online payment-processing company to handle their business, but there are those who like to keep everything “in the family” so to speak. If you’re one of them I can’t blame you, there’s no shame in getting the hang of SSL Certificates, I’m sure it will benefit you in the long run. If you’re still having troubles you can try Sphere IT who are an IT Support and Services Company based in London.

It’s been quite some time since we’ve been introduced to a brand new group of TLDs (Top Level Domains). A few months ago it was decided that we should be “blessed” with these brand new extensions of domain names, and it turns out they could be potential game changers. The amount of new TLDs available to you this time around is pretty astounding, so astounding that it might even call for a brand new strategy to be implemented on your part (in the end it’s all about protecting your personal interests). It’s no surprise that people have always tried to sell their TLDs to consumers, they would say things like “You absolutely need to hop on the .example train right now”. Although many people in the world aren’t going to question the legitimacy of these new TLDs, there may be some that do (me being one of them).

Every time a TLD appears out of nowhere there needs to be a reason for its defence, plenty of them seem like they’re simply “fads” in a sense. Some are definitely here for the long haul, one example would be the introduction of the .CO TLD (which is almost always used as a misspelling of .COM, for example a really good one would be Goggle.co for those who can’t spell). Of course the .CO representative aren’t going to state that it’s for the “typo domain” market, but we’re smart enough to piece these things together for ourselves. On top of that there were some that simply were shunned, for example .XXX (which had adult webmasters scrambling to their computers to try and get their own .XXX domain). Some of the TLDs available are simply forgotten to say the least, some of these would be .TEL or .PRO (in which many hosting companies have dropped support for, but nobody cared). With all of this being said there’s a new batch of TLDs for us to sink our teeth into (as well as judge for ourselves), and those TLDs are: .EMAIL, .GURU, .HOLDINGS and .VENTURES.

Defending Your Territory Will Be Nearly Impossible

Seeing as there are too many TLDs coming out in the near future (some have said that we should be within the thousands sooner than we would think), the price is something to leave to the imagination as well. These newer TLDs are not only more expensive than the common .CA or .COM, but they’re brand new; how many people are going to be looking to get into them? We’re already used to the ones we’ve got now, and some of the newer ones are plain silly in my personal opinion (the perfect example would be .WED, seeing as it has strange rules and guidelines based around it; did we mention it’s $25,000/year for a two year project?). It’s a good thing I’m not the only one who finds this ridiculous, as plenty of registrars are refusing to support these new TLDs (like I’m about to pay $25,000 a year for a .WED domain!).

Although most of them are relatively silly, there are a couple of brand new TLDs for you to keep your eye on in the near future. One of the better ones would be .WEB, it’s simple and to the point and is one of the ones that isn’t completely absurd. Although I could easily see myself with a .WEB domain, the bids for them are rather competitive right now (and there are even a few law suits associated with it).

One of the better ones to look at besides .WEB would be .CORP (which of course would be rather useful for businesses). People have stated this TLD is going to “break the TLD world as we know it”, which may be a bit over-exaggerated.

How Should We Feel About This?

There’s no denying the fact that time is going to move forward, and with that process there’s going to be newer things introduced to the world of technology. Even though there’s no telling when TLD expansion is going to “die”, it’s definitely not as powerful as t could be in the current day. Every single TLD is going to tell you that you need it, they’re also going to tell you to purchase a domain as quickly as possible before you miss your chance. If you have any smart bones in your body you know how business works, and for the most part these rather atrocious TLDs this year just seem like schemes. You can simply register the TLD you feel that you will need (whether useful for your company or to simply protect your brand) via a registrar such a GoDaddy, or 1 and 1 to mention a few.

It’s something like the spike of “crypto currencies” we’ve come to know, things like Bitcoin and Litecoin, etc. People are taking the Bitcoin block chain ledger model and are creating their own versions of bitcoin. It just goes to show you that if something has worked in the past, there are going to be people whom pursue it (sometimes so much so that they saturate the market). There are a plethora of “coins” available now, it seems as if there might even be too many. The creation of DAC (Decentralized Autonomous Corporations) with block chains and naming proves that innovation isn’t present within ICANN approved TLDs (the newest ones that is).

Which TLD Should I Register As My Own?

Picking the proper TLD to register your name under can be kind of tricky, although there are techniques to it. If you want to be proficient my only suggestion would be the Frank Schilling model, which consists of you purchasing a .com (or .net/.org domain) alongside a ccTLD pertaining to the country your base of operations is in. After you’ve done that you can expand and improve your TLD selection, particularly some city-based TLDs (one example would be Toronto with the TLD of .TO).

If you’re a webmaster you may have found yourself in a similar predicament, as many webmasters these days aren’t complete sure as to what the difference is between a 302 redirect and a 301 redirect. Search engines are able to tell which type of redirect is actually occurring, so if you’re in the business of search engine optimization (SEO) than this is something rather important for you to know. When you talk about the 301 redirect, it means that a page is being move from its original location to a whole new one (this is a permanent state of relocation). A 302 is different, as the redirection of the page is a process that is temporary rather than permanent. Search engines make uses of these in a peculiar way, as it determines whether the old page is going to be kept or if the page is going to be replaced with the newly relocated one. If you set up the wrong type of redirect for you page it could lead to some confusion regarding the search engines process, which means you are going to see a drop in the number of visitors to your site (loss of traffic).

You may not think that it matters much, but it has a very important role to play when it comes to being a webmaster. If you find yourself in the situation where you’re going to be completely moving an entire web site (for example changing your companies domain name) you’re going to want to have the right redirect set up to allow users to find your site. The redirect will allow the browser of the user to automatically take you to the new location from the old one. When it comes to the bigger search engines like Google and such you probably think that they have the ability to follow these redirects, but it isn’t that simple. Whenever you’re moving a site with the use of a redirect it has the possibility of inflicting the Google aging delay upon your page, this means that your site has the possibility of dropping off the page ranks for a long period of time (sometimes months, and in extreme cases up to a year).

301 is the most common redirect you’re going to see, this is because the 302 redirect in its own right calls for certain circumstances. If you find yourself temporarily moving pages for a long period of time than it’s probably the right choice for you (although people usually find themselves moving pages permanently). Even though this is the case most people would tell you that the process of a 302 redirect is a lot easier to manage than a 301 redirect. If you wanted to you could make use of Javascript (or even a meta tag) to create your 302 redirect. When you want to make a 301 redirect you have to have special commands handy within the .htaccess file (if you’re using Apache that is). If you’re making use of Windows Servers than 301’s can come off as even more unappealing due to the difficult process of creating them and lack of support available. This is the sole reason why people make use of 302 redirects when they should be using 301s.

Google is able to tell that the use of 302 when a 301 should be implanted is there, but it isn’t in their ideals to take people as literal as they are trying to be. They really don’t have to legal authority to look at it as a 301 when it’s a 302, even if you had meant it to be a 301. If you make this mistake the search engines might index older versions of the site instead of fresher and newer ones you have available. The popularity of your links could be potentially divided by two different URLs, which would of course hurt you in the rankings. Some search engines may have the ability to figure out the woes of the 302 redirect, but they also might not. Google representatives have stated that 302’s will be treated as 301’s if it seems like the webmaster had made a simple mistake, but is this their mistake to fix? What about other search engines as well?

If you’re going to be moving a web site or web page on a permanent basis, than you’re going to want to make use of a 301 redirect. 302’s should never be used in a situation like this, it’s just improper practice! When you’re making a temporary move related to your page a 302 redirect is going to tell the search engine to index the old domain/page rather than the new one (and you’re obviously going to want the newest page available to the search engines index). People have the tendency of using 302 redirects to battle the Google aging delay, and although it may have worked in the past, isn’t very sound to do right now.

If you’re worried about losing your search engine rankings due to a 301 technicality, nothing is going to be fixed if you change your domain (or even to so become non-dependent pertaining to your page ranking income). Businesses have always tried to avoid changing their names because it could lead to a whole world of trouble, not only marketing wise but reputation wise. People could deem it shady of sorts, it just so happens that Google shares the same morals.

Facebook has always been one of the main components of social interaction online, ever since it was introduced people have been completely aware of what to do with it and how to do it. One thing we always forget to ponder is “what happens to my social media account when I pass away?”. As terrible as it sounds, death is inevitable, no matter who you are or what you do for a living you’re going to die eventually. It may take 20 years, it may take 200, but it’s a known fact in our “physical world” that you’re going to leave this plain at some point.

This leads us the actual topic of the article, dealing with deaths on Facebook. Facebook had a pretty strict ruling with dead persons profiles the past few years, but now they find themselves rethinking their strategies on the topic. Whenever a Facebook user passes away the people whom are mourning their loss could ask Facebook to memorialize the persons account. When this happens, only friends and family are able to view the actual profile. Pretty much, it’s for those who actually cared and will miss the person instead of random people hearing about the event. This is changing though, because on Friday Facebook is going to allow the public to see people whom have passed away accounts.

They feel like it’s the best choice, having the persons life available to see for those are intrigued. I guess it’s a good thing, because it allows for more people to hear and see what had happened, as well as more people to mourn the loss that they’ve had to deal with. If an account you frequent or even an account of a close friend has been memorialized recently you will see the changes soon enough, every single profile that has already been “tamed” will resort to these changes by the end of next week.

This gives a whole heap of ideas to those who have been thinking about it, one site (eterni.me) is actually implementing a way to talk to deceased relatives and loved ones like a “Skype call from the past”. They take any information provided about your loved one and then transfer all of that information into the avatar that they build. From here, you have a full-fledged conversation with someone you haven’t talked to in over 5 years. This sounds kind of strange and even sounds like it could break some heart when it comes down to it, but it’s a pretty cool site to take into consideration nonetheless. Of course with all of this being said Facebook is going to ponder what they should be doing when it comes to the memorialisation of a Facebook page, which they consider as long as possible.

Apparently as of recent people have been saying that the mastermind company Google is trying to produce something we aren’t used to seeing. A smart phone isn’t too crazy when it comes to the developing of it, but one that views in 3D? That could take some getting used to. The technology giant has been rumored to be looking for developers who are willing to develop unique and “unusual” applications around its new platform. It’s known as “Project Tango”, and as of now it seems like it’s going to be a pretty crazy experience when it finally comes out.

The whole idea of “Project Tango” came about when developers at Google decided to give mobile devices a “human-scale, understanding of space and motions”, which is a direct quote form the main man himself Johnny Lee (he’s the projects lead at Google’s Projects group). Many people have been curious as to how this is going to pan out, because not everybody is completely down for 3-D screens as silly as it sounds. Johnny Lee was saying how people consider the phone to finish at the screen, but there’s always room for more development.

The whole point of moving forward in life and time is to see what happens and plays out on the worlds stage, 3D screens on phones is a pretty cool thing to look out for though. We haven’t seen a lot of 3-D technology being implemented in mobile devices, although we have been seeing it quite often in the television field.

The options are immense when it comes to the implementation of a 3D screen on a smart phone, from getting the dimensions of a couch you plan on buying before you actually buy it to finding the aisle and exact shelf where a product is located in a store. The screen itself could change the way we look at phones as a whole, because a 3D screen would open up so many doors when it comes to talking about the development of new applications and such.

The prototype that they’ve got ready at the moment is a 5-inch smart phone running Android, which in my personal opinion is better than the iOS. It combines this alongside the robotics and computer vision technology implemented within the phone, which is used to track the actual 3D motion of the phone (while creating a 3D model of your surrounding environment in the process of it all).

Google has said that it hopes professional developers take the opportunity to get into something new and unique while it’s still fresh, Google also plans on releasing approximately 200 development kits to those who need it by March 14th. If you can wait to gets your hands on one of those development kits, you’re going to have to keep patiently waiting until March rolls around. There’s no specific release date at this time, but believe me, we’re looking for it just as much as you are!