[twitter-dev] Re: Looks like our application is DOA...
On Feb 12, 2:19 pm, Gummy Bear ser...@seductive.com wrote: There's simple workaround for that. Just think about it and you'll figure it out ;-) Yes, use email instead. I can't help thinking that all these devs up in arms because Twitter have limited use of their (free) service are making twitter apps just because it's the latest bandwagon to jump on, rather than because it's the most suited platform for the task in hand. I personally think Twitter should bin DMs altogether, it seems at odds with what Twitter is all about. Regards Tim -- 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: how to communicate with followers
On Feb 12, 1:15 am, Carlos Eduardo carlos@gmail.com wrote: I need a help, I'm developing an app for a client where it needs to communicate with his followers individually, each follower will receive a different link, the solution would be to have DM, but with a limit of 250 per day this becomes impossible, try sending mentions twitter but suspends the User, for thinking and spam, is there any way? thanks Eduardo Presumably these followers have opted-in to receive these DMs? In which case why not ask them to opt-in with their email address and send them an email instead? If they've not, then shame on you for adding to the spam pool. Regards Tim -- 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] Freedom's just another word for nothing left to lose
The behavior on this group has changed significantly since Ryan finally admitted that Whitelisting no longer exists. I've never seen anyone discuss methods of getting around TOS before, well there was Edward H., and we saw what happened to him. Now there are free flowing discussions of MTurk and other tricks to go way beyond the rate limits. I think this is great. Frankly, Twitter has done a good job of offering free resources to devs, which I thank them for, but there was way too much fear before. Now there are no extra benefits that can be given and withdrawn on a case by case basis. Boy do I hate that phrase. Of course, they can ban people from this list, but maybe the irony of Twitter blocking free speech on their own forum may restrain that urge in the future. Personally, I've treated Whitelisting like Social Security. It ain't going to be there when I need it. That has turned out to be a winning strategy. I don't really violate TOS, since I'm not as spammer, but I have never tried building anything that would fail if Twitter didn't give me Whitelisting after it got into production, which BTW was the most disrespectful thing I've seen from a platform vendor. Everyone should assume that you need to use what is there by default, and always be ready with a workaround if that gets taken away. My gut tells me that things will get worse before they get better. Twitter HQ will be under huge pressure to make money before the IPO, and we are likely to get some of the cuts. The inevitable they are parasites leeching off of us will surface. Anyone here old enough to remember Ed Esber? But in the long run, I've never seen a global phenomenon like Twitter, so I'm in it for the next 10 years at least. Then I can retire. Let's keep the discussion open guys. They've already taken away the most important thing you wanted. Now we can build with our eyes open. And don't be afraid to speak up. This is Twitter. Revolutions happen here. Adam Green Twitter API Consultant and Trainer 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
Re: [twitter-dev] Whitelisting is still in the docs. Please remove this.
Hi, It'll be nice to mention that in the following page as well: http://twitter.com/help/request_whitelisting There are many pages which link to the form. http://www.google.com/search?hl=ensafe=offclient=safarirls=enq=linkto%3Ahttp%3A%2F%2Ftwitter.com%2Fhelp%2Frequest_whitelistingaq=faqi=aql=oq= Best, -- 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/ On Feb 13, 2011, at 01:29 , Taylor Singletary wrote: Sorry Adam, missed this document among the many -- it's fixed now. The form itself and its text are immutable at the moment. On Sat, Feb 12, 2011 at 5:26 AM, Adam Green 140...@gmail.com wrote: http://dev.twitter.com/pages/rate-limiting#whitelisting Ryan, Taylor, Matt, I know changing mistakes in the docs has been impossible in the past. My guess is that someone lost the password for these pages. But leaving the whitelisting statement in the docs and the whitelisting form online is a sign of complete disrespect for your developers. New devs will see this and still think they can get whitelisting. Even worse they will waste their time building apps that need whitelisting, since the request form says: Whitelisting is only available to developers and to applications in production How would you feel if you started building an app today, spent months on it, got it into production, and then waited months for approval, since the docs say you won't get a response until approval is done? Not removing this shows that developers don't really matter to Twitter. Removing it right away shows that they do. Please don't say that you are too busy to make that change, and that it will be done some time in the future. Nobody is that busy. Please remove it. 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
Re: [twitter-dev] Twitter Development platform - A Rant
While , being philosophical about loss of whitelisting, the recent behaviour wsith regard to searches is not necessarily very postive for Twitter's public profile. Software history has shown that more than the individual product , it is the ecosystem, which determines the future of the product and the company. The current debate on Nokia and it's viability has been a prime-example of that. It is well-known that Java became popular despite efforts by various forces to discourage it's widespread usage . Now, Twitter and it's API groups claim that, they, are putting artificial limits of rates to ensure proper delivery for regular service. Someone has not studied the history of path-breaking products up there. If the method here is to discourage developers to invest in twitter to create applications, it is not the best idea. There is a lot of talk in market ccts that Twitter is looking at different ways to monetise it's huge userbase. Somehow, the recent actions leads us to believe , that, with that kind of focus you guys are losing track of what twitter can actually become. Twitter is already a successful product. It was a great idea which has changed the way people communicate with each other. Today, revolutions happen in twitter. With all these restrictive views and thought processes, one believes that, perhaps, It does not think like a startup anymore. Guys, your role model should be facebook. Even today, they think like startups. It was facebook's open development platform which was the driver to more users in it's 2nd phase of expansion. We in our company view twitter as much larger than micro-blogging product. We believe it can symbolise the next WWW. Our product lines are designed on that. We dont have whitelisting and we were not planning to apply for it. We were willing to work around the different restrictions and come up with innovative solutions. These restrictions have increased resource requirements for the product we're building, but out here, we're happy about it. They've got us people who have innovation which is essential to a successful startup. Somehow, the recent statements make me believe that twitter is losing it here. I come from the domain of server technologies. I completely understand that QoS (Quality of service) is a big issue. But, in times of peak load, twitter still does go down. By putting artificial limits on querying twitter, you're not allowing creation of the next generation of products. All these limits indirectly makes one believe that twitter does not want more users. That seems very contradictory for a company whose valuation of 8-10 Billion USD is a function of it's userbase. If I were given the charge of solving this problem i would add new servers . Our server requirement[dedicated] costs us about 140 USD permonth/perserver. It has been said that you guys use Cassandra. Given Cassandra's performance replication efficencies are fairly decent. A fleet of 10 servers should be enough to handle things for you guys for the near future. That will be less than what you guys pay a developer. I'm sure lots of users will be happy to pay for this too. Although, the real trick is to be free. The future is about being open. Facebook was a means of bringing your social experience online. But, there was a concept of exclusivity to it. Twitter was diametrically opposite. It allowed people to talk to anybody. Politically speaking, it was a very democratic experience. I would like to see twitter bigger than Google someday. Blocking development platforms is not the way to go. Regards Umashankar Das On Sun, Feb 13, 2011 at 6:16 PM, Adam Green 140...@gmail.com wrote: The behavior on this group has changed significantly since Ryan finally admitted that Whitelisting no longer exists. I've never seen anyone discuss methods of getting around TOS before, well there was Edward H., and we saw what happened to him. Now there are free flowing discussions of MTurk and other tricks to go way beyond the rate limits. I think this is great. Frankly, Twitter has done a good job of offering free resources to devs, which I thank them for, but there was way too much fear before. Now there are no extra benefits that can be given and withdrawn on a case by case basis. Boy do I hate that phrase. Of course, they can ban people from this list, but maybe the irony of Twitter blocking free speech on their own forum may restrain that urge in the future. Personally, I've treated Whitelisting like Social Security. It ain't going to be there when I need it. That has turned out to be a winning strategy. I don't really violate TOS, since I'm not as spammer, but I have never tried building anything that would fail if Twitter didn't give me Whitelisting after it got into production, which BTW was the most disrespectful thing I've seen from a platform vendor. Everyone should assume that you need to use what is there by default, and always be ready with a workaround if that gets
Re: [twitter-dev] Re: DM rate limit
Why not have each client register a notification account with your app that sends a DM to their main account. That gives every client 250 DMs. Better yet, make it a private account and push notifications as status updates giving you 1000/day while keeping privacy. Sent from my iPhone On Feb 12, 2011, at 5:17 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Sat, 12 Feb 2011 17:07:36 -0500, Trevor Dean trevord...@gmail.com wrote: I agree, don't be so quick to judge. We have an opt-in based service and out clients have thousands of customers that explicitly say yes send me direct messages. The information we send is requested by the end user and is not spam. So you can imagine that a client with a large user base could quickly go beyond the 250 dm/day limit. It's unfortunate that the spammers take advantage and ultimately ruin things for legitimate services. Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information Speaking of spam, there's a great article at the New York Times on J.C. Penney, black hat SEO and Google: http://www.nytimes.com/2011/02/13/business/13search.html Many thanks to Twitter's spam fighters for keeping it as clean as it is, under the circumstances. -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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: Confused
well i was trying to get commets without just retweeting From: L. Mohan Arun mar...@gmail.com To: Twitter Development Talk twitter-development-talk@googlegroups.com Sent: Sat, February 12, 2011 7:00:16 PM Subject: [twitter-dev] Re: Confused Can you tell us exactly what it is that you are looking for? This is the Twitter API development group where we discuss issues faced by developers. - Mohan -- 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] Widgets above Slimbox/lilghtbox
Twitter wigdets are displaying above lightbox gallery, here is example: http://i.imgur.com/QwYFE.jpg This is an old problem ( http://groups.google.com/group/twitter-development-talk/browse_thread/thread/79df37343715b2cb ) but I haven't find solution yet. -- 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] Search API the public alternative to URL count API?
Hi there, I am busy writing an aggregator and I am looking at using the Twitter API to get URL counts. I seems that public developers are not allowed to use the URL counting API based on the Tweet Button FAQ. Which leaves me with not other option but to use the search API for URL counting. Using the search API makes not sense if there a Count API. This leaves me with the following questions 1. Will my application / I.P. get banned if I use the Count API? 2. Is there a way to request multiple URLs at once to limit round- trips? 3. The URL count API returns not threshold information. So if I am allowed to use it, should I manage the thresholds myself FAQ - http://dev.twitter.com/pages/tweet_button_faq#count-api URL Count API - http://urls.api.twitter.com/1/urls/count.json?url=URL Search API - http://search.twitter.com/search.format My application aggregates URLs on a central server using a shared account so the request numbers may be quite high Martin -- 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: Looks like our application is DOA...
We already have email as an option (and SMS, and a variety of other methods) - we had been specifically asked by a couple of customers to use twitter as a notification feed and this development was in response to those requests. We actually do take customer requests in and listen to what they are asking, and see if it is something we can do for them. If we feel it is something that might be of use to more than one customer, we won't even charge for any of the dev work - infact it's very rare that a request is made that we can't see as being of interest to others, and we will share the resultant modules with other customers as long as the original requestor has no objection. I can only think of one such request over the last year or so that ended up as a charged piece of work. We have now gone back to these customers and explained the situation to them - that whilst we have an application that works and will do what they wanted, we can't release it owing to these restrictions as it would not be a reliable service. They now understand and accept the situation, and have thanked us the effort in making the app, and were appreciative that we have found out about these restrictions before we put things live and then later ran into problems and had to stop a service that they had started using. On Feb 13, 12:32 pm, Tim Skipper t...@intonet-technology.co.uk wrote: On Feb 12, 2:19 pm, Gummy Bear ser...@seductive.com wrote: There's simple workaround for that. Just think about it and you'll figure it out ;-) Yes, use email instead. I can't help thinking that all these devs up in arms because Twitter have limited use of their (free) service are making twitter apps just because it's the latest bandwagon to jump on, rather than because it's the most suited platform for the task in hand. I personally think Twitter should bin DMs altogether, it seems at odds with what Twitter is all about. Regards Tim -- 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: DM rate limit
I appreciate the feedback but the issue is that our clients send DM's to their customers and the customer base could and has grown beyond 250 users. We have whitelisted the clients that needed increased rate limits so we are ok for now but this could effect how we deal with future clients. There has been a lot of activity from this group and it's been hard to keep track of all of the information but I did read that you can still request increased DM rate limits which is all we need but I don't know if this has been confirmed by someone from twitter. Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information On 2011-02-12, at 6:59 PM, Xristofer Obbit dixt...@dixtort.net wrote: Why not have each client register a notification account with your app that sends a DM to their main account. That gives every client 250 DMs. Better yet, make it a private account and push notifications as status updates giving you 1000/day while keeping privacy. Sent from my iPhone On Feb 12, 2011, at 5:17 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Sat, 12 Feb 2011 17:07:36 -0500, Trevor Dean trevord...@gmail.com wrote: I agree, don't be so quick to judge. We have an opt-in based service and out clients have thousands of customers that explicitly say yes send me direct messages. The information we send is requested by the end user and is not spam. So you can imagine that a client with a large user base could quickly go beyond the 250 dm/day limit. It's unfortunate that the spammers take advantage and ultimately ruin things for legitimate services. Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information Speaking of spam, there's a great article at the New York Times on J.C. Penney, black hat SEO and Google: http://www.nytimes.com/2011/02/13/business/13search.html Many thanks to Twitter's spam fighters for keeping it as clean as it is, under the circumstances. -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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: DM rate limit
Confirming limits is not Twitter HQ's strength. I can see why. They want to keep their options open. Instead of asking for approval, why not start a petition to get what you need? Put up a message here stating a case for more DMs. Explain why you want it. Ask other devs to sign on with a confirming response. When you get no reaction, repost the same request the following week, and again, and again, until Twitter makes the change or comes up with a useful alternative. What can they do to you? Cut off your whitelisting? Believe me, grandfathered whitelisting is just a way of keeping established devs quiet, and is unfair on its face. All whitelisting will go away. Anyone want to bet against that? Devs are Twitter's partners, not users to be controlled. Dev's make money for Twitter. Let's help them make more money by getting them more serious, business oriented users, not just more Beiber fans. We can do this for Twitter. Twitter needs to help us do it. Ok, Trevor? On Sun, Feb 13, 2011 at 10:49 AM, Trevor Dean trevord...@gmail.com wrote: I appreciate the feedback but the issue is that our clients send DM's to their customers and the customer base could and has grown beyond 250 users. We have whitelisted the clients that needed increased rate limits so we are ok for now but this could effect how we deal with future clients. There has been a lot of activity from this group and it's been hard to keep track of all of the information but I did read that you can still request increased DM rate limits which is all we need but I don't know if this has been confirmed by someone from twitter. Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information On 2011-02-12, at 6:59 PM, Xristofer Obbit dixt...@dixtort.net wrote: Why not have each client register a notification account with your app that sends a DM to their main account. That gives every client 250 DMs. Better yet, make it a private account and push notifications as status updates giving you 1000/day while keeping privacy. Sent from my iPhone On Feb 12, 2011, at 5:17 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Sat, 12 Feb 2011 17:07:36 -0500, Trevor Dean trevord...@gmail.com wrote: I agree, don't be so quick to judge. We have an opt-in based service and out clients have thousands of customers that explicitly say yes send me direct messages. The information we send is requested by the end user and is not spam. So you can imagine that a client with a large user base could quickly go beyond the 250 dm/day limit. It's unfortunate that the spammers take advantage and ultimately ruin things for legitimate services. Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information Speaking of spam, there's a great article at the New York Times on J.C. Penney, black hat SEO and Google: http://www.nytimes.com/2011/02/13/business/13search.html Many thanks to Twitter's spam fighters for keeping it as clean as it is, under the circumstances. -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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 -- Adam Green Twitter API Consultant and Trainer 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
RE: [twitter-dev] Freedom's just another word for nothing left to lose
Adam, Lol the writing was on the wall when they tried to shut down my app MyPostButler for providing end users easy access to the API in the early days. (August 2009) I'm still a lurker here but I learnt my lesson early, nothing I build is reliant on Twitter, if they want to shut off our access we have facebook/google/email as alternatives. I'm sure twitter will make a bundle of cash selling to someone, and I'm sure they will make a bundle of money through other methods so this post will fall through the cracks but when their lawyers on a recorded conference call said we're going to shut you down one way or another I knew it was time to spend my energy elsewhere. I am thankful that twitter propagated the whole idea of api access as a method to spread fast through the development community as it's made me money in other ways so for that I'm thankful. (didn't invent but certainly enouraged/continued) Regards, Dean Collins Cognation Inc d...@cognation.net +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] On Behalf Of Adam Green Sent: Sunday, February 13, 2011 7:47 AM To: Twitter Development Talk Subject: [twitter-dev] Freedom's just another word for nothing left to lose The behavior on this group has changed significantly since Ryan finally admitted that Whitelisting no longer exists. I've never seen anyone discuss methods of getting around TOS before, well there was Edward H., and we saw what happened to him. Now there are free flowing discussions of MTurk and other tricks to go way beyond the rate limits. I think this is great. Frankly, Twitter has done a good job of offering free resources to devs, which I thank them for, but there was way too much fear before. Now there are no extra benefits that can be given and withdrawn on a case by case basis. Boy do I hate that phrase. Of course, they can ban people from this list, but maybe the irony of Twitter blocking free speech on their own forum may restrain that urge in the future. Personally, I've treated Whitelisting like Social Security. It ain't going to be there when I need it. That has turned out to be a winning strategy. I don't really violate TOS, since I'm not as spammer, but I have never tried building anything that would fail if Twitter didn't give me Whitelisting after it got into production, which BTW was the most disrespectful thing I've seen from a platform vendor. Everyone should assume that you need to use what is there by default, and always be ready with a workaround if that gets taken away. My gut tells me that things will get worse before they get better. Twitter HQ will be under huge pressure to make money before the IPO, and we are likely to get some of the cuts. The inevitable they are parasites leeching off of us will surface. Anyone here old enough to remember Ed Esber? But in the long run, I've never seen a global phenomenon like Twitter, so I'm in it for the next 10 years at least. Then I can retire. Let's keep the discussion open guys. They've already taken away the most important thing you wanted. Now we can build with our eyes open. And don't be afraid to speak up. This is Twitter. Revolutions happen here. Adam Green Twitter API Consultant and Trainer 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
[twitter-dev] Re: Widgets above Slimbox/lilghtbox
OK, i figured it out myself, I'll write solution here if someone needs
this.
First, put div tags around your tweeter widget code like this:
div id=tweets
/* here is your tweeter widget code */
/div
Then in css file wtite this:
#tweets .twtr-timeline {
z-index: 0;
}
On Feb 13, 12:47 pm, Ivan imilose...@gmail.com wrote:
Twitter wigdets are displaying above lightbox gallery, here is
example:http://i.imgur.com/QwYFE.jpg
This is an old problem
(http://groups.google.com/group/twitter-development-talk/browse_thread...
) but I haven't find solution yet.
--
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 there going to be another Chirp?
On Feb 12, 2011, at 3:25 PM, M. Edward (Ed) Borasky wrote: On Sat, 12 Feb 2011 11:29:09 -0500, Brainewave Consulting i...@brainewave.com wrote: True enough, but Twitter is a global application - the developer conference should go global too! Rio! Twitter's huge in Brasil, and Facebook is conspicuously absent there! Oo, I think I'd try to make a trip to Brasil, that sounds fun. Mike Caprio Principal and Lead Consultant Brainewave Consulting 402 Graham Avenue PMB 211 Brooklyn, NY 11211 p: +1-347-269-0558 @brainewave -- 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 Development platform - A Rant
On Feb 13, 2011, at 08:53 , Umashankar Das wrote: Now, Twitter and it's API groups claim that, they, are putting artificial limits of rates to ensure proper delivery for regular service. Mr. Das, While you make many interesting points in your rant, I think many of them are conjecture and opinion. As reasonable people can disagree about opinions, I've edited them out of my reply. I wish to focus on some unambiguous issues. We each have to make our business bets with respect to the Twitter platform. (I speak as the developer of ch@tter™, an iPad Twitter client. In many ways, Twitter destroyed my business opportunity when they purchased Tweetie and made it free. I mention this for context and not as a cause to rant at Twitter. I'm making plenty of money as a result of building ch@tter™. The iOS consulting business is very healthy.) It is clear from this thread that many developers made, perhaps unwisely, product plans based on Twitter's continued support for white listing. In my case as a client developer, the increase of my API count from 150/hour to 350/hour due to moving to OAuth totally removed my need for white listing. If user streams was supported, I could easily live with 150/hour limit. If they would stand behind their user streams API, I would switch to it immediately. (Beta status is not, frankly, good enough. If they cannot make a commitment to their new API, why should I? By my count, user streams has been in beta for almost 6 months.) Changing a platform's API is hard. Twitter is discovering this the hard way. Every developer has an investment they would like to preserve in the status quo. That said, Twitter's API evolution practices, presumably approved by their CTO, Mr. Sarver, are not, in my opinion, helping their partners grow with Twitter. That they are turning off white listing while not having yet made a production commitment to user streams, is a great example of an evolutionary stumble. That they haven't announced any other methods of enhancing Twitter's ability to scale while supporting functionality enabled by the large white lists is an oversight. The outrage expressed in this thread is good, unambiguous evidence of the stumble. Another example is the closed roll-out of promoted tweets. I think every third party app developer would love to find a way to further monetize their Twitter application. Twitter did announce that they would find a way to allow their developer partners to participate with the promoted tweets program. That has not yet happened. Currently, as Twitter has made a floor price of $0.00 for iOS apps, I have to resort to Apple's iAds to capture revenue from my labors. I don't mind but it does cut my other market-making partner, Twitter, out of the revenue stream. As it reduces my revenue opportunities, I think this is sub-optimal. I win when my partner wins. A third example is the annotation feature. I am sure all of us could find an excellent use for annotations. I have many ideas on how to use them. But I cannot. A fourth example is Chirp? When is it? Will they hold it in a large enough venue? Or is it going to be like their announcement of #NewTwitter. A major announcement whose video was streamed by Robert Scoble? The sound was poor. The image sucked. And, BTW, thank you Robert Scoble. Without him Twitter could not have gotten their message quickly out. In contrast to these missteps, I have to publicly thank Mr. Singletary, Mr. Kalucki and Mr. Harris. Without their constant engagement on this list, the Twitter ecosystem would not be what it is. Overall, everyone needs to remember that we are dealing with a company that publicly claims to not yet be trying to capture revenue from their platform. We are seeing from their experiments the collateral damage. Rolling with the punches is painful. That is the cost of trying to access the almost 200 million Twitter users. What do I want? I want a better developer experience. Both Apple and Microsoft show what a good experience can be. I want user streams, a promoted tweet API and annotations. I hope Twitter can deliver these technical features to enable new business opportunities for themselves and the Twitter app ecosystem. Myself included. Anon, Andrew Andrew W. Donoho Donoho Design Group, L.L.C. a...@ddg.com, +1 (512) 750-7596 Knowing is not enough; we must apply. Willing is not enough; we must do. -- Johann Wolfgang von Goethe -- 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 Development platform - A Rant
On Sun, 13 Feb 2011 12:18:11 -0600, Andrew W. Donoho andrew.don...@gmail.com wrote: It is clear from this thread that many developers made, perhaps unwisely, product plans based on Twitter's continued support for white listing. In my case as a client developer, the increase of my API count from 150/hour to 350/hour due to moving to OAuth totally removed my need for white listing. If user streams was supported, I could easily live with 150/hour limit. If they would stand behind their user streams API, I would switch to it immediately. (Beta status is not, frankly, good enough. If they cannot make a commitment to their new API, why should I? By my count, user streams has been in beta for almost 6 months.) User Streams is in fact in production and has been for months. The only restrictions on User Streams, other than what's documented in the technical documentation, is that it is *only* for desktop *clients*, not servers or mobile. I'm not sure where iPad fits in this spectrum, but for sure an iPhone is mobile. *Site* Streams is designed for servers and it is still in beta. Perhaps you need to be pitching your idea to Twitter and adapting your service to Site Streams if it's a server-backed app, which I'm guessing an iPhone/iPad app would be. That said, Twitter's API evolution practices, presumably approved by their CTO, Mr. Sarver, are not, in my opinion, helping their partners grow with Twitter. [snip] Another example is the closed roll-out of promoted tweets. I think every third party app developer would love to find a way to further monetize their Twitter application. Twitter did announce that they would find a way to allow their developer partners to participate with the promoted tweets program. That has not yet happened. Currently, as Twitter has made a floor price of $0.00 for iOS apps, I have to resort to Apple's iAds to capture revenue from my labors. I don't mind but it does cut my other market-making partner, Twitter, out of the revenue stream. As it reduces my revenue opportunities, I think this is sub-optimal. I win when my partner wins. The key word in this rant is partner. A *partner* is, IMHO, someone who has a *formal* partnership arrangement. Sure, there's a certain formality when you accept Twitter's TOS, but I think if you want to use Site Streams or Promoted content, you should be negotiating as a business with Twitter as a business. What's in it for Twitter? Twitter has built a powerful brand. I was there in early 2007 when the vast majority of pundits predicted that it would go nowhere - that it was just a bunch of Ruby hackers with too much time on their hands, that it would destroy flow, etc. It's now one of the top ten sites world wide according to Alexa. If you want to be a partner with Twitter, *you* are the one who needs to have something to offer *them* IMHO. [snip] Overall, everyone needs to remember that we are dealing with a company that publicly claims to not yet be trying to capture revenue from their platform. I seem to have missed that claim. As far as I know, they *are* trying to capture revenue through a combination of Promoted Accounts, Tweets and Trends with bundled analytics and data licensing. What do I want? I want a better developer experience. Both Apple and Microsoft show what a good experience can be. I want user streams, a promoted tweet API and annotations. I hope Twitter can deliver these technical features to enable new business opportunities for themselves and the Twitter app ecosystem. Myself included. I think you have User Streams, though it may not be suitable for your specific application. You may be eligible to get in the Site Streams beta, although I'm guessing that was invite-only. You can always ask - as a business negotiating a partnership with another business. We'll have to wait and see about the Promoted products. Advertising sales is a fiercely competitive business and it's not something I personally want to deal with at the moment. Annotations? That was definitely a case where Twitter's reach seems to have exceeded its grasp. The story I've heard is that there are people in Twitter hacking away on it but the priorities do get adjusted according to the demands of the marketplace. If it could be a breakthrough spam killer, I think they'd push it front and center in a big hurry. ;-) -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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 Development platform - A Rant
Edward, I'm going to jump in on the partner issue, since that is my big point. I think you are thinking too small when you say If you want to be a partner with Twitter, *you* are the one who needs to have something to offer *them* IMHO. One dev is very small compared to Twitter. 10,000 devs is a labor force. 100,000 devs is a market that protects Twitter from *any* competitor, including Google. We are all partners, because we all make money. You look old enough to remember dBASE. That was a huge labor force that protected Ashton-Tate for years when they had a product with technical limitations. Sound familiar? Corporations and government agencies used dBASE not because it was *best*, but because they could find many qualified developers. Ashton-Tate started attacking their developers in 1988, when they were one of the top 5 software companies. They were out of business 3 years later. If Twitter wants to be embedded into the infrastructure of corporations around the world, they must have outside developers. If they want it to be a cool toy for the Kardashians and Justin Beiber to amuse their fans. They don't need us at all. It is their choice. On Sun, Feb 13, 2011 at 2:04 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Sun, 13 Feb 2011 12:18:11 -0600, Andrew W. Donoho andrew.don...@gmail.com wrote: It is clear from this thread that many developers made, perhaps unwisely, product plans based on Twitter's continued support for white listing. In my case as a client developer, the increase of my API count from 150/hour to 350/hour due to moving to OAuth totally removed my need for white listing. If user streams was supported, I could easily live with 150/hour limit. If they would stand behind their user streams API, I would switch to it immediately. (Beta status is not, frankly, good enough. If they cannot make a commitment to their new API, why should I? By my count, user streams has been in beta for almost 6 months.) User Streams is in fact in production and has been for months. The only restrictions on User Streams, other than what's documented in the technical documentation, is that it is *only* for desktop *clients*, not servers or mobile. I'm not sure where iPad fits in this spectrum, but for sure an iPhone is mobile. *Site* Streams is designed for servers and it is still in beta. Perhaps you need to be pitching your idea to Twitter and adapting your service to Site Streams if it's a server-backed app, which I'm guessing an iPhone/iPad app would be. That said, Twitter's API evolution practices, presumably approved by their CTO, Mr. Sarver, are not, in my opinion, helping their partners grow with Twitter. [snip] Another example is the closed roll-out of promoted tweets. I think every third party app developer would love to find a way to further monetize their Twitter application. Twitter did announce that they would find a way to allow their developer partners to participate with the promoted tweets program. That has not yet happened. Currently, as Twitter has made a floor price of $0.00 for iOS apps, I have to resort to Apple's iAds to capture revenue from my labors. I don't mind but it does cut my other market-making partner, Twitter, out of the revenue stream. As it reduces my revenue opportunities, I think this is sub-optimal. I win when my partner wins. The key word in this rant is partner. A *partner* is, IMHO, someone who has a *formal* partnership arrangement. Sure, there's a certain formality when you accept Twitter's TOS, but I think if you want to use Site Streams or Promoted content, you should be negotiating as a business with Twitter as a business. What's in it for Twitter? Twitter has built a powerful brand. I was there in early 2007 when the vast majority of pundits predicted that it would go nowhere - that it was just a bunch of Ruby hackers with too much time on their hands, that it would destroy flow, etc. It's now one of the top ten sites world wide according to Alexa. If you want to be a partner with Twitter, *you* are the one who needs to have something to offer *them* IMHO. [snip] Overall, everyone needs to remember that we are dealing with a company that publicly claims to not yet be trying to capture revenue from their platform. I seem to have missed that claim. As far as I know, they *are* trying to capture revenue through a combination of Promoted Accounts, Tweets and Trends with bundled analytics and data licensing. What do I want? I want a better developer experience. Both Apple and Microsoft show what a good experience can be. I want user streams, a promoted tweet API and annotations. I hope Twitter can deliver these technical features to enable new business opportunities for themselves and the Twitter app ecosystem. Myself included. I think you have User Streams, though it may not be suitable for your specific application. You may be eligible to get in the Site Streams beta, although
Re: [twitter-dev] Twitter Development platform - A Rant
Andrew , Thank you for such a measured response. I'm not looking at the immediate action of stopping whitelisting by twitter. I must add, that, if a certain feature requires an application process, I had doubts in my ability to convince twitter, that, I really deserve to be in the list. I believe I've also mentioned in my mail ,that , we, as a team/company, have already made arrangements which does not require us to use whitelisting. Perhaps, since, my initial mail was a rant, but, not a structured 'reply' it got lost in whatever I said. What I say is essentially this. Twitter seems to be discouraging developers whose products have the potential who increasing their userbase. It almost as If I'm hearing that, 'WE DONT WANT ANYMORE USERS' . We're tired of managing the existing number. I don't disagree that nobody should make plans on features which have no guarantees [whitelisting], that, they will continue in future. But, by putting such limits isn't Twitter running the risk of becoming just another product. The creation of the facebook development platform was responsible in spawning a market leader in gaming field i.e ZYNGA.But, These limits by twitter dont allow someone to think about a new idea. He will stop thinking that ; what if I get traffic ? Anyhow, twitter will block me if I cross their rate limit. How can an innovator think in such an environment? I'm not sure if you find this as conjecture. This , to me , is a logical line of reasoning. Anyhow, We ,as a team , have planned on working with a worst case scenario. twitter's search API is very important to us. We never planned for whitelisting, we dont need it. The only worry is if tomorrow, (hopefully), if we generate traffic from our product, will twitter just stop the 'SEARCH API' . We need to know that. Clarity in this will go a long way. I hope I haven't offended anybody here. These are views , since, we as a team , feel that we can create something path-breaking using twitter as our backend resource. We will only help twitter that way. Thanks Regards Umashankar Das On Sun, Feb 13, 2011 at 11:48 PM, Andrew W. Donoho andrew.don...@gmail.comwrote: On Feb 13, 2011, at 08:53 , Umashankar Das wrote: Now, Twitter and it's API groups claim that, they, are putting artificial limits of rates to ensure proper delivery for regular service. Mr. Das, While you make many interesting points in your rant, I think many of them are conjecture and opinion. As reasonable people can disagree about opinions, I've edited them out of my reply. I wish to focus on some unambiguous issues. We each have to make our business bets with respect to the Twitter platform. (I speak as the developer of ch@tter™, an iPad Twitter client. In many ways, Twitter destroyed my business opportunity when they purchased Tweetie and made it free. I mention this for context and not as a cause to rant at Twitter. I'm making plenty of money as a result of building ch@tter™. The iOS consulting business is very healthy.) It is clear from this thread that many developers made, perhaps unwisely, product plans based on Twitter's continued support for white listing. In my case as a client developer, the increase of my API count from 150/hour to 350/hour due to moving to OAuth totally removed my need for white listing. If user streams was supported, I could easily live with 150/hour limit. If they would stand behind their user streams API, I would switch to it immediately. (Beta status is not, frankly, good enough. If they cannot make a commitment to their new API, why should I? By my count, user streams has been in beta for almost 6 months.) Changing a platform's API is hard. Twitter is discovering this the hard way. Every developer has an investment they would like to preserve in the status quo. That said, Twitter's API evolution practices, presumably approved by their CTO, Mr. Sarver, are not, in my opinion, helping their partners grow with Twitter. That they are turning off white listing while not having yet made a production commitment to user streams, is a great example of an evolutionary stumble. That they haven't announced any other methods of enhancing Twitter's ability to scale while supporting functionality enabled by the large white lists is an oversight. The outrage expressed in this thread is good, unambiguous evidence of the stumble. Another example is the closed roll-out of promoted tweets. I think every third party app developer would love to find a way to further monetize their Twitter application. Twitter did announce that they would find a way to allow their developer partners to participate with the promoted tweets program. That has not yet happened. Currently, as Twitter has made a floor price of $0.00 for iOS apps, I have to resort to Apple's iAds to capture revenue from my labors. I don't mind but it does cut my other market-making partner, Twitter, out of the revenue stream. As it reduces my revenue
[twitter-dev] Re: Twitter Development platform - A Rant
If you're basing your business on the Search API it definitely sounds as if you're not aware yet of the [mostly unofficially documented] limits and constraints [mostly just alluded to by John Kalucki and others through their exhortations on this list for people to rather use the Streaming API] on using the Search API. If your application is based on the assumption that you can throw an unlimited [or even just a reasonably elevated] number of queries at the Search API as and when your app needs scaling or hits a volume spike, you will be wise to rethink your approach. On Feb 13, 4:03 pm, Umashankar Das umashankar...@gmail.com wrote: We ,as a team , have planned on working with a worst case scenario. twitter's search API is very important to us. We never planned for whitelisting, we dont need it. The only worry is if tomorrow, (hopefully), if we generate traffic from our product, will twitter just stop the 'SEARCH API' . We need to know that. -- 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 Development platform - A Rant
On Feb 13, 2011, at 13:04 , M. Edward (Ed) Borasky wrote: On Sun, 13 Feb 2011 12:18:11 -0600, Andrew W. Donoho andrew.don...@gmail.com wrote: It is clear from this thread that many developers made, perhaps unwisely, product plans based on Twitter's continued support for white listing. In my case as a client developer, the increase of my API count from 150/hour to 350/hour due to moving to OAuth totally removed my need for white listing. If user streams was supported, I could easily live with 150/hour limit. If they would stand behind their user streams API, I would switch to it immediately. (Beta status is not, frankly, good enough. If they cannot make a commitment to their new API, why should I? By my count, user streams has been in beta for almost 6 months.) User Streams is in fact in production and has been for months. The only restrictions on User Streams, other than what's documented in the technical documentation, is that it is *only* for desktop *clients*, not servers or mobile. I'm not sure where iPad fits in this spectrum, but for sure an iPhone is mobile. *Site* Streams is designed for servers and it is still in beta. Perhaps you need to be pitching your idea to Twitter and adapting your service to Site Streams if it's a server-backed app, which I'm guessing an iPhone/iPad app would be. Mr. Borasky, Any API where the very first line in the schema section says it is subject to change is not, in fact, in production. Now it may be due to sloppy documentation but I doubt it. Twitter's documentation process has become much better. IOW, user streams is in beta. If it is production worthy, then Twitter should commit to it. This API, until they version the route, should no longer be subject to change. That said, Twitter's API evolution practices, presumably approved by their CTO, Mr. Sarver, are not, in my opinion, helping their partners grow with Twitter. [snip] Another example is the closed roll-out of promoted tweets. I think every third party app developer would love to find a way to further monetize their Twitter application. Twitter did announce that they would find a way to allow their developer partners to participate with the promoted tweets program. That has not yet happened. Currently, as Twitter has made a floor price of $0.00 for iOS apps, I have to resort to Apple's iAds to capture revenue from my labors. I don't mind but it does cut my other market-making partner, Twitter, out of the revenue stream. As it reduces my revenue opportunities, I think this is sub-optimal. I win when my partner wins. The key word in this rant is partner. Let me be very clear. The term rant was applied by the opening poster. I am pointing out what I think are concrete issues which we all, as business partners with Twitter should consider. That is not a rant. A *partner* is, IMHO, someone who has a *formal* partnership arrangement. Sure, there's a certain formality when you accept Twitter's TOS, but I think if you want to use Site Streams or Promoted content, you should be negotiating as a business with Twitter as a business. What's in it for Twitter? The ToS is a contract. I've also based my business on Twitter's APIs. I view the APIs and other aspects of the relationship I have with Twitter to effectively be a partnership. Twitter, as the senior partner in this relationship, barely knows I exist. As to what's in it for Twitter? They have support a public API because it makes their product better. And they do want people like me making their and my product better. Twitter has built a powerful brand. I was there in early 2007 when the vast majority of pundits predicted that it would go nowhere - that it was just a bunch of Ruby hackers with too much time on their hands, that it would destroy flow, etc. It's now one of the top ten sites world wide according to Alexa. If you want to be a partner with Twitter, *you* are the one who needs to have something to offer *them* IMHO. And, I believe I do. I suspect that you believe you offer them value and vice versa or you would not waste your time on this list. This email and those of other developers do improve their product. Every bug discovered helps their product. Are we suckers? Perhaps. Overall, I have profited from this arrangement. I wish Twitter well and I hope they improve their relationship with the developer community. [snip] Overall, everyone needs to remember that we are dealing with a company that publicly claims to not yet be trying to capture revenue from their platform. I seem to have missed that claim. As far as I know, they *are* trying to capture revenue through a combination of Promoted Accounts, Tweets and Trends with bundled analytics and data licensing. Stone, reacting to a question from TechEye, said that there was still so much the company wanted to do, including proving that it had a
[twitter-dev] Re: Update on Whitelisting
It may sound foolish, but some of us coded our apps a couple years ago, improved them up to production readiness and then released and moved on to something else. Each of these mayor changes would in theory make one reread all this old code and find where one uses whatever you plan to change this time. I do not have that luxury of time. I strongly prefer to spend time with my two kids than fix something that is not broken yet but eventually will. I have recoded the whole app two times to accomodate, and yes I am growing tired of playing this. My kids have not even changed a single tooth and I have coded the whole app 3 times!!! If it is s easy to change to oauth and streaming why don't you release some open source code which implements the old calls using these new capabilities? Then we would just point our old calls to our own server. It's called backwards compatibility. And just like the previous two times, I do not plan to be absent from my kids' life while I redo old code. I will just let it break and *then* the failure points will be obvious. If it fixes in a day I will. Else, end of life, and 80k users get a blog post. And since users have no idea about this, I need an analogy... Dear printing press users: the excessive amount of Bibles you have been printing has created an undue demand of the L O R D letters. As of today we will be supplying a very limited amount of these four letters, but we will be supplying paper that has the word LORD preprinted on it. Please adjust your texts accordingly. On Feb 10, 3:43 pm, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers interested in elevated access to the Twitter stream for the purpose of research or analytics can contact our partner Gnip for more information. As always, we are here to answer questions, and help you build applications and services that offer value to users. Ryan -- Ryan Sarver @rsarver -- 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] Tweet button doesn't support internationalized domain names
My Japanese website has an international domain name: http://xn--mcki2eq4ryb.hobby-site.org/ Depending on which browser you use, this may or may not be displayed as http://ガーデニング.hobby-site.org/ When I use the code generated by the tweet button code generator (http://twitter.com/about/resources/tweetbutton) I get the following message when clicking on it: URL required 'url' parameter does not contain a valid URL. So, I have tried specifying the URL explicitly as an urlencoded query parameter like so: http://twitter.com/share?url=http%3A%2F%2Fxn--mcki2eq4ryb.hobby-site.org%2 ... but I get the same message. A page with a tweet button that demonstrates this exact problem can be found here: http://xn--mcki2eq4ryb.hobby-site.org/introducing-gardening-hobby-site.html The URL http://xn--mcki2eq4ryb.hobby-site.org/ IS a valid url, so it seems like this is a bug in the tweet button. Please could you fix it as soon as possible? 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-dev] Re: Data-expanded-url attribute
Any ideas on this one guys? On Feb 10, 4:06 pm, ctrand ctr...@gmail.com wrote: Hello, I have a bunch of shortened urls which are resolved/redirected to full urls by my webapp. e.g. http://dealush.com/sale/2wml resolves to http://dealush.com/shopping-sales/2wml/sydney-sale-8-off-at-catwalk-w... When I tweet the short URL, sometimes the data-expanded-url attribute is populated for the url and when I mouseover it I can see the full url. However sometimes it is not populated, and there is no data- expanded-url attribute at all! I am wondering if anyone can shed some light onto why it would be so. I am also thinking that this is affecting the counters on my tweet buttons, as tweets that do have an URL with the data-expanded-url attribute give a +1 for the counter, and those that do not have a data- expanded-url don't. Does something need to happen for the data-expanded-url value to populate? Or perhaps there something wrong with some of my URLS? Note: THe example URL above does have a data-expanded-url value. Thanks in advance, Carl PS - Please let me know if you need any additional information from me and it will be forthcoming! -- 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 Development platform - A Rant
On Sun, 13 Feb 2011 14:16:30 -0500, Adam Green 140...@gmail.com wrote: Edward, I'm going to jump in on the partner issue, since that is my big point. I think you are thinking too small when you say If you want to be a partner with Twitter, *you* are the one who needs to have something to offer *them* IMHO. One dev is very small compared to Twitter. 10,000 devs is a labor force. 100,000 devs is a market that protects Twitter from *any* competitor, including Google. We are all partners, because we all make money. You look old enough to remember dBASE. That was a huge labor force that protected Ashton-Tate for years when they had a product with technical limitations. Sound familiar? Corporations and government agencies used dBASE not because it was *best*, but because they could find many qualified developers. Ashton-Tate started attacking their developers in 1988, when they were one of the top 5 software companies. They were out of business 3 years later. If Twitter wants to be embedded into the infrastructure of corporations around the world, they must have outside developers. If they want it to be a cool toy for the Kardashians and Justin Beiber to amuse their fans. They don't need us at all. It is their choice. Well, I'm old enough but I was doing something radically different from Ashton-Tate at the time. This whole thread is starting to sound eerily similar to last year, when Fred Wilson made the infamous filling holes blog post, followed by Twitter buying Tweetie, followed by Chirp. I'd be surprised if the *Twitter* ecosystem could support 10,000 independent developers - they'd self-organize into businesses with some sort of power law size distribution, where the largest such business is Twitter itself. I don't know that Twitter wants to be embedded into the infrastructure of corporations. It seems to me that Twitter is unique and not at all suited to intra-enterprise communications. Besides, there are dozens of enterprise software platforms that can do everything Twitter can do except talk to the hundreds of millions of Twitter users in real-time. ;-) Maybe I am thinking too small, but then again, people aren't coming to *me* with problems big enough to require whitelisting, or for that matter Cassandra, or MapReduce, or sending thousands of DMs a day. Even if they did, there's no way I could compete with Twitter. I really should save this for my blog - it's been a while since I wrote a post about Twitter, and that's what my search analytics tell me people read there. ;-) -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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 Development platform - A Rant
Well, I'm old enough but I was doing something radically different from Ashton-Tate at the time. This whole thread is starting to sound eerily similar to last year, when Fred Wilson made the infamous filling holes blog post, followed by Twitter buying Tweetie, followed by Chirp. I'd be surprised if the *Twitter* ecosystem could support 10,000 independent developers - they'd self-organize into businesses with some sort of power law size distribution, where the largest such business is Twitter itself. I don't know that Twitter wants to be embedded into the infrastructure of corporations. It seems to me that Twitter is unique and not at all suited to intra-enterprise communications. Besides, there are dozens of enterprise software platforms that can do everything Twitter can do except talk to the hundreds of millions of Twitter users in real-time. ;-) Maybe I am thinking too small, but then again, people aren't coming to *me* with problems big enough to require whitelisting, or for that matter Cassandra, or MapReduce, or sending thousands of DMs a day. Even if they did, there's no way I could compete with Twitter. I really should save this for my blog - it's been a while since I wrote a post about Twitter, and that's what my search analytics tell me people read there. ;-) Good points. I think the basic confusion is the definition of developer. It could mean someone who builds a web or mobile app and tries to monetize it. That would be limited. I think it also means all the consultants and in-house programmers who integrate Twitter into existing websites and businesses. As I started responding CNN ran a big button on the screen telling people to try their Twitter integration on their website. I think that was built by a developer, not Twitter HQ. Multiply that by every TV show, radio program, newspaper, magazine, movie, real estate office, hospital, retailer, you get the point. There are way more than 10,000 programmers who work on websites and mobile apps around the world. They are all possible Twitter developers, among other tasks they did. Too big an idea? Maybe, but with the right assistance from Twitter, there would be enough developers that when a competitor comes along Twitter would have a base that would make it hard to switch. That is what we offer them. I have an idea. Why doesn't Twitter hire a developer relations person? Not a support person. Matt and Taylor do a good job of technical support. I appreciate what they do. I mean someone who could run a developer program. I haven't seen someone like that yet. Could some of the $200 million pay that salary? I look forward to your blog post on this, Edward. -- Adam Green Twitter API Consultant and Trainer 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
Re: [twitter-dev] Twitter Development platform - A Rant
On Mon, 14 Feb 2011 01:21:29 -0500, Adam Green 140...@gmail.com wrote: Good points. I think the basic confusion is the definition of developer. It could mean someone who builds a web or mobile app and tries to monetize it. That would be limited. I think it also means all the consultants and in-house programmers who integrate Twitter into existing websites and businesses. As I started responding CNN ran a big button on the screen telling people to try their Twitter integration on their website. I think that was built by a developer, not Twitter HQ. My impression is that this is exactly the sort of thing @anywhere was designed to do - make it possible for a CNN or even the Original Coffee Brake to incorporate Twitter into their web site with a budget of, say, 8 hours of HTML editing time. ;-) I haven't kept up with how well @anywhere is fulfilling that promise, though. I ran it for a long time on my blog but shut it down because the trips to Twitter's servers were slowing down page loads. I should probably revisit that now that I'm starting to get traffic again. Multiply that by every TV show, radio program, newspaper, magazine, movie, real estate office, hospital, retailer, you get the point. There are way more than 10,000 programmers who work on websites and mobile apps around the world. They are all possible Twitter developers, among other tasks they did. I don't know about the rest of the world, but here in PDX, the skills that are in huge demand are HTML5/CSS3/JavaScript and user interface design. We've got a small collection of people who do stuff with Twitter, but you don't see help wanted ads for Twitter API coding - that's something people do in their spare time. Most folks use Twitter the old-fashioned way - from the web app or from a client - or license a monitoring platform that talks to Twitter and Facebook. Too big an idea? Maybe, but with the right assistance from Twitter, there would be enough developers that when a competitor comes along Twitter would have a base that would make it hard to switch. That is what we offer them. I think it would be harder for a competitor to get Twitter's millions of active subscribers than to get thousands of developers. ;-) I was just looking at the Alexa statistics - Twitter is in 9th place world-wide now. http://www.alexa.com/topsites Who's ahead of us? Twitter is just below the huge Chinese site Baidu.com. Neither Facebook nor Twitter is active in China, although I have seen accounts claiming to be from Guangzhou. Next up the ladder is Wikipedia. In short, it's been a long climb since March of 2006 to get there, and there's a lot of power above Twitter - Google/Youtube/Blogger, Yahoo, Microsoft, Facebook, Wikipedia and Baidu.com. Twitter is, as they say, running with the big dogs. And we're ahead of Aol. ;-) I have an idea. Why doesn't Twitter hire a developer relations person? Not a support person. Matt and Taylor do a good job of technical support. I appreciate what they do. I mean someone who could run a developer program. I haven't seen someone like that yet. Could some of the $200 million pay that salary? Maybe again I'm thinking small, but I have yet to run up against anything that Twitter did that seriously impacted me. Twitter's not like Microsoft, Android or Apple where you need a huge standardized SDK / MSDN-like library. The one thing I'd want as an independent developer would be some kind of keyword tools along the lines of what Google provides for webmasters. I can easily determine what people tweet about but I *can't* determine what they search for. Oh, yeah - a Streaming endpoint that delivers the overall tweets per minute every minute, so I can draw pretty graphs in real time like Carolyn Penner did on the Twitter blog. http://blog.twitter.com/2011/02/superbowl.html -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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
