[twitter-dev] Re: Requesting shadow role for streaming API
Please email a...@twitter.com with your details. -Chad On Sat, Sep 26, 2009 at 12:50 AM, hansamann wrote: > > Hi all, > > what is the process for requesting the shadow role (up to 50 000 > follower ids) for the streaming APIs? Is there a special form someone > can link me to? I'd need the shadow role for the 'groovytweets' user > account, we just passed the magic 400 followers and I want to use the > streaming api. > > Thx > Sven >
[twitter-dev] Requesting shadow role for streaming API
Hi all, what is the process for requesting the shadow role (up to 50 000 follower ids) for the streaming APIs? Is there a special form someone can link me to? I'd need the shadow role for the 'groovytweets' user account, we just passed the magic 400 followers and I want to use the streaming api. Thx Sven
[twitter-dev] Re: Please Make 401 Singular In Meaning
That absolutely seems like a bug, or at least an inconsistency - we generally return a 404 when things are missing. Please file an issue and we'll fix it up early next week. On Fri, Sep 25, 2009 at 17:51, Dewald Pretorius wrote: > > API folks, could you please, please NOT return 401 "Not authorized" > when an authenticated call with a perfectly valid username and > password requests a /queryusername.json where that queryusername > happens to be a username that does not exist. > > Rather return 404. > > By returning 401 you are making it impossible for me to tell where the > actual problem lies and inform the user. Is it with the user's > password, or is it because the user wanted information about a Twitter > account that does not exist? > > Dewald > -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
??? were is my information 2009/9/26, Michael Steuer : > > Twitter actually announced versioning along those lines during the > "API 2.0" developer track session at #140tc. > > > > On Sep 25, 2009, at 8:08 PM, "Jim Renkel" > wrote: > >> >> +1. For this and other reasons the API should be versioned. >> >> Jim Renkel >> >> -Original Message- >> From: twitter-development-talk@googlegroups.com >> [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Scott >> Haneda >> Sent: Friday, September 25, 2009 21:28 >> To: twitter-development-talk@googlegroups.com >> Subject: [twitter-dev] Re: SERIOUS Problem With Cursors In JSON >> Followers/Friends Ids >> >> >> Why is the API not versioned then? api.twitter.com/?v=1, >> api.twitter.com/?v=1.1, api.twitter.com/?v=1.2 etc >> >> Or, if that is too much maintenance, how about >> api.twitter.com/?bitfix=32 or whatever. >> -- >> Scott * If you contact me off list replace talklists@ with scott@ * >> >> On Sep 25, 2009, at 6:40 PM, JDG wrote: >> >>> and it would also break everyone who CAN handle 64 bit ints and >>> expects >>> results in decimal numeric format. >>> >>> On Fri, Sep 25, 2009 at 16:01, Richard wrote: >>> Can this not be returned as hex or base64? It would save bandwidth for Twitter (and us) and make it a string people could convert it to 64bit int if they still want to. On Sep 25, 10:16 pm, Scott Haneda wrote: > I would not change either. But there are those here that are > stating > they need new hardware to work around this issue, and that they can > not afford that. I was trying to be that voice of reason if that > is > the road/excuse they are choosing to go. > > There seem to be acceptable workarounds, solid proposed > workarounds, > etc. I guess I am not getting it, JSON is just a string returned, > yes, it can represent type of data, but it is still just a > string. I > can not see it being that huge a performance hit to massage that > string a bit once you get ahold of it. > -- > Scott * If you contact me off list replace talklists@ with scott@ * > > On Sep 25, 2009, at 2:02 PM, jmathai wrote: > >> It's ridiculous to suggest a change in hardware (64 bit) or >> software >> (switch from PHP) to use Twitter's API. It's not like either of >> these >> are archaic. It sucks, sure, but it's silly to suggest such a >> "solution". > >> BTW, I don't have this problem. I'm just trying to be the voice of >> reason. >>> >> >> >
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
Yes, versioning the API is on the roadmap, I just don't know of any official timeline. -Chad On Fri, Sep 25, 2009 at 11:47 PM, Michael Steuer wrote: > > Twitter actually announced versioning along those lines during the "API 2.0" > developer track session at #140tc. > > > > On Sep 25, 2009, at 8:08 PM, "Jim Renkel" wrote: > >> >> +1. For this and other reasons the API should be versioned. >> >> Jim Renkel >> >> -Original Message- >> From: twitter-development-talk@googlegroups.com >> [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Scott >> Haneda >> Sent: Friday, September 25, 2009 21:28 >> To: twitter-development-talk@googlegroups.com >> Subject: [twitter-dev] Re: SERIOUS Problem With Cursors In JSON >> Followers/Friends Ids >> >> >> Why is the API not versioned then? api.twitter.com/?v=1, >> api.twitter.com/?v=1.1, api.twitter.com/?v=1.2 etc >> >> Or, if that is too much maintenance, how about >> api.twitter.com/?bitfix=32 or whatever. >> -- >> Scott * If you contact me off list replace talklists@ with scott@ * >> >> On Sep 25, 2009, at 6:40 PM, JDG wrote: >> >>> and it would also break everyone who CAN handle 64 bit ints and >>> expects >>> results in decimal numeric format. >>> >>> On Fri, Sep 25, 2009 at 16:01, Richard wrote: >>> Can this not be returned as hex or base64? It would save bandwidth for Twitter (and us) and make it a string people could convert it to 64bit int if they still want to. On Sep 25, 10:16 pm, Scott Haneda wrote: > > I would not change either. But there are those here that are > stating > they need new hardware to work around this issue, and that they can > not afford that. I was trying to be that voice of reason if that is > the road/excuse they are choosing to go. > > There seem to be acceptable workarounds, solid proposed workarounds, > etc. I guess I am not getting it, JSON is just a string returned, > yes, it can represent type of data, but it is still just a > string. I > can not see it being that huge a performance hit to massage that > string a bit once you get ahold of it. > -- > Scott * If you contact me off list replace talklists@ with scott@ * > > On Sep 25, 2009, at 2:02 PM, jmathai wrote: > >> It's ridiculous to suggest a change in hardware (64 bit) or >> software >> (switch from PHP) to use Twitter's API. It's not like either of >> these >> are archaic. It sucks, sure, but it's silly to suggest such a >> "solution". > >> BTW, I don't have this problem. I'm just trying to be the voice of >> reason. >>> >> >> >
[twitter-dev] Re: Please Make 401 Singular In Meaning
The same thing goes for 403... It's either update limit hit, or not allowed to DM that person because you're not following him. The latter should really have another error code, or you're forced to either make another api call, or to interpret the returned response. On Sep 25, 2009, at 5:51 PM, Dewald Pretorius wrote: API folks, could you please, please NOT return 401 "Not authorized" when an authenticated call with a perfectly valid username and password requests a /queryusername.json where that queryusername happens to be a username that does not exist. Rather return 404. By returning 401 you are making it impossible for me to tell where the actual problem lies and inform the user. Is it with the user's password, or is it because the user wanted information about a Twitter account that does not exist? Dewald
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
Twitter actually announced versioning along those lines during the "API 2.0" developer track session at #140tc. On Sep 25, 2009, at 8:08 PM, "Jim Renkel" wrote: +1. For this and other reasons the API should be versioned. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Scott Haneda Sent: Friday, September 25, 2009 21:28 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids Why is the API not versioned then? api.twitter.com/?v=1, api.twitter.com/?v=1.1, api.twitter.com/?v=1.2 etc Or, if that is too much maintenance, how about api.twitter.com/?bitfix=32 or whatever. -- Scott * If you contact me off list replace talklists@ with scott@ * On Sep 25, 2009, at 6:40 PM, JDG wrote: and it would also break everyone who CAN handle 64 bit ints and expects results in decimal numeric format. On Fri, Sep 25, 2009 at 16:01, Richard wrote: Can this not be returned as hex or base64? It would save bandwidth for Twitter (and us) and make it a string people could convert it to 64bit int if they still want to. On Sep 25, 10:16 pm, Scott Haneda wrote: I would not change either. But there are those here that are stating they need new hardware to work around this issue, and that they can not afford that. I was trying to be that voice of reason if that is the road/excuse they are choosing to go. There seem to be acceptable workarounds, solid proposed workarounds, etc. I guess I am not getting it, JSON is just a string returned, yes, it can represent type of data, but it is still just a string. I can not see it being that huge a performance hit to massage that string a bit once you get ahold of it. -- Scott * If you contact me off list replace talklists@ with scott@ * On Sep 25, 2009, at 2:02 PM, jmathai wrote: It's ridiculous to suggest a change in hardware (64 bit) or software (switch from PHP) to use Twitter's API. It's not like either of these are archaic. It sucks, sure, but it's silly to suggest such a "solution". BTW, I don't have this problem. I'm just trying to be the voice of reason.
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
+1. For this and other reasons the API should be versioned. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Scott Haneda Sent: Friday, September 25, 2009 21:28 To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids Why is the API not versioned then? api.twitter.com/?v=1, api.twitter.com/?v=1.1, api.twitter.com/?v=1.2 etc Or, if that is too much maintenance, how about api.twitter.com/?bitfix=32 or whatever. -- Scott * If you contact me off list replace talklists@ with scott@ * On Sep 25, 2009, at 6:40 PM, JDG wrote: > and it would also break everyone who CAN handle 64 bit ints and > expects > results in decimal numeric format. > > On Fri, Sep 25, 2009 at 16:01, Richard wrote: > >> >> Can this not be returned as hex or base64? >> It would save bandwidth for Twitter (and us) and make it a string >> people could convert it to 64bit int if they still want to. >> >> On Sep 25, 10:16 pm, Scott Haneda wrote: >>> I would not change either. But there are those here that are >>> stating >>> they need new hardware to work around this issue, and that they can >>> not afford that. I was trying to be that voice of reason if that is >>> the road/excuse they are choosing to go. >>> >>> There seem to be acceptable workarounds, solid proposed workarounds, >>> etc. I guess I am not getting it, JSON is just a string returned, >>> yes, it can represent type of data, but it is still just a >>> string. I >>> can not see it being that huge a performance hit to massage that >>> string a bit once you get ahold of it. >>> -- >>> Scott * If you contact me off list replace talklists@ with scott@ * >>> >>> On Sep 25, 2009, at 2:02 PM, jmathai wrote: >>> It's ridiculous to suggest a change in hardware (64 bit) or software (switch from PHP) to use Twitter's API. It's not like either of these are archaic. It sucks, sure, but it's silly to suggest such a "solution". >>> BTW, I don't have this problem. I'm just trying to be the voice of reason. >
[twitter-dev] Re: Please Make 401 Singular In Meaning
Agree. Completely. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Dewald Pretorius Sent: Friday, September 25, 2009 20:05 To: Twitter Development Talk Subject: [twitter-dev] Re: Please Make 401 Singular In Meaning And if anyone is going to tell me I should make additional API calls to try and determine the real source of the error, or I should try and interpret the returned error message, I am going to remotely install a VB program on your laptop that is going to repeatedly pick up the mouse and whack you over the head with it. What I am really saying is the API is returning a false error message. The user is properly authenticated. The error is that the target information resource does not exist. That's why it must return 404. Try it for yourself and see what I mean: curl -u username:password http://twitter.com/statuses/user_timeline/broughtin.json Dewald On Sep 25, 9:51 pm, Dewald Pretorius wrote: > API folks, could you please, please NOT return 401 "Not authorized" > when an authenticated call with a perfectly valid username and > password requests a /queryusername.json where that queryusername > happens to be a username that does not exist. > > Rather return 404. > > By returning 401 you are making it impossible for me to tell where the > actual problem lies and inform the user. Is it with the user's > password, or is it because the user wanted information about a Twitter > account that does not exist? > > Dewald
[twitter-dev] Re: 401 Unauthorized error while posting status with Unicode characters (non english characters)
Hello, I had this same problem. I had to convert all multi-byte characters into their individual bytes. So, for example, for the character "の": Your example has %306E, but the encoding that works for me is %E3%81%AE (three bytes for the three-byte character). On Sep 25, 5:00 pm, Satheesh Natesan wrote: > Yes, it is UTF-8 encoded. > > The request body for "の脚本家が贈る" is > oauth_consumer_key=wmeO7Y20oMFa1ptKVY4WA&oauth_nonce=3231757&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1253903495&oauth_token=76084396-0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ&oauth_version=1.0&status=%306E%811A%672C%5BB6%304C%8D08%308B&oauth_signature=AMcLsF43vPP6Hmn8fv%2bZCMdqEnU%3d > > and the base signature is > POST&http%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.json&oauth_consumer_key%3DwmeO7Y20oMFa1ptKVY4WA%26oauth_nonce%3D3231757%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1253903495%26oauth_token%3D76084396-0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ%26oauth_version%3D1.0%26status%3D%25306E%25811A%25672C%255BB6%25304C%258D08%25308B > > Do you see anything wrong here? > > Thanks! > Satheesh Natesan > > > > On Thu, Sep 24, 2009 at 6:49 PM, Carlos wrote: > > > Are you sure you are encoding your posts as UTF-8? > > > On Sep 24, 5:16 pm, Satheesh Natesan > > wrote: > > > I am getting "401 Unauthorized" exception when updating status with > > > non english characters using my app. > > > > This exception is happening for any Japanese or Korean characters. > > > > Another interesting thing is that it is possible to post some other > > > non english characters like Malayalam. The exception will not happen > > > for single word in these cases, but occurs for multiple words. > > > For example consider the following example > > > > ØáÇÞµæù çµdw - does not work > > > > ØáÇÞµæùçµdw - with space removed works. > > > > Base signature for "ØáÇÞµæù çµdw" which throws exception is > > > > POST&http%3A%2F%2Ftwitter.com%2Fstatuses > > > %2Fupdate.json&oauth_consumer_key% > > > 3DwmeO7Y20oMFa1ptKVY4WA%26oauth_nonce > > > %3D4504682%26oauth_signature_method% > > > 3DHMAC-SHA1%26oauth_timestamp%3D1253727596%26oauth_token%3D76084396- > > > 0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ%26oauth_version > > > %3D1.0%26status% > > > 3D%25D8%25E1%25C7%25DE%25B5%25E6%25F9%2520%25E7%25B5dw > > > > and for "ØáÇÞµæùçµdw" which works is > > > > POST&http%3A%2F%2Ftwitter.com%2Fstatuses > > > %2Fupdate.json&oauth_consumer_key% > > > 3DwmeO7Y20oMFa1ptKVY4WA%26oauth_nonce > > > %3D9388868%26oauth_signature_method% > > > 3DHMAC-SHA1%26oauth_timestamp%3D1253727793%26oauth_token%3D76084396- > > > 0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ%26oauth_version > > > %3D1.0%26status% > > > 3D%25D8%25E1%25C7%25DE%25B5%25E6%25F9%25E7%25B5dw > > > > OAuth client library I am using is in .Net > > > > Could you please help to solve this issue? Also I would like to know > > > you support all unicode characters. > > > Your help is greatly appreciated. > > > > Thanks, > > > Satheesh Natesan- Hide quoted text - > > - Show quoted text -
[twitter-dev] Re: Please Make 401 Singular In Meaning
I think it would be more appropriate to "create a GUI interface in Visual Basic, see if I can track an IP address." :) -- Scott * If you contact me off list replace talklists@ with scott@ * On Sep 25, 2009, at 6:05 PM, Dewald Pretorius wrote: I am going to remotely install a VB program on your laptop that is going to repeatedly pick up the mouse and whack you over the head with it.
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
I actually like the idea of versioning the API. Having an API version that returns all values as strings can be as simple on the Twitter side as an IF statement in the final stages of constructing the JSON output that just converts all numerical values to strings before the JSON encode. Dewald On Sep 25, 10:57 pm, jmathai wrote: > Dewald sums it up great. I'm not affected by this issue but keeping > the barrier of entry low is of high value. It sucks that some PHP > installations have this issue, but if there's a good way to accomodate > such a popular language then what's the harm? > > This brings up an issue though. I'm not in favor of changing the > default int to a string. It's the default that's important. Adding > in an override parameter isn't really anymore helpful than suggesting > to parse the json once you get it. Except, the thought of pre-parsing > json (no matter how simple) makes my stomach churn. > > Think about it from the perspective of a developer that's just > starting with the API. What would trip them up? If there's a way to > resolve that, then that should be a high priority. > > For me it's not a big deal since I've used it enough and know people > in the API community and this group where I can get an answer. That's > a luxury I didn't have when I started though. > > So far, two proposed solutions: > * Abraham suggested an additional key (this is great because you see > it in the response without having to know of an additional paramter) > * I suggested an additional parameter which would return all values > as a string (drawback is that this is a bit more "hidden" - not > everyone RTM :( ) > * Your suggestion here! > > Think about the children! :)
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
Why is the API not versioned then? api.twitter.com/?v=1, api.twitter.com/?v=1.1, api.twitter.com/?v=1.2 etc Or, if that is too much maintenance, how about api.twitter.com/?bitfix=32 or whatever. -- Scott * If you contact me off list replace talklists@ with scott@ * On Sep 25, 2009, at 6:40 PM, JDG wrote: and it would also break everyone who CAN handle 64 bit ints and expects results in decimal numeric format. On Fri, Sep 25, 2009 at 16:01, Richard wrote: Can this not be returned as hex or base64? It would save bandwidth for Twitter (and us) and make it a string people could convert it to 64bit int if they still want to. On Sep 25, 10:16 pm, Scott Haneda wrote: I would not change either. But there are those here that are stating they need new hardware to work around this issue, and that they can not afford that. I was trying to be that voice of reason if that is the road/excuse they are choosing to go. There seem to be acceptable workarounds, solid proposed workarounds, etc. I guess I am not getting it, JSON is just a string returned, yes, it can represent type of data, but it is still just a string. I can not see it being that huge a performance hit to massage that string a bit once you get ahold of it. -- Scott * If you contact me off list replace talklists@ with scott@ * On Sep 25, 2009, at 2:02 PM, jmathai wrote: It's ridiculous to suggest a change in hardware (64 bit) or software (switch from PHP) to use Twitter's API. It's not like either of these are archaic. It sucks, sure, but it's silly to suggest such a "solution". BTW, I don't have this problem. I'm just trying to be the voice of reason.
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
Dewald sums it up great. I'm not affected by this issue but keeping the barrier of entry low is of high value. It sucks that some PHP installations have this issue, but if there's a good way to accomodate such a popular language then what's the harm? This brings up an issue though. I'm not in favor of changing the default int to a string. It's the default that's important. Adding in an override parameter isn't really anymore helpful than suggesting to parse the json once you get it. Except, the thought of pre-parsing json (no matter how simple) makes my stomach churn. Think about it from the perspective of a developer that's just starting with the API. What would trip them up? If there's a way to resolve that, then that should be a high priority. For me it's not a big deal since I've used it enough and know people in the API community and this group where I can get an answer. That's a luxury I didn't have when I started though. So far, two proposed solutions: * Abraham suggested an additional key (this is great because you see it in the response without having to know of an additional paramter) * I suggested an additional parameter which would return all values as a string (drawback is that this is a bit more "hidden" - not everyone RTM :( ) * Your suggestion here! Think about the children! :) On Sep 25, 6:48 pm, Dewald Pretorius wrote: > I think the point that some folks are trying to make is that forcing > consumers of the API to use 64-bit machines is stifling innovation. > > Many Twitter apps start as pet projects hosted on a shared HostGator > or other provider's server for nine bucks a month. That's how mine > started way back. You don't have the option of editing php.ini or > running on a 64-bit machine, unless you want to reduce your groceries > per month and fork out more for a server. > > Dewald
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
I think the point that some folks are trying to make is that forcing consumers of the API to use 64-bit machines is stifling innovation. Many Twitter apps start as pet projects hosted on a shared HostGator or other provider's server for nine bucks a month. That's how mine started way back. You don't have the option of editing php.ini or running on a 64-bit machine, unless you want to reduce your groceries per month and fork out more for a server. Dewald
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
and it would also break everyone who CAN handle 64 bit ints and expects results in decimal numeric format. On Fri, Sep 25, 2009 at 16:01, Richard wrote: > > Can this not be returned as hex or base64? > It would save bandwidth for Twitter (and us) and make it a string > people could convert it to 64bit int if they still want to. > > On Sep 25, 10:16 pm, Scott Haneda wrote: > > I would not change either. But there are those here that are stating > > they need new hardware to work around this issue, and that they can > > not afford that. I was trying to be that voice of reason if that is > > the road/excuse they are choosing to go. > > > > There seem to be acceptable workarounds, solid proposed workarounds, > > etc. I guess I am not getting it, JSON is just a string returned, > > yes, it can represent type of data, but it is still just a string. I > > can not see it being that huge a performance hit to massage that > > string a bit once you get ahold of it. > > -- > > Scott * If you contact me off list replace talklists@ with scott@ * > > > > On Sep 25, 2009, at 2:02 PM, jmathai wrote: > > > > > It's ridiculous to suggest a change in hardware (64 bit) or software > > > (switch from PHP) to use Twitter's API. It's not like either of these > > > are archaic. It sucks, sure, but it's silly to suggest such a > > > "solution". > > > > > BTW, I don't have this problem. I'm just trying to be the voice of > > > reason. > -- Internets. Serious business.
[twitter-dev] Re: Please Make 401 Singular In Meaning
And if anyone is going to tell me I should make additional API calls to try and determine the real source of the error, or I should try and interpret the returned error message, I am going to remotely install a VB program on your laptop that is going to repeatedly pick up the mouse and whack you over the head with it. What I am really saying is the API is returning a false error message. The user is properly authenticated. The error is that the target information resource does not exist. That's why it must return 404. Try it for yourself and see what I mean: curl -u username:password http://twitter.com/statuses/user_timeline/broughtin.json Dewald On Sep 25, 9:51 pm, Dewald Pretorius wrote: > API folks, could you please, please NOT return 401 "Not authorized" > when an authenticated call with a perfectly valid username and > password requests a /queryusername.json where that queryusername > happens to be a username that does not exist. > > Rather return 404. > > By returning 401 you are making it impossible for me to tell where the > actual problem lies and inform the user. Is it with the user's > password, or is it because the user wanted information about a Twitter > account that does not exist? > > Dewald
[twitter-dev] Please Make 401 Singular In Meaning
API folks, could you please, please NOT return 401 "Not authorized" when an authenticated call with a perfectly valid username and password requests a /queryusername.json where that queryusername happens to be a username that does not exist. Rather return 404. By returning 401 you are making it impossible for me to tell where the actual problem lies and inform the user. Is it with the user's password, or is it because the user wanted information about a Twitter account that does not exist? Dewald
[twitter-dev] Re: About the oneforty application directory
oneforty.com seems like a valuable and useful site, one I would
definitely take advantage of, but I have a couple of questions and
concerns that need to be answered before I do so.
1. I'm not sure why I have to grant the site access to a twitter account
to use, and I am REALY concerned about why it needs update access, not
just read access. I don't want this site, or any other site like it, to
be able to update my twitter account, generating tweets or DMs, etc.,
until I see what the benefit of it doing so is.
What will you be using my twitter account for, other than authorization?
If you reregister the site to only need read access to my twitter
account, I would be a lot less reluctant to use it.
2. The site seems to be geared toward client applications. My
application is, for now, just a web-site (http://twxlate.com) with the
possibility of it evolving into desktop and smart phone client
applications in the future. Is your intention to be as relevant to
web-sites as to client applications?
Thanks in advance.
Jim Renkel
-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Alex
Payne
Sent: Thursday, September 24, 2009 14:24
To: Twitter Development Talk
Subject: [twitter-dev] About the oneforty application directory
Just wanted to pass on a note from the team at oneforty.com, who
recently launched with over 1300 Twitter applications in their
directory. Your app might already be on their site. If it's not yet,
you can register as a developer and add it. Once you register and
claim your app you can promote it with screenshots, descriptions,
tags, and reviews.
If you saw the early alpha version of oneforty, it's much improved -
real home page, most popular apps ranking and essentials. New item
pages just launched and look much better than the prototype did.
Their team working on the ability to sell apps right on the site.
They're also definitely looking for your feedback. @freerobby,
@graysky, @macasek, and @pistachio are often in the #twitterapi IRC
channel. There's more contact info below, too.
A note from the oneforty team and info on how to register, claim, edit
& add stuff:
"""
We built oneforty to help the best stuff being built on the Twitter
API get found and get profitable.
Come claim your apps, add content and add new projects in the "Twitter
appstore" oneforty.com
To get started:
Sign in via oauth. (We whitelisted as many dev usernames as we could
find. If you can't login already use invite code TWAPI and we'll let
you right in.)
Register as a developer: http://oneforty.com/me/developer_profile
Search for and claim your app ("Suggest Item" if we don't have it
yet!)
Check out your item's page, make sure it's tagged well, tweet a link to
it, etc
Once approved, add details, screenshots, media coverage and more
In the near future you'll be able to offer things for sale right in
oneforty. For now we link to your sites and (optionally) let you
collect donations.
We want to help you get your app found, rated, reviewed and into the
hands of the users who need it the most. We also want to get the
Twitter community to do a better job supporting developers and apps so
that your innovation can flourish. It's frustrating when great apps go
defunct because of server costs, etc.
We're anticipating decent blog and press coverage, so we want your to
look its best! Please let us know whatever we can do to help you.
Thank you.
We'd really love to know what you think and what you want: Uservice
feedback forum. Any questions at all, develop...@oneforty.com or
617-645-7767, anytime.
oneforty Founder Laura (@Pistachio) Fitton will be at events in Fort
Worth 9/25, Seattle 9/26-27, SF/bay area 9/27-30 and Boston 10/1 and
would love to meet you (see http://bit.ly/tour140 for Tweetup & event
info). She also wrote Twitter for Dummies.
"""
Check 'em out!
--
Alex Payne - Platform Lead, Twitter, Inc.
http://twitter.com/al3x
[twitter-dev] Re: A few questions regarding rate limits / whitelisting
See Inline: On Fri, Sep 25, 2009 at 4:21 PM, HardipSingh wrote: > > We are launching some code next week that will be using the API to > post updates for multiple twitter accounts. In preparation for our > launch, I want to make sure that we're not going to get burned by rate > limits. While reading over the documentation, a few questions came > up. > > My questions are as follows: > > 1) On this page --> http://apiwiki.twitter.com/Rate-limiting, it > states that updates via http post do not affect rate limits. > > Yet, on this page.. http://help.twitter.com/forums/10711/entries/15364, > it states that ..there is a rate limit of "1,000 total updates per > day, on any and all devices (web, mobile web, phone, API, etc. )". > > From my understanding, this means that there is no restriction on how > many update requests come from a single IP. There is, however, a > limit on how many updates a single account can post. > > Is this correct? That is correct. > > 2) I understand that there is a rate limit of 1000 updates per day per > account. The documentation also states that getting whitelisted does > not remove this limit since this is done on a per account basis. Does > this mean that there is no way to post more than 1000 updates a day > from a single account regardless of whether or not we get > whitelisted? Also correct. > > 3) On the Whitelisting form, it states.. "Whitelisting is only > available to developers and to applications in production; all other > requests are rejected.". Since our code is not actually live yet, but > is set to go live next week, does this mean that there is no way to > get whitelisted beforehand? Also, if we were to get whitelisted > beforehand, do we have to do this per account, or per ip address? If you have a preview version available, you can add the URL in the whitelist request form, otherwise you must wait until you are in production, otherwise we cannot gauge the app. Typically applications are whitelisted by IP, we do not do bulk account whitelisting. > > That's all I have for now. Thanks in advance for your time. Cheers, -Chad
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
Can this not be returned as hex or base64? It would save bandwidth for Twitter (and us) and make it a string people could convert it to 64bit int if they still want to. On Sep 25, 10:16 pm, Scott Haneda wrote: > I would not change either. But there are those here that are stating > they need new hardware to work around this issue, and that they can > not afford that. I was trying to be that voice of reason if that is > the road/excuse they are choosing to go. > > There seem to be acceptable workarounds, solid proposed workarounds, > etc. I guess I am not getting it, JSON is just a string returned, > yes, it can represent type of data, but it is still just a string. I > can not see it being that huge a performance hit to massage that > string a bit once you get ahold of it. > -- > Scott * If you contact me off list replace talklists@ with scott@ * > > On Sep 25, 2009, at 2:02 PM, jmathai wrote: > > > It's ridiculous to suggest a change in hardware (64 bit) or software > > (switch from PHP) to use Twitter's API. It's not like either of these > > are archaic. It sucks, sure, but it's silly to suggest such a > > "solution". > > > BTW, I don't have this problem. I'm just trying to be the voice of > > reason.
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
On Fri, Sep 25, 2009 at 5:16 PM, Scott Haneda wrote: > > I can not see it > being that huge a performance hit to massage that string a bit once you get > ahold of it. Precisely. If you really want to turn the numbers into strings in PHP, here are 2 workaround examples. Please note, I use PHP personally, so I am not apathetic to this issue. There are programmatic ways of dealing with it, and that's half the fun of programming, right? Example 1 (cursor specific example); http://twitter.com/followers/ids/barackobama.json?cursor=-1";); echo $json; $pattern = "/\"next_cursor\":([0-9]+),/"; $replace = "\"next_cursor\":\"$1\","; $new_json = preg_replace($pattern, $replace, $json); $pattern = "/\"previous_cursor\":([0-9]+),/"; $replace = "\"previous_cursor\":\"$1\","; /* note $new_json in third parameter */ $new_json = preg_replace($pattern, $replace, $new_json); echo $new_json; var_dump(json_decode($new_json)); ?> Example 2 (generalized json "naked" numbers example): http://twitter.com/followers/ids/barackobama.json?cursor=-1";); echo $json; $new_json = stringify_json_numbers($json); echo $new_json; echo ""; var_dump(json_decode($new_json)); echo ""; ?> Can't we all just get along? -Chad
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
I would not change either. But there are those here that are stating they need new hardware to work around this issue, and that they can not afford that. I was trying to be that voice of reason if that is the road/excuse they are choosing to go. There seem to be acceptable workarounds, solid proposed workarounds, etc. I guess I am not getting it, JSON is just a string returned, yes, it can represent type of data, but it is still just a string. I can not see it being that huge a performance hit to massage that string a bit once you get ahold of it. -- Scott * If you contact me off list replace talklists@ with scott@ * On Sep 25, 2009, at 2:02 PM, jmathai wrote: It's ridiculous to suggest a change in hardware (64 bit) or software (switch from PHP) to use Twitter's API. It's not like either of these are archaic. It sucks, sure, but it's silly to suggest such a "solution". BTW, I don't have this problem. I'm just trying to be the voice of reason.
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you & we're adding statuses/retweets)
John, thanx for your comment over at groovyconsole.appspot.com - http://groovyconsole.appspot.com/view.groovy?id=19003 In case you do not get updates on comments there, let me ask my main question again. This would make my (our) lives a lot easier when it comes to retweet tracking, still it would not require me to use the streaming API: >If we could pass multiple status ids into the statuses/retweets method in >which case it returns summaries for each tweets retweets like the count, only >the screennames that >retweeted, etc. I could keep it on one system. It would >help me a lot. Are you investigating support for this? Is this under consideration? Thx Sven On Sep 24, 9:50 am, John Kalucki wrote: > I'll update the Wiki to reflect the new reality. > > Retweetswill begin to flow through all /1/statuses/* resources soon > -- in advance of the full retweet launch. This will give developers > time to test and deploy features in advance. Also, the retweet volume > is very low now, so exceptions should be easier to handle. > > -John Kaluckihttp://twitter.com/jkalucki > Services, Twitter Inc. > > On Sep 23, 10:15 pm, hansamann wrote: > > > John, I assume the method to use would then be > > >http://stream.twitter.com/1/statuses/filter.format > > > It does not mention that it includesretweets, but it will once the > > API is live? > > > Cheers > > Sven > > > On Sep 23, 9:38 pm, hansamann wrote: > > > > Thanx, I'll give that a try. > > > > On Sep 23, 8:11 pm, John Kalucki wrote: > > > > >Retweetswill be searched by the follow parameter on the filter > > > > resource. The intention is that you get all statuses (including > > > >retweets) where any user_id field matches your predicate list. So, > > > > tweets, replies and both ends ofretweets. > > > > > If GAE cuts you off after 30 seconds, then you shouldn't open > > > > connections to the Streaming API. Gather ye data elsewhere and smuggle > > > > it into GAE by other means. > > > > > -John Kaluckihttp://twitter.com/jkalucki > > > > Services, Twitter Inc. > > > > > On Sep 23, 7:50 pm, hansamann wrote: > > > > > > One reason for example is being on Google App Engine and having a 30 > > > > > second limit. I cannot keep the connection open. > > > > > > Another reason is I am not interested in everyonesretweets, just the > > > > >retweets(and in this case all, not just a sample) of that twitter > > > > > user's friends. > > > > > > What do you think? > > > > > > Cheers > > > > > Sven > > > > > > On Sep 22, 9:49 pm, John Kalucki wrote: > > > > > > > Retweetaggregators should use the Streaming API /1/statuses/sample > > > > > > method to gather a sample ofRetweetsor apply for the fullRetweet > > > > > > stream on /1/statuses/retweet. > > > > > > > The Streaming API may be in Alpha, but the service has been very > > > > > > reliable. > > > > > > > I'm unaware of any technical issues that would block a reasonably > > > > > > proficient service developer on a reasonable stack from integrating > > > > > > Streaming API results in fairly short order. I'm sure there are > > > > > > examples of byzantine stacks upon which this isn't true, but > > > > > > workarounds can be found. > > > > > > > -John Kaluckihttp://twitter.com/jkalucki > > > > > > Services, TwitterInc. > > > > > > > On Sep 22, 9:27 pm, hansamann wrote: > > > > > > > > I am still hoping for an answer to the questions in this thread, > > > > > > > but > > > > > > > meanwhile here is another idea the Twitter Team might find > > > > > > > interesting. > > > > > > > > As it seems many of us want to trackretweets. What we are really > > > > > > > interested in is the number ofretweetsover time so we can find > > > > > > > trending topics, in my case within a community (e.g. not for > > > > > > > public > > > > > > > timeline tweets, just for the tweets among my friends). So: why > > > > > > > not > > > > > > > have a method that is capable of returning severalretweetcounts? > > > > > > > > So what if statuses/retweetswould either accept *just a single > > > > > > > id* in > > > > > > > which case the behaviour is as currently described, or *many ids* > > > > > > > in > > > > > > > which case the response is a summary for many statusIds. The > > > > > > > summary > > > > > > > should contain the usernames that retweeted the original ids and > > > > > > > the > > > > > > >retweetcounts at least. > > > > > > > > If the API is left as it is, guess a lot of us will need to get > > > > > > > whitelisted. Excessively calling status/retweetsfor single tweets > > > > > > > cannot be the intention of Twitter. Also manyretweetaggregators > > > > > > > will > > > > > > > really be in trouble (unless they use the streaming apis, but > > > > > > > those > > > > > > > again are alpha and some cannot use them for technical reasons) > > > > > > > as the > > > > > > > twitter accounts of their users are not whitelisted and as such > > > > > > > constraint to 150 API calls. > > > > > > > > Come on, would anyo
[twitter-dev] Re: About the oneforty application directory
Thanks Nelu!
Not sure when, but the chances of Chicago are really good. The next
few trips are mid/late October, Mid November and early December.
Details will be kept up-to-date at http://bit.ly/tour140.
Also? We're working to get this thing out into the sunlight as quickly
as possible to that folks can casually browse without signups, etc.
Just as you point out, that's important.
Thanks all for the feedback and glad to be part of this list. I'll
pretty much keep my mouth shut here and leave it to oneforty's
developers say intelligent development related stuff, but I'm a
lurking fan of the work all you guys are doing.
Warmly,
Laura
Laura Fitton, Founder
oneforty inc.
la...@oneforty.com
http://twitter.com/pistachio
http://twitter.com/oneforty
On Sep 24, 3:55 pm, Nelu Lazar wrote:
> I have checked thedirectorypast days, and claimed my app. Congrats
> on a work very well done.
>
> A couple of suggestions:
> - the site doesn't currently allow new lines in the description field;
> this could be useful for listing features;
> - although it's understandable why thedirectoryrequires user's
> authentication, specific pages of the website may be more useful if
> public, to allow new users to familiarize with Twitter's capabilities
> and the apps around it.
>
> I live near Chicago, any chance you will add it to your tour?
>
> Nelu Lazar
> Founder Tweetvisor.comhttp://twitter.com/nelulazar
>
> On Sep 24, 3:24 pm, Alex Payne wrote:
>
> > Just wanted to pass on a note from the team atoneforty.com, who
> > recently launched with over 1300 Twitter applications in their
> >directory. Your app might already be on their site. If it's not yet,
> > you can register as a developer and add it. Once you register and
> > claim your app you can promote it with screenshots, descriptions,
> > tags, and reviews.
>
> > If you saw the early alpha version ofoneforty, it's much improved -
> > real home page, most popular apps ranking and essentials. New item
> > pages just launched and look much better than the prototype did.
>
> > Their team working on the ability to sell apps right on the site.
> > They're also definitely looking for your feedback. @freerobby,
> > @graysky, @macasek, and @pistachio are often in the #twitterapi IRC
> > channel. There's more contact info below, too.
>
> > A note from theonefortyteam and info on how to register, claim, edit
> > & add stuff:
>
> > """
> > We builtonefortyto help the best stuff being built on the Twitter
> > API get found and get profitable.
> > Come claim your apps, add content and add new projects in the "Twitter
> > appstore"oneforty.com
> > To get started:
> > Sign in via oauth. (We whitelisted as many dev usernames as we could
> > find. If you can't login already use invite code TWAPI and we'll let
> > you right in.)
> > Register as a developer:http://oneforty.com/me/developer_profile
> > Search for and claim your app ("Suggest Item" if we don't have it yet!)
> > Check out your item's page, make sure it's tagged well, tweet a link to it,
> > etc
> > Once approved, add details, screenshots, media coverage and more
>
> > In the near future you'll be able to offer things for sale right in
> >oneforty. For now we link to your sites and (optionally) let you
> > collect donations.
>
> > We want to help you get your app found, rated, reviewed and into the
> > hands of the users who need it the most. We also want to get the
> > Twitter community to do a better job supporting developers and apps so
> > that your innovation can flourish. It's frustrating when great apps go
> > defunct because of server costs, etc.
>
> > We're anticipating decent blog and press coverage, so we want your to
> > look its best! Please let us know whatever we can do to help you.
> > Thank you.
>
> > We'd really love to know what you think and what you want: Uservice
> > feedback forum. Any questions at all, develop...@oneforty.com or
> > 617-645-7767, anytime.
>
> >onefortyFounder Laura (@Pistachio) Fitton will be at events in Fort
> > Worth 9/25, Seattle 9/26-27, SF/bay area 9/27-30 and Boston 10/1 and
> > would love to meet you (seehttp://bit.ly/tour140forTweetup & event
> > info). She also wrote Twitter for Dummies.
> > """
>
> > Check 'em out!
>
> > --
> > Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
> You either need to run on a newer system or use a language that can > properly handle 64-bit numbers. C, Python, Ruby, Scala, Erlang, C#, > etc none of them have problems with 64-bit ints. Heck, Perl does it fine. I run TTYtter on a 32-bit system that runs a Perl that's over 10 years old, and it's perfectly happy with bigints. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- The less we know, the better we feel. -- David Bowie, "Miracle Goodnight" --
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
It's ridiculous to suggest a change in hardware (64 bit) or software (switch from PHP) to use Twitter's API. It's not like either of these are archaic. It sucks, sure, but it's silly to suggest such a "solution". BTW, I don't have this problem. I'm just trying to be the voice of reason. On Sep 25, 1:55 pm, Scott Haneda wrote: > I tend to agree, a MacMini, around 600.00, would build php out as 64 > bit no issue. If you are a baby startup, that should really cover you > and be able to handle a lot more load than you would think. You may > have to pop your database on something more robust, but it works quite > well as a php front end. > > Take it to 1000.00 or so, and you can built out your own 1U server > that is going to hold it's own very very well. Or, rent a 1U, they > are a few hundred bucks a month, you get to pick the OS, pick the > bit'ness, etc. > > If you are a startup, on a shoestring, part of the fun is being > creative, and making due with what you have. > > And don't laugh at that MacMini, you can easily get to the SATA port, > and plug it right into a SATA array elsewhere, getting SATA II on full > size dives. I just pegged the drives to a cork board, its not pretty, > but it works. I have a second on standby in case that one craps. I > just had them laying around, and made them up from parts. > > While I am not going to mention the site, I can tell you, it is php on > the front, apache2 with a good deal of mod_rewriting going on, and > substantial database work, all happening on the MacMini, handling > 500,000+ average unique visitors, which is a lot more requests when > you add in images and the rest. (this site is not twitter related) > > If I was sloppy, that database would fall on it's face under that > load. I have added in some caching where needed, so pages are > rendered to disk at the expense of a php include of the data. > > I am in this thread to learn about the issue, but so far, getting to > 64 bits should not be a barrier. Isn't this really a php issue > anyway? Why can't php handle a 64 bit int in a 32 bit system? Maybe > they need a bug report or a patch. MySql seems to handle 64 bit on my > 32 bit test system here just fine. Maybe someone can write a wrapper > for the json encode/decode that fixes this in that part of php? > -- > Scott * If you contact me off list replace talklists@ with scott@ * > > On Sep 25, 2009, at 12:23 PM, David Fisher wrote: > > > Saying that startups can't afford 64 bit processors in systems is > > crazy. Most startups I know are running on EC2 or have fairly new > > hardware. I bought a killer 64-bit quad xeon server for less than > > $1,500 for our startup and its rocking. If your startup doesn't have > > $1,500 for a primary capital computing expense that's another problem > > you have there.
[twitter-dev] Re: 401 Unauthorized error while posting status with Unicode characters (non english characters)
Yes, it is UTF-8 encoded. The request body for "の脚本家が贈る" is oauth_consumer_key=wmeO7Y20oMFa1ptKVY4WA&oauth_nonce=3231757&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1253903495&oauth_token=76084396-0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ&oauth_version=1.0&status=%306E%811A%672C%5BB6%304C%8D08%308B&oauth_signature=AMcLsF43vPP6Hmn8fv%2bZCMdqEnU%3d and the base signature is POST&http%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.json&oauth_consumer_key%3DwmeO7Y20oMFa1ptKVY4WA%26oauth_nonce%3D3231757%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1253903495%26oauth_token%3D76084396-0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ%26oauth_version%3D1.0%26status%3D%25306E%25811A%25672C%255BB6%25304C%258D08%25308B Do you see anything wrong here? Thanks! Satheesh Natesan On Thu, Sep 24, 2009 at 6:49 PM, Carlos wrote: > > Are you sure you are encoding your posts as UTF-8? > > On Sep 24, 5:16 pm, Satheesh Natesan > wrote: > > I am getting "401 Unauthorized" exception when updating status with > > non english characters using my app. > > > > This exception is happening for any Japanese or Korean characters. > > > > Another interesting thing is that it is possible to post some other > > non english characters like Malayalam. The exception will not happen > > for single word in these cases, but occurs for multiple words. > > For example consider the following example > > > > ØáÇÞµæù çµdw - does not work > > > > ØáÇÞµæùçµdw - with space removed works. > > > > Base signature for "ØáÇÞµæù çµdw" which throws exception is > > > > POST&http%3A%2F%2Ftwitter.com%2Fstatuses > > %2Fupdate.json&oauth_consumer_key% > > 3DwmeO7Y20oMFa1ptKVY4WA%26oauth_nonce > > %3D4504682%26oauth_signature_method% > > 3DHMAC-SHA1%26oauth_timestamp%3D1253727596%26oauth_token%3D76084396- > > 0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ%26oauth_version > > %3D1.0%26status% > > 3D%25D8%25E1%25C7%25DE%25B5%25E6%25F9%2520%25E7%25B5dw > > > > and for "ØáÇÞµæùçµdw" which works is > > > > POST&http%3A%2F%2Ftwitter.com%2Fstatuses > > %2Fupdate.json&oauth_consumer_key% > > 3DwmeO7Y20oMFa1ptKVY4WA%26oauth_nonce > > %3D9388868%26oauth_signature_method% > > 3DHMAC-SHA1%26oauth_timestamp%3D1253727793%26oauth_token%3D76084396- > > 0M9ll2nghrjWhjALbH7YEHXizcLDNvoLfgXKfHQZQ%26oauth_version > > %3D1.0%26status% > > 3D%25D8%25E1%25C7%25DE%25B5%25E6%25F9%25E7%25B5dw > > > > OAuth client library I am using is in .Net > > > > Could you please help to solve this issue? Also I would like to know > > you support all unicode characters. > > Your help is greatly appreciated. > > > > Thanks, > > Satheesh Natesan >
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
I tend to agree, a MacMini, around 600.00, would build php out as 64 bit no issue. If you are a baby startup, that should really cover you and be able to handle a lot more load than you would think. You may have to pop your database on something more robust, but it works quite well as a php front end. Take it to 1000.00 or so, and you can built out your own 1U server that is going to hold it's own very very well. Or, rent a 1U, they are a few hundred bucks a month, you get to pick the OS, pick the bit'ness, etc. If you are a startup, on a shoestring, part of the fun is being creative, and making due with what you have. And don't laugh at that MacMini, you can easily get to the SATA port, and plug it right into a SATA array elsewhere, getting SATA II on full size dives. I just pegged the drives to a cork board, its not pretty, but it works. I have a second on standby in case that one craps. I just had them laying around, and made them up from parts. While I am not going to mention the site, I can tell you, it is php on the front, apache2 with a good deal of mod_rewriting going on, and substantial database work, all happening on the MacMini, handling 500,000+ average unique visitors, which is a lot more requests when you add in images and the rest. (this site is not twitter related) If I was sloppy, that database would fall on it's face under that load. I have added in some caching where needed, so pages are rendered to disk at the expense of a php include of the data. I am in this thread to learn about the issue, but so far, getting to 64 bits should not be a barrier. Isn't this really a php issue anyway? Why can't php handle a 64 bit int in a 32 bit system? Maybe they need a bug report or a patch. MySql seems to handle 64 bit on my 32 bit test system here just fine. Maybe someone can write a wrapper for the json encode/decode that fixes this in that part of php? -- Scott * If you contact me off list replace talklists@ with scott@ * On Sep 25, 2009, at 12:23 PM, David Fisher wrote: Saying that startups can't afford 64 bit processors in systems is crazy. Most startups I know are running on EC2 or have fairly new hardware. I bought a killer 64-bit quad xeon server for less than $1,500 for our startup and its rocking. If your startup doesn't have $1,500 for a primary capital computing expense that's another problem you have there.
[twitter-dev] Re: About the oneforty application directory
Hi folks, Really sorry this reply didn't get out sooner; I was on a plane last night when Dewald raised these issues. I regret any concern or alarm caused by our developer contract. We're now reviewing a number of the issues that Dewald brought up because frankly, we don't like them either. The off-site revenue share clause was an outright error that has already been removed from the contract effective today. I'm sorry for the confusion this caused and we will be making further revisions to the contract and clarifying its terms promptly. Please be assured that listings on oneforty.com will always be free -- and free of obligations to the developer. We will never demand a cut in exchange for being listed because we would fail the Twitter Community if our lists of applications left any out. Having a good relationship with the developer community is very important to us. This kind of issue is precisely why we're in private beta -- to work out the kinks and to find out what developers want and need. I'm available at la...@oneforty.com to discuss any concerns or further feedback at any time. Warmly, Laura Laura Fitton, Founder oneforty inc. la...@oneforty.com On Sep 24, 8:25 pm, Dewald Pretorius wrote: > Please read the Publishers Contract that you agree to when you > register as a publisher and make yourapplicationavailable for sale > throughOneForty. > > Here's a bird's eye view of some things you need to determine whether > you like them or not: > > 1)OneFortytakes 30% of nett revenue on the sales of your product as > royalties. > > 2) They pay your money (the 70%) within 2 months after the calendar > month in which the sale occurred, and only when the amount owed > exceeds $250.00. > > 3) You receive your money as a gift or donation fromOneForty(that > may or may not have tax implications). > > 4) You can only contact customers for support, meaning you are not > allowed to contact them for any marketing or upsells. Violations can > cause agreement termination, or financial penalties. > > 5) You must price your item no higher than the lowest price available > to other distributors. > > 6) If customers purchase your item directly from your web site and > they came via a link fromOneForty, you must payOneForty30% of that > sale. > > 7) For the first 12 months, you can cancel the agreement with 30 days > notice only ifOneFortyhas breached the agreement. > > 8) After the first 12 months, you can cancel the agreement at will > with 60 days notice.
[twitter-dev] A few questions regarding rate limits / whitelisting
We are launching some code next week that will be using the API to post updates for multiple twitter accounts. In preparation for our launch, I want to make sure that we're not going to get burned by rate limits. While reading over the documentation, a few questions came up. My questions are as follows: 1) On this page --> http://apiwiki.twitter.com/Rate-limiting, it states that updates via http post do not affect rate limits. Yet, on this page.. http://help.twitter.com/forums/10711/entries/15364, it states that ..there is a rate limit of "1,000 total updates per day, on any and all devices (web, mobile web, phone, API, etc. )". >From my understanding, this means that there is no restriction on how many update requests come from a single IP. There is, however, a limit on how many updates a single account can post. Is this correct? 2) I understand that there is a rate limit of 1000 updates per day per account. The documentation also states that getting whitelisted does not remove this limit since this is done on a per account basis. Does this mean that there is no way to post more than 1000 updates a day from a single account regardless of whether or not we get whitelisted? 3) On the Whitelisting form, it states.. "Whitelisting is only available to developers and to applications in production; all other requests are rejected.". Since our code is not actually live yet, but is set to go live next week, does this mean that there is no way to get whitelisted beforehand? Also, if we were to get whitelisted beforehand, do we have to do this per account, or per ip address? That's all I have for now. Thanks in advance for your time.
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
I don't think anyone's saying it's Twitter's problem (at least I hope not). It's the same issue as supporting Internet Explorer. You can bitch and complain all you want about IE not supporting standards but if it's the most popular (or one of the most popular) browsers that are in use --- then practical beats principle. My suggestion was to return everything as a string if that's how it's being requested. It's a safe backwards compatible addition that doesn't affect anyone that doesn't run into this problem. If your scope is limited to what startups can or can't afford, then that's really narrow. This applies to anyone consuming the API be than on a laptop for development or anything else. On Sep 25, 12:23 pm, David Fisher wrote: > I'm sorry, but the problem isn't Twitter- its your language and JSON > parser. Outputting everything as a string, when it clearly should be a > number, is inefficient and crazy. > > Saying that startups can't afford 64 bit processors in systems is > crazy. Most startups I know are running on EC2 or have fairly new > hardware. I bought a killer 64-bit quad xeon server for less than > $1,500 for our startup and its rocking. If your startup doesn't have > $1,500 for a primary capital computing expense that's another problem > you have there. > > You either need to run on a newer system or use a language that can > properly handle 64-bit numbers. C, Python, Ruby, Scala, Erlang, C#, > etc none of them have problems with 64-bit ints. > > Not a Twitter problem. It's a programming issue on your end and > unfortunately I can't help as I don't know PHP in depth. > > -dave > > On Sep 24, 3:29 pm, Dewald Pretorius wrote: > > > That magical maximum number appears to be 1 (1.0E+12). > > > So, for tweet ids we still have a bit of breathing space. > > > Dewald > > > On Sep 24, 4:18 pm, Dewald Pretorius wrote: > > > > Clearly PHP_INT_MAX plays no role in json_decode. > > > > There must be some other mystical maximum number above which it > > > represents the number as float in the decoded data. > > > > Dewald
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
I'm sorry, but the problem isn't Twitter- its your language and JSON parser. Outputting everything as a string, when it clearly should be a number, is inefficient and crazy. Saying that startups can't afford 64 bit processors in systems is crazy. Most startups I know are running on EC2 or have fairly new hardware. I bought a killer 64-bit quad xeon server for less than $1,500 for our startup and its rocking. If your startup doesn't have $1,500 for a primary capital computing expense that's another problem you have there. You either need to run on a newer system or use a language that can properly handle 64-bit numbers. C, Python, Ruby, Scala, Erlang, C#, etc none of them have problems with 64-bit ints. Not a Twitter problem. It's a programming issue on your end and unfortunately I can't help as I don't know PHP in depth. -dave On Sep 24, 3:29 pm, Dewald Pretorius wrote: > That magical maximum number appears to be 1 (1.0E+12). > > So, for tweet ids we still have a bit of breathing space. > > Dewald > > On Sep 24, 4:18 pm, Dewald Pretorius wrote: > > > > > Clearly PHP_INT_MAX plays no role in json_decode. > > > There must be some other mystical maximum number above which it > > represents the number as float in the decoded data. > > > Dewald
[twitter-dev] 6 months of login issues, sorry to bring this here...
At least 6 months, maybe even a year, I've had login issues to Twitter. Pre front page design change and post design change. I know this is not the right forum for this but support desk is so overwhelmed and fundamentally broken I give up. (if you want to know why I say broken please ask, but I'm not submitting a ticket to the support desk about it :) ) Maybe I'm one of few that does not "remember me" when I login and that's why I see this every day. On login, enter I user and pass, ~40% of the time I am logged in. The rest, I end up at /sessions with a server error. A refresh does not repost my login and pass, (I'm assuming headers are lost as a result of a redirect or JS posting) sometimes I'm logged in and can just drop /sessions from the URL, other times I am not. In a short time of non use of the site, I am logged out. I have not quit my browser, and the cookie remains, with a session of no expire time, so it should live until I quit the browser. Never logged out during use, only on returning to the site from working elsewhere. I see this in Safari, on multiple computers. I rarely use Firefox aside from development so I can not say if it is browser specific. I reported it to the help desk, I just can't handle the auto generic emails asking me the most off topic questions. If I put the time into a bug report, which I have, with headers and return strings, I expect more than a 5 response back and forth about reading the FAQ. I can repat this. It is seemingly random. It can be made worse by using a password manager, which can auto submit the user and pass. I suspect too quickly sending in data may have something to do with it. Or, the /sessions page freaks out and does not change the header to where it needs to go. I end up with a funky set of cookies which may explain my getting logged out randomly. Any devs from Twitter care to look into this with me? If you also want to talk about the help desk, I'd be happy to point out why that is not a good way to treat users, whether they need general help or technical help. Thanks. Not trying to sound bitchy, just being matter of fact. I tried the correct support channels, they are just too much work to prove it's not user error. -- Scott Iphone says hello.
[twitter-dev] Re: Brain Wave Help required with Twitter - rss- map
Ok, I'll bite :) I though you meant "phishing" at first. Do you have programmin experience? If so, what languages are you familiar with? If not, do you have access to a programer and are just looking for confirmation that your idea could be realized? This mailing list is primarily for developers/programmers so you may be in the wrong area. Though you may find a receptive developer to hire here, this is probably not the best place to be asking. Let us know and we will see if we can not get you going in the right direction. -- Scott Iphone says hello. On Sep 25, 2009, at 8:58 AM, "billy2...@googlemail.com" > wrote: Thank you for reading this as I am looking for some help to sort out a brain wave. You know what it is like do not know enough and do not know if it can be done. Is it possible to question twitter for Fishing Matches? What I would like to do is take all the information on Fishing Matches from Twitter into a RSS feed and then onto a map keeping every one informed of fishing matches in there area. Am I dreaming to much or is this possible. Any help in the right direction much appreciated and would also appreciate being told that it is too much work and not very good. Thanking you in anticipation. Billy World Fishing News UK Yorkshire
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
If you are on 32 bit, what php.ini changes are you referring to that would be beneficial? -- Scott Iphone says hello. On Sep 25, 2009, at 10:35 AM, jmathai wrote: I like Abraham's idea: Twitter could add: "next_cursor_string":"1314614526448841129" Or a general return_as_string parameter which would return all values as strings. This would solve the problem for future values that might exceed the max int. There are going to be a lot of devs using PHP that don't have the option to switch to 64 bit or make any php.ini changes. On Sep 24, 12:29 pm, Dewald Pretorius wrote: That magical maximum number appears to be 1 (1.0E+12). So, for tweet ids we still have a bit of breathing space. Dewald On Sep 24, 4:18 pm, Dewald Pretorius wrote: Clearly PHP_INT_MAX plays no role in json_decode. There must be some other mystical maximum number above which it represents the number as float in the decoded data. Dewald
[twitter-dev] Re: master thesis related to Twitter
Good luck and I look forward to reading some drafts, yeah? On Fri, Sep 25, 2009 at 7:41 AM, Stefna wrote: > > I've submitted a ticket with following content: > *** *** *** > I am a 23 years old student of informatics at AGH Universtity of > Science and Technology in Cracow (Poland). Due to a rapid development, > strict formed data and accessible API I would like to designate my > master thesis to the Twitter related topic. My promoter is the PhD at > the Department of Computer Linguistics and our first pick was vaguely > to analyse the semantic meaning of tweets. > > Do you have suggestions about the dissertation topic? > Do you have any pending requests or prospect features you want to > develop? > > I will browse known issues, I will think thoroughly about the topic > but still - your suggestion might be very helpful. Even the shortest > one (like "good luck") will encourage me to more intensive research. > *** *** *** > Does anyone have any suggestions? My ticket has a six-digit number so > I'm afraid I won't get any answer :) > > I'll probably ask for help during my work so I subscribe to this group > anyway. > > Thanks in advance! > -- Kevin Mesiab CEO, Mesiab Labs L.L.C. http://twitter.com/kmesiab http://mesiablabs.com http://retweet.com
[twitter-dev] master thesis related to Twitter
I've submitted a ticket with following content: *** *** *** I am a 23 years old student of informatics at AGH Universtity of Science and Technology in Cracow (Poland). Due to a rapid development, strict formed data and accessible API I would like to designate my master thesis to the Twitter related topic. My promoter is the PhD at the Department of Computer Linguistics and our first pick was vaguely to analyse the semantic meaning of tweets. Do you have suggestions about the dissertation topic? Do you have any pending requests or prospect features you want to develop? I will browse known issues, I will think thoroughly about the topic but still - your suggestion might be very helpful. Even the shortest one (like "good luck") will encourage me to more intensive research. *** *** *** Does anyone have any suggestions? My ticket has a six-digit number so I'm afraid I won't get any answer :) I'll probably ask for help during my work so I subscribe to this group anyway. Thanks in advance!
[twitter-dev] The Difference Between a Twitter "Web" and "Desktop" Application
Hi folks: I'm adding some Twitter integration to a desktop app, and I'm unhappy with the whole "copy/paste this PIN into your application" experience. In my case, I happen to have a browser instance containing the OAuth authentication process embedded within my desktop app, so it's possible to listen for redirection events that happen inside that browser and respond to them -- but when I mark my Twitter app as a "desktop" app (on the app-settings screen on Twitter, where it's defined), I'm forced into using the copy-this-PIN approach (because no callback URL can be specified for desktop apps), which, from a user- experience perspective, kinda sucks. I do notice, though, that if I make my app a "web" app instead, I can specify a callback URL, and have my app watch for redirections to that URL, which works quite well and provides a more seamless user experience. So my question is, is there any disadvanage to marking my installed desktop app a "web" app on Twitter, so I can take advantage of using a callback URL to provide a better user experience? Is it a violation of terms of use or anything? Any drawbacks at all? Thanks in advance -- Chris
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
I like Abraham's idea: >>Twitter could add: "next_cursor_string":"1314614526448841129" Or a general return_as_string parameter which would return all values as strings. This would solve the problem for future values that might exceed the max int. There are going to be a lot of devs using PHP that don't have the option to switch to 64 bit or make any php.ini changes. On Sep 24, 12:29 pm, Dewald Pretorius wrote: > That magical maximum number appears to be 1 (1.0E+12). > > So, for tweet ids we still have a bit of breathing space. > > Dewald > > On Sep 24, 4:18 pm, Dewald Pretorius wrote: > > > Clearly PHP_INT_MAX plays no role in json_decode. > > > There must be some other mystical maximum number above which it > > represents the number as float in the decoded data. > > > Dewald
[twitter-dev] twitter Widget wont load results
im getting an error loading results in my twitter search widget : Object doesn't support this property or method the only way to get rid of these errors is to comment out a scriptresource.axd that ties to data already on my site. HELP?
[twitter-dev] Re: Deprecation Notice: pagination on several methods is being replaced with cursoring on October 26, 2009
I'll pass those numbers along to our App Services team and see what they can do. On Thu, Sep 24, 2009 at 19:07, Dewald Pretorius wrote: > > Alex, > > Thanks for this. > > Is there any way that response times on the call could be improved? > > It takes around 4 seconds to retrieve one cursor. When one retrieves > the followers/friends of an account with 100,000 of those, with 100 > followers/friends per cursor, it takes more than an hour to retrieve > all the followers/friends. > > It's not a train smash issue, it would just be good to have faster > response times. I have noticed the same slower response times > (measured against 0.4 seconds for other calls) on the social graph > methods when using cursors. > > Dewald > -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Brain Wave Help required with Twitter - rss- map
Thank you for reading this as I am looking for some help to sort out a brain wave. You know what it is like do not know enough and do not know if it can be done. Is it possible to question twitter for Fishing Matches? What I would like to do is take all the information on Fishing Matches from Twitter into a RSS feed and then onto a map keeping every one informed of fishing matches in there area. Am I dreaming to much or is this possible. Any help in the right direction much appreciated and would also appreciate being told that it is too much work and not very good. Thanking you in anticipation. Billy World Fishing News UK Yorkshire
