I find it better to get users to follow your account and then send them a DM with a URL. Builds followers and eliminates errors from user side. R
On Nov 22, 11:30 am, Amir Michail <[EMAIL PROTECTED]> wrote: > On Nov 22, 12:26 pm, "Chad Etzel" <[EMAIL PROTECTED]> wrote: > > > This is a good method to verify (claim) an account, yes... but if you wanted > > them to be able to do any sort of authenticated request (like tweeting or > > sending a direct message), you'd still need their password. That is, unless > > you are asking twitter to change the way their API works. > > > By "future logins", do you mean to twitter? or to your service? > > > -Chad > > It would simplify future logins to my service over even OAuth. > > The problem for me though is that without user-specific authentication > (i.e., I use authentication under my account always), IP-based rate > limiting is a severe problem making this at best a temporary solution. > > Amir > > > > > On Sat, Nov 22, 2008 at 12:22 PM, Amir Michail <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > One could just have the user enter an assigned code into the bio/url > > > or even in a post (which would also help promote your service). Doing > > > so would allow the user to "claim" the twitter account and associate > > > it with his/her account in your service. > > > > Unlike OAuth, this would even make future logins simpler. > > > > Is this a reasonable way to go? > > > > Amir
