k our app
unless recoded.
Zaudio
Developer BullsOnWallStreet.com
To unsubscribe from this group, send email to
twitter-development-talk+unsubscribegooglegroups.com or reply to this email
with the words "REMOVE ME" as the subject.
24.14 )
where I'm getting this, and my testing account Zaudio... and the test
user Zaudio2 - all looks good
Please urgently address this. I thought it a blacklisting issue... but
maybe it's a bug?
Thanks
Simon (Zaudio)
Developer www.bullsonwallstreet.com
Yes - Please can we have that urgently - yes or no?
Thanks
Simon
On Jan 6, 8:15 pm, PJB wrote:
> Can we please get some confirmation that the cursor-less calls won't
> be going away this coming Monday?
>
> On Dec 22 2009, 4:13 pm, Wilhelm Bierbaum wrote:
>
>
>
> > We noticed that some clients
Hey Kyle,
Is that true re the rate limits?
I've always assumed that ANY request on an IP is xounted against that
IP's rate limit - so comes of the 20,000; and each user has their own
rate limit... normally 150 per hour.
So an authenticated request comes off both the user's and and IP's
rate limi
I actually totally prefer time's to all be UNC / GMT as they are
now...
it's the same erevywhere, and very easily converted to local timezones
for display - which is what I imagine most end users want to see...
they don't want to be working out timezones from around the world in
their heads!
If t
.
>
> Nicholas
> ---
> Nicholas Granado
> email: ngran...@gmail.com
> twitter: heatxsink
> web:http://nickgranado.com
>
> On Mon, Oct 19, 2009 at 6:38 AM, Zaudio wrote:
>
> > Nicholas,
> > That's great feedback!
>
> > In you opinion, how
> > ---
> > Nicholas Granado
> > email: ngran...@gmail.com <mailto:ngran...@gmail.com>
> > twitter: heatxsink
> > web:http://nickgranado.com
>
> > On Mon, Oct 19, 2009 at 6:38 AM, Zaudio > <mailto:si...@z-audio.co.uk>> wrote:
>
> > Nic
the file)
> --8cbed79c91b24f3
>
> The rest of the OAuth variables should be passed on the query string.
>
> I hope this helps.
>
> Cheers,
> Nicholas
> ---
> Nicholas Granado
> email: ngran...@gmail.com
> twitter: heatxsink
> web:
witter
'fixed' their Oauth implementation?
Can anyone else advise if they have got this working and where I might
be going wrong?
Thanks
Simon (Zaudio)
On Aug 19, 11:40 pm, David Carson wrote:
> Got this sorted out and working, and thought I should share the two
> pitfalls w
have to name a member "status" just because it is a Status data
> type...
>
> Marco
>
> 2009/10/7 Zaudio
>
>
>
>
>
> > Sure, I'll justify this mroe...
>
> > One of our apps receives updates via the Streaming API and the various
> > RE
t as user also makes good object sense... but
then the retweeted_status is not 'status' anymore... and it is a
status I'm suggesting soemthing similar for it's inner node..
Simon (Zaudio)
On Oct 6, 12:01 pm, Marco Kaiser wrote:
> No, please don't change that to
ate of the tweet... I alreayd have to contend with a
created_at field in the user and status nodes... now that could double
up... so owuld appreciate an easier to find retweeted user node for
JSON parsability
Thanks
Simon (Zaudio)
On Oct 4, 8:16 am, John Kalucki wrote:
> Retweetis an invasive
Hey John,
Thanks for that... can you put an earliest date on 'very soon' please
- just so I know how long we've got?
Thanks
Simon (Zaudio)
On Oct 3, 8:15 pm, John Kalucki wrote:
> There are plans to filter retweets from various resource, see the
> documentation. Howe
one of our apps gets broken until it's recoded
to handle the retweet payload...
or is the ONLY was to get these vie the retweet methods and the new
home_timeline ? If so, what about apps that mainly make use of the
Streaming API for tweets?
Thanks
Simon (Zaudio)
re: bullsonwallstreet.com
We're getting a few duplicated DMs for a single POST to the API this
morning... anyone else having the same trouble?
We're also seeing loads on 'Server Unavailable' responses surrounding
the times of the duped DMs
Simon (Zaudio)
g now???
Simon
On Aug 12, 3:49 pm, Zaudio wrote:
> My trial has worked so far today... not a singleinvalidnonce
> error but it's only been 12 hours
>
> Simon
>
> On Aug 12, 12:59 pm, "Rob O'Brien" wrote:
>
>
>
> > The interesting th
I get the same with my apps; an authenticated and unauthenticated call
to get rate limits returns the same hits available out of the 20K...
never managed to get an answer why I'm guessing the authentication
is being ignored, and I just get IP limits all the time?
Just go to www.bullsonwallstr
is larger than the last and eachnonceis unique.
>
> Knowing that my values are legit makes me think there's another problem, but
> Twitter hasn't responded to my api@ email.
>
> Rob O'Brien
> Web Application Developer & Consultant
> r...@zepoid.com
>
>
>
We're having the same issue in our app, occurs sporadically in our
logs - but I believe the cause with us is that:
We're generating nonce values as a timestamp seeded sequence of random
numbers
We're creating an instance of the Oauth class that does this for each
logged in user for the app
Thus,
I'm getting the ame problem with bullsonwallstreet.com - previous
whitelisted rates of 2 now down to 150... not recovered yet.
And I throttle all requests to a pretty low level for the REST API...
but still down at 150!
Let's hope that this attack ends soon, and honest users can have the
per
I don't myself think that twitter are doing anything more than
enforcing the standard. I spent 3 hours 'fixing' my code for our
application (uses Shannon Whitley's c# library as a base); I only
found two bugs in thelibrary that caused any problem... the use of
httputility.urlencode in place of the
Mine were all to do with urlencoding, and ensuring all post data is
sent as post data, and none on the querystring for the URL; and thus
ensuring I use the modified URLencoding method required for Oauth -
which was previously being used, but not on the post data!
Once I did that, that test update
22 matches
Mail list logo
