The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#51
|
|||
|
|||
Quote:
|
#52
|
|||
|
|||
Im pretty new around here but the first post should set the standard here on this thread!...Im sick and tired of installing hacks, then having to come back for help and help is not given by the creator!...
In this up coming week I will be removing about 3 full hacks which the creators have not responded to help questions in the last 2 months...I don't want to use a hack that will not have support or is not working properly.... I support all hacks and the creators of their hacks, but PLEASE follow thru with what you create! This is the only and best site to get hacks, just wish there was a standard or a set of rules to govern what is created and support.... Hats off to all who have gave up their time to others to better the system...now lets get the ball rollin and keep it high... MuSuL |
#53
|
||||
|
||||
A lot of the hackers have lives outside of vB. So they may not have time to answer questions in their hack threads, especially if the question has been answered before.
We used to have a tag that stated whether the hack author would support the hack or not. Maybe we need that back... |
#54
|
||||
|
||||
yes we will need that Back
|
#55
|
||||
|
||||
Interesting concept, but I'd like to add a little...err..a lot.
When posting a new hack, offer an option to the hack writer to have it "certified". This would basically be the in-depth inspection mentioned in the first post..but it wouldn't be free. If someone writes a hack and wishes for it to be "certified" as functional and secure, they can have it looked over by by a qualified person for a small fee...a couple bucks. This fee would go to the person who certifies the hack via Paypal. Perhaps smaller fees for super simple hacks. The couple bucks is a small amount to pay to have a hack certified, but for someone who knows what they are doing, they could certify a few hacks a month and earn some spending money, or money to pay for their cable internet. Of course in order to be able to certify hacks, you would have to prove yourself a worthy coder. So here's how I think it should work... Member goes to post a new hack... They choose whether or not to have it certified by a "professional". If they choose yes, then the hack gets posted to an area only accessible to those members that have been designated to be able to certify new hacks, and an overview of the hack gets posted to a "waiting for cert" section viewable by all members. (this would prevent someone from attempting to code something that is already in the pipeline for release) Those people that are able to certify hacks would have a section that lists all hacks currently requiring certification, and they can then choose which hack they want to work on. They would only be able to certify one hack at a time. The person who certifies a hack would also be responsible for providing support for that hack, since during the inspection process, they would know the code as well or better than the original writer. After the hack is certified, they are paid via Paypal and the hack gets posted with a "certified" icon. Payment not sent? Hack not posted. Simple. If the hack writer chooses to not have his work certified, it gets posted immediately with an "as is" and "not certified" warning, and people can download and install it at their own risk, with support offered when possible. This pay-for-certification system would benefit everyone. The hack writer would get piece of mind knowing that his hack is worthy of a "certified" icon, and can begin work on new projects while support for his certified hacks is provided by someone else. The certifier benefits financially for his time and work. The end user benefits by having the choice to only install certified hacks and gets piece of mind knowing that certifed hacks will always be supported. Additionally, it would be great if anyone could pay to have a hack certified. For example... Member XXX posts a really great hack, but for whatever reason chooses not to pay to have it certified. Member ZZZ loves the hack concept, but is nervous about installing a non-certified hack, so member ZZZ can "sponsor" the certification process by paying for it himself. Just my thoughts. I for one would have no problem in paying a small amount for the piece of mind in knowing that what i'm about to install wont cause security issues or conflicts. |
#56
|
||||
|
||||
This will not be a paid system. We're aiming to raise the overall quality of hacks with this, not to segregate and create a sort of "elite hacks" vs "plain hacks" system.
Moreover, payment for Hacks is not allowed on vB.org, and as far as I gather from vB.org and vB.com Staff, your proposal would fall under that mention and thus not be allowed to begin with. |
#57
|
|||
|
|||
Quote:
Yes, I think there should be more made of the fact that most hackers are freely sharing their modifications and doing so in their spare time. It is frustrating to see support threads where hackers are criticized and attacked by people who do not even know if they have access masks enabled or not. This rudeness might discourage good people from contributing more hacks. Since vb.org is starting fresh with vb3, it might be good to become less tolerant of people who badger hack creators and make a nuisance demanding (not suggesting) additional features. A hack is a hack, IMO. Take it as a free gift or just leave it alone. We are all administrators and should have some mutual respect for each other. My mindset is that "authenticated" hacks should be presented in a way where a person of reasonable skill and caution can successfully install it. And maybe you can ask for volunteers who (with permission) would like to be caretaker of other people's hacks once the original hacker moves on? PS. Yes, I know I have too much to say....but if feedback is solicited, I will give it! |
#58
|
||||
|
||||
Quote:
On the whole, though, there are ways to ensure that your hack is easy to install for people. One such way is by using the Hack Tracking Log to create your hacks. Tons of benefits come with that, one of which being the Installer Routine that comes with it, which will allow you to generate installer files that others can use, similar to Chen's vBHacker, but then taken to far higher levels of usability, ease of use, functionality, etc. oh, and we're very happy with your feedback! Keep it coming! ^_^ |
#59
|
||||
|
||||
Quote:
|
#60
|
||||
|
||||
Quote:
Ahwell, it's not just my decision only or anything, but I can't see the benefits of making this be available only to those with money to spare, when our goal is to raise the quality of ALL hacks released here. Involving money in one way or another will create a `niche market`, pretty much, so that would defeat the purpose of all this. The Service Requests forum is for those with mucho $$$, not for your average joe hacker on this site (which is 95% of the userbase). |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|