Quote:
Originally Posted by ap0c
This is where your arguement fails and you would lose in court. By allowing other sites to use your forums, ie," link back to your site: " to create subforums and control them as they see fit, that is a violation of the LA.
No one, according to this section, has the right to sublicence or assign their copy of vbulletin to other sites without Jelsoft's approval.
Since the hack contains the ability of another site to use your vb, again the "link back to your site:," it is in direct violation of the LA.
|
Simply put, that is just wrong. The problem with any type of verbiage associated with that type of implication, is that you couldn't create any manner of portal site or way for sites to be networked. In effect, vBulletin itself would be nearly in direct violation of that agreement by providing the ability to setup a link within the forumhome template back to another site.
The only thing preventing this would be the sheer fact that all of those links also are running their own vBulletin.
The problem here, is that this is a huge grey area. Sure, GreyFinalFantasySite.com can create a page and say, "To discuss GFFSite.com, click here." Then, the user would be moved offsite to VbHOSTINGVBulletin.com where the person has set up their own part of the site, with similar colors and a different header.
The problem is, they still work off the same vBulletin. The user would have to still register within the overall network of vbhostingvbulletin.com, and anytime they reach the top of the breadcrumb, it would be the true nature of the site that runs and owns the content.
That being said, I have wasted ENTIRELY too much time researching and pouring my heart over the vBulletin Licensing Agreement...I've read the thing almost 10 times now. Here are the parts which trip up either side if this were brought to litigation:
Quote:
vBulletin ('the Software') is a copyrighted work of authorship and is also protected under applicable database laws.
|
The Good: Jelsoft does the smart thing by declaring vBulletin as The Software. Provided that copyright law has been followed, the terms of exactly what vBulletin is should be easy to prove in a court of law. Thereby determing that the licensing agreement is in fact viable.
The Bad: Insufficient by any standards. You cannot claim copyright without broadcasting type of copyright (US, International, etc.) or broadcasting that copyright data can be obtained by contacting the following source. Also, a broad assumption of "Applicable Database Laws" does no good without citing which laws the licensing agreement heretofore references as being the foundation for said license agreement.
Quote:
vBulletin licence grants you the right to run one instance (a single installation) of the Software on one web server and one web site for each licence purchased. Each licence may power one instance of the Software on one domain. For each installed instance of the Software, a separate licence is required.
|
The Good: Jelsoft does a bang up job here by declaring that only one instance of the software be installed on one web server and one web site for each license purchased
The Bad: No verbiage about exactly what defines a singular instance. In these estimations, any link to
www.speedstreet.org/forums is ok, irregardless of content provided, so long as the link that appears in the URL bar is only to one server, one database and one domain.
Quote:
The Software is licensed only to you. You may not rent, lease, sublicence, sell, assign, pledge, transfer or otherwise dispose of the Software in any form, on a temporary or permanent basis, without the prior written consent of Jelsoft.
|
The Good: The wording is ok.
The Bad: By not clearly defining what an instance is in the previous bullet, assigning a software function such as vbhosting as a sublicensing product is nigh impossible. Since the hack falls within the established parameters of an instance, you cannot apply any manner of infringement violation due to its inherent nature.
---
This is all I will go into without working directly with the JelSoft team. I think that the best thing to do for Jelsoft would be to bring someone in to help with Risk Assesment, because having a virtual company such as this leaves you open to risk and liability because you have so many "representatives" of your organization speaking. The minute someone posts and a Team suffix is attached to their name, it becomes company mantra.
We cannot blame GameCrash for the fantastic work he has done with this hack. He takes some of the best features of the vBulletin software and develops them even further. The sadness ensues when you realize that this hack can facilitate the destruction of the integrity of our community, simply by allowing any jackass to create their own section on your boards.
GameCrash, please consider revising your hack to increase additional security. It can be a tremendous boost to our group as a whole, if only a few minor tweaks were made to it.