The reason I make hacks is just to see if I can do it.
If I complete it then I get satifaction.

I write hacks for vbulletin because the coding is easy to learn and the feedback is nice.
I also write hacks for recognition and to increase my knowledge of vbulletin's coding and php itself.

I wrote one successful hack (Custom Navbar Links) which should be standard in vbulletin but a lot more advanced.

Right now the biggest reward I want is that if vbulletin implements my hack into their software they'll mention who inspired the feature.

Its funny this thread comes up when people are too lazy to even given thanks....


https://vborg.vbsupport.ru/showthread.php?t=105887

Hey, missed that one when you posted it. :)

On the bright side, only 20 minutes now before I go home to my nice warm bed, I feel better already :D

I think you should get compensated from flashchat in some way. You give a lot of support here and there.

thanks a lots

You guys and gals still trying to get free stuff ? :rolleyes:

I think anyone that releases a good hack should get PIE!

I think many of us say thanks in the Hacks own thread or by PM Corrie.

Besides. I think most coders know their hacks are appreciated (well of course they are - most adults would naturally be grateful for any help they receive..) but perhaps they want a little thanks from the companies whos products they are making more attractive/sellable/profitable?

Anyway I can't fight their battles for them so am gonna pipe down now - I've posted my thoughts about it and I sincerely hope that some of the points get taken on board.

:)

I'm not reading the whole thread, but bad idea cause that would mean the users would most likely have to pay for the hacks.

Maybe you should have read the thread :p. We're not talking about having users pay for anything. :p

I throw some money to the coders of mods or hacks that really enhance my site.
I can think of 3 people I have given money to.
I consider it a tip and appreciation for their efforts and contribution.
That covers 3 renewals right there. Well almost.
Maybe I'll start giving $30 instead of $25.

I apologize for bringing this thread back to life, but I feel it fitting to express my opinion on the subject.

I know quite a few site owners who use vbulletin for their sites. Most of these people are not code writers by any stretch of the imagination, but desire to see the functionality on their sites improve. Therefore, they will get people who are technically capable of doing these various technical tasks, and in most cases make then administrators of their sites.

I am one of these people.

The owner of the site I frequent was having a problem with account sharing. He runs a premium site, and charges a fee for membership to the site. Well, it was found out that in some cases, close to 50 users were logging into the same account to reap benefits from the site. The solution? He came here and looked for a hack that would detect account sharing, but found nothing that was really suitable. There was a multiple IP detection hack, but that did not address users with dynamic IP's such as AOL users whose IP change every time they click a new link. Also, many other scenarios came into play which this particular plugin did not address.

Since I am a software engineer, he approached me about the problem, and asked me if I could help. I decided I would help. Therefore, myself, and another software engineer took to the task of developing a product that is very effective at detecting "account sharing". We wanted to be very non evasive to the current vbulletin infrastructure, yet also wanted to use vbulletin's current infrastructure to our advantage. Therefore we developed a plugin that requires no template modifications to perform the required tasks.

I did figure that other vbulletin users could greatly benefit from this plugin that we have developed. We created it with vbulletin's code specifications and suggested standards... making it so that it would be easily editable even for a novice coder.

This plugin will probably never see the light of day in the public arena. Why? Because neither myself nor the other software engineer that developed this software are licensed vbulletin users. I do not run my own forums, therefore I have absolutely no need for my own license. Yet, if I did want to share this software "out of the goodness of my heart", there is no provision for doing so... as I cannot even post in the "modification" section of the forums. Therefore, there is no possible way that I could support a product on your site. (BTW, I would never ask the owner of that site to add me to his email product support list)

What Jelsoft has done, is created a very "closed" community. The majority of the people holding a vbulletin license couldn't code to save their lives (nothing wrong with that). But, many of the talented people who would like to code and share have no need for a vbulletin license because they do not run their own forums. I tell you... it is easier to petition a royal court than it is to get information on vbulletin's code infrastructure and built in functions if you do not hold a vbulletin license. I cannot even see code snippets and examples when I browse this forum. Therefore, I had to export whatever plugins the forum owner already had installed to look at a few examples of vbulletin code, and to see how the hook system worked, and to see how the templates were designed.

Therefore I would like to make a suggestion:

It would be real nice if you would make a provision for anyone to be able to submit code modifications somewhere. If the code modification is decided to be "worthy", then create a status for the "unlicensed coder" to be able to support their products. Also, it would be nice if that "unlicensed coder" could see code snippets on the site. I see no real reason to allow that "unlicensed coder" to be able to download other plugins, as they would have no use for them, except for learning from them... but being able to learn from other code snippets would be very helpful.

This would only benefit your own customers, as they would have access to more forum enhancements, and more products than are already available. Also, you would probably be surprised at how many "good" code submissions you receive. I know many software engineers, and coders (good people, not your "133t H@XoR" type), that like to do things for a hobby. Something like this would be right up their alley.

I understand what you are saying, but the more people that get their hands on vbulletin code without jumping through the hoop of buying a license, the more exploits will be found and abused.

You may say "Hey that will just create more secure code", but, if noone finds out about the exploit, it really isnt a problem.

The reason you can't see code here if you are not licensed is to make people buy legitimate licenses. If you haven't got a license you can't get proper help (i.e. gain an undestanding of vBulletin's Code). The email support list thing is there for people like you, the owner of the site should have put you on it I don't see why they didn't.

But to be very honest with you pastalover you are unfortunately a very very small minority. You have to compare the amount of people out there who are using vBulletin illegally with those that are like you.

People like your are few and far between.

I design skins for vBulletin and when I eventually want to sell my license I want be able to access this site anymore :(

I appreciate your response Blaine0002. This reminds me of a comic strip that I once seen called "bobby tables" - google it, it is funny. :)

"Obscurity" as a protection, proves to be little or no protection at all. Just look at anything that is hacked. If an exploiter is so inclined, they CAN find information on the desired subject they want to exploit. Just take a look at pay-tv systems, playstations, or even vbulletin itself. "Obscurity" proved to be nothing more than a minor inconvenience. While carousing through google looking for information about vbulletin, I found many things from people you would consider "unfriendly". It was not hard finding every plugin that vbulletin has ever had posted on this site.

Sure, you may get more people that exploit weaknesses, yet you would get more people that could sanitize these vulnerabilities before they ever made it to the public scene. "Obscurity" will not stop someone with the "know how", not if they are obliging enough. Instead, we should be looking at sanitizing every sort of user input, to get rid of these vulnerabilities. And coders themselves should be on the lookout for other coder's code that could pose a potential vunerability... then discuss how to fix it.

What would you rather have? A product with holes in it that a select few can exploit at will, at any given time... things that aren't public? Or the exploits to made public, and fixes to be made? I would choose the latter of these two options.

These few people that are "obliging" enough to find these exploitations and do illegal activities is what jelsofts legal team is for.

seriously though, if you search for phpbb exploits you will find more than vbulletin exploits.


PS good comic :)

As you are aware we do have procedures to have additional people showing as licensed. If you choose not to ask the license owner to add you to his support list, then this is your decission.

I understand your position, and thank you for considering my suggestion. I will not push the issue further.

Have a merry Christmas everyone! And a happy New Year! :)