I got bored, I like to program, and I often like thinking "it would be cool too..." - sometimes I act upon it.
At MFC there is no access to a history (timeline) of Cam scores (as far as I could see?). On Saturday I was bored and wondered how Cam score varies, and why I couldn't see a way of visualising it. After thinking about how easy it would be to construct one through what is publicly viewable, I set to work - simply because it was a problem I could solve easily, and it was interesting I'd never programmed a "web-crawler" before. As I finished it, I realised something else too...
A history of Cam score could give some great knowledge - some direct (how's it been going for a certain model recently, how did the other night affect camscore), some which may be inferred (good days of the week, how well certain nights went, whether bad nights were MFC wide or did a particular model do well and others badly, when may be a good time to take holidays, which nights may be best to avoid). So then I made a "proper" front end to display the info (easier/simpler to use php and mysql to display the info than program a java application to show the information to me - so I just turned my simple php output into something more structured, a "website").
http://www.camscorestats.com/
It took about 1 hour to program, although the site took about 8 hours to make as I suck at making things look good. The original idea is to output a graph of performance over time - yet to be implemented as a few points does not make an interesting graph (also looking at Google's Graph API as well, hopefully within a fortnight it'll be something I put in). The output you can see is not real time, it is updated when I run the program (about midnight, GMT, so about 6-7pm NYC timezone of the day it says last update!). This was made for my own personal curiosity, and bit of fun (yes, I find programming fun ).
Before people panic - All information gathered is publically available. There's nothing here that isn't viewable via visiting a profile. If a profile is private than no data other than the name is known. The program visits the profile found via the Offline List (publicly available list), which only contains "Top performers over the past 3 days" (paraphrasing, it averages about 2800 model names). It does not visit every models profile on MFC, only those in that list, and reads data from the profile (Model Name, Profile Picture URL, Cam Score, and Last Online to be specific - NOTHING ELSE).
Bottom line - this is the sort of silly idea that I make, and then when I see the result, think about sharing. If people like it enough/find it interesting enough, then I will share it as a separate website and improve it significantly in the way you may manipulate or visualise the data. Of course, input is more than welcome in what you'd like to see, so suggest away if you think it has some value.
So, feel free to speak up, criticise, suggest, support, ridicule or just ask questions. Until now it is just something cooked up in my spare time due to boredom to satiate an interest in how cam scores change for people, so I'm happy I'm sharing here to see if others may like it, that's all. Bottom line is that, believe it or not, I am not hoping to make money at all. This is just something I enjoyed doing, and am unsure whether to continue and put it out into public or not. If I did, I guess I'd have to contact MFC to ensure there would be no issues?
Meh, long post - hopefully not wasting time :roll:
At MFC there is no access to a history (timeline) of Cam scores (as far as I could see?). On Saturday I was bored and wondered how Cam score varies, and why I couldn't see a way of visualising it. After thinking about how easy it would be to construct one through what is publicly viewable, I set to work - simply because it was a problem I could solve easily, and it was interesting I'd never programmed a "web-crawler" before. As I finished it, I realised something else too...
A history of Cam score could give some great knowledge - some direct (how's it been going for a certain model recently, how did the other night affect camscore), some which may be inferred (good days of the week, how well certain nights went, whether bad nights were MFC wide or did a particular model do well and others badly, when may be a good time to take holidays, which nights may be best to avoid). So then I made a "proper" front end to display the info (easier/simpler to use php and mysql to display the info than program a java application to show the information to me - so I just turned my simple php output into something more structured, a "website").
http://www.camscorestats.com/
It took about 1 hour to program, although the site took about 8 hours to make as I suck at making things look good. The original idea is to output a graph of performance over time - yet to be implemented as a few points does not make an interesting graph (also looking at Google's Graph API as well, hopefully within a fortnight it'll be something I put in). The output you can see is not real time, it is updated when I run the program (about midnight, GMT, so about 6-7pm NYC timezone of the day it says last update!). This was made for my own personal curiosity, and bit of fun (yes, I find programming fun ).
Before people panic - All information gathered is publically available. There's nothing here that isn't viewable via visiting a profile. If a profile is private than no data other than the name is known. The program visits the profile found via the Offline List (publicly available list), which only contains "Top performers over the past 3 days" (paraphrasing, it averages about 2800 model names). It does not visit every models profile on MFC, only those in that list, and reads data from the profile (Model Name, Profile Picture URL, Cam Score, and Last Online to be specific - NOTHING ELSE).
Bottom line - this is the sort of silly idea that I make, and then when I see the result, think about sharing. If people like it enough/find it interesting enough, then I will share it as a separate website and improve it significantly in the way you may manipulate or visualise the data. Of course, input is more than welcome in what you'd like to see, so suggest away if you think it has some value.
So, feel free to speak up, criticise, suggest, support, ridicule or just ask questions. Until now it is just something cooked up in my spare time due to boredom to satiate an interest in how cam scores change for people, so I'm happy I'm sharing here to see if others may like it, that's all. Bottom line is that, believe it or not, I am not hoping to make money at all. This is just something I enjoyed doing, and am unsure whether to continue and put it out into public or not. If I did, I guess I'd have to contact MFC to ensure there would be no issues?
Meh, long post - hopefully not wasting time :roll: