> One solution to this problem is to add to each twitter > account another "private" ID.
Jim, Wouldn't it make more sense to implement this "private id" thing on your own server? My thought here is that your service should maintain its own database of users, and issue a unique "private id" for each of these users. Then when the visitor tries to login, your code can check to see if the private id the visitor has entered is in your own database. If so the person is allowed to login, and if not they get an error. Would this work to solve the problem of am I missing something here? Owkaye
