vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin.org Site Feedback (https://vborg.vbsupport.ru/forumdisplay.php?f=7)
-   -   New Forum Request (https://vborg.vbsupport.ru/showthread.php?t=165467)

Kirk Y 12-18-2007 07:52 PM

Quote:

Originally Posted by Prince (Post 1403807)
no more liabiilty than the current forum where members request paid services.

What if a paid product was put into this hypothetical forum - and was then later discovered to have serious security vulnerabilities which lead to the exploitation or destruction of several forums. vB.org (Jelsoft) could then be held liable for endorsing or advertising this product, or for even allowing it to have been on the forum at all.

At least with the Request for Paid Services forum, any blame rests solely on the individual who took up the request, not on Jelsoft or vB.org. With a forum like the one you're suggesting, blame would rest on BOTH Jelsoft/vB.org (for allowing the product to be published here) and whoever the product's developer was (for the existence of the exploit).

Prince 12-18-2007 10:02 PM

I fail to see this liability that you think would have, but we can all agree to disagree.

Freesteyelz 12-19-2007 01:48 AM

Quote:

Originally Posted by Kirk Y (Post 1403913)
What if a paid product was put into this hypothetical forum - and was then later discovered to have serious security vulnerabilities which lead to the exploitation or destruction of several forums. vB.org (Jelsoft) could then be held liable for endorsing or advertising this product, or for even allowing it to have been on the forum at all.


Maybe but unlikely.

- You're neither endorsing or advertising brand vB if paid services are offered here.
- Modifications that are verfied as unsafe are usually removed quickly by the staff. There is no reason to suggest that it will be different if the (hypothetical) forum is up.
- The game changes if either organization takes a cut from revenue gained of a product by percentage, tax, royalty, lease and so forth.

I am not saying that there are no issues with liability. If you want to find a reason, you will. However, it doesn't matter to me either way. I'm just responding to the above quote.

nexialys 12-19-2007 02:01 AM

looks like a dead-end again...

Marco van Herwaarden 12-19-2007 04:13 AM

vBulletin.org is a site about sharing among vBulletin owners free advice. Advertising commercial products in any form is not what we want.

Closing thread.


All times are GMT. The time now is 01:20 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01034 seconds
  • Memory Usage 1,726KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (2)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (1)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (5)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete