[snip everything irrelevant] On a tehnical note, I don't really see how you can prevent this sharing of logins. This is something I was actually looking into for a site that had nothing to do with pr0n (would love to know where that came from, it seems so universal now). If you read up on the general issues surrounding client identification (http://phpsec.org) it is pretty much impossible to come up with a solution of uniquely identifying a specific browser session that will work in all instances. And really, this is what you are trying to get at isn't it? Uniquely identifying your clients. The only non-technical solution I can offer you is that you change the passwords for each person as they login. This would make people much more reluctant to shre their account as they would not be able to access their own account as soon as someone else logs in with it. Of course, people aren't gonna like have to remember all the different passwords but I think it helps with your problem. As for the rest of this whole thread, I think we should all be a little more "live and let live" about this. So you don't like pr0n? So what? I know a lot of people who do (not so much myself, am more of a doer) but I don't think it makes them bad people. I also happen to know that not all pr0n is about exploitation. Some is, of course, and I'm sure that even Dan would agree that this is not good - if anyone had bothered to find out in the first place. I'm not trying to invite more flaming here - there have been some very valid points made, I just hope this thread can die a quick and silent death not that the technical issue has been addressed. Mikey -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
