[twitter-dev] API Changes for March 3, 2009

[Matt Sanford]

A few minor updates today, 2009-03-03:

* Fixed: The /friends/ids and /followers/ids no longer require  
authentication for protected users. - http://code.google.com/p/twitter-api/issues/detail?id=268
* Fixed: The /friends/ids and /followers/ids now support the  
callback parameter for JSON. - http://code.google.com/p/twitter-api/issues/detail?id=318
* Fixed: Statuses ending in "..." are no longer incorrectly  
trimmed when displayed on twitter.com. - http://code.google.com/p/twitter-api/issues/detail?id=247


These are in the process of being deployed across all machines, so it  
may take a little bit before you see the changes take effect.


Thanks;
  — Matt Sanford

[twitter-dev] Re: "in reply to" metadata missing for manual replies

[Cameron Kaiser]

> One of my main concerns is with SMS. There is current *no* way for SMS users
> to reply to a specific status.

Actually, this also affects mobile web, since you can't mark a post to reply
to on m.twitter.com either (unless you are using the standard interface,
of course).

-- 
 personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- It's tradition, that makes it okay. -- Weird Al, "Weasel Stomping Day" -

[twitter-dev] Re: "in reply to" metadata missing for manual replies

[Abraham Williams]

One of my main concerns is with SMS. There is current *no* way for SMS users
to reply to a specific status.

I recently submitted an issue to make the in_reply_to_status_id updatable so
people could repair their broken threads if they wanted to. But it has been
marked as wont fix.
http://code.google.com/p/twitter-api/issues/detail?id=309

Are there more false positives happening before the change or are there more
correct links that are now not being applied? I would wager the first is
correct. I find it nice that now they are almost always correct.


On Tue, Mar 3, 2009 at 19:04, simX  wrote:

>
> Uh, Twitter doesn't *need* to read users' minds, it just needs to
> merge the two approaches together.  Before, Twitter auto-linked
> everything, and manual replies were considered genuine replies even if
> they weren't.  Now, it auto-links nothing, and manual replies aren't
> auto-linked even if they *are* genuine replies.
>
> So Twitter can auto-link manual replies that aren't specifically
> marked as such (e.g.: by clicking the reply swoosh in the web
> interface), and store that data *separately* from genuine replies that
> are specifically marked as replies.  That is, the "in_reply_to" data
> can have a flag letting the client know if the data was auto-linked or
> if it was not.  Then, clients can decide what to do with that extra
> data.
>
> For example, there could be a setting in the Twitter web interface to
> show "in reply to" links for manual replies *and* genuine replies, or
> to show "in reply to" links only for genuine replies.  That way it can
> satisfy me (and the other users that feel the same way), as well as
> those that only want the most accurate links between conversations.
>
> I (and some of my followers) think that more context is better than no
> context at all, even if the context is only approximate.  Others think
> that only accurate context is valuable, and approximate context isn't
> at all.  Such a change would preserve *more* metadata and would allow
> *both* kinds of users to use Twitter how they want to.
>
> -- Simone
> - Show quoted text -
>
> On 3 Mar, 16:24, atebits  wrote:
> > > Requiring a user to go through a specific part of the
> > > UI just to reply to a tweet is not acceptable.
> >
> > How else would you expect it to work?  Twitter can't read users' minds.
>



-- 
Abraham Williams | http://the.hackerconundrum.com
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.

[twitter-dev] Re: "in reply to" metadata missing for manual replies

[simX]

Uh, Twitter doesn't *need* to read users' minds, it just needs to
merge the two approaches together.  Before, Twitter auto-linked
everything, and manual replies were considered genuine replies even if
they weren't.  Now, it auto-links nothing, and manual replies aren't
auto-linked even if they *are* genuine replies.

So Twitter can auto-link manual replies that aren't specifically
marked as such (e.g.: by clicking the reply swoosh in the web
interface), and store that data *separately* from genuine replies that
are specifically marked as replies.  That is, the "in_reply_to" data
can have a flag letting the client know if the data was auto-linked or
if it was not.  Then, clients can decide what to do with that extra
data.

For example, there could be a setting in the Twitter web interface to
show "in reply to" links for manual replies *and* genuine replies, or
to show "in reply to" links only for genuine replies.  That way it can
satisfy me (and the other users that feel the same way), as well as
those that only want the most accurate links between conversations.

I (and some of my followers) think that more context is better than no
context at all, even if the context is only approximate.  Others think
that only accurate context is valuable, and approximate context isn't
at all.  Such a change would preserve *more* metadata and would allow
*both* kinds of users to use Twitter how they want to.

-- Simone

On 3 Mar, 16:24, atebits  wrote:
> > Requiring a user to go through a specific part of the
> > UI just to reply to a tweet is not acceptable.
>
> How else would you expect it to work?  Twitter can't read users' minds.

[twitter-dev] Re: "in reply to" metadata missing for manual replies

[simX]

Most of them are coming either from Twitterrific or from "web", but
that's probably just an artifact of those users whom I follow.  Most
of my friends on Twitter are those who do Mac and iPhone development,
and are most likely using Twitterrific on their Macs.

Incidentally, it was pointed out to me that m.twitter.com does not
even offer the reply swooshes that set the "in reply to" metadata.  So
much for Twitter clients "conforming" to the new API. :rolleyes:

Also, it should be noted that while there are some users that are
constant violators (and seemingly never go through the UI steps to set
up the "in reply to" metadata), other users sometimes *simply forget*
to make a tweet so the correct metadata is applied.  This is expected;
humans make errors all the time.  Breaking metadata because of it is
lame.

-- Simone


On 3 Mar, 16:07, Chad Etzel  wrote:
> Just curious, of these replies that *should* be linked to a specific
> tweet, how many are coming "from web" and how many "from another
> application" ?
> -Chad

[twitter-dev] Re: advanced search with source: and a query returns error or nothing

[woo]

Thanks Matt,
Filed a bug:
http://code.google.com/p/twitter-api/issues/detail?id=320

Steve


On Mar 3, 2:36 pm, Matt Sanford  wrote:
> Hi Steve,
>
>      There definitely seems to be a bug there. Please open an issue 
> athttp://code.google.com/p/twitter-api/issues/entry
>   and I'll take a look. I see you update issue #80 but please open a  
> new one since this seem unrelated and I don't want to forget about it.
>
> — Matt
>
> On Mar 3, 2009, at 11:25 AM, woo wrote:
>
>
>
>
>
> > Hi, I'm trying to do a search for tweets from my iphone app
> > (source:ootunes) which doesn't work without a query string.  When I
> > add a query string that I know should return results:
> >http://search.twitter.com/search?q=source%3Aootunes+listening
> > Get either:
>
> > We're sorry, but something went wrong.
> > We've been notified about this issue and we'll take a look at it
> > shortly.
>
> > or just a blank page without results.  I know this issue:
> >http://code.google.com/p/twitter-api/issues/detail?id=80covers the
> > general use of source: filtering, but not sure if I should file
> > another for this result?  Any other way to find tweets from my app?
> > Steve

[twitter-dev] Re: "in reply to" metadata missing for manual replies

[atebits]

> Requiring a user to go through a specific part of the
> UI just to reply to a tweet is not acceptable.

How else would you expect it to work?  Twitter can't read users' minds.

[twitter-dev] Re: "in reply to" metadata missing for manual replies

[Chad Etzel]

Just curious, of these replies that *should* be linked to a specific
tweet, how many are coming "from web" and how many "from another
application" ?
-Chad

On Tue, Mar 3, 2009 at 7:04 PM, simX  wrote:
>
> When is this problem going to get fixed?  1.5 months after the
> original API change, I am still getting a significant portion of
> replies in my timeline that are supposed to be *to a specific tweet*,
> but are not because Twitter is no longer auto-linking manual @replies
> and people are lazy and don't want to take the time in the interface
> of their client to "correctly" reply to a tweet.
>
> Note: user laziness is *not* a failure on the part of the user, this
> is a failure on the part of Twitter.  Requiring a user to go through a
> specific part of the UI just to reply to a tweet is not acceptable.
>
> When is a viable compromise solution going to get implemented so that
> @replies become tolerable again?

[twitter-dev] Re: "in reply to" metadata missing for manual replies

[simX]

When is this problem going to get fixed?  1.5 months after the
original API change, I am still getting a significant portion of
replies in my timeline that are supposed to be *to a specific tweet*,
but are not because Twitter is no longer auto-linking manual @replies
and people are lazy and don't want to take the time in the interface
of their client to "correctly" reply to a tweet.

Note: user laziness is *not* a failure on the part of the user, this
is a failure on the part of Twitter.  Requiring a user to go through a
specific part of the UI just to reply to a tweet is not acceptable.

When is a viable compromise solution going to get implemented so that
@replies become tolerable again?

[twitter-dev] Search for a link / no partial search

[Nicole Simon]

Please tell me if I missed something:

I was trying to figure out why the frak my search did not yield any results
as I was playing around with the Yoast tweetback plugin for WP.

And I think I have found the culprit:

A search for http://tinyurl.com/acu8rb does not bring a result back
if somebody tweeted

reading: topic blabla (http://tinyurl.com/acu8rb)

[which is how twithis posts all links).

My question is: assuming that partiel search is hard to implement, would
it at least be possible to implement a 'search for link'? you do after all
'recognize' the link so it should be searchable, right?

Otherwise I see gazillion possiblities how tweetbacks would have
to be queried and I am sure you would not like the API traffic. ;)

thanks
Nicole



-- 
Jetzt im Buchhandel:
"Twitter - Mit 140 Zeichen zum Web 2.0"
Amazon: http://tinyurl.com/6at9c5

http://mit140zeichen.de - http://twitter.com/m140z

Kontakt:
http://twitter.com/NicoleSimon
https://www.xing.com/profile/Nicole_Simon

skype: nicole.simon / mailto:nicole.si...@mit140zeichen.de
phone: +49 451 899 75 03 / mobile: +49 179 499 7076

[twitter-dev] Re: Posting a status update to the Mobile version of Twitter

[aschobel]

Thanks Alex,

I noticed there is no JS on the page, so using a framekiller wouldn't
work. And for speed you probably don't want JS running.

Is there a way to force the standard version without having them
submit the form at the bottom of the page?

Cheers,
Andreas

Follow us on Twitter @3banana
http://twitter.com/3banana

On Mar 3, 2:15 pm, Alex Payne  wrote:
> In order to prevent clickjacking attacks, we had to disable this 
> functionality.
>
>
>
> On Tue, Mar 3, 2009 at 13:44, aschobel  wrote:
>
> > To clarify, we only want to prepopulate the status field.
>
> > This works on the standard version, doesn't work on the mobile
> > version.
>
> > It used to work on mobile version according to this thread:
>
> >http://groups.google.com/group/twitter-development-talk/browse_thread...
>
> > Cheers,
> > Andreas
>
> > Follow us on Twitter @3banana
> >http://twitter.com/3banana
>
> > On Mar 3, 1:00 pm, aschobel  wrote:
> >> We are having problems posting status updates to the mobile version of
> >> Twitter, it looks like the status input field for the mobile version
> >> comes with a default value of "".
>
> >>  >> value=""/>
>
> >> For the standard version of Twitter, we can pre-populate the status
> >> field by doing opening the following page:
>
> >>http://twitter.com/home?status=Hello%20world
>
> >> Our app for Android lets folks share their notes to Twitter, and this
> >> was working fine until Twitter started detecting the user agent for
> >> Android and giving people the mobile version instead of the standard
> >> version.
>
> >> Is there a way to force the Standard version? Passing in &ui_type=s
> >> doesn't do anything.
>
> >> We support Twidroid, but not everybody has that installed.
>
> >> Cheers,
> >> Andreas
>
> >> Follow us on Twitter @3bananahttp://twitter.com/3banana
>
> --
> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x

[twitter-dev] Re: Advanced search queries and grouping terms

[Matt Sanford]

Hi Chad,

The search.twitter.com query parser does not support grouping  
like this. We've talked about it a few times internally but it's  
pretty difficult and never seems to have a high enough priority. Go  
ahead and open a Google Code issue on it so I don't forget.


Thanks;
  — MAtt

On Mar 3, 2009, at 02:46 PM, Chad Etzel wrote:



Hi there,

I have tried all boolean search logic I know to accomplish this, but
I've run out... is this possible?

The logic I am trying to search is this:

(term1 AND term2) OR term3

meaning: results containg both term1 and term2 OR only containing  
term3


example usage:

(from:prsarahevans AND #journchat) OR from:journchat

I know this is not valid Twitter Search syntax, but is there a syntax
that will accomplish this?

Basically, how do I group terms together so that they can be used with
an OR operator?

Thanks,
-Chad

[twitter-dev] Advanced search queries and grouping terms

[Chad Etzel]

Hi there,

I have tried all boolean search logic I know to accomplish this, but
I've run out... is this possible?

The logic I am trying to search is this:

(term1 AND term2) OR term3

meaning: results containg both term1 and term2 OR only containing term3

example usage:

(from:prsarahevans AND #journchat) OR from:journchat

I know this is not valid Twitter Search syntax, but is there a syntax
that will accomplish this?

Basically, how do I group terms together so that they can be used with
an OR operator?

Thanks,
-Chad

[twitter-dev] Re: Posting a status update to the Mobile version of Twitter

[Alex Payne]

In order to prevent clickjacking attacks, we had to disable this functionality.

On Tue, Mar 3, 2009 at 13:44, aschobel  wrote:
>
> To clarify, we only want to prepopulate the status field.
>
> This works on the standard version, doesn't work on the mobile
> version.
>
> It used to work on mobile version according to this thread:
>
> http://groups.google.com/group/twitter-development-talk/browse_thread/thread/291311d3fda932bc/1d512b31e0860c5a
>
> Cheers,
> Andreas
>
> Follow us on Twitter @3banana
> http://twitter.com/3banana
>
>
>
> On Mar 3, 1:00 pm, aschobel  wrote:
>> We are having problems posting status updates to the mobile version of
>> Twitter, it looks like the status input field for the mobile version
>> comes with a default value of "".
>>
>> > value=""/>
>>
>> For the standard version of Twitter, we can pre-populate the status
>> field by doing opening the following page:
>>
>> http://twitter.com/home?status=Hello%20world
>>
>> Our app for Android lets folks share their notes to Twitter, and this
>> was working fine until Twitter started detecting the user agent for
>> Android and giving people the mobile version instead of the standard
>> version.
>>
>> Is there a way to force the Standard version? Passing in &ui_type=s
>> doesn't do anything.
>>
>> We support Twidroid, but not everybody has that installed.
>>
>> Cheers,
>> Andreas
>>
>> Follow us on Twitter @3bananahttp://twitter.com/3banana
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

[twitter-dev] Re: Search results issue

[Matt Sanford]

Hi Chris,

I just checked your example and it looks like the third entry (http://twitter.com/dailythomas/statuses/1266693521 
) has what you expect. Perhaps the issue is that most people using  
#food are also using #recipe. For hashtags we index both the #term and  
term alone so people searching for 'recipe' will also find '#recipe'  
if they don't know about hashtags.


— Matt

On Mar 3, 2009, at 01:35 PM, Chris wrote:



Hi guys,

When I search for "recipe #food" - I was expecting to see tweets that
are tagged with #food, and also contain the text 'recipe'.

But it seems as though it is picking up results that are tagged with
"#food" AND tagged with "#recipe" - is this expected behavior? (ref:
http://search.twitter.com/search?q=recipe+%23food)

Cheers,


Chris Rickard.

[twitter-dev] Re: Posting a status update to the Mobile version of Twitter

[aschobel]

To clarify, we only want to prepopulate the status field.

This works on the standard version, doesn't work on the mobile
version.

It used to work on mobile version according to this thread:

http://groups.google.com/group/twitter-development-talk/browse_thread/thread/291311d3fda932bc/1d512b31e0860c5a

Cheers,
Andreas

Follow us on Twitter @3banana
http://twitter.com/3banana



On Mar 3, 1:00 pm, aschobel  wrote:
> We are having problems posting status updates to the mobile version of
> Twitter, it looks like the status input field for the mobile version
> comes with a default value of "".
>
>  value=""/>
>
> For the standard version of Twitter, we can pre-populate the status
> field by doing opening the following page:
>
> http://twitter.com/home?status=Hello%20world
>
> Our app for Android lets folks share their notes to Twitter, and this
> was working fine until Twitter started detecting the user agent for
> Android and giving people the mobile version instead of the standard
> version.
>
> Is there a way to force the Standard version? Passing in &ui_type=s
> doesn't do anything.
>
> We support Twidroid, but not everybody has that installed.
>
> Cheers,
> Andreas
>
> Follow us on Twitter @3bananahttp://twitter.com/3banana

[twitter-dev] Search results issue

[Chris]

Hi guys,

When I search for "recipe #food" - I was expecting to see tweets that
are tagged with #food, and also contain the text 'recipe'.

But it seems as though it is picking up results that are tagged with
"#food" AND tagged with "#recipe" - is this expected behavior? (ref:
http://search.twitter.com/search?q=recipe+%23food)

Cheers,


Chris Rickard.

[twitter-dev] Re: Consistent 502 errors for users with large friend & follower lists

[Alex Payne]

That would definitely require us to weigh our current knowledge of
Thrift vs Protocol Buffers. I'll think about it.

On Tue, Mar 3, 2009 at 12:42, Dossy Shiobara  wrote:
>
> On 3/3/09 3:07 PM, Alex Payne wrote:
>>
>> We're fully aware of what Protocol Buffers are their intended use. We
>> use Thrift, Facebook's clone of Protocol Buffers. You might note the
>> use of the world "internal" in the material you quoted.
>
> Quoting from http://code.google.com/apis/protocolbuffers/docs/faq.html:
>
>    "We would like to provide public APIs that accept protocol buffers as
> well as XML, both because it is more efficient and because we're just going
> to convert that XML to protocol buffers on our end anyway."
>
> Their use of the word "internal" simply clarifies where they _currently_ use
> it, not its limitation.
>
> Could Twitter be the first service to offer protocol buffers?  Sure.  I
> guess you're saying it's not going to happen, though.
>
> --
> Dossy Shiobara              | do...@panoptic.com | http://dossy.org/
> Panoptic Computer Network   | http://panoptic.com/
>  "He realized the fastest way to change is to laugh at your own
>    folly -- then you can let go and quickly move on." (p. 70)
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

[twitter-dev] Posting a status update to the Mobile version of Twitter

[aschobel]

We are having problems posting status updates to the mobile version of
Twitter, it looks like the status input field for the mobile version
comes with a default value of "".



For the standard version of Twitter, we can pre-populate the status
field by doing opening the following page:

http://twitter.com/home?status=Hello%20world


Our app for Android lets folks share their notes to Twitter, and this
was working fine until Twitter started detecting the user agent for
Android and giving people the mobile version instead of the standard
version.

Is there a way to force the Standard version? Passing in &ui_type=s
doesn't do anything.

We support Twidroid, but not everybody has that installed.

Cheers,
Andreas

Follow us on Twitter @3banana
http://twitter.com/3banana

[twitter-dev] Re: Rate limiting message in search

[Paul Kinlan]

Thats pretty much where I am handling the 503, my client code intercepts the
exception and then inspects the header.  The other thing I noticed, and it
is probably not best on this list is that you use WebRequest which raises a
WebException, and you can't get the 503 out of it easily (at least from what
I understand), where as HttpWebRequest raises HttpWebException which you can
directly check for a 503 error.

Anyway, I really enjoy using Tweet# and if any .Net devs out there need a
.Net Twitter library this is the one I recommend.

Paul

2009/3/3 Dimebrain 

>
> Thanks for the feedback; right now you can get at the response in
> instance.Root.Response (where instance is your FluentTwitter query),
> which will give you the instance of the last response returned. I'll
> look at this closer (unless you have a patch already of course).
>
> Daniel
>
> On Mar 3, 11:28 am, Paul Kinlan  wrote:
> > Hi Daniel,
> >
> > I am using tweet# a lot, and it would be good if you catch the 503 error
> > status on the rate limited requests (including the Retry-After header in
> the
> > response), I have had to implement it in tweet# for our product.
> >
> > Kind Regards,
> > Paul
> >
> > 2009/3/3 Dimebrain 
> >
> >
> >
> > > I have experienced sending search requests out which return a plain
> > > string, rather than JSON representing a twitter error. It's this:
> >
> > > "You have been rate limited. Enhance your calm."
> >
> > > a) What is the rate limiting based on, IP or client? What is the
> > > limit? I develop a Twitter library (tweetsharp) and by default I send
> > > the tweet# credentials along with the call. If this means that anyone
> > > using my library will be rate limited because of that header
> > > information, I need to know so I can force my users to provide their
> > > own credentials so that the library isn't unusable in this area, and
> >
> > > b) Can we get his as XML, JSON and not a plain string?
>

[twitter-dev] Re: Rate limiting message in search

[Dimebrain]

Thanks for the feedback; right now you can get at the response in
instance.Root.Response (where instance is your FluentTwitter query),
which will give you the instance of the last response returned. I'll
look at this closer (unless you have a patch already of course).

Daniel

On Mar 3, 11:28 am, Paul Kinlan  wrote:
> Hi Daniel,
>
> I am using tweet# a lot, and it would be good if you catch the 503 error
> status on the rate limited requests (including the Retry-After header in the
> response), I have had to implement it in tweet# for our product.
>
> Kind Regards,
> Paul
>
> 2009/3/3 Dimebrain 
>
>
>
> > I have experienced sending search requests out which return a plain
> > string, rather than JSON representing a twitter error. It's this:
>
> > "You have been rate limited. Enhance your calm."
>
> > a) What is the rate limiting based on, IP or client? What is the
> > limit? I develop a Twitter library (tweetsharp) and by default I send
> > the tweet# credentials along with the call. If this means that anyone
> > using my library will be rate limited because of that header
> > information, I need to know so I can force my users to provide their
> > own credentials so that the library isn't unusable in this area, and
>
> > b) Can we get his as XML, JSON and not a plain string?

[twitter-dev] Re: Rate limiting message in search

[Burhan TANWEER]

Thanks Paul,

I really appreciate it.


On Tue, Mar 3, 2009 at 3:20 PM, Paul Kinlan  wrote:

> Hi Burhan,
>
> Tweet# is a .Net twitter client API.  It has been developed in a fluent
> interface style so you construct your twitter requests in a manner that you
> can read from left to right.
>
> For example I use it to search:
>
> var result =
> FluentTwitter.CreateRequest().Search().Query().Containing("\"exeter
> city\"").Since(last_id).Return(10).Request();
>
> It Reads: Create a Request of type Search using a Query Containing ""exeter
> city"" Since the last id returning up to 10 results.
>
> It is on google code http://code.google.com/p/tweetsharp/
>
> Kind Regards,
> Paul Kinlan
>
>
> 2009/3/3 Burhan TANWEER 
>
>> Hi Paul,
>>
>> What is tweet#? Can you let us know more about it?
>>
>>   On Tue, Mar 3, 2009 at 2:28 PM, Paul Kinlan wrote:
>>
>>> Hi Daniel,
>>>
>>> I am using tweet# a lot, and it would be good if you catch the 503 error
>>> status on the rate limited requests (including the Retry-After header in the
>>> response), I have had to implement it in tweet# for our product.
>>>
>>> Kind Regards,
>>> Paul
>>>
>>> 2009/3/3 Dimebrain 
>>>

 I have experienced sending search requests out which return a plain
 string, rather than JSON representing a twitter error. It's this:

 "You have been rate limited. Enhance your calm."

 a) What is the rate limiting based on, IP or client? What is the
 limit? I develop a Twitter library (tweetsharp) and by default I send
 the tweet# credentials along with the call. If this means that anyone
 using my library will be rate limited because of that header
 information, I need to know so I can force my users to provide their
 own credentials so that the library isn't unusable in this area, and

 b) Can we get his as XML, JSON and not a plain string?


>>>
>>
>>
>> --
>> Sincerely,
>>
>> Burhan Tanweer
>> www.explorewww.com
>> expl...@explorewww.com
>>
>>
>


-- 
Sincerely,

Burhan Tanweer
www.explorewww.com
expl...@explorewww.com

[twitter-dev] Re: Consistent 502 errors for users with large friend & follower lists

[Dossy Shiobara]

On 3/3/09 3:07 PM, Alex Payne wrote:

We're fully aware of what Protocol Buffers are their intended use. We
use Thrift, Facebook's clone of Protocol Buffers. You might note the
use of the world "internal" in the material you quoted.


Quoting from http://code.google.com/apis/protocolbuffers/docs/faq.html:

"We would like to provide public APIs that accept protocol buffers 
as well as XML, both because it is more efficient and because we're just 
going to convert that XML to protocol buffers on our end anyway."


Their use of the word "internal" simply clarifies where they _currently_ 
use it, not its limitation.


Could Twitter be the first service to offer protocol buffers?  Sure.  I 
guess you're saying it's not going to happen, though.


--
Dossy Shiobara  | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network   | http://panoptic.com/
  "He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)

[twitter-dev] Re: advanced search with source: and a query returns error or nothing

[Matt Sanford]

Hi Steve,

There definitely seems to be a bug there. Please open an issue at http://code.google.com/p/twitter-api/issues/entry 
 and I'll take a look. I see you update issue #80 but please open a  
new one since this seem unrelated and I don't want to forget about it.


— Matt

On Mar 3, 2009, at 11:25 AM, woo wrote:



Hi, I'm trying to do a search for tweets from my iphone app
(source:ootunes) which doesn't work without a query string.  When I
add a query string that I know should return results:
http://search.twitter.com/search?q=source%3Aootunes+listening
Get either:

We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it
shortly.

or just a blank page without results.  I know this issue:
http://code.google.com/p/twitter-api/issues/detail?id=80 covers the
general use of source: filtering, but not sure if I should file
another for this result?  Any other way to find tweets from my app?
Steve

[twitter-dev] Re: Maximum length of a direct message?

[TjL]

On Tue, Mar 3, 2009 at 2:54 PM, Alex Payne  wrote:
>
> Our system may allow for DMs of longer than 140 characters, but I
> don't know if we'll support that in perpetuity. Hence, what's
> documented.

The website just recently (IIRC) started to enforce the 140 characters
rule in the past week or so. Before that it was possible to send
longer DMs even though the counter was below 0.

TjL

[twitter-dev] Re: Rate limiting message in search

[Paul Kinlan]

Hi Burhan,

Tweet# is a .Net twitter client API.  It has been developed in a fluent
interface style so you construct your twitter requests in a manner that you
can read from left to right.

For example I use it to search:

var result =
FluentTwitter.CreateRequest().Search().Query().Containing("\"exeter
city\"").Since(last_id).Return(10).Request();

It Reads: Create a Request of type Search using a Query Containing ""exeter
city"" Since the last id returning up to 10 results.

It is on google code http://code.google.com/p/tweetsharp/

Kind Regards,
Paul Kinlan


2009/3/3 Burhan TANWEER 

> Hi Paul,
>
> What is tweet#? Can you let us know more about it?
>
> On Tue, Mar 3, 2009 at 2:28 PM, Paul Kinlan  wrote:
>
>> Hi Daniel,
>>
>> I am using tweet# a lot, and it would be good if you catch the 503 error
>> status on the rate limited requests (including the Retry-After header in the
>> response), I have had to implement it in tweet# for our product.
>>
>> Kind Regards,
>> Paul
>>
>> 2009/3/3 Dimebrain 
>>
>>>
>>> I have experienced sending search requests out which return a plain
>>> string, rather than JSON representing a twitter error. It's this:
>>>
>>> "You have been rate limited. Enhance your calm."
>>>
>>> a) What is the rate limiting based on, IP or client? What is the
>>> limit? I develop a Twitter library (tweetsharp) and by default I send
>>> the tweet# credentials along with the call. If this means that anyone
>>> using my library will be rate limited because of that header
>>> information, I need to know so I can force my users to provide their
>>> own credentials so that the library isn't unusable in this area, and
>>>
>>> b) Can we get his as XML, JSON and not a plain string?
>>>
>>>
>>
>
>
> --
> Sincerely,
>
> Burhan Tanweer
> www.explorewww.com
> expl...@explorewww.com
>
>

[twitter-dev] Re: 500 internal error

[Chad Etzel]

I'm curious.

I have been trying to get a client-side javascript posting mechanism
to work for a long time, but gave up since cross-domain
xmlhttprequests are usually disallowed.  How did you get this to work?
 I just tried your code snippet out, and sure enough, got a permission
denied error in my console, and no request was sent.

Is it running in something other than a browser?

-Chad

On Wed, Feb 25, 2009 at 5:48 AM, Paul Haenel  wrote:
>
> Hi,
>
> Im getting a internal error which i execute this JavaScript function:
>
> function setTwitterStatus(twitterStatus){
>var twitterStatus = 'status='+twitterStatus;
>
>alert(twitterStatus);
>
>var req = new XMLHttpRequest();
>
>req.open('POST', 'http://twitter.com/statuses/update.json',1);
>req.setRequestHeader('Authorization', 'Basic '+Base64.encode
> (twitterUsername+':'+twitterPassword));
>req.onreadystatechange = function(){
>if(req.readyState ==4){
>alert(req.responseText);
>}
>}
>req.send(twitterStatus);
> }
>
> twitter status is is a plain text like "hello" or " is working hard."
>
> here is s acopy of the response:
>
> Status: 500 Internal Server Error
> Content-Type: text/html
>
> 500 Internal Server ErrorStatus:
> 500 Internal Server Error
> Content-Type: text/html
>
> 500 Internal Server Error
>
> Any help appreciated.
>
> Thanks Paul
>

[twitter-dev] Re: Consistent 502 errors for users with large friend & follower lists

[Alex Payne]

We're fully aware of what Protocol Buffers are their intended use. We
use Thrift, Facebook's clone of Protocol Buffers. You might note the
use of the world "internal" in the material you quoted.

On Tue, Mar 3, 2009 at 12:05, Dossy Shiobara  wrote:
>
> On 3/3/09 2:51 PM, Alex Payne wrote:
>>
>> Protocol Buffers aren't really designed for over-the-Internet APIs.
>> Unless I'm mistaken, I don't believe that Google allows third-party
>> interaction with their services over Protocol Buffers.
>
> From the Protocol Buffers project page:
>
> "Protocol Buffers are a way of encoding structured data in an efficient yet
> extensible format. Google uses Protocol Buffers for almost all of its
> internal RPC protocols and file formats."
>
> Protocol Buffers are definitely well-designed for over-the-Internet APIs.
>  It's a means of encoding structured data, like XML is, but efficient.
>
> XML and JSON are swell, but they suck for any non-trivial amount of data
> where the structure's overhead really starts to add up.
>
> --
> Dossy Shiobara              | do...@panoptic.com | http://dossy.org/
> Panoptic Computer Network   | http://panoptic.com/
>  "He realized the fastest way to change is to laugh at your own
>    folly -- then you can let go and quickly move on." (p. 70)
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

[twitter-dev] advanced search with source: and a query returns error or nothing

[woo]

Hi, I'm trying to do a search for tweets from my iphone app
(source:ootunes) which doesn't work without a query string.  When I
add a query string that I know should return results:
http://search.twitter.com/search?q=source%3Aootunes+listening
Get either:

We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it
shortly.

or just a blank page without results.  I know this issue:
http://code.google.com/p/twitter-api/issues/detail?id=80 covers the
general use of source: filtering, but not sure if I should file
another for this result?  Any other way to find tweets from my app?
Steve

[twitter-dev] Re: Rate limiting message in search

[Burhan TANWEER]

Hi Paul,

What is tweet#? Can you let us know more about it?

On Tue, Mar 3, 2009 at 2:28 PM, Paul Kinlan  wrote:

> Hi Daniel,
>
> I am using tweet# a lot, and it would be good if you catch the 503 error
> status on the rate limited requests (including the Retry-After header in the
> response), I have had to implement it in tweet# for our product.
>
> Kind Regards,
> Paul
>
> 2009/3/3 Dimebrain 
>
>>
>> I have experienced sending search requests out which return a plain
>> string, rather than JSON representing a twitter error. It's this:
>>
>> "You have been rate limited. Enhance your calm."
>>
>> a) What is the rate limiting based on, IP or client? What is the
>> limit? I develop a Twitter library (tweetsharp) and by default I send
>> the tweet# credentials along with the call. If this means that anyone
>> using my library will be rate limited because of that header
>> information, I need to know so I can force my users to provide their
>> own credentials so that the library isn't unusable in this area, and
>>
>> b) Can we get his as XML, JSON and not a plain string?
>>
>>
>


-- 
Sincerely,

Burhan Tanweer
www.explorewww.com
expl...@explorewww.com

[twitter-dev] Re: Consistent 502 errors for users with large friend & follower lists

[Dossy Shiobara]

On 3/3/09 2:51 PM, Alex Payne wrote:

Protocol Buffers aren't really designed for over-the-Internet APIs.
Unless I'm mistaken, I don't believe that Google allows third-party
interaction with their services over Protocol Buffers.


From the Protocol Buffers project page:

"Protocol Buffers are a way of encoding structured data in an efficient 
yet extensible format. Google uses Protocol Buffers for almost all of 
its internal RPC protocols and file formats."


Protocol Buffers are definitely well-designed for over-the-Internet 
APIs.  It's a means of encoding structured data, like XML is, but efficient.


XML and JSON are swell, but they suck for any non-trivial amount of data 
where the structure's overhead really starts to add up.


--
Dossy Shiobara  | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network   | http://panoptic.com/
  "He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)

[twitter-dev] Re: Maximum length of a direct message?

[Alex Payne]

Our system may allow for DMs of longer than 140 characters, but I
don't know if we'll support that in perpetuity. Hence, what's
documented.

I'm not crazy about the tips and how unpredictable they make message
length, but it's not up to me.

On Tue, Mar 3, 2009 at 11:26, Chad Etzel  wrote:
>
> Ok, well I stand corrected.  Now I'm not getting "d username" tips for
> any sized DMs through SMS.  So, nevermind :)
> -chad
>
> On Tue, Mar 3, 2009 at 2:07 PM, dougw  wrote:
>>
>> Chad,
>> I just sent myself:
>> 1) 40 character DM and did receive the tip. The message was contained
>> to a single text.
>>
>> 2) 150 character DM and did not receive the tip. The message was
>> contained to a single text message.
>>
>> 2) 170 character DM and the message was split into two SMS texts. The
>> second SMS text did not have the tip.
>>
>> Color me confused why I'm not getting the tip now in these tests.
>>
>> Doug
>> @dougw
>>
>> On Mar 3, 1:58 pm, Chad Etzel  wrote:
>>> Unless things changed recently, this is not my experience at all.  The
>>>  "d username to reply" info always came through and frequently spilled
>>> over to a 2nd message thus doubling my txt rate for every DM
>>> received.  Since I don't have unlimited text, that promptly caused me
>>> to disable DMs at SMS.
>>>
>>> -Chad
>>>
>>> On Tue, Mar 3, 2009 at 1:43 PM, Doug Williams  wrote:
>>> > Well said.
>>>
>>> > In my experience, the tip ("d TwitterName to reply") at the bottom of the
>>> > SMS delivered direct message is only applied if it does not extend the
>>> > message beyond the 160 char boundary of the current text message. (This 
>>> > same
>>> > behavior is also seen when you subscribe to SMS device notifications for
>>> > specific user updates.)
>>>
>>> > Thanks,
>>> > Doug
>>> > @dougw
>>>
>>> > On Tue, Mar 3, 2009 at 1:34 PM, TjL  wrote:
>>>
>>> >> On Tue, Mar 3, 2009 at 12:30 PM, Craig Hockenberry
>>> >>  wrote:
>>>
>>> >> > Won't this present a problem for users who are getting their direct
>>> >> > messages through SMS? Do they get truncated on delivery?
>>>
>>> >> Hi Craig :-)
>>>
>>> >> FWIW: Almost *all* DMs come through as two SMSes.
>>>
>>> >> Why?
>>>
>>> >> Because "Direct Message from " is prepended to the
>>> >> message, which counts towards the 160 character SMS limit AND (what is
>>> >> worse) Twitter also appends something like "Use d TwitterName to
>>> >> reply"
>>>
>>> >> (I left my iPhone home today or I could give you the exact message).
>>>
>>> >> The second SMS is almost always just the last bit of the message: "d
>>> >> TwitterName to reply"
>>>
>>> >> So unless Twitter stops appending the "How to reply to a DM via SMS",
>>> >> sending a DM that is longer than 140 characters not really going to
>>> >> cause much of a hardship. The second SMS will simply have more actual
>>> >> content in it :-) And there's little to no chance that you'll reach
>>> >> the length of having *3* SMSes (320 characters)
>>>
>>> >> TjL
>>>
>>> > --
>>> > Doug Williams
>>>
>>> > do...@igudo.com
>>> >http://www.igudo.com
>>>
>>>
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

[twitter-dev] Re: Consistent 502 errors for users with large friend & follower lists

[Alex Payne]

Protocol Buffers aren't really designed for over-the-Internet APIs.
Unless I'm mistaken, I don't believe that Google allows third-party
interaction with their services over Protocol Buffers.

On Mon, Mar 2, 2009 at 19:37, Abraham Williams <4bra...@gmail.com> wrote:
> There is always json.
> Perhaps Twitter will consider implementing Protocol Buffers.
> Google uses this lightweight protocol
> internally: http://code.google.com/p/protobuf/
> I don't know how it compares to json performance wise though.
> On Mon, Mar 2, 2009 at 19:14, Jeffrey Greenberg 
> wrote:
>>
>> My app (tweettronics.com) fetches friends and followers for a given
>> user with the following pair of calls, done one immediately after the
>> other:
>> http://twitter.com/friends/ids.xml
>> http://twitter.com/followers/ids.xml
>>
>> They take quite a while on large users (understandably up to a 2-3megs
>> of data via XML encoding), but worse they often fail with a 502 error.
>>
>> It's easy to see on user barackobama and less frequently as you go
>> down the top 10 lists... e.g. on ev ... somewhere around 200k
>> followers it's less frequent
>>
>> Can this be addressed on your side?
>>
>> BTW: I want this data pretty fresh and I'd like to avoid duplicating
>> the Twitter DB, so I'm wanting to avoid caching these calls... still I
>> can imagine caching as viable just to improve the performance of
>> transferring the large ist   Nonetheless, since you are deep into
>> facing massive data growth, I'm wondering if there are any interesting
>> alternatives to a scheme that transfers something other than XML, one
>> that pack more data/byte?
>>
>> Thanks
>> Jeffrey
>>
>> http://www.jeffrey-greenberg.com
>>
>>
>>
>>
>>
>
>
>
> --
> Abraham Williams | http://the.hackerconundrum.com
> Web608 | Community Evangelist | http://web608.org
> This email is: [ ] blogable [x] ask first [ ] private.
> Sent from: Madison Wisconsin United States.



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

[twitter-dev] Re: 400 Bad Request from Twitter RSS Feed

[Alex Payne]

We have, actually. I'm guessing they expanded to more IPs and haven't
yet requested whitelisting for those new IPs.

On Tue, Mar 3, 2009 at 10:16, David Neubauer  wrote:
>
> Maybe they should whitelist yahoo pipes? :)
>
> Regards,
>
> David Neubauer
> 832-252-9004
>
>
> -Original Message-
> From: twitter-development-talk@googlegroups.com
> [mailto:twitter-development-t...@googlegroups.com] On Behalf Of travelvice
> Sent: Tuesday, March 03, 2009 10:17 AM
> To: Twitter Development Talk
> Subject: [twitter-dev] Re: 400 Bad Request from Twitter RSS Feed
>
>
> Exactly -- For me, it looks like this:
>
> warning error fetching
> http://twitter.com/statuses/user_timeline/21192372.rss
> (400 Bad Request)
>
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

[twitter-dev] Re: 500 internal error

[Alex Payne]

I think you'll find that Charles doesn't require a special plugin for
Safari. If you allow it to automatically configure your proxy setup,
it Just Works.

On Tue, Mar 3, 2009 at 01:36, Paul Haenel  wrote:
>
> Hi Ed,
>
> Thank you very much for getting back to.
>
> Charles doesnt help me because im using Safari and there is no plug in
> for it and i cant use Firefox for my project.
>
> Any other suggestions??
>
> Paul
>
>
> On Feb 25, 2:47 pm, Ed Finkler  wrote:
>> Try using adebuggingproxylikeCharlesso you can see the exact
>> request being sent. That aids greatly in sorting out things like this.
>>
>> --
>> Ed Finklerhttp://funkatron.com
>> Twitter:@funkatron
>> AIM: funka7ron
>> ICQ: 3922133
>> XMPP:funkat...@gmail.com
>>
>> On Feb 25, 5:48 am, Paul Haenel  wrote:
>>
>> > Hi,
>>
>> > Im getting a internal error which i execute this JavaScript function:
>>
>> > function setTwitterStatus(twitterStatus){
>> >     var twitterStatus = 'status='+twitterStatus;
>>
>> >     alert(twitterStatus);
>>
>> >     var req = new XMLHttpRequest();
>>
>> >     req.open('POST', 'http://twitter.com/statuses/update.json',1);
>> >     req.setRequestHeader('Authorization', 'Basic '+Base64.encode
>> > (twitterUsername+':'+twitterPassword));
>> >     req.onreadystatechange = function(){
>> >         if(req.readyState ==4){
>> >             alert(req.responseText);
>> >         }
>> >     }
>> >     req.send(twitterStatus);
>>
>> > }
>>
>> > twitter status is is a plain text like "hello" or " is working hard."
>>
>> > here is s acopy of the response:
>>
>> > Status: 500 Internal Server Error
>> > Content-Type: text/html
>>
>> > 500 Internal Server ErrorStatus:
>> > 500 Internal Server Error
>> > Content-Type: text/html
>>
>> > 500 Internal Server Error
>>
>> > Any help appreciated.
>>
>> > Thanks Paul
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

[twitter-dev] Re: Rate limiting message in search

[Paul Kinlan]

Hi Daniel,

I am using tweet# a lot, and it would be good if you catch the 503 error
status on the rate limited requests (including the Retry-After header in the
response), I have had to implement it in tweet# for our product.

Kind Regards,
Paul

2009/3/3 Dimebrain 

>
> I have experienced sending search requests out which return a plain
> string, rather than JSON representing a twitter error. It's this:
>
> "You have been rate limited. Enhance your calm."
>
> a) What is the rate limiting based on, IP or client? What is the
> limit? I develop a Twitter library (tweetsharp) and by default I send
> the tweet# credentials along with the call. If this means that anyone
> using my library will be rate limited because of that header
> information, I need to know so I can force my users to provide their
> own credentials so that the library isn't unusable in this area, and
>
> b) Can we get his as XML, JSON and not a plain string?
>
>

[twitter-dev] Re: Maximum length of a direct message?

[Chad Etzel]

Ok, well I stand corrected.  Now I'm not getting "d username" tips for
any sized DMs through SMS.  So, nevermind :)
-chad

On Tue, Mar 3, 2009 at 2:07 PM, dougw  wrote:
>
> Chad,
> I just sent myself:
> 1) 40 character DM and did receive the tip. The message was contained
> to a single text.
>
> 2) 150 character DM and did not receive the tip. The message was
> contained to a single text message.
>
> 2) 170 character DM and the message was split into two SMS texts. The
> second SMS text did not have the tip.
>
> Color me confused why I'm not getting the tip now in these tests.
>
> Doug
> @dougw
>
> On Mar 3, 1:58 pm, Chad Etzel  wrote:
>> Unless things changed recently, this is not my experience at all.  The
>>  "d username to reply" info always came through and frequently spilled
>> over to a 2nd message thus doubling my txt rate for every DM
>> received.  Since I don't have unlimited text, that promptly caused me
>> to disable DMs at SMS.
>>
>> -Chad
>>
>> On Tue, Mar 3, 2009 at 1:43 PM, Doug Williams  wrote:
>> > Well said.
>>
>> > In my experience, the tip ("d TwitterName to reply") at the bottom of the
>> > SMS delivered direct message is only applied if it does not extend the
>> > message beyond the 160 char boundary of the current text message. (This 
>> > same
>> > behavior is also seen when you subscribe to SMS device notifications for
>> > specific user updates.)
>>
>> > Thanks,
>> > Doug
>> > @dougw
>>
>> > On Tue, Mar 3, 2009 at 1:34 PM, TjL  wrote:
>>
>> >> On Tue, Mar 3, 2009 at 12:30 PM, Craig Hockenberry
>> >>  wrote:
>>
>> >> > Won't this present a problem for users who are getting their direct
>> >> > messages through SMS? Do they get truncated on delivery?
>>
>> >> Hi Craig :-)
>>
>> >> FWIW: Almost *all* DMs come through as two SMSes.
>>
>> >> Why?
>>
>> >> Because "Direct Message from " is prepended to the
>> >> message, which counts towards the 160 character SMS limit AND (what is
>> >> worse) Twitter also appends something like "Use d TwitterName to
>> >> reply"
>>
>> >> (I left my iPhone home today or I could give you the exact message).
>>
>> >> The second SMS is almost always just the last bit of the message: "d
>> >> TwitterName to reply"
>>
>> >> So unless Twitter stops appending the "How to reply to a DM via SMS",
>> >> sending a DM that is longer than 140 characters not really going to
>> >> cause much of a hardship. The second SMS will simply have more actual
>> >> content in it :-) And there's little to no chance that you'll reach
>> >> the length of having *3* SMSes (320 characters)
>>
>> >> TjL
>>
>> > --
>> > Doug Williams
>>
>> > do...@igudo.com
>> >http://www.igudo.com
>>
>>

[twitter-dev] Re: Consistent 502 errors for users with large friend & follower lists

[Doug Williams]

Jeffrey,
Do you think a paging interface for the social graph methods would quickly
solve this problem? In that way, you could limit the number of users
returned with each call (thus limiting the number of bytes returned per
call).

Doug
@dougw


On Tue, Mar 3, 2009 at 12:56 PM, Jeffrey Greenberg <
jeffreygreenb...@gmail.com> wrote:

>
> True JSON is probably more compact.   But NO to Google's Protocol
> Buffers - it's yet another RPC interface requiring compilation.
>
> But really I want to focus on the 502 errors!
>



-- 
Doug Williams

do...@igudo.com
http://www.igudo.com

[twitter-dev] Re: Consistent 502 errors for users with large friend & follower lists

[Jeffrey Greenberg]

True JSON is probably more compact.   But NO to Google's Protocol
Buffers - it's yet another RPC interface requiring compilation.

But really I want to focus on the 502 errors!

[twitter-dev] Re: Maximum length of a direct message?

[dougw]

Chad,
I just sent myself:
1) 40 character DM and did receive the tip. The message was contained
to a single text.

2) 150 character DM and did not receive the tip. The message was
contained to a single text message.

2) 170 character DM and the message was split into two SMS texts. The
second SMS text did not have the tip.

Color me confused why I'm not getting the tip now in these tests.

Doug
@dougw

On Mar 3, 1:58 pm, Chad Etzel  wrote:
> Unless things changed recently, this is not my experience at all.  The
>  "d username to reply" info always came through and frequently spilled
> over to a 2nd message thus doubling my txt rate for every DM
> received.  Since I don't have unlimited text, that promptly caused me
> to disable DMs at SMS.
>
> -Chad
>
> On Tue, Mar 3, 2009 at 1:43 PM, Doug Williams  wrote:
> > Well said.
>
> > In my experience, the tip ("d TwitterName to reply") at the bottom of the
> > SMS delivered direct message is only applied if it does not extend the
> > message beyond the 160 char boundary of the current text message. (This same
> > behavior is also seen when you subscribe to SMS device notifications for
> > specific user updates.)
>
> > Thanks,
> > Doug
> > @dougw
>
> > On Tue, Mar 3, 2009 at 1:34 PM, TjL  wrote:
>
> >> On Tue, Mar 3, 2009 at 12:30 PM, Craig Hockenberry
> >>  wrote:
>
> >> > Won't this present a problem for users who are getting their direct
> >> > messages through SMS? Do they get truncated on delivery?
>
> >> Hi Craig :-)
>
> >> FWIW: Almost *all* DMs come through as two SMSes.
>
> >> Why?
>
> >> Because "Direct Message from " is prepended to the
> >> message, which counts towards the 160 character SMS limit AND (what is
> >> worse) Twitter also appends something like "Use d TwitterName to
> >> reply"
>
> >> (I left my iPhone home today or I could give you the exact message).
>
> >> The second SMS is almost always just the last bit of the message: "d
> >> TwitterName to reply"
>
> >> So unless Twitter stops appending the "How to reply to a DM via SMS",
> >> sending a DM that is longer than 140 characters not really going to
> >> cause much of a hardship. The second SMS will simply have more actual
> >> content in it :-) And there's little to no chance that you'll reach
> >> the length of having *3* SMSes (320 characters)
>
> >> TjL
>
> > --
> > Doug Williams
>
> > do...@igudo.com
> >http://www.igudo.com
>
>

[twitter-dev] Re: Maximum length of a direct message?

[TjL]

On Tue, Mar 3, 2009 at 1:43 PM, Doug Williams  wrote:

> In my experience, the tip ("d TwitterName to reply") at the bottom of the
> SMS delivered direct message is only applied if it does not extend the
> message beyond the 160 char boundary of the current text message.

If that's the case, why does it result in a second SMS being sent?

Honest question. If the message plus header/footer is less than 160,
it shouldn't overflow onto a 2nd SMS, but as I said, almost every DM
that I get from Twitter comes as two with just the footer in the 2nd
message.

TjL

[twitter-dev] Re: Rate limiting message in search

[Chad Etzel]

If I remember correctly, the HTTP response code for rate limiting is
something other that 200 (which doesn't really do much good if you're
using a JSONP type request from a browser), so jsonifying or xmlifying
that rate limit string would be useful.  I suggest opening an issue
for it.

As for credentials, search requests are totally unauthenticated, so
you needn't send any credentials along with the search request.

-Chad

On Tue, Mar 3, 2009 at 1:46 PM, John Adams  wrote:
>
> Rate limiting is based on the IP address of the client.
>
> -j
>
> On Mar 3, 2009, at 10:42 AM, Dimebrain wrote:
>
>>
>> I have experienced sending search requests out which return a plain
>> string, rather than JSON representing a twitter error. It's this:
>>
>> "You have been rate limited. Enhance your calm."
>>
>> a) What is the rate limiting based on, IP or client? What is the
>> limit? I develop a Twitter library (tweetsharp) and by default I send
>> the tweet# credentials along with the call. If this means that anyone
>> using my library will be rate limited because of that header
>> information, I need to know so I can force my users to provide their
>> own credentials so that the library isn't unusable in this area, and
>>
>> b) Can we get his as XML, JSON and not a plain string?
>>
>
> ---
> John Adams
> Twitter Operations
> j...@twitter.com
> http://twitter.com/netik
>
>
>
>
>

[twitter-dev] Re: Maximum length of a direct message?

[Chad Etzel]

Unless things changed recently, this is not my experience at all.  The
 "d username to reply" info always came through and frequently spilled
over to a 2nd message thus doubling my txt rate for every DM
received.  Since I don't have unlimited text, that promptly caused me
to disable DMs at SMS.

-Chad

On Tue, Mar 3, 2009 at 1:43 PM, Doug Williams  wrote:
> Well said.
>
> In my experience, the tip ("d TwitterName to reply") at the bottom of the
> SMS delivered direct message is only applied if it does not extend the
> message beyond the 160 char boundary of the current text message. (This same
> behavior is also seen when you subscribe to SMS device notifications for
> specific user updates.)
>
> Thanks,
> Doug
> @dougw
>
> On Tue, Mar 3, 2009 at 1:34 PM, TjL  wrote:
>>
>> On Tue, Mar 3, 2009 at 12:30 PM, Craig Hockenberry
>>  wrote:
>> >
>> > Won't this present a problem for users who are getting their direct
>> > messages through SMS? Do they get truncated on delivery?
>>
>> Hi Craig :-)
>>
>> FWIW: Almost *all* DMs come through as two SMSes.
>>
>> Why?
>>
>> Because "Direct Message from " is prepended to the
>> message, which counts towards the 160 character SMS limit AND (what is
>> worse) Twitter also appends something like "Use d TwitterName to
>> reply"
>>
>> (I left my iPhone home today or I could give you the exact message).
>>
>> The second SMS is almost always just the last bit of the message: "d
>> TwitterName to reply"
>>
>> So unless Twitter stops appending the "How to reply to a DM via SMS",
>> sending a DM that is longer than 140 characters not really going to
>> cause much of a hardship. The second SMS will simply have more actual
>> content in it :-) And there's little to no chance that you'll reach
>> the length of having *3* SMSes (320 characters)
>>
>> TjL
>
>
>
> --
> Doug Williams
>
> do...@igudo.com
> http://www.igudo.com
>

[twitter-dev] Re: Rate limiting message in search

[John Adams]

Rate limiting is based on the IP address of the client.

-j

On Mar 3, 2009, at 10:42 AM, Dimebrain wrote:



I have experienced sending search requests out which return a plain
string, rather than JSON representing a twitter error. It's this:

"You have been rate limited. Enhance your calm."

a) What is the rate limiting based on, IP or client? What is the
limit? I develop a Twitter library (tweetsharp) and by default I send
the tweet# credentials along with the call. If this means that anyone
using my library will be rate limited because of that header
information, I need to know so I can force my users to provide their
own credentials so that the library isn't unusable in this area, and

b) Can we get his as XML, JSON and not a plain string?



---
John Adams
Twitter Operations
j...@twitter.com
http://twitter.com/netik

[twitter-dev] Re: Maximum length of a direct message?

[Doug Williams]

Well said.

In my experience, the tip ("d TwitterName to reply") at the bottom of the
SMS delivered direct message is only applied if it does not extend the
message beyond the 160 char boundary of the current text message. (This same
behavior is also seen when you subscribe to SMS device notifications for
specific user updates.)

Thanks,
Doug
@dougw

On Tue, Mar 3, 2009 at 1:34 PM, TjL  wrote:

>
> On Tue, Mar 3, 2009 at 12:30 PM, Craig Hockenberry
>  wrote:
> >
> > Won't this present a problem for users who are getting their direct
> > messages through SMS? Do they get truncated on delivery?
>
> Hi Craig :-)
>
> FWIW: Almost *all* DMs come through as two SMSes.
>
> Why?
>
> Because "Direct Message from " is prepended to the
> message, which counts towards the 160 character SMS limit AND (what is
> worse) Twitter also appends something like "Use d TwitterName to
> reply"
>
> (I left my iPhone home today or I could give you the exact message).
>
> The second SMS is almost always just the last bit of the message: "d
> TwitterName to reply"
>
> So unless Twitter stops appending the "How to reply to a DM via SMS",
> sending a DM that is longer than 140 characters not really going to
> cause much of a hardship. The second SMS will simply have more actual
> content in it :-) And there's little to no chance that you'll reach
> the length of having *3* SMSes (320 characters)
>
> TjL
>



-- 
Doug Williams

do...@igudo.com
http://www.igudo.com

[twitter-dev] Rate limiting message in search

[Dimebrain]

I have experienced sending search requests out which return a plain
string, rather than JSON representing a twitter error. It's this:

"You have been rate limited. Enhance your calm."

a) What is the rate limiting based on, IP or client? What is the
limit? I develop a Twitter library (tweetsharp) and by default I send
the tweet# credentials along with the call. If this means that anyone
using my library will be rate limited because of that header
information, I need to know so I can force my users to provide their
own credentials so that the library isn't unusable in this area, and

b) Can we get his as XML, JSON and not a plain string?

[twitter-dev] Re: Maximum length of a direct message?

[TjL]

On Tue, Mar 3, 2009 at 12:30 PM, Craig Hockenberry
 wrote:
>
> Won't this present a problem for users who are getting their direct
> messages through SMS? Do they get truncated on delivery?

Hi Craig :-)

FWIW: Almost *all* DMs come through as two SMSes.

Why?

Because "Direct Message from " is prepended to the
message, which counts towards the 160 character SMS limit AND (what is
worse) Twitter also appends something like "Use d TwitterName to
reply"

(I left my iPhone home today or I could give you the exact message).

The second SMS is almost always just the last bit of the message: "d
TwitterName to reply"

So unless Twitter stops appending the "How to reply to a DM via SMS",
sending a DM that is longer than 140 characters not really going to
cause much of a hardship. The second SMS will simply have more actual
content in it :-) And there's little to no chance that you'll reach
the length of having *3* SMSes (320 characters)

TjL

[twitter-dev] Re: 400 Bad Request from Twitter RSS Feed

[David Neubauer]

Maybe they should whitelist yahoo pipes? :)

Regards,

David Neubauer
832-252-9004


-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of travelvice
Sent: Tuesday, March 03, 2009 10:17 AM
To: Twitter Development Talk
Subject: [twitter-dev] Re: 400 Bad Request from Twitter RSS Feed


Exactly -- For me, it looks like this:

warning error fetching
http://twitter.com/statuses/user_timeline/21192372.rss
(400 Bad Request)

[twitter-dev] Re: Twitter Feed into a Chat Room

[David Neubauer]

I'll do it. :)

Regards,

David Neubauer
832-252-9004


-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of BrummiesFans
Sent: Tuesday, March 03, 2009 8:13 AM
To: Twitter Development Talk
Subject: [twitter-dev] Twitter Feed into a Chat Room


Hi

I run a phpBB3 forum which has an AJAX Chat Room added to it. What I'd
appreciate is for a facility whereby an RSS feed from my Twitter
account could be used to add newsflashes into the live chat room.

The scenario for its use would be when sporting fans go to "away"
sporting fixtures, they can update scores via their mobile phone to
Twitter, then, using the RSS feed from Twitter, the chatroom cabn
receive and show the updates for onward discussion by those "stay at
home" fans who are using the chat room.

That's the principle.Now what is needed is someome willing to
volunteer, who has the required PHP programming skills who can modify
the AJAX Chat MOD to phpBB3 (all readily available at www.phpbb.com)

I hope that someone would be able to take up the cause, and look
forward to seeing how this idea develops.

Thanks

Martin

[twitter-dev] Re: Twitter Feed into a Chat Room

[David Neubauer]

I'll do this...

Regards,

David Neubauer
832-252-9004


-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of BrummiesFans
Sent: Tuesday, March 03, 2009 8:13 AM
To: Twitter Development Talk
Subject: [twitter-dev] Twitter Feed into a Chat Room


Hi

I run a phpBB3 forum which has an AJAX Chat Room added to it. What I'd
appreciate is for a facility whereby an RSS feed from my Twitter
account could be used to add newsflashes into the live chat room.

The scenario for its use would be when sporting fans go to "away"
sporting fixtures, they can update scores via their mobile phone to
Twitter, then, using the RSS feed from Twitter, the chatroom cabn
receive and show the updates for onward discussion by those "stay at
home" fans who are using the chat room.

That's the principle.Now what is needed is someome willing to
volunteer, who has the required PHP programming skills who can modify
the AJAX Chat MOD to phpBB3 (all readily available at www.phpbb.com)

I hope that someone would be able to take up the cause, and look
forward to seeing how this idea develops.

Thanks

Martin

[twitter-dev] Re: 400 Bad Request from Twitter RSS Feed

[travelvice]

Exactly -- For me, it looks like this:

warning error fetching http://twitter.com/statuses/user_timeline/21192372.rss
(400 Bad Request)

[twitter-dev] Re: Twitter Search issue

[Paul Kinlan]

Hi,

Yeah, I am pretty sure our Api client takes a litteral query string and
since we store it that way it is probablly sending it that way.

Paul.

2009/3/3 Matt Sanford 

> Hi all,
>  If you send something invalid we do attempt to fix-up invalid requests
> rather than just 400. This looks like a case where the bad request becomes a
> different sort of badness on the way out. Escaping the quotes seems like the
> only real fix.
>
> — Matt
>
> On Mar 3, 2009, at 09:13 AM, Chad Etzel wrote:
>
>
> Ok, I can replicate your results with curl
>
> $ curl -v "http://search.twitter.com/search.json?q=\"exeter%20city\"";
>
> ...returns the wrong results, as you say.
>
> $ curl -v "http://search.twitter.com/search.json?q=%22exeter%20city%22";
>
> ...returns the correct results.
>
> I think double quotes are not actually valid URL characters (tho some
> browsers try to treat them as such), so you should really turn " into
> %22 before the requests go out.
>
>
> That said, I'm starting to agree with Paul that twitter is doing some
> sort of encoding trick on their end when literal quotes are sent in
> the request:
>
> $ curl -v http://search.twitter.com/search.json?q=\"exeter%20city\";
> * About to connect() to search.twitter.com port 80 (#0)
> *   Trying 128.121.146.107... connected
> * Connected to search.twitter.com (128.121.146.107) port 80 (#0)
>
> GET /search.json?q="exeter%20city" HTTP/1.1
>
> User-Agent: curl/7.16.4 (i486-pc-linux-gnu) libcurl/7.16.4 OpenSSL/0.9.8e
> zlib/1.2.3.3 libidn/1.0
>
> Host: search.twitter.com
>
> Accept: */*
>
>
> < HTTP/1.1 200 OK
> < Date: Tue, 03 Mar 2009 17:09:34 GMT
> < Server: hi
> < Status: 200 OK
> < Cache-Control: max-age=20, must-revalidate, max-age=300
> < Content-Type: application/json; charset=utf-8
> < X-Served-By: searchweb003.twitter.com
> < Expires: Tue, 03 Mar 2009 17:14:34 GMT
> < Content-Length: 195
> < Vary: Accept-Encoding
> < X-Varnish: 1733084231
> < Age: 0
> < Via: 1.1 varnish
> < X-Cache-Svr: searchweb003.twitter.com
> < X-Cache: MISS
> < Connection: close
> <
> * Closing connection #0
>
> {"results":[],"since_id":0,"max_id":1274236746,"refresh_url":"?since_id=1274236746&q=%22exeter%2520city%22","results_per_page":15,"completed_in":0.112164,"page":1,"query":"%22exeter%2520city%22"}
>
> Now, one could argue that the request itself is invalid or malformed,
> and so the result may be undefined, but I do agree that something is
> happening on twitter's end.
>
>
> Moral of the story: encode " as %22 in URLs.
>
> -Chad
>
> On Tue, Mar 3, 2009 at 11:33 AM, Paul Kinlan 
> wrote:
>
> Hi,
>
>
> It works with the "+", but I knew that :)
>
>
> With a space (in IE) it encodes it as %20 when it makes the request and I
>
> can see it through fiddler (as below) and it comes back.
>
>
> GET /search.json?q="exeter%20city" HTTP/1.1
>
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
>
> application/x-ms-application, application/vnd.ms-xpsdocument,
>
> application/xaml+xml, application/x-ms-xbap, application/x-shockwave-flash,
>
> application/vnd.ms-excel, application/vnd.ms-powerpoint,
> application/msword,
>
> */*
>
> Accept-Language: en-gb
>
> UA-CPU: x86
>
> Accept-Encoding: gzip, deflate
>
> User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET
>
> CLR 2.0.50727; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30618;
>
> InfoPath.2; OfficeLiveConnector.1.3; OfficeLivePatch.0.0)
>
> Host: search.twitter.com
>
> Connection: Keep-Alive
>
> Cookie:
>
> __utma=43838368.379476752167577530.1234449205.1234449205.1234449205.1;
>
> __utmz=43838368.1234449205.1.1.utmcsr=blog.twe2.com
> |utmccn=(referral)|utmcmd=referral|utmcct=/;
>
> __utmv=43838368.lang%3A%20en_GB
>
>
> I fully accept it is probably our client software that is not encoding
>
> correcly, but I also tried this from the command line curl
>
> "http://search.twitter.com/search.json?q=\"exeter%20city\""; the response
>
> comes back as %22exeter%2520city%22 in the json object.  From my point of
>
> view I know the quotes are not correct, but it looks like twitter is
>
> encoding them when it recieves them.  I belive our client API is sending
>
> double quotes rather %22.
>
>
> Kind Regards,
>
> Paul
>
>
> 2009/3/3 Chad Etzel 
>
>
> I also just tested searching "exeter city" in TweetGrid with IE,
>
> FireFox, and Chrome. All came back with the same results.
>
> fwiw,
>
> -Chad
>
>
> On Tue, Mar 3, 2009 at 11:14 AM, Matt Sanford  wrote:
>
> Hi Paul,
>
>I just tested form the command line and everything seems fine
>
> with: curl
>
> 'http://search.twitter.com/search.json?q=%22exeter%20city%22'
>
>If you are typing %20 into the IE address bar it is likely try to
>
> correct your %  (which is not a valid URL character) and making it %25
>
> in
>
> the request but displaying it correctly to you. Try replacing it with a
>
> + or
>
> a space and see what you get.
>
> Thanks;
>
>  — Matt
>
> - Show quoted text -
>
> On M

[twitter-dev] Maximum length of a direct message?

[Craig Hockenberry]

The REST API docs state that the maximum length of the "text"
parameter to /direct_messages/new.format is 140 characters.

Testing that interface shows that 255 characters go through without
any problem. Also, this message from Alex indicates that it's an
allowable value:



Won't this present a problem for users who are getting their direct
messages through SMS? Do they get truncated on delivery?

-ch

[twitter-dev] Re: Twitter Search issue

[Matt Sanford]

Hi all,

 If you send something invalid we do attempt to fix-up invalid  
requests rather than just 400. This looks like a case where the bad  
request becomes a different sort of badness on the way out. Escaping  
the quotes seems like the only real fix.


— Matt

On Mar 3, 2009, at 09:13 AM, Chad Etzel wrote:



Ok, I can replicate your results with curl

$ curl -v "http://search.twitter.com/search.json?q=\"exeter%20city\"";

...returns the wrong results, as you say.

$ curl -v "http://search.twitter.com/search.json?q=%22exeter%20city 
%22"


...returns the correct results.

I think double quotes are not actually valid URL characters (tho some
browsers try to treat them as such), so you should really turn " into
%22 before the requests go out.


That said, I'm starting to agree with Paul that twitter is doing some
sort of encoding trick on their end when literal quotes are sent in
the request:

$ curl -v http://search.twitter.com/search.json?q=\"exeter%20city\";
* About to connect() to search.twitter.com port 80 (#0)
*   Trying 128.121.146.107... connected
* Connected to search.twitter.com (128.121.146.107) port 80 (#0)

GET /search.json?q="exeter%20city" HTTP/1.1
User-Agent: curl/7.16.4 (i486-pc-linux-gnu) libcurl/7.16.4 OpenSSL/ 
0.9.8e zlib/1.2.3.3 libidn/1.0

Host: search.twitter.com
Accept: */*


< HTTP/1.1 200 OK
< Date: Tue, 03 Mar 2009 17:09:34 GMT
< Server: hi
< Status: 200 OK
< Cache-Control: max-age=20, must-revalidate, max-age=300
< Content-Type: application/json; charset=utf-8
< X-Served-By: searchweb003.twitter.com
< Expires: Tue, 03 Mar 2009 17:14:34 GMT
< Content-Length: 195
< Vary: Accept-Encoding
< X-Varnish: 1733084231
< Age: 0
< Via: 1.1 varnish
< X-Cache-Svr: searchweb003.twitter.com
< X-Cache: MISS
< Connection: close
<
* Closing connection #0
{"results":[],"since_id":0,"max_id":1274236746,"refresh_url":"? 
since_id=1274236746&q=%22exeter%2520city%22","results_per_page": 
15,"completed_in":0.112164,"page":1,"query":"%22exeter%2520city%22"}


Now, one could argue that the request itself is invalid or malformed,
and so the result may be undefined, but I do agree that something is
happening on twitter's end.


Moral of the story: encode " as %22 in URLs.

-Chad

On Tue, Mar 3, 2009 at 11:33 AM, Paul Kinlan   
wrote:

Hi,

It works with the "+", but I knew that :)

With a space (in IE) it encodes it as %20 when it makes the request  
and I

can see it through fiddler (as below) and it comes back.

GET /search.json?q="exeter%20city" HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/x-ms-application, application/vnd.ms-xpsdocument,
application/xaml+xml, application/x-ms-xbap, application/x- 
shockwave-flash,
application/vnd.ms-excel, application/vnd.ms-powerpoint,  
application/msword,

*/*
Accept-Language: en-gb
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0;  
SLCC1; .NET
CLR 2.0.50727; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR  
3.0.30618;

InfoPath.2; OfficeLiveConnector.1.3; OfficeLivePatch.0.0)
Host: search.twitter.com
Connection: Keep-Alive
Cookie:
__utma 
=43838368.379476752167577530.1234449205.1234449205.1234449205.1;
__utmz=43838368.1234449205.1.1.utmcsr=blog.twe2.com| 
utmccn=(referral)|utmcmd=referral|utmcct=/;

__utmv=43838368.lang%3A%20en_GB

I fully accept it is probably our client software that is not  
encoding

correcly, but I also tried this from the command line curl
"http://search.twitter.com/search.json?q=\"exeter%20city\""; the  
response
comes back as %22exeter%2520city%22 in the json object.  From my  
point of

view I know the quotes are not correct, but it looks like twitter is
encoding them when it recieves them.  I belive our client API is  
sending

double quotes rather %22.

Kind Regards,
Paul

2009/3/3 Chad Etzel 


I also just tested searching "exeter city" in TweetGrid with IE,
FireFox, and Chrome. All came back with the same results.
fwiw,
-Chad

On Tue, Mar 3, 2009 at 11:14 AM, Matt Sanford   
wrote:

Hi Paul,
   I just tested form the command line and everything seems fine
with: curl
'http://search.twitter.com/search.json?q=%22exeter%20city%22'
   If you are typing %20 into the IE address bar it is likely try  
to
correct your %  (which is not a valid URL character) and making  
it %25

in
the request but displaying it correctly to you. Try replacing it  
with a

+ or
a space and see what you get.
Thanks;
 — Matt
- Show quoted text -
On Mar 3, 2009, at 08:06 AM, Paul Kinlan wrote:

Forgot to add, I am checking our client library now too.

Paul.

2009/3/3 Paul Kinlan 


Hi Matt,

I was typing the search term through IE (to test it after  
reports that

""
enclosed searches aren't working) as
http://search.twitter.com/search.json?q="exeter city" which it  
then

converts
to http://search.twitter.com/search.json?q="exeter%20city"; but the
result
came back as "%22exeter%2520city%22" (see json object below) in  
the

search
API json object.  It works in fir

[twitter-dev] Re: Twitter Search issue

[Chad Etzel]

Ok, I can replicate your results with curl

$ curl -v "http://search.twitter.com/search.json?q=\"exeter%20city\"";

...returns the wrong results, as you say.

$ curl -v "http://search.twitter.com/search.json?q=%22exeter%20city%22";

...returns the correct results.

I think double quotes are not actually valid URL characters (tho some
browsers try to treat them as such), so you should really turn " into
%22 before the requests go out.


That said, I'm starting to agree with Paul that twitter is doing some
sort of encoding trick on their end when literal quotes are sent in
the request:

$ curl -v http://search.twitter.com/search.json?q=\"exeter%20city\";
* About to connect() to search.twitter.com port 80 (#0)
*   Trying 128.121.146.107... connected
* Connected to search.twitter.com (128.121.146.107) port 80 (#0)
> GET /search.json?q="exeter%20city" HTTP/1.1
> User-Agent: curl/7.16.4 (i486-pc-linux-gnu) libcurl/7.16.4 OpenSSL/0.9.8e 
> zlib/1.2.3.3 libidn/1.0
> Host: search.twitter.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Tue, 03 Mar 2009 17:09:34 GMT
< Server: hi
< Status: 200 OK
< Cache-Control: max-age=20, must-revalidate, max-age=300
< Content-Type: application/json; charset=utf-8
< X-Served-By: searchweb003.twitter.com
< Expires: Tue, 03 Mar 2009 17:14:34 GMT
< Content-Length: 195
< Vary: Accept-Encoding
< X-Varnish: 1733084231
< Age: 0
< Via: 1.1 varnish
< X-Cache-Svr: searchweb003.twitter.com
< X-Cache: MISS
< Connection: close
<
* Closing connection #0
{"results":[],"since_id":0,"max_id":1274236746,"refresh_url":"?since_id=1274236746&q=%22exeter%2520city%22","results_per_page":15,"completed_in":0.112164,"page":1,"query":"%22exeter%2520city%22"}

Now, one could argue that the request itself is invalid or malformed,
and so the result may be undefined, but I do agree that something is
happening on twitter's end.


Moral of the story: encode " as %22 in URLs.

-Chad

On Tue, Mar 3, 2009 at 11:33 AM, Paul Kinlan  wrote:
> Hi,
>
> It works with the "+", but I knew that :)
>
> With a space (in IE) it encodes it as %20 when it makes the request and I
> can see it through fiddler (as below) and it comes back.
>
> GET /search.json?q="exeter%20city" HTTP/1.1
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
> application/x-ms-application, application/vnd.ms-xpsdocument,
> application/xaml+xml, application/x-ms-xbap, application/x-shockwave-flash,
> application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword,
> */*
> Accept-Language: en-gb
> UA-CPU: x86
> Accept-Encoding: gzip, deflate
> User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET
> CLR 2.0.50727; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30618;
> InfoPath.2; OfficeLiveConnector.1.3; OfficeLivePatch.0.0)
> Host: search.twitter.com
> Connection: Keep-Alive
> Cookie:
> __utma=43838368.379476752167577530.1234449205.1234449205.1234449205.1;
> __utmz=43838368.1234449205.1.1.utmcsr=blog.twe2.com|utmccn=(referral)|utmcmd=referral|utmcct=/;
> __utmv=43838368.lang%3A%20en_GB
>
> I fully accept it is probably our client software that is not encoding
> correcly, but I also tried this from the command line curl
> "http://search.twitter.com/search.json?q=\"exeter%20city\""; the response
> comes back as %22exeter%2520city%22 in the json object.  From my point of
> view I know the quotes are not correct, but it looks like twitter is
> encoding them when it recieves them.  I belive our client API is sending
> double quotes rather %22.
>
> Kind Regards,
> Paul
>
> 2009/3/3 Chad Etzel 
>>
>> I also just tested searching "exeter city" in TweetGrid with IE,
>> FireFox, and Chrome. All came back with the same results.
>> fwiw,
>> -Chad
>>
>> On Tue, Mar 3, 2009 at 11:14 AM, Matt Sanford  wrote:
>> > Hi Paul,
>> > I just tested form the command line and everything seems fine
>> > with: curl
>> > 'http://search.twitter.com/search.json?q=%22exeter%20city%22'
>> > If you are typing %20 into the IE address bar it is likely try to
>> > correct your %  (which is not a valid URL character) and making it %25
>> > in
>> > the request but displaying it correctly to you. Try replacing it with a
>> > + or
>> > a space and see what you get.
>> > Thanks;
>> >   — Matt
>> > - Show quoted text -
>> > On Mar 3, 2009, at 08:06 AM, Paul Kinlan wrote:
>> >
>> > Forgot to add, I am checking our client library now too.
>> >
>> > Paul.
>> >
>> > 2009/3/3 Paul Kinlan 
>> >>
>> >> Hi Matt,
>> >>
>> >> I was typing the search term through IE (to test it after reports that
>> >> ""
>> >> enclosed searches aren't working) as
>> >> http://search.twitter.com/search.json?q="exeter city" which it then
>> >> converts
>> >> to http://search.twitter.com/search.json?q="exeter%20city"; but the
>> >> result
>> >> came back as "%22exeter%2520city%22" (see json object below) in the
>> >> search
>> >> API json object.  It works in firefox so I am presuming firefox is
>> >> correctly
>> >> encoding the url.
>> >>
>> >>
>> >>
>> >> {"results":

[twitter-dev] Re: Twitter Search issue

[Paul Kinlan]

Hi,

It works with the "+", but I knew that :)

With a space (in IE) it encodes it as %20 when it makes the request and I
can see it through fiddler (as below) and it comes back.

GET /search.json?q="exeter%20city" HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/x-ms-application, application/vnd.ms-xpsdocument,
application/xaml+xml, application/x-ms-xbap, application/x-shockwave-flash,
application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword,
*/*
Accept-Language: en-gb
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET
CLR 2.0.50727; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30618;
InfoPath.2; OfficeLiveConnector.1.3; OfficeLivePatch.0.0)
Host: search.twitter.com
Connection: Keep-Alive
Cookie:
__utma=43838368.379476752167577530.1234449205.1234449205.1234449205.1;
__utmz=43838368.1234449205.1.1.utmcsr=blog.twe2.com|utmccn=(referral)|utmcmd=referral|utmcct=/;
__utmv=43838368.lang%3A%20en_GB

I fully accept it is probably our client software that is not encoding
correcly, but I also tried this from the command line curl "
http://search.twitter.com/search.json?q=\"exeter%20city\""; the response
comes back as %22exeter%2520city%22 in the json object.  From my point of
view I know the quotes are not correct, but it looks like twitter is
encoding them when it recieves them.  I belive our client API is sending
double quotes rather %22.

Kind Regards,
Paul

2009/3/3 Chad Etzel 

>
> I also just tested searching "exeter city" in TweetGrid with IE,
> FireFox, and Chrome. All came back with the same results.
> fwiw,
> -Chad
>
> On Tue, Mar 3, 2009 at 11:14 AM, Matt Sanford  wrote:
> > Hi Paul,
> > I just tested form the command line and everything seems fine
> with: curl
> > 'http://search.twitter.com/search.json?q=%22exeter%20city%22'
> > If you are typing %20 into the IE address bar it is likely try to
> > correct your %  (which is not a valid URL character) and making it %25 in
> > the request but displaying it correctly to you. Try replacing it with a +
> or
> > a space and see what you get.
> > Thanks;
> >   — Matt
> > - Show quoted text -
> > On Mar 3, 2009, at 08:06 AM, Paul Kinlan wrote:
> >
> > Forgot to add, I am checking our client library now too.
> >
> > Paul.
> >
> > 2009/3/3 Paul Kinlan 
> >>
> >> Hi Matt,
> >>
> >> I was typing the search term through IE (to test it after reports that
> ""
> >> enclosed searches aren't working) as
> >> http://search.twitter.com/search.json?q="exeter city" which it then
> converts
> >> to http://search.twitter.com/search.json?q="exeter%20city"; but the
> result
> >> came back as "%22exeter%2520city%22" (see json object below) in the
> search
> >> API json object.  It works in firefox so I am presuming firefox is
> correctly
> >> encoding the url.
> >>
> >>
> >>
> {"results":[],"since_id":0,"max_id":1273765306,"refresh_url":"?since_id=1273765306&q=%22exeter%2520city%22","results_per_page":15,"completed_in":1.313905,"page":1,"query":"%22exeter%2520city%22"}
> >>
> >> it is highly likely that if IE is having the issue, the client API would
> >> probably have it, however the query that is going out over the wire (I
> >> checked with fiddler as "exeter%20city" and the result comes back as
> above,
> >> so I don't think it is us for the entire problem).
> >>
> >> Kind Regards,
> >> Paul.
> >>
> >> 2009/3/3 Matt Sanford 
> >>>
> >>> Hi Paul,
> >>> It sounds like whatever is generating your API requests is double
> URL
> >>> encoding. So the space becomes %20, and then on the second url encoding
> the
> >>> % becomes a %25.
> >>> Thanks;
> >>>   — Matt Sanford / @mzsanford
> >>> On Mar 3, 2009, at 07:34 AM, Paul Kinlan wrote:
> >>>
> >>> Hi,
> >>>
> >>> I am noticing something that I think is odd at the moment.
> >>>
> >>> Some of our users are not getting searches that are enclosed in quotes
> >>> via the API, yet they work directly from the website.
> >>>
> >>> For example there is a difference between the following query on the
> API
> >>> and Website:
> >>>
> >>> http://search.twitter.com/search?q=%22exeter%20city%22 which has the
> same
> >>> results as http://search.twitter.com/search?q=%22exeter+city%22
> >>>
> >>> but returns a different result via the API using the following query
> >>>
> >>> http://search.twitter.com/search.json?q="exeter%20city";
> >>>
> >>> Looking at what is returned by the API the query looks like it has been
> >>> transformed in to "%22exeter%2520city%22". To me the %2520 looks odd
> when I
> >>> would expect %20
> >>>
> >>> Kind Regards,
> >>> Paul Kinlan
> >>>
> >>
> >
> >
> >
>

[twitter-dev] Re: Twitter Search issue

[Chad Etzel]

I also just tested searching "exeter city" in TweetGrid with IE,
FireFox, and Chrome. All came back with the same results.
fwiw,
-Chad

On Tue, Mar 3, 2009 at 11:14 AM, Matt Sanford  wrote:
> Hi Paul,
>     I just tested form the command line and everything seems fine with: curl
> 'http://search.twitter.com/search.json?q=%22exeter%20city%22'
>     If you are typing %20 into the IE address bar it is likely try to
> correct your %  (which is not a valid URL character) and making it %25 in
> the request but displaying it correctly to you. Try replacing it with a + or
> a space and see what you get.
> Thanks;
>   — Matt
> - Show quoted text -
> On Mar 3, 2009, at 08:06 AM, Paul Kinlan wrote:
>
> Forgot to add, I am checking our client library now too.
>
> Paul.
>
> 2009/3/3 Paul Kinlan 
>>
>> Hi Matt,
>>
>> I was typing the search term through IE (to test it after reports that ""
>> enclosed searches aren't working) as
>> http://search.twitter.com/search.json?q="exeter city" which it then converts
>> to http://search.twitter.com/search.json?q="exeter%20city"; but the result
>> came back as "%22exeter%2520city%22" (see json object below) in the search
>> API json object.  It works in firefox so I am presuming firefox is correctly
>> encoding the url.
>>
>>
>> {"results":[],"since_id":0,"max_id":1273765306,"refresh_url":"?since_id=1273765306&q=%22exeter%2520city%22","results_per_page":15,"completed_in":1.313905,"page":1,"query":"%22exeter%2520city%22"}
>>
>> it is highly likely that if IE is having the issue, the client API would
>> probably have it, however the query that is going out over the wire (I
>> checked with fiddler as "exeter%20city" and the result comes back as above,
>> so I don't think it is us for the entire problem).
>>
>> Kind Regards,
>> Paul.
>>
>> 2009/3/3 Matt Sanford 
>>>
>>> Hi Paul,
>>>     It sounds like whatever is generating your API requests is double URL
>>> encoding. So the space becomes %20, and then on the second url encoding the
>>> % becomes a %25.
>>> Thanks;
>>>   — Matt Sanford / @mzsanford
>>> On Mar 3, 2009, at 07:34 AM, Paul Kinlan wrote:
>>>
>>> Hi,
>>>
>>> I am noticing something that I think is odd at the moment.
>>>
>>> Some of our users are not getting searches that are enclosed in quotes
>>> via the API, yet they work directly from the website.
>>>
>>> For example there is a difference between the following query on the API
>>> and Website:
>>>
>>> http://search.twitter.com/search?q=%22exeter%20city%22 which has the same
>>> results as http://search.twitter.com/search?q=%22exeter+city%22
>>>
>>> but returns a different result via the API using the following query
>>>
>>> http://search.twitter.com/search.json?q="exeter%20city";
>>>
>>> Looking at what is returned by the API the query looks like it has been
>>> transformed in to "%22exeter%2520city%22". To me the %2520 looks odd when I
>>> would expect %20
>>>
>>> Kind Regards,
>>> Paul Kinlan
>>>
>>
>
>
>

[twitter-dev] Re: Twitter Search issue

[Matt Sanford]

Hi Paul,

I just tested form the command line and everything seems fine  
with: curl 'http://search.twitter.com/search.json?q=%22exeter%20city%22'
If you are typing %20 into the IE address bar it is likely try to  
correct your %  (which is not a valid URL character) and making it %25  
in the request but displaying it correctly to you. Try replacing it  
with a + or a space and see what you get.


Thanks;
  — Matt

On Mar 3, 2009, at 08:06 AM, Paul Kinlan wrote:


Forgot to add, I am checking our client library now too.

Paul.

2009/3/3 Paul Kinlan 
Hi Matt,

I was typing the search term through IE (to test it after reports  
that "" enclosed searches aren't working) as http://search.twitter.com/search.json?q= 
"exeter city" which it then converts to http://search.twitter.com/search.json?q= 
"exeter%20city" but the result came back as "%22exeter%2520city 
%22" (see json object below) in the search API json object.  It  
works in firefox so I am presuming firefox is correctly encoding the  
url.


{"results":[],"since_id":0,"max_id":1273765306,"refresh_url":"? 
since_id=1273765306&q=%22exeter%2520city%22","results_per_page": 
15,"completed_in":1.313905,"page":1,"query":"%22exeter%2520city%22"}


it is highly likely that if IE is having the issue, the client API  
would probably have it, however the query that is going out over the  
wire (I checked with fiddler as "exeter%20city" and the result comes  
back as above, so I don't think it is us for the entire problem).


Kind Regards,
Paul.

2009/3/3 Matt Sanford 

Hi Paul,

It sounds like whatever is generating your API requests is  
double URL encoding. So the space becomes %20, and then on the  
second url encoding the % becomes a %25.


Thanks;
  — Matt Sanford / @mzsanford

On Mar 3, 2009, at 07:34 AM, Paul Kinlan wrote:


Hi,

I am noticing something that I think is odd at the moment.

Some of our users are not getting searches that are enclosed in  
quotes via the API, yet they work directly from the website.


For example there is a difference between the following query on  
the API and Website:


http://search.twitter.com/search?q=%22exeter%20city%22 which has  
the same results as http://search.twitter.com/search?q=%22exeter+city%22


but returns a different result via the API using the following query

http://search.twitter.com/search.json?q="exeter%20city";

Looking at what is returned by the API the query looks like it has  
been transformed in to "%22exeter%2520city%22". To me the %2520  
looks odd when I would expect %20


Kind Regards,
Paul Kinlan

[twitter-dev] Re: Twitter Search issue

[Paul Kinlan]

Forgot to add, I am checking our client library now too.

Paul.

2009/3/3 Paul Kinlan 

> Hi Matt,
>
> I was typing the search term through IE (to test it after reports that ""
> enclosed searches aren't working) as
> http://search.twitter.com/search.json?q="exeter city" which it then
> converts to http://search.twitter.com/search.json?q="exeter%20city"; but
> the result came back as "%22exeter*%2520*city%22" (see json object below)
> in the search API json object.  It works in firefox so I am presuming
> firefox is correctly encoding the url.
>
>
> {"results":[],"since_id":0,"max_id":1273765306,"refresh_url":"?since_id=1273765306&q=%22exeter%2520city%22","results_per_page":15,"completed_in":1.313905,"page":1,"query":"%22exeter%2520city%22"}
>
> it is highly likely that if IE is having the issue, the client API would
> probably have it, however the query that is going out over the wire (I
> checked with fiddler as "exeter%20city" and the result comes back as above,
> so I don't think it is us for the entire problem).
>
> Kind Regards,
> Paul.
>
> 2009/3/3 Matt Sanford 
>
> Hi Paul,
>> It sounds like whatever is generating your API requests is double URL
>> encoding. So the space becomes %20, and then on the second url encoding the
>> % becomes a %25.
>>
>> Thanks;
>>   — Matt Sanford / @mzsanford
>>
>> On Mar 3, 2009, at 07:34 AM, Paul Kinlan wrote:
>>
>> Hi,
>>
>> I am noticing something that I think is odd at the moment.
>>
>> Some of our users are not getting searches that are enclosed in quotes via
>> the API, yet they work directly from the website.
>>
>> For example there is a difference between the following query on the API
>> and Website:
>>
>> http://search.twitter.com/search?q=%22exeter%20city%22 which has the same
>> results as http://search.twitter.com/search?q=%22exeter+city%22
>>
>> but returns a different result via the API using the following query
>>
>> http://search.twitter.com/search.json?q="exeter%20city";
>>
>> Looking at what is returned by the API the query looks like it has been
>> transformed in to "%22exeter*%2520*city%22". To me the %2520 looks odd
>> when I would expect %20
>>
>> Kind Regards,
>> Paul Kinlan
>>
>>
>>
>

[twitter-dev] Re: Twitter Search issue

[Paul Kinlan]

Hi Matt,

I was typing the search term through IE (to test it after reports that ""
enclosed searches aren't working) as
http://search.twitter.com/search.json?q="exeter city" which it then converts
to http://search.twitter.com/search.json?q="exeter%20city"; but the result
came back as "%22exeter*%2520*city%22" (see json object below) in the search
API json object.  It works in firefox so I am presuming firefox is correctly
encoding the url.

{"results":[],"since_id":0,"max_id":1273765306,"refresh_url":"?since_id=1273765306&q=%22exeter%2520city%22","results_per_page":15,"completed_in":1.313905,"page":1,"query":"%22exeter%2520city%22"}

it is highly likely that if IE is having the issue, the client API would
probably have it, however the query that is going out over the wire (I
checked with fiddler as "exeter%20city" and the result comes back as above,
so I don't think it is us for the entire problem).

Kind Regards,
Paul.

2009/3/3 Matt Sanford 

> Hi Paul,
> It sounds like whatever is generating your API requests is double URL
> encoding. So the space becomes %20, and then on the second url encoding the
> % becomes a %25.
>
> Thanks;
>   — Matt Sanford / @mzsanford
>
> On Mar 3, 2009, at 07:34 AM, Paul Kinlan wrote:
>
> Hi,
>
> I am noticing something that I think is odd at the moment.
>
> Some of our users are not getting searches that are enclosed in quotes via
> the API, yet they work directly from the website.
>
> For example there is a difference between the following query on the API
> and Website:
>
> http://search.twitter.com/search?q=%22exeter%20city%22 which has the same
> results as http://search.twitter.com/search?q=%22exeter+city%22
>
> but returns a different result via the API using the following query
>
> http://search.twitter.com/search.json?q="exeter%20city";
>
> Looking at what is returned by the API the query looks like it has been
> transformed in to "%22exeter*%2520*city%22". To me the %2520 looks odd
> when I would expect %20
>
> Kind Regards,
> Paul Kinlan
>
>
>

[twitter-dev] Re: Twitter Feed into a Chat Room

[Doug Williams]

Martin,
You can also approach those interested in freelance work listed here
http://apiwiki.twitter.com/Developers for your development needs. There are
a number of PHP programmers listed with experience developing Twitter
applications.

Thanks,
Doug Williams

On Tue, Mar 3, 2009 at 10:04 AM, Aaron Brazell wrote:

> The RSS is available to you. Presuming you have the programming chops to
> turn this into a chat room, go for it. ;)
> --
> Aaron Brazell
> web:: www.technosailor.com
> phone:: 410-608-6620
> skype:: technosailor
> twitter:: @technosailor
>
>
>
> On Tue, Mar 3, 2009 at 9:13 AM, BrummiesFans wrote:
>
>>
>> Hi
>>
>> I run a phpBB3 forum which has an AJAX Chat Room added to it. What I'd
>> appreciate is for a facility whereby an RSS feed from my Twitter
>> account could be used to add newsflashes into the live chat room.
>>
>> The scenario for its use would be when sporting fans go to "away"
>> sporting fixtures, they can update scores via their mobile phone to
>> Twitter, then, using the RSS feed from Twitter, the chatroom cabn
>> receive and show the updates for onward discussion by those "stay at
>> home" fans who are using the chat room.
>>
>> That's the principle.Now what is needed is someome willing to
>> volunteer, who has the required PHP programming skills who can modify
>> the AJAX Chat MOD to phpBB3 (all readily available at www.phpbb.com)
>>
>> I hope that someone would be able to take up the cause, and look
>> forward to seeing how this idea develops.
>>
>> Thanks
>>
>> Martin
>>
>
>


-- 
Doug Williams

do...@igudo.com
http://www.igudo.com

[twitter-dev] Re: Twitter Search issue

[Matt Sanford]

Hi Paul,

It sounds like whatever is generating your API requests is double  
URL encoding. So the space becomes %20, and then on the second url  
encoding the % becomes a %25.


Thanks;
  — Matt Sanford / @mzsanford

On Mar 3, 2009, at 07:34 AM, Paul Kinlan wrote:


Hi,

I am noticing something that I think is odd at the moment.

Some of our users are not getting searches that are enclosed in  
quotes via the API, yet they work directly from the website.


For example there is a difference between the following query on the  
API and Website:


http://search.twitter.com/search?q=%22exeter%20city%22 which has the  
same results as http://search.twitter.com/search?q=%22exeter+city%22


but returns a different result via the API using the following query

http://search.twitter.com/search.json?q="exeter%20city";

Looking at what is returned by the API the query looks like it has  
been transformed in to "%22exeter%2520city%22". To me the %2520  
looks odd when I would expect %20


Kind Regards,
Paul Kinlan

[twitter-dev] Twitter Search issue

[Paul Kinlan]

Hi,

I am noticing something that I think is odd at the moment.

Some of our users are not getting searches that are enclosed in quotes via
the API, yet they work directly from the website.

For example there is a difference between the following query on the API and
Website:

http://search.twitter.com/search?q=%22exeter%20city%22 which has the same
results as http://search.twitter.com/search?q=%22exeter+city%22

but returns a different result via the API using the following query

http://search.twitter.com/search.json?q="exeter%20city";

Looking at what is returned by the API the query looks like it has been
transformed in to "%22exeter*%2520*city%22". To me the %2520 looks odd when
I would expect %20

Kind Regards,
Paul Kinlan

[twitter-dev] Re: Twitter Feed into a Chat Room

[Aaron Brazell]

The RSS is available to you. Presuming you have the programming chops to
turn this into a chat room, go for it. ;)
-- 
Aaron Brazell
web:: www.technosailor.com
phone:: 410-608-6620
skype:: technosailor
twitter:: @technosailor


On Tue, Mar 3, 2009 at 9:13 AM, BrummiesFans  wrote:

>
> Hi
>
> I run a phpBB3 forum which has an AJAX Chat Room added to it. What I'd
> appreciate is for a facility whereby an RSS feed from my Twitter
> account could be used to add newsflashes into the live chat room.
>
> The scenario for its use would be when sporting fans go to "away"
> sporting fixtures, they can update scores via their mobile phone to
> Twitter, then, using the RSS feed from Twitter, the chatroom cabn
> receive and show the updates for onward discussion by those "stay at
> home" fans who are using the chat room.
>
> That's the principle.Now what is needed is someome willing to
> volunteer, who has the required PHP programming skills who can modify
> the AJAX Chat MOD to phpBB3 (all readily available at www.phpbb.com)
>
> I hope that someone would be able to take up the cause, and look
> forward to seeing how this idea develops.
>
> Thanks
>
> Martin
>

[twitter-dev] Re: 500 internal error

[Paul Haenel]

Hi Ed,

Thank you very much for getting back to.

Charles doesnt help me because im using Safari and there is no plug in
for it and i cant use Firefox for my project.

Any other suggestions??

Paul


On Feb 25, 2:47 pm, Ed Finkler  wrote:
> Try using adebuggingproxylikeCharlesso you can see the exact
> request being sent. That aids greatly in sorting out things like this.
>
> --
> Ed Finklerhttp://funkatron.com
> Twitter:@funkatron
> AIM: funka7ron
> ICQ: 3922133
> XMPP:funkat...@gmail.com
>
> On Feb 25, 5:48 am, Paul Haenel  wrote:
>
> > Hi,
>
> > Im getting a internal error which i execute this JavaScript function:
>
> > function setTwitterStatus(twitterStatus){
> >     var twitterStatus = 'status='+twitterStatus;
>
> >     alert(twitterStatus);
>
> >     var req = new XMLHttpRequest();
>
> >     req.open('POST', 'http://twitter.com/statuses/update.json',1);
> >     req.setRequestHeader('Authorization', 'Basic '+Base64.encode
> > (twitterUsername+':'+twitterPassword));
> >     req.onreadystatechange = function(){
> >         if(req.readyState ==4){
> >             alert(req.responseText);
> >         }
> >     }
> >     req.send(twitterStatus);
>
> > }
>
> > twitter status is is a plain text like "hello" or " is working hard."
>
> > here is s acopy of the response:
>
> > Status: 500 Internal Server Error
> > Content-Type: text/html
>
> > 500 Internal Server ErrorStatus:
> > 500 Internal Server Error
> > Content-Type: text/html
>
> > 500 Internal Server Error
>
> > Any help appreciated.
>
> > Thanks Paul

[twitter-dev] Re: 500 internal error

[Paul Haenel]

thxs got it sorted

did set the headers :

req.setRequestHeader('Content-Type', 'application/x-www-form-
urlencoded');

Thanks again

Paul


On Feb 25, 2:47 pm, Ed Finkler  wrote:
> Try using adebuggingproxylikeCharlesso you can see the exact
> request being sent. That aids greatly in sorting out things like this.
>
> --
> Ed Finklerhttp://funkatron.com
> Twitter:@funkatron
> AIM: funka7ron
> ICQ: 3922133
> XMPP:funkat...@gmail.com
>
> On Feb 25, 5:48 am, Paul Haenel  wrote:
>
> > Hi,
>
> > Im getting a internal error which i execute this JavaScript function:
>
> > function setTwitterStatus(twitterStatus){
> >     var twitterStatus = 'status='+twitterStatus;
>
> >     alert(twitterStatus);
>
> >     var req = new XMLHttpRequest();
>
> >     req.open('POST', 'http://twitter.com/statuses/update.json',1);
> >     req.setRequestHeader('Authorization', 'Basic '+Base64.encode
> > (twitterUsername+':'+twitterPassword));
> >     req.onreadystatechange = function(){
> >         if(req.readyState ==4){
> >             alert(req.responseText);
> >         }
> >     }
> >     req.send(twitterStatus);
>
> > }
>
> > twitter status is is a plain text like "hello" or " is working hard."
>
> > here is s acopy of the response:
>
> > Status: 500 Internal Server Error
> > Content-Type: text/html
>
> > 500 Internal Server ErrorStatus:
> > 500 Internal Server Error
> > Content-Type: text/html
>
> > 500 Internal Server Error
>
> > Any help appreciated.
>
> > Thanks Paul

[twitter-dev] Re: 400 Bad Request from Twitter RSS Feed

[Jan]

Same Problem Here;

feed itself works fine, when pulled through yahoo pipes I get 400 bad
request

[twitter-dev] Re: Other Languages?

[Fred Laranjo]

I like help translate the API to portuguese to. =]

2009/3/2 Alex Payne 

>
> Unless you're asking about API documentation, this isn't the place to
> ask about translations. If you'd like to help translate the API
> documentation, though, we'll happily accept submissions.
>
> On Mon, Mar 2, 2009 at 11:00, Johnnnyboy15nl  wrote:
> >
> > Hello Twitter,
> >
> > Will there be more Languages available soon? Like: Dutch, German,
> > French, ect?
> >
> > - John
> >
>
>
>
> --
> Alex Payne - API Lead, Twitter, Inc.
> http://twitter.com/al3x
>



-- 
Fred "Fosco" Laranjo
www.thief.com.br
www.fosco.multiply.com

[twitter-dev] Re: 500 internal error

[Paul Haenel]

sorry ignore the last one of course it works with safari too ;).

Paul


On Feb 25, 2:47 pm, Ed Finkler  wrote:
> Try using adebuggingproxylikeCharlesso you can see the exact
> request being sent. That aids greatly in sorting out things like this.
>
> --
> Ed Finklerhttp://funkatron.com
> Twitter:@funkatron
> AIM: funka7ron
> ICQ: 3922133
> XMPP:funkat...@gmail.com
>
> On Feb 25, 5:48 am, Paul Haenel  wrote:
>
> > Hi,
>
> > Im getting a internal error which i execute this JavaScript function:
>
> > function setTwitterStatus(twitterStatus){
> >     var twitterStatus = 'status='+twitterStatus;
>
> >     alert(twitterStatus);
>
> >     var req = new XMLHttpRequest();
>
> >     req.open('POST', 'http://twitter.com/statuses/update.json',1);
> >     req.setRequestHeader('Authorization', 'Basic '+Base64.encode
> > (twitterUsername+':'+twitterPassword));
> >     req.onreadystatechange = function(){
> >         if(req.readyState ==4){
> >             alert(req.responseText);
> >         }
> >     }
> >     req.send(twitterStatus);
>
> > }
>
> > twitter status is is a plain text like "hello" or " is working hard."
>
> > here is s acopy of the response:
>
> > Status: 500 Internal Server Error
> > Content-Type: text/html
>
> > 500 Internal Server ErrorStatus:
> > 500 Internal Server Error
> > Content-Type: text/html
>
> > 500 Internal Server Error
>
> > Any help appreciated.
>
> > Thanks Paul

[twitter-dev] Twitter Feed into a Chat Room

[BrummiesFans]

Hi

I run a phpBB3 forum which has an AJAX Chat Room added to it. What I'd
appreciate is for a facility whereby an RSS feed from my Twitter
account could be used to add newsflashes into the live chat room.

The scenario for its use would be when sporting fans go to "away"
sporting fixtures, they can update scores via their mobile phone to
Twitter, then, using the RSS feed from Twitter, the chatroom cabn
receive and show the updates for onward discussion by those "stay at
home" fans who are using the chat room.

That's the principle.Now what is needed is someome willing to
volunteer, who has the required PHP programming skills who can modify
the AJAX Chat MOD to phpBB3 (all readily available at www.phpbb.com)

I hope that someone would be able to take up the cause, and look
forward to seeing how this idea develops.

Thanks

Martin