Re: [twitter-dev] Is there a standard PHP linkify routine?
I've never looked at entities but I turn URLs into links using this: $linkedtext = ereg_replace([[:alpha:]]+://[^[:space:]]+[[:alnum:]/],a href=\\\0\\\0/a, $tweet['statustext']); On Tue, Jul 12, 2011 at 10:30 AM, Adam Green 140...@gmail.com wrote: Every PHP app that displays tweets needs to apply the entities as links. Is there a standard function for this available, or are hundreds of thousands of developers each rolling their own? If you have a favorite code snippet, please point it out here. Maybe we can all review them and figure out which is best. I'me specially interested in solving UTF8 character problems, which cause invalid link positioning. -- 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] I found a good solution for PHP language detection in tweets
Hi Adam, Did you see this? I haven't tested it. Just was curious to look around after your post. http://stackoverflow.com/questions/1550950/detect-chinese-multibyte-character-in-the-string Matt Terenzio On Thu, Mar 24, 2011 at 10:50 AM, Adam Green 140...@gmail.com wrote: This has been a problem with collecting tweets from the API since I started working with it. My users only want English tweets and they view non-English tweets that I deliver to be a bug in my software. The lang=en argument in the search API only filters a small percentage of this, and I know of no way to do any filtering in the streaming API. I started working with the PHP library call LanguageDetect a few days ago, and it is doing a great job. http://pear.php.net/package/Text_LanguageDetect/ I tested it by filtering 40,000 recent tweets about @barackobama from my 2012twit.com site, and it found almost 20% of the tweets to be non- English. I screened the ones it found as non-English by hand, and found less than a 1% false positive rate. That means I lost 0.2% of the total flow to false positives to eliminate a 20% non-English rate. Pretty good for a solution that is small, about 2,500 lines of code, fast, open source, and free. I use it in my tweet parse phase of tweet collection. First I gather tweets into a MySQL cache with Phirehose, and then I parse the cached tweets into a normalized scheme. During this parsing phase I screen each tweet with LanguageDetect. The additional processing time of language detection is unnoticeable. The only limitation I found is that it doesn't detect Chinese or Japanese, but I think I can find other solutions for this. If anyone knows of a simple PHP detection algorithm for these languages, please let me know. - Adam Green Twitter API Developer http://2012twit.com http://140dev.com @140dev -- 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 + Gnip Partnership
We have every right in the world to gather this data for analysis without any permission. It's public. Redistributing it will be subject to fair use and copyright law but not gathering it and making broad analysis. That is what search engines do and so far the courts have said they have a right to cache copies on their own servers, not for public display necessarily, but in order to better analyze it. Oddly, the courts landed on the right side for once, saying that the greater good of the utility of search was a societal need and, in this case, more important than minor infringements, if any, on the site's copyrights. On Wed, Nov 17, 2010 at 12:18 PM, Ryan Sarver rsar...@twitter.com wrote: Companies have leveraged Twitter’s open API to analyze and report on conversations and sentiment across the network since its inception. These products have been indispensable in helping brands, marketers and businesses engage with their customers on Twitter. This is an area we want to support more fully, and today we are excited to announce a partnership with Gnip to develop and market data products specifically for these analysis and non-display companies. Gnip will sublicense access to our public Tweets to developers interested in analyzing large amounts of Twitter data. Over the past year we have spoken with many companies and entrepreneurs throughout the ecosystem who need easier access to more data. In particular, companies building analysis and non-display products have asked us for greater volume and coverage. Our partnership with Gnip is built to address this need. Gnip will focus exclusively on creating products to meet the existing and emerging demands of companies creating non-display products. Check out Gnip’s blog to learn more and to see details about their initial Twitter data products: http://blog.gnip.com/gnip-twitter-partnership/. Many of you may wonder what this means for elevated access and whitelisting requests. Our default levels like Spritzer, Follow and Track will not be changing, and will remain free and available directly from Twitter. Companies and developers are encouraged to begin development with these free APIs, available at http://dev.twitter.com/pages/streaming_api. This does affect companies wishing to create products which analyze Tweets and do not display Tweets to end-users. Moving forward, we will begin to encourage these companies needing elevated access for analysis and non-display products to work with Gnip to find the right data products for their commercial needs. We’re excited about this partnership, and the support it offers the data analysis and non-display market. You can learn more about the details and Gnip by visiting http://gnip.com/twitter. Please let me know if you have any questions about how this affects you and your products. To contact Gnip: web: http://gnip.com email: i...@gnip.com twitter: http://twitter.com/gnip Best, Ryan -- 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
I don't care what your newsletter says. I'm talking about American law. On Thu, Nov 18, 2010 at 11:28 PM, L. Mohan Arun mar...@gmail.com wrote: We have every right in the world to gather this data for analysis without any permission. It's public. No. You don't get to compile posts from a discussion forum into a product, under the idea that such posts are public domain. They are not. - Unless you own the forum or have a deal with the forum owner, and you stated in the TOS that all posts made in the forum can be repackaged commercially and only you have the right to do that. I am not saying this on my own, this is from one of the newsletters I receive, which covered this exact same topic, I would be happy to share the relevant text of the newsletter if someone is interested ... - - - Mohan Arun www.mohanarun.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] Re: Twitter + Gnip Partnership
Just to clarify. I never said they were Public Domain. Twitter or the user own the copyrights. Probably both. I meant it has been made public information, thereby granting some rights to those it was made public to. I wouldn't have a right to redistribute a book written by you, but I have every right to quote it in an article I write about you. More importantly, I can read 1000 books by 1000 different people and then write a paper that says 50% of the books written contained the word 'Obama' and and the average amount of times Obama was used in a book was 14. I wouldn't be breaking any laws. But who cares. In the future, if you want to access the Twitter data for such usage with any sort of speed you will pay to do so. It won't even be worth the headache if you can devise an alternative. On Thu, Nov 18, 2010 at 11:35 PM, Matthew Terenzio mteren...@gmail.comwrote: I don't care what your newsletter says. I'm talking about American law. On Thu, Nov 18, 2010 at 11:28 PM, L. Mohan Arun mar...@gmail.com wrote: We have every right in the world to gather this data for analysis without any permission. It's public. No. You don't get to compile posts from a discussion forum into a product, under the idea that such posts are public domain. They are not. - Unless you own the forum or have a deal with the forum owner, and you stated in the TOS that all posts made in the forum can be repackaged commercially and only you have the right to do that. I am not saying this on my own, this is from one of the newsletters I receive, which covered this exact same topic, I would be happy to share the relevant text of the newsletter if someone is interested ... - - - Mohan Arun www.mohanarun.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] Twitter + Gnip Partnership
Right. usage of the API is completely under Twitter control and TOS. I understand that. And yes, all of this is new and subject to litigation. Not worth the headache unless a rug was pulled out under and existing established business and agreement, which is probably only a few companies if any and I'm sure Twitter is working with them. On Fri, Nov 19, 2010 at 12:14 AM, Edward Hotchkiss edw...@edwardhotchkiss.com wrote: Well, they do have their ToS the law has so far placed in favor of usage of apps and apis regardless of ToS as long as it is legal. Yet, due to massive litigation. Best, -- Edward H. Hotchkiss http://www.edwardhotchkiss.com/ http://www.twitter.com/edwardhotchkiss/ -- On Nov 18, 2010, at 2:26 PM, Matthew Terenzio wrote: We have every right in the world to gather this data for analysis without any permission. It's public. Redistributing it will be subject to fair use and copyright law but not gathering it and making broad analysis. That is what search engines do and so far the courts have said they have a right to cache copies on their own servers, not for public display necessarily, but in order to better analyze it. Oddly, the courts landed on the right side for once, saying that the greater good of the utility of search was a societal need and, in this case, more important than minor infringements, if any, on the site's copyrights. On Wed, Nov 17, 2010 at 12:18 PM, Ryan Sarver rsar...@twitter.com wrote: Companies have leveraged Twitter’s open API to analyze and report on conversations and sentiment across the network since its inception. These products have been indispensable in helping brands, marketers and businesses engage with their customers on Twitter. This is an area we want to support more fully, and today we are excited to announce a partnership with Gnip to develop and market data products specifically for these analysis and non-display companies. Gnip will sublicense access to our public Tweets to developers interested in analyzing large amounts of Twitter data. Over the past year we have spoken with many companies and entrepreneurs throughout the ecosystem who need easier access to more data. In particular, companies building analysis and non-display products have asked us for greater volume and coverage. Our partnership with Gnip is built to address this need. Gnip will focus exclusively on creating products to meet the existing and emerging demands of companies creating non-display products. Check out Gnip’s blog to learn more and to see details about their initial Twitter data products: http://blog.gnip.com/gnip-twitter-partnership/. Many of you may wonder what this means for elevated access and whitelisting requests. Our default levels like Spritzer, Follow and Track will not be changing, and will remain free and available directly from Twitter. Companies and developers are encouraged to begin development with these free APIs, available at http://dev.twitter.com/pages/streaming_api. This does affect companies wishing to create products which analyze Tweets and do not display Tweets to end-users. Moving forward, we will begin to encourage these companies needing elevated access for analysis and non-display products to work with Gnip to find the right data products for their commercial needs. We’re excited about this partnership, and the support it offers the data analysis and non-display market. You can learn more about the details and Gnip by visiting http://gnip.com/twitter. Please let me know if you have any questions about how this affects you and your products. To contact Gnip: web: http://gnip.com email: i...@gnip.com twitter: http://twitter.com/gnip Best, Ryan -- 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
Re: [twitter-dev] Is authentication required to use Streaming API?
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 emai...@sharedlog.com 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
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- 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 Streaming API and use of OAuth from web browser
On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/dochttp://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk 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] User Streaming API and use of OAuth from web browser
So yes, I was correct (at least with search) that a web based solution is severely limited compared to a desktop. It will share usage among all it's users while a desktop client can spread the load amongst its users IPs. That stinks in my opinion. (I'm a web developer.) On Wed, Oct 6, 2010 at 7:44 PM, Matt Harris thematthar...@twitter.comwrote: All the information about rate limits can be found on our developer site: http://dev.twitter.com/pages/rate-limiting When talking about rate limits it is important to be clear about the API being used, as each has their own. For the REST API (requests to api.twitter.com) the limit is 150 requests per hour unauthenticated and 350 request per hour for an authenticated user. When you make an authenticated request the users rate limit is affected, not the IPs. The Search API has it's own rate limit based on the IP the request comes from. There is no authenticating for Search so all requests are IP rate limited. The Streaming APIs do not have rate limits in the same way. For the Streaming API the rate limit is controlled by the predicate limits (5,000 user ids etc) and the allowed sampling rate (1% etc). I hope that clarifies how the rate limits apply. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 3:28 PM, Matthew Terenzio mteren...@gmail.com wrote: On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- 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 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 Streaming API and use of OAuth from web browser
Fair enough. On Wed, Oct 6, 2010 at 8:39 PM, Matt Harris thematthar...@twitter.comwrote: Well remember with Search you don't need to proxy from your server - instead the Search API supports JSONP so you can run it directly from the website. Regarding Toms proxy comment. I think Tom was suggesting it for the userstreams functionality. As userstreams require a long poll connection there are various other obstacles to overcome if it were to be run from within the browser directly. In addition, userstreams are for single user use and not suitable for web applications where multiple users interact. Instead the something like the Site Streams service (currently in beta) could be better suited. On Wed, Oct 6, 2010 at 5:18 PM, Matthew Terenzio mteren...@gmail.com wrote: So yes, I was correct (at least with search) that a web based solution is severely limited compared to a desktop. It will share usage among all it's users while a desktop client can spread the load amongst its users IPs. That stinks in my opinion. (I'm a web developer.) On Wed, Oct 6, 2010 at 7:44 PM, Matt Harris thematthar...@twitter.com wrote: All the information about rate limits can be found on our developer site: http://dev.twitter.com/pages/rate-limiting When talking about rate limits it is important to be clear about the API being used, as each has their own. For the REST API (requests to api.twitter.com) the limit is 150 requests per hour unauthenticated and 350 request per hour for an authenticated user. When you make an authenticated request the users rate limit is affected, not the IPs. The Search API has it's own rate limit based on the IP the request comes from. There is no authenticating for Search so all requests are IP rate limited. The Streaming APIs do not have rate limits in the same way. For the Streaming API the rate limit is controlled by the predicate limits (5,000 user ids etc) and the allowed sampling rate (1% etc). I hope that clarifies how the rate limits apply. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 3:28 PM, Matthew Terenzio mteren...@gmail.com wrote: On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- 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 via Twitter: http://twitter.com/twitterapi
[twitter-dev] Search and/or streaming rate limits
If my app has 1000 users and each one wants to do a unique search once an hour it seems like that is beyond what is being suggested. Even if I use the streaming api and filters, it looks like I could only have a couple hundred users. ( Am I missing some technique because it doesn't seem like you can do anything useful with my use case if you are limited to a few hundred users. I've never found the rate limits a burden since you can spread the requests out among the users via OAuth, but the IP limits seem way too restrictive. Maybe I'm overlooking a creative workaround. Anyone? -- 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] List Statuses Page Limit
What is the per page limit of statuses returned on the: http://dev.twitter.com/doc/get/:user/lists/:id/statuses method? Also, if since_id is passed, how many will be returned in a page by default (if the amount returned is greater than the default)? Thanks, Matt -- 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?hl=en
Re: [twitter-dev] Re: Twitter-async now let's you view a sequence diagram of calls
++ I only recommend EpiTwitter to folks as a PHP library now, ++ It's solid. On Sat, Sep 4, 2010 at 6:15 PM, Scott Wilcox sc...@dor.ky wrote: Haha, that can only lead to a better experience for the end users. For what its worth, I only recommend EpiTwitter to folks as a PHP library now, and quite the volume of people at that! Shows you're doing something right! :) Scott. On 4 Sep 2010, at 23:10, jmathai wrote: Thanks Scott :). The same sweetness will be added to my fork of Twilio and Facebook's library as well :). I think my goal in life is to add asynchronous-ness to all php libraries :). On Sep 4, 1:31 pm, Scott Wilcox sc...@dor.ky wrote: That's a fantastic addition to an already great library. Great work! On 4 Sep 2010, at 21:22, jmathai wrote: The twitter-async library on github now lets you easily view a sequence diagram of calls. This is specifically useful when you're making multiple calls asynchronously. Here's a sample output (looks better with fixed width font). http://wiki.github.com/jmathai/twitter-async/#sequence (http://api.twitter.com/1/direct_messages.json:: code=200, start=1283577305.2462, end=1283577305.5109, total=0.264562) [] (http://api.twitter.com/1/users/suggestions.json:: code=200, start=1283577305.2726, end=1283577305.3871, total=0.114419) [ = ] (http://api.twitter.com/1/statuses/public_timeline.json:: code=200, start=1283577305.2731, end=1283577305.4195, total=0.146262) [ ] -- 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?hl=en
Re: [twitter-dev] Re: Tweeting from a CMS
Wheras formerly you must have supplied the Company's Twitter account username and password, you will now need to supply the OAuth credentials of the company account. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials If the case happens to be you were using third party code and you don't know how it works but just supplied the the username and password, then it is very possible that that code will no longer work. You will need to use a library that supports OAuth. There are many. On Fri, Aug 27, 2010 at 7:44 AM, stevew stevewhite...@gmail.com wrote: You mean *from* your company's account? With OAuth, you don't need username/password, because these are replaced by credentials. It's still very much possible. bah, I got shifted onto other projects and completely forgot about this... any ideas where I can find information about doing this? I am stuck Everything I have seen seems to rely on the user getting a token, and re-inputting that into the web app, but I can't seem to get to the satge of twitter offering me a token without being logged in :-( Basically to sum up, I want this :: a user loges into our CMS using their company credentials, they can tweet from/as the company account and all of the twitter stuff is hidden from them. -- 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?hl=en -- 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?hl=en
Re: [twitter-dev] getting 404 error when trying to subscribe to a list
Try screen_name instead of userid. I'm not certain but it rings a bell. Not that it shouldn't work with id, of course. On Tue, Aug 24, 2010 at 8:49 PM, bear bea...@gmail.com wrote: Using oAuth I am making the following call: POST /1/userid/3968155/subscribers.json where userid is the user whose oAuth tokens are in use and 3968155 is the id of the list i'm trying to subscribe to Twitter returns a stock 404 result I've even tried it with the slug id of the list, same result. I also know I have a valid oAuth environment because i'm getting the list information from a previous valid call to /1/userid/lists/ subscriptions.json and I always do /1/account/verify_credentials.json when i'm working on the library code. any clues? 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?hl=en -- 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?hl=en
Re: [twitter-dev] Is Twitter oAuth broken?
I'm getting problems on the return as well. On Mon, Jul 19, 2010 at 2:55 PM, nischalshetty nischalshett...@gmail.comwrote: My apps getting 'user has not given permission' and this is by the hundreds! I presume the oAuth API is having issues!
[twitter-dev] OAuth redirect
The redirect back to my site from the OAuth allow page always hangs. Clicking on the link results in sending the user back to the correct page. Trying to figure out how that could be on my end, but I can't see it. It fails 100% of the time, or so it seems.
Re: [twitter-dev] Re: disparities between bit.ly Google Analytics?
Google Analytics is javascript based which means a browser or some environment that can execute JS needs to open a page for a pageview There are many more HTTP requests for a given URL. Bots, spiders, aggregators etc. Since Bit.ly and other shorteners are doing 301 redirects, they can't really discern between the requests. Well, maybe they could with some well known agents, but it is not really feasible to detect every one out there. At least that probably accounts for much of the discrepancy.
Re: [twitter-dev] List ID
On Thu, Jan 21, 2010 at 1:00 PM, Lloyd England ll...@lloydengland.comwrote: Hi, quick question which I cannot find an answer for anywhere - how do you find the ID of a twitter list? http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-list-id Thanks!
Re: [twitter-dev] Re: OAuth DELETE LIST problem
There MAY also be an issue with how a DELETE request is formed. Try putting the parameters in the query string if you aren't. That seemed to make it work for me when it wasn't. On Tue, Dec 15, 2009 at 6:11 PM, Abraham Williams 4bra...@gmail.com wrote: The proper method is with DELETE and no _method=delete. For environments where you can only make GETs and POSTs you can add _method=delete as a work around. That being said I've had issues with random lists being frozen and not deletable. I've heard a number of other people mention the same issue. Abraham On Mon, Dec 14, 2009 at 09:37, volker volker.kr...@googlemail.com wrote: i think your base String should look like this: base: DELETEhttp%3A%2F%2Fstaging..com%2Fapi%2Fmodel%%2Fcontroller %2F2467oauth_consumer_key%thekey%26oauth_nonce %3D1429%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1260804448%26oauth_token%3Dtoken%26oauth_version%3D1.0 so you had to strip out _method=delete and send via POST but the basestring must start with DELETE maybe this helps Volker -- Abraham Williams | Awesome Lists | http://bit.ly/sprout608 Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] member_count lists issue
I SEEM to be getting a zero member count from a list where the only member is the owner of said list. Once I added another member to the list, the member count was 2. Anyone else notice this? Still trying to verify it's not on my end.
[twitter-dev] Show a specific list you can use the new resource
Can someone explain this? GET '/:users/lists/:list_slug.:format' Show a specific list you can use the new resource.
[twitter-dev] Re: Suggestion for User record
+1 On Sat, Oct 31, 2009 at 11:10 PM, Dave Winer dave.wi...@gmail.com wrote: It would be useful if a user had a lists_count element, in addition to the other counts (followers, statuses, favourites).
[twitter-dev] Re: Errornous link - Bracket problem with bit.ly
Yes, you need to ask twitter to fix that. They are using our api, but obviously, they are encoding the ) after the .jpg. Thanks for letting us know, but yes, this is a twitter issue. Good luck with that. Since it is acceptable to have the unencoded ) character in a URL, I don't know how they might interpret that it does not belong. They can make a good guess at best.
[twitter-dev] Re: Errornous link - Bracket problem with bit.ly
If in fact URL shortening is possible via the API, then there should at least be an option to suppress it. I have seen the API shorten URLs that I have already shortened which has caused problems but I never got an answer on what the rules were because I have also noticede some longer URLs slip by so there is an algorithm working there somewhere. Silence to the questions is the frustrating part. I guess I'm not big enough yet.
