View Single Post
  #121  
Old 01-04-2004, 07:08 PM
tamarian tamarian is offline
 
Join Date: Oct 2001
Location: Canada
Posts: 1,205
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

While I can sympathize with vB and what they're going through with this ddos thing, I really cannot agree with what they're doing. After weeks of not being able to access, and assuming it's due to the ddos attack, I find out they're running o.k. and their server as in vB.org is up, but only blocking ips from vB.com! Can't those who are blocked ddos vb.org to bring the server down?!?!

This sounds fishy to me, technically, and especially having no attempt at explaining any of this to us blocked customers, even by email, to alert us that we need to constantly update vB support with our IP's if we need to access our accounts.

The excuse so far is that vB staff are busy handling the attack? That's a big mistake, IMHO, as throwing more staff at handling the attack doesn't help. Have the ones with network security background handle it, or hire an expert, let them do their job, and let the rest do other things, like minimal updates and communication with customers. Send a lousy email, have vb.org create a temporary forum to update us (or mirror vb.com's announcement on vb.org), etc. There are so many things the rest can do.

The way it looks so far is like a high way accedent, where all spectators want to watch the wreck and monitoring those who are doing the rescue, while stopping traffic, and no one wants do do anything else useful.

That's just my opinion, and I don't know sh*t about what they're doing and what's going on, but that's not my fault, it's vB's fault for being so silent, uncommunicative, keeping customers uninformed about the situation, so we're left to guess what is really happening, and what's being done.

Nothing can help the situation with your customers better than being open, communicative and transparent. Explain what is going on and what's being done, constant updates, etc.
Reply With Quote
 
X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01248 seconds
  • Memory Usage 1,763KB
  • Queries Executed 11 (?)
More Information
Template Usage:
  • (1)SHOWTHREAD_SHOWPOST
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_box
  • (1)post_thanks_button
  • (1)post_thanks_javascript
  • (1)post_thanks_navbar_search
  • (1)post_thanks_postbit_info
  • (1)postbit
  • (1)postbit_onlinestatus
  • (1)postbit_wrapper
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • reputationlevel
  • showthread
Included Files:
  • ./showpost.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/functions_bigthree.php
  • ./includes/class_postbit.php
  • ./includes/class_bbcode.php
  • ./includes/functions_reputation.php
  • ./includes/functions_post_thanks.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_postinfo_query
  • fetch_postinfo
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • showpost_start
  • bbcode_fetch_tags
  • bbcode_create
  • postbit_factory
  • showpost_post
  • postbit_display_start
  • post_thanks_function_post_thanks_off_start
  • post_thanks_function_post_thanks_off_end
  • post_thanks_function_fetch_thanks_start
  • post_thanks_function_fetch_thanks_end
  • post_thanks_function_thanked_already_start
  • post_thanks_function_thanked_already_end
  • fetch_musername
  • postbit_imicons
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • postbit_display_complete
  • post_thanks_function_can_thank_this_post_start
  • showpost_complete