Hi Tim, I'm pretty sure the oauth_verifier is documented in their
oAuth articles.. I'm speeking from memory here, but I'm sure I saw
last week when we were investigating our own oAuth issues..
But, nonetheless, you are correct, oauth_verifier should be passed
back every time.
D
gt; Tom
>
> > > On 12/2/10 11:42 PM, LeeS - @semel wrote:
>
> > >> I am using this library on all my sites:
> > >>https://github.com/jmathai/twitter-async,
> > >> all of which are now broken and fail to let anyone log in.
>
> > >> Any way th
b.com/jmathai/twitter-async,
> >> all of which are now broken and fail to let anyone log in.
>
> >> Any way this can be rolled back until all the various oAuth libraries
> >> people are using are brought up to date?
>
> >> Lee
>
> >> On Dec 2, 5:35 pm,
ould be a valid one now. We're just
> checking the validity in more use cases than we were previously, and
> checking other validity points we were flexible with previously.
>
> Taylor
>
> On Thu, Dec 2, 2010 at 1:32 PM, Twitlonger wrote:
>
>
>
>
>
>
>
&
I noticed I've just started getting 401's for all my oAuth requests.
Seems to be happening on more than one site for me.. My application
keys and status still look good..
Just wondering if anyone else is having an issue..?
--
Twitter developer documentation and resources: http://dev.twitter.com/
. That made
me realized that I’ve been taking for granted what you guys have
achieved with this api.
Well done guys
Hat’s off to you and your colleagues.
Dave
Twiends
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
I totally agree. It would be difficult for twitter to do this...
Give your users confidence by proactively anticipating their fears and
addressing them. Figure out what would stop them from signing in with
OAuth and answer those questions upfron. The favstar.fm example is
very good as it demonstra
As I fellow developer I'll say I fully support the drive to OAuth.
It's a lot more secure and although it might mean that you actually
have to write a few lines of code it will help stamp out a lot issues
with straight usernames and passwords..
OAuth took me total of about 2 hours to implement, w
as well and I agree.
> > I've found sorting out bots and pure spammers to be very difficult.
> > Some folks tweet so much they resemble bots/spam.
>
> > Feels like a pipe dream but if they can I'd love a karma scoring
> > system directly from the API.
>
> &
I’m looking to implement this feature on my site as I can really see
the value in it. But as you have pointed out I can also see the danger
in it. If spammers knew who had follow-back turned on they would seek
out these users and follow them, knowing they would get followed back.
They could then po
I really like the option of reporting spam via the api. I’ve been
blocking spam on my site for a long time but this gives me an option
to report it now, and hopefully get these account suspended quicker so
that they don’t come back.
It would be really great if we could have a proactive api functio
11 matches
Mail list logo
