Twitter Development Talk Google Group

Re: Tags

2009-11-25T05:53:56Z

Sorry, but currently unsupported.

-John Kalucki
[link]
Services, Twitter Inc.

[OAuth + LIST API ] 401 Unauthorized problem

2009-11-25T03:09:14Z

I am using OAuth to access List API, but I find that if the request
URL contain some char like "_", "(", then twitter will return 401
Unauthorized.

Does anyone know what is the problem??

and this is my request:

*Request URL:

[link]

*Request header:

Re: [twitter-dev] Re: Twitter app marked "inactive"?

2009-11-25T02:46:48Z

Gotcha, thanks for the info Brian.

∞ Andy Badera

oauth_callback help

2009-11-25T01:38:13Z

Trying to work through web authentication and running into a problem
that I am sure someone else has solved.

[link]

I authorize the app, but I am not redirected to my localhost page - I

Re: Wrong account and correct IP is whitelisted

2009-11-25T00:51:06Z

You can apply for whitelisting again while logged in as the correct
account. Just make sure to mention the other username so that we know
the history of your request.

Brian

Re: Twitter app marked "inactive"?

2009-11-25T00:48:05Z

Listerine was temporarily suspended pending a conversation between the
developer and the owners of the registered mark "Listerine." This was
a rare case, so if you do have any specific questions about
objectionable application behavior as outlined in our policies, don't
hesitate to email us at a...@twitter.com :)

Re: [twitter-dev] Flood of c*ck sucking spam

2009-11-24T21:33:11Z

401 Unauthorized

2009-11-24T21:22:54Z

I having this error for a while and is happening only on my machine, I
deploy the same project in another similar VM and it worked, so I am
starting to think that there might be something related to my
environment that is causing the 401 Unauthorized issue. I have a Mac
with OS 10.5.6 and a VM running on Paralles, the VM is Fedora Core

Re: [twitter-dev] Flood of c*ck sucking spam

2009-11-24T21:10:28Z

wow, thats cool.

Hey, sorry group, thought that was just a reply to Andrew.

On Tue, Nov 24, 2009 at 1:08 PM, Hedley Robertson <

Re: [twitter-dev] Flood of c*ck sucking spam

2009-11-24T21:08:36Z

You can?

[link]

<[link]>

Re: [twitter-dev] Flood of c*ck sucking spam

2009-11-24T20:49:00Z

Hahaha I wish I could retweet your mail.

Sent from my iPhone

Flood of c*ck sucking spam

2009-11-24T20:41:46Z

There seems to be a flood of bambibots with a (not very) blurry avatar
of someone brushing their teeth with a skin flute. Any chance Twitter
HQ is aware of, and working to mitigate, this?

∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private

Re: [twitter-dev] List creation updated (needs description param)

2009-11-24T20:28:56Z

The list API requiring a parameter to create/update a list has been fixed
and should be deployed today or tomorrow. Thanks everyone who reported this.
Sorry about that...

--
Marcel Molina
Twitter Platform Team
[link]

Re: [twitter-dev] oauth Process flow and status Part 1

2009-11-24T20:17:17Z

The signature has to go last. That's one mistake that most people make.
You are suppose to put the parameters in order EXCEPT the signature
parameter. The signature parameter is created by using the other
parameters, then it's appended to the end of the query string.

The OAuth signature is generated.