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
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 dpr...@gmail.com 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
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?
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
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
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
Good luck and I look forward to reading some drafts, yeah?
On Fri, Sep 25, 2009 at 7:41 AM, Stefna mstefa...@gmail.com 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
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 jmat...@gmail.com wrote:
I like Abraham's idea:
Twitter could add: next_cursor_string:1314614526448841129
Or a general
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
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
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
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
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
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
Yes, it is UTF-8 encoded.
The request body for の脚本家が贈る is
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
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
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
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
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,
On Fri, Sep 25, 2009 at 5:16 PM, Scott Haneda talkli...@newgeo.com 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
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 talkli...@newgeo.com wrote:
I would not change either. But there are those here that are
See Inline:
On Fri, Sep 25, 2009 at 4:21 PM, HardipSingh mr.hardip.si...@gmail.com 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
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
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
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
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 ryt...@gmail.com 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
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
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
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
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
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
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
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
+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 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 james.ren...@gmail.com
wrote:
+1. For this and other reasons the API should be versioned.
Jim Renkel
-Original Message-
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
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 mste...@gmail.com wrote:
Twitter actually announced versioning along those lines during the API 2.0
developer track session at #140tc.
On Sep 25,
???
were is my information
2009/9/26, Michael Steuer mste...@gmail.com:
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
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 dpr...@gmail.com wrote:
API folks, could you please, please NOT return
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.
Please email a...@twitter.com with your details.
-Chad
On Sat, Sep 26, 2009 at 12:50 AM, hansamann sven.hai...@googlemail.com 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
42 matches
Mail list logo
