Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
valitl
Starting Member
2 Posts |
 Posted - 2006-04-19 : 18:22:32
|
| Hi,I have a .asp + SQL2K "classifieds" website.I am indexing (every 2h) the posts with "Microsoft Search"; users can query it through a VBscript UserQuery_ParseTokens (eg: classi*)It is working OK.Users abuse ! sometime they post a "message" and after 1min they will re-postit.(so I've implemented a 10 min. any-re-pose cache).Now they know the trick.. and they re-post the same "message" changing only 2-3 words !I'm thinking to do "if 80% of keyword are the same, refuse it !"Well, I can do this but the problem is I can't use the "Microsoft Search" because that second or third post of the abuser will be in a 3min interval and I cannot force "Microsoft Search" to index every 1min.So I have to make a new SQL SP that will be able to search for given strings and rank the results.. But hey, THIS IS what "Microsoft Search" does ! :)So please, help me out,Do you have another idea? |
|
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
Posted - 2006-04-19 : 22:38:53
|
| Sample data and expected results, please.... |
 |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2006-04-20 : 05:11:29
|
| Why not tackle the problem at source....track who posts what in volume terms and then disable/slow down the posting rate of the key abusers....a lot simpler! |
|
|
|
Kristen
Test
22859 Posts |
|
|
valitl
Starting Member
2 Posts |
Posted - 2006-04-21 : 03:04:54
|
quote:
Originally posted by AndrewMurphy
Why not tackle the problem at source..
Thank you.I will track the users with an encripted ID, hidden into a cookieand I'll add the messageID of every last post he tryes to make + time of the last post.. in this way I hope to track/find/verify the abussers (I think ..:) |
|
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2006-04-21 : 09:07:30
|
| ...just issue a 'personalised' message, that due to the frequency of postings, they next posting can't be accepted for 5/10/15 mins/hours!...unless the contact you and explain what's up. |
|
|
|
|
|
|
SQL SP check against dirty words