Thread: A new censor
View Single Post
  #3  
Old 05-05-2003, 07:35 PM
thefluke's Avatar
thefluke thefluke is offline
 
Join Date: Apr 2003
Posts: 6
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Quote:
Today at 10:16 PM Logician said this in Post #2
As a matter of fact, your best bet is to change your rules and make it clear that if someone intentionally passes around a censorword, he will get banned. G-force's User Warning hack may help you achieve this goal too. This is because:
We've tried that. The only problem is with 1.5k new posts per day, you sometimes have to ignore the censor abuse and go for the bigger offences. I was looking for something that we could do to automate that.

Quote:

2- Filtering is quite server intensive and that is why it is restricted with 250 words and there is no "user specific filters" in vbulletin. Say, I'm using "show 40 post per thread" setting here in vb.org so vbulletin display me 40 posts per thread. Say each post has 150 words in it which makes 6000 words per page. Say admins set 250 filter/replacement words in options and I have my own of 250 which makes 500 words. Can you imagine the server load and slowness of process if vbulletin passes through a 500 words list to match them in 6000 words in every thread I read here. You'll soon get the server on to its knees.

So maybe my message did not help you but it may clear the ground why the help you are asking is not so easy to get in technical aspect.
My intent was to not have users add words to the censor, but to exempt certain users from seeing censored posts- that is if 2 people view the thread, one can see the posts, as written, the other will see the posts after they have been censored. Certain words will always have to be censored, due to agreements with the host.

I'm not sure if that is in anyway different from a technical aspect, though it sounds like that might make the load slightly less? I'm still new at this sort of thin, so I could be very wrong.
Reply With Quote
 
X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01920 seconds
  • Memory Usage 1,766KB
  • 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
  • (2)bbcode_quote
  • (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