Paul M
10-15-2005, 04:10 PM
New thread as advised.
Actually I'd like to know exactly how it does work, since my top three hacks have had 250, 160 and 135 installs in the last 31 days, which is more than any of the above ???
It's based on the thread-dateline and number of installs.
The cron script gets hacks posted in the last month and sorts them by number of total installs. From this list the top five hacks are taken and inserted into the poll.
I'm guessing that your hacks where released before September 15th, so they where not included in the poll due to the dateline.
Except the release date of the Extended Signatures is 02 Sep 2005,
IMO (biased of course) if a hack is popular enough in the last month to get xxx installs then surly it should qualify for Hack of the Month ? irrespective of when it was released. Only previous winners should be excluded.
I agree, but did not code the script in question (Xenon is the man you're looking for). It seems Extended Signature Limits was last updated on the 2nd of this month, I think that is why it was included in this poll.
If you would like to propse changes in the way we select hacks for the poll please post a new thread in site feedback. More people will see the discussion there and I'd rather keep it outside of this thread. :)
it takes the last 5 weeks of released threads, and sorts them by install count.
that way hacks which are VERY popular in the first week of their release can be in two polls.
As for basing it not on the releasedate but on the install dates: i thought about that myself as well, and we might change it soon, but we'll see
I'm still a bit confused as Sep 2nd is more than 5 weeks ago .....
Anyway, it seems to me that myself (and I'm sure others) have basically been penalised for releasing 3.5 hacks early - the full release of 3.5 has seen a sharpe increase in installs, but because they were released a while ago, they are barred from the hotm vote.
In the future I would like to propose the vote includes any hack that is not a previous winner, based on it's installs in the previous 30 days.
No doubt any change will be too late for me (again :(), but at least someone may benefit from a fairer system.
Actually I'd like to know exactly how it does work, since my top three hacks have had 250, 160 and 135 installs in the last 31 days, which is more than any of the above ???
It's based on the thread-dateline and number of installs.
The cron script gets hacks posted in the last month and sorts them by number of total installs. From this list the top five hacks are taken and inserted into the poll.
I'm guessing that your hacks where released before September 15th, so they where not included in the poll due to the dateline.
Except the release date of the Extended Signatures is 02 Sep 2005,
IMO (biased of course) if a hack is popular enough in the last month to get xxx installs then surly it should qualify for Hack of the Month ? irrespective of when it was released. Only previous winners should be excluded.
I agree, but did not code the script in question (Xenon is the man you're looking for). It seems Extended Signature Limits was last updated on the 2nd of this month, I think that is why it was included in this poll.
If you would like to propse changes in the way we select hacks for the poll please post a new thread in site feedback. More people will see the discussion there and I'd rather keep it outside of this thread. :)
it takes the last 5 weeks of released threads, and sorts them by install count.
that way hacks which are VERY popular in the first week of their release can be in two polls.
As for basing it not on the releasedate but on the install dates: i thought about that myself as well, and we might change it soon, but we'll see
I'm still a bit confused as Sep 2nd is more than 5 weeks ago .....
Anyway, it seems to me that myself (and I'm sure others) have basically been penalised for releasing 3.5 hacks early - the full release of 3.5 has seen a sharpe increase in installs, but because they were released a while ago, they are barred from the hotm vote.
In the future I would like to propose the vote includes any hack that is not a previous winner, based on it's installs in the previous 30 days.
No doubt any change will be too late for me (again :(), but at least someone may benefit from a fairer system.