The time has come to introduce the next major version of LiveStats. LiveStats is a web app that enables you to monitor your Site's traffic in real-time.

Since we launched LiveStats just 3 months ago, we've received an absolutely fantastic response with almost entirely positive feedback. We couldn't be more thrilled with your reactions. Over 1,000 Sites have signed up to LiveStats since launch ranging from small personal portfolio sites, up to the corporate sites of some huge institutions and companies. With the most recent updates we're confident we can push forward and develop LiveStats knowing we can serve every Site real-time traffic stats all the time.

We've said from the start that we won't be able to keep LiveStats free forever. On Wednesday, we'll be introducing some very affordable payment plans for the service. Purchasing a LiveStats plan will enable us to continue pioneering the real-time analytics market, and in return gain some extremely high end features from day one that aren't available with any other service.

We also wanted to take this opportunity to begin putting together a list of supported and unsupported services that LiveStats runs on.

List of Supported Services

• Any Self Hosted Site
• Tumblr
• Wordpress
• Squarespace

If you know of or are responsible for any services that can benefit from LiveStats (most services can), please contact us so that we can update our list of supported services.

Services we Cannot Currently Support

The following services do not allow you to embed custom javascript so cannot take advantage of LiveStats real-time traffic monitoring.

• Posterous blogs
• Facebook pages
• Twitter pages

We really can't wait to share more information about LiveStats 2. See you Wednesday.

James Gill, Geoff Wagstaff, James Taylor
A.K.A. The GoSquared Team.

It seems pretty clear that the future of Apple (and general human interaction with computers) is touch based.

Apple's responsible for kickstarting the touch screen revolution with the iPhone, so why would they do anything other than push themselves as far as possible along the trajectory they've already begun? When you consider the possibility of Apple building a device that not only sits alongside your iPhone, but replaces your MacBook, the game changes. Whatever Apple's tablet finally shows up as, I'm pretty sure it'll be more "this is the end of keyboard and mouse computing as we know it" than "oh it's a big iPhone".

Many people seem to assume that the keyboard and mouse are here to stay for the foreseeable future, and one of the main reasons they cite is that you can gain pixel level accuracy with a mouse and cursor. The tablet, if it becomes the MacBook replacement many have suggested, will not rely on finger input alone. Sure you'll never need anything more than your fingers (on both hands) to use the device, but I think there are a number of scenarios where using a pen or stylus (or whatever you want to call it) could be incredibly useful.

The Tablet is to Production what the iPhone is to Consumption.

Artists may not be the core target audience for the Tablet (or at least that's what I thought until seeing the invite), but when you consider how many creatives purchase Wacom graphics tablets, and that Wacom can can be the size of company it is through selling graphics tablets alone, this market segment is not insignificant. Perhaps my opinions are swayed being the graphic designer I am, but having a 10" Tablet that I could draw directly on with a beautiful aluminium pen would make my life considerably better - I could save a fortune on Moleskines.

With regards to text input, I don't think I should even begin to pretend I have worked out what Apple has decided upon. After 4-10 years of development time, text input on the Tablet could be a completely new concept, or (more likely) a very smart implementation of text input that we're already at least slightly familiar with. My guess is that we will see handwriting recognition in some form, and if so, likely not see an onscreen keyboard. Just as Apple encouraged the use of the mouse over the keyboard with the first Mac, whatever they perceive as the best method of text input, we will likely end up being forced to use.

As many have already pointed out, text entry on a 10 inch display is not the same as text entry on an iPhone-size display. The iPhone is designed to be used with one hand free, and only rarely requires both hands for efficient use. The Tablet will likely require both hands for operation at most times - one to hold and one to touch the screen when in portrait mode.

Read the rest of this entry »

Today we announce the second instalment in our series of GoSquared updates. This update has been in development since November and marks out a key milestone for LiveStats in terms of the service's under-the-hood architecture. LiveStats 1.2 introduces a completely re-written and re-structured tracking backend, geared up for blazing performance, lower latency, more accurate statistics and greater app stability. In short, the LiveStats 1.2 update launches us into the freedom of unlimited scalability, enabling us to take full advantage of the expansive power of the Cloud. Although there are no notable front-end improvements to the UI, the update allows us to scale our hardware horizontally and provide you with an even better service.

When LiveStats was experimentally released back in late October, we didn't have a great idea about how the app would perform under high load. However, thanks to a surge of sites implementing the service, we weren't in the dark for very long; we quickly discovered that the system in its initial incarnation was unable to cope with the load it was being subjected to. LiveStats 1.0 was hideously unoptimised, and was completely dependant on a sluggish database which was unable to scale to a high level of writes.

Something needed to be done quickly to tune the performance of the system so that it could hold for long enough while we worked on a different approach to the tracking architecture. James detailed these modifications in his post LiveStats - One Week On and that was the system we had been operating since... until now. So, what's changed?

Server layout

Previously, the system was bound to a single server running a single, slow and unoptimised MySQL database. Now it has been liberated by a horizontally scalable design in which any number of new servers running our custom AMI can be manually or automatically booted up as LiveStats "nodes" when other nodes approach their load limits. We developed our own internal API which empowers all of our servers to collaborate with each other in a conglomerated stack. Using this API, Sites are allocated to specific nodes depending on their size and resource utilization of each node, so resource constraints can be easily avoided, leaving LiveStats functioning quickly and reliably. In addition to this, we have moved our DNS hosting to UltraDNS for super low-latency, high availability DNS query resolution for all of our services, and also thanks to their API, granting our systems with the ability to dynamically assign subdomains to our server nodes.

Software

A major objective for the 1.2 rewrite was to completely eliminate reliance on the MySQL database. Data collected by LiveStats is currently not persistent anyway (apart from custom naming, more on that later) so there was no need for the use of a MySQL database when there are far more suitable tools available, like memcached. LiveStats 1.1 introduced partial memcached support which, along with closing the service as invite-only, relieved a considerable amount of load, allowing the system to just about hold out for this long despite still being database-bound. With LiveStats 1.2, each node operates its own native memcached instance with access to a large amount of memory, in which the real-time statistical data is temporarily stored. This way data is not delayed by arbitrary disc I/O caused by MySQL, and instead resides in memory which is extremely fast to access.

Persistent Data

For certain features like custom naming of visitors, persistent data is required. Memcached however is not a database, and a database of some sort is usually the best way to go for persistent data. While we haven't yet committed to a particular solution, we've been researching into a relatively immature technology: Key/Value databases, like Redis, Project Voldemort (used at LinkedIn) and Cassandra which is in production use at Digg and Rackspace. Currently we're using a simple implementation of Redis for custom names, although this is subject to change in the future once we take a closer look at persistent data.

Code

All of our backend code has been redesigned from the ground up to take full advantage of these changes in our system architecture. The way we handle our data has completely changed, and has been fully optimised with performance in mind. As such, we hope you'll find the requests in the LiveStats app load at consistent intervals with fewer delays. Furthermore, accuracy of the data has increased. In LiveStats 1.0 and 1.1, due to the database architecture and data propagation across databases, some hits would occasionally be dropped, or sometimes null or "ghost" hits would show up where incomplete information has been received. These problems have been eliminated and LiveStats now displays a very accurate reflection of who's visited and where.

Now that our capacity has increased, we will soon be distributing more invites more regularly. If you want one, ask us on support or twitter, it's likely you'll get one! As always, new software isn't perfect and there are likely to be bugs, so if you encounter problems, get in contact and we'll look into it.

Finally, just a quick mention of LiveStats 2; it is under development and introduces some really intuitive new features that we know you're going to love! More on this soon.

From all of us at GoSquared, we wish you all the best this year and we hope you enjoy LiveStats!

Geoff Wagstaff, James Gill, James Taylor
A.K.A. The GoSquared Team.

Welcome back to GoSquared - it's an exiting new year and we're pleased to kick it off with a small but helpful new addition to the GoSquared app line up: Site Manager.

Since we launched LiveStats we've had loads of great feedback from you wonderful members, but some of the same requests kept coming up: you wanted to be able to add and remove Sites in your Account easier and to be able to access and change the details associated with them without having to laboriously email us and complain about it.

With Site Manager, we've solved some of these common problems with a fairly sleek and simple to use solution. All of the Sites associated with your Account show up in the sidebar on the left, and you can see their details at a glance by simply clicking on each Site's Preview Image. You can change the name, description, and URL of your Site, and update the Preview Image in a handful of clicks. Your site's GSTC code is also available on the "Tracking code" tab, should you need remind yourself of what it is or how to embed it in your Site's pages.

A new feature we're introducing with this update is the ability for you to invite your friends to GoSquared. Many of you are using LiveStats within organisations (both big and small) and have asked if multiple people can view LiveStats for the same Site on different computers with different accounts. Now you can! Simply invite anyone you know by entering their email and you can share LiveStats for any Site in your Account with as many people as you wish. We really think people in teams working and developing on the same Site are going to love this - whether you're at the home or the office you'll be able to see who's on any of your Sites with LiveStats.

If you're signed in to your GoSquared Account, check out Site Manager here.

That's all for now folks, we hope you like it.

Peace,

James Gill, Geoff Wagstaff, James Taylor
A.K.A. The GoSquared Team.

Our elevator pitch with Hermione Way of Techfluff.

What a way to kick off 2010 - our first video appearance on YouTube.

Check out LiveStats if you haven't already, we hope you like it.