[Logician]

Originally posted by tubedogg
Post your thoughts in this thread. Tell us what we can do to make it a better place.

IMHO the most important problem in vb.org is it does not befit well with its primary concern, that is "vbulletin hacks".

The number of hack threads is over 1200 in full releases section and it's impossible to track them with the existing system anymore. Hacks appear in the main page while they are released and the new release rate is so rapid that they expire even in 2 or 3 days. Then they are forgotten in the dark corners of Full Releases section and nobody runs into them unless they are accidently bumped. Hack db is a very nice idea but it's obvious it's not working very well to promote hacks.

IMO a new approach is needed urgently to handle the rapid hack release rate (which is a good thing BTW!)...

I'm not determined what would be the best approach but different methods can be thought like:
* Dividing the section into small pieces and seperating the small code modifications from major hacks (like Xenon always suggests)
* Putting hack releases under moderation
* Promoting more hacks in the main page dynamically. Top 10 hack list might be good idea but it just makes sures that the hacks in the list will be always in top 10 considering the traffic they get just because they are listed in that list. Different promotion tools can be coded such as listing top X hacks according to different criteria and randomly changing..
* In forum home there can be a small line choosing a hack randomly from the db with a few lines of comment and giving it a chance to be promoted..
* Regs's idea is also nice
* More hacks from different authors should be applied to vb.org. This would both increase the functionality here, encourage hacking and promote more hacks to vb members..

Well many others can be thought but I guess I made my point. The bottom line is: Full Releases section is a mass and does not suffice for the very high number of new hack releases anymore..

We have a chance: Vb3 will be released soon, so whatever new approach will be applied, it can at least be applied to VB3 hacks section..