gt; On Fri, Jun 4, 2010 at 9:56 AM, Yann Malet wrote:
> > > Steve,
> > > The image is only 33.7kb and it is a jpg.
> > > Do you have any python sample code for the ?
> > > Regards,
> > > --yml
>
> > > On Fri, Jun 4, 2010 at 9:38 AM, Steve
Twitpic will only 400 Bad Request you if it can't find the image in
your multipart/form-
data or if the image is invalid (not jpg/png/gif or >5MB in size).
Thanks,
Steve C
Twitpic
On Jun 4, 9:20 am, Yann Malet wrote:
> If I send this request to 127.0.0.1:9000 without the file her
I just looked at your code briefly, but I believe the problem is this
line:
oauth_request = TwitpicOAuthRequest(http_method="POST",
http_url=settings.TWITPIC_API_URL,
The OAuth Request needs to be signed using the Twitter Endpoint
(https://api.twitter.com/1/account/verify_credentials.json), not t
Thanks for posting this, I'm glad someone else is seeing the same
issue as us. Similarly, I was disappointed with the response from
Twitter- maybe I didn't explain the problem well enough.
Unfortunately, we had to pull @anywhere from Twitpic until they get
the issue resolved.
Steve Corona
On Jun
erhttp://twitter.com/episod
>
>
>
> On Tue, Jun 1, 2010 at 6:50 AM, Steve C wrote:
> > We had some reports over the weekend of users using older browsers
> > (Firefox 2.0 was mentioned) being auto-redirected to "twitter.com/
> > undefined" due to @anywhere. Anyone else having the same issue?
We had some reports over the weekend of users using older browsers
(Firefox 2.0 was mentioned) being auto-redirected to "twitter.com/
undefined" due to @anywhere. Anyone else having the same issue?
Hi Rich-
Nice catch! During one of our deployments today, we mistakingly
switched the OAuth Echo API to use Twitter's Non-SSL Endpoint. I just
pushed a fix for it- can you let me know if everything works correctly
for you again?
(Coincidently, the deployment that turned off SSL for the API was
tu
rror on ALL browsers
> which do not have firebug installed and running.
>
> -Nischal
>
> On May 19, 11:41 pm, Dan Webb wrote:
>
>
>
> > On Wed, May 19, 2010 at 11:27 AM, Steve C wrote:
> > > We just rolled out @anywhere yesterday and some of our users
Thanks Dan- We appreciate you & your teams hard work.
On May 19, 2:53 pm, Dan Webb wrote:
> On Wed, May 19, 2010 at 11:48 AM, Damon Clinkscales wrote:
> > On Wed, May 19, 2010 at 1:41 PM, Dan Webb wrote:
> >> On Wed, May 19, 2010 at 11:27 AM, Steve C wrote:
> > J
What is your ETA on rolling out the change? We are deciding on whether
we should disable @anywhere until alert() is removed.
On May 19, 2:41 pm, Dan Webb wrote:
> On Wed, May 19, 2010 at 11:27 AM, Steve C wrote:
> > We just rolled out @anywhere yesterday and some of our
We just rolled out @anywhere yesterday and some of our users are
experiencing similar issues.
http://twitpic.com/1p00d6
Steve
On May 14, 6:57 pm, Larry wrote:
> I just came across a coworker's browser that triggered analert() call
> fromanywhere.js. While okay for development, the use ofalert()
11 matches
Mail list logo