Quote:
Originally Posted by Brujah
Just for thought, on a forum I run it has a spam service you can connect to, and based on the code returned (0, 1, 2, 3, 4) you configure how you want it to respond.
Code 0 means that the request could not be processed by the spam service, due to an out of date license key or other technical issue.
Code 1 is sent if the spam service determines that the account is unlikely to be spam.
Code 2 is sent by the service if the account is possibly spam
Code 3 is sent by the service if the account is likely spam
Code 4 is sent by the service if the account is a known spammer
Options are:
- Proceed with registration
- Flag as spammer
- Register account, but mark it banned
Seemed like a pretty good way to deal with a restriction system, whether for spam or blacklist/whitelist, users, etc..
|
Sorry, I didn't answer this second part at the time as I got caught up in something else....
Yes, indeed, but this would be the cms author's job, not mine. I have my own cms in the works, which is interested only in secure streaming and won't touch user-uploads. It is for a different market niche, so things like this would need to be added by those that cater to the tube cms market.
But, first thing's first - if I can get this idea off the ground it will be a giant leap in the right direction, but trying to move this lot is like trying to drive a Prosche out of wet concrete
