Moving Forward for Tweekly.fm

In January this year when I first undertook the Tweekly.fm project in ran in a very different way than what it does now. I’ve completely rewrote the code base that the system works from. It now runs a lot faster and we can support more users than previous. I now run both statistics for Twitter (tweekly.fm) and for Facebook (laststat.us). The past few days I’ve pushed changes out that change the way the system interacts with Last.fm and how we store your data.

~

In January this year when I first undertook the Tweekly.fm project in ran in a very different way than what it does now. I’ve completely rewrote the code base that the system works from. It now runs a lot faster and we can support more users than previous. I now run both statistics for Twitter (tweekly.fm) and for Facebook (laststat.us). The past few days I’ve pushed changes out that change the way the system interacts with Last.fm and how we store your data.

A major change in the way the system works has been added. Instead of providing your Last.fm username to us now we use the Last.fm Webauth (very similar to OAUTH in fact) to interact with your Last.fm data. Even if you protect your data within Last.fm we can collect and publish your data for you (should you wish to do so). Protected user support is now live within the Facebook application and will be coming to the Twitter version very soon.

The larger problem that we encounter now is capacity. We’re taking on average between 280 and 550 new users per day. Over our platform we currently sit at just over 55,000 users. The entire platform is being financed independently by me which isn’t the best form of business model. Simon and I have discussed recruiting for venture capital but to do that we would need to develop a sound model to work from that could provide a return on any investment. Anyone interested in discussing this, please get in touch.


~

Comments