[twitter-dev] Re: FW: Twitter is Suing me!!!

I got a letter from a UK law firm too regarding www.twitlonger.com (which clearly doesn't use the word Twitter). They weren't too draconian in their claims. They want a disclaimer put on the site (fair enough) and for me to stop using the little blue birds (again, fair enough. This is what happen

[twitter-dev] Re: Following Churn: Specific guidance needed

Well said Shannon. -- Kevin Mesiab CEO, Mesiab Labs L.L.C. http://twitter.com/kmesiab http://mesiablabs.com http://retweet.com

[twitter-dev] Re: Get user email?

The API does not provide access to viewing an user's email. You may update the users email if you wish via http://twitter.com/account/update_profile [1] Josh [1] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0update_profile On Wed, Aug 12, 2009 at 12:04 AM, Almir Karic wrote

[twitter-dev] Re: Newbie to seek advice on the flow of a twitter app with OAuth

Andrew, I can't seem to get this working and wanted to see if you would be able to shed some light... thx in my main index i created a variable: (i tried with both of these) $callback_url ='&callback_url=http%3A%2F%2Fwww.tweetivism.com%2Fblog'; $callback_url ='http%3A%2F%2Fwww.tweetivism.com%2F

[twitter-dev] Re: terrible! my statuses lose! from 3000+ to 84

The same here, i lost a lot of tweets. I recommend opening a ticket. Good luck. Cheers, Zalt On Aug 10, 11:21 am, bang wrote: > I began to use twitter one year ago. I have been posted statuses no > less than 3000, but today I found my statuses count become 84! Then I > go to twitter homepage to

[twitter-dev] Re: Following Churn: Specific guidance needed

Here also lies an ongoing issue I see repeated over and over with regard to all social applications (but especially Twitter) - the assumption that how the author uses the tool is how and why everyone uses that tool. ie not all Twitter accounts are used to follow others actively - but in so

[twitter-dev] Re: Following Churn: Specific guidance needed

I never said you did unfollows. Rather, I pointed out that tweetlater uses Twitter's follow limit as a guidepost for your bulk auto follow and bulk auto return follow features. That's fine. But I then found it odd that that you would say "Amen" when someone said that Twitter shouldn't publish

[twitter-dev] Re: Following Churn: Specific guidance needed

I agree my comparison to dictatorships is a stretch, but I was in a poetic mood and trying to emphasize the point that clarity is better than ambiguity. Twitter is obviously doing a tremendous job dealing with their explosive growth and dynamic nature of this new medium they've created. That sai

[twitter-dev] Get user email?

is it possible to get the user email once the user has authorized me via OAuth?

[twitter-dev] Re: FW: Twitter is Suing me!!!

I really really want to see them backup the tweet trademark. All birds are now being sued by twitter, they can no longer say; tweet tweet LOL. Seems lil twitter grew up and found lawyers. While I don't agree or like the product that Dean sells, I dis-agree more with the misuse of legal represent

[twitter-dev] Re: FW: Twitter is Suing me!!!

Actually, what they say is "If, however, you do not comply with these requests, Twitter will be forced to consider suspending your Twitter accounts and take such steps as it deems necessary to protect its intellectual property rights". In short, we are asking you to stop selling your product and g

[twitter-dev] Re: FW: Twitter is Suing me!!!

There's two different issues here: the name, and what it does. If it was just the name, that letter would likely just ask you to do that prior to continuing sales. The larger issue, it seems, is that the app does things that violate the TOS (and annoy Twitter users). Unless you change the applicati

[twitter-dev] Re: FW: Twitter is Suing me!!!

I guess I should have pointed out that my tongue was firmly planted in my check when I wrote my previous post. My bad! :-( Dean: I don't mean to make light of your particular situation. Sometimes I just can't not point out absurdities, which the logic I presented clearly is. What I was trying to

[twitter-dev] Re: FW: Twitter is Suing me!!!

It's not that simple - if you read the letter they are telling me I have to stop selling the software entirely. www.MyTwitterButler.com/I'm_Being_Sued Regards, Dean Collins d...@mytwitterbutler.com

[twitter-dev] Re: FW: Twitter is Suing me!!!

Not to add fuel to the fire either, but looks like Twitter may have to become like the RIAA and spend all their money suing half the Internet (or paying high priced lawyers to send out letters etc) Re: 2/ That no one can use the word "Twitter" in their domain A quick Google search reveals... tw

[twitter-dev] Re: FW: Twitter is Suing me!!!

Have you consider renaming your app to Tweetrobot , twtrbutler, tweeturk? They own the brand Twitter why not rename your service? -E Gpro.ws On Tue, Aug 11, 2009 at 11:56 PM, Dean Collins wrote: > > I'm glad you feel you can move on.I'm the one facing legal action!! > > > (and yes

[twitter-dev] Re: FW: Twitter is Suing me!!!

Not taking sides, here, but so far you are the only one that has reported receiving the C&D letter. How do you get from 1 instance of legal action to "Twitter's lawyers are shutting down the third party developer community"? - h On Tue, Aug 11, 2009 at 20:56, Dean Collins wrote: > > Does Twitte

[twitter-dev] Re: FW: Twitter is Suing me!!!

Twitter warned a while back that they where being granted the trademark for "Twitter" and they would like developers to no longer use "Twitter" in their product names. This does not mean you can't display a "powered by twitter" logo. They just don't want you associating their brand name with your p

[twitter-dev] Re: FW: Twitter is Suing me!!!

> > (sorry I'm new to this and freaking out - never had a lawyer sue me like > this) And you still haven't. > >

[twitter-dev] Re: FW: Twitter is Suing me!!!

I'm glad you feel you can move on.I'm the one facing legal action!! (and yes I read the comment I'm not being suedI'm facing legal action) Does Twitter inc know that their lawyers are shutting down the third party developer community? (sorry I'm new to this and freaking out - never

[twitter-dev] Re: FW: Twitter is Suing me!!!

An interesting implication is buried in all of this. FACT: http://apiwiki.twitter.com/Terms-of-Service states: "Please give us a nod in your app, perhaps by including one of these stylish "Powered by Twitter" badges", which I read as "If ya use the API you must acknowledge twitter." FACT: The le

[twitter-dev] Re: FW: Twitter is Suing me!!!

As others have pointed out, this isn't a lawsuit. That aside, Twitter announced some time ago that they were not comfortable with people using their name as part of the name of their product ( http://blog.twitter.com/2009/07/may-tweets-be-with-you.html) , so it seems odd that you would be surp

[twitter-dev] Re: FW: Twitter is Suing me!!!

Funny thing about trademarking a name and trying to utilize that trademark against a URL, can't be done. If so, MicroSoft would have nailed people left and right for infringement upon IE (can we say IE7.com and IE8.com) as well as several other websites that utilize trademarked MS product names LO

[twitter-dev] Re: FW: Twitter is Suing me!!!

On Tue, Aug 11, 2009 at 20:48, Dean Collins wrote: > Any other developer being sued by Twitter today? > I might be. Oh wait, no, I'm not, because I know the difference between a lawsuit and a cease and desist letter that enumerates all the things I'm doing that violates Twitter's terms of servi

[twitter-dev] Re: RateLimit Calculation

As I've pointed out in other posts to this group, and I will be the first to acknowledge that there are conflicting opinions and facts on this, it is my understanding and experience that for GET requests that require authorization the rate limit is per user per IP address: -If *EITHER* the use

[twitter-dev] Re: FW: Twitter is Suing me!!!

The same TOS that applies to users applies to developers, along with this one: http://apiwiki.twitter.com/Terms-of-Service If you haven't already, I encourage all developers to familiarize themselves with both. You may also, now, find more value in join

[twitter-dev] Re: FW: Twitter is Suing me!!!

Sorry Cameron :-) it's just so easy to hit that button :-) peace Neil On 12 Aug 2009, at 04:02, Cameron Kaiser wrote: Could we please not quote the *entire* *original* *message* with every reply? -- personal: http://www.cameronkaiser.com/ -- Camero

[twitter-dev] Re: FW: Twitter is Suing me!!!

Could we please not quote the *entire* *original* *message* with every reply? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- They told me I was gullible ... and I believed them. -

[twitter-dev] Re: Twitter Update, 8/10 noon PST

Geometric backoffs are more generally know as exponential backoffs. If ya google that, ya get a couple of useful and interesting things: http://en.wikipedia.org/wiki/Exponential_backoff http://en.wikipedia.org/wiki/Truncated_binary_exponential_backoff http://dthain.blogspot.com/2009/02/exponentia

[twitter-dev] Re: php curl api calls no returns about 90% of the time

If you include the full headers in your response output, that would be helpful in tracking this down. On Tue, Aug 11, 2009 at 17:17, freefall wrote: > > It's quite impressive but I get nothing back from most of the curl api > request I make to twitter. Fully whitelisted on ip, lots of ratelimit

[twitter-dev] php curl api calls no returns about 90% of the time

It's quite impressive but I get nothing back from most of the curl api request I make to twitter. Fully whitelisted on ip, lots of ratelimit spare, total failures from twitter all the time. A new favourite appeared today from a http://twitter.com/friends/ids/accountname.xml get: I'd love t

[twitter-dev] Re: RateLimit Calculation

On Wed, Aug 12, 2009 at 6:41 AM, Julio Biason wrote: > > On Wed, Aug 12, 2009 at 7:01 AM, shiplu wrote: >> Oops! Basic Mistake! >> But what about I am talking about GET requests. > > If you're doing a GET 3 times every hour, then it would be better not > use a whitelisted IP. This way, the rate li

[twitter-dev] Re: PubSubHubbub and Twitter RSS

I want to believe! If there are compelling arguments, we'll consider this deeply. So far I'm still unconvinced. The Streaming API is built only on open standards: HTTP, XML, JSON. Anyone can build a Streaming API client in a few hours of work using well worn libraries and techniques. (Only a slig

[twitter-dev] Re: OAuth vs. Basic authentication strictly on iPhone

Why would it be hosted in your app? Why can't you open Safari? Obviously Safari is *more* trusted. But if you've already installed an untrusted app onto your machine, the untrusted app has enough power to keylog, brute force your keychain (or other password db), send personal info over

[twitter-dev] Re: RateLimit Calculation

On Wed, Aug 12, 2009 at 7:01 AM, shiplu wrote: > Oops! Basic Mistake! > But what about I am talking about GET requests. If you're doing a GET 3 times every hour, then it would be better not use a whitelisted IP. This way, the rate limit will count to each user, not the IP (considering that you're

[twitter-dev] Re: PubSubHubbub and Twitter RSS

Persistent connections for notifications certainly allay my fears around latency and throughput for well-behaved hubs. I don't see any real cost savings, other than some minor bandwidth savings on the fan-out. We'd incur significant development cost to support this alternative approach, as we've

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

For me the API behavior is now back again to this morning, with around 2 to 5 rejections per second, and most being successful on the first or second backed-off retry. Dewald On Aug 11, 6:22 pm, Alex Payne wrote: > Just found out that our hosting provider put some hardware in place that may > c

[twitter-dev] Re: OAuth vs. Basic authentication strictly on iPhone

JDG, > Why would it be hosted in your app? Why can't you open Safari? The ideal usage pattern in an application is not to leave the application. Opening Safari requires exiting the current application. Opening a UIWebView within your application is the way to go. Brad On Aug 11, 2009, at

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

Just found out that our hosting provider put some hardware in place that may cause disruptions. Our operations team just spoke them, and they should be taking it down in 15 - 30 minutes. On Tue, Aug 11, 2009 at 14:03, Andrew Badera wrote: > > On Tue, Aug 11, 2009 at 5:01 PM, Andrew Badera wrote:

[twitter-dev] Re: Search API Limits lowered?

I don't have a domain to point back to. I'm doing data-mining and analysis on a server that isn't public. I have set the User-Agent to something unique (I thought you were saying to change it for every request?). Yet I'm still getting rate limited and told to back off a lot. Ryan S said it might s

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

On Tue, Aug 11, 2009 at 5:01 PM, Andrew Badera wrote: > On Tue, Aug 11, 2009 at 4:57 PM, Alex Payne wrote: >> Yes, I've just been informed that the attack has resumed, and that our >> service provider is putting network hardware in place to counter the attack. >> We're trying to work with them to

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

On Tue, Aug 11, 2009 at 4:57 PM, Alex Payne wrote: > Yes, I've just been informed that the attack has resumed, and that our > service provider is putting network hardware in place to counter the attack. > We're trying to work with them to ensure minimal impact to the API, but in > the near term th

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

Also, please be sure to provide packet dumps and full headers where possible so we can more easily determine the source of the issue. Thanks, Ryan On Tue, Aug 11, 2009 at 2:00 PM, Alex Payne wrote: > We're aware of these issues; sorry. > Our ops team tells me that the countermeasures that are be

[twitter-dev] Re: RateLimit Calculation

On Wed, Aug 12, 2009 at 3:57 AM, Dewald Pretorius wrote: > > On Aug 11, 5:53 pm, shiplu wrote: >> Scenario 1: > > No, you don't. Status updates are POSTs, which do not count against > your 20,000 rate limit. > > Dewald Oops! Basic Mistake! But what about I am talking about GET requests. -- A K

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

We're aware of these issues; sorry. Our ops team tells me that the countermeasures that are being put in place should not cause the 302 redirect behavior that impacted OAuth and other services late last week. If you're seeing that behavior, please post here and we'll coordinate with them to elimina

[twitter-dev] Re: Seeing same login issues right now as when DDoD happened

Please see the other thread in this group. On Tue, Aug 11, 2009 at 13:55, Sean Callahan wrote: > > I've tried logging into a handful of sites built around the Twitter > API without success. I'm seeing the same login issues right now as > when the DDoD happened. Twitter is aware of the downtime i

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

Alex, Did not see this post and posted a new message. Still receiving lots of errors and no one can login on our site, tweetphoto.com, right now along with a handful of others (that I've tried myself). Just wanted to give you a heads up. Thanks! Sean On Aug 11, 1:11 pm, Alex Payne wrote: > Our

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

Yes, I've just been informed that the attack has resumed, and that our service provider is putting network hardware in place to counter the attack. We're trying to work with them to ensure minimal impact to the API, but in the near term there may be issues with OAuth and the Streaming API. This is

[twitter-dev] Re: RateLimit Calculation

On Aug 11, 5:53 pm, shiplu wrote: > Scenario 1: No, you don't. Status updates are POSTs, which do not count against your 20,000 rate limit. Dewald

[twitter-dev] Re: Tweepy -- python library

Thanks Terry for catching that mistake. I'll get that fixed and pushed out ASAP. Josh On Tue, Aug 11, 2009 at 3:48 PM, Terry Jones wrote: > > On Mon, Aug 10, 2009 at 9:50 AM, Josh Roesslein > wrote: > > Hello twitter developers: > > Hi Josh > > That's great, it looks very clean. I'll give it a

[twitter-dev] Seeing same login issues right now as when DDoD happened

I've tried logging into a handful of sites built around the Twitter API without success. I'm seeing the same login issues right now as when the DDoD happened. Twitter is aware of the downtime issue on their status page, http://status.twitter.com, but are they aware of the API issues (e.g., being a

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

My guess is it's still ongoing. I'm seeing far more rejections per second, and the number of backed-off retries have also increased. Dewald On Aug 11, 5:37 pm, Andrew Badera wrote: > On Tue, Aug 11, 2009 at 4:11 PM, Alex Payne wrote: > > Our operations staff has informed me that the attack ceas

[twitter-dev] RateLimit Calculation

Hello, I need to be clear on something. Scenario 1: Suppose We have a twitter app where 1 user logs in everyday. And we have 1 whitelisted IP address. So If each user sends 3 tweets/hours, It will be over(3) the whitlisted IP rate limit, which is 2. In this case, we need to use extra

[twitter-dev] Re: created_at format

We do intend to move to unified format. This inconsistency is the result of the Search system being developed independently of Twitter before it was acquired. On Tue, Aug 11, 2009 at 13:33, Jonas wrote: > > I am using search.json and track.json and I noticed that the date > format for created_at

[twitter-dev] Re: Tweepy -- python library

On Mon, Aug 10, 2009 at 9:50 AM, Josh Roesslein wrote: > Hello twitter developers: Hi Josh That's great, it looks very clean. I'll give it a try soon. BTW, you raise NotImplemented in (at least) cache.py. That should instead be raise NotImplementedError. Terry

[twitter-dev] created_at format

I am using search.json and track.json and I noticed that the date format for created_at is different. search.json: Tue, 11 Aug 2009 20:23:36 + track.json: Tue Aug 11 20:23:36 + 2009 Is there a reason why Twitter uses different formats for the same information? Is there any interest in u

[twitter-dev] Re: Following Churn: Specific guidance needed

Owkaye > > > > Would be very helpful to know the definition of > > > > "quick" as relates to following churn suspensions. > > > > > > As Cameron pointed out earlier, as soon as they do > > > that, the following churners will adjust their > > > methods to be just inside that definition of OK.

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

On Tue, Aug 11, 2009 at 4:11 PM, Alex Payne wrote: > Our operations staff has informed me that the attack ceased several minutes > ago. Site performance should be returning to normal. > > On Tue, Aug 11, 2009 at 12:23, Alex Payne wrote: >> >> We're currently experiencing another wave of Distribut

[twitter-dev] How to develop flash widget with oauth

Hi, We're trying to figure out what's the recommended way to implement a widget (flash) with oauth. We actually already implemented it but just before we finished testing it broke with the latest changes. Now the questions are: 1. Would such an application be considered web or desktop. 2. Can we

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

I'm so happy gmail has a star feature, that deserved one. Tim. On Wed, Aug 12, 2009 at 7:28 AM, Dewald Pretorius wrote: > > I have a spare bazooka in my basement. Let me know. I can FedEx it to > you. > > Dewald > > On Aug 11, 4:23 pm, Alex Payne wrote: >> We're currently experiencing another w

[twitter-dev] Re: Tweepy -- python library

Thanks Alex for getting that added to the wiki. Ryan, thank you for the kind words glad you like it The streaming API is pretty cool and it was a top priority for me to include it. On Tue, Aug 11, 2009 at 3:13 PM, Ryan Sarver wrote: > > Awesome work Josh. Thanks for posting this out to everyone

[twitter-dev] Re: Search API Limits lowered?

The referrer is not as important as the user-agent. You can also put your URL in the user-agent instead. -Chad On Tue, Aug 11, 2009 at 4:09 PM, Larry Wright wrote: > In addition to setting a unique user-agent, I believe it was requested that > we set a referrer header that pointed back to a domai

[twitter-dev] Re: Tweepy -- python library

Awesome work Josh. Thanks for posting this out to everyone and I especially like the Streaming API support. Best, Ryan On Mon, Aug 10, 2009 at 9:50 AM, Josh Roesslein wrote: > Hello twitter developers: > > Just posting here to announce a library for python I have been putting > together. > It su

[twitter-dev] Re: Following Churn: Specific guidance needed

I have no problems debating with you, if you can keep your facts straight. Or rather, if you bother getting the facts in the first place. Dewald On Aug 11, 2:09 pm, TFT Media wrote: > I never said that your system does unfollow.  I point out that > tweetlater does bulk auto follow and bulk auto

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

Our operations staff has informed me that the attack ceased several minutes ago. Site performance should be returning to normal. On Tue, Aug 11, 2009 at 12:23, Alex Payne wrote: > We're currently experiencing another wave of Distributed Denial of Service > (DDoS) attacks against our system. Expe

[twitter-dev] Re: Search API Limits lowered?

In addition to setting a unique user-agent, I believe it was requested that we set a referrer header that pointed back to a domain. On Tue, Aug 11, 2009 at 9:30 AM, David Fisher wrote: > > While i haven't done scientific testing of this, I was able to run up > to 3-4 instances of my search scrip

[twitter-dev] Re: Twitter Update, 8/9 noon PST

Thanks for the update Dewald. Keep us posted if things change. Best, Ryan On Tue, Aug 11, 2009 at 6:26 AM, Dewald Pretorius wrote: > > Ryan, > > I am now doing geometric backoffs on 502s and connection refuses. > > I did not do exact math, but I seem to be getting between 2 and 5 > connection re

[twitter-dev] Re: Following Churn: Specific guidance needed

I never said that your system does unfollow. I point out that tweetlater does bulk auto follow and bulk auto return follow, and you do so using Twitter's follow limits as a guidepost. That's fine. But I thought it a bit funny how you then write "Amen" when someone said that if Twitter publishe

[twitter-dev] Re: OAuth vs. Basic authentication strictly on iPhone

Why would it be hosted in your app? Why can't you open Safari? On Tue, Aug 11, 2009 at 13:29, Bradley S. O'Hearne wrote: > Srikanth, > > By third party i meant some one like 'TwitViewer' (some one who would pay > and register their app in appstore and trick the users to believe in them > but who

[twitter-dev] Re: Following Churn: Specific guidance needed

> > > Would be very helpful to know the definition of "quick" > > > as relates to following churn suspensions. > > > > As Cameron pointed out earlier, as soon as they do that, > > the following churners will adjust their methods to be > > just inside that definition of OK. > > This seems like a r

[twitter-dev] Re: Search API Limits lowered?

Hi Dave, I'm not sure which twitter wrapper you are using. But if you're using Dan Croak's from here: http://github.com/dancroak/twitter-search You might need to update your gem, and make sure you specify the name of your app as the "agent" instead of using the default "twitter-search". Yu-Shan

[twitter-dev] Re: OAuth vs. Basic authentication strictly on iPhone

Srikanth, By third party i meant some one like 'TwitViewer' (some one who would pay and register their app in appstore and trick the users to believe in them but who do not work the way they were expected to ) That's not a valid use case for faulting the authentication mechanism. The use

[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th

I have a spare bazooka in my basement. Let me know. I can FedEx it to you. Dewald On Aug 11, 4:23 pm, Alex Payne wrote: > We're currently experiencing another wave of Distributed Denial of Service > (DDoS) attacks against our system. Expect periodic slowness and errors until > the attack passes

[twitter-dev] Timeouts and API Errors, Tuesday August 11th

We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience.

[twitter-dev] Re: Twitter Update, 8/9 noon PST

I appear to still be getting request timeouts on one of my servers. On Aug 9, 3:13 pm, Ryan Sarver wrote: > *Finally* have what we hope is good news for everyone. As of about 10 > minutes ago we have been able to restore critical parts of API operation > that should have great affect on your app

[twitter-dev] Re: Search API Limits lowered?

David, I don't know Ruby, so I don't know if this is possible. But, if possible you need to edit your copy of the Twitter API wrapper and set the user agent to something that is unique to your service. If you use the same user agent as everyone else who are using that wrapper, then you are goin

[twitter-dev] Re: Following Churn: Specific guidance needed

And if followed by an obvious spammer should we not block them and then let Twitter make it clear to other users how many times they've blocked. A few black marks against a spammer and they won't get followed back anymore. This is like the feedback rating in ebay it encourages you to behave

[twitter-dev] Re: Following Churn: Specific guidance needed

Step 1.) turn off email notifications (legitimat, but easily mitigated problem).Step 2.) getting spammed? Unfollow that user (question why you followed them in the first place). On Tue, Aug 11, 2009 at 8:35 AM, Kevin Mesiab wrote: > And here lies the slippery slope. > > On Tue, Aug 11, 2009 at

[twitter-dev] Re: Following Churn: Specific guidance needed

And here lies the slippery slope. On Tue, Aug 11, 2009 at 8:25 AM, owkaye wrote: > > > If users paid due diligence to those they follow and only > > followed those people who demonstrate some value to them, > > follower churn would not exist. Period. > > Obviously they won't so maybe it's time to

[twitter-dev] Re: Following Churn: Specific guidance needed

> If users paid due diligence to those they follow and only > followed those people who demonstrate some value to them, > follower churn would not exist. Period. Obviously they won't so maybe it's time to deal with reality rather than dreaming of a perfect world. Owkaye

[twitter-dev] Re: Following Churn: Specific guidance needed

Follower churn wouldn't exist, but getting hundreds of spam emails (about being followed) would still exist. I've got over 12,000 emails in my inbox about being followed on Twitter. Dozens of those are from the same users. Some weeks the same users unfollow and refollow me nonstop to try to get me

[twitter-dev] Re: Following Churn: Specific guidance needed

And a 'X people blocked this person' next to their details in the follows notification would help to identify which are spammers. ATB Neil On 11 Aug 2009, at 18:55, Kevin Mesiab wrote: This entire debate focuses on the wrong side of the coin. Follow churn exists as a side effect of the impro

[twitter-dev] Re: Tweepy -- python library

Thanks for your library, Josh! I've added it to http://apiwiki.twitter.com/Libraries#Python On Mon, Aug 10, 2009 at 09:50, Josh Roesslein wrote: > Hello twitter developers: > > Just posting here to announce a library for python I have been putting > together. > It supports pretty much the entire

[twitter-dev] Re: Following Churn: Specific guidance needed

This entire debate focuses on the wrong side of the coin. Follow churn exists as a side effect of the improper Twitter culture of reciprocating follows blindly. If users paid due diligence to those they follow and only followed those people who demonstrate some value to them, follower churn would

[twitter-dev] Re: Following Churn: Specific guidance needed

> > Would be very helpful to know the definition of "quick" > > as relates to following churn suspensions. > > As Cameron pointed out earlier, as soon as they do that, > the following churners will adjust their methods to be > just inside that definition of OK. This seems like a really short-sigh

[twitter-dev] Re: TwitterLand - Ruby wrapper for many Twitter-related APIs

Very cool! Thanks much. I've added it to http://apiwiki.twitter.com/Libraries#Ruby On Mon, Aug 10, 2009 at 10:18, Wynn Netherland wrote: > > I'd like to thank those of you who have released your own APIs for the > apps you've built on top of Twitter. If you're using Ruby, we've > bundled up our w

[twitter-dev] Re: External API Team App Test Site

One of the projects on our list is a continuous testing system, running from a machine outside our cluster. We have the test suite built to do it, just not the production-safe fixture data. On Mon, Aug 10, 2009 at 10:20, Dewald Pretorius wrote: > > Does the API team have a "test third-party app"

[twitter-dev] Re: Search API Limits lowered?

The user agent for each search request is the same. I'm using the Ruby Twitter API wrapper, so sending anything else with search requests isn't possible unless that is now deprecated. dave On Aug 11, 10:36 am, Andrew Badera wrote: > On Tue, Aug 11, 2009 at 10:30 AM, David Fisher wrote: > > > Wh

[twitter-dev] Re: Format of 'favorite status' URL

Even if passing "id" as a parameter works, it's not the documented behavior and isn't guaranteed to be supported indefinitely. Please specify IDs in-URL. On Tue, Aug 11, 2009 at 02:37, Mariusz wrote: > > Hi > > I am making small Twitter client in Java. Currently I make option > 'farourite status

[twitter-dev] Re: OAuth vs. Basic authentication strictly on iPhone

For the case of a dedicated application on a rich mobile platform like iPhone, I agree that OAuth does not offer a particularly different user experience. It does, however, provide us at Twitter the information we need to provide detailed usage analytics back to developers, as well as the data we n

[twitter-dev] Re: Following Churn: Specific guidance needed

An update on this thread: we have an inquiry out to our spam team to get more information about the metrics they use when policing mass-following/unfollowing. On Mon, Aug 10, 2009 at 15:12, IDOLpeeps wrote: > > Twitter recently started suspending accounts which bulk unfollow those > who don't fol

[twitter-dev] Re: OAuth vs. Basic authentication strictly on iPhone

By third party i meant some one like 'TwitViewer' (some one who would pay and register their app in appstore and trick the users to believe in them but who do not work the way they were expected to ) <> NO. With OAuth you are not keying in your password with in the app. <> I have to agree with

[twitter-dev] Re: Invalid / used nonce

We're having the same issue in our app, occurs sporadically in our logs - but I believe the cause with us is that: We're generating nonce values as a timestamp seeded sequence of random numbers We're creating an instance of the Oauth class that does this for each logged in user for the app Thus,

[twitter-dev] Re: Firehose feed.

You probably want either the follow streaming api or if you have a couple more users the shadow http://apiwiki.twitter.com/Streaming-API-Documentation#follow shadow See birddog above. Allows following up to 50,000 users. > URL: htt

[twitter-dev] Re: Following Churn: Specific guidance needed

On Mon, Aug 10, 2009 at 8:31 PM, IDOLpeeps wrote: > Lots of community members and developers are leaving Twitter because > of what appears to them to be arbitrary suspension of accounts they've > invested considerable time and good citizenship developing only to > have them removed without notice

[twitter-dev] Firehose feed.

I'm developing a Twitter Directory that is saving tweets locally via a cron that's making authenticated calls to friends_timeline every 10 minutes. Ideally, I'd like to update the directory more frequently. Is there a way to get a firehose feed for a single account, or some other way to approach

[twitter-dev] Re: Following Churn: Specific guidance needed

On Aug 11, 11:48 am, IDOLpeeps wrote: > Would be very helpful to know the definition of "quick" as relates to > following churn suspensions. As Cameron pointed out earlier, as soon as they do that, the following churners will adjust their methods to be just inside that definition of OK. Also, I

[twitter-dev] Re: Following Churn: Specific guidance needed

I agree my comparison to dictatorships is a stretch, but I was in a poetic mood and trying to emphasize the point that clarity is better than ambiguity. Twitter is obviously doing a tremendous job dealing with their explosive growth and dynamic nature of this new medium they've created. That sai

[twitter-dev] Read-only application cannot POST - only sometimes...

Hi, we currently built a twitter client into our application, but we are having trouble to get this to work. The setup: - registered OAuth client - our app is registered as read and write - I think we added the oauth_access_type=write* We have been testing for a couple of days now. Now the i

[twitter-dev] Re: OAuth vs. Basic authentication strictly on iPhone

Srikanth, Thank you for your thoughts -- good ones. Responses: But what if the app was developed by some thirdparty devs? you never know whether the password is stored or logged some where. I'm not sure who the "third party" is relative to -- if you are the user of an iPhone app, *every*

  1   2   >