Yes, people of the internet, LastGraph has returned. After over two weeks of beta testing and bugfixing, it’s finally in a useable state, and so I’m pushing it out to lastgraph.aeracode.org as I type this. If it doesn’t work for you yet, wait for the DNS change to propagate.
This version will, inevitably, contain bugs, so I would appreciate it if any bugs could be emailed to lastgraph at aeracode.org.
There have been some improvements, such as much better error handling, reduced PDF sizes, faster rendering (and more render nodes), and detailed progress. There are still some missing features, though, notably the ability to set the plays threshold and to remove a graph from the queue (this will only be possible if you’ve provided an email address).
Plans for the future include custom colourschemes, more notification methods (jabber, and perhaps some kind of twitter reply thing). If you have more ideas, send them in to that address above (or poke me via one of the many methods found on the contact page).
LastGraph is still undergoing rewriting after the beta showed up some lovely bugs (including inverted labels and labels everywhere they shouldn’t be). I’m working on it over the weekend, after my week was overtaken by the sheer mass of activity involved with university and Fresher’s Week (I find it strangely ironic that it’s actually more timeconsuming this year, when I’m not a fresher).
I’ll give a progress report soon; hopefully I can clear up the fetching errors (Last.fm have also kindly agreed to let me access the API more often, so fetching speed should increase), and make uploading to S3 faster (aegis’ upload speed is somewhat limited, so it will be done directly from the render nodes themselves - this does somewhat scupper my plans for distributing the rendernode client, though, as they need my S3 secret key to do this, unless they can upload elsewhere and pass back an appropriate URL).
