[twitter-dev] Re: Noise-tweet regex repository
A Twitter client can do an HTTP get to here: http://talkingpuffin.appspot.com/filters/noise and expect lines of plain text like this: Just joined a twibe. Visit http\://twibes\.com/.* just joined a video chat at http\://tinychat\.com.*
[twitter-dev] Re: Noise-tweet regex repository
Please submit your candidate “noise tweets”: http://bit.ly/NoiseTweets I’ll review them and add them to the repository. These should generally be messages of the type of viral advertising— some service doing something for a Twitter user and then blabbing about it through the careless or inconsiderate user’s account.
[twitter-dev] I have a problem with update my status across API
When I try update my status sometimes I have success, but sometimes status not updated and I receive empty response and http code is 0 I have no exceed twitter limits. Why this problem may occur?
[twitter-dev] Re: Account management app - suspended accounts
On Thu, Oct 8, 2009 at 11:03 PM, Abraham Williams 4bra...@gmail.com wrote: Twitter's spam flagging system is an ever-changing trade secret. It is unlikely that you will get a direct answer. Have the 600 account holders contact Twitter support and hopefully they will get re-enabled quickly. Abraham Or, in the event that they ARE spammers, hopefully they WON'T. People writing, selling or hosting multiple-account management software need to become a LOT more circumspect in who they serve as clientele, and how precisely they serve them. There is a TON of abuse here, and greedy people need to learn a lesson. Not saying that's the case with the OP, but I'm EXTREMELY happy to see more aggressive filtering going on! (And looking forward to the Address Book!) ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera
[twitter-dev] Re: Have you read the OneForty.com Developer Contract?
Laura, Sounds like you're taking some of the right steps to make your offering better for everyone concerned. I look forward to seeing the results of your efforts. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Fri, Oct 9, 2009 at 1:05 AM, Pistachio pistachioconsult...@gmail.com wrote: Andrew us absolutely correct. I personally bear full responsibility for letting that flawed contract get into production, even on a beta. It was likewise my error of judgment to assume that the alpha testers had been fine with the proposed contract merely because we had not received adverse feedback. We're listening. We're learning. Our comment on Bradley's post (http://bit.ly/DgM40) summarizes some of the contentious points we're revising, but there are others. To make this right, we'd like to better engage the TwitterAPI community in reviewing our next version. We are also separating the claiming terms from the resale terms. One more thing worth mentioning, we held off on building features that will allow developers to offer items for sale because we want to work that - and the related contract issues - out in close cooperation with developers. We'd love to hear from you if you want to have a voice on that. I've been sending out my cell # on all emails bound for developers because we want to be extremely accessible to developers. on email, Twitter, IRC... We will be working hard to earn your trust and to discover how we can better serve. Warmly, Laura Fitton la...@oneforty.com (sent from @pistachio: RT @dwroelands @oneforty needs to change their developer contract #onefortycontract http://bit.ly/DgM40 //we're seeking feedback) On Oct 8, 10:21 pm, Andrew Badera and...@badera.us wrote: All else aside ... lawyers complicate things? Maybe, but you don't launch a product/platform and expect commitment from outside parties until YOU are happy with what YOUR lawyers have produced and thus YOU are offering to the outside world. There's no defense for a questionable contract. You stand behind your contract, or you don't publish it. Period. ∞ Andy Badera ∞+1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Thu, Oct 8, 2009 at 10:16 PM, Michael Ivey michael.i...@gmail.com wrote: OneForty is not a developer-friendly platform. I think this is a demonstrably false statement. All of my interactions with Laura and the 140 team have been very positive, and she's made it clear that they're working on the contract. Sometimes lawyers overcomplicate things, and it takes time to dial it back. And yes, when I claimed Twitpay I balked at the contract initially. We don't have an app to sell, so none of it applied to us, and I knew Laura was working on it, so I went ahead with the registration. Whether you sign it or not, I hope people will give Laura and her team time to sort this out. She's a good person, and has shown a real desire to make something good here. -- ivey On Thu, Oct 8, 2009 at 8:24 PM, Duane Roelands duane.roela...@gmail.com wrote: I read it, and I was horrified. So, I logged into IRC and found two members of the OneForty development team. I asked them to remove my application from the directory. They refused. OneForty is not a developer-friendly platform. On Oct 8, 7:44 pm, brad...@squeejee.com brad...@praexis.com wrote: wow, somehow managed to totally miss that thread... thanks! On Oct 8, 6:07 pm, Dewald Pretorius dpr...@gmail.com wrote: There's another thread herehttp://bit.ly/Owfvdwherethedeveloper contract also raised some eyebrows. Dewald On Oct 8, 7:25 pm, brad...@squeejee.com brad...@praexis.com wrote: There has been a lot of buzz around OneForty.com and what it will mean for all of us Twitter app developers. However, some of the things in their developer contract (that you have to agree to in order to claim your application on their side) gave us (Squeejee) pause after we decided to read the fine print. Please see read the contract for yourself (http://oneforty.com/terms/ publisher_contract), see our blog post with our concerns (http:// squeejee.com/blog/2009/10/08/questions-for-oneforty) and leave your comments! Laura Fitton, the founder of oneforty.com, has been very receptive and wants to engage in open dialogue about the contract. Please add to the discussion!
[twitter-dev] Re: Noise-tweet regex repository
Please don't forget the Ive just taken the 'WHOSE HOTTER' quiz and voted for Miley fucking Cyrus spam via @reply (and DM also) On Oct 9, 7:03 am, Dave Briccetti da...@davebsoft.com wrote: A Twitter client can do an HTTP get to here: http://talkingpuffin.appspot.com/filters/noise and expect lines of plain text like this: Just joined a twibe. Visit http\://twibes\.com/.* just joined a video chat at http\://tinychat\.com.*
[twitter-dev] Re: Noise-tweet regex repository
ps. thats not the actual string. I'll paste actual noise here as I discover it though On Oct 9, 10:22 am, Sam Street sam...@gmail.com wrote: Please don't forget the Ive just taken the 'WHOSE HOTTER' quiz and voted for Miley fucking Cyrus spam via @reply (and DM also) On Oct 9, 7:03 am, Dave Briccetti da...@davebsoft.com wrote: A Twitter client can do an HTTP get to here: http://talkingpuffin.appspot.com/filters/noise and expect lines of plain text like this: Just joined a twibe. Visit http\://twibes\.com/.* just joined a video chat at http\://tinychat\.com.*
[twitter-dev] Re: OAuth + Mobile nightmare
Hi all, any update on this?it is still not clear when mobile applications could migrate ot OAuth and how long we could use basic auth? Thanks! On Sep 4, 3:36 pm, twittme_mobi nlupa...@googlemail.com wrote: in addition to storing the access token somewhere , wouldn't it be better if twitter delivermobilefriendly version of the oauth pages? On Aug 19, 12:14 am, JDG ghil...@gmail.com wrote: That's what you should be doing. There's no reason to get a new Access Token every time. Per the OAuth spec, you should probably code your app to handle an expired token gracefully. The spec states that tokens MAY expire -- Twitter currently does not expire theirs, though. However, that doesn't mean that they couldn't in the future. 2009/8/18 André Arruda arrud...@gmail.com I'm thinking about storing the access token in the phone so the user won't have to go through all the auth process everytime the program is opened. I hope i won't find any new surprises by doing this. 2009/8/18 Otávio Ribeiro otavio.ribe...@gmail.com no.. just the same problem. On Mon, Aug 17, 2009 at 3:09 PM, AArruda arrud...@gmail.com wrote: I've been developing a Java/MIDP Twitter client for the past two months, and i still need a couple more months to publish a beta version. A few days ago i found out that the update source (app name) is no longer customizable unless the client uses OAuth for authentication, which means that any update sent through my client is shown as from API instead of my app's name. I understand that OAuth is important for many security reasons, but it still has important issues withmobileapplications, forcing the user to open a page through amobiledevice, writing down the PIN, switching back to the app and logging in again is just hell. Not to mention the smartphones that don't support programs running in the background. The current API's methods shouldn't be restricted to OAuth unless these issues are solved first. We, developers andmobileusers, would be thankful. Is anyone using any other solution for OAuth andmobiledevices, if there is any? -- Internets. Serious business.
[twitter-dev] Re: I have a problem with update my status across API
I think it's just the REST methods hiccuping. I've have this happen like twice. On Oct 9, 2009, at 4:02 AM, gonandriy gonand...@gmail.com wrote: When I try update my status sometimes I have success, but sometimes status not updated and I receive empty response and http code is 0 I have no exceed twitter limits. Why this problem may occur?
[twitter-dev] Re: Mobile oAuth
Hi Jim, any news on that?How close are you to address this? Thanks. On Sep 7, 9:54 am, jim.renkel james.ren...@gmail.com wrote: I've opened a feature request for this in the issues database: http://code.google.com/p/twitter-api/issues/detail?id=1011 If you like this idea and / or think it's a good thing, please indicate your support both here and in the issues forum. If you don't like it and / or don't think it's so hot, I'd like to hear that too. Thank you in advance. Jim Renkel On Sep 5, 4:42 am, twittme_mobi nlupa...@googlemail.com wrote: Jim, Thanks for the broad summary, I fully agree with you. There should be some mechanism formobiledevices with less resources forOAuth. Regarding the source parameter of the Application, it is very important with regards of e-marketing of the application itself. Greetings! On Sep 5, 2:08 am, Jim Renkel james.ren...@gmail.com wrote: OAuthis great, in certain circumstances. In others, it's not so great. Circumstances for which it is great include: - consumer web sites; and - consumer client applications that have access to a reasonable browser on the client device in both cases with the qualification that the authorization pages of the service provider are in a language (e.g., English, Japanese, etc.) that is the same as that used by the consumer. In these circumstances,OAuthas defined by the specifications and implemented by twitter works very well. Circumstances for which it is not so great include: - consumer client applications that do not have access to a reasonable browser on the client device; and - consumer client applications and web sites that are in languages for which service authorization pages in those languages are not available. In these circumstances,OAuthas defined by the specifications and implemented by twitter does not work so well. Currently, in circumstances whereOAuthdoes not work very well, twitter client applications and web-sites can resort to Basic Authentication. The drawbacks to this are obvious: - the user must give their twitter password to the client; - at some point twitter will no longer support Basic Authentication; and - the source of tweets created by these clients is API rather than the client's name. Pooh pooh the last drawback if you will, but to some it is important. Now, the fact of the matter is that some users are perfectly comfortable in giving their twitter passwords to client applications and web-sites, even where those clients supportOAuth. I don't think these users should be penalized and forced to useOAuth if'n and when'n twitter drops support for Basic Authentication. And if'n and when'n twitter drops support for Basic Authentication, client applications and web-sites that now only support Basic Authentication will be forced to supportOAuth. Myself, I don't think that's an unreasonable requirement, but others may differ. And I don't think these creators should have to forgo having their client's name as the source of tweets their clients create, now or ever, just because their users chose to trust them to use Basic Authentication. So I propose the following enhancement to twitter'sOAuth implementation: Allow a userID and password to be included as optional parameters of an oauth/access_token request. If supplied and authentic, they would cause a valid access token to be returned without the user having visited the authorize URL and approved the access. Alternately, the userID and password could be optional on an oauth/request_token request, in which case, if supplied and authentic, the request would return a valid access token, rather than a request token, again without the user having visited the authorize URL and approved the access. The advantage to this alternative is it reduces by one the number of API calls needed. I believe either of these alternatives is a viable solution for the circumstances where the existingOAuthimplementation does not work so great. Comments expected and welcome. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of twittme_mobi Sent: Friday, September 04, 2009 08:39 To: Twitter Development Talk Subject: [twitter-dev] Re:MobileoAuth I am also interested inmobileoath solution. twitter guys should think of something before deprecating basic auth On Aug 20, 8:01 am, Cameron Kaiser spec...@floodgap.com wrote: I have amobilebased twitter client in the field and have implemented oAuthfor this client. Some of the devices are either very low memory or have primitive browsers that dont support the rendering of the 'allow' / 'deny' access page (http://twitter.com/oauth/authorize). I
[twitter-dev] Re: I have a problem with update my status across API
0 is a common result when PHP and cURL can not connect to Twitter. Abraham On Fri, Oct 9, 2009 at 05:10, ryan alford ryanalford...@gmail.com wrote: I think it's just the REST methods hiccuping. I've have this happen like twice. On Oct 9, 2009, at 4:02 AM, gonandriy gonand...@gmail.com wrote: When I try update my status sometimes I have success, but sometimes status not updated and I receive empty response and http code is 0 I have no exceed twitter limits. Why this problem may occur? -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
[twitter-dev] Re: Have you read the OneForty.com Developer Contract?
Laura, You may want to consider temporarily removing the contract and maybe even the entire claiming feature while you're sorting this out. Why continue to ask developers to agree to something that you don't agree with yourself, and continue to tick off developers? It may be a prudent approach to relaunch that part of the service once all the ducks are in a row. Besides, the Twitter lawyers may also have something to say about the contract. Dewald On Oct 9, 2:05 am, Pistachio pistachioconsult...@gmail.com wrote: Andrew us absolutely correct. I personally bear full responsibility for letting that flawed contract get into production, even on a beta. It was likewise my error of judgment to assume that the alpha testers had been fine with the proposed contract merely because we had not received adverse feedback. We're listening. We're learning. Our comment on Bradley's post (http://bit.ly/DgM40) summarizes some of the contentious points we're revising, but there are others. To make this right, we'd like to better engage the TwitterAPI community in reviewing our next version. We are also separating the claiming terms from the resale terms. One more thing worth mentioning, we held off on building features that will allow developers to offer items for sale because we want to work that - and the related contract issues - out in close cooperation with developers. We'd love to hear from you if you want to have a voice on that. I've been sending out my cell # on all emails bound for developers because we want to be extremely accessible to developers. on email, Twitter, IRC... We will be working hard to earn your trust and to discover how we can better serve. Warmly, Laura Fitton la...@oneforty.com (sent from @pistachio: RT @dwroelands @oneforty needs to change their developer contract #onefortycontracthttp://bit.ly/DgM40//we're seeking feedback) On Oct 8, 10:21 pm, Andrew Badera and...@badera.us wrote: All else aside ... lawyers complicate things? Maybe, but you don't launch a product/platform and expect commitment from outside parties until YOU are happy with what YOUR lawyers have produced and thus YOU are offering to the outside world. There's no defense for a questionable contract. You stand behind your contract, or you don't publish it. Period. ∞ Andy Badera ∞+1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Thu, Oct 8, 2009 at 10:16 PM, Michael Ivey michael.i...@gmail.com wrote: OneForty is not a developer-friendly platform. I think this is a demonstrably false statement. All of my interactions with Laura and the 140 team have been very positive, and she's made it clear that they're working on the contract. Sometimes lawyers overcomplicate things, and it takes time to dial it back. And yes, when I claimed Twitpay I balked at the contract initially. We don't have an app to sell, so none of it applied to us, and I knew Laura was working on it, so I went ahead with the registration. Whether you sign it or not, I hope people will give Laura and her team time to sort this out. She's a good person, and has shown a real desire to make something good here. -- ivey On Thu, Oct 8, 2009 at 8:24 PM, Duane Roelands duane.roela...@gmail.com wrote: I read it, and I was horrified. So, I logged into IRC and found two members of the OneForty development team. I asked them to remove my application from the directory. They refused. OneForty is not a developer-friendly platform. On Oct 8, 7:44 pm, brad...@squeejee.com brad...@praexis.com wrote: wow, somehow managed to totally miss that thread... thanks! On Oct 8, 6:07 pm, Dewald Pretorius dpr...@gmail.com wrote: There's another thread herehttp://bit.ly/Owfvdwherethedeveloper contract also raised some eyebrows. Dewald On Oct 8, 7:25 pm, brad...@squeejee.com brad...@praexis.com wrote: There has been a lot of buzz around OneForty.com and what it will mean for all of us Twitter app developers. However, some of the things in their developer contract (that you have to agree to in order to claim your application on their side) gave us (Squeejee) pause after we decided to read the fine print. Please see read the contract for yourself (http://oneforty.com/terms/ publisher_contract), see our blog post with our concerns (http:// squeejee.com/blog/2009/10/08/questions-for-oneforty) and leave your comments! Laura Fitton, the founder of oneforty.com, has been very receptive and wants to engage in open dialogue about the contract. Please add to the discussion!
[twitter-dev] Re: I have a problem with update my status across API
What about an empty response? I get it from my .Net API. I've only had it happen twice. On Fri, Oct 9, 2009 at 6:21 AM, Abraham Williams 4bra...@gmail.com wrote: 0 is a common result when PHP and cURL can not connect to Twitter. Abraham On Fri, Oct 9, 2009 at 05:10, ryan alford ryanalford...@gmail.com wrote: I think it's just the REST methods hiccuping. I've have this happen like twice. On Oct 9, 2009, at 4:02 AM, gonandriy gonand...@gmail.com wrote: When I try update my status sometimes I have success, but sometimes status not updated and I receive empty response and http code is 0 I have no exceed twitter limits. Why this problem may occur? -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
[twitter-dev] Re: Account management app - suspended accounts
Absolutely true. on both counts... However, not so long ago Twitter banned many accounts by mistake because they used tweetlater. The trouble is on one hand Twitter supports, encourages the creation of these applications and on the other hand fails horribly to provide sufficient guidelines about their use. I know one of the accounts was purely posting quotes of a dead comedian, and this went down very well - had a big following of people who regularly responded positively. Account status today? Suspended. Why? Who knows. Who is being asked about this? Me. It is not up to the 600 individuals to contact Twitter but rather for Twitter to explain what is changing so people can ensure they are within these new parameters. On Oct 9, 10:07 am, Andrew Badera and...@badera.us wrote: On Thu, Oct 8, 2009 at 11:03 PM, Abraham Williams 4bra...@gmail.com wrote: Twitter's spam flagging system is an ever-changing trade secret. It is unlikely that you will get a direct answer. Have the 600 account holders contact Twitter support and hopefully they will get re-enabled quickly. Abraham Or, in the event that they ARE spammers, hopefully they WON'T. People writing, selling or hosting multiple-account management software need to become a LOT more circumspect in who they serve as clientele, and how precisely they serve them. There is a TON of abuse here, and greedy people need to learn a lesson. Not saying that's the case with the OP, but I'm EXTREMELY happy to see more aggressive filtering going on! (And looking forward to the Address Book!) ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera
[twitter-dev] Re: twitter.com/followers/befriend_all ?
Bump.. On Wed, Oct 7, 2009 at 2:29 PM, Rick Yazwinski rick.yazwin...@gmail.com wrote: I see comments via google about having a bot call this regularily to make sure your bot follows anyone following the bot... makes sense (rather than getting all friends and all followers and issuing seperate friend requests), however I see no reference to it on the twitter api site. Is this legit? When I call it it just redirects to my home page. Rick...
[twitter-dev] Search API - HTTP Response Code 502, what to do?
Hey there, I'm posting this because I'm concerned with the possibility of exceeding the rate limit and so I would like advice on what to do. I have an application that does several queries to the Search API on several Geocode locations. The twitter Search API documentation clearly states that if I hit a 503 status code I should (and I do) have my application wait the time specified in the Retry-After header. However I haven't yet hit any 503 status codes, instead I'm receiving a few 502 http status codes with the infamous Time out! whale message. My question is: How should I process these? Since there is no Retry-After header on 502 codes I can't know how much time to wait. Will it influence my rate limiting, and get me banned if I ignore them? How long should I wait before the next request? (a few seconds, minutes, until the next hour?) Would appreciate any input I could get on this :) Thank you.
[twitter-dev] Re: Noise-tweet regex repository
Don't paste them here. Please go to the link he posted above. Pasting them here would be, in effect, noise. On Fri, Oct 9, 2009 at 03:22, Sam Street sam...@gmail.com wrote: ps. thats not the actual string. I'll paste actual noise here as I discover it though On Oct 9, 10:22 am, Sam Street sam...@gmail.com wrote: Please don't forget the Ive just taken the 'WHOSE HOTTER' quiz and voted for Miley fucking Cyrus spam via @reply (and DM also) On Oct 9, 7:03 am, Dave Briccetti da...@davebsoft.com wrote: A Twitter client can do an HTTP get to here: http://talkingpuffin.appspot.com/filters/noise and expect lines of plain text like this: Just joined a twibe. Visit http\://twibes\.com/.* just joined a video chat at http\://tinychat\.com.* -- Internets. Serious business.
[twitter-dev] Re: Noise-tweet regex repository
To add a bit more usefulness to this, I'd suggest adding some sort of Bayesian filter and domain white/black listing. Just my 2 cents. Great idea though. On Oct 9, 9:40 am, JDG ghil...@gmail.com wrote: Don't paste them here. Please go to the link he posted above. Pasting them here would be, in effect, noise. On Fri, Oct 9, 2009 at 03:22, Sam Street sam...@gmail.com wrote: ps. thats not the actual string. I'll paste actual noise here as I discover it though On Oct 9, 10:22 am, Sam Street sam...@gmail.com wrote: Please don't forget the Ive just taken the 'WHOSE HOTTER' quiz and voted for Miley fucking Cyrus spam via @reply (and DM also) On Oct 9, 7:03 am, Dave Briccetti da...@davebsoft.com wrote: A Twitter client can do an HTTP get to here: http://talkingpuffin.appspot.com/filters/noise and expect lines of plain text like this: Just joined a twibe. Visit http\://twibes\.com/.* just joined a video chat at http\://tinychat\.com.* -- Internets. Serious business.
[twitter-dev] Re: twitter.com/followers/befriend_all ?
There's no need to bump threads here. As for your question, I believe the befriend_all link was available a year (or two) ago, until people abused it. If I remember correctly, it was accessible through a GET request which made it easy to abuse (shorten the link, tweet it out, boom!). Someone please correct me if I'm wrong, though. :) -- Chris Thomson On 2009-10-09, at 8:29 AM, Rick Yazwinski wrote: Bump.. On Wed, Oct 7, 2009 at 2:29 PM, Rick Yazwinski rick.yazwin...@gmail.com wrote: I see comments via google about having a bot call this regularily to make sure your bot follows anyone following the bot... makes sense (rather than getting all friends and all followers and issuing seperate friend requests), however I see no reference to it on the twitter api site. Is this legit? When I call it it just redirects to my home page. Rick...
[twitter-dev] Re: Search API - HTTP Response Code 502, what to do?
Get used to receiving random 502 (and other response codes) from the Twitter API. If you don't know exactly what the code means I suggest retrying it. If it's explicit that you're being rate limited then wait before you retry. http://twitter.com/jkalucki/status/4686847704 http://twitter.com/jkalucki/status/4686422873 On Oct 9, 5:12 am, Zamite ekzam...@gmail.com wrote: Hey there, I'm posting this because I'm concerned with the possibility of exceeding the rate limit and so I would like advice on what to do. I have an application that does several queries to the Search API on several Geocode locations. The twitter Search API documentation clearly states that if I hit a 503 status code I should (and I do) have my application wait the time specified in the Retry-After header. However I haven't yet hit any 503 status codes, instead I'm receiving a few 502 http status codes with the infamous Time out! whale message. My question is: How should I process these? Since there is no Retry-After header on 502 codes I can't know how much time to wait. Will it influence my rate limiting, and get me banned if I ignore them? How long should I wait before the next request? (a few seconds, minutes, until the next hour?) Would appreciate any input I could get on this :) Thank you.
[twitter-dev] Re: Account management app - suspended accounts
Openness about abuse is generally counter-productive for everyone. For example, opaque limits are harder to game and give better detection signals. Also, practically, limits need to be adjusted without notice to respond changing attacks. In the end, valid access that is difficult to distinguish from access overwhelmingly used for invalid purposes are sometimes, sadly, going to get caught in a low-latency high-volume countermeasure system. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Oct 9, 5:23 am, SuperCerial s...@cyberdyneseo.com wrote: Absolutely true. on both counts... However, not so long ago Twitter banned many accounts by mistake because they used tweetlater. The trouble is on one hand Twitter supports, encourages the creation of these applications and on the other hand fails horribly to provide sufficient guidelines about their use. I know one of the accounts was purely posting quotes of a dead comedian, and this went down very well - had a big following of people who regularly responded positively. Account status today? Suspended. Why? Who knows. Who is being asked about this? Me. It is not up to the 600 individuals to contact Twitter but rather for Twitter to explain what is changing so people can ensure they are within these new parameters. On Oct 9, 10:07 am, Andrew Badera and...@badera.us wrote: On Thu, Oct 8, 2009 at 11:03 PM, Abraham Williams 4bra...@gmail.com wrote: Twitter's spam flagging system is an ever-changing trade secret. It is unlikely that you will get a direct answer. Have the 600 account holders contact Twitter support and hopefully they will get re-enabled quickly. Abraham Or, in the event that they ARE spammers, hopefully they WON'T. People writing, selling or hosting multiple-account management software need to become a LOT more circumspect in who they serve as clientele, and how precisely they serve them. There is a TON of abuse here, and greedy people need to learn a lesson. Not saying that's the case with the OP, but I'm EXTREMELY happy to see more aggressive filtering going on! (And looking forward to the Address Book!) ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera
[twitter-dev] Re: Account management app - suspended accounts
How about you just answer my question? What you're saying is mankind is wrong to live by well defined and concrete rules. I could steal that car and it will be ok, then again it might not - what don't you try and find out. You really think that's right? Of course the reality is Twitter is another laissez fair bums on seats driven site and as google proved, there is nothing like the abiltiy to change the rules on a whim, or hide a problem for a company of this ilk. On Oct 9, 6:07 pm, John Kalucki jkalu...@gmail.com wrote: Openness about abuse is generally counter-productive for everyone. For example, opaque limits are harder to game and give better detection signals. Also, practically, limits need to be adjusted without notice to respond changing attacks. In the end, valid access that is difficult to distinguish from access overwhelmingly used for invalid purposes are sometimes, sadly, going to get caught in a low-latency high-volume countermeasure system. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Oct 9, 5:23 am, SuperCerial s...@cyberdyneseo.com wrote: Absolutely true. on both counts... However, not so long ago Twitter banned many accounts by mistake because they used tweetlater. The trouble is on one hand Twitter supports, encourages the creation of these applications and on the other hand fails horribly to provide sufficient guidelines about their use. I know one of the accounts was purely posting quotes of a dead comedian, and this went down very well - had a big following of people who regularly responded positively. Account status today? Suspended. Why? Who knows. Who is being asked about this? Me. It is not up to the 600 individuals to contact Twitter but rather for Twitter to explain what is changing so people can ensure they are within these new parameters. On Oct 9, 10:07 am, Andrew Badera and...@badera.us wrote: On Thu, Oct 8, 2009 at 11:03 PM, Abraham Williams 4bra...@gmail.com wrote: Twitter's spam flagging system is an ever-changing trade secret. It is unlikely that you will get a direct answer. Have the 600 account holders contact Twitter support and hopefully they will get re-enabled quickly. Abraham Or, in the event that they ARE spammers, hopefully they WON'T. People writing, selling or hosting multiple-account management software need to become a LOT more circumspect in who they serve as clientele, and how precisely they serve them. There is a TON of abuse here, and greedy people need to learn a lesson. Not saying that's the case with the OP, but I'm EXTREMELY happy to see more aggressive filtering going on! (And looking forward to the Address Book!) ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera- Hide quoted text - - Show quoted text -
[twitter-dev] Re: twitter.com/followers/befriend_all ?
If it is not in the Twitter API documentation, if the API call not work for you, if you see no reference to it here on this forum... I am at a loss why you are asking whether it exists or not. Clearly it does not. On Oct 7, 11:29 am, Rick Yazwinski rick.yazwin...@gmail.com wrote: I see comments via google about having a bot call this regularily to make sure your bot follows anyone following the bot... makes sense (rather than getting all friends and all followers and issuing seperate friend requests), however I see no reference to it on the twitter api site. Is this legit? When I call it it just redirects to my home page. Rick...
[twitter-dev] Re: Account management app - suspended accounts
Openness about abuse is generally counter-productive for everyone. For example, opaque limits are harder to game and give better detection signals. Also, practically, limits need to be adjusted without notice to respond changing attacks. In the end, valid access that is difficult to distinguish from access overwhelmingly used for invalid purposes are sometimes, sadly, going to get caught in a low-latency high-volume countermeasure system. How about you just answer my question? What you're saying is mankind is wrong to live by well defined and concrete rules. Um, no. What John is saying is that Twitter doesn't live by them. And, considering that Twitter is a relatively new medium, that's pretty much by definition. Of course the reality is Twitter is another laissez fair bums on seats driven site and as google proved, there is nothing like the abiltiy to change the rules on a whim, or hide a problem for a company of this ilk. The line for Jaiku starts over there. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Prediction is very difficult, especially ... about the future. -- Niels Bohr
[twitter-dev] Re: Account management app - suspended accounts
Yes exactly - Twitter doesnt live by a coherent ruleset. It openly promotes bots yet suspends people without any warning or information. It opens its doors to be gamed and kicks people out randomly. This lack of transparant rules is working like a charm isnt it. On Oct 9, 7:44 pm, Cameron Kaiser spec...@floodgap.com wrote: Openness about abuse is generally counter-productive for everyone. For example, opaque limits are harder to game and give better detection signals. Also, practically, limits need to be adjusted without notice to respond changing attacks. In the end, valid access that is difficult to distinguish from access overwhelmingly used for invalid purposes are sometimes, sadly, going to get caught in a low-latency high-volume countermeasure system. How about you just answer my question? What you're saying is mankind is wrong to live by well defined and concrete rules. Um, no. What John is saying is that Twitter doesn't live by them. And, considering that Twitter is a relatively new medium, that's pretty much by definition. Of course the reality is Twitter is another laissez fair bums on seats driven site and as google proved, there is nothing like the abiltiy to change the rules on a whim, or hide a problem for a company of this ilk. The line for Jaiku starts over there. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- Prediction is very difficult, especially ... about the future. -- Niels Bohr
[twitter-dev] Re: Account management app - suspended accounts
John, With reference to used for invalid purposes in your post. That begs the question, what exactly constitute invalid purposes? From a Twitter purist's point of view, anything other than What are you doing? constitutes an invalid purpose. I'd venture to say that very few people use Twitter for What are you doing? No way do I want to or need to tell a few thousand strangers (and have it indexed by Google) where I am right now, what I am doing right now, or what I am having for lunch. Facebook is a far better platform for that, where one has privacy and a hand-picked audience who just might care. Twitter created a platform that is ideally suited for the marketers and mega-phones. Why else would people actually spend money to buy followers, and get involved in all kinds of schemes to acquire more followers? Because the way your platform works enables and encourages that type of purpose. When you find yourself spending many frustrating hours of fighting invalid use, you are in effect fighting the animal that Twitter created. One cannot be angry with users when they use the service in unforeseen ways, especially when the service enables that type of use. The easiest way to fight invalid use is to change Twitter so that only valid use is possible. When Facebook realized that they were enabling the mega-phone type, they quickly changed their system to discourage that use by limiting the number of friends one can have. You either have to do that, or you have to expand your definition of valid use, and rejoice in the success it brings you when people use your service in unexpected and unanticipated ways. By having a flexible platform that encourages many purposes and trying to limit those purposes only to what you deem valid, you are forever going to fight a losing battle. And, you are laying down rich soil for the competition to germinate. If every who does not stick to What are you doing? abandoned Twitter today, you will be back to where you were in your early days in terms of size and relevance. Dewald On Oct 9, 2:07 pm, John Kalucki jkalu...@gmail.com wrote: Openness about abuse is generally counter-productive for everyone. For example, opaque limits are harder to game and give better detection signals. Also, practically, limits need to be adjusted without notice to respond changing attacks. In the end, valid access that is difficult to distinguish from access overwhelmingly used for invalid purposes are sometimes, sadly, going to get caught in a low-latency high-volume countermeasure system. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Oct 9, 5:23 am, SuperCerial s...@cyberdyneseo.com wrote: Absolutely true. on both counts... However, not so long ago Twitter banned many accounts by mistake because they used tweetlater. The trouble is on one hand Twitter supports, encourages the creation of these applications and on the other hand fails horribly to provide sufficient guidelines about their use. I know one of the accounts was purely posting quotes of a dead comedian, and this went down very well - had a big following of people who regularly responded positively. Account status today? Suspended. Why? Who knows. Who is being asked about this? Me. It is not up to the 600 individuals to contact Twitter but rather for Twitter to explain what is changing so people can ensure they are within these new parameters. On Oct 9, 10:07 am, Andrew Badera and...@badera.us wrote: On Thu, Oct 8, 2009 at 11:03 PM, Abraham Williams 4bra...@gmail.com wrote: Twitter's spam flagging system is an ever-changing trade secret. It is unlikely that you will get a direct answer. Have the 600 account holders contact Twitter support and hopefully they will get re-enabled quickly. Abraham Or, in the event that they ARE spammers, hopefully they WON'T. People writing, selling or hosting multiple-account management software need to become a LOT more circumspect in who they serve as clientele, and how precisely they serve them. There is a TON of abuse here, and greedy people need to learn a lesson. Not saying that's the case with the OP, but I'm EXTREMELY happy to see more aggressive filtering going on! (And looking forward to the Address Book!) ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera
[twitter-dev] Re: Account management app - suspended accounts
As someone who's been a Twitter user since March 2007 or so, and a developer since late 2007, I have a hard time disagreeing with anything I've seen from Twitter on spam policies. In general, it seems to me, if you're not a douchebag, you don't get suspended. With one or two exceptions in that entire time. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Fri, Oct 9, 2009 at 2:54 PM, freefall tehgame...@googlemail.com wrote: Yes exactly - Twitter doesnt live by a coherent ruleset. It openly promotes bots yet suspends people without any warning or information. It opens its doors to be gamed and kicks people out randomly. This lack of transparant rules is working like a charm isnt it. On Oct 9, 7:44 pm, Cameron Kaiser spec...@floodgap.com wrote: Openness about abuse is generally counter-productive for everyone. For example, opaque limits are harder to game and give better detection signals. Also, practically, limits need to be adjusted without notice to respond changing attacks. In the end, valid access that is difficult to distinguish from access overwhelmingly used for invalid purposes are sometimes, sadly, going to get caught in a low-latency high-volume countermeasure system. How about you just answer my question? What you're saying is mankind is wrong to live by well defined and concrete rules. Um, no. What John is saying is that Twitter doesn't live by them. And, considering that Twitter is a relatively new medium, that's pretty much by definition. Of course the reality is Twitter is another laissez fair bums on seats driven site and as google proved, there is nothing like the abiltiy to change the rules on a whim, or hide a problem for a company of this ilk. The line for Jaiku starts over there. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- Prediction is very difficult, especially ... about the future. -- Niels Bohr
[twitter-dev] Re: Twitter Geo stuff
On that note, is it known if the setting to opt in will be exposed in the account/update_profile API? On Oct 4, 4:13 am, Rich rhyl...@gmail.com wrote: TheGeotag is only populated firstly if the user posting the tweet has opted in via Twitter's website (which hasn't been enabled yet) and secondlyGeodata was submitted with that tweet On Oct 4, 4:41 am, Patrick kenned...@gmail.com wrote: I have been reading about the TwitterGeostuff - it all sounds exciting - and I'd like to start playing with it even it's not fully prime time. Supposedly it's available to some extent via the API. I see the geo/ tag in my feed, and I wonder how I can opt in and get it populated. Also, can someone provide an example of how the location field could be populated - I have cURL examples to update location, and I have my location info via my Nokia GPS-assisted phone, so I'd like to see an example on now to simulate the future geo/ feature, i.e., update location field as if it were geo/, if I cannot yet opt in to geo/.- Hide quoted text - - Show quoted text -
[twitter-dev] Announcing GoTwitr
/* Disclaimer - this app is not officially affiliated with Twitter. No Twitter endorsement implied. */ First, I’d like to say thanks to everyone on this board for sharing their thoughts, questions, and help every day, and also thank Twitter for creating a Great API for us to use. Today we’re launching a new site call GoTwitr - www.gotwitr.com GoTwitr is a Twitter Automation website designed to help people grow and nourish their Twitter communities. We’ve spent a great deal of effort trying to make this an application that works well for everyone in the Twitter community - (New Users, Power Users, and of course Twitter.) GoTwitr takes a new approach to growing your community. It provides you with a set of tools to send out beautiful HTML invitations to invite people to your Twitter community. You can send invitations via email, on websites or blogs, or even to Twitter users. (This blog has some screen shots of the HTML invitations - http://www.gotwitr.com/content/gotwitr-site-built-drupal ) It also allows you to create a group of friends and attach them to an invitation so when your invitee decides to follow you; they can also follow your friends at the same time. This is a great way to get new people started on Twitter. Here are a few technical things we did to help people find quality connections without just blindly mass following: 1. GoTwitr lets you preview everyone you follow or un-follow. Many other Twitter automation tools bulk follow people. This feature ensures that you get a chance to decide if you want to follow or not, and helps to reduce or eliminate follower churn. 2. GoTwitr delivers people to your website. Every invitation accepted will take your recipient to your website, twitter page, blog, or any other URL. 3. 100% Oauth - You don't have to give away your Twitter password to use all the features of our service. This also provides you with easy sign in and registration. 4. API Limits – No user can hit the Twitter API more than 1000 times in a 24 hour period. Thanks again everyone for sharing your daily tips and insights. Please visit and have a look: http://www.gotwitr.com All feedback welcome. Jim Fulford
[twitter-dev] Preview Access to Lists API?
So, I am hearing from a few people that they have advanced preview access to the Lists API, the feature that was announced recently. It is a cool thing to see a steady stream of feature additions in the pipeline. I look forward to adding Lists to Nambu. First, please confirm that this is true, that some people have access to these APIs while the rest of us don't even know what the feature set actually is, and what we will be possible via the API. Second, if true, can Twitter please at least publish these APIs as beta specifications as you have done with the retweet APIs, so the rest of us second-tier developers can at least see what they will *exactly* be? With that we can at least prepare implementations. I all really want to know is what lists will *exactly* be as offered by the Twitter API. At the moment many of us that are not blessed services dont even know what they are, let alone have a chance to already build features on top of them, while those are that are blessed are already working on them. --ejw Eric Woodward Email: e...@nambu.com
[twitter-dev] Twitter Translator
Hi everybody, I just received an e-mail to join the translation program, nice ! But on my twitter homepage, the panel translate is not visible and the page on http://twitter.com/translate/translator/ is empty. Do you know what I can do to activate the translation panel ? Thanks Brice - @bgouban
[twitter-dev] Re: Account management app - suspended accounts
One more thought about this. Audience (followers) is to Twitter what PageRank is to Google. Twitter created a commodity when it enabled the unlimited follower capability. As long as it is a commodity, money-motivated people will continue to exploit it as a commodity, just like they exploit Google's PageRank. The entire SEO industry is centered around ranking high in SE's, with Google's PageRank being one of the most coveted commodities. You can expect to see an entire industry forming around gaining Twitter followers. And very clever people will continuously try to outsmart you to circumvent any counter-measures that you try to implement. The only way to win that battle is to make followers a non-commodity. Dewald On Oct 9, 4:04 pm, Dewald Pretorius dpr...@gmail.com wrote: John, With reference to used for invalid purposes in your post. That begs the question, what exactly constitute invalid purposes? From a Twitter purist's point of view, anything other than What are you doing? constitutes an invalid purpose. I'd venture to say that very few people use Twitter for What are you doing? No way do I want to or need to tell a few thousand strangers (and have it indexed by Google) where I am right now, what I am doing right now, or what I am having for lunch. Facebook is a far better platform for that, where one has privacy and a hand-picked audience who just might care. Twitter created a platform that is ideally suited for the marketers and mega-phones. Why else would people actually spend money to buy followers, and get involved in all kinds of schemes to acquire more followers? Because the way your platform works enables and encourages that type of purpose. When you find yourself spending many frustrating hours of fighting invalid use, you are in effect fighting the animal that Twitter created. One cannot be angry with users when they use the service in unforeseen ways, especially when the service enables that type of use. The easiest way to fight invalid use is to change Twitter so that only valid use is possible. When Facebook realized that they were enabling the mega-phone type, they quickly changed their system to discourage that use by limiting the number of friends one can have. You either have to do that, or you have to expand your definition of valid use, and rejoice in the success it brings you when people use your service in unexpected and unanticipated ways. By having a flexible platform that encourages many purposes and trying to limit those purposes only to what you deem valid, you are forever going to fight a losing battle. And, you are laying down rich soil for the competition to germinate. If every who does not stick to What are you doing? abandoned Twitter today, you will be back to where you were in your early days in terms of size and relevance. Dewald On Oct 9, 2:07 pm, John Kalucki jkalu...@gmail.com wrote: Openness about abuse is generally counter-productive for everyone. For example, opaque limits are harder to game and give better detection signals. Also, practically, limits need to be adjusted without notice to respond changing attacks. In the end, valid access that is difficult to distinguish from access overwhelmingly used for invalid purposes are sometimes, sadly, going to get caught in a low-latency high-volume countermeasure system. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Oct 9, 5:23 am, SuperCerial s...@cyberdyneseo.com wrote: Absolutely true. on both counts... However, not so long ago Twitter banned many accounts by mistake because they used tweetlater. The trouble is on one hand Twitter supports, encourages the creation of these applications and on the other hand fails horribly to provide sufficient guidelines about their use. I know one of the accounts was purely posting quotes of a dead comedian, and this went down very well - had a big following of people who regularly responded positively. Account status today? Suspended. Why? Who knows. Who is being asked about this? Me. It is not up to the 600 individuals to contact Twitter but rather for Twitter to explain what is changing so people can ensure they are within these new parameters. On Oct 9, 10:07 am, Andrew Badera and...@badera.us wrote: On Thu, Oct 8, 2009 at 11:03 PM, Abraham Williams 4bra...@gmail.com wrote: Twitter's spam flagging system is an ever-changing trade secret. It is unlikely that you will get a direct answer. Have the 600 account holders contact Twitter support and hopefully they will get re-enabled quickly. Abraham Or, in the event that they ARE spammers, hopefully they WON'T. People writing, selling or hosting multiple-account management software need to become a LOT more circumspect in who they serve as clientele, and how precisely they serve them. There is a TON of abuse here, and greedy
[twitter-dev] Re: Twitter Geo stuff
it will not (at least, that's what I've seen on the list thus far.) On Fri, Oct 9, 2009 at 09:18, Axthelm caxth...@openpathproducts.com wrote: On that note, is it known if the setting to opt in will be exposed in the account/update_profile API? On Oct 4, 4:13 am, Rich rhyl...@gmail.com wrote: TheGeotag is only populated firstly if the user posting the tweet has opted in via Twitter's website (which hasn't been enabled yet) and secondlyGeodata was submitted with that tweet On Oct 4, 4:41 am, Patrick kenned...@gmail.com wrote: I have been reading about the TwitterGeostuff - it all sounds exciting - and I'd like to start playing with it even it's not fully prime time. Supposedly it's available to some extent via the API. I see the geo/ tag in my feed, and I wonder how I can opt in and get it populated. Also, can someone provide an example of how the location field could be populated - I have cURL examples to update location, and I have my location info via my Nokia GPS-assisted phone, so I'd like to see an example on now to simulate the future geo/ feature, i.e., update location field as if it were geo/, if I cannot yet opt in to geo/.- Hide quoted text - - Show quoted text - -- Internets. Serious business.
[twitter-dev] Whitelisted IPs only work when authed?
I recently received email that confirmed my whitelisting status. I have several IPs whitelisted, as well as the account. From a shell on one of the whitelisted servers, I make a couple requests and then try: curl http://twitter.com/account/rate_limit_status.xml ?xml version=1.0 encoding=UTF-8? hash hourly-limit type=integer150/hourly-limit reset-time-in-seconds type=integer1255123230/reset-time-in- seconds reset-time type=datetime2009-10-09T21:20:30+00:00/reset-time remaining-hits type=integer147/remaining-hits /hash If, on the other hand, I try: curl -u username:password http://twitter.com/account/rate_limit_status.xml hash remaining-hits type=integer1/remaining-hits reset-time type=datetime2009-10-09T21:57:09+00:00/reset-time hourly-limit type=integer2/hourly-limit reset-time-in-seconds type=integer1255125429/reset-time-in- seconds /hash I was under the impression I did not have to auth if I was making calls from the API? Also: if I use my application's oauth credentials to generate an oauth_request and use the oauth URL, I am still getting the lower rate limit. Is this normal behavior?
[twitter-dev] Re: Account management app - suspended accounts
Agreed. What else is wefollow.com, which Twitter freely advertises, but a ranking of people by followers (just look at some of the top people in the categories and you have to ask yourself, wtf!?) When the value of a Twitter account is determined by followers (as apps like wefollow make clear), then people will obviously and naturally try to increase their follower counts. I mean, Twitter freely advertises twittercounter.com too... and that app even shows charted daily growth in followers, prompting viewers to wonder how they, too, can have such growth. And, personally, I don't necessarily see anything wrong with that. After all, which is more detrimental to the community, someone like Karl Rove or Rick Sanchez or Arnold Schwarzenegger using some auto- follow technique, or the 10s of 1000s of BS accounts tweeting about weight loss or promotional URL @replies to random people? I wish Twitter would focus it's anti-spam tactics MORE on the content of the tweet stream, rather than on some amorphous following abuse which they undercut by highlighting apps like wefollow. Or at least a combination of the two. There's too many accounts tweeting about weight loss, etc... and it's a shame when folks like Karl Rove, Rick Sanchez, and others get suspended because they apparently fell afoul of follow/unfollow. A quick look at their tweet stream and it is apparent they are not spammers. There's too many false positives in the current anti-spam dragnets, and far too little focus on the clear-as-day spam tweets currently making Twitter increasingly hard to use. On Oct 9, 12:59 pm, Dewald Pretorius dpr...@gmail.com wrote: One more thought about this. Audience (followers) is to Twitter what PageRank is to Google. Twitter created a commodity when it enabled the unlimited follower capability. As long as it is a commodity, money-motivated people will continue to exploit it as a commodity, just like they exploit Google's PageRank. The entire SEO industry is centered around ranking high in SE's, with Google's PageRank being one of the most coveted commodities. You can expect to see an entire industry forming around gaining Twitter followers. And very clever people will continuously try to outsmart you to circumvent any counter-measures that you try to implement. The only way to win that battle is to make followers a non-commodity. Dewald On Oct 9, 4:04 pm, Dewald Pretorius dpr...@gmail.com wrote: John, With reference to used for invalid purposes in your post. That begs the question, what exactly constitute invalid purposes? From a Twitter purist's point of view, anything other than What are you doing? constitutes an invalid purpose. I'd venture to say that very few people use Twitter for What are you doing? No way do I want to or need to tell a few thousand strangers (and have it indexed by Google) where I am right now, what I am doing right now, or what I am having for lunch. Facebook is a far better platform for that, where one has privacy and a hand-picked audience who just might care. Twitter created a platform that is ideally suited for the marketers and mega-phones. Why else would people actually spend money to buy followers, and get involved in all kinds of schemes to acquire more followers? Because the way your platform works enables and encourages that type of purpose. When you find yourself spending many frustrating hours of fighting invalid use, you are in effect fighting the animal that Twitter created. One cannot be angry with users when they use the service in unforeseen ways, especially when the service enables that type of use. The easiest way to fight invalid use is to change Twitter so that only valid use is possible. When Facebook realized that they were enabling the mega-phone type, they quickly changed their system to discourage that use by limiting the number of friends one can have. You either have to do that, or you have to expand your definition of valid use, and rejoice in the success it brings you when people use your service in unexpected and unanticipated ways. By having a flexible platform that encourages many purposes and trying to limit those purposes only to what you deem valid, you are forever going to fight a losing battle. And, you are laying down rich soil for the competition to germinate. If every who does not stick to What are you doing? abandoned Twitter today, you will be back to where you were in your early days in terms of size and relevance. Dewald On Oct 9, 2:07 pm, John Kalucki jkalu...@gmail.com wrote: Openness about abuse is generally counter-productive for everyone. For example, opaque limits are harder to game and give better detection signals. Also, practically, limits need to be adjusted without notice to respond changing attacks. In the end, valid access that is difficult to distinguish from access overwhelmingly used for invalid purposes
[twitter-dev] Re: Account management app - suspended accounts
Well, in the last dragnet, http://twitter.com/ricksanchezcnn, http://twitter.com/scottkwalker, http://twitter.com/karlrove were all suspended. And while you might disagree with their politics, it's pretty evident from their tweets that they were not spammers. These well-known personalities (and several others) were quickly restored, but you have to wonder how many non-wellknown, non-spam accounts are now in the weeds waiting for Twitter to restore their accounts. Too many false positives, and too many unknown rules arbitrarily applied. On Oct 9, 12:05 pm, Andrew Badera and...@badera.us wrote: As someone who's been a Twitter user since March 2007 or so, and a developer since late 2007, I have a hard time disagreeing with anything I've seen from Twitter on spam policies. In general, it seems to me, if you're not a douchebag, you don't get suspended. With one or two exceptions in that entire time. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Fri, Oct 9, 2009 at 2:54 PM, freefall tehgame...@googlemail.com wrote: Yes exactly - Twitter doesnt live by a coherent ruleset. It openly promotes bots yet suspends people without any warning or information. It opens its doors to be gamed and kicks people out randomly. This lack of transparant rules is working like a charm isnt it. On Oct 9, 7:44 pm, Cameron Kaiser spec...@floodgap.com wrote: Openness about abuse is generally counter-productive for everyone. For example, opaque limits are harder to game and give better detection signals. Also, practically, limits need to be adjusted without notice to respond changing attacks. In the end, valid access that is difficult to distinguish from access overwhelmingly used for invalid purposes are sometimes, sadly, going to get caught in a low-latency high-volume countermeasure system. How about you just answer my question? What you're saying is mankind is wrong to live by well defined and concrete rules. Um, no. What John is saying is that Twitter doesn't live by them. And, considering that Twitter is a relatively new medium, that's pretty much by definition. Of course the reality is Twitter is another laissez fair bums on seats driven site and as google proved, there is nothing like the abiltiy to change the rules on a whim, or hide a problem for a company of this ilk. The line for Jaiku starts over there. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com*ckai...@floodgap.com -- Prediction is very difficult, especially ... about the future. -- Niels Bohr
[twitter-dev] Twitter API in 24 Hours
I am co-authoring a book about the Twitter API, and I was wondering if any of you guys wanted to write a chapter. The book will be in the SAMS 24 hour series, and it's scheduled to be released mid-next year. Here is our tentative table of contents: Introduction to Twitter An overview of Twitter and Microblogging Common Types of Twitter Applications Key Issues to Consider when Developing Twitter Apps Overview of Twitters's API structure The API is HTTP-based The API uses Representational State Transfer (REST) There are pagination limits The Twitter API supports UTF-8 encoding Getting Started with the API Setting up an environment Making your first API call Parsing the reply Message, date, author, image Creating a simple display Setting up an application framework Creating a twitter Class Various twitter libraries are available PHP Class used in this book Modifing our class Twitter Error messages What each error code means Modifing our twitter Class Passing credentials to twitter Standard method (HTTP) Using cookies (create, retrieve, delete) OAuth Sending and Receiving messages from Twitter Creating a basic twitter client Sending messages in twitter Twitter search Dealing with Twitter downtimes and errors Twitter Beyond the API Future of Twitter Example Applications Other Mashup Twitter Services Twitter Etiquette Ping me directly if you are interested! andrew.ma...@gmail.com
[twitter-dev] Re: Announcing GoTwitr
Cool apps, looks well designed. Cheers, Dean -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Jim Fulford Sent: Friday, October 09, 2009 11:37 AM To: Twitter Development Talk Subject: [twitter-dev] Announcing GoTwitr /* Disclaimer - this app is not officially affiliated with Twitter. No Twitter endorsement implied. */ First, I'd like to say thanks to everyone on this board for sharing their thoughts, questions, and help every day, and also thank Twitter for creating a Great API for us to use. Today we're launching a new site call GoTwitr - www.gotwitr.com GoTwitr is a Twitter Automation website designed to help people grow and nourish their Twitter communities. We've spent a great deal of effort trying to make this an application that works well for everyone in the Twitter community - (New Users, Power Users, and of course Twitter.) GoTwitr takes a new approach to growing your community. It provides you with a set of tools to send out beautiful HTML invitations to invite people to your Twitter community. You can send invitations via email, on websites or blogs, or even to Twitter users. (This blog has some screen shots of the HTML invitations - http://www.gotwitr.com/content/gotwitr-site-built-drupal ) It also allows you to create a group of friends and attach them to an invitation so when your invitee decides to follow you; they can also follow your friends at the same time. This is a great way to get new people started on Twitter. Here are a few technical things we did to help people find quality connections without just blindly mass following: 1. GoTwitr lets you preview everyone you follow or un-follow. Many other Twitter automation tools bulk follow people. This feature ensures that you get a chance to decide if you want to follow or not, and helps to reduce or eliminate follower churn. 2. GoTwitr delivers people to your website. Every invitation accepted will take your recipient to your website, twitter page, blog, or any other URL. 3. 100% Oauth - You don't have to give away your Twitter password to use all the features of our service. This also provides you with easy sign in and registration. 4. API Limits - No user can hit the Twitter API more than 1000 times in a 24 hour period. Thanks again everyone for sharing your daily tips and insights. Please visit and have a look: http://www.gotwitr.com All feedback welcome. Jim Fulford
[twitter-dev] Re: Whitelisted IPs only work when authed?
Bump On Oct 9, 4:08 pm, Charles colei...@gmail.com wrote: I recently received email that confirmed my whitelisting status. I have several IPs whitelisted, as well as the account. From a shell on one of the whitelisted servers, I make a couple requests and then try: curlhttp://twitter.com/account/rate_limit_status.xml ?xml version=1.0 encoding=UTF-8? hash hourly-limit type=integer150/hourly-limit reset-time-in-seconds type=integer1255123230/reset-time-in- seconds reset-time type=datetime2009-10-09T21:20:30+00:00/reset-time remaining-hits type=integer147/remaining-hits /hash If, on the other hand, I try: curl -u username:passwordhttp://twitter.com/account/rate_limit_status.xml hash remaining-hits type=integer1/remaining-hits reset-time type=datetime2009-10-09T21:57:09+00:00/reset-time hourly-limit type=integer2/hourly-limit reset-time-in-seconds type=integer1255125429/reset-time-in- seconds /hash I was under the impression I did not have to auth if I was making calls from the API? Also: if I use my application's oauth credentials to generate an oauth_request and use the oauth URL, I am still getting the lower rate limit. Is this normal behavior?
[twitter-dev] Re: Search API Rate limiting - App Engine (again)
Thanks Abraham. Any pointers on how to setup a proxy on amazon ec2 for GAE? On Oct 8, 6:07 pm, Abraham Williams 4bra...@gmail.com wrote: Pretty much. You have limited options: 1) Run your Search API requests through a proxy where you will have exclusive access to the IP. 2) Wait for V2 of the Twitter API where the REST and Search APIs get combined so you can have authenticated search queries. 3) Hope Twitter slaps some duct tape on the issue and rolls out a whitelisting method for the Search API that includes passkeys in your user agent or some such thing. 4) Develop on non cloud base infrastructure. 5) Something else. Abraham 2009/10/8 Akshar akshar.d...@gmail.com http://apiwiki.twitter.com/Rate-limitingstates that for cloud platforms like Google App Engine, applications without a static IP addresses cannot receive Search whitelisting. Does that mean there is no way to avoid getting HTTP 503 response codes to search requests from app engine? On Oct 8, 2:09 pm, Akshar akshar.d...@gmail.com wrote: Any other solutions available for app engine folks stuck out here? Please help! I'm noticing this exact problem as well. I'm making only a few requests per hour. I have tried setting the user-agent but it did not help. Akshar On Oct 6, 9:50 am, Chad Etzel c...@twitter.com wrote: Hi All, GAE sites are problematic for the Twitter/SearchAPIbecause the IPs making outgoing requests are fluid and cannot as such be easily allowed for access. Also, since most IPs are shared, other applications on the same IPs making requests mean that fewer requests per app get through. One work around would be to spin up a server in EC2 or Rackspace Cloud or something and use it as a proxy for your requests. That way you have a dedicated IP that will have its full share of resources talking with the Twitter servers. HTH, -Chad On Tue, Oct 6, 2009 at 12:45 PM, Martin Omander moman...@google.com wrote: Same here; my app runs on Google App Engine and 40% of the requests to the TwitterSearchAPIget the 503 error message indicating rate limiting. Is there anything we as app authors can do on our side to alleviate the problem? /Martin On Oct 5, 1:53 pm, Paul Kinlan paul.kin...@gmail.com wrote: I am pretty sure there are custom headers on the App Engine that indicate the application that is sending the request. 2009/10/5 elkelk danielshaneup...@gmail.com Hi all, I am having the same issue. I have tried setting a custom user-agent, but this doesn't seem to affect the fact that twitter is limiting based on I.P. address. I'm only making about 5 searches an hour and 80% of them are failing on app engine due to a 503 rate limit. Twitter needs to determine a better way to let cloud clients access theirsearchAPI. It seems like they have really started blocking searchrequests in the last week or so. If anyone has any idea about how to better identify my app engine app please let let me know. On Oct 5, 2:59 am, steel steel...@gmail.com wrote: Hi. I have this problem too. My application does two request per hour and it get rate limit. What is wrong? I think it is twitter's problems On 1 окт, 01:45, Paul Kinlan paul.kin...@gmail.com wrote: Hi Guys, I have an app on the App engine using thesearchAPIand it is getting heavily rate limited again this past couple of days. I know that we are on a shared set of IP addresses and someone else could be hammering the system, but it seems to run for weeks without seeing the rate limit being hit and then all of a sudden only about 60% of the searches I perform will be rate limited. This seems to occur every two months or so. Has something changed recently? Paul -- Abraham Williams | Community Evangelist |http://web608.org Hacker |http://abrah.am|http://twitter.com/abrahamhttp://web608.org/geeks/abraham/blogs/2009/10/03/win-google-wave-invite This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: Have you read the OneForty.com Developer Contract?
Cross-posting this comment just posted to @BradleyJoyce's blog: http://bit.ly/2RqnU9 Hi folks, We're doing our best to hear and respond to developer feedback and better serve the community. Our approach to the developer contract was wrong. We're working to make it right. Here's how: Revised Publisher Registration Contract * Effective immediately, the old Reseller Agreement is replaced with a Publisher Registration Contract. (View it here: http://oneforty.com/terms/publisher_contract) * This lets you register as a developer and claim your apps. * We're still working on needed improvements to this contract to create productive terms of service that cover registration, claiming and optional donations Two separate agreements: * Publisher Registration Contract (applies if you wish to register for developer privileges to claim and edit your app) * Reseller Agreement (future: will only apply if you wish to offer items for sale at oneforty.com when that functionality is rolled out). This contract will be developed as part of our ecommerce pilot program. Interested in being part of the pilot testing? Ping us at develop...@oneforty.com. Donations * To revise the contract today, we had to temporarily disable the donation service. * We have refunded all donations that were made under the terms of the old contract. * We're revising the Publisher Registration Contract to allow us to turn donations back on for those who opt-in. Reseller Agreement * As part of our ecommerce pilot, we'll create a second contract for developers who wish to sell products on our site. * Its terms will be more developer friendly and created together with your feedback. Thank you for bearing with us while we work out these early kinks. We value your feedback, and we're anxious to make the Twitter community an even better place. As always, you can reach us at develop...@oneforty.com. Warmly, the oneforty team Laura, Mike, Michael and Robby ***NOTE: You do not have to claim your apps to get credit as the developer. Prefer no contract at all? We can add your name as the developer on a listing without you having to agree to anything beyond the site's general TOS.*** On Oct 9, 5:20 am, Andrew Badera and...@badera.us wrote: Laura, Sounds like you're taking some of the right steps to make your offering better for everyone concerned. I look forward to seeing the results of your efforts. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Fri, Oct 9, 2009 at 1:05 AM, Pistachio pistachioconsult...@gmail.com wrote: Andrew us absolutely correct. I personally bear full responsibility for letting that flawed contract get into production, even on a beta. It was likewise my error of judgment to assume that the alpha testers had been fine with the proposed contract merely because we had not received adverse feedback. We're listening. We're learning. Our comment on Bradley's post (http://bit.ly/DgM40) summarizes some of the contentious points we're revising, but there are others. To make this right, we'd like to better engage the TwitterAPI community in reviewing our next version. We are also separating the claiming terms from the resale terms. One more thing worth mentioning, we held off on building features that will allow developers to offer items for sale because we want to work that - and the related contract issues - out in close cooperation with developers. We'd love to hear from you if you want to have a voice on that. I've been sending out my cell # on all emails bound for developers because we want to be extremely accessible to developers. on email, Twitter, IRC... We will be working hard to earn your trust and to discover how we can better serve. Warmly, Laura Fitton la...@oneforty.com (sent from @pistachio: RT @dwroelands @oneforty needs to change their developer contract #onefortycontracthttp://bit.ly/DgM40//we're seeking feedback) On Oct 8, 10:21 pm, Andrew Badera and...@badera.us wrote: All else aside ... lawyers complicate things? Maybe, but you don't launch a product/platform and expect commitment from outside parties until YOU are happy with what YOUR lawyers have produced and thus YOU are offering to the outside world. There's no defense for a questionable contract. You stand behind your contract, or you don't publish it. Period. ∞ Andy Badera ∞+1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Thu, Oct 8, 2009 at 10:16 PM, Michael Ivey michael.i...@gmail.com wrote: OneForty is not a developer-friendly platform. I think this is a demonstrably false statement. All of my interactions with Laura and the 140 team have been very positive, and she's made it clear that they're working on the
[twitter-dev] Re: Account management app - suspended accounts
There is a very fundamental reason why I'm not holding my breath for Twitter to make any radical changes to their service: Human nature. Twitter management has tasted fame, and every Twitter employee can smell fortune around the corner. (Good for them, they deserve it.) It's is just natural that nobody will want to do anything to jeopardize that. Nobody is going to implement something that could cause 60% of the user count to take flight, even if the remaining users will enjoy the service more. Imagine the impact that will have on investors, perceived worth, etc. It's a far easier path to create more nebulous rules, and employ more people to enforce those rules. It does not upset the apple-cart. Dewald On Oct 9, 6:36 pm, PJB pjbmancun...@gmail.com wrote: Agreed. What else is wefollow.com, which Twitter freely advertises, but a ranking of people by followers (just look at some of the top people in the categories and you have to ask yourself, wtf!?) When the value of a Twitter account is determined by followers (as apps like wefollow make clear), then people will obviously and naturally try to increase their follower counts. I mean, Twitter freely advertises twittercounter.com too... and that app even shows charted daily growth in followers, prompting viewers to wonder how they, too, can have such growth. And, personally, I don't necessarily see anything wrong with that. After all, which is more detrimental to the community, someone like Karl Rove or Rick Sanchez or Arnold Schwarzenegger using some auto- follow technique, or the 10s of 1000s of BS accounts tweeting about weight loss or promotional URL @replies to random people? I wish Twitter would focus it's anti-spam tactics MORE on the content of the tweet stream, rather than on some amorphous following abuse which they undercut by highlighting apps like wefollow. Or at least a combination of the two. There's too many accounts tweeting about weight loss, etc... and it's a shame when folks like Karl Rove, Rick Sanchez, and others get suspended because they apparently fell afoul of follow/unfollow. A quick look at their tweet stream and it is apparent they are not spammers. There's too many false positives in the current anti-spam dragnets, and far too little focus on the clear-as-day spam tweets currently making Twitter increasingly hard to use. On Oct 9, 12:59 pm, Dewald Pretorius dpr...@gmail.com wrote: One more thought about this. Audience (followers) is to Twitter what PageRank is to Google. Twitter created a commodity when it enabled the unlimited follower capability. As long as it is a commodity, money-motivated people will continue to exploit it as a commodity, just like they exploit Google's PageRank. The entire SEO industry is centered around ranking high in SE's, with Google's PageRank being one of the most coveted commodities. You can expect to see an entire industry forming around gaining Twitter followers. And very clever people will continuously try to outsmart you to circumvent any counter-measures that you try to implement. The only way to win that battle is to make followers a non-commodity. Dewald On Oct 9, 4:04 pm, Dewald Pretorius dpr...@gmail.com wrote: John, With reference to used for invalid purposes in your post. That begs the question, what exactly constitute invalid purposes? From a Twitter purist's point of view, anything other than What are you doing? constitutes an invalid purpose. I'd venture to say that very few people use Twitter for What are you doing? No way do I want to or need to tell a few thousand strangers (and have it indexed by Google) where I am right now, what I am doing right now, or what I am having for lunch. Facebook is a far better platform for that, where one has privacy and a hand-picked audience who just might care. Twitter created a platform that is ideally suited for the marketers and mega-phones. Why else would people actually spend money to buy followers, and get involved in all kinds of schemes to acquire more followers? Because the way your platform works enables and encourages that type of purpose. When you find yourself spending many frustrating hours of fighting invalid use, you are in effect fighting the animal that Twitter created. One cannot be angry with users when they use the service in unforeseen ways, especially when the service enables that type of use. The easiest way to fight invalid use is to change Twitter so that only valid use is possible. When Facebook realized that they were enabling the mega-phone type, they quickly changed their system to discourage that use by limiting the number of friends one can have. You either have to do that, or you have to expand your definition of valid use, and rejoice in the success it brings you when people use your service in unexpected and unanticipated ways. By having a
[twitter-dev] Re: Whitelisted IPs only work when authed?
Please note: Bumping is highly discouraged. Bumping after 122 minutes is *really* highly discouraged. -Chad On Fri, Oct 9, 2009 at 7:10 PM, Charles colei...@gmail.com wrote: Bump On Oct 9, 4:08 pm, Charles colei...@gmail.com wrote: I recently received email that confirmed my whitelisting status. I have several IPs whitelisted, as well as the account. From a shell on one of the whitelisted servers, I make a couple requests and then try: curlhttp://twitter.com/account/rate_limit_status.xml ?xml version=1.0 encoding=UTF-8? hash hourly-limit type=integer150/hourly-limit reset-time-in-seconds type=integer1255123230/reset-time-in- seconds reset-time type=datetime2009-10-09T21:20:30+00:00/reset-time remaining-hits type=integer147/remaining-hits /hash If, on the other hand, I try: curl -u username:passwordhttp://twitter.com/account/rate_limit_status.xml hash remaining-hits type=integer1/remaining-hits reset-time type=datetime2009-10-09T21:57:09+00:00/reset-time hourly-limit type=integer2/hourly-limit reset-time-in-seconds type=integer1255125429/reset-time-in- seconds /hash I was under the impression I did not have to auth if I was making calls from the API? Also: if I use my application's oauth credentials to generate an oauth_request and use the oauth URL, I am still getting the lower rate limit. Is this normal behavior?
[twitter-dev] Re: Twitter Geo stuff
There is going to be a read-only geo_enabled flag on the user object that denotes whether or not the user has enabled geolocation. For security reasons, the user will need to come to twitter.com to change the setting. Best, Ryan On Fri, Oct 9, 2009 at 8:18 AM, Axthelm caxth...@openpathproducts.com wrote: On that note, is it known if the setting to opt in will be exposed in the account/update_profile API? On Oct 4, 4:13 am, Rich rhyl...@gmail.com wrote: TheGeotag is only populated firstly if the user posting the tweet has opted in via Twitter's website (which hasn't been enabled yet) and secondlyGeodata was submitted with that tweet On Oct 4, 4:41 am, Patrick kenned...@gmail.com wrote: I have been reading about the TwitterGeostuff - it all sounds exciting - and I'd like to start playing with it even it's not fully prime time. Supposedly it's available to some extent via the API. I see the geo/ tag in my feed, and I wonder how I can opt in and get it populated. Also, can someone provide an example of how the location field could be populated - I have cURL examples to update location, and I have my location info via my Nokia GPS-assisted phone, so I'd like to see an example on now to simulate the future geo/ feature, i.e., update location field as if it were geo/, if I cannot yet opt in to geo/.- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Woah There Page on Login
Any word on this behavior I see in different Twitter OAuth implementations. Nick On Sep 11, 5:41 pm, Nicholas Granado ngran...@gmail.com wrote: Any idea what the fix is for this situation? Is it a bug on twitter's end, if so any time frame for when the fix will be deployed? http://getsatisfaction.com/izea/topics/unable_to_allow_application_fo... Thanks, Nick --- Nicholas Granado twitter: heatxsink web: http://nickgranado.com
[twitter-dev] Re: Have you read the OneForty.com Developer Contract?
Laura, If my understanding is correct, this new contract is applicable when I want to claim my app in oneforty. With that in mind: a) Why do I need to license to oneforty and your sublicensees (whomever that may be) all my trademarks, trade names, service marks, logos or other identifying or distinctive marks. Let's say wondersocialwidget is my trademark. By licensing it to oneforty and your sublicensees, I enable you (collective) to create sites called buywondersocialwidget.com, getsocialwidgethere.com, therealsocialwidget.com, etc., and there is nothing I can do to stop that because I have licensed you to do that. Just for the ability to claim my app in your service? That does not make sense. What then about the unclaimed apps? Will you be violating their trademarks by virtue of the fact that their developers have not agreed to this contract? b) Why is 3.2 necessary at all? In other words, why do I need to license my app to oneforty in order for me to claim it? Shouldn't all this licensing stuff be in the Reseller Agreement? Dewald On Oct 9, 8:14 pm, Pistachio pistachioconsult...@gmail.com wrote: Cross-posting this comment just posted to @BradleyJoyce's blog:http://bit.ly/2RqnU9 Hi folks, We're doing our best to hear and respond to developer feedback and better serve the community. Our approach to the developer contract was wrong. We're working to make it right. Here's how: Revised Publisher Registration Contract * Effective immediately, the old Reseller Agreement is replaced with a Publisher Registration Contract. (View it here:http://oneforty.com/terms/publisher_contract) * This lets you register as a developer and claim your apps. * We're still working on needed improvements to this contract to create productive terms of service that cover registration, claiming and optional donations Two separate agreements: * Publisher Registration Contract (applies if you wish to register for developer privileges to claim and edit your app) * Reseller Agreement (future: will only apply if you wish to offer items for sale at oneforty.com when that functionality is rolled out). This contract will be developed as part of our ecommerce pilot program. Interested in being part of the pilot testing? Ping us at develop...@oneforty.com. Donations * To revise the contract today, we had to temporarily disable the donation service. * We have refunded all donations that were made under the terms of the old contract. * We're revising the Publisher Registration Contract to allow us to turn donations back on for those who opt-in. Reseller Agreement * As part of our ecommerce pilot, we'll create a second contract for developers who wish to sell products on our site. * Its terms will be more developer friendly and created together with your feedback. Thank you for bearing with us while we work out these early kinks. We value your feedback, and we're anxious to make the Twitter community an even better place. As always, you can reach us at develop...@oneforty.com. Warmly, the oneforty team Laura, Mike, Michael and Robby ***NOTE: You do not have to claim your apps to get credit as the developer. Prefer no contract at all? We can add your name as the developer on a listing without you having to agree to anything beyond the site's general TOS.*** On Oct 9, 5:20 am, Andrew Badera and...@badera.us wrote: Laura, Sounds like you're taking some of the right steps to make your offering better for everyone concerned. I look forward to seeing the results of your efforts. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Fri, Oct 9, 2009 at 1:05 AM, Pistachio pistachioconsult...@gmail.com wrote: Andrew us absolutely correct. I personally bear full responsibility for letting that flawed contract get into production, even on a beta. It was likewise my error of judgment to assume that the alpha testers had been fine with the proposed contract merely because we had not received adverse feedback. We're listening. We're learning. Our comment on Bradley's post (http://bit.ly/DgM40) summarizes some of the contentious points we're revising, but there are others. To make this right, we'd like to better engage the TwitterAPI community in reviewing our next version. We are also separating the claiming terms from the resale terms. One more thing worth mentioning, we held off on building features that will allow developers to offer items for sale because we want to work that - and the related contract issues - out in close cooperation with developers. We'd love to hear from you if you want to have a voice on that. I've been sending out my cell # on all emails bound for developers because we want to be extremely accessible to developers. on email, Twitter, IRC...
[twitter-dev] Re: Twitter API in 24 Hours
I don't know if you have enough for a full book. Even some of the chapters seem more like sub-sections at this point. Andrew Mager wrote: I am co-authoring a book about the Twitter API, and I was wondering if any of you guys wanted to write a chapter. The book will be in the SAMS 24 hour series, and it's scheduled to be released mid-next year. Here is our tentative table of contents: Introduction to Twitter An overview of Twitter and Microblogging Common Types of Twitter Applications Key Issues to Consider when Developing Twitter Apps Overview of Twitters's API structure The API is HTTP-based The API uses Representational State Transfer (REST) There are pagination limits The Twitter API supports UTF-8 encoding Getting Started with the API Setting up an environment Making your first API call Parsing the reply Message, date, author, image Creating a simple display Setting up an application framework Creating a twitter Class Various twitter libraries are available PHP Class used in this book Modifing our class Twitter Error messages What each error code means Modifing our twitter Class Passing credentials to twitter Standard method (HTTP) Using cookies (create, retrieve, delete) OAuth Sending and Receiving messages from Twitter Creating a basic twitter client Sending messages in twitter Twitter search Dealing with Twitter downtimes and errors Twitter Beyond the API Future of Twitter Example Applications Other Mashup Twitter Services Twitter Etiquette Ping me directly if you are interested! andrew.ma...@gmail.com
[twitter-dev] Re: Have you read the OneForty.com Developer Contract?
Maybe, at a more basic level my question is this: Why do I need to enter into a contract with oneforty at all, when all I want to do is say, I am Joe, WonderSocialWidget is my app, and here is more information about it. Isn't this part of oneforty nothing more than a free application directory, where the developer can identify him/herself and provide more information if he/she chooses to do so? Dewald On Oct 9, 9:34 pm, Dewald Pretorius dpr...@gmail.com wrote: Laura, If my understanding is correct, this new contract is applicable when I want to claim my app in oneforty. With that in mind: a) Why do I need to license to oneforty and your sublicensees (whomever that may be) all my trademarks, trade names, service marks, logos or other identifying or distinctive marks. Let's say wondersocialwidget is my trademark. By licensing it to oneforty and your sublicensees, I enable you (collective) to create sites called buywondersocialwidget.com, getsocialwidgethere.com, therealsocialwidget.com, etc., and there is nothing I can do to stop that because I have licensed you to do that. Just for the ability to claim my app in your service? That does not make sense. What then about the unclaimed apps? Will you be violating their trademarks by virtue of the fact that their developers have not agreed to this contract? b) Why is 3.2 necessary at all? In other words, why do I need to license my app to oneforty in order for me to claim it? Shouldn't all this licensing stuff be in the Reseller Agreement? Dewald On Oct 9, 8:14 pm, Pistachio pistachioconsult...@gmail.com wrote: Cross-posting this comment just posted to @BradleyJoyce's blog:http://bit.ly/2RqnU9 Hi folks, We're doing our best to hear and respond to developer feedback and better serve the community. Our approach to the developer contract was wrong. We're working to make it right. Here's how: Revised Publisher Registration Contract * Effective immediately, the old Reseller Agreement is replaced with a Publisher Registration Contract. (View it here:http://oneforty.com/terms/publisher_contract) * This lets you register as a developer and claim your apps. * We're still working on needed improvements to this contract to create productive terms of service that cover registration, claiming and optional donations Two separate agreements: * Publisher Registration Contract (applies if you wish to register for developer privileges to claim and edit your app) * Reseller Agreement (future: will only apply if you wish to offer items for sale at oneforty.com when that functionality is rolled out). This contract will be developed as part of our ecommerce pilot program. Interested in being part of the pilot testing? Ping us at develop...@oneforty.com. Donations * To revise the contract today, we had to temporarily disable the donation service. * We have refunded all donations that were made under the terms of the old contract. * We're revising the Publisher Registration Contract to allow us to turn donations back on for those who opt-in. Reseller Agreement * As part of our ecommerce pilot, we'll create a second contract for developers who wish to sell products on our site. * Its terms will be more developer friendly and created together with your feedback. Thank you for bearing with us while we work out these early kinks. We value your feedback, and we're anxious to make the Twitter community an even better place. As always, you can reach us at develop...@oneforty.com. Warmly, the oneforty team Laura, Mike, Michael and Robby ***NOTE: You do not have to claim your apps to get credit as the developer. Prefer no contract at all? We can add your name as the developer on a listing without you having to agree to anything beyond the site's general TOS.*** On Oct 9, 5:20 am, Andrew Badera and...@badera.us wrote: Laura, Sounds like you're taking some of the right steps to make your offering better for everyone concerned. I look forward to seeing the results of your efforts. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Fri, Oct 9, 2009 at 1:05 AM, Pistachio pistachioconsult...@gmail.com wrote: Andrew us absolutely correct. I personally bear full responsibility for letting that flawed contract get into production, even on a beta. It was likewise my error of judgment to assume that the alpha testers had been fine with the proposed contract merely because we had not received adverse feedback. We're listening. We're learning. Our comment on Bradley's post (http://bit.ly/DgM40) summarizes some of the contentious points we're revising, but there are others. To make this right, we'd like to better engage the TwitterAPI community in
[twitter-dev] where will we be next year
With the 2010 elections coming soon,and an angry electorate I can see twitter playing an unheard of influence on these elections.. as i see it the tasks will be KEEP IT ACCURATE,keep it brief,and keep it relevant The pols are allready sitting up and taking notice, NOTE;;the 18 to 30 year old electors COULD CONTROL EVERY ELECTION, if they chose to vote
[twitter-dev] Re: where will we be next year
how does this have anything to do with twitter development? On Fri, Oct 9, 2009 at 20:16, tom tomros0...@gmail.com wrote: With the 2010 elections coming soon,and an angry electorate I can see twitter playing an unheard of influence on these elections.. as i see it the tasks will be KEEP IT ACCURATE,keep it brief,and keep it relevant The pols are allready sitting up and taking notice, NOTE;;the 18 to 30 year old electors COULD CONTROL EVERY ELECTION, if they chose to vote -- Internets. Serious business.
[twitter-dev] Re: where will we be next year
Is there a development question here? On Oct 9, 2009, at 7:16 PM, tom tomros0...@gmail.com wrote: With the 2010 elections coming soon,and an angry electorate I can see twitter playing an unheard of influence on these elections.. as i see it the tasks will be KEEP IT ACCURATE,keep it brief,and keep it relevant The pols are allready sitting up and taking notice, NOTE;;the 18 to 30 year old electors COULD CONTROL EVERY ELECTION, if they chose to vote
