[twitter-dev] massive #fail - auto profile popups
The automated profile popups are a profound source of #fail. Anyone using an Atom based machine is basically twiddling their thumbs for 30% of the time they're trying to use the web interface. Chrome users already had this feature with the bit.ly expander and it did much, much more. There really needs to be a No Silly Automated Profile Popup [ ] check box available in account config. If this had been the Twitter interface when I started I'd have 5 followers, 10 tweets, and I'd have been idle for 600+ days. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Mobile oAuth always says access update
It appears that mobile oAuth is ignoring the *access only* flag set on the connection permissions. I go out of my way to ensure I'm not writing to people's account, and now it says it anyway, screen shot here: http://img42.yfrog.com/img42/3104/ifrw.jpg Any chance of a fix? Thanks, Remy. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] massive #fail - auto profile popups
On Fri, Mar 19, 2010 at 2:26 AM, neal rauhauser nrauhau...@gmail.com wrote: The automated profile popups are a profound source of #fail. Anyone using an Atom based machine is basically twiddling their thumbs for 30% of the time they're trying to use the web interface. Chrome users already had this feature with the bit.ly expander and it did much, much more. There really needs to be a No Silly Automated Profile Popup [ ] check box available in account config. If this had been the Twitter interface when I started I'd have 5 followers, 10 tweets, and I'd have been idle for 600+ days. The popovers are very awkward. The popups that use a pointer are much more usable in my opinion. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: banned ip
Thanks Twitter Team for helping us resolve this issue. On Mar 17, 4:20 pm, @kemeny_x loop...@gmail.com wrote: We have fixed some issues, that could have caused the problem. Our app, and our personal accounts were running under the same whitelisted IP address, when split this, and keept the whitelisted IP ONLY for our app, and move to a non whitelisted IP our personal accounts. On Mar 17, 1:13 pm, John Kalucki j...@twitter.com wrote: We just banned a number of IPs that were not following the Streaming API policy. Open a support ticket with a...@twitter.com. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Mar 17, 2010 at 9:29 AM, @kemeny_x loop...@gmail.com wrote: Hi, we are able to access twitter.com or any other twitter service. we are currently running an app through the streaming API, and have been whitelisted by Twitter. But a few minutes ago we havent been able to access any of the twitter services. Could we have been bannend? if so, why? To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Twitter Project using the API (Paid)
I am looking for a twitter developer that is able to use the API to respond back to tweets containing a specific quote. Lets say for example an artist YXZ has just done a rendition of New York by Frank Sinatra. We want to @reply every user that mentions York Sinatra in their tweet with a customized reply such as I see you like Sinatra's original New York song.. but have you checked out ZYX's new version? It's a simple concept, and it has been done already. Please also be aware that twitter has an API limit that we don't want to disturb. We are in need of a developer to move this project forward. Please contact us back using this form: http://bit.ly/9CSUc0 Thanks! (= To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] massive #fail - auto profile popups
I actually quite like them, though I use tweetdeck most of the time. On 19 March 2010 06:26, neal rauhauser nrauhau...@gmail.com wrote: The automated profile popups are a profound source of #fail. Anyone using an Atom based machine is basically twiddling their thumbs for 30% of the time they're trying to use the web interface. Chrome users already had this feature with the bit.ly expander and it did much, much more. There really needs to be a No Silly Automated Profile Popup [ ] check box available in account config. If this had been the Twitter interface when I started I'd have 5 followers, 10 tweets, and I'd have been idle for 600+ days. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] since_id to old and some way to detect new id
When I perform some search through the API, like this example: http://search.twitter.com/search.atom?q=imente%20com%20-huubs%20verdienst%20-steven%20huubs%20-marc%20mateu%20gardey%20-marc%20mateu%20alsina%20-v%20imente%20com%20-juvenil%20-marc%20mateusince_id=9970356763 I get he response that since_id is to old. The tweet that is referred by id is correct, present and accessible. Is this one: http://twitter.com/pa1et/status/9970356763 In somewhere there's a specification of a id could not be used in since_id parameter? There's some pattern, some rule to detect when a id is too old to use in since_id parameter? To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Twitter Project using the API (Paid)
This sounds a lot like @reply spam: http://help.twitter.com/forums/10711/entries/64986 If you are replying to followers, maybe that's OK, and maybe it isn't. But, if you are @replying to everyone, you will be suspended. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Mar 18, 2010 at 8:26 PM, TheN2S thenext2sh...@gmail.com wrote: I am looking for a twitter developer that is able to use the API to respond back to tweets containing a specific quote. Lets say for example an artist YXZ has just done a rendition of New York by Frank Sinatra. We want to @reply every user that mentions York Sinatra in their tweet with a customized reply such as I see you like Sinatra's original New York song.. but have you checked out ZYX's new version? It's a simple concept, and it has been done already. Please also be aware that twitter has an API limit that we don't want to disturb. We are in need of a developer to move this project forward. Please contact us back using this form: http://bit.ly/9CSUc0 Thanks! (= To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] GetUserTimeline( since ) doesn't seem to work
Hi Guys, Am using for since the HTTP-formatted date as described in http://www.w3.org/TR/NOTE-datetime . Any ideas why this doesn't work? For example, api.GetUserTimeline(user=APlusK, since=2008) returns 20 entries when it should return hundreds. thank you, Rami To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Most popular tweets in the search API
Hi Developers!
The Search team is working on a beta project that returns the most popular
tweets for a query, rather than only the most recent tweets. This is a beta
project, but an important first step to surface the most popular tweets for
users searching Twitter.
You can expect many improvements as we tune and tweak our algorithms, but we
want to give everyone a heads up so we can go over the implications for
those consuming the search API.
--- New attribute in the payload ---
First of all there will be a new attribute in search result payloads. Since
some tweets are popular for a given query while others are simply the most
recent results that match the query, we are adding a metadata section to
specify the type of result that a given result represents.
So for a popular tweet the result_type in the metadata section will have
the value popular.
Example of a result with a popular tweet:
{
results:
[
{
profile_image_url:
http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon,15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:lt;a href=quot;http://www.atebits.com/quot;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: popular
}
}
/* etc ... */
}
Results that are not popular and represent simply recent query matches will
have the result_type in the metadata section with a value of recent.
Example of a recent result:
{
results:
[
{
profile_image_url:
http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:lt;a href=quot;http://www.atebits.com/quot;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: recent
}
},
/* etc ... */
}
--- Results with popular tweets aren't ordered chronologically ---
Until the popular tweet feature all search results have been sorted
chronologically, most recent results at the top. If a search query has any
popular results, those will be returned at the top, even if they are older
than the other results.
Example of a non-chronologically ordered set of results including popular
results:
{
results:
[
{
profile_image_url:
http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon, 15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:lt;a href=quot;http://www.atebits.com/quot;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: popular
}
},
{
profile_image_url:
http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:lt;a href=quot;http://www.atebits.com/quot;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: recent
}
}
/* etc ... */
}
--- Only getting popular results ---
If you *only* care about popular results for a given query term, you can
provide a result_type parameter with the value popular. Then only
popular results, if there are any, will be returned. By default, if
result_type isn't provided, all result types will be returned.
--- Never getting popular results ---
Conversely, if you *do not* want to receive popular results, provide a
result_type parameter with the value recent. Then only recent results
will be returned.
--- Dealing with popular tweets for refreshing search widgets ---
For those using client side search widgets, by default the first request
might include popular results. If you want to display these you can use the
result_type attribute to visually differentiate them. If you don't want to
display these you can always
[twitter-dev] Re: Most popular tweets in the search API
So this would change the default behavior of the search API, which is
currently to return recent results?
If so, I think that's a bad idea. Better to offer the option than to
change existing behavior when possible.
--
Ed Finkler
http://funkatron.com
Twitter:@funkatron
AIM: funka7ron
ICQ: 3922133
XMPP:funkat...@gmail.com
On Mar 19, 10:37 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Developers!
The Search team is working on a beta project that returns the most popular
tweets for a query, rather than only the most recent tweets. This is a beta
project, but an important first step to surface the most popular tweets for
users searching Twitter.
You can expect many improvements as we tune and tweak our algorithms, but we
want to give everyone a heads up so we can go over the implications for
those consuming the search API.
--- New attribute in the payload ---
First of all there will be a new attribute in search result payloads. Since
some tweets are popular for a given query while others are simply the most
recent results that match the query, we are adding a metadata section to
specify the type of result that a given result represents.
So for a popular tweet the result_type in the metadata section will have
the value popular.
Example of a result with a popular tweet:
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon,15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:lt;a href=quot;http://www.atebits.com/;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: popular
}
}
/* etc ... */
}
Results that are not popular and represent simply recent query matches will
have the result_type in the metadata section with a value of recent.
Example of a recent result:
{
results:
[
{
profile_image_url:http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:lt;a href=quot;http://www.atebits.com/;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: recent
}
},
/* etc ... */
}
--- Results with popular tweets aren't ordered chronologically ---
Until the popular tweet feature all search results have been sorted
chronologically, most recent results at the top. If a search query has any
popular results, those will be returned at the top, even if they are older
than the other results.
Example of a non-chronologically ordered set of results including popular
results:
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon, 15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:lt;a href=quot;http://www.atebits.com/;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: popular
}
},
{
profile_image_url:http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:lt;a href=quot;http://www.atebits.com/;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: recent
}
}
/* etc ... */
}
--- Only getting popular results ---
If you *only* care about popular results for a given query term, you can
provide a result_type parameter with the value popular. Then only
popular results, if there are any, will be returned. By default, if
result_type isn't provided, all result types will be returned.
--- Never
Re: [twitter-dev] Re: Most popular tweets in the search API
On 3/19/10 10:42 AM, funkatron wrote: So this would change the default behavior of the search API, which is currently to return recent results? If so, I think that's a bad idea. Better to offer the option than to change existing behavior when possible. +1. Don't break backwards compatibility unless there's a really good reason to do so. -- 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) To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Twitter API roadmap: When will geolocation be enabled for direct messages too?
Hi Twitter team, all Are there any plans to enable geolocation support for direct messages (i.e. not only for public status updates) anytime soon? There's definitely a demand (and potential for new apps and business) for this. For example, if you'd like to instantly order a location-based service through Twitter, you may want the supplier to know your exact location, but not necessarily the public. Further, people are likely more willing to allow and use geolocation for private, direct messages rather than public status updates. We're currently building a Twitter app prototype where geolocation support in DMs would be a win-win-win. Cheers Daniel To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] GetUserTimeline( since ) doesn't seem to work
By default the user_timeline only returns 20 statuses at a time. If you include the 'count' parameter you can increase that to 200 after which you will have to use 'page' to go further back. http://apiwiki.twitter.com/Twitter-REST-API-Method:-statuses-user_timeline Abraham On Fri, Mar 19, 2010 at 05:53, ramia rami...@gmail.com wrote: Hi Guys, Am using for since the HTTP-formatted date as described in http://www.w3.org/TR/NOTE-datetime . Any ideas why this doesn't work? For example, api.GetUserTimeline(user=APlusK, since=2008) returns 20 entries when it should return hundreds. thank you, Rami To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] massive #fail - auto profile popups
On Thu, Mar 18, 2010 at 23:26, neal rauhauser nrauhau...@gmail.com wrote: The automated profile popups are a profound source of #fail. Anyone using an Atom based machine is basically twiddling their thumbs for 30% of the time they're trying to use the web interface. Chrome users already had this feature with the bit.ly expander and it did much, much more. As far as I can tell the bit.ly expander only works on URLs so it does not interfere with Twitter's popups which only work on profiles. Abraham -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] massive #fail - auto profile popups
The bit.ly expander does a fine job on Twitter profiles - place the pointer over the name at the beginning of the tweet, and it would pull the info into a tidy box. Much, much, MUCH smoother than what Twitter has done. On Fri, Mar 19, 2010 at 10:41 AM, Abraham Williams 4bra...@gmail.comwrote: On Thu, Mar 18, 2010 at 23:26, neal rauhauser nrauhau...@gmail.comwrote: The automated profile popups are a profound source of #fail. Anyone using an Atom based machine is basically twiddling their thumbs for 30% of the time they're trying to use the web interface. Chrome users already had this feature with the bit.ly expander and it did much, much more. As far as I can tell the bit.ly expander only works on URLs so it does not interfere with Twitter's popups which only work on profiles. Abraham -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: 403 on statuses longer than 140 characters
The URLs might be shortened not the text of the status itself. Abraham On Thu, Mar 18, 2010 at 22:03, Andy Freeman ana...@earthlink.net wrote: What in the return JSON tells us that you've shortened? For example, are you setting/returning truncate? Are you returning the shortened tweet in status? On Mar 18, 12:30 pm, Mark McBride mmcbr...@twitter.com wrote: I should clarify. Returning a 403 is what we do right now. Later today (hopefully) we will correct the behavior to return a 200 in this case. So short story: we'll be doing what you want us to do. ---Mark http://twitter.com/mccv On Thu, Mar 18, 2010 at 11:57 AM, Dewald Pretorius dewaldpub...@gmail.comwrote: In the announcement, Mark said, ...in the case that a long status can be reduced to under 140 characters by shortening URLs. In this case we return a 403 but successfully create the status. Any chance that you can instead return a 200? Returning a 403 while you actually created the status will cause confusion.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Twitter Stream crossdomain.xml
Am I interpreting this correct as saying out of capacity concern we're currently blocking Flash developers? The crossdomain.xml issue has been extremely frustrating across all of Twitter's service endpoints and if I'm interpreting this post correctly this just adds to a series of poor choices Twitter has made in regard to Flash developers in my opinion. If this service needs to be limited for capacity reasons it should be limited in the same way regardless of what technology you are using to make requests of the API. -Orian Marx Flex Developer On Mar 17, 1:50 pm, John Kalucki j...@twitter.com wrote: It's in the code, but turned off out of an abundance of caution for capacity reasons. Given our current plans, it's going to be a little while longer before we can turn this on. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Mar 17, 2010 at 10:29 AM, TarGz julien.ter...@gmail.com wrote: hi, I have prevriuosly work on twittearth.com and now I work a project that use the stream API. The stream API work very well, it is very responsive and powerfull and help me build a realtime geolocated search tool... The bad sing is that my Flash app only work offline because of the lak of crossdomain.xml Did you have plan to put ahttp://sream.twitter.com/crossdomain.xml file live soon ? because I love to share my tools with the world. Thank per advance for your answer(s) Looking forward for your reply To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] massive #fail - auto profile popups
So it does. By logging out of Twitter you can turn off Twitter's popup to see bit.ly's. Twitter's popup is slow but it also include a lot more info. But since you are running chrome you could just write an extension to disable Twitter's popups. Abraham On Fri, Mar 19, 2010 at 08:49, neal rauhauser nrauhau...@gmail.com wrote: The bit.ly expander does a fine job on Twitter profiles - place the pointer over the name at the beginning of the tweet, and it would pull the info into a tidy box. Much, much, MUCH smoother than what Twitter has done. On Fri, Mar 19, 2010 at 10:41 AM, Abraham Williams 4bra...@gmail.comwrote: On Thu, Mar 18, 2010 at 23:26, neal rauhauser nrauhau...@gmail.comwrote: The automated profile popups are a profound source of #fail. Anyone using an Atom based machine is basically twiddling their thumbs for 30% of the time they're trying to use the web interface. Chrome users already had this feature with the bit.ly expander and it did much, much more. As far as I can tell the bit.ly expander only works on URLs so it does not interfere with Twitter's popups which only work on profiles. Abraham -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Why does changing this one char invalidate this message
Hi there, I've just been playing about and have come across a curious bug (I have changed one letter of the hashcode) - connecting and sending POST http://twitter.com/statuses/update.json HTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 36 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35tej DOESN'T WORK but POST http://twitter.com/statuses/update.json HTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 35 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35te DOES - why is this?? Many thanks in advance To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Message footer proposal
Since Google Groups started adding a broke footer message I am proposing adding a custom one that would be more helpful. Maybe something like: -- You received this message because you are subscribed to the Twitter Development Talk Google Group. To unsubscribe from this group, send an email to twitter-development-talk+unsubscr...@googlegroups.comtwitter-development-talk%2bunsubscr...@googlegroups.com To subscribe to the announcements group visit http://groups.google.com/group/twitter-api-announce For FAQs visit http://apiwiki.twitter.com/FAQ or for more support visit http://apiwiki.twitter.com/Support Thoughts? Do we need a footer? Should it be shorter? What information should it include? Abraham -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Why does changing this one char invalidate this message
Also worth noting: there was no error returned - it hung up after 3/4 seconds. If you connect to twitter.com port 80 using hyperterminal / winsock, you can copy and paste (replacing the authorisation, and enabling append line feeds onto line ends in hyperterminal options) my examples and see this for yourself. Any other ideas? I would really appreciate any comments on this issue. On Mar 19, 3:16 pm, Oli oliverst...@gmail.com wrote: Hi there, I've just been playing about and have come across a curious bug (I have changed one letter of the hashcode) - connecting and sending POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 36 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35tej DOESN'T WORK but POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 35 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35te DOES - why is this?? Many thanks in advance To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Most popular tweets in the search API
So this would change the default behavior of the search API, which is currently to return recent results? If so, I think that's a bad idea. Better to offer the option than to change existing behavior when possible. +1. Don't break backwards compatibility unless there's a really good reason to do so. Also +1. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- If you're too open-minded, your brains will fall out. -- To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Most popular tweets in the search API
On Fri, Mar 19, 2010 at 7:37 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers! The Search team is working on a beta project that returns the most popular tweets for a query, What is the definition of popular? Nick To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] since_id to old and some way to detect new id
Can you post the exact URL you're using? The one posted fails because the query is longer than 140 characters. Trimming it to a single term succeeds. This may be due to the fact that your ID is older than two weeks, and is therefore unknown to search. You could try using since=date instead and see if that works. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 2:49 AM, NetOak net...@gmail.com wrote: When I perform some search through the API, like this example: http://search.twitter.com/search.atom?q= imente%20com%20-huubs%20verdienst%20-steven%20huubs%20-marc%20mateu%20gardey%20-marc%20mateu%20alsina%20-v%20imente%20com%20-juvenil%20-marc%20mateusince_id=9970356763 I get he response that since_id is to old. The tweet that is referred by id is correct, present and accessible. Is this one: http://twitter.com/pa1et/status/9970356763 In somewhere there's a specification of a id could not be used in since_id parameter? There's some pattern, some rule to detect when a id is too old to use in since_id parameter? To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] GetUserTimeline( since ) doesn't seem to work
No timelines support since, only since_id. If you're specifying a since parameter it's being ignored. If you're specifying since_id with a value of 20 it's effectively meaningless, as tweet ID 20 is years old. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 8:36 AM, Abraham Williams 4bra...@gmail.com wrote: By default the user_timeline only returns 20 statuses at a time. If you include the 'count' parameter you can increase that to 200 after which you will have to use 'page' to go further back. http://apiwiki.twitter.com/Twitter-REST-API-Method:-statuses-user_timeline Abraham On Fri, Mar 19, 2010 at 05:53, ramia rami...@gmail.com wrote: Hi Guys, Am using for since the HTTP-formatted date as described in http://www.w3.org/TR/NOTE-datetime . Any ideas why this doesn't work? For example, api.GetUserTimeline(user=APlusK, since=2008) returns 20 entries when it should return hundreds. thank you, Rami To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Why does changing this one char invalidate this message
You'll almost certainly want to change the password on that account immediately, as the basic auth header is easily decrypted. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:20 AM, Oli oliverst...@gmail.com wrote: Also worth noting: there was no error returned - it hung up after 3/4 seconds. If you connect to twitter.com port 80 using hyperterminal / winsock, you can copy and paste (replacing the authorisation, and enabling append line feeds onto line ends in hyperterminal options) my examples and see this for yourself. Any other ideas? I would really appreciate any comments on this issue. On Mar 19, 3:16 pm, Oli oliverst...@gmail.com wrote: Hi there, I've just been playing about and have come across a curious bug (I have changed one letter of the hashcode) - connecting and sending POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 36 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35tej DOESN'T WORK but POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 35 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35te DOES - why is this?? Many thanks in advance To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Why does changing this one char invalidate this message
Missed the part about the one letter change. Clever! ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:54 AM, Mark McBride mmcbr...@twitter.com wrote: You'll almost certainly want to change the password on that account immediately, as the basic auth header is easily decrypted. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:20 AM, Oli oliverst...@gmail.com wrote: Also worth noting: there was no error returned - it hung up after 3/4 seconds. If you connect to twitter.com port 80 using hyperterminal / winsock, you can copy and paste (replacing the authorisation, and enabling append line feeds onto line ends in hyperterminal options) my examples and see this for yourself. Any other ideas? I would really appreciate any comments on this issue. On Mar 19, 3:16 pm, Oli oliverst...@gmail.com wrote: Hi there, I've just been playing about and have come across a curious bug (I have changed one letter of the hashcode) - connecting and sending POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 36 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35tej DOESN'T WORK but POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 35 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35te DOES - why is this?? Many thanks in advance To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Why does changing this one char invalidate this message
On to the real problem, are you using a library to make that POST request, or raw sockets? What is likely happening is you're telling the server to expect 36 bytes of info in the first call. You send 35. The server waits and waits then hangs up. In the second call you're telling the server to expect 35, you send 35, the server does it's deal, and everybody is happy. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:55 AM, Mark McBride mmcbr...@twitter.com wrote: Missed the part about the one letter change. Clever! ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:54 AM, Mark McBride mmcbr...@twitter.comwrote: You'll almost certainly want to change the password on that account immediately, as the basic auth header is easily decrypted. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:20 AM, Oli oliverst...@gmail.com wrote: Also worth noting: there was no error returned - it hung up after 3/4 seconds. If you connect to twitter.com port 80 using hyperterminal / winsock, you can copy and paste (replacing the authorisation, and enabling append line feeds onto line ends in hyperterminal options) my examples and see this for yourself. Any other ideas? I would really appreciate any comments on this issue. On Mar 19, 3:16 pm, Oli oliverst...@gmail.com wrote: Hi there, I've just been playing about and have come across a curious bug (I have changed one letter of the hashcode) - connecting and sending POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 36 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35tej DOESN'T WORK but POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 35 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35te DOES - why is this?? Many thanks in advance To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: 403 on statuses longer than 140 characters
Abraham is correct. We only truncate text in the case of SMS tweets. We won't chop text off of tweets when posted via the API, however we will shorten URLs if it will get the tweet to fit into 140 characters. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 8:52 AM, Abraham Williams 4bra...@gmail.com wrote: The URLs might be shortened not the text of the status itself. Abraham On Thu, Mar 18, 2010 at 22:03, Andy Freeman ana...@earthlink.net wrote: What in the return JSON tells us that you've shortened? For example, are you setting/returning truncate? Are you returning the shortened tweet in status? On Mar 18, 12:30 pm, Mark McBride mmcbr...@twitter.com wrote: I should clarify. Returning a 403 is what we do right now. Later today (hopefully) we will correct the behavior to return a 200 in this case. So short story: we'll be doing what you want us to do. ---Mark http://twitter.com/mccv On Thu, Mar 18, 2010 at 11:57 AM, Dewald Pretorius dewaldpub...@gmail.comwrote: In the announcement, Mark said, ...in the case that a long status can be reduced to under 140 characters by shortening URLs. In this case we return a 403 but successfully create the status. Any chance that you can instead return a 200? Returning a 403 while you actually created the status will cause confusion.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Twitter Project using the API (Paid)
John, Thanks for pointing that out! I will have a chat with my team and see how we can avoid this conflict. We do have another simple project that we want to get off its feet! Lets say we premiere an exclusive new song on our site. However to get to the song, users must login through twitter/facebook. While they login they are automatically set to follow @ouraccount and it automatically posts a status update on their account Currently checking out the brand new song for Sinatra! http://link.com;. Once that is done, the user is forwarded to the appropriate page that they originally intended to. If they don't sign in, they miss out on the release. This doesnt seem to be going against any terms of service... right? Once again, contact us if you are able to complete this project: http://bit.ly/9CSUc0 (all css/html is handled by us. We simply need the motor to power up the project. We take care of all the aesthetics.) On Mar 19, 9:27 am, John Kalucki j...@twitter.com wrote: This sounds a lot like @reply spam:http://help.twitter.com/forums/10711/entries/64986 If you are replying to followers, maybe that's OK, and maybe it isn't. But, if you are @replying to everyone, you will be suspended. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Mar 18, 2010 at 8:26 PM, TheN2S thenext2sh...@gmail.com wrote: I am looking for a twitter developer that is able to use the API to respond back to tweets containing a specific quote. Lets say for example an artist YXZ has just done a rendition of New York by Frank Sinatra. We want to @reply every user that mentions York Sinatra in their tweet with a customized reply such as I see you like Sinatra's original New York song.. but have you checked out ZYX's new version? It's a simple concept, and it has been done already. Please also be aware that twitter has an API limit that we don't want to disturb. We are in need of a developer to move this project forward. Please contact us back using this form:http://bit.ly/9CSUc0 Thanks! (= To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Most popular tweets in the search API
Your questions so far have been great and we're listening. I wanted to let everyone know that when we do roll this out, it will be such that developers will opt-in to receiving Top Tweets in their results for the first month or so of the feature rollout. After the trial transition period is complete, we'll enable this feature by default. You will have time to adjust. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, Mar 19, 2010 at 9:44 AM, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Mar 19, 2010 at 7:37 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers! The Search team is working on a beta project that returns the most popular tweets for a query, What is the definition of popular? Nick To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Most popular tweets in the search API
Bad idea.
1) reduces the credibility and thereby the value of the results in
twitter search
2) who determines which is popular- no matter how you try to calculate
this, someone will figure it out and spam the results.
3) people are used to searching twitter for breaking news, rather than
authoritative results. You'll have to change user expectations.
4) perhaps this can be an advanced setting, rather than a default
practice.
On Mar 19, 10:37 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Developers!
The Search team is working on a beta project that returns the most popular
tweets for a query, rather than only the most recent tweets. This is a beta
project, but an important first step to surface the most popular tweets for
users searching Twitter.
You can expect many improvements as we tune and tweak our algorithms, but we
want to give everyone a heads up so we can go over the implications for
those consuming the search API.
--- New attribute in the payload ---
First of all there will be a new attribute in search result payloads. Since
some tweets are popular for a given query while others are simply the most
recent results that match the query, we are adding a metadata section to
specify the type of result that a given result represents.
So for a popular tweet the result_type in the metadata section will have
the value popular.
Example of a result with a popular tweet:
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon,15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:a href=http://www.atebits.com/;
rel=nofollowTweetie/a,
metadata:
{
result_type: popular
}
}
/* etc ... */
}
Results that are not popular and represent simply recent query matches will
have the result_type in the metadata section with a value of recent.
Example of a recent result:
{
results:
[
{
profile_image_url:http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:a href=http://www.atebits.com/;
rel=nofollowTweetie/a,
metadata:
{
result_type: recent
}
},
/* etc ... */
}
--- Results with popular tweets aren't ordered chronologically ---
Until the popular tweet feature all search results have been sorted
chronologically, most recent results at the top. If a search query has any
popular results, those will be returned at the top, even if they are older
than the other results.
Example of a non-chronologically ordered set of results including popular
results:
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon, 15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:a href=http://www.atebits.com/;
rel=nofollowTweetie/a,
metadata:
{
result_type: popular
}
},
{
profile_image_url:http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:a href=http://www.atebits.com/;
rel=nofollowTweetie/a,
metadata:
{
result_type: recent
}
}
/* etc ... */
}
--- Only getting popular results ---
If you *only* care about popular results for a given query term, you can
provide a result_type parameter with the value popular. Then only
popular results, if there are any, will be returned. By default, if
result_type isn't provided, all result types will be returned.
--- Never
Re: [twitter-dev] Re: Most popular tweets in the search API
Even further clarifications:
Top Tweets are coming to make search results even more relevant. We'll be
tuning our ranking algorithms with gusto. Some people will naturally resist
these changes. Approach with a zen mind.
When we launch this new feature for the API, it will be opt-in for a
transitory period, but the search.twitter.com site will come with these
results already baked in. Before implementing in your own applications,
you'll be able to see the top results for your favorite queries your self.
The Search team is always working on ways of making results more
relevant. We recognize that not everyone wants search results with
algorithmic ranking of tweets, but we like what we've come up with and we
think you'll like it too.
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Fri, Mar 19, 2010 at 10:11 AM, davidzimm davidz...@yahoo.com wrote:
Bad idea.
1) reduces the credibility and thereby the value of the results in
twitter search
2) who determines which is popular- no matter how you try to calculate
this, someone will figure it out and spam the results.
3) people are used to searching twitter for breaking news, rather than
authoritative results. You'll have to change user expectations.
4) perhaps this can be an advanced setting, rather than a default
practice.
On Mar 19, 10:37 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Developers!
The Search team is working on a beta project that returns the most
popular
tweets for a query, rather than only the most recent tweets. This is a
beta
project, but an important first step to surface the most popular tweets
for
users searching Twitter.
You can expect many improvements as we tune and tweak our algorithms, but
we
want to give everyone a heads up so we can go over the implications for
those consuming the search API.
--- New attribute in the payload ---
First of all there will be a new attribute in search result payloads.
Since
some tweets are popular for a given query while others are simply the
most
recent results that match the query, we are adding a metadata section
to
specify the type of result that a given result represents.
So for a popular tweet the result_type in the metadata section will
have
the value popular.
Example of a result with a popular tweet:
{
results:
[
{
profile_image_url:
http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon,15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:a href=http://www.atebits.com/;
rel=nofollowTweetie/a,
metadata:
{
result_type: popular
}
}
/* etc ... */
}
Results that are not popular and represent simply recent query matches
will
have the result_type in the metadata section with a value of
recent.
Example of a recent result:
{
results:
[
{
profile_image_url:
http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:a href=http://www.atebits.com/;
rel=nofollowTweetie/a,
metadata:
{
result_type: recent
}
},
/* etc ... */
}
--- Results with popular tweets aren't ordered chronologically ---
Until the popular tweet feature all search results have been sorted
chronologically, most recent results at the top. If a search query has
any
popular results, those will be returned at the top, even if they are
older
than the other results.
Example of a non-chronologically ordered set of results including popular
results:
{
results:
[
{
profile_image_url:
http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon, 15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:a href=http://www.atebits.com/;
rel=nofollowTweetie/a,
metadata:
{
[twitter-dev] Re: Most popular tweets in the search API
I'm assuming popular is based on retweet count? I'd suggest that if result_type is not given in the request that the search performs as it has been. If you want just popular, you'd use popular as you've suggested or recent for non popular. If you wanted a mix, ordered as you are suggesting, then add the value all for the result_type. That would be much more of an extension/feature rather than a refactor. On Mar 19, 10:09 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Your questions so far have been great and we're listening. I wanted to let everyone know that when we do roll this out, it will be such that developers will opt-in to receiving Top Tweets in their results for the first month or so of the feature rollout. After the trial transition period is complete, we'll enable this feature by default. You will have time to adjust. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, Mar 19, 2010 at 9:44 AM, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Mar 19, 2010 at 7:37 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers! The Search team is working on a beta project that returns the most popular tweets for a query, What is the definition of popular? Nick To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Twitter Project using the API (Paid)
John, Another idea we came up with would be sort of like an Artificial Intelligence Twitter account. Anyone can ask it a question. Keywords are extracted from that question, and the Twitter account replies back with a pre-defined @reply message. Would this idea conflict with the twitter terms of use? On Mar 19, 1:01 pm, TheN2S thenext2sh...@gmail.com wrote: John, Thanks for pointing that out! I will have a chat with my team and see how we can avoid this conflict. We do have another simple project that we want to get off its feet! Lets say we premiere an exclusive new song on our site. However to get to the song, users must login through twitter/facebook. While they login they are automatically set to follow @ouraccount and it automatically posts a status update on their account Currently checking out the brand new song for Sinatra!http://link.com;. Once that is done, the user is forwarded to the appropriate page that they originally intended to. If they don't sign in, they miss out on the release. This doesnt seem to be going against any terms of service... right? Once again, contact us if you are able to complete this project:http://bit.ly/9CSUc0 (all css/html is handled by us. We simply need the motor to power up the project. We take care of all the aesthetics.) On Mar 19, 9:27 am, John Kalucki j...@twitter.com wrote: This sounds a lot like @reply spam:http://help.twitter.com/forums/10711/entries/64986 If you are replying to followers, maybe that's OK, and maybe it isn't. But, if you are @replying to everyone, you will be suspended. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Mar 18, 2010 at 8:26 PM, TheN2S thenext2sh...@gmail.com wrote: I am looking for a twitter developer that is able to use the API to respond back to tweets containing a specific quote. Lets say for example an artist YXZ has just done a rendition of New York by Frank Sinatra. We want to @reply every user that mentions York Sinatra in their tweet with a customized reply such as I see you like Sinatra's original New York song.. but have you checked out ZYX's new version? It's a simple concept, and it has been done already. Please also be aware that twitter has an API limit that we don't want to disturb. We are in need of a developer to move this project forward. Please contact us back using this form:http://bit.ly/9CSUc0 Thanks! (= To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Why does changing this one char invalidate this message
Hi Mark, thanks for your response but I think you may be mistaken. In the first call, I do send 36 bytes I state prior to sending - status=ALAhM%3A+Test_Unit+t1%3A35tej In the second call, I do send the 35 bytes I state prior to sending - status=ALAhM%3A+Test_Unit+t1%3A35te Additionally, I am 100% sure there are no spaces at the end / other chars that are hidden. I am dealing with the raw socket and to rule out any software mishap I have been testing manually using hyperterminal (winsock) to diagnose the problem. I'm at a dead end on this until somebody can figure out what I am doing wrong / if there is genuinely a problem elsewhere. Thanks again On Mar 19, 4:58 pm, Mark McBride mmcbr...@twitter.com wrote: On to the real problem, are you using a library to make that POST request, or raw sockets? What is likely happening is you're telling the server to expect 36 bytes of info in the first call. You send 35. The server waits and waits then hangs up. In the second call you're telling the server to expect 35, you send 35, the server does it's deal, and everybody is happy. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:55 AM, Mark McBride mmcbr...@twitter.com wrote: Missed the part about the one letter change. Clever! ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:54 AM, Mark McBride mmcbr...@twitter.comwrote: You'll almost certainly want to change the password on that account immediately, as the basic auth header is easily decrypted. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:20 AM, Oli oliverst...@gmail.com wrote: Also worth noting: there was no error returned - it hung up after 3/4 seconds. If you connect to twitter.com port 80 using hyperterminal / winsock, you can copy and paste (replacing the authorisation, and enabling append line feeds onto line ends in hyperterminal options) my examples and see this for yourself. Any other ideas? I would really appreciate any comments on this issue. On Mar 19, 3:16 pm, Oli oliverst...@gmail.com wrote: Hi there, I've just been playing about and have come across a curious bug (I have changed one letter of the hashcode) - connecting and sending POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 36 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35tej DOESN'T WORK but POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 35 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35te DOES - why is this?? Many thanks in advance To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Search API - Does Tweet already exist?
I have some search API code that works, but seems way too slow. I am hoping I can get some pointers and best-practices advice. I am using an RSS news headline feed at my organization (a university) and only posting Tweets for new headlines. I iterate through the headlines and search for Tweets from our own account. I am searching for the title of the article, the bit.ly URL, and the combination of the title + bit.ly URL. If none of these three searches returns a result, I go ahead and post a Tweet. I haven't added date filters, yet. I plan to do that next to help speed things up. Is there any way to post a primary key ID or some other unique ID as some sort of metadata for a Tweet, and simply search for the primary key / unique ID? To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Most popular tweets in the search API
I wanted to let everyone know that when we do roll this out, it will be such that developers will opt-in to receiving Top Tweets in their results for the first month or so of the feature rollout. After the trial transition period is complete, we'll enable this feature by default. You will have time to adjust. So how do you opt-out? Really, this feature doesn't square with TTYtter's search API support at all. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Software sucks because users demand it to. -- Nathan Mhyrvold, Microsoft --- To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Most popular tweets in the search API
I'm also curious to understand how 'popular' tweets will be determined. Once a tweet is considered to be popular for search purposes, might it be cached for an extended period of time so that it will return for queries beyond the currently limited period? -- Richard Nevins Twitter: @hornOKplease To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Why does changing this one char invalidate this message
Hi Mark, thanks for your reply but I think you may be mistaken. - In the first example, I tell the server to expect 36 bytes and I then send it: status=ALAhM%3A+Test_Unit+t1%3A35tej - In the second example, I tell the server to expect 35 bytes and I then send it: status=ALAhM%3A+Test_Unit+t1%3A35te Notice the 'j' on the first example - not there in the second one. I'm dealing with the raw sockets, but I have been diagnosing manually using hyperterminal / winsock to be sure that it's not my software clouding the issue. You can test this example quite easily by just copying and pasting into hyperterminal (be sure to enable the option File-Properties-Settings-ASCII Setup-Send line ends with line feeds) and changing the Auth value (you can use http://www.functions-online.com/en/base64_encode.html to generate). Secondly, I am aware that duplicate posts will not be posted and I am sure that this is not the issue. Lastly, I am 100% sure that there are not any hidden bytes / spaces being sent on the end. Any other suggestions? Thanks again On Mar 19, 3:16 pm, Oli oliverst...@gmail.com wrote: Hi there, I've just been playing about and have come across a curious bug (I have changed one letter of the hashcode) - connecting and sending POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 36 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35tej DOESN'T WORK but POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 35 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35te DOES - why is this?? Many thanks in advance To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Why does changing this one char invalidate this message
Now that I'm clear... 1) It works for me using telnet. This may or may not be subtly different from hyperterminal. 2) Note that if you do this repeatedly with the same status text you'll get rejections due to duplicate tweets. On twitter.com this returns a 200 with no response body. You shouldn't be using this endpoint anyway, please use api.twitter.com instead. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 10:33 AM, Oli oliverst...@gmail.com wrote: Hi Mark, thanks for your response but I think you may be mistaken. In the first call, I do send 36 bytes I state prior to sending - status=ALAhM%3A+Test_Unit+t1%3A35tej In the second call, I do send the 35 bytes I state prior to sending - status=ALAhM%3A+Test_Unit+t1%3A35te Additionally, I am 100% sure there are no spaces at the end / other chars that are hidden. I am dealing with the raw socket and to rule out any software mishap I have been testing manually using hyperterminal (winsock) to diagnose the problem. I'm at a dead end on this until somebody can figure out what I am doing wrong / if there is genuinely a problem elsewhere. Thanks again On Mar 19, 4:58 pm, Mark McBride mmcbr...@twitter.com wrote: On to the real problem, are you using a library to make that POST request, or raw sockets? What is likely happening is you're telling the server to expect 36 bytes of info in the first call. You send 35. The server waits and waits then hangs up. In the second call you're telling the server to expect 35, you send 35, the server does it's deal, and everybody is happy. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:55 AM, Mark McBride mmcbr...@twitter.com wrote: Missed the part about the one letter change. Clever! ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:54 AM, Mark McBride mmcbr...@twitter.com wrote: You'll almost certainly want to change the password on that account immediately, as the basic auth header is easily decrypted. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 9:20 AM, Oli oliverst...@gmail.com wrote: Also worth noting: there was no error returned - it hung up after 3/4 seconds. If you connect to twitter.com port 80 using hyperterminal / winsock, you can copy and paste (replacing the authorisation, and enabling append line feeds onto line ends in hyperterminal options) my examples and see this for yourself. Any other ideas? I would really appreciate any comments on this issue. On Mar 19, 3:16 pm, Oli oliverst...@gmail.com wrote: Hi there, I've just been playing about and have come across a curious bug (I have changed one letter of the hashcode) - connecting and sending POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 36 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35tej DOESN'T WORK but POSThttp://twitter.com/statuses/update.jsonHTTP/1.1 Host: twitter.com Authorization: Basic bWz0cm9uMjpwb2tlcmNoYW1wMQ== Content-type: application/x-www-form-urlencoded Content-length: 35 Connection: Close status=ALAhM%3A+Test_Unit+t1%3A35te DOES - why is this?? Many thanks in advance To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Twitter Project using the API (Paid)
One of our teammates came up with the idea of having a cooperative twitter interview. For our site we interview artists/producers. However we want our users to feel a part of the site as it grows by allowing them to interact as much as possible. With this in mind, another project would be to create a twitter/facebook login page that would (again) force the user to sign in. After signing in the user automatically follows us on twitter, and updates their status to a pre- defined text that we choose. Once they login, they will be able to view a form that will be used to leave a quick little question for the upcoming interview. Once they submit their question their twitter/ facebook status is updated to let their friends know: @someone just left an interview question for @singer at: http://link.com Get your question answered! The public questions will be stored in a thread format on that page. On Mar 19, 1:24 pm, TheN2S thenext2sh...@gmail.com wrote: John, Another idea we came up with would be sort of like an Artificial Intelligence Twitter account. Anyone can ask it a question. Keywords are extracted from that question, and the Twitter account replies back with a pre-defined @reply message. Would this idea conflict with the twitter terms of use? On Mar 19, 1:01 pm, TheN2S thenext2sh...@gmail.com wrote: John, Thanks for pointing that out! I will have a chat with my team and see how we can avoid this conflict. We do have another simple project that we want to get off its feet! Lets say we premiere an exclusive new song on our site. However to get to the song, users must login through twitter/facebook. While they login they are automatically set to follow @ouraccount and it automatically posts a status update on their account Currently checking out the brand new song for Sinatra!http://link.com;. Once that is done, the user is forwarded to the appropriate page that they originally intended to. If they don't sign in, they miss out on the release. This doesnt seem to be going against any terms of service... right? Once again, contact us if you are able to complete this project:http://bit.ly/9CSUc0 (all css/html is handled by us. We simply need the motor to power up the project. We take care of all the aesthetics.) On Mar 19, 9:27 am, John Kalucki j...@twitter.com wrote: This sounds a lot like @reply spam:http://help.twitter.com/forums/10711/entries/64986 If you are replying to followers, maybe that's OK, and maybe it isn't. But, if you are @replying to everyone, you will be suspended. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Mar 18, 2010 at 8:26 PM, TheN2S thenext2sh...@gmail.com wrote: I am looking for a twitter developer that is able to use the API to respond back to tweets containing a specific quote. Lets say for example an artist YXZ has just done a rendition of New York by Frank Sinatra. We want to @reply every user that mentions York Sinatra in their tweet with a customized reply such as I see you like Sinatra's original New York song.. but have you checked out ZYX's new version? It's a simple concept, and it has been done already. Please also be aware that twitter has an API limit that we don't want to disturb. We are in need of a developer to move this project forward. Please contact us back using this form:http://bit.ly/9CSUc0 Thanks! (= To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Twitter bug OR deliberate OAuth exception in the new versioning api ?
I didn't get any response for last week's http://twitter.com/CascadeRam/status/10487105790 , so I'm hoping to get an official response here. In October, last year, http://groups.google.com/group/twitter-api-announce/browse_thread/thread/2b70bd6ea4aec175 recommended that all developers move to the new versioned apis and that Twitter would set a hard date after whch http://twitter.com will not be serviced. However, 5 months after that announcement, the new versioned api doesn't seem to be supported for Twitter OAuth calls (though the versioned api works with other methods like http://api.twitter.com/1/friendships/create.xml) http://api.twitter.com/1/oauth/request_token returns a 404 (but http://twitter.com/oauth/request_token and http://api.twitter.com/oauth/access_token work correctly) So for now, I'm using the following (non-versioned) URLs http://api.twitter.com/oauth/authorize?oauth_token=xx http://api.twitter.com/oauth/authorize http://api.twitter.com/oauth/access_token and I'm using versioned URLs for other stuff like http://api.twitter.com/1/statuses/update.xml Are these the best URLs to be using now ? Does anyone know whether the 404 error is due to a bug, due to an incomplete implementation of the new api or whether OAuth apis are exempted from versioning ? To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Introduce yourself!
My name is Quy Le (@quytennis) and I used to be a software engineer but now I'm product manager at a high-tech company. I've been using the Twitter API for the past 3 months on a Twitter project that hopefully will go live in a few weeks. I've been using PHP/mySQL/ memcached to build my site but it has been a slow process since I have a day job and I'm relearning some of the new technology since I haven't touched a piece of code in over 8-9 years. (Designing for IE6 sucks). The feature I would love the most is a conversation API so it's easy to show conversations based on a tweet. Quy On Feb 19, 1:20 pm, Abraham Williams 4bra...@gmail.com wrote: We have not had an introductions thread in a long time (or ever that I could find) so I'm starting one. Don't forget to add an answer to the tools thread [1](Gmail link [2]) as well. I'm Abraham Williams, I've been working with the Twitter API and this group since early 2008. I do mostly freelance Drupal and Twitter API integration and personal projects. I love seeing the creative projects developers build or integrate with the API and look forward to meeting many of you at Chirp. TwitterOAuth [3] the first PHP library to support OAuth is built and maintained by me, and will hopefully see a new release soon. I also built a fun Chrome extension [4] that integrates common friends and followers into Twitter profiles. The feature I would most like added to the API is a conversation method to get replies to a specific status. So. Who are you, what do you do, what have you built, and what feature do you most want to see added? @Abraham [1]http://groups.google.com/group/twitter-development-talk/browse_thread... [2]https://mail.google.com/mail/#inbox/12680cd0fa59011e [3]https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogo... [4]http://code.google.com/p/twitter-api/issues/detail?id=142 -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Twitter Stream crossdomain.xml
John, thanks for the response. This makes sense. While I do trust that the existing crossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non-search Twitter API. Twitter has addressed security concerns very well through OAuth. There is really no reason Flash apps should be restricted if they are making OAuth calls to the new api.twitter.com endpoints. For other discussions of this please see http://groups.google.com/group/twitter-development-talk/browse_frm/thread/e35a708400b529b3 and http://groups.google.com/group/twitter-development-talk/browse_frm/thread/d3230be66c27c88e?hl=entvc=1 -Orian On Mar 19, 2:17 pm, John Kalucki j...@twitter.com wrote: Currently the Streaming API is primarily intended for service to service integrations, and we've provisioned stream.twitter.com as such. We've also opened it up for all sorts of open-ended experimentation as well. However, we've asked large-scale deployments, such desktop apps and widgets, to hold off on releasing products against the Streaming API until we can provide a few more features (oAuth, etc.), provide sufficient capacity, and fully isolate desktop traffic from integration traffic. A single Hosebird process can pump out a lot of data. A cluster of them is a bit like a bull in a china shop. We want to avoid a success catastrophe where a set of popular clients releases all at once and inadvertently overwhelms the service and potentially knocks integrations and/or non-trivial slice of www traffic offline. This would be bad for everyone, including open experimental access. So, among a dozen other disabled features, crossdomain.xml is also off on stream.twitter.com. We're working on this right now. Please have patience. The crossdomain.xml policy on other endpoints is the doing of others, and I don't remember all the details. Please trust that the policies chosen were made with user privacy and user security as the primary concerns. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Mar 19, 2010 at 8:55 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Am I interpreting this correct as saying out of capacity concern we're currently blocking Flash developers? The crossdomain.xml issue has been extremely frustrating across all of Twitter's service endpoints and if I'm interpreting this post correctly this just adds to a series of poor choices Twitter has made in regard to Flash developers in my opinion. If this service needs to be limited for capacity reasons it should be limited in the same way regardless of what technology you are using to make requests of the API. -Orian Marx Flex Developer On Mar 17, 1:50 pm, John Kalucki j...@twitter.com wrote: It's in the code, but turned off out of an abundance of caution for capacity reasons. Given our current plans, it's going to be a little while longer before we can turn this on. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Mar 17, 2010 at 10:29 AM, TarGz julien.ter...@gmail.com wrote: hi, I have prevriuosly work on twittearth.com and now I work a project that use the stream API. The stream API work very well, it is very responsive and powerfull and help me build a realtime geolocated search tool... The bad sing is that my Flash app only work offline because of the lak of crossdomain.xml Did you have plan to put ahttp://sream.twitter.com/crossdomain.xml file live soon ? because I love to share my tools with the world. Thank per advance for your answer(s) Looking forward for your reply To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] List count
Is there an easy way to get the total number of lists for a user? I don't want to have to page through GET lists and count. Quy To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] count rewteets
hello
i want to count retweets for special tweets. but it doesn´t work. with
error_reporting( E_ALL | E_STRICT ); i get no error message
error_reporting( E_ALL | E_STRICT );
ini_set('display_errors', TRUE);
$user = 'user';
$pass = 'xxx';
$strTwitURL = 'http://twitter.com/statuses/retweets/10660323641.json';
$curl = curl_init();
curl_setopt($curl, CURLOPT_URL, $strTwitURL);
curl_setopt($curl, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($curl, CURLOPT_USERPWD, $user:$pass);
$query = json_decode(curl_exec($curl));
curl_close($curl);
foreach($query as $output)
{
echo $count = count( $output-id);
echo 'br';
}
To unsubscribe from this group, send email to
twitter-development-talk+unsubscribegooglegroups.com or reply to this email
with the words REMOVE ME as the subject.
Re: [twitter-dev] Chrome plugin to shut down unwanted Twitter popups?
The problem is clientside script. The answer with a Chrome plugin would be clientside script. Catch-22? ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Fri, Mar 19, 2010 at 2:12 PM, neal rauhauser nrauhau...@gmail.com wrote: Someone suggested that a Chrome plugin to shut down this profile popup stuff was possible - has anyone actually done such a thing? It is desperately needed - Twitter is all but unusable for those of us on Atom based machines with all of this undesired popping lag. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Most popular tweets in the search API
Your definition of time to adjust may not be ours. Twitter has, to be honest, a fairly crappy reputation for changing API behavior. While some of that was surely driven by performance concerns, I don't see how this could be. This doesn't help the rep. Please, do not enable this by default, *ever*. Don't change behavior unless it is necessary. Add a new API method, or make recent results the default and keep it that way. If you're advocating for developers, advocate for making us do less work to maintain current functionality, please. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Mar 19, 1:09 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Your questions so far have been great and we're listening. I wanted to let everyone know that when we do roll this out, it will be such that developers will opt-in to receiving Top Tweets in their results for the first month or so of the feature rollout. After the trial transition period is complete, we'll enable this feature by default. You will have time to adjust. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, Mar 19, 2010 at 9:44 AM, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Mar 19, 2010 at 7:37 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers! The Search team is working on a beta project that returns the most popular tweets for a query, What is the definition of popular? Nick To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Chrome plugin to shut down unwanted Twitter popups?
The hovercards are trigger with class=tweet-url screen-name. Have the Chrome extension remove those classes and the hovercards stop. Abraham On Fri, Mar 19, 2010 at 12:15, Andrew Badera and...@badera.us wrote: The problem is clientside script. The answer with a Chrome plugin would be clientside script. Catch-22? ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Fri, Mar 19, 2010 at 2:12 PM, neal rauhauser nrauhau...@gmail.com wrote: Someone suggested that a Chrome plugin to shut down this profile popup stuff was possible - has anyone actually done such a thing? It is desperately needed - Twitter is all but unusable for those of us on Atom based machines with all of this undesired popping lag. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Most popular tweets in the search API
Your definition of time to adjust may not be ours. Twitter has, to be honest, a fairly crappy reputation for changing API behavior. While some of that was surely driven by performance concerns, I don't see how this could be. This doesn't help the rep. Please, do not enable this by default, *ever*. Don't change behavior unless it is necessary. Add a new API method, or make recent results the default and keep it that way. If you're advocating for developers, advocate for making us do less work to maintain current functionality, please. This is spot on. It's not that I think the idea itself is bad -- I'm all for more relevant search results *when relevance is what's requested*. Right now, every app that queries the Search API expects time-oriented results because that's what we got before. Making this the new default is needless dev chaos, *and* I haven't heard if there is even a way to opt back to the old behaviour if this becomes the ill-advised default anyway. I'd love to support this feature, in the appropriate context, when it makes sense to do so. I don't want to have to code around it as the new, unsolicited default when it doesn't. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- FORTUNE: Good day for romance, but try a single person this time. -- To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Most popular tweets in the search API
Taylor,
In terms of this change, you need to separate Twitter Search from the
Twitter Search API in your minds.
Do with Twitter Search (the web interface) what you like. Make popular
the default if you want.
But, don't decide on behalf of the developers (the consumers of the
Twitter Search API) that popular is the default that we want. In most
cases it probably isn't. In my case it definitely isn't, otherwise I
would have asked for something like that a long time ago.
In other words, don't force something down our throats just because
you think it's a cool idea.
Leave the default as is. Make popular an option that we can use if
we want to. That's good developer service, because it doesn't create
additional work for us if we want to remain with the status quo, and
it gives us additional options if we want to use them.
On Mar 19, 2:39 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Even further clarifications:
Top Tweets are coming to make search results even more relevant. We'll be
tuning our ranking algorithms with gusto. Some people will naturally resist
these changes. Approach with a zen mind.
When we launch this new feature for the API, it will be opt-in for a
transitory period, but the search.twitter.com site will come with these
results already baked in. Before implementing in your own applications,
you'll be able to see the top results for your favorite queries your self.
The Search team is always working on ways of making results more
relevant. We recognize that not everyone wants search results with
algorithmic ranking of tweets, but we like what we've come up with and we
think you'll like it too.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Fri, Mar 19, 2010 at 10:11 AM, davidzimm davidz...@yahoo.com wrote:
Bad idea.
1) reduces the credibility and thereby the value of the results in
twitter search
2) who determines which is popular- no matter how you try to calculate
this, someone will figure it out and spam the results.
3) people are used to searching twitter for breaking news, rather than
authoritative results. You'll have to change user expectations.
4) perhaps this can be an advanced setting, rather than a default
practice.
On Mar 19, 10:37 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Developers!
The Search team is working on a beta project that returns the most
popular
tweets for a query, rather than only the most recent tweets. This is a
beta
project, but an important first step to surface the most popular tweets
for
users searching Twitter.
You can expect many improvements as we tune and tweak our algorithms, but
we
want to give everyone a heads up so we can go over the implications for
those consuming the search API.
--- New attribute in the payload ---
First of all there will be a new attribute in search result payloads.
Since
some tweets are popular for a given query while others are simply the
most
recent results that match the query, we are adding a metadata section
to
specify the type of result that a given result represents.
So for a popular tweet the result_type in the metadata section will
have
the value popular.
Example of a result with a popular tweet:
{
results:
[
{
profile_image_url:
http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon,15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:a href=http://www.atebits.com/;
rel=nofollowTweetie/a,
metadata:
{
result_type: popular
}
}
/* etc ... */
}
Results that are not popular and represent simply recent query matches
will
have the result_type in the metadata section with a value of
recent.
Example of a recent result:
{
results:
[
{
profile_image_url:
http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:a href=http://www.atebits.com/;
rel=nofollowTweetie/a,
metadata:
{
result_type: recent
}
},
/* etc ... */
}
--- Results with popular tweets aren't ordered
Re: [twitter-dev] Chrome plugin to shut down unwanted Twitter popups?
FWIW, twttr.HOVERCARD.disable() does exactly what you'd guess. It would be dead easy to wrap into a userscript or bookmarklet if that's what you want to do. Jordan On Fri, Mar 19, 2010 at 2:24 PM, Abraham Williams 4bra...@gmail.com wrote: The hovercards are trigger with class=tweet-url screen-name. Have the Chrome extension remove those classes and the hovercards stop. Abraham On Fri, Mar 19, 2010 at 12:15, Andrew Badera and...@badera.us wrote: The problem is clientside script. The answer with a Chrome plugin would be clientside script. Catch-22? ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Fri, Mar 19, 2010 at 2:12 PM, neal rauhauser nrauhau...@gmail.com wrote: Someone suggested that a Chrome plugin to shut down this profile popup stuff was possible - has anyone actually done such a thing? It is desperately needed - Twitter is all but unusable for those of us on Atom based machines with all of this undesired popping lag. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Chrome plugin to shut down unwanted Twitter popups?
I can understand the strategic need Twitter has to get value add services in place and some of them are very good, but they should be OPTIONS controllable in our profile so as to not antagonize those with wee computin' widgets. On Fri, Mar 19, 2010 at 2:34 PM, Jordan Running jrunn...@gmail.com wrote: FWIW, twttr.HOVERCARD.disable() does exactly what you'd guess. It would be dead easy to wrap into a userscript or bookmarklet if that's what you want to do. Jordan On Fri, Mar 19, 2010 at 2:24 PM, Abraham Williams 4bra...@gmail.com wrote: The hovercards are trigger with class=tweet-url screen-name. Have the Chrome extension remove those classes and the hovercards stop. Abraham On Fri, Mar 19, 2010 at 12:15, Andrew Badera and...@badera.us wrote: The problem is clientside script. The answer with a Chrome plugin would be clientside script. Catch-22? ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Fri, Mar 19, 2010 at 2:12 PM, neal rauhauser nrauhau...@gmail.com wrote: Someone suggested that a Chrome plugin to shut down this profile popup stuff was possible - has anyone actually done such a thing? It is desperately needed - Twitter is all but unusable for those of us on Atom based machines with all of this undesired popping lag. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Twitter bug OR deliberate OAuth exception in the new versioning api ?
While we may very well version the OAuth endpoints in the future, it's best not to consider OAuth authorization flow steps as APIs in and of themselves. At this time, versioned areas of the API are areas relating to actual resources that correspond to data Twitter provides and processes (statuses, search results, information about users, favorites, lists, timelines, etc.) Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, Mar 19, 2010 at 11:11 AM, Ram group...@cascadesoft.net wrote: I didn't get any response for last week's http://twitter.com/CascadeRam/status/10487105790 , so I'm hoping to get an official response here. In October, last year, http://groups.google.com/group/twitter-api-announce/browse_thread/thread/2b70bd6ea4aec175 recommended that all developers move to the new versioned apis and that Twitter would set a hard date after whch http://twitter.com will not be serviced. However, 5 months after that announcement, the new versioned api doesn't seem to be supported for Twitter OAuth calls (though the versioned api works with other methods like http://api.twitter.com/1/friendships/create.xml) http://api.twitter.com/1/oauth/request_token returns a 404 (but http://twitter.com/oauth/request_token and http://api.twitter.com/oauth/access_token work correctly) So for now, I'm using the following (non-versioned) URLs http://api.twitter.com/oauth/authorize?oauth_token=xx http://api.twitter.com/oauth/authorize http://api.twitter.com/oauth/access_token and I'm using versioned URLs for other stuff like http://api.twitter.com/1/statuses/update.xml Are these the best URLs to be using now ? Does anyone know whether the 404 error is due to a bug, due to an incomplete implementation of the new api or whether OAuth apis are exempted from versioning ? To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Twitter bug OR deliberate OAuth exception in the new versioning api ?
Thanks Taylor, this is good to know. Btw for OAuth, should I be using the following URLs http://api.twitter.com/oauth/authorize?oauth_token=xx http://api.twitter.com/oauth/authorize http://api.twitter.com/oauth/access_token or should I be using their http://twitter.com equivalents ? Both work fine. Thanks Ram On Mar 19, 1:07 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: While we may very well version the OAuth endpoints in the future, it's best not to consider OAuth authorization flow steps as APIs in and of themselves. At this time, versioned areas of the API are areas relating to actual resources that correspond to data Twitter provides and processes (statuses, search results, information about users, favorites, lists, timelines, etc.) Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, Mar 19, 2010 at 11:11 AM, Ram group...@cascadesoft.net wrote: I didn't get any response for last week's http://twitter.com/CascadeRam/status/10487105790 , so I'm hoping to get an official response here. In October, last year, http://groups.google.com/group/twitter-api-announce/browse_thread/thr... recommended that all developers move to the new versioned apis and that Twitter would set a hard date after whchhttp://twitter.comwill not be serviced. However, 5 months after that announcement, the new versioned api doesn't seem to be supported for Twitter OAuth calls (though the versioned api works with other methods like http://api.twitter.com/1/friendships/create.xml) http://api.twitter.com/1/oauth/request_tokenreturns a 404 (but http://twitter.com/oauth/request_tokenand http://api.twitter.com/oauth/access_token work correctly) So for now, I'm using the following (non-versioned) URLs http://api.twitter.com/oauth/authorize?oauth_token=xx http://api.twitter.com/oauth/authorize http://api.twitter.com/oauth/access_token and I'm using versioned URLs for other stuff like http://api.twitter.com/1/statuses/update.xml Are these the best URLs to be using now ? Does anyone know whether the 404 error is due to a bug, due to an incomplete implementation of the new api or whether OAuth apis are exempted from versioning ? To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Twitter bug OR deliberate OAuth exception in the new versioning api ?
Hi Ram, I recommend standardizing on api.twitter.com for the OAuth endpoints as well as the resource endpoints. Further, for all the OAuth-related steps (authorize, access_token, and request_token) I strongly recommend using SSL. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, Mar 19, 2010 at 1:21 PM, Ram group...@cascadesoft.net wrote: Thanks Taylor, this is good to know. Btw for OAuth, should I be using the following URLs http://api.twitter.com/oauth/authorize?oauth_token=xx http://api.twitter.com/oauth/authorize http://api.twitter.com/oauth/access_token or should I be using their http://twitter.com equivalents ? Both work fine. Thanks Ram On Mar 19, 1:07 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: While we may very well version the OAuth endpoints in the future, it's best not to consider OAuth authorization flow steps as APIs in and of themselves. At this time, versioned areas of the API are areas relating to actual resources that correspond to data Twitter provides and processes (statuses, search results, information about users, favorites, lists, timelines, etc.) Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, Mar 19, 2010 at 11:11 AM, Ram group...@cascadesoft.net wrote: I didn't get any response for last week's http://twitter.com/CascadeRam/status/10487105790 , so I'm hoping to get an official response here. In October, last year, http://groups.google.com/group/twitter-api-announce/browse_thread/thr. .. recommended that all developers move to the new versioned apis and that Twitter would set a hard date after whchhttp://twitter.comwill not be serviced. However, 5 months after that announcement, the new versioned api doesn't seem to be supported for Twitter OAuth calls (though the versioned api works with other methods like http://api.twitter.com/1/friendships/create.xml) http://api.twitter.com/1/oauth/request_tokenreturns a 404 (but http://twitter.com/oauth/request_tokenand http://api.twitter.com/oauth/access_token work correctly) So for now, I'm using the following (non-versioned) URLs http://api.twitter.com/oauth/authorize?oauth_token=xx http://api.twitter.com/oauth/authorize http://api.twitter.com/oauth/access_token and I'm using versioned URLs for other stuff like http://api.twitter.com/1/statuses/update.xml Are these the best URLs to be using now ? Does anyone know whether the 404 error is due to a bug, due to an incomplete implementation of the new api or whether OAuth apis are exempted from versioning ? To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Twitter bug OR deliberate OAuth exception in the new versioning api ?
Thanks again, Taylor. I'll use api.twitter.com instead of twitter.com I'm already using https://twitter.com calls for the app (currently in the app store), but I use http for test purposes (easier for debugging and tracking traffic) Ram On Mar 19, 1:30 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Ram, I recommend standardizing on api.twitter.com for the OAuth endpoints as well as the resource endpoints. Further, for all the OAuth-related steps (authorize, access_token, and request_token) I strongly recommend using SSL. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, Mar 19, 2010 at 1:21 PM, Ram group...@cascadesoft.net wrote: Thanks Taylor, this is good to know. Btw for OAuth, should I be using the following URLs http://api.twitter.com/oauth/authorize?oauth_token=xx http://api.twitter.com/oauth/authorize http://api.twitter.com/oauth/access_token or should I be using theirhttp://twitter.comequivalents ? Both work fine. Thanks Ram On Mar 19, 1:07 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: While we may very well version the OAuth endpoints in the future, it's best not to consider OAuth authorization flow steps as APIs in and of themselves. At this time, versioned areas of the API are areas relating to actual resources that correspond to data Twitter provides and processes (statuses, search results, information about users, favorites, lists, timelines, etc.) Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, Mar 19, 2010 at 11:11 AM, Ram group...@cascadesoft.net wrote: I didn't get any response for last week's http://twitter.com/CascadeRam/status/10487105790 , so I'm hoping to get an official response here. In October, last year, http://groups.google.com/group/twitter-api-announce/browse_thread/thr. .. recommended that all developers move to the new versioned apis and that Twitter would set a hard date after whchhttp://twitter.comwill not be serviced. However, 5 months after that announcement, the new versioned api doesn't seem to be supported for Twitter OAuth calls (though the versioned api works with other methods like http://api.twitter.com/1/friendships/create.xml) http://api.twitter.com/1/oauth/request_tokenreturnsa 404 (but http://twitter.com/oauth/request_tokenand http://api.twitter.com/oauth/access_token work correctly) So for now, I'm using the following (non-versioned) URLs http://api.twitter.com/oauth/authorize?oauth_token=xx http://api.twitter.com/oauth/authorize http://api.twitter.com/oauth/access_token and I'm using versioned URLs for other stuff like http://api.twitter.com/1/statuses/update.xml Are these the best URLs to be using now ? Does anyone know whether the 404 error is due to a bug, due to an incomplete implementation of the new api or whether OAuth apis are exempted from versioning ? To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Introduce yourself!
Hi, I'm Derek Gathright, Yahoo engineer by day, Twitter hacker by night. I first started with the platform by creating a web client a few years ago (Tweenky.com, currently suffering from a little neglect) and since went on to create a number of other random apps. After Tweenky's launch, TechCrunch picked it up and the traffic slammed the site, just about killing it. Performance was horrible, so I decided to fix the scaling issue by getting rid of a backend. Wha? How do you do that? I rewrote it in 99% JavaScript (the 1% being a cross-domain proxy). I first started with jQuery, and am now working on another rewrite in YUI3. In the past, it was easy to out-innovate the Twitter.com client, but nowdays it is hard to keep up with only a few hours/week. Slow down guys! :P By doing all this experimentation with Twitter in JS, it's allowed, and inspired me, to learn so much about that language. Knowledge I otherwise probably wouldn't have, and that's what I love about the Twitter platform. It's so flexible and allows me to use it as the basis for tinkering around with any new technology I want. Feel like learning some new language or framework? Create a Twitter app. When the incredibly awesome JSFiddle.net came out, the first thing I did was hack together a YUI3/YQL/Twitter example to play around (http://jsfiddle.net/derek/Vjxt2/). Doing that with Facebook and other platforms would be more difficult than just a few lines of code. Anyways, /rambling Cheers http://twitter.com/derek http://derekville.net On Fri, Mar 19, 2010 at 11:19 AM, Quy quyten...@gmail.com wrote: My name is Quy Le (@quytennis) and I used to be a software engineer but now I'm product manager at a high-tech company. I've been using the Twitter API for the past 3 months on a Twitter project that hopefully will go live in a few weeks. I've been using PHP/mySQL/ memcached to build my site but it has been a slow process since I have a day job and I'm relearning some of the new technology since I haven't touched a piece of code in over 8-9 years. (Designing for IE6 sucks). The feature I would love the most is a conversation API so it's easy to show conversations based on a tweet. Quy On Feb 19, 1:20 pm, Abraham Williams 4bra...@gmail.com wrote: We have not had an introductions thread in a long time (or ever that I could find) so I'm starting one. Don't forget to add an answer to the tools thread [1](Gmail link [2]) as well. I'm Abraham Williams, I've been working with the Twitter API and this group since early 2008. I do mostly freelance Drupal and Twitter API integration and personal projects. I love seeing the creative projects developers build or integrate with the API and look forward to meeting many of you at Chirp. TwitterOAuth [3] the first PHP library to support OAuth is built and maintained by me, and will hopefully see a new release soon. I also built a fun Chrome extension [4] that integrates common friends and followers into Twitter profiles. The feature I would most like added to the API is a conversation method to get replies to a specific status. So. Who are you, what do you do, what have you built, and what feature do you most want to see added? @Abraham [1] http://groups.google.com/group/twitter-development-talk/browse_thread... [2]https://mail.google.com/mail/#inbox/12680cd0fa59011e [3] https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogo... [4]http://code.google.com/p/twitter-api/issues/detail?id=142 -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Most popular tweets in the search API
As a developer, I've got my foot in (at least) two communities:
Twitter developers and on-line marketing practitioners. Given that, I
think this discussion needs to happen in a larger forum than the
Twitter Developers' Google Group. I've put up a blog post and created
a hashtag (#tweetsearchpop), and I'd like to invite you all to
participate that way - I'm prepared to man the comment monitoring
dashboard ;-)
http://borasky-research.net/2010/03/19/seeker-or-seller-what-do-you-think-about-adding-popularity-to-twitter-search-tweetsearchpop/
--
M. Edward (Ed) Borasky
borasky-research.net/m-edward-ed-borasky/
A mathematician is a device for turning coffee into theorems. ~ Paul Erdos
Quoting Dewald Pretorius dpr...@gmail.com:
Taylor,
In terms of this change, you need to separate Twitter Search from the
Twitter Search API in your minds.
Do with Twitter Search (the web interface) what you like. Make popular
the default if you want.
But, don't decide on behalf of the developers (the consumers of the
Twitter Search API) that popular is the default that we want. In most
cases it probably isn't. In my case it definitely isn't, otherwise I
would have asked for something like that a long time ago.
In other words, don't force something down our throats just because
you think it's a cool idea.
Leave the default as is. Make popular an option that we can use if
we want to. That's good developer service, because it doesn't create
additional work for us if we want to remain with the status quo, and
it gives us additional options if we want to use them.
On Mar 19, 2:39 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Even further clarifications:
Top Tweets are coming to make search results even more relevant. We'll be
tuning our ranking algorithms with gusto. Some people will naturally resist
these changes. Approach with a zen mind.
When we launch this new feature for the API, it will be opt-in for a
transitory period, but the search.twitter.com site will come with these
results already baked in. Before implementing in your own applications,
you'll be able to see the top results for your favorite queries your self.
The Search team is always working on ways of making results more
relevant. We recognize that not everyone wants search results with
algorithmic ranking of tweets, but we like what we've come up with and we
think you'll like it too.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Fri, Mar 19, 2010 at 10:11 AM, davidzimm davidz...@yahoo.com wrote:
Bad idea.
1) reduces the credibility and thereby the value of the results in
twitter search
2) who determines which is popular- no matter how you try to calculate
this, someone will figure it out and spam the results.
3) people are used to searching twitter for breaking news, rather than
authoritative results. You'll have to change user expectations.
4) perhaps this can be an advanced setting, rather than a default
practice.
On Mar 19, 10:37 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Developers!
The Search team is working on a beta project that returns the most
popular
tweets for a query, rather than only the most recent tweets. This is a
beta
project, but an important first step to surface the most popular tweets
for
users searching Twitter.
You can expect many improvements as we tune and tweak our
algorithms, but
we
want to give everyone a heads up so we can go over the implications for
those consuming the search API.
--- New attribute in the payload ---
First of all there will be a new attribute in search result payloads.
Since
some tweets are popular for a given query while others are simply the
most
recent results that match the query, we are adding a metadata section
to
specify the type of result that a given result represents.
So for a popular tweet the result_type in the metadata section will
have
the value popular.
Example of a result with a popular tweet:
{
results:
[
{
profile_image_url:
http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon,15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:a href=http://www.atebits.com/;
rel=nofollowTweetie/a,
metadata:
{
result_type: popular
}
}
/* etc ... */
}
Results that are not popular and represent simply recent query matches
will
have the result_type in the metadata section with a value of
recent.
Example of a recent result:
{
results:
[
{
profile_image_url:
[twitter-dev] Search API - Search words + people + date
Is it possible to search for a phrase, posted by a given user, since a given date? It doesn't seem to work. You can search for a phrase by a given user. Or you can search for a phrase since a given date. Both when you search for it all, you get zero results. I tried using this page, thinking my syntax was wrong: http://search.twitter.com/advanced. But that didn't do it, either. I am thinking I have to search my search results to do this b/c Twitter Search API doesn't seem to support it. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Twitter Project using the API (Paid)
Please let me know where this site is so I don't even consider going there. This is just spamming, surely? On 19 March 2010 17:01, TheN2S thenext2sh...@gmail.com wrote: John, Thanks for pointing that out! I will have a chat with my team and see how we can avoid this conflict. We do have another simple project that we want to get off its feet! Lets say we premiere an exclusive new song on our site. However to get to the song, users must login through twitter/facebook. While they login they are automatically set to follow @ouraccount and it automatically posts a status update on their account Currently checking out the brand new song for Sinatra! http://link.com;. Once that is done, the user is forwarded to the appropriate page that they originally intended to. If they don't sign in, they miss out on the release. This doesnt seem to be going against any terms of service... right? Once again, contact us if you are able to complete this project: http://bit.ly/9CSUc0 (all css/html is handled by us. We simply need the motor to power up the project. We take care of all the aesthetics.) On Mar 19, 9:27 am, John Kalucki j...@twitter.com wrote: This sounds a lot like @reply spam: http://help.twitter.com/forums/10711/entries/64986 If you are replying to followers, maybe that's OK, and maybe it isn't. But, if you are @replying to everyone, you will be suspended. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Mar 18, 2010 at 8:26 PM, TheN2S thenext2sh...@gmail.com wrote: I am looking for a twitter developer that is able to use the API to respond back to tweets containing a specific quote. Lets say for example an artist YXZ has just done a rendition of New York by Frank Sinatra. We want to @reply every user that mentions York Sinatra in their tweet with a customized reply such as I see you like Sinatra's original New York song.. but have you checked out ZYX's new version? It's a simple concept, and it has been done already. Please also be aware that twitter has an API limit that we don't want to disturb. We are in need of a developer to move this project forward. Please contact us back using this form:http://bit.ly/9CSUc0 Thanks! (= To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Introduce yourself!
I'll follow Quy's lead. I have been providing social media training / support to companies for the last year, earlier this year I identified a number of services/features that desktop clients should have, and have today successfully used my client, developed in C++ with QTwitlib, to read from and post to Twitter. After some further development, the client will be released (Windows only till someone provides me Mac Linux machines) as open-source. I've been following the discussion here for a couple of weeks, it has helped me understand the API better. Cheers all, Nigel. On 19 March 2010 18:19, Quy quyten...@gmail.com wrote: My name is Quy Le (@quytennis) and I used to be a software engineer but now I'm product manager at a high-tech company. I've been using the Twitter API for the past 3 months on a Twitter project that hopefully will go live in a few weeks. I've been using PHP/mySQL/ memcached to build my site but it has been a slow process since I have a day job and I'm relearning some of the new technology since I haven't touched a piece of code in over 8-9 years. (Designing for IE6 sucks). The feature I would love the most is a conversation API so it's easy to show conversations based on a tweet. Quy On Feb 19, 1:20 pm, Abraham Williams 4bra...@gmail.com wrote: We have not had an introductions thread in a long time (or ever that I could find) so I'm starting one. Don't forget to add an answer to the tools thread [1](Gmail link [2]) as well. I'm Abraham Williams, I've been working with the Twitter API and this group since early 2008. I do mostly freelance Drupal and Twitter API integration and personal projects. I love seeing the creative projects developers build or integrate with the API and look forward to meeting many of you at Chirp. TwitterOAuth [3] the first PHP library to support OAuth is built and maintained by me, and will hopefully see a new release soon. I also built a fun Chrome extension [4] that integrates common friends and followers into Twitter profiles. The feature I would most like added to the API is a conversation method to get replies to a specific status. So. Who are you, what do you do, what have you built, and what feature do you most want to see added? @Abraham [1] http://groups.google.com/group/twitter-development-talk/browse_thread... [2]https://mail.google.com/mail/#inbox/12680cd0fa59011e [3] https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogo... [4]http://code.google.com/p/twitter-api/issues/detail?id=142 -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] stream heartbeat/keep-alives
the twitter streaming api docs say Parsers must be tolerant of occasional extra newline characters placed between statuses. These characters are placed as periodic keep-alive messages, should the stream of statuses temporarily pause. These keep-alives allow clients and NAT firewalls to determine that the connection is indeed still valid during low volume periods. that's all well and good, but I'd like some clarification on some behavior I'm seeing. I never see newlines come through alone... rather I always see CRLF (carriage return + linefeed; adjacent) pairs (two chars) come through on 30 second intervals to keep-alive. as a result, I've built my parser to consider the combination CRLF as the heartbeat. should I be doing this, or am I missing something along the way in which I should truly only ever be looking for LFs? To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] stream heartbeat/keep-alives
CRLF pairs are indeed what get sent, and what you should build around. You shouldn't ever get a naked LF. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 3:50 PM, Jud jvale...@gmail.com wrote: the twitter streaming api docs say Parsers must be tolerant of occasional extra newline characters placed between statuses. These characters are placed as periodic keep-alive messages, should the stream of statuses temporarily pause. These keep-alives allow clients and NAT firewalls to determine that the connection is indeed still valid during low volume periods. that's all well and good, but I'd like some clarification on some behavior I'm seeing. I never see newlines come through alone... rather I always see CRLF (carriage return + linefeed; adjacent) pairs (two chars) come through on 30 second intervals to keep-alive. as a result, I've built my parser to consider the combination CRLF as the heartbeat. should I be doing this, or am I missing something along the way in which I should truly only ever be looking for LFs? To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] stream heartbeat/keep-alives
Newline is a logical concept generally materialized as a CRLF. The pair of characters is a newline. Generally you don't need to look for the newline, if you can set your TCP socket timeout to some small multiple of the keepalive time, perhaps 60 or 90 seconds, you should get this for free. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Mar 19, 2010 at 3:50 PM, Jud jvale...@gmail.com wrote: the twitter streaming api docs say Parsers must be tolerant of occasional extra newline characters placed between statuses. These characters are placed as periodic keep-alive messages, should the stream of statuses temporarily pause. These keep-alives allow clients and NAT firewalls to determine that the connection is indeed still valid during low volume periods. that's all well and good, but I'd like some clarification on some behavior I'm seeing. I never see newlines come through alone... rather I always see CRLF (carriage return + linefeed; adjacent) pairs (two chars) come through on 30 second intervals to keep-alive. as a result, I've built my parser to consider the combination CRLF as the heartbeat. should I be doing this, or am I missing something along the way in which I should truly only ever be looking for LFs? To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Most popular tweets in the search API
+1 to Cameron and funkatron. Making this default, even with a transition period, would be extremely bad practice. The whole point of API versioning is such that old stuff does not break. And yes, changing behavior so that results returned to same query are suddenly different is definitely breaking. I find popular tweets in search results mixed with recents to be a great idea, but it cannot be the default, since it would break many apps that have relied on current behavior. And having whatever transition period is not good enough. You are forcing developers to change priorities and re-test old stuff, some of which may be unmaintained legacy. API versioning and backwards compatibility are standard industry practices, just please stick to those and don't piss off developers any further. (I could insert a more elaborate rant here to show what I really feel, but the above captures the point.) rgds, Jaanus On Mar 19, 3:29 pm, Cameron Kaiser spec...@floodgap.com wrote: Your definition of time to adjust may not be ours. Twitter has, to be honest, a fairly crappy reputation for changing API behavior. While some of that was surely driven by performance concerns, I don't see how this could be. This doesn't help the rep. Please, do not enable this by default, *ever*. Don't change behavior unless it is necessary. Add a new API method, or make recent results the default and keep it that way. If you're advocating for developers, advocate for making us do less work to maintain current functionality, please. This is spot on. It's not that I think the idea itself is bad -- I'm all for more relevant search results *when relevance is what's requested*. Right now, every app that queries the Search API expects time-oriented results because that's what we got before. Making this the new default is needless dev chaos, *and* I haven't heard if there is even a way to opt back to the old behaviour if this becomes the ill-advised default anyway. I'd love to support this feature, in the appropriate context, when it makes sense to do so. I don't want to have to code around it as the new, unsolicited default when it doesn't. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- FORTUNE: Good day for romance, but try a single person this time. -- To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Most popular tweets in the search API
+1 for asking for keeping the default as it is right now (should be clear really strange to even discuss this) To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] translation in twitter
i dont know,sorrie if u find out e-mail me ok.candelaria.pa...@gmail.com On Thu, Mar 18, 2010 at 12:48 PM, deb123 debolina@gmail.com wrote: Hello, I am using twitter 4j to get the oauth page with the Accept and Deny options. I am wondering if twitter has support for international languages and if so how do I pass the locale information in the url? Thanks, D To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Scheduling send times for tweets
go to your calendar do it on that it mit work , On Thu, Mar 18, 2010 at 10:52 AM, Cassidy cassc...@gmail.com wrote: I'm trying to put together a twitter app so I can easily send myself reminders...what I'm currently doing is using HootSuite to manually schedule tweets to be sent out at specific times to my personal account. I'd like to make it so that I can mention my reminder twitter account and then it will take the info in the tweet, schedule it, and @reply me back at the given time. So basically I would tweet @dontforget2 pick up your medicine, 03/20/2010 6:00pm and my account would tweet back @me pick up your medicine at 6pm on 3/20. There are a lot of things that I still need to figure out, but the main challenge for me right now is finding out a method to store the time and actual have it send the tweet at the given time. Any suggestions? To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: since_id to old and some way to detect new id
Sorry this is the url without spaces scaped http://search.twitter.com/search.atom?q=imente com -huubs verdienst -steven huubs -marc mateu gardey -marc mateu alsina -v imente com -juvenil -marc mateusince_id=1520639490 In fact now, at this moment, this id is older than 2 weeks but the problem starts to appear in the beginning of the week, 15, or 16 when the 2 weeks was not completed. One question then, for what you say. If I make this search http://search.twitter.com/search.atom?q=twitter This give me various tweets and this url link type=application/atom+xml href=http://search.twitter.com/ search.atom?q=twitteramp;since_id=10744222159 rel=refresh/ So the next search I will use that since_id. In the case of these search there will be no problem, because is a query with a lot of results so I will made that search more often than 2 weeks. But if I wait more thant 2 weeks to redone the search, this id will expire? In that case could be usefull that with error since_id to old could be included the oldest allowed since_id On 19 Març, 17:46, Mark McBride mmcbr...@twitter.com wrote: Can you post the exact URL you're using? The one posted fails because the query is longer than 140 characters. Trimming it to a single term succeeds. This may be due to the fact that your ID is older than two weeks, and is therefore unknown to search. You could try using since=date instead and see if that works. ---Mark http://twitter.com/mccv On Fri, Mar 19, 2010 at 2:49 AM, NetOak net...@gmail.com wrote: When I perform some search through the API, like this example: http://search.twitter.com/search.atom?q= imente%20com%20-huubs%20verdienst%20-steven%20huubs%20-marc%20mateu% 20gardey%20-marc%20mateu%20alsina%20-v%20imente%20com%20-juvenil%20-m arc%20mateusince_id=9970356763 I get he response that since_id is to old. The tweet that is referred by id is correct, present and accessible. Is this one:http://twitter.com/pa1et/status/9970356763 In somewhere there's a specification of a id could not be used in since_id parameter? There's some pattern, some rule to detect when a id is too old to use in since_id parameter? To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Most popular tweets in the search API
As someone who's developing some applications right now specifically
involving the search APIs I now have to worry about whether or not I
should pre-emptively include the result_type parameter so my app
doesn't become non-functioning when the changes are pushed to the
site. Why do the popular tweets have to be the default behavior in the
API?
On Mar 19, 7:42 am, funkatron funkat...@gmail.com wrote:
So this would change the default behavior of the search API, which is
currently to return recent results?
If so, I think that's a bad idea. Better to offer the option than to
change existing behavior when possible.
--
Ed Finklerhttp://funkatron.com
Twitter:@funkatron
AIM: funka7ron
ICQ: 3922133
XMPP:funkat...@gmail.com
On Mar 19, 10:37 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Developers!
The Search team is working on a beta project that returns the most popular
tweets for a query, rather than only the most recent tweets. This is a beta
project, but an important first step to surface the most popular tweets for
users searching Twitter.
You can expect many improvements as we tune and tweak our algorithms, but we
want to give everyone a heads up so we can go over the implications for
those consuming the search API.
--- New attribute in the payload ---
First of all there will be a new attribute in search result payloads. Since
some tweets are popular for a given query while others are simply the most
recent results that match the query, we are adding a metadata section to
specify the type of result that a given result represents.
So for a popular tweet the result_type in the metadata section will have
the value popular.
Example of a result with a popular tweet:
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon,15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:lt;a href=quot;http://www.atebits.com/;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: popular
}
}
/* etc ... */
}
Results that are not popular and represent simply recent query matches will
have the result_type in the metadata section with a value of recent.
Example of a recent result:
{
results:
[
{
profile_image_url:http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:lt;a href=quot;http://www.atebits.com/;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: recent
}
},
/* etc ... */
}
--- Results with popular tweets aren't ordered chronologically ---
Until the popular tweet feature all search results have been sorted
chronologically, most recent results at the top. If a search query has any
popular results, those will be returned at the top, even if they are older
than the other results.
Example of a non-chronologically ordered set of results including popular
results:
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon, 15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:lt;a href=quot;http://www.atebits.com/;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: popular
}
},
{
profile_image_url:http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:lt;a
