Hey Twitter API devs,
We're working on daemons to poll the search API, and we want to make
sure that our code will behave correctly when it encounters a
RETRY_AFTER header. We think our code should work correctly, but we'd
like to be able to test it with a real RETRY_AFTER header. Could you
add
Hey Craig,
We found an addition to this. Your regex is great, but it doesn't
limit the length of screen names. Twitter doesn't allow signups
greater than 15 chars (but in tweets, it will actually link up to 20
chars).
So, @abcdefghijklmnopqrstuvwxyz will be linked out to
@abcdefghijklmnopqrst
Seconding this.
On Apr 3, 4:51 am, Todd Sampson toddsampson2...@gmail.com wrote:
If you are going to deprecate this method, can you at least return a
user not found error as opposed to returning user twitter.com/show?
I have received numerous complaints that users we lookup are being
