Re: [twitter-dev] I'm using xAuth, I need to read Direct Messages, what are my options?
Forgive me if I'm wrong, but don't you get the oAuth tokens when you log in with xAuth? On 7/15/2011 10:00 AM, Garry wrote: e xAuth to access Twitter, my platform of choice (IBM AS/ 400) has no GUI, and no web browser, so OAuth is out. -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] Re: Twitter API SSL certificate failing validation
Make sure in /etc/ssl/certs that you have a copy of the Verisign root CA file, just like in the java example above. If you're loading all files from /etc/ssl/certs you should be able to just drop in the http://curl.haxx.se/ca/cacert.pem file and that should fix your issue. -j On Wed, Jul 20, 2011 at 3:29 AM, Haitham wrote: > Pardon me, I have the same problem, but I seem to be missing something > about the solution. > > My application is in Ruby on Rails, with a gem called "OmniAuth" doing > the OAuth work. It was working just fine before this change, > automatically fetching my certificates from /etc/ssl/certs directory. > What should I do to adjust to the new CA? > > Thanks in advance. > > On Jul 19, 5:54 am, John Adams wrote: > > On Mon, Jul 18, 2011 at 8:17 PM, pgarvie wrote: > > > Has Twitter done something with its SSL certificates lately? As in > > > sometime this afternoon? We've been seeing a ton of > > > sun.security.validator.ValidatorExceptions coming out of Twitter4J > > > since about 5:30PM, USCentral. > > > > The certificate for api.twitter.com previously used a wildcard > certificate > > which was issued by Rapid SSL. We switched the API SSL certificate (after > > much testing) to a Verisign SSL certificate today and the IP to dedicated > > VIPs. If you are using Java, there may be a chance that you do not have > the > > Verisign Root CA Certificate installed in the Java Keychain of your > > application. Make sure that exists. You'll need that to verify our > > certificate chain. > > > > You want this Root CA, which is available from Verisign (or in this file: > http://curl.haxx.se/ca/cacert.pem) > > > >i:/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification > > Authority - G2/OU=(c) 1998 VeriSign, Inc. - For authorized use > > only/OU=VeriSign Trust Network > > > > You may also need to clear your DNS cache and/or restart your > application. > > I've seen Java's security layer not revalidate SSL certificates correctly > > until restart, but I know little about how your application functions. > > > > -John > > Twitter Security > > -- > Have you visited the Developer Discussions feature on > https://dev.twitter.com/discussions yet? > > Twitter developer links: > Documentation and resources: https://dev.twitter.com/docs > API updates via Twitter: https://twitter.com/twitterapi > > Unsubscribe or change your group membership settings: > http://groups.google.com/group/twitter-development-talk/subscribe > -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] Twitter API SSL certificate failing validation
On Mon, Jul 18, 2011 at 8:17 PM, pgarvie wrote: > Has Twitter done something with its SSL certificates lately? As in > sometime this afternoon? We've been seeing a ton of > sun.security.validator.ValidatorExceptions coming out of Twitter4J > since about 5:30PM, USCentral. The certificate for api.twitter.com previously used a wildcard certificate which was issued by Rapid SSL. We switched the API SSL certificate (after much testing) to a Verisign SSL certificate today and the IP to dedicated VIPs. If you are using Java, there may be a chance that you do not have the Verisign Root CA Certificate installed in the Java Keychain of your application. Make sure that exists. You'll need that to verify our certificate chain. You want this Root CA, which is available from Verisign (or in this file: http://curl.haxx.se/ca/cacert.pem) i:/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority - G2/OU=(c) 1998 VeriSign, Inc. - For authorized use only/OU=VeriSign Trust Network You may also need to clear your DNS cache and/or restart your application. I've seen Java's security layer not revalidate SSL certificates correctly until restart, but I know little about how your application functions. -John Twitter Security -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] tweet button zero count
Well, as i said before, it doesnt work with Firefox 3.6. Thanks anyway. 2011/6/2 Scott Wilcox > Firefox 4.0.1, OSX 10.6. No plugins. Works fine in Chrome and Safari too. > > On 2 Jun 2011, at 12:04, John Carver wrote: > > What version of browser do you use? Do you have any plugins installed? > > 2011/6/2 Scott Wilcox > >> The URL count is working fine for me. >> >> On 2 Jun 2011, at 11:41, John Carver wrote: >> >> Hi Matt, >> >> Today have figured out zero count is firefox issue. IE, Opera, Chrome all >> work just fine. >> >> Take the look: >> http://icisweb.ru/tweet-button-test/ >> >> I'm using FF 3.6.17 >> >> Any suggestions? >> >> Thanks >> >> >> -- >> Scott Wilcox >> >> @dordotky | sc...@dor.ky | http://dor.ky >> +44 (0) 7538 842418 | +1 (646) 827-0580 >> >> >> >> >> -- >> Twitter developer documentation and resources: >> https://dev.twitter.com/doc >> API updates via Twitter: https://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> https://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> https://groups.google.com/forum/#!forum/twitter-development-talk >> > > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > > > -- > Scott Wilcox > > @dordotky | sc...@dor.ky | http://dor.ky > +44 (0) 7538 842418 | +1 (646) 827-0580 > > > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] tweet button zero count
What version of browser do you use? Do you have any plugins installed? 2011/6/2 Scott Wilcox > The URL count is working fine for me. > > On 2 Jun 2011, at 11:41, John Carver wrote: > > Hi Matt, > > Today have figured out zero count is firefox issue. IE, Opera, Chrome all > work just fine. > > Take the look: > http://icisweb.ru/tweet-button-test/ > > I'm using FF 3.6.17 > > Any suggestions? > > Thanks > > > -- > Scott Wilcox > > @dordotky | sc...@dor.ky | http://dor.ky > +44 (0) 7538 842418 | +1 (646) 827-0580 > > > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] tweet button zero count
Hi Matt, Today have figured out zero count is firefox issue. IE, Opera, Chrome all work just fine. Take the look: http://icisweb.ru/tweet-button-test/ I'm using FF 3.6.17 Any suggestions? Thanks -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] tweet button zero count
Hello Twitter support, Please advice im starting to frustrate. Tweet button count for our posts stays equal to 0. We set urls canonical, we use data-url and data-count-url with exactly same data - nothing helps. Please advice extremely ASAP: http://52outspoker.com/posts/?word1-word2-word0 http://52outspoker.com/posts/?word1-word2-word1 http://52outspoker.com/posts/?word1-word2-word2 http://52outspoker.com/posts/?word1-word2-word3 Regards, John. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: oauth weird issue
I was able to get things to work again by using https for the affected timelines. The api docs do not state that https is required. Is this some issue with the twitter api? Also not all users seem to be affected. Seems like another person was having a similar issue: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/b12eb886ec477465 On May 31, 2:30 am, John wrote: > I have an app that hasn't changed and has been working fine for > months. But the other day it stopped working. Heres what i'm > experiencing: > > -login, favorites, lists still works fine > -home, mentions and DMs give 'invalid signature' oauth error > > Other people have reported the same issue but for others the app works > fine. > > This first occurred after I came back from vacation from another > country and I tried to use the app from a device that I hadn't used in > months. The date/time on this device was incorrect causing oauth to > not work. When I update the date/time it allowed me to login but was > getting errors for home/mentions/DMs. The error seemed to pass over to > my other device which never had this problem and had been using on > vacation. > > I tried testing my twitter account with other twitter apps on the same > device and had the same issue on one but worked fine on another. > > any ideas? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] oauth weird issue
I have an app that hasn't changed and has been working fine for months. But the other day it stopped working. Heres what i'm experiencing: -login, favorites, lists still works fine -home, mentions and DMs give 'invalid signature' oauth error Other people have reported the same issue but for others the app works fine. This first occurred after I came back from vacation from another country and I tried to use the app from a device that I hadn't used in months. The date/time on this device was incorrect causing oauth to not work. When I update the date/time it allowed me to login but was getting errors for home/mentions/DMs. The error seemed to pass over to my other device which never had this problem and had been using on vacation. I tried testing my twitter account with other twitter apps on the same device and had the same issue on one but worked fine on another. any ideas? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] is there video or audio link inside
Thanks Taylor. I'll see how to proceed. Thanks again for your reply. 2011/5/3 Taylor Singletary > Hi John, > > There's currently no sure-fire way to determine if a link in a Tweet leads > to renderable content or the disposition of that content as a picture or a > video. > > However, by using Tweet Entities ( > http://dev.twitter.com/pages/tweet_entities ) you can get expanded > information about many of the URLs presented in Tweets -- for some URLs like > t.co-based URLs, they'll also be unshortened. Most API functions that return > Tweet data respond to an additional query parameter, include_entities=true > which expands the resource response to include the additional data nodes. > > A great additional thing you can do is keep up to date with the services > that embed.ly supports ( by using their API every so often to update your > list of their supported services: http://api.embed.ly/docs/service ) and > leverage embed.ly to render rich content when its origin is identifiable > by the tweet entities. > > @episod <http://twitter.com/episod> - Taylor Singletary > > > On Tue, May 3, 2011 at 7:17 AM, John Carver wrote: > >> Hi people. >> >> i wonder is there a way to determine if video or audio link inside >> statuse body? especially when short ls provided? i mean is there a n >> indication about? >> >> Any replies and thoughts would be appreciated. >> >> Thanks. >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] is there video or audio link inside
Hi people. i wonder is there a way to determine if video or audio link inside statuse body? especially when short ls provided? i mean is there a n indication about? Any replies and thoughts would be appreciated. Thanks. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: need twitter spam for a research project
You can use my account as an example. I'm currently getting between 50 and 150 follow spams per day for the last 3 weeks. Here's a graph that demonstrates the 'attack' http://screencast.com/t/xl7zcgdYI If you have any other questions, I'm @johnsheehan and can be reached via email same user name at gmail. John -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Custom URL Schemes on iphone with OAuth
After sending the user to safari to authorize, i get sent to mobile.twitter.com as opposed to my custom url scheme (something like myapp://). prior to authorizing, I did receive oauth_callback_confirmed=true. I've tried using a normal link like http://www.teamliquid.net, which works fine. Is there something I am missing? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] "D. Wade" !!!
hi why im not able to post any tweet starts with "D. Wade" ??? :) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] API (oAuth) posting to multiple accounts
hello everyone, i have one twitter client application under one twitter account. so oauth provides me possibility to update/status to this my twitter account. is there a way using JUST ONE APP to post to several accounts which belongs to me also. if yes how should i proceed? should i register app for each these accounts? thanks. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Streaming API limits...
This is documented in painful detail here: http://dev.twitter.com/pages/streaming_api_concepts#updating-filter-predicates . If you connect a second time, you should get a TCP Close or Reset on the first connection. It sounds like your client library isn't detecting the connection close. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Thu, Feb 24, 2011 at 1:08 PM, Josiah Carlson wrote: > Now that I've got OAuth with statuses/follow.json working, I've been > working through building a small part of our app. > > Part of the streaming API docs state that only one connection is allowed > (reasonable). Upon making a second connection, the first no longer receives > any data (not even anti-timeout newlines), nor does it get connected by the > server. On my end of things, I've written an async client which can detect > such a condition (it watches a shared Redis key looking for a changed state > when it doesn't receive any data for a while), and automatically > disconnects. > > The streaming API docs also state that repeated reconnections, etc., are > frowned upon and may result in banning. > > My question is simple: how often can I reconnect to follow different > people/keywords? Obviously ten times a second is well beyond reasonable and > would probably get us banned in seconds. But isat most once every 5 minutes > okay? At most once every minute? At what level would we be safe? > > Thank you, > - Josiah > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Streaming API access level limit
Are you specifying the IDs in the URL or in a POST parameter? There's a limit to the URL length that we'll parse, but we'll take huge POST parameters. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Tue, Feb 22, 2011 at 11:22 PM, aquajach wrote: > Hi, > > Just started to play with streaming API, but get confused on how many > followers id could be tracked with one connection. In basic level of > filter, > http://dev.twitter.com/doc/post/statuses/filter says 400 followers ids > http://dev.twitter.com/pages/streaming_api_methods says 5,000 > followers ids > > Then I tried in local machine, could only follow around 320 ids > ( receive 413 if more) and seems multiple connections in one IP are > not allowed. Any body here know: Is there any ways to follow a few > thousands ids for each authenticated account (with oauth)? Or how to > apply for higher access level? > > Any experience share or answers are appreciated! > > J > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Twitter stream shuts off every 60 seconds
It sounds like you have multiple connections on the same account. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Fri, Feb 25, 2011 at 2:20 PM, jon wrote: > Hi, > > If I try: > curl -d @tracking http://stream.twitter.com/1/statuses/filter.json - > uUsername:Password > tweets.json > > This shuts off in exactly 60 seconds. If I try the same command with > another account... it'll keep on going. > > Is there any way I can check the status of my account and know when > I'll have full access to the stream again? I'm trying to figure out > what's cutting off my stream. > > Thanks! > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Site Streams Beta - Endpoint change to sitestream.twitter.com
Note that Site Streams is still in a beta test. We're just moving endpoints around for other projects. Sorry for any confusion. -John On Tue, Feb 22, 2011 at 2:15 PM, John Kalucki wrote: > Please change your Site Streams beta clients to point to > sitestream.twitter.com and not to betastream.twitter.com. We'll continue > to support betastream.twitter.com for several weeks. This is more of a > clean-up step. > > Thanks, > -John Kalucki > http://twitter.com/jkalucki > Twitter, Inc. > > > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Site Streams Beta - Endpoint change to sitestream.twitter.com
Please change your Site Streams beta clients to point to sitestream.twitter.com and not to betastream.twitter.com. We'll continue to support betastream.twitter.com for several weeks. This is more of a clean-up step. Thanks, -John Kalucki http://twitter.com/jkalucki Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] is there a way to update statuses more then 100 per semi-hour at all?
greatings people. im using twitter api to update statuses but im getting this after about 100 of them have been posted in 1 hour time period: "error: User is over daily status update limit" i HAVE to post new tweets say 200 or even 500 per hour. is it possible at all? if yes how can i achieve this? it won't be spam or some kind of inappropriate materials. this is going to be value posts for my readers. i'd like to have this ability really much. thanks. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] User Streams and delimited=length
Delimited=length works with User Streams. Perhaps you have a typo.
-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.
On Wed, Feb 16, 2011 at 6:00 PM, WushuJames wrote:
> Hi,
>
> I'm playing around with User Streams. I was able to connect to
> https://userstream.twitter.com/2/user.json authenticated via OAuth and can
> see data coming in.
>
> I'm having trouble getting delimited=length working with User Streams. Or
> rather, I'm not sure if I'm using it correctly. I'm doing a POST and passing
> delimited=length in the body of my post.
>
> Here's what I see when I connect:
> 1) First, a list of friends as documented at
> http://dev.twitter.com/pages/user_streams, followed by \r\n
> Example:
>
> {"friends":[1497,169686021,790205,15211564,37784836,821958,14884312,92015003,822571,63846421...]}\r\n
>
> 2) Next, an "empty" line containing \r\n
>
> 3) the messages. The messages are JSON, and the line ends in \r\n. For
> example, I see:
> { ...somejson... }\r\n
> { ...somejson... }\r\n
> { ...somejson... }\r\n
>
> Is delimited=length supposed to work with user streams? Am I passing in the
> parameter correctly? (as POST variables in the body) Should I be passing
> delimited=length as GET variables in the URL? That didn't seem to work
> either, my request got rejected with a 401 HTTP error.
>
> Thanks,
> -James
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Streaming API vs. Search API: no API returns >95% of intented tweets
http://dev.twitter.com/pages/streaming_api_concepts#result-quality
Search filters for relevance and is not intended as a source of all tweets.
Streaming provides the complete record to all you to perform whatever
post-processing you'd like.
-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.
On Thu, Feb 17, 2011 at 12:15 AM, Karussell wrote:
> Hi Matt,
>
> sorry for being unspecific. By 'only in async' I meant tweets which
> were only found by the streaming API ('asynchronous retrieval') but
> were not in the search results **
>
> Why are they missing when using search API?
>
> > Also can you give an example of what you mean by a long Tweet.
>
> I investingated this a bit more and it seems to be intendend (?):
> these tweets are 'only' retweets. As example here is one too short
> tweet returned from the streaming API:
>
> RT @bcoders: Episode 33 onsite from @JFokus with @neal4d @nicksieger
> @brjavaman & Kirk Pepperdine is out! http://bit.ly/eikmux "is
> #Java ...
>
> and the same tweet (id == 37959896615886848) was more complete when
> returned from the search API:
>
> RT @bcoders: Episode 33 onsite from @JFokus with @neal4d @nicksieger
> @brjavaman & Kirk Pepperdine is out! http://bit.ly/eikmux "is #Java a
> dead-end?"
>
> So, when I use search API I'll miss tweets and when using streaming
> API I'll miss text? Do I need to use both?
>
> Regards,
> Peter.
>
> **
> 37952879822110720 Architecte Java J2EE: Priorité sera donnée à un
> candidat de la région nantaise. Merci de tran... http://bit.ly/dQhIoK
> #freelance #offres
> 37954149668622336 به روز رسانی: Nimbuzz اکنون با پشتیبانی از اتصال
> رسمی API فیس بوک http://t.co/ICgTAXX
> 37954912847400960 『Java Hangs When Converting 2.2250738585072012e-308』
> http://zennin.blog55.fc2.com/blog-entry-2773.html
> 37956641609621504 Mastering Grails: Grails in the enterprise
> https://www.ibm.com/developerworks/java/library/j-grails12168/ #grails
> 37956994061176832 NEW! FileNet - Java/J2EE Developer - Vigilant
> Technologies: ( #Columbus , OH) http://bit.ly/e6ULEw #OpenSource
> #Jobs #Job #TweetMyJOBS
> 37957325557989376 After a day of Java programming in Eclipse, C++
> programming in Visual Studio just feels slow and crappy :(
>
> more examples in the given file:
> https://github.com/karussell/TestTwitterAPI/blob/master/discrepancy.txt
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Opening sitestream with authorization only for some users issue
Neither the 'before' case nor the 'now' case is correct. You'll only receive the 400 if none of the users specified have authorized your application. You'll receive a friends list for each user who has authorized your application. You can tell those who haven't by the absence of the friends list. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Tue, Feb 15, 2011 at 11:52 AM, A.A.Novikov wrote: > Hi, a couple of days ago I've noticed that the implementation of a > undocumented edge case changed: > > Let's say there are users A,B,C; users A & B have authorized our > twitter app, user C either hadn't or removed authorization shortly > after. > > BEFORE if used to return an HTTP 400 (or 401) when ANY of the A,B,C > hadn't authorized the twitter app > > NOW, if there's at least 1 user who has authorized the service, the > sitestream api returns 200, and simply does not pass any messages > about the users who didn't authorize twitter app. > > Which leads to an issue that currently the users of the sitestream > can't know for which subset of requested follow set of users it was > actually valid & successful. > > Would it be possible to simply respond with a JSON one-liner > immediately, reporting users with mismatched authorization? > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Streaming API vs. Search API: no API returns >95% of intented tweets
On every occasion where I've tested the Firehose and track terms from the Streaming API against the Tweet database and against each other, there is no loss -- all the sources match exactly. Unless there's some unusual operational instability, the Streaming API returns 100% of the tweets requested, or sends a limit message to let you know what has been dropped. -John Kalucki http://twitter.com/jkalucki Twitter Inc. On Tue, Feb 15, 2011 at 12:50 PM, Karussell wrote: > Hi Colin, hi John, > > > To increase recall, search sometimes includes keywords in followed links > and other techniques. > > This is indeed the case. and 'twitter search' is a lot in urls ala: > > http://search.twitter.com/search?q=jetwick > > that is where the big differences came from. Can I turn off this > 'feature'? It shouldn't take into account that. Although the title of > the web site should taken into account ... like it is done in > jetwick ;) > > I'll investigate for other keywords now. > > > Typically your first poll will return 100 items then subsequent polls > > will return only "new" data if using since_id and/or dedupping. > > I already removed these early tweets, of course ... > > > I also ran some tests > > with which keywords do you ran the tests? > > > For testing purposes both my poller and stream reader only output IDs > > so I can use cat, sort, uniq, wc and diff to compare results. > > Yes, I went the same way :) > > Regards, > Peter. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Streaming API vs. Search API: no API returns >95% of intented tweets
If you examine set C, do they contain matches on fields other than the Tweet
text? To increase recall, search sometimes includes keywords in followed
links and other techniques.
Also, are you getting rate limit messages on the Streaming API?
-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.
On Tue, Feb 15, 2011 at 3:36 AM, Karussell wrote:
> Hi,
>
> this problem was already posted to the twitter4j mailing list [1]. Not
> sure if it is an issue with my code, twitter4j or an API issue... user
> reported similar problems in the past [2].
>
> First:
>
> I'm doing a 100 tweet search (without paging) every 5 minutes e.g.
> against 'twitter search'. I get a set of tweets A - excluding the
> duplicates, of course. I get approx 5 new tweets for every 5 minutes,
> so 100 tweets as pageSize should be perfectly sufficient to get all
> tweets.
>
> Second:
> When I'm doing a streaming filter request for the same terms 'twitter
> search' then I'm getting a set of tweets B.
>
> The problem is: combining A and B ('C=A v B') gives me a set C where
> the count of C is more than 10% larger then A or B, which means that
> neither with search nor streaming API I can catch a nearly complete
> set of tweets.
>
> E.g. doing this for 3 hours I'm getting 254 tweets (A) for the search
> and 257 tweets (B) for the streaming but the combined set C has 337
> tweets!
>
> Is this a bug in my code or could this be an API issue?
>
> BTW: I don't assume 100% correctness, I only want something above
> 90% :) especially for such relatively infrequent terms, where users
> can, should and have noticed it.
>
> Regards,
> Peter.
>
> [1]
> http://groups.google.com/group/twitter4j/msg/d959e6257ceb452f
>
> [2]
>
> http://groups.google.com/group/twitter-development-talk/browse_thread/thread/71ab5cc666113c9e
>
>
> http://blog.tweetsmarter.com/twitter-downtime/twitters-dirty-secret-they-dont-show-you-all-tweets/
>
> --
>
> http://jetwick.com Twitter Search without Noise
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Site Streams - Testing a new cluster
We're in the last stages of preparation and testing to move Site Streams to yet another cluster. If you are in the in the beta, and could point some test streams at 199.59.148.137 today, this would provide a nice final check before we start moving traffic over via DNS. If you have issues or success, please either DM @sitestreams, mention @sitestreams, or simply reply to this thread. Please keep all of your production streams on the DNS name sitestream.twitter.com. Thanks, -John Kalucki http://twitter.com/jkalucki Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Streaming API maintenance: brief delivery pause and an increased likelihood for duplicate tweets
Yesterday's maintenance resulted in about of 5 seconds of latency on Tweets, and about 10% of social events were delayed by about 10 minutes. No data was lost. We're going to perform another maintenance on social events now. You may experience duplicate social events for several seconds up to about two minutes. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Wed, Feb 9, 2011 at 1:15 PM, John Kalucki wrote: > We are performing a maintenance activity shortly that will increase the > likelihood of duplicate tweets and other messages on all Streaming APIs: > User Streams, Site Streams, and stream.twitter.com. There may also be a > brief pause in delivery. No tweets or other messages will be lost during > this maintenance event. > > The maintenance window is predicted to be approximately 2 minutes long and > may occur between 1:15pm PST / 21:15 UTC and 3:30pm PST / 23:15 UTC. > > Note that this possibility of duplications has always been documented on > the Streaming API at: > http://dev.twitter.com/pages/streaming_api_concepts#quality-of-service. > > -John Kalucki > Twitter, Inc. > http://twitter.com/jkalucki > > > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Streaming API maintenance: brief delivery pause and an increased likelihood for duplicate tweets
We are performing a maintenance activity shortly that will increase the likelihood of duplicate tweets and other messages on all Streaming APIs: User Streams, Site Streams, and stream.twitter.com. There may also be a brief pause in delivery. No tweets or other messages will be lost during this maintenance event. The maintenance window is predicted to be approximately 2 minutes long and may occur between 1:15pm PST / 21:15 UTC and 3:30pm PST / 23:15 UTC. Note that this possibility of duplications has always been documented on the Streaming API at: http://dev.twitter.com/pages/streaming_api_concepts#quality-of-service. -John Kalucki Twitter, Inc. http://twitter.com/jkalucki -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Site Streams Beta Users
Please refrain from large-scale restarts of Site Streams connections during the Super Bowl. Routine operations and the resulting connection churn is not a problem. Rather, starts and stops of a large number of connections is a bit stressful on our system, and we'd rather not disrupt other Site Streams clients during the event. We've made an of optimization in this area over the last week, and we hope to get that fix into production soon, but not before the game. If you can schedule stress testing and non-critical maintenance activities around the broadcast, this would be helpful. We don't expect any service interruptions, but we'd like to keep everyone's distractions to a minimum. Thank you, John Kalucki http://twitter.com/jkalucki Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: 401: Unauthorized (Python)
Matt,
The response is empty, that's what I'm curious about. I've included
the uri, headers, body and request variables below. This request was
performed at 2/5/2011 12:06.
Uri =
'https://twitter.com/oauth/request_token?
oauth_nonce=47248509&oauth_timestamp=1296925690&oauth_consumer_key=h3bOaVfTr8I7r2KQCzYCA&oauth_signature_method=HMAC-
SHA1&oauth_version=1.0&oauth_signature=9fpRZWGZls2kpfUQOZFnvPPTC9s%3D'
Request = {'oauth_nonce': '45640133', 'oauth_timestamp': '1296925356',
'oauth_consumer_key': 'h3bOaVfTr8I7r2KQCzYCA',
'oauth_signature_method': 'HMAC-SHA1', 'oauth_version': '1.0',
'oauth_token': 'Y0kKb5PhvjynbpKhfwF9na6ptznlkreKDheHo4YBmY',
'oauth_signature': 'zWwMR/v81XlzoeCpeYWHiMMIrPc='}
Body =
'oauth_nonce=45640133&oauth_timestamp=1296925356&oauth_consumer_key=h3bOaVfTr8I7r2KQCzYCA&oauth_signature_method=HMAC-
SHA1&oauth_version=1.0&oauth_token=Y0kKb5PhvjynbpKhfwF9na6ptznlkreKDheHo4YBmY&oauth_signature=zWwMR
%2Fv81XlzoeCpeYWHiMMIrPc%3D'
Headers = {'Content-Type': 'application/x-www-form-urlencoded'}
Thanks,
John
On Feb 4, 9:40 pm, Matt Harris wrote:
> Hi John,
>
> That dict object doesn't contain the response body. In the response body we
> give an error reason such as 'Invalid signature', or 'timestamp out of
> bounds'.
>
> Best,
> Matt
>
> On Feb 4, 2011, at 17:37, john wrote:
>
> > Hi Matt,
>
> > Thanks for responding. I've posted the response below (as a python
> > dict).
>
> > {'status': '401', 'content-length': '1', 'x-xss-protection': '1;
> > mode=block', 'x-transaction': 'Sat Feb 05 01:33:54 +
> > 2011-76395-3097', 'set-cookie': 'k=74.128.37.77.1296869634703204;
> > path=/; expires=Sat, 12-Feb-11 01:33:54 GMT; domain=.twitter.com,
> > guest_id=129686963484327539; path=/; expires=Mon, 07 Mar 2011 01:33:54
> > GMT,
> > _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCBwzdPMtAToHaWQiJWY1OTdhNDQ2Yjg1YzIw
> > %250AYTVjMmEyNWUyMjM2ZTY1ZGY3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
> > %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--01f06bea7e9f7559080f47e3b046117c40c39212;
> > domain=.twitter.com; path=/', 'expires': 'Tue, 31 Mar 1981 05:00:00
> > GMT', 'vary': 'Accept-Encoding', 'x-runtime': '0.00533', 'server':
> > 'hi', 'x-revision': 'DEV', 'last-modified': 'Sat, 05 Feb 2011 01:33:54
> > GMT', 'connection': 'close', 'pragma': 'no-cache', 'cache-control':
> > 'no-cache, no-store, must-revalidate, pre-check=0, post-check=0',
> > 'date': 'Sat, 05 Feb 2011 01:33:54 GMT', 'x-frame-options':
> > 'SAMEORIGIN', 'content-type': 'text/html; charset=utf-8'}
>
> > From what I've read, Twitter's oauth responses lack the error handling
> > that one would like. Any idea where I should go from here? I found the
> > section of the library I'm using that creates the UTC timestamp, by
> > calling time.time(). I would think that Django's timezone property
> > would set the runtime timezone, however I have not checked that
> > specifically. Any ideas?
>
> > Thanks,
> > John
>
> > On Feb 4, 4:58 pm, Matt Harris wrote:
> >> Hi John,
>
> >> What is the does the body of the error response say? The message will tell
> >> you which part of the oauth request failed.
>
> >> Also be aware that oauth timestamps are in UTC seconds.
>
> >> Best,
> >> @themattharris
>
> >> On Feb 4, 2011, at 12:45, john wrote:
>
> >>> I have an application that contains a simple setup using the
> >>> oauthtwitter library found here.
>
> >>>http://code.google.com/p/oauth-python-twitter/
>
> >>> #Example code
> >>> twitter = app.extras.oauthtwitter.OAuthApi(CONSUMER_KEY,
> >>> CONSUMER_SECRET)
> >>> request_token = twitter.getRequestToken()
> >>> oauth_verifier = request.GET.get('oauth_verifier')
> >>> access_token = twitter.getAccessToken(request_token, oauth_verifier)
>
> >>> I'm failing at getting the access token. I have a verifier and am
> >>> passing that along, like the example in the oauth lib, however am
> >>> continuing to get (all day now) 401s. My system
[twitter-dev] Re: 401: Unauthorized (Python)
Hi Matt,
Thanks for responding. I've posted the response below (as a python
dict).
{'status': '401', 'content-length': '1', 'x-xss-protection': '1;
mode=block', 'x-transaction': 'Sat Feb 05 01:33:54 +
2011-76395-3097', 'set-cookie': 'k=74.128.37.77.1296869634703204;
path=/; expires=Sat, 12-Feb-11 01:33:54 GMT; domain=.twitter.com,
guest_id=129686963484327539; path=/; expires=Mon, 07 Mar 2011 01:33:54
GMT,
_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCBwzdPMtAToHaWQiJWY1OTdhNDQ2Yjg1YzIw
%250AYTVjMmEyNWUyMjM2ZTY1ZGY3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--01f06bea7e9f7559080f47e3b046117c40c39212;
domain=.twitter.com; path=/', 'expires': 'Tue, 31 Mar 1981 05:00:00
GMT', 'vary': 'Accept-Encoding', 'x-runtime': '0.00533', 'server':
'hi', 'x-revision': 'DEV', 'last-modified': 'Sat, 05 Feb 2011 01:33:54
GMT', 'connection': 'close', 'pragma': 'no-cache', 'cache-control':
'no-cache, no-store, must-revalidate, pre-check=0, post-check=0',
'date': 'Sat, 05 Feb 2011 01:33:54 GMT', 'x-frame-options':
'SAMEORIGIN', 'content-type': 'text/html; charset=utf-8'}
>From what I've read, Twitter's oauth responses lack the error handling
that one would like. Any idea where I should go from here? I found the
section of the library I'm using that creates the UTC timestamp, by
calling time.time(). I would think that Django's timezone property
would set the runtime timezone, however I have not checked that
specifically. Any ideas?
Thanks,
John
On Feb 4, 4:58 pm, Matt Harris wrote:
> Hi John,
>
> What is the does the body of the error response say? The message will tell
> you which part of the oauth request failed.
>
> Also be aware that oauth timestamps are in UTC seconds.
>
> Best,
> @themattharris
>
> On Feb 4, 2011, at 12:45, john wrote:
>
> > I have an application that contains a simple setup using the
> > oauthtwitter library found here.
>
> >http://code.google.com/p/oauth-python-twitter/
>
> > #Example code
> > twitter = app.extras.oauthtwitter.OAuthApi(CONSUMER_KEY,
> > CONSUMER_SECRET)
> > request_token = twitter.getRequestToken()
> > oauth_verifier = request.GET.get('oauth_verifier')
> > access_token = twitter.getAccessToken(request_token, oauth_verifier)
>
> > I'm failing at getting the access token. I have a verifier and am
> > passing that along, like the example in the oauth lib, however am
> > continuing to get (all day now) 401s. My system time is set correctly,
> > as this is in a Django project, and I'm setting it via TIME_ZONE =
> > 'America/Kentucky/Louisville' in my settings.py. Can anyone help?
>
> > Thanks,
> > John
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this
> > group:http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] 401: Unauthorized (Python)
I have an application that contains a simple setup using the
oauthtwitter library found here.
http://code.google.com/p/oauth-python-twitter/
#Example code
twitter = app.extras.oauthtwitter.OAuthApi(CONSUMER_KEY,
CONSUMER_SECRET)
request_token = twitter.getRequestToken()
oauth_verifier = request.GET.get('oauth_verifier')
access_token = twitter.getAccessToken(request_token, oauth_verifier)
I'm failing at getting the access token. I have a verifier and am
passing that along, like the example in the oauth lib, however am
continuing to get (all day now) 401s. My system time is set correctly,
as this is in a Django project, and I'm setting it via TIME_ZONE =
'America/Kentucky/Louisville' in my settings.py. Can anyone help?
Thanks,
John
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Tweet button fails to parse URL - query strings beginning with & rather than ?
On Fri, Jan 28, 2011 at 3:02 AM, JonM wrote: > The following URLs won't parse using the "tweet" button: > > "'url' parameter does not contain a valid URL." > > > http://www.pitchero.com/clubs/stockport/j/team-news-1249.html&news_id=247910 Well, that's not a valid URL. See the RFC. http://www.ietf.org/rfc/rfc1738.txt If you need a "&" right there, you'll have to encode it. > I expect this is because the string has an ampersand "&" rather than a > question mark "?" before the first GET variable. Yes. > Facebooks "share" and "like" functions both accept this formatting, as > do Google and Yahoo. My guess is that they are encoding the URL for you, and Twitter does not at this time. > Is there a reason Twitter's API does not? Is there any work around I > can use? Mainly security. We've seen people abusing the tweetbutton URLs in cross-site-scripting attempts and other forms of abuse. -j > Thanks > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] stream_socket_client with STREAM_CLIENT_ASYNC_CONNECT yields 401
The Phirehose library for PHP and the Twitter Streaming API is well tested
and widely used. I'd start by looking at their code.
-John
On Sun, Jan 16, 2011 at 12:18 PM, webjay wrote:
> I should probably ask in a Php group, but I'll try here first, in case it's
> Twitter related.
>
> When I connect with stream_socket_client('tcp://stream.twitter.com:443') I
> get a 401 unauthorized error immediately.
> If I use fopen('https://stream.twitter.com/1/statuses/sample.json') I get
> a connection.
>
> The reason I would like to use stream_socket_client is to be able to use
> STREAM_CLIENT_ASYNC_CONNECT.
>
> Is this not possible?
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Streaming Site API hogs at some stage
The approach that Tim mentions is a good backstop, but this covers for an operational situation at Twitter that almost never happens. If you are seeing this condition happen often, there's probably something else wrong somewhere. If it is on our end, I'd like to fix it, but chances are its on your end, as there are no other reports of this situation. Do you have NAT or a HTTP proxy, either in hardware or software, between your server and the internet? If so, it may be dropping sessions, leaving your session high and dry. -John On Sun, Jan 2, 2011 at 6:56 AM, Tim Haines wrote: > The best practices guide (or some doc) explains the streaming connections > have heartbeats every 60 seconds or so. You should listen for them. If you > don't hear one for 90 seconds, drop the connection and reconnect. > > > On Sun, Jan 2, 2011 at 7:48 PM, Artem Skvira wrote: > >> Hi all, >> >> I have a strange problem. >> >> After successful oAuth session is established and request to, say, >> http://betastream.twitter.com/2b/site.json is sent, I start receiving >> some data. >> >> New tweets flow in, notification of deleted messages occasionally show >> up, the usual. >> >> However, after some time the activity ceases. If I look at the TCP >> connection in the list of OS connections - it is still there - or at >> least netstat tells me so: >> >> sudo netstat -p | grep >> node >> >> tcp0 0 192-168-1-2..:34897 128.242.250.199:www >> ESTABLISHED 9008/node >> >> >> Do you have any idea why this might be happening? Could that possibly >> be twitter's fault? Can I somehow tell that connection became 'frozen' >> so I can re-start it? >> >> Thanks! >> Art >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Exposing IP addresses for legal threats
On Tue, Jan 4, 2011 at 6:39 AM, Felipe Knorr Kuhn wrote: > Hello everyone, > > Although this is probably not the best list to discuss this, perhaps you > guys have some experience to share. > > A friend of mine is being threated by a Twitter user via DMs and public > messages. > > He doesn't know the identity of the user and thought about tracking him via > the IP he uses to post to Twitter. > Have your friend report the user to our Trust and Safety team. With regards to private user data, such as IP addresses: Private information requires a subpoena or court order In accordance with our Privacy Policy <https://twitter.com/privacy> and Terms of Service <https://twitter.com/tos>, non-public information about Twitter users is not released unless we have received a subpoena, court order, or other valid legal process document. Some information we store is automatically collected, while other information is provided at the user’s discretion. Though we do store this information, it may not be accurate if the user has created a fake or anonymous profile. Twitter doesn’t require email verification or identity authentication. See here for reporting guidelines and our Abusive user policy http://support.twitter.com/articles/15794 -john -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Stream problems on 2010-12-17?
Are you tracking reconnections and HTTP error codes? Sounds like you may have been churning your connection and getting banned. -John Kalucki http://twitter.com/jkalucki Twitter Inc. On Sat, Dec 18, 2010 at 7:32 AM, Frank Sorro wrote: > Hi Twitter admins and developers, > I am developing a social media application which uses a follow stream > with track words. At about 21:00 on Dev 16 2010 (UTC), the tweet rate > rapidly dropped from about 2800 tweets per minute to about 700, > including none we are looking for. Since today (Dec 18th) at about > 5:15 UTC, the rate is continuously rising again. This is weird because > nothing was changed and we lost the tweets of almost two days. > I am quite certain my software didn't have a problem because it worked > properly for quite some time, and I didn't change anything during this > time. > Is it possible that the Twitter Stream API may behave this way? The > API status page does not report any problems, but maybe it does not > report this kind of problems because I did get Tweets, but not enough > and not the right ones seemingly. > It would be very good to hear something from Twitter admins or other > developers who had the same problem because my bosses are very angry > with me anyway right now. If it helps, I'll send more info by e-mail. > Thanks in advance and best regards, Frank > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] user stream best practices
Yes, our model does externalize some development and hosting costs onto clients. But, we tend to only externalize cost when issues would be far cheaper, in aggregate, to solve on the client, or would be intractable to solve on our end and might otherwise prevent the launch of the feature. We try to balance this cost externalization very carefully and with all due concern for everyone's time. Our resources are limited, and our reasoning may not always be immediately obvious, but we're trying to get you as much data as possible, as efficiently as possible for everyone. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Tue, Dec 14, 2010 at 2:07 PM, Isaiah Carew wrote: > > In other words, if I want to disambiguate the stream, I have to filter it > myself. Well, humph… > > Not impossible, just a pain in the butt. > > From an information organization standpoint, it seems odd: The REST API is > broken out into separate calls. The stream has everything glommed together. > > It would be no big deal if you only needed one or the other, but you have > to do backfill with the REST API, so you always need both. > > The REST API has hierarchy in the endpoints. The Stream API has hierarchy > in the schema. Why not make the hierarchies (at least roughly) the same? > You don't have to answer, I'm just mouthing off. I'll get back to work > writing a track-term to nspredicate converter. ;-) > > > isaiah > http://twitter.com/isaiah > > On Dec 13, 2010, at 9:30 AM, John Kalucki wrote: > > Roughly: > If the tweet is from a following, place it in the home timeline. > If the tweet refers to the user (to or from), or contains the @screenname > place it in mentions > If it's a message -> messages. > What remains is probably a track term. > > -John Kalucki > http://twitter.com/jkalucki > Twitter, Inc. > > > > > On Fri, Dec 10, 2010 at 5:58 PM, isaiah wrote: > >> >> Hi, >> >> I'm implementing user streams in my client and looking for some advice >> on best practices. My client supports viewing multiple timelines at >> the same time, so it's quite possible to, for example: view a saved >> search, the user's own home timeline, and another user's recent >> tweets. >> >> Of course, I'd love to implement these in user streams. My concern is >> that if each of these timelines were to open a separate stream >> simultaneously, then the user could easily cross over their limit of >> active streams. Another potential solution seems to be adding the >> search and the second user as tracking parameters to a single user >> stream. That works fine and the track parameter limitations seem to >> be similar to the limitations of the UI/UX of my app, so it seemed >> like a good fit. >> >> The challenge is that once track parameters are added to the stream I >> get a whole bunch of new statuses returned but i can't tell which are >> associated with each parameter. Or, well, I couldn't figure out how >> to tell short of building a regex for each of my track parameters and >> trying to sort the items by hand (yuck!). >> >> So my question: >> 1. Is there some way to disambiguate statuses returned as a specific >> track parameter from those returned for other reasons? >> 2. Is there some other way to skin this cat that I'm missing? >> >> Thanks, >> Isaiah >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Usage of site streams in production projects.
We're not quite ready to move Site Streams out of beta. We have a few features to add, and we want to expand capacity somewhat to give a quicker, more consistent, login experience. We want to make as many risky changes as possible under beta, and then move much more carefully in full production. Other than a lower threshold for restarting on our end, however, Site Streams is pretty close to production-ready. Once we're in production, we'll be somwhat more hesitant to do restarts. As it stands, we'll restart beta whenever we need to gather some important information. Historically tends to be once a week or so, with occasional bursts. I'd launch a production product on Site Streams, but I'd keep a very close eye on things, and be prepared to make changes very quickly. We won't offer long transition periods for required changes, and we assume that beta clients can be pretty nimble on changing your end. Also, keep your REST API fallback code well tested for the time being... -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Thu, Dec 16, 2010 at 1:32 PM, ||M|| wrote: > Hi, > > Maybe this question is asked before but I was unable to find it in the > post history. > > At the moment we are developing an application that needs to get the > timelines of many users in real time. The are many possibilities to > create this solution but I think twitters site stream API looks like > the perfect solution for our problem. We can setup one or maybe a few > connections that enables us to get this information much easier than > when using the user stream API. > > I played around with it for the last couple of weeks and I very > enthusiastic about it to use in our current project. I wondering if it > is advisable to use twitters site stream API for production > applications because this is in BETA at this moment. > > Is there some kind of road map available for the site stream API? It > will take at least a couple of months before we will release the first > version of the application so the BETA it's not a problem at this > moment but if there's no indication of when the BETA period will end > and the site streams will go into production is it than available to > use it our to still use the user stream as alternative. > > I hope someone can help me with this? > > Kind Regards, > > Melvin > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Sporadic 401s?
We have a user database lookup capacity issue that is most acute on Site Streams. This is compounded by a bug that causes Hosebird to cache a timed-out database lookup as a negative authentication entry, and then your account can't log in on that one server for the cache duration. Generally if you try again, you'll hit another server and everything will be fine. This strikes randomly, but, very rarely. Earlier this week we spent a lot of time adding about ten times the database capacity and also fixing this awful bug, but there were a few minor problems along the way, leading to several redeploys and restarts that you may have experienced. Eventually, we ran out of time for the deploy. We'll just mumble through the next week as things are and avoid restarts on our end. If we don't restart, and your client doesn't do a full restart, you should have good Site Streams connectivity through the holidays, and we'll get this out in the New Year. There are a number of minor goodies queued behind this deploy. We'll get there. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Fri, Dec 17, 2010 at 10:54 AM, David wrote: > I have been getting sporadic 401s interleaved with 200s while connected to > Site Streams. I'll either open up a connection and it'll return 401s for a > while, then eventually start returning normal responses, or vice versa. This > issue started cropping up yesterday after the Site Stream restarts. Other > users in the IRC channel seem to be reporting 401s across other endpoints > somewhat sporadically as well. Is this a known issue? Any help would be > greatly appreciated! > > Best, > David > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Site stream unfollow event
We'd like to help developers maintain a local copy of their authorized users' followings -- the accounts that their users follow. We hope to enable a feature that will make this easier in early 2011. We're not particularly interested in helping developers maintain the set of an account's followers. There are awful scaling issues involved here, vectors for spammy behavior, and generally not much value for end-users in providing this data. Twitter is mostly about who you follow and what you are interested in. Who is following you is becoming less and less relevant. -John Kalucki http://twitter.com/jkalucki Twitter Inc. On Fri, Dec 17, 2010 at 8:15 PM, Shane wrote: > We currently need to maintain accurate follower lists for our Twitter > connected users. Using the site streams, we are able to easily add new > followers with the follow event. However, I have not found a clean, > efficient method of determine who has unfollowed a user. Currently, > unless I'm missing something, I have to retrieve all of the user's > follower IDs and compare them to what we have in our database. While > this is fine for a user with only a couple thousand followers, it gets > ugly in a hurry with when you have several users that have 50k+ > followers. > > Is it possible to have the unfollow events sent in the streams? At > least in our case, it would cut down the amount of API requests and > bandwidth consumed significantly. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Different crossdomains for a0.twimg.com & a2.twimg.com, a3 etc
a0 through a4 should offer identical crossdomain.xml files. They are all going through a CDN, so it might be the case that the CDN endpoint you are hitting has a stale file. I just checked all of the CDN endpoints from here and they are returning the same data. Try again? -john On Wed, Dec 15, 2010 at 5:20 PM, WildFoxMedia wrote: > Im currently seeing the same issue, however, in completely reverse. > > As of this moment, a0 & a1 are not allowing other domains and a2 & a3 > are allowing all domains. > > The other day, all 4 were not allowing other domains. > > Is there any reason or rhyme for this and more importantly, what is > the expectation? Are we supposed to be able to make calls from Flash > for profile images or not? > > On Nov 28, 3:57 pm, stephen wrote: > > Hey, > > > > It appears the crossdomains for a2, a3, etc are different and are > > preventing flash from accessing profile images on these domains. a0 > > and a1 are fine, however the api returns profile image urls using all > > of these domains (a0 - a?). > > > > Are the crossdomains suppose to be all the same or are we suppose to > > target only the first two? From the few that I've tested, it seems > > all profile images are accessible through the a0 or a1 domains despite > > what the api returns. > > > > Crossdomains > > > > > http://a0.twimg.com/crossdomain.xmlhttp://a1.twimg.com/crossdomain.xmlhttp://a2.twimg.com/crossdomain.xmlhttp://a3.twimg.com/crossdomain.xml > > > > Stephen > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] user stream best practices
Roughly: If the tweet is from a following, place it in the home timeline. If the tweet refers to the user (to or from), or contains the @screenname place it in mentions If it's a message -> messages. What remains is probably a track term. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Fri, Dec 10, 2010 at 5:58 PM, isaiah wrote: > > Hi, > > I'm implementing user streams in my client and looking for some advice > on best practices. My client supports viewing multiple timelines at > the same time, so it's quite possible to, for example: view a saved > search, the user's own home timeline, and another user's recent > tweets. > > Of course, I'd love to implement these in user streams. My concern is > that if each of these timelines were to open a separate stream > simultaneously, then the user could easily cross over their limit of > active streams. Another potential solution seems to be adding the > search and the second user as tracking parameters to a single user > stream. That works fine and the track parameter limitations seem to > be similar to the limitations of the UI/UX of my app, so it seemed > like a good fit. > > The challenge is that once track parameters are added to the stream I > get a whole bunch of new statuses returned but i can't tell which are > associated with each parameter. Or, well, I couldn't figure out how > to tell short of building a regex for each of my track parameters and > trying to sort the items by hand (yuck!). > > So my question: > 1. Is there some way to disambiguate statuses returned as a specific > track parameter from those returned for other reasons? > 2. Is there some other way to skin this cat that I'm missing? > > Thanks, > Isaiah > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] not getting unfollow and retweet event from User Stream
Yusuke, The documentation had an error. We don't send friendship deletions, even those that come from you. I fixed the documentation. I just tested retweets. I logged in, as myself, retweeted something, and the retweet (really, a tweet), and the subsequent deletion were syndicated properly. Can you reproduce this case? -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Wed, Dec 8, 2010 at 12:24 AM, Yusuke Yamamoto wrote: > Hi all, > > I'm not getting "unfollow" (from me) and "retweet" (from me) events from > User Stream now. > I suppose I used to be getting that sort of events as documented. > > -- >• Friendship Events >• Created - To you, from you > ... >• Retweet Events >• To you, from you. (Retweets from your followings are sent > as the actual home timeline retweet) > -- > from: http://dev.twitter.com/pages/user_streams > > > Is there any spec change that I'm missing? > > Thanks in advance, > -- > Yusuke Yamamoto > yus...@mac.com > > this email is: [x] bloggable/tweetable [ ] private > follow me on : http://twitter.com/yusukeyamamoto > subscribe me at : http://samuraism.jp/ > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] XML disabled on Streaming API
As previously announced, XML has been disabled on the Streaming API. The few remaining consumers should move to JSON, and bid the year 2003 adieu. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Streaming API firehose visibility
Yes, where firehose is the stream of all public statuses, with some low-quality accounts removed. On Wed, Dec 1, 2010 at 3:52 PM, dburkes wrote: > If I am using the statuses/filter streaming API, with a "track=" query > that is not overly broad, and my client never receives any "limit" > responses, can I assume that the results returned represent all the > results from the entire firehose? In other words, in the absence of > "limit" response, is my visibility into the firehose 100%? > > Thanks- > > Danny Burkes > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Best scalable method to process mentions
You should use Site Streams to gather mentions for a large number of users, or User Streams to gather for a single user. Otherwise you will run into API rate limits and other issues. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Tue, Nov 30, 2010 at 4:09 AM, Serdar wrote: > I think I could not make myself clear! > > My app already processes new tweets in a scheduled manner, and stores > the results in a database accordingly (using this API method: > http://dev.twitter.com/doc/get/statuses/mentions). > > I don't get why would I use stream API and how it would help? > > On Nov 30, 4:04 am, fbparis wrote: > > I guess you should use the stream api to get mentions in real time. No > > need to process it directly, you could code a simple client connected > > to the stream api which record new mention in database, then launch > > your script time to time and get the mentions via the database rather > > than via the twitter api. > > > > On Nov 30, 1:25 am, Serdar wrote: > > > > > Hi I have just launched my first twitter application. Basically: > > > > > -People send a tweet that mentions @appName (authorizing not needed) > > > -App checks for new @appName mentions *from time to time*, and process > > > them. > > > > > There is a max mentions limit (200) that can be retrieved at a time > > > via API. I know I'm not hitting this limit soon with the app but I > > > want to code a scalable method fo get mentions. > > > > > Unfortunaltely we do not have the option to get mentions in the > > > 'oldest first' order. > > > > > This causes a little tricky code for getting mentions in chunks and > > > not missing older tweets. (Suppose you had 200+ mentions since last > > > check). > > > > > For testing I limit, 'max mentions to get at a time' to 10, in my code > > > and it seems to be working. > > > > > I won't go into more details... > > > > > -I would like to know if any of you have coded something similar? > > > > > -Would love to see an alternative, as I'm not happy with my code! > > > > > -Is there an API method I could use for this purpose, which would make > > > things easier? > > > > > Thanks, > > > Serdar. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] filter.json per user connection limit
You should open just one connection from your site and multiplex all your track-compatable keyword search requests over that single connection. The docs describe how to change the predicates based on user demand without data loss or tripping up the connection rate limit. Users are slowly being trained not to enter their credentials into other websites, and once basic auth is turned off on the Streaming API, this option will be precluded. -John Kalucki http://twitter.com/jkalucki Twitter Inc On Sat, Nov 20, 2010 at 9:57 AM, Jason Newell wrote: > The docs recommended I contact Twitter about something like this, so > here goes. > > I'm working on a personal project the goal of which is to provide a > variety of different views of results for user input search terms, > using the Twitter streaming API, specifically filter.json. From what > I've seen it looks like connections are limited to one per user. > > It seems like I've got to force a user visiting my site to either > input their Twitter username and password, or log in to Twitter > through my site and get an OAuth token. The total impact on Twitter's > servers would be the same if I could just make the connections using a > single unchanging piece of authorization information. (well, nearly > the same, some users who would have left might stay instead) I would > like to do this. > > Am I mistaken? Or is it easy to get limited special permissions like > this? If I can't get them now, would I have better luck when I've got > a functional, useful version of the site? > > Thanks. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] User Streams count parameter
We never deployed this feature due to complexity in the privacy model. In retrospect, few REST calls would be saved by this approach, as most users disappear for longer than the count parameter would cover. We may revisit this in the future, once we can accurately model the potential savings. In the mean time, hit the REST API after a connection is established to do the backfill. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Mon, Nov 22, 2010 at 8:01 PM, Jonathon Hill wrote: > Per http://dev.twitter.com/pages/user_streams_suggestions: > > "If disconnected for just a few minutes, use the streaming count > parameter to backfill missing events. Note: count is currently > disabled May 22, 2010" > > Why was count disabled for User Streams, and is there any plan to make > it available once again? > > Thanks, > > Jonathon Hill > http://rainmakerapp.com > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Site Stream latency
This isn't how Site Streams should work. First, you should only open 25 connections per second. Second, have you calculated how much bandwidth is required to download all of the initial notifications and subsequent updates? I'd suspect insufficient bandwidth as the first cause of these kinds of symptoms. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Sun, Nov 14, 2010 at 12:13 PM, N wrote: > When my program makes hundreds of connections with Site Stream to > observe tens of thousands of users, the latency for every status > messages seems to start off like 10~30 minutes. It gradually gets > better and will be like 0~1 seconds within an hour or two, though. > > Is this expected behavior? > > Because this wouldn't be the case when it'd make much much fewer > connections, I'm guessing something must be wrong somewhere. The > traffic isn't any issue and my program can handle much more data > simultaneously. > > It appears to me that Site Stream server is taking too much time to > send out many "friend list" to clients. > > Any thoughts? > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Twitter + Gnip Partnership
Every search engine, social network, blogging platform, content aggregator, and to a certain extent, every used book store and used record store... -John On Wed, Nov 17, 2010 at 1:04 PM, Dewald Pretorius wrote: > As a business model, is there another company that takes content, > which its users create and enter into the company's service with no > compensation, and then turns around and sells that content to third > parties, still with no compensation to the creators of the content? > > I've been trying to think of another company that does this, but I'm > striking a blank. I'm sure there must be others. > > On Nov 17, 4:55 pm, Adam Green <140...@gmail.com> wrote: > > Ryan, I understand. I'm just happy to see you help companies put a > > real value on Twitter data in any form. And I'm happy to see Twitter > > find new ways to make money. You'll never hear "everything online must > > be free" from me. I go way back to when people paid for software, in > > a box, in stores. > > > > I'm also willing to bet that Twitter will eventually allow a paid > > market to develop in actual tweets as well as data derived from them. > > When Twitter IPOs, the market will demand that. Paying a third party > > to filter and rank tweets that can be displayed on a website seems > > perfectly legitimate. Why should every company have to pay to do their > > own API programming to display aggregated tweets, when they can pay > > someone for high quality tweets as a service? It seems illogical to > > me, and from the point of view of the tweet's author, the copyright > > issues are identical. > > > > > > > > On Wed, Nov 17, 2010 at 3:31 PM, Ryan Sarver > wrote: > > > Adam, it's a good question and it really comes down to what you are > > > trying to re-sell. > > > > > Re-syndication or re-sale of the actual tweets is strictly prohibited > > > and won't change on our end. We are however, ok with reselling of data > > > that results from analysis of the Twitter API. > > > > > So a great example is Klout. They do a lot of work to determine a > > > user's Klout score by analyzing the Twitter API and the content of > > > tweets. They *are* able to resell their score, but they would not be > > > able to resell the tweets that were used to determine that score. > > > > > It's nuanced, so let me know if that makes sense. > > > > > On Wed, Nov 17, 2010 at 12:55 PM, Adam Green <140...@gmail.com> wrote: > > >> Ryan: > > > > >> Shannon raises a lot of great points, but I'd like to hear more about > > >> the issue of reselling data derived from a purchased stream. Right now > > >> the TOS says that you can't resell data from the API. I've been > > >> telling clients that eventually Twitter will decide to make money from > > >> the API, and when that happens there would have to be a way to resell > > >> what has been paid for. Now that you are selling access to the API, > > >> which I strongly agree with, will you allow a free market to evolve > > >> around that by making it possible for Twitter data retailers to grow > > >> businesses, as well as wholesalers like Gnip? Please, say yes. I'm > > >> hoping an Apple-style, control the distribution channel completely > > >> mindset doesn't develop at Twitter. I'm hoping Twitter wants to help > > >> the developer ecosystem turn into a true third party market. Letting > > >> developers sell data or help clients sell data is essential for that. > > > > >> On Wed, Nov 17, 2010 at 1:27 PM, Shannon Clark < > shannon.cl...@gmail.com> wrote: > > >>> Looking at Gnip's website they have the "contact us for pricing" > links - > > >>> will Twitter & Gnip be making the pricing for the various levels > public? > > > > >>> Will companies that license the data be allowed to, in turn, sell > services > > >>> on top of that data - i.e. will this spark a new generation of > products such > > >>> as Scout Labs (now Lithium) or other analytics tools which are built > by > > >>> companies who have negotiated for full or partial firehose access but > which > > >>> are then used by clients of those companies each of whom will > configure > > >>> different queries and searches to monitor? > > > > >>> And on a more technical level will Gnip and Twitte
Re: [twitter-dev] @Anywhere communicate with PHP OAuth
On 18/11/10 8:21 AM, Abraham Williams wrote:
It still works for me. My two suggestions is to make sure you are
issuing a POST request to oauth/access_token and check that
oauth_bridge_code is getting passed correctly.
Definitely a post, and the bridge code seems to be correct as well.
I've tried a few variants in the way it is being sent as well to no avail.
You could use a tool like Charles Proxy to verify this information.
http://www.charlesproxy.com/
Might have to look into it.
Thanks for your help.
JB.
On Tue, Nov 16, 2010 at 20:57, John Barratt mailto:djo...@gmail.com>> wrote:
On 6/10/10 7:17 AM, Abraham Williams wrote:
The functionality is there just not officially supported.
http://blog.abrah.am/2010/09/using-twitter-anywhere-bridge-codes.html
I've had a go at implementing this with ruby & jnunemaker's twitter
gem (https://github.com/jnunemaker/twitter), but to no avail.
All other aspects of @anywhere access works fine for me, as does
getting access through OAuth for use via the REST API. Just can't
get the token & secret for use with OAuth via @anywhere.
Can anyone verify that this functionality does still work & is there
any timeframe for it to be officially supported?
Apart from the original slides by Matt & article by Abraham I can't
find any more information on it.
For reference I always get a 401, with the message "Failed to
validate oauth signature and token". FWIW my server time is fine,
and all other OAuth interactions are working fine.
I have tried many variants, but the basic code is :
token="ABC";secret="DEF";oauth_bridge_code="GHI"
oauth = Twitter::OAuth.new(token, secret, :sign_in => true)
access_token = oauth.request_token.get_access_token({},
:oauth_bridge_code => oauth_bridge_code)
It's at this point that it 401's.
I have verified that I am using valid token & secret, and what looks
like a valid bridge code is also obtained & used. But perhaps there
is something I am missing here?
Thanks,
JB.
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
Update: http://blog.abrah.am/2010/10/organizing-my-life.html
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Tue, Oct 5, 2010 at 12:39, Krileon mailto:krile...@gmail.com>
<mailto:krile...@gmail.com <mailto:krile...@gmail.com>>> wrote:
I've been reading that it is planned, but is it ever going
to happen?
Facebook does hits, Google Friend Connect does this
(subsequently
provides Twitter login as well through their API), so why can't
twitters own API? Just pass a authorized key and secret with the
cookie so we can through it through the OAuth request. This
is making
it an absolute nightmare to provide "single sign-on" for
Twitter users
as can be done with Facebook connect. 99% sites out there
can't only
superficially log users in with JS "prettiness". They need to be
stored inside the database so access permissions and what
have you may
function.
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates
Re: [twitter-dev] @Anywhere communicate with PHP OAuth
On 6/10/10 7:17 AM, Abraham Williams wrote:
The functionality is there just not officially supported.
http://blog.abrah.am/2010/09/using-twitter-anywhere-bridge-codes.html
I've had a go at implementing this with ruby & jnunemaker's twitter gem
(https://github.com/jnunemaker/twitter), but to no avail.
All other aspects of @anywhere access works fine for me, as does getting
access through OAuth for use via the REST API. Just can't get the
token & secret for use with OAuth via @anywhere.
Can anyone verify that this functionality does still work & is there any
timeframe for it to be officially supported?
Apart from the original slides by Matt & article by Abraham I can't find
any more information on it.
For reference I always get a 401, with the message "Failed to validate
oauth signature and token". FWIW my server time is fine, and all other
OAuth interactions are working fine.
I have tried many variants, but the basic code is :
token="ABC";secret="DEF";oauth_bridge_code="GHI"
oauth = Twitter::OAuth.new(token, secret, :sign_in => true)
access_token = oauth.request_token.get_access_token({},
:oauth_bridge_code => oauth_bridge_code)
It's at this point that it 401's.
I have verified that I am using valid token & secret, and what looks
like a valid bridge code is also obtained & used. But perhaps there is
something I am missing here?
Thanks,
JB.
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
Update: http://blog.abrah.am/2010/10/organizing-my-life.html
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Tue, Oct 5, 2010 at 12:39, Krileon mailto:krile...@gmail.com>> wrote:
I've been reading that it is planned, but is it ever going to happen?
Facebook does hits, Google Friend Connect does this (subsequently
provides Twitter login as well through their API), so why can't
twitters own API? Just pass a authorized key and secret with the
cookie so we can through it through the OAuth request. This is making
it an absolute nightmare to provide "single sign-on" for Twitter users
as can be done with Facebook connect. 99% sites out there can't only
superficially log users in with JS "prettiness". They need to be
stored inside the database so access permissions and what have you may
function.
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Receiving streaming API tweets without id_str
This should be fixed. Again. Please let us know if this recurs. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Sat, Nov 6, 2010 at 10:08 AM, Adam Green <140...@gmail.com> wrote: > My error logs started showing tweets without an id_str value a few > days ago. I investigated today and found that these tweets are coming > about 5-6 times an hour out of about 500 tweets per hour. I am using > Phirehose to gather these tweets from the streaming API. I am > collecting the tweets in JSON format. Neither my code or Phirehose has > changed in the recent past, and as I said, about 99% of the tweets are > fine. Here is an example of a bad tweet. It has a truncated field, > which I haven't seen before. I assume this has something to do with > the missing values. Does anyone have any idea what is happening here? > >[new_id_str] => 951769790156802 >[place] => >[truncated] => >[user] => stdClass Object >( >[follow_request_sent] => >[time_zone] => Jakarta >[url] => http://lada-hitam.livejournal.com/ >[profile_background_color] => B2DFDA >[screen_name] => MissLadaHitam >[profile_background_image_url] => > http://s.twimg.com/a/1288660386/images/themes/theme13/bg.gif >[profile_text_color] => 33 >[listed_count] => 0 >[lang] => en >[profile_background_tile] => >[statuses_count] => 891 >[following] => >[favourites_count] => 159 >[profile_link_color] => 93A644 >[show_all_inline_media] => >[profile_use_background_image] => 1 >[description] => >[contributors_enabled] => >[profile_sidebar_fill_color] => ff >[protected] => >[location] => Indonesia >[geo_enabled] => >[name] => Lada Hitam >[notifications] => >[friends_count] => 8 >[profile_sidebar_border_color] => ee >[id] => 117790534 >[verified] => >[utc_offset] => 25200 >[created_at] => Fri Feb 26 16:36:22 + 2010 >[followers_count] => 18 >[profile_image_url] => > http://a1.twimg.com/profile_images/740195225/42360__1__normal.jpg >) > >[in_reply_to_status_id] => >[favorited] => >[source] => web >[new_id] => 9.517697901568E+14 >[contributors] => >[in_reply_to_screen_name] => >[coordinates] => >[retweet_count] => >[in_reply_to_user_id] => >[entities] => stdClass Object >( >[user_mentions] => Array >( >) > >[hashtags] => Array >( >) > >[urls] => Array >( >) > >) > >[geo] => >[retweeted] => >[id] => 9.517697901568E+14 >[text] => Today's cookings mostly failed :( It makes me less > motivated to try another recipe tomorrow. But I have some mushrooms > that need to be used. >[created_at] => Sat Nov 06 16:44:54 + 2010 > ) > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Exception while using count parameter of streaming api
Shadow allows you to follow more users, but also allows you to continue to use track. There are no cases where we support count and track together. -John Kalucki http://twitter.com/jkalucki Twitter, Inc On Fri, Nov 5, 2010 at 9:41 AM, revati choudhari wrote: > Thanks for your reply. > Actually I have the Shadow access level, which means that I should be > able to use the count parameter. > Why do I still get the exception? :( > Also, I didnt understand what you mean by "endpoint"? Please explain. > > Does "Note that the count parameter is not allowed elsewhere, > including > track, sample" mean that I cannot use the count parameter with the > track parameter? The wording are a little confusing. > > Thanks, > Revati > > > On Nov 2, 11:02 am, Taylor Singletary > wrote: > > The count parameter is not available for all streaming roles/endpoints. > What > > end point are you executing and what level of streaming do you have > access > > to? > > > > From the docs on the count parameter: > > *Firehose, Links, Birddog and Shadow* clients interested in capturing all > > statuses should maintain a current estimate of the number of statuses > > received per second and note the time that the last status was received. > > Upon a reconnect, the client can then estimate the appropriate backlog to > > request. *Note that the count parameter is not allowed elsewhere*, > including > > track, sample and on the default access role. > > > > Taylor > > > > On Tue, Nov 2, 2010 at 10:14 AM, revati choudhari < > > > > > > > > revati.choudh...@gmail.com> wrote: > > > I am doing a project on twitter sentiment analysis, and I was trying > > > to pull previous statuses using the "count" parameter. Here is the > > > code: > > > > > inputConfig.Parameters = "track=" + FilterParametersTbx.Text + > > > "&count=10"; > > > > > I was granted the shadow access level by twitter yesterday, which > > > means I can use the "count" parameter. Why do I still get the > > > following exception? > > > > > System.Net.WebException was unhandled by user code > > > Message=The remote server returned an error: (416) Requested Range Not > > > Satisfiable. > > > Source=System > > > StackTrace: > > > at System.Net.HttpWebRequest.GetResponse() > > > at AdvantIQ.ExampleAdapters.Input.Twitter.TwitterInput.ProduceEvents() > > > in C:\Stream Insight Example\JAhlen - username\ExampleAdapters\Input > > > \Twitter\TwitterInput.cs:line 68 > > > at AdvantIQ.ExampleAdapters.Input.Twitter.TwitterInput.Start() in C: > > > \Stream Insight Example\JAhlen - username\ExampleAdapters\Input\Twitter > > > \TwitterInput.cs:line 45 > > > at Filter.InvokeWithFilter(Action , Func`2 , Action`1 ) > > > at > > > > > > Microsoft.ComplexEventProcessing.Diagnostics.Exceptions.ExecuteWithFilter(Action > > > body, Func`2 filter, Action`1 handler) > > > at > > > > Microsoft.ComplexEventProcessing.Adapters.Adapter.ThreadProcStart(Object > > > thisPtr) > > > InnerException: > > > > > If anyone has any idea about this, please help me out. > > > > > -- > > > Twitter developer documentation and resources: > http://dev.twitter.com/doc > > > API updates via Twitter:http://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >http://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >http://groups.google.com/group/twitter-development-talk- Hide quoted > text - > > > > - Show quoted text - > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Receiving streaming API tweets without id_str
We're looking into this issue. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Sat, Nov 6, 2010 at 10:08 AM, Adam Green <140...@gmail.com> wrote: > My error logs started showing tweets without an id_str value a few > days ago. I investigated today and found that these tweets are coming > about 5-6 times an hour out of about 500 tweets per hour. I am using > Phirehose to gather these tweets from the streaming API. I am > collecting the tweets in JSON format. Neither my code or Phirehose has > changed in the recent past, and as I said, about 99% of the tweets are > fine. Here is an example of a bad tweet. It has a truncated field, > which I haven't seen before. I assume this has something to do with > the missing values. Does anyone have any idea what is happening here? > >[new_id_str] => 951769790156802 >[place] => >[truncated] => >[user] => stdClass Object >( >[follow_request_sent] => >[time_zone] => Jakarta >[url] => http://lada-hitam.livejournal.com/ >[profile_background_color] => B2DFDA >[screen_name] => MissLadaHitam >[profile_background_image_url] => > http://s.twimg.com/a/1288660386/images/themes/theme13/bg.gif >[profile_text_color] => 33 >[listed_count] => 0 >[lang] => en >[profile_background_tile] => >[statuses_count] => 891 >[following] => >[favourites_count] => 159 >[profile_link_color] => 93A644 >[show_all_inline_media] => >[profile_use_background_image] => 1 >[description] => >[contributors_enabled] => >[profile_sidebar_fill_color] => ff >[protected] => >[location] => Indonesia >[geo_enabled] => >[name] => Lada Hitam >[notifications] => >[friends_count] => 8 >[profile_sidebar_border_color] => ee >[id] => 117790534 >[verified] => >[utc_offset] => 25200 >[created_at] => Fri Feb 26 16:36:22 + 2010 >[followers_count] => 18 >[profile_image_url] => > http://a1.twimg.com/profile_images/740195225/42360__1__normal.jpg >) > >[in_reply_to_status_id] => >[favorited] => >[source] => web >[new_id] => 9.517697901568E+14 >[contributors] => >[in_reply_to_screen_name] => >[coordinates] => >[retweet_count] => >[in_reply_to_user_id] => >[entities] => stdClass Object >( >[user_mentions] => Array >( >) > >[hashtags] => Array >( >) > >[urls] => Array >( >) > >) > >[geo] => >[retweeted] => >[id] => 9.517697901568E+14 >[text] => Today's cookings mostly failed :( It makes me less > motivated to try another recipe tomorrow. But I have some mushrooms > that need to be used. >[created_at] => Sat Nov 06 16:44:54 + 2010 > ) > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Removing new_id from Streaming on or after Monday November 15, 2010
The new_id field in Streaming is redundant now that we've completed the switch to the Snowflake status id generation scheme. We'll drop the new_id field from Streaming on or after Monday November 15, 2010. If you are dependent on the new_id field, switch back to the main status id as soon as is practical. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Duplicate tweets showing in the stream
I'm assuming that this is on Site Streams. It's very odd that the tweet ids and created_at timestamps are so very close together. Can you post the raw, unparsed JSON that you are receiving? Just one example would be sufficient to get started. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Thu, Nov 4, 2010 at 6:54 PM, Jayrox wrote: > Hello, > I am Jay the developer of tweelay.net /wavehello > > I am getting a bunch of tweets duplicated in my stream. I have > attached a small group of the tweets that were noticed by one of my > users. > I have noted which tweets you can actually pull up on twitter.com with > the "-real" notation and the ones noted as "-dupe" have a unique ID > but are unable to be pulled up on twitter.com > I am currently using phirehose (PHP) to consume my tweets from the > stream. > > Twitter_NameTwitter_UID Tweet_IDTweet_Str (truncated by > phpMyAdmin) Post_Date Post_Time > > scootinater 10167662322418165948420 I think I'll just lay right > here > and take a nap…he... 2010-11-04 19:04:05 -dupe > scootinater 10167662322418165948416 I think I'll just lay right > here > and take a nap…he... 2010-11-04 19:04:05 -real > scootinater 10167662340148264894460 "Mirror, mirror on the wall > who > is the cutest of t... 2010-11-04 20:14:32 -dupe > scootinater 10167662340148264894464 "Mirror, mirror on the wall > who > is the cutest of t... 2010-11-04 20:14:32 -real > scootinater 10167662339829959172100 And the doctor said "no > more > monkeys jumping on th... 2010-11-04 20:13:16 -dupe > scootinater 10167662339829959172096 And the doctor said "no > more > monkeys jumping on th... 2010-11-04 20:13:16 -real > scootinater 10167662349977012338690 @jayrox hey J! Have a > teensy > problem :) (don't you... 2010-11-04 20:53:35 -dupe > scootinater 10167662349977012338689 @jayrox hey J! Have a > teensy > problem :) (don't you... 2010-11-04 20:53:35 -real > scootinater 10167662352786432659460 @jayrox that is strange?? > 2010-11-04 21:04:45 -dupe > scootinater 10167662352786432659456 @jayrox that is strange?? > 2010-11-04 21:04:45 -real > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Basic question re Snowflake/K-sorted
This is good enough, as it's very unlikely that a tweet will be delivered
with an id less than your saved maximum id. If you want to be paranoid, you
can subtract a few seconds from the millisecond part of the id, but this is,
in practice, unlikely to ever happen.
-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.
On Thu, Nov 4, 2010 at 2:41 PM, @Joel_Hughes wrote:
> Hi all,
> many apologies if I'm asking a basic question here but I'm looking at
> this new Snowflake ID on the horizon...
>
> My usual logic for processing tweets is something like this:
> - find all tweets I'm interested in with status id > {stored max
> status id}
> - process those tweets
> - store the highest status id of processed tweets for next time round
> - (etc)
>
> ...this way I've got a a kinda sliding window for the processing
> tweets - I don't pull in tweets I know I've already processed (e.g. on
> my tweko.con app)
>
> From what I've seen of Snowflake the ids ARE sequential so the above
> logic should work?
>
> thanks for any thoughts guys - I've TRIED to get my head around k-
> sorted but, quite frankly, I'm not bright enough :)
>
> Joel
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] 10 minute warning: Snowflake status id jump in 10 minutes: 2:00pm PDT, 14:00 UTC
-- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Site Streams Beta now allows applications to stream all of their users.
The 100k user / 1k connection limit is no longer necessary and has been dropped. You may now connect for all of your tokens. Please limit your implementation to no more than 25 new connections per second. Follow @sitestreams for more information about this beta test. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] De-duplicating Site Streams
Create two in-memory hash sets of seen ids. Write ids to both. If the id is found on write, discard. Alternatively expire them every few tens of minutes to bound growth, but provide continuous coverage. -John On Tue, Oct 26, 2010 at 8:55 PM, Marc Mims wrote: > De-duplicating statuses in the Streaming API is fairly straightforward. > But with Site Streams, where a single status might be received multiple > times for multiple mentioned users, and/or as favorites, it is a bit > more difficult. > > I'm wondering if anyone can offer advice on an efficient method for > de-duplicating Site Streams. > >-Marc > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Rate limit for streaming api (tracking keyword)
http://dev.twitter.com/pages/streaming_api_concepts#filter-limiting http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses On Thu, Oct 28, 2010 at 9:55 PM, Thiago Esteves wrote: > Hi, > > I am developing an application that needs to track a keyword on > twitter, that keyword is a hashtag, the frequency of that keyword is > not high, but the application needs to stay listening and don't stop > never. What is the rate limit Twitter apply for this case? Could not > find it on twitter devel pages. > > Thanks > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Additional capacity added to stream.twitter.com and betastream.twitter.com clusters
We've completed an upgrade to the stream.twitter.com cluster this afternoon. Additional bandwidth and servers are now in production. This additional capacity should help throughput on certain distant high-volume clients during peak periods. Most other stream.twitter.com clients will not notice a difference in throughput. We also just moved the Site Streams beta onto a larger cluster. Demand has grown significantly over the last few days, and this move will provide headroom and improve stability. Information about the Site Streams beta is here: http://dev.twitter.com/pages/site_streams. The User Streams endpoint is unaffected by these changes. If your streaming client has outbound firewall rules, ignores DNS TTL, or otherwise aggressively caches DNS entries, you may wish to restart, as we're going to decommission at least one virtual ip address that we've retired from rotation. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] friends list in Site Stream
This amount of data is trivial compared to the total amount of data sent over Site Streams. The friends list per user is roughly the size of a tweet or two. We have to weigh the cost of maintaining the feature vs. the bandwidth and CPU savings. Unless the savings is significant, generally the optimal solution is to let the client discard unneeded data. -John On Tue, Oct 19, 2010 at 5:16 PM, N wrote: > Hi there, > > I've been playing with Site Stream for a bit, and I have a request. > > When a client connects to the server, it returns a series of the > friend list for each users. Can you make this optional? Receiving a > lot of friends data for thousands of users is a quite bit of trafic > and wasteful unless it's really needed. I'd be very happy if I > wouldn't have to receive it when I don't need. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] what does "K-sorted" mean?
K-sorted means roughly sorted, where no item is no more than K positions from it's totally ordered position. A sequence is k-sorted IFF, for all i,r, 1<= i <= r <= n, i<= r-k implies that a(i) <= a(r). The generation scheme has to allow sufficient IDs to be generated in a non-coordinated way to cover expected TPS well into the future. If you remove bits from the timestamp, you'll need to add those bits back in to the other fields, or you might starve for IDs. This scheme allows for 2^24 Ids to be generated per millisecond, but that 24 bit space must be sparse to allow for uncoordinated tweet generation. -John On Wed, Oct 20, 2010 at 7:13 AM, davidnicol wrote: > > the matt harris informs us: > 6) Why not restrict IDs to 53bits? > A Snowflake ID is composed: > * 41bits for millisecond precision time (69 years) > * 10bits for a configured machine identity (1024 machines) > * 12bits for a sequence number (4096 per machine) > The factor influencing the length of the ID is the time. For a 53bit > ID this > would mean only 31bits are available for the time. 31bits is only > enough for > 24 days (2147483648/(1000*60*60*24)) of time. > Reducing the resolution of the timestamp would prevent a K-sorted > resolution > of 1 second or less. > __END__ > > Why does the precision need to be 1000x the resolution? That makes no > sense to me. > The only references I can find for "K sorted" are concerned with > questions about "K sorted lists" where K is the number of different > lists. Sorting the streams from all thousand machines into one stream > you will have K=1024, sure, but if all those streams have millisecond > precision timestamps, the sorted output will have resolution of two > milliseconds. Half-second precision is sufficient to keep everything > in the right second bucket, possibly even whole-second precision. > > Or is "K sorted" something besides a mondegreen that happens to > include a letter? > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Twitter Button on sites.google.com
If the button code offered on the website is pasted into a Google hosted website, it generates the following error message: "Your HTML either contains unsafe tags (iframe, embed, styles, script) or extra attributes. They will be removed when the page is viewed." Can you advise a work-around? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: No of statuses extracted by statuses/filter
The only way to get limited is to specify a too broad predicate and go
beyond the allowed proportion of tweets. If you specify too many keywords,
you aren't limited, your connection is rejected. This is all documented on
http://dev.twitter.com/pages/streaming_api, specifically:
http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses
-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.
On Thu, Oct 14, 2010 at 12:29 PM, AA wrote:
> Thanks a lot!
> This is very helpful.
>
> John:
>
> You said:
> "If you don't receive a limit message, you know that you've received
> all
> possible tweets for the predicate"
>
> But:
> -The only way to get limited in status/filter is using more keywords
> or more users id than is allowed according to access level?
> Is there any other way?
>
> -The limit message contains some kind of sum info? (Additionnally,
> where can I find the "data spec" for this limit message and for data
> returned by status/filter in general?)
>
> Thanks in advance.
> Alejandro.
>
>
>
> On Oct 12, 7:17 pm, John Kalucki wrote:
> > Sorry. Gmail fail / Groups fail.
> >
> >
> >
> > On Tue, Oct 12, 2010 at 3:17 PM, John Kalucki wrote:
> > > If you don't receive a limit message, you know that you've received all
> > > possible tweets for the predicate. If you do receive a limit message,
> you
> > > know the precise proportion of tweets received and dropped.
> >
> > > -John Kalucki
> > >http://twitter.com/jkalucki
> > > Twitter Inc.
> >
> > > On Tue, Oct 12, 2010 at 2:36 PM, AA
> wrote:
> >
> > >> Hi everybody!
> > >> Thank you Edward.
> >
> > >> I copy paste part of your answer:
> >
> > >> ["If your filter criteria are sufficiently narrow, you get *all* of
> > >> the public tweets with those keywords sent by users who aren't being
> > >> blocked by Twitter's quality filter." At least that's what the
> > >> documentation has said in the past.]
> >
> > >> -Can anyone confirm this?
> > >> -I think, taking Edward's approach, I've still the same problem : even
> > >> taking a "very narrow" criteria I can never know what's the total, so
> > >> I can'´t know if all the tweets got by streaming are useful or not.
> > >> I think I have to remark that I don't need to know an exact total of
> > >> tweets in a given moment. What I'd like to know is an approximate
> > >> percentage over some approximate total of tweets estimation. I dare to
> > >> think it's part of the "service providing specification".
> >
> > >> I do understand that it can be difficult to exactly define "total of
> > >> tweets" when streaming and having tweets going into Twitter
> > >> permanently but not constantly, but some estimated info would be
> > >> great.
> >
> > >> Thank you all in advance.
> > >> Alejandro.
> >
> > >> On Oct 11, 5:57 pm, "M. Edward (Ed) Borasky" > >> research.net> wrote:
> > >> > Quoting AA :
> >
> > >> > > Hi everybody!
> > >> > > I'm designing an app to do some mining over a corpus of tweets.
> > >> > > I think I'll use streaming api, statuses/filter filtering by
> keywords.
> >
> > >> > > I'd like to know, before starting development, what is the
> percentage
> > >> > > of tweets delivered by this stream over the total tweets
> ('meaning
> > >> > > total tweets' the total of tweets that have the tracking keywords)
> .
> > >> > > This is information is crucial because of statistical confidence:
> a
> > >> > > very little sample may not be significant.
> >
> > >> > > Addittionally, Ive been googling and reading a lot for 3 days and
> I
> > >> > > can't figure out how i can use different 'level accesses'.
> > >> > > I've readhttp://
> > >> dev.twitter.com/pages/streaming_api_methods#statuses-filter
> > >> > > but how can I use this different levels levels of access?
> >
> > >> > > Thanks in advance!
> > >> > > Regards
> > >> > > Alejandro.
> >
> > >> > I actually think the answer to *yout* question is, "If your filter
> > >> > criter
Re: [twitter-dev] Stream API responds with 401 when multiple keywords are used
There's at least one OAuth library out there that doesn't encode the comma correctly. Search back in this group for details. -John Kalucki http://twitter.com/jkalucki Twitter Inc. On Thu, Oct 14, 2010 at 6:40 PM, Corey Wallis wrote: > Hi All, > > I have working code that uses OAuth to connect to the Stream API and > filter using keywords. When I supply a single keyword the API works as > expected and tweets are returned. What is odd is that when I specify > multiple keywords, or keywords that include a # symbol I get a 401 > UNAUTHORIZED error. > > Has anyone seen this before and come up with a successful resolution? > > I've captured the HTTP headers of both a successful and unsuccessful > call and I can't see anything that is different other than the list of > tracks contains multiple entries. Samples of the headers is below. > > This works: > > POST /1/statuses/filter.json HTTP/1.1 > Authorization: OAuth oauth_token="###", oauth_consumer_key="###", > oauth_version="1.0", oauth_signature_method="HMAC-SHA1", > oauth_timestamp="1287106462", oauth_nonce="-1686656262164231601", > oauth_signature="###" > Content-Length: 13 > Content-Type: application/x-www-form-urlencoded > Host: stream.twitter.com > Connection: Keep-Alive > User-Agent: Apache-HttpClient/4.0.1 (java 1.5) > Expect: 100-Continue > > HTTP/1.1 100 Continue > > track=twitter > > This does not: > > POST /1/statuses/filter.json HTTP/1.1 > Authorization: OAuth oauth_token="###", oauth_consumer_key="###", > oauth_version="1.0", oauth_signature_method="HMAC-SHA1", > oauth_timestamp="1287105193", oauth_nonce="-3374947181315671264", > oauth_signature="###" > Content-Length: 20 > Content-Type: application/x-www-form-urlencoded > Host: stream.twitter.com > Connection: Keep-Alive > User-Agent: Apache-HttpClient/4.0.1 (java 1.5) > Expect: 100-Continue > > HTTP/1.1 100 Continue > > track=twitter,lolcat > > Any thoughts would be gratefully received. > > With thanks. > > -Corey > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: No of statuses extracted by statuses/filter
Sorry. Gmail fail / Groups fail.
On Tue, Oct 12, 2010 at 3:17 PM, John Kalucki wrote:
> If you don't receive a limit message, you know that you've received all
> possible tweets for the predicate. If you do receive a limit message, you
> know the precise proportion of tweets received and dropped.
>
> -John Kalucki
> http://twitter.com/jkalucki
> Twitter Inc.
>
>
>
> On Tue, Oct 12, 2010 at 2:36 PM, AA wrote:
>
>> Hi everybody!
>> Thank you Edward.
>>
>> I copy paste part of your answer:
>>
>> ["If your filter criteria are sufficiently narrow, you get *all* of
>> the public tweets with those keywords sent by users who aren't being
>> blocked by Twitter's quality filter." At least that's what the
>> documentation has said in the past.]
>>
>> -Can anyone confirm this?
>> -I think, taking Edward's approach, I've still the same problem : even
>> taking a "very narrow" criteria I can never know what's the total, so
>> I can'´t know if all the tweets got by streaming are useful or not.
>> I think I have to remark that I don't need to know an exact total of
>> tweets in a given moment. What I'd like to know is an approximate
>> percentage over some approximate total of tweets estimation. I dare to
>> think it's part of the "service providing specification".
>>
>> I do understand that it can be difficult to exactly define "total of
>> tweets" when streaming and having tweets going into Twitter
>> permanently but not constantly, but some estimated info would be
>> great.
>>
>> Thank you all in advance.
>> Alejandro.
>>
>>
>> On Oct 11, 5:57 pm, "M. Edward (Ed) Borasky" > research.net> wrote:
>> > Quoting AA :
>> >
>> >
>> >
>> >
>> >
>> > > Hi everybody!
>> > > I'm designing an app to do some mining over a corpus of tweets.
>> > > I think I'll use streaming api, statuses/filter filtering by keywords.
>> >
>> > > I'd like to know, before starting development, what is the percentage
>> > > of tweets delivered by this stream over the total tweets ('meaning
>> > > total tweets' the total of tweets that have the tracking keywords) .
>> > > This is information is crucial because of statistical confidence: a
>> > > very little sample may not be significant.
>> >
>> > > Addittionally, Ive been googling and reading a lot for 3 days and I
>> > > can't figure out how i can use different 'level accesses'.
>> > > I've readhttp://
>> dev.twitter.com/pages/streaming_api_methods#statuses-filter
>> > > but how can I use this different levels levels of access?
>> >
>> > > Thanks in advance!
>> > > Regards
>> > > Alejandro.
>> >
>> > I actually think the answer to *yout* question is, "If your filter
>> > criteria are sufficiently narrow, you get *all* of the public tweets
>> > with those keywords sent by users who aren't being blocked by
>> > Twitter's quality filter." At least that's what the documentation has
>> > said in the past.
>> >
>> > But *my* question is, "How does one determine the total number of
>> > tweets, for some definition of total?
>> >
>> > a. All tweets created, including those that aren't public?
>> > b. All public tweets created, including those from "low quality users"
>> > that don't get indexed by search or sent to the "filter" stream?
>> > c. All tweets sent to the inlet of the filter stream and the various
>> > elevated access level stream?
>> >
>> > Remind me again - when does "Snowflake" go live? I haven't looked at
>> > Streaming data for a couple months.
>> >
>> > --
>> > M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://
>> twitter.com/znmeb
>> >
>> > "A mathematician is a device for turning coffee into theorems." - Paul
>> Erdos
>>
>> --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk
>>
>
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: No of statuses extracted by statuses/filter
If you don't receive a limit message, you know that you've received all
possible tweets for the predicate. If you do receive a limit message, you
know the precise proportion of tweets received and dropped.
-John Kalucki
http://twitter.com/jkalucki
Twitter Inc.
On Tue, Oct 12, 2010 at 2:36 PM, AA wrote:
> Hi everybody!
> Thank you Edward.
>
> I copy paste part of your answer:
>
> ["If your filter criteria are sufficiently narrow, you get *all* of
> the public tweets with those keywords sent by users who aren't being
> blocked by Twitter's quality filter." At least that's what the
> documentation has said in the past.]
>
> -Can anyone confirm this?
> -I think, taking Edward's approach, I've still the same problem : even
> taking a "very narrow" criteria I can never know what's the total, so
> I can'´t know if all the tweets got by streaming are useful or not.
> I think I have to remark that I don't need to know an exact total of
> tweets in a given moment. What I'd like to know is an approximate
> percentage over some approximate total of tweets estimation. I dare to
> think it's part of the "service providing specification".
>
> I do understand that it can be difficult to exactly define "total of
> tweets" when streaming and having tweets going into Twitter
> permanently but not constantly, but some estimated info would be
> great.
>
> Thank you all in advance.
> Alejandro.
>
>
> On Oct 11, 5:57 pm, "M. Edward (Ed) Borasky" research.net> wrote:
> > Quoting AA :
> >
> >
> >
> >
> >
> > > Hi everybody!
> > > I'm designing an app to do some mining over a corpus of tweets.
> > > I think I'll use streaming api, statuses/filter filtering by keywords.
> >
> > > I'd like to know, before starting development, what is the percentage
> > > of tweets delivered by this stream over the total tweets ('meaning
> > > total tweets' the total of tweets that have the tracking keywords) .
> > > This is information is crucial because of statistical confidence: a
> > > very little sample may not be significant.
> >
> > > Addittionally, Ive been googling and reading a lot for 3 days and I
> > > can't figure out how i can use different 'level accesses'.
> > > I've readhttp://
> dev.twitter.com/pages/streaming_api_methods#statuses-filter
> > > but how can I use this different levels levels of access?
> >
> > > Thanks in advance!
> > > Regards
> > > Alejandro.
> >
> > I actually think the answer to *yout* question is, "If your filter
> > criteria are sufficiently narrow, you get *all* of the public tweets
> > with those keywords sent by users who aren't being blocked by
> > Twitter's quality filter." At least that's what the documentation has
> > said in the past.
> >
> > But *my* question is, "How does one determine the total number of
> > tweets, for some definition of total?
> >
> > a. All tweets created, including those that aren't public?
> > b. All public tweets created, including those from "low quality users"
> > that don't get indexed by search or sent to the "filter" stream?
> > c. All tweets sent to the inlet of the filter stream and the various
> > elevated access level stream?
> >
> > Remind me again - when does "Snowflake" go live? I haven't looked at
> > Streaming data for a couple months.
> >
> > --
> > M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://
> twitter.com/znmeb
> >
> > "A mathematician is a device for turning coffee into theorems." - Paul
> Erdos
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Site Streams: Work Locally / 401 Unauthorized From EC2 (/cc @jkalucki)
I can see what you describe in the logs. The most likely problem is that the EC2-based client isn't signing the OAuth correctly somehow. There should be nothing on our end that allows you in on one IP, but 401s you on another. -John On Tue, Oct 12, 2010 at 1:28 PM, tsmango wrote: > I've been working on a site stream implementation for the past week or > so from my local environment without any issues. However, I just setup > a new EC2 instance this morning and I'm unable to connect from it (I > receive 401 Unauthorized). > > I've tried a few attempts over the course of several hours. I'm using > @frflyapp and I've tried both my development oauth app and my > production oauth app (both of which work locally) with the same > result. > > My last failed attempt was at: > > Tue Oct 12 20:08:17 + 2010 > > I received the following response: > > HTTP/1.1 401 Unauthorized > > WWW-Authenticate: Basic realm="Firehose" > > Cache-Control: must-revalidate,no-cache,no-store > > Content-Type: text/html; charset=iso-8859-1 > > Content-Length: 1286 > > Server: Jetty(6.1.25) > > My EC2 instance is at: > stream1.frf.ly > 174.129.10.194 > > With the default security group on EC2, I don't think it's possible to > ping the instance and I'm not sure if that's related or not. > > Thanks, in advance, for any help you can provide. > > -- > Thomas Mango > tsma...@gmail.com > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Streaming API sampling and filter limiting algorithms switched to new status id
The new status id format, previewed as new_id, requires slightly different algorithms for sampling and imposing filter limits on the Streaming API. In preparation for the big switch later today, we've cut over to using the new_id for these cases at about 6:30am PDT, 13:30 UTC. Only the most careful observer of the sampled streams should notice a difference. Consumers of the Streaming filter endpoint (track, loc, etc.) that aggressively push the rate limits may notice some minor differences in when the limits are imposed. We may tweak this algorithm and the associated Filter limits in the future. Overall, the results for Sample and Filter should be very similar to the previous sequentially generated status id system. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Is authentication required to use Streaming API?
Every account has default-level access. On Thu, Oct 7, 2010 at 10:26 AM, D. Smith wrote: > Can I use any Twitter account username/password or does the account > have to be registered with Twitter API? > > On Oct 7, 1:18 pm, John Kalucki wrote: >> stream.twitter.com/1/statuses/filter.json >> track=keyword1,keyword2 >> >> etc. >> >> -John >> >> >> >> On Thu, Oct 7, 2010 at 10:13 AM, D. Smith wrote: >> > I'm confused now. Which API should I use Streaming or Search? >> > What I want is to monitor Twitter and every time someone uses certain >> > words (maybe a total of about 20 words that I want to monitor >> > continuously), I want to show the tweet on the screen (or record it >> > into database) >> >> > Should I use search api or streaming api? >> >> > On Oct 7, 12:55 pm, Matthew Terenzio wrote: >> >> Yes, for the streaming api, >> >> >>http://dev.twitter.com/pages/streaming_api >> >> >> but it sounds like you may want the search api which doesn't require >> >> authentication: >> >> >>http://dev.twitter.com/doc/get/search >> >> >> On Thu, Oct 7, 2010 at 12:49 PM, D. Smith wrote: >> >> > Hello! I want to start using streaming API to monitor all tweets with >> >> > certain keywords in them. Do I need to provide any authentication in >> >> > order to connect? >> >> >> > -- >> >> > Twitter developer documentation and resources:http://dev.twitter.com/doc >> >> > API updates via Twitter:http://twitter.com/twitterapi >> >> > Issues/Enhancements Tracker: >> >> >http://code.google.com/p/twitter-api/issues/list >> >> > Change your membership to this group: >> >> >http://groups.google.com/group/twitter-development-talk >> >> > -- >> > Twitter developer documentation and resources:http://dev.twitter.com/doc >> > API updates via Twitter:http://twitter.com/twitterapi >> > Issues/Enhancements >> > Tracker:http://code.google.com/p/twitter-api/issues/list >> > Change your membership to this >> > group:http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Is authentication required to use Streaming API?
stream.twitter.com/1/statuses/filter.json track=keyword1,keyword2 etc. -John On Thu, Oct 7, 2010 at 10:13 AM, D. Smith wrote: > I'm confused now. Which API should I use Streaming or Search? > What I want is to monitor Twitter and every time someone uses certain > words (maybe a total of about 20 words that I want to monitor > continuously), I want to show the tweet on the screen (or record it > into database) > > Should I use search api or streaming api? > > On Oct 7, 12:55 pm, Matthew Terenzio wrote: >> Yes, for the streaming api, >> >> http://dev.twitter.com/pages/streaming_api >> >> but it sounds like you may want the search api which doesn't require >> authentication: >> >> http://dev.twitter.com/doc/get/search >> >> >> >> On Thu, Oct 7, 2010 at 12:49 PM, D. Smith wrote: >> > Hello! I want to start using streaming API to monitor all tweets with >> > certain keywords in them. Do I need to provide any authentication in >> > order to connect? >> >> > -- >> > Twitter developer documentation and resources:http://dev.twitter.com/doc >> > API updates via Twitter:http://twitter.com/twitterapi >> > Issues/Enhancements Tracker: >> >http://code.google.com/p/twitter-api/issues/list >> > Change your membership to this group: >> >http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Tweet button not working with a 'localhost' data-url?
There were recently some anti-XSS patches made to our code that might be blocking your use of "localhost". -j On Wed, Oct 6, 2010 at 1:29 PM, Olivier K wrote: > Hi, I'm currently testing the tweet button for our website. When I > test the button locally and want to share a link in the form of > 'http://localhost:8080/somepath/image.jpg' its says that the 'url' > param is invalid. But when I test it on a 'real' server (like > example.com) the button does work. > The data-url attribures are dynamically generated, which means if the > file was on 'example.com' instead of 'localhost' the link would be > 'http://example.com/somepath/image.jpg' > Can anyone confirm that share does not work with 'localhost' as data- > url? > > Thanks, > > Olivier. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: [SiteStreams] can't follow more than one user
It might be an OAuth encoding error with the ','. Which OAuth library are you using? -John On Wed, Oct 6, 2010 at 9:34 AM, Ruben Fonseca wrote: > Hi Thomas > > On Oct 6, 5:20 pm, Thomas Mango wrote: >> Hey, Ruben. That's the correct URL format. Are you sure your account was >> approved for Site Stream access? > > Yes it is, I filled all forms and received confirmation on monday. > Maybe I'm wrong, but the fact that it works with only one person to > follow proves that I have access to SiteStreams. > > Anyways my username is 'rubenfonseca' (no quotes). I'm using an OAuth > token from that user on my application. > > Thank you! > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Streaming API test: Adding new_id field to statuses at 17:00 UTC Sept 29
I dug back to Mark's email for context, but I still can't puzzle out what Mark was referring to and what you are asking for. The answer might be buried somewhere in that 74 message thread. Could you restate your question? Does the count parameter do what you need? -John Kalucki http://twitter.com/jkalucki Twitter, Inc On Sun, Oct 3, 2010 at 9:28 PM, Walter Santos wrote: > Hi, John > > Does Twitter still plan to implement backfill support in streaming > API? In an older post from > Mark McBride (April, 2010), he said: > > "To alleviate some of the concerns raised in this > thread we thought it would be useful to give more details about how we > plan > to generate IDs ... > ... 4) We will provide a way to backfill from the streaming API. ..." > > Thanks! > > On 28 set, 18:34, John Kalucki wrote: >> Tomorrow, Wednesday September 29, at 10:00 AM PDT / 17:00 UTC, we will >> briefly introduce a field called new_id to statuses delivered over >> theStreamingAPI. If this 10 minute test is successful, we will enable >> the new_id field continuously on Thursday September 30th at about the >> same time. Note that timelines returned by the REST and Search APIs >> will not contain this field. This new_id field will allow applications >> to preview thenewstatusidgeneration scheme before the primary key >> transition scheduled for Tuesday October 12th. >> >> For more information on our statusidtransition: >> >> http://groups.google.com/group/twitter-api-announce/browse_thread/thr...http://groups.google.com/group/twitter-api-announce/browse_thread/thr... >> >> -John Kaluckihttp://twitter.com/jkalucki >> Twitter, Inc. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] about Rate-limit
If you have 100k members to poll continuously, perhaps you should look into the Site Streams beta? -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Sun, Oct 3, 2010 at 4:47 PM, Emre GÜLCAN wrote: > Thanks Scott > > Emre GULCAN > Application Developer > > > > On Mon, Oct 4, 2010 at 1:15 AM, Scott Wilcox wrote: >> >> Each user gets 350 calls per hour via your application. >> On 3 Oct 2010, at 23:08, Emre GÜLCAN wrote: >> >> Hi everbody, >> I know this issue talked many times before different ways in this list. >> But I don't understand something about rate-limiting. >> As a portal developer, I'm using Twitter API to show our members' twitter >> home-timeline to our portal. oAuth rate-limit is 350, but we have 100.000+ >> members. >> As you can guess this is a big problem, in this state; Rate-limiting (350) >> is counting for our application or counting for authenticated user. >> For example application called X >> user A authenticated to X 10 times / per hour >> user B authenticated to X 50 times / per hour >> user C authenticated to X 100 times / per hour >> user D authenticated to X 75 times / per hour >> user E authenticated to X 5 times / per hour >> user F authenticated to X 50 times / per hour >> user G authenticated to X 60 times / per hour >> This count 350. So what about other users >> Or every member has own rate-limiting for this application X. >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Site Streams - Unfollow Events?
I just verified with curl and it worked fine. ? -John On Fri, Oct 1, 2010 at 2:02 PM, Tom van der Woerdt wrote: > I tried, but I didn't see anything. Adding a new user to one of my lists > didn't send anything, and removing didn't either. > > Haven't been able to test this outside my app, although I doubt that > it's my code (it simply outputs all incoming data to debug). Tried with > cURL but got an error about Basic Auth. > > Can anyone verify that there are no list events in the streams, or am I > simply going blind? > > Tom > > > On 10/1/10 10:57 PM, John Kalucki wrote: >> List modifications are streamed as social events. The lists themselves >> are not streamed. >> >> -John >> >> >> On Fri, Oct 1, 2010 at 11:01 AM, Tom van der Woerdt wrote: >>> Correct. >>> >>> I'd like to add an additional question to this thread: what about list >>> events? The docs say that they get sent, but they don't. >>> >>> http://dev.twitter.com/pages/user_streams >>> >>> Tom >>> >>> >>> On 10/1/10 7:46 PM, Justin wrote: >>>> It sounds like it's the same (NO) for both: >>>> >>>> Friendship Events >>>> Created - To you, from you >>>> Deleted - From you >>>> >>>> So, unfollow events from you not to you as the target. There doesn't >>>> seem to be any way to tell when someone stops following other than >>>> using the rest API to check followers and compare it to the list of >>>> following. >>>> >>>> Same with blocks: >>>> >>>> Created - From you (source) >>>> Deleted - From you (source) >>>> >>>> >>>> On Sep 30, 12:05 pm, "M. Edward (Ed) Borasky" >>> research.net> wrote: >>>>> Site Streams only or User Streams? I'm developing around User Streams. >>>>> -- >>>>> M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb >>>>> >>>>> "A mathematician is a device for turning coffee into theorems." - Paul >>>>> Erdos >>>>> >>>>> Quoting tsmango : >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> Hi, Ed. Block and unblock events are already being delivered in the >>>>>> Site Stream. Very useful! >>>>> >>>>>> On Sep 30, 12:30 pm, "M. Edward (Ed) Borasky" >>>>> research.net> wrote: >>>>>>> As long as we're wishing, I'd like to get a notification when someone >>>>>>> blocks me. ;-) >>>>>>> -- >>>>>>> M. Edward (Ed) >>>>>>> Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb >>>>> >>>>>>> "A mathematician is a device for turning coffee into theorems." - Paul >>>>>>> Erdos >>>>> >>>>>> - >>>>>> Thomas Mango >>>>>> @tsmango >>>>> >>>>>> -- >>>>>> Twitter developer documentation and resources:http://dev.twitter.com/doc >>>>>> API updates via Twitter:http://twitter.com/twitterapi >>>>>> Issues/Enhancements >>>>>> Tracker:http://code.google.com/p/twitter-api/issues/list >>>>>> Change your membership to this group: >>>>>> http://groups.google.com/group/twitter-development-talk >>>> >>> >>> -- >>> Twitter developer documentation and resources: http://dev.twitter.com/doc >>> API updates via Twitter: http://twitter.com/twitterapi >>> Issues/Enhancements Tracker: >>> http://code.google.com/p/twitter-api/issues/list >>> Change your membership to this group: >>> http://groups.google.com/group/twitter-development-talk >>> >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: How many user are using my app?
On 10/1/2010 2:04 PM, Justin wrote: There's probably a better way, but: http://search.twitter.com/search?q=a+source:hootsuite That gets any message coming out of hootsuite with "a" in it, limited by the reliability of the search data of course. Other than designing your software to report back to the mothership (and raising a lot of privacy issues as well), I don't think so. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Site Streams - Unfollow Events?
List modifications are streamed as social events. The lists themselves are not streamed. -John On Fri, Oct 1, 2010 at 11:01 AM, Tom van der Woerdt wrote: > Correct. > > I'd like to add an additional question to this thread: what about list > events? The docs say that they get sent, but they don't. > > http://dev.twitter.com/pages/user_streams > > Tom > > > On 10/1/10 7:46 PM, Justin wrote: >> It sounds like it's the same (NO) for both: >> >> Friendship Events >> Created - To you, from you >> Deleted - From you >> >> So, unfollow events from you not to you as the target. There doesn't >> seem to be any way to tell when someone stops following other than >> using the rest API to check followers and compare it to the list of >> following. >> >> Same with blocks: >> >> Created - From you (source) >> Deleted - From you (source) >> >> >> On Sep 30, 12:05 pm, "M. Edward (Ed) Borasky" > research.net> wrote: >>> Site Streams only or User Streams? I'm developing around User Streams. >>> -- >>> M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb >>> >>> "A mathematician is a device for turning coffee into theorems." - Paul Erdos >>> >>> Quoting tsmango : >>> >>> >>> >>> >>> >>> >>> >>>> Hi, Ed. Block and unblock events are already being delivered in the >>>> Site Stream. Very useful! >>> >>>> On Sep 30, 12:30 pm, "M. Edward (Ed) Borasky" >>> research.net> wrote: >>>>> As long as we're wishing, I'd like to get a notification when someone >>>>> blocks me. ;-) >>>>> -- >>>>> M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb >>> >>>>> "A mathematician is a device for turning coffee into theorems." - Paul >>>>> Erdos >>> >>>> - >>>> Thomas Mango >>>> @tsmango >>> >>>> -- >>>> Twitter developer documentation and resources:http://dev.twitter.com/doc >>>> API updates via Twitter:http://twitter.com/twitterapi >>>> Issues/Enhancements >>>> Tracker:http://code.google.com/p/twitter-api/issues/list >>>> Change your membership to this group: >>>> http://groups.google.com/group/twitter-development-talk >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Looking for Java class/package for Firehose
We have internal consumers here at Twitter that use Twitter4J to consume streams. Many of the data-driven features you see on Twitter.com, and many more that you can't see run on Twitter4J. -John On Thu, Sep 30, 2010 at 8:36 AM, D. Smith wrote: > I am looking for something specifically for Firehose. I must use > threads to pass the jobs to and i must have some mechanism to forking > and staying alive like a daemon or something like that, and ideally it > would automatically handle reconnecting in case of error. > > > > On Sep 30, 11:33 am, John Kalucki wrote: >> Twitter4J seems to be popular, but I don't have first-hand experience with >> it. >> >> -John >> >> >> >> On Thu, Sep 30, 2010 at 8:32 AM, D. Smith wrote: >> > Oh, man, I am new to Java, don't even know what Scala is... I've heard >> > about it that it's like based on Java and it's supposed to be easier >> > to code than in Java, but have not look at it, Will it even work in >> > Eclipse or will I need Eclipse plugin? Just don't feed like learning >> > yet another language just yet. >> >> > Is there are anything in pure Java? >> >> > On Sep 30, 11:28 am, Taylor Singletary >> > wrote: >> >> While it's in Scala, not Java, I've heard good things about >> >> @alejandrocrosa's Scala-TwitterStreamer >> >> :http://github.com/acrosa/Scala-TwitterStreamer--you should be able >> >> to make use of it fairly easily in a Java environment. >> >> >> We'd love to start collecting libraries built around the Streaming API. >> >> >> Regardless of language, does anyone have libraries to share with everyone? >> >> >> Taylor >> >> >> On Thu, Sep 30, 2010 at 8:25 AM, D. Smith wrote: >> >> > Hello there! >> >> > I am pretty experienced with using PHP for Twitter, but now I want to >> >> > use firehose and Java seems to be a much better fit because of >> >> > 'Threads', so I can listen to Firehose the pass a job to a thread and >> >> > return right away. PHP cannot do that, well, maybe to some crazy hacks >> >> > that I am not too impressed with. >> >> >> > Anyway, can someone recommend a good Java client that does that, >> >> > ideally where I can just extend the class to write my own runnable >> >> > classes. >> >> >> > thanks a lot. >> >> >> > -- >> >> > Twitter developer documentation and resources:http://dev.twitter.com/doc >> >> > API updates via Twitter:http://twitter.com/twitterapi >> >> > Issues/Enhancements >> >> > Tracker:http://code.google.com/p/twitter-api/issues/list >> >> > Change your membership to this >> >> > group:http://groups.google.com/group/twitter-development-talk >> >> > -- >> > Twitter developer documentation and resources:http://dev.twitter.com/doc >> > API updates via Twitter:http://twitter.com/twitterapi >> > Issues/Enhancements >> > Tracker:http://code.google.com/p/twitter-api/issues/list >> > Change your membership to this >> > group:http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Looking for Java class/package for Firehose
Twitter4J seems to be popular, but I don't have first-hand experience with it. -John On Thu, Sep 30, 2010 at 8:32 AM, D. Smith wrote: > Oh, man, I am new to Java, don't even know what Scala is... I've heard > about it that it's like based on Java and it's supposed to be easier > to code than in Java, but have not look at it, Will it even work in > Eclipse or will I need Eclipse plugin? Just don't feed like learning > yet another language just yet. > > Is there are anything in pure Java? > > On Sep 30, 11:28 am, Taylor Singletary > wrote: >> While it's in Scala, not Java, I've heard good things about >> @alejandrocrosa's Scala-TwitterStreamer >> :http://github.com/acrosa/Scala-TwitterStreamer-- you should be able >> to make use of it fairly easily in a Java environment. >> >> We'd love to start collecting libraries built around the Streaming API. >> >> Regardless of language, does anyone have libraries to share with everyone? >> >> Taylor >> >> >> >> On Thu, Sep 30, 2010 at 8:25 AM, D. Smith wrote: >> > Hello there! >> > I am pretty experienced with using PHP for Twitter, but now I want to >> > use firehose and Java seems to be a much better fit because of >> > 'Threads', so I can listen to Firehose the pass a job to a thread and >> > return right away. PHP cannot do that, well, maybe to some crazy hacks >> > that I am not too impressed with. >> >> > Anyway, can someone recommend a good Java client that does that, >> > ideally where I can just extend the class to write my own runnable >> > classes. >> >> > thanks a lot. >> >> > -- >> > Twitter developer documentation and resources:http://dev.twitter.com/doc >> > API updates via Twitter:http://twitter.com/twitterapi >> > Issues/Enhancements >> > Tracker:http://code.google.com/p/twitter-api/issues/list >> > Change your membership to this >> > group:http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] twitter streams API question
If the result set size per time period is below the rate limit, you get the full result set. Otherwise the part of the result set above the limit is discarded, and you get a notice to that effect. Note that with relevance enabled in search, it's not always full-fidelity result set either, especially for higher velocity predicates. See http://dev.twitter.com/pages/streaming_api_concepts#filter-limiting for more details` -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Thu, Sep 30, 2010 at 5:37 AM, Tom van der Woerdt wrote: > Filter = all, just like search. > > Tom > > > On Sep 30, 2010, at 2:24 PM, rakesh wrote: > >> Hi All - >> >> Could someone please answer this for me - >> >> If I use curl to execute the following - >> >> curl -d @locations http://stream.twitter.com/1/statuses/filter.json - >> uAnyTwitterUser:Password >> >> and my 'locations' parameter had a bounding box for 'dallas, tx' - >> would I then get ALL (exhaustively) tweets from the public timeline >> from Dallas with geocodes? >> >> Would this be a sample of tweets and not all of them? >> >> Could someone answer conclusively? >> >> Thx >> >> Rakesh >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Site Streams - Unfollow Events?
Thanks both for your responses. -John On Thu, Sep 30, 2010 at 6:12 AM, tsmango wrote: > Hey, John. There are a few reasons I'm interested in unfollow events > in Site Streams, but Tim got to the real point: "it would make it > extremely easy to keep the relationship info up to date". > > * My service shows you the latest tweet, matching specific criteria, > from each person you follow. Currently, unless I manually check the > REST API every so often, I wouldn't know to stop showing you a tweet > from someone you stopped following. With unfollow events in the Site > Stream, this would be trivial and wouldn't require me to run a > background process against the REST API. > > * I have a system in place to retrieve the relationship information > between two people using my service. This currently hits the REST API > to check whether or not you're following that requested person. I then > cache that relationship information to my database and expire it after > a certain amount of time. With only access to the REST API, there's > always a chance my cache is out of date. Site Streams already deliver > the full list of people being followed by each person the stream > follows in addition to new follow events. Unfortunately, this isn't > enough for me to stop using the REST API and expiring relationship > details from my cache. I could keep the cache semi-updated based on > new follow events, but I'd still need to expire that information and > fallback to the REST API after some time. If Site Streams delivered > unfollow events, there wouldn't be any need to fallback on the REST > API because I'd have the full list of people being followed when the > stream was opened and then each follow and unfollow event thereafter. > My local cache would always be up to date and I wouldn't need to hit > the REST API or expire any details locally. > > * Although I currently use a messaging type architecture for the main > part of my service, there are certain features I'd like to implement > that would require joining across a friendships table to find all > tweets, matching specific criteria, by everyone being followed by the > current user (I can't use my messaging tables because those only > contain information for you after you start using the service and > would prevent you from seeing any older tweets we already have > matching that criteria). Manually keeping a user's full social graph > synced up is wasteful and I've disabled the features in my site that > currently require it. However, if Site Streams delivered unfollow > events in addition to the list of people being followed by someone at > the start of a stream as well as new follow events after the stream > was open, keeping the user's social graph updated would be very > efficient. > > For me, getting unfollow events delivered in the Site Stream means I > would no longer have to hit the REST API for relationship details. > Everything would be up to date and nothing in my cache would have to > expire (unless a Site Stream was restarted, in which case I would > clear the currently cached relationship details for each user being > followed by that stream and set them up again). > > I hope this clarifies the different situations where I'd find unfollow > events useful. Thanks! > > On Sep 29, 11:42 pm, John Kalucki wrote: >> Please describe your use case for unfollows on Site Streams... >> >> -John Kaluckihttp://twitter.com/jkalucki >> Twitter, Inc. >> >> >> >> On Wed, Sep 29, 2010 at 5:09 PM, tsmango wrote: >> > Ah I wasn't able to find that. It's a shame if true. Thanks for the >> > information. >> >> > On Sep 29, 6:05 pm, Tim Haines wrote: >> >> Seen this answered about 1 - 2 weeks ago. Answer is no. >> >> >> On Thu, Sep 30, 2010 at 6:23 AM, tsmango wrote: >> >> > I was hoping for some clarification on the social events delivered to >> >> > a Site Stream. The documentation (http://dev.twitter.com/pages/ >> >> > site_streams) doesn't specifically mention unfollow events and I'm not >> >> > seeing them. I am seeing follow events, as expected. User Streams, >> >> > however, are said to support both follow and unfollow events. Are the >> >> > plans to add unfollow events to Site Streams? >> >> >> > Thanks, in advance! >> >> >> > - @tsmango >> >> >> > By the way, Home Timelines being delivered through Site Streams is >> >> > really incredible. I can't wait to get this stuff into my production >> >&
[twitter-dev] Desktop vs web apps
Can I use the same tokens that I generated with a desktop application for a web application, or vice versa? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Site Streams - Unfollow Events?
Please describe your use case for unfollows on Site Streams... -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Wed, Sep 29, 2010 at 5:09 PM, tsmango wrote: > Ah I wasn't able to find that. It's a shame if true. Thanks for the > information. > > On Sep 29, 6:05 pm, Tim Haines wrote: >> Seen this answered about 1 - 2 weeks ago. Answer is no. >> >> >> >> On Thu, Sep 30, 2010 at 6:23 AM, tsmango wrote: >> > I was hoping for some clarification on the social events delivered to >> > a Site Stream. The documentation (http://dev.twitter.com/pages/ >> > site_streams) doesn't specifically mention unfollow events and I'm not >> > seeing them. I am seeing follow events, as expected. User Streams, >> > however, are said to support both follow and unfollow events. Are the >> > plans to add unfollow events to Site Streams? >> >> > Thanks, in advance! >> >> > - @tsmango >> >> > By the way, Home Timelines being delivered through Site Streams is >> > really incredible. I can't wait to get this stuff into my production >> > environment. Thanks, again! >> >> > -- >> > Twitter developer documentation and resources:http://dev.twitter.com/doc >> > API updates via Twitter:http://twitter.com/twitterapi >> > Issues/Enhancements Tracker: >> >http://code.google.com/p/twitter-api/issues/list >> > Change your membership to this group: >> >http://groups.google.com/group/twitter-development-talk > > - @tsmango > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Streaming API new_id test
We streamed the new_id field for about 15 minutes this morning, starting at about 10:05 PDT, 17:05 UTC until about 10:15 / 17:15 UTC. If your streaming consumer had problems during this period: 1) Check your markup parser. 2) Respond to this thread. Barring any issues, we'll nail this setting up tomorrow at about the same time. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Steaming API — is track lagging considerably behind real–time right now?
The status blog will be updated shortly. -John On Wed, Sep 29, 2010 at 7:22 AM, Taylor Singletary wrote: > Hi Ben, > > The Streaming API is working through a backlog now after some earlier > issues. It should become more current soon. > > Taylor > > On Wed, Sep 29, 2010 at 6:03 AM, Ben Hodgson wrote: >> Hi, >> >> I’m having some trouble with the streaming API. Results for terms >> we’re tracking for Cursebird (http://cursebird.com/) are coming in >> about 40 minutes late right now. Currently every single line is also a >> duplicate. I’ve verified this both in production and on my local >> development machine. Are other people experiencing this? I would >> imagine it’s transient but it’s been like this for approximately 40 >> minutes. Is it just me, or is something broken at Twitter? >> >> Ben >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: User Streams goes Production, Site Streams adds Home Timelines
Followings is additive to the Users. You can observe the behavior of these settings on userstream.twitter.com. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Tue, Sep 28, 2010 at 9:10 PM, Michael Ledford wrote: > > On Sep 28, 3:04 pm, John Kalucki wrote: > >> Site Streams and User Streams now support the "with" parameter to >> control the delivery of home timelines. This parameter currently >> accepts two values: "users" or "followings". > > Is it possible to get both users and followings at the same time? It > seems as if you are saying if you don't provide the with parameter you > will get the 'users' option with the user stream by default. If not > are you allowed to open two user streams one for users and one for > followings? It doesn't seem like the API documentation is updated yet > and is the reason for this clarification. > > Sincerely, > Michael > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Streaming API test: Adding new_id field to statuses at 17:00 UTC Sept 29
Tomorrow, Wednesday September 29, at 10:00 AM PDT / 17:00 UTC, we will briefly introduce a field called new_id to statuses delivered over the Streaming API. If this 10 minute test is successful, we will enable the new_id field continuously on Thursday September 30th at about the same time. Note that timelines returned by the REST and Search APIs will not contain this field. This new_id field will allow applications to preview the new status id generation scheme before the primary key transition scheduled for Tuesday October 12th. For more information on our status id transition: http://groups.google.com/group/twitter-api-announce/browse_thread/thread/daf6298d0fdcbc87 http://groups.google.com/group/twitter-api-announce/browse_thread/thread/7982e3b037eeef95 -John Kalucki http://twitter.com/jkalucki Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: User Streams goes Production, Site Streams adds Home Timelines
Correction: The endpoint is https://userstream.twitter.com/2/user.json. User Streams is HTTPS only. On Tue, Sep 28, 2010 at 12:04 PM, John Kalucki wrote: > User Streams > = > > After an uneventful beta test period, the User Streams feature of the > Twitter Streaming API is now in regular production. As with all > production APIs, material changes will be pre-announced and > non-backward-compatible changes will be avoided. Developers may > release products against the production endpoint at > http://userstream.twitter.com/2/user.json. > > While User Streams is most useful for Desktop Clients, experimentation > in other use cases is encouraged. Note that service integrations, such > as websites and other server-based systems, must not open more than a > very small number of User Streams. Instead, services must use Site > Streams. Follow the product selection guide, > http://dev.twitter.com/pages/streaming_api#products to select the > correct product and avoid access interruptions. > > Access to User Streams on betastream.twitter.com is now unsupported, > and the beta test endpoints will be disabled in a few days. > > > Home Timelines > = > > Site Streams and User Streams now support the "with" parameter to > control the delivery of home timelines. This parameter currently > accepts two values: "users" or "followings". > > When set to "users", only messages targeted directly at a user will be > delivered: > > * Statuses created by the user > * @mentions and Direct Messages sent to the user > * Retweets and favorites of the user's statuses > * New followings by the user > * New followers of the user > * User's profile updates > > When set to "followings", the stream will also include: > > * Statuses and retweets created by any of the user's followings > * @mentions from any of the user's followings, subject to the setting > of the "replies" parameter > > Site Streams defaults to "users" while User Streams defaults to > "followings". These differing default values may be confusing, but > were chosen to retain backwards compatibility. We recommend that you > explicitly set this parameter to avoid confusion and future > compatibility problems as we refine this API. > > John Kalucki http://twitter.com/jkalucki > Mark McBride http://twitter.com/mccv > Cara Meverden http://twitter.com/caramev > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] User Streams goes Production, Site Streams adds Home Timelines
User Streams = After an uneventful beta test period, the User Streams feature of the Twitter Streaming API is now in regular production. As with all production APIs, material changes will be pre-announced and non-backward-compatible changes will be avoided. Developers may release products against the production endpoint at http://userstream.twitter.com/2/user.json. While User Streams is most useful for Desktop Clients, experimentation in other use cases is encouraged. Note that service integrations, such as websites and other server-based systems, must not open more than a very small number of User Streams. Instead, services must use Site Streams. Follow the product selection guide, http://dev.twitter.com/pages/streaming_api#products to select the correct product and avoid access interruptions. Access to User Streams on betastream.twitter.com is now unsupported, and the beta test endpoints will be disabled in a few days. Home Timelines = Site Streams and User Streams now support the "with" parameter to control the delivery of home timelines. This parameter currently accepts two values: "users" or "followings". When set to "users", only messages targeted directly at a user will be delivered: * Statuses created by the user * @mentions and Direct Messages sent to the user * Retweets and favorites of the user's statuses * New followings by the user * New followers of the user * User's profile updates When set to "followings", the stream will also include: * Statuses and retweets created by any of the user's followings * @mentions from any of the user's followings, subject to the setting of the "replies" parameter Site Streams defaults to "users" while User Streams defaults to "followings". These differing default values may be confusing, but were chosen to retain backwards compatibility. We recommend that you explicitly set this parameter to avoid confusion and future compatibility problems as we refine this API. John Kalucki http://twitter.com/jkalucki Mark McBride http://twitter.com/mccv Cara Meverden http://twitter.com/caramev -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty wrote: > @John thanks a lot. 2 things : > > 1. Requests are still timing out though at a lesser rate, I guess this > should die down in some time? > > 2. Can we prevent this from happening? I know apps from GAE end up > misusing the API and your algo blocks the IP. But, won't you be able > to whitelist the good apps? So that the next time there is an IP > block, the calls where a registered app sends requests, you can allow > it to go through? > > -Nischal > > On Sep 28, 10:49 am, John Adams wrote: > > We talked with GAE and have resolved this issue. > > > > -j > > > > On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty < > nischalshett...@gmail.com>wrote: > > > > > > > > > Hi John, > > > > > Just got news from appengine that it is being blocked. > > >http://twitter.com/app_engine/status/25743996553 > > > > > Can you please have a check? It must be the blocking issue, had one a > > > few months back for Appengine apps. Seems to work fine on my local dev > > > environment. > > > > > -N > > > > > On Sep 28, 6:49 am, John Adams wrote: > > > > We're not currently blocking google app engine; Could you pass along > some > > > > source IPs and we'll research? > > > > > > -john > > > > > > On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty < > > > nischalshett...@gmail.com>wrote: > > > > > > > My apphttp://www.justunfollow.comisnot able to connect to Twitter > > > > > from the Google Appengine. I had faced this problem a few months > ago > > > > > where you guys found out that the appengine IPs were being blocked > due > > > > > to some rogue app. > > > > > > > Please help, thousands of my users are getting timeout errors! > > > > > > > -- > > > > > Twitter developer documentation and resources: > > >http://dev.twitter.com/doc > > > > > API updates via Twitter:http://twitter.com/twitterapi > > > > > Issues/Enhancements Tracker: > > > > >http://code.google.com/p/twitter-api/issues/list > > > > > Change your membership to this group: > > > > >http://groups.google.com/group/twitter-development-talk > > > > > -- > > > Twitter developer documentation and resources: > http://dev.twitter.com/doc > > > API updates via Twitter:http://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >http://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty wrote: > Hi John, > > Just got news from appengine that it is being blocked. > http://twitter.com/app_engine/status/25743996553 > > Can you please have a check? It must be the blocking issue, had one a > few months back for Appengine apps. Seems to work fine on my local dev > environment. > > -N > > On Sep 28, 6:49 am, John Adams wrote: > > We're not currently blocking google app engine; Could you pass along some > > source IPs and we'll research? > > > > -john > > > > On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty < > nischalshett...@gmail.com>wrote: > > > > > > > > > My apphttp://www.justunfollow.comis not able to connect to Twitter > > > from the Google Appengine. I had faced this problem a few months ago > > > where you guys found out that the appengine IPs were being blocked due > > > to some rogue app. > > > > > Please help, thousands of my users are getting timeout errors! > > > > > -- > > > Twitter developer documentation and resources: > http://dev.twitter.com/doc > > > API updates via Twitter:http://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >http://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] not authorized over and over again
It sounds that, perhaps, you aren't recalculating the hash with the current timestamp. You can't re-use hashes. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Mon, Sep 27, 2010 at 3:39 PM, eMailaya wrote: > Im developing a desktop application. firstly, the user needs to > approve my app to let it access his account, enter the PIN code and > retrieve his statuses and his followees' statuses, all is working > fine. > > im closing my application and re-open it. now i already have his PIN > code so im skipping the authorization part. i put the oauth_key and > oauth_key_secret, the consumer_key and consumer_secret and ask for his > statuses, this one works but when i want to retrieve his followees > statuses i get "unauthorized" error. trying again causing the > "unauthorized" error also for his statuses. the only way to solve this > problem is to ask for an authorization everytime, this is annoying. > > also, i cant update the status for the same reason/error > any idea what am i missing? > thanks > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Not able to connect to twitter through Google Appengine, getting Timeouts
We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty wrote: > My app http://www.justunfollow.com is not able to connect to Twitter > from the Google Appengine. I had faced this problem a few months ago > where you guys found out that the appengine IPs were being blocked due > to some rogue app. > > Please help, thousands of my users are getting timeout errors! > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] xAuth problem with using filter streams
The reason text was enclosed. It says 403 - Administratively Forbidden.
You've been blacklisted, almost certainly for violating the API policy.
-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.
On Mon, Sep 27, 2010 at 6:06 AM, Tom van der Woerdt wrote:
> Hi,
>
> The 403 error can mean a lot of things. Can you give us the error
> message itself, instead of what Twitter4j gives you?
>
> Tom
>
>
> On Mon, 27 Sep 2010 19:03:58 +0900, Shinpei Ohtani
> wrote:
> > Hi all,
> >
> > I got xAuth problem using filter streams.
> > My simple code has been doing fine before September(just logging).
> > But there is something changed after sometime in September,
> > the same code is forbidden(403) by Twitter.
> >
> > I processed xAuth authentication at July,
> > and my code has been doing great with the authentication before
> September.
> >
> > I am using Twitter4j, and my code is authenticated by xAuth.
> > The error was like:
> > ===
> > TwitterException{exceptionCode=[6b837d58-1851a359], statusCode=403,
> > retryAfter=0, rateLimitStatus=null, version=2.1.4}
> > 6b837d58-1851a359
> > 403:The request is understood, but it has been refused. An
> > accompanying error message will explain why.
> > Administratively forbidden
> > ===
> >
> > So I have no idea what's going on.
> > Anybody has idea about this?
> >
> > Thanks,
> > Shinpei
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
