Hey Roy,

Is this running on Google App Engine? We have some problems earlier today
which may have been causing this for you.
If not can you try running:
  curl
http://api.twitter.com/1/statuses/user_timeline.json?since_id=1923315\&screen_name=roytang

and let me know if that works for you.

Matt


On Fri, Jul 23, 2010 at 12:11 PM, Roy <royt...@gmail.com> wrote:

> It's happening consistently with me I'm afraid.
>
> I'm using my own twitter account for testing: roytang.
>
> On Jul 24, 1:36 am, Matt Harris <thematthar...@twitter.com> wrote:
> > A "Something is technically wrong" error sometimes happens but normally
> it
> > goes away when you request again a little bit later. Is this still
> happening
> > when you make that request?
> > If it is could you let us know the screen name which this is happening
> to.
> >
> > Best,
> > Matt
> >
> >
> >
> >
> >
> > On Thu, Jul 22, 2010 at 10:59 PM, Roy <royt...@gmail.com> wrote:
> > > Hi,
> >
> > > I've been encountering this issue: If I access
> >
> > >http://api.twitter.com/1/statuses/user_timeline.json
> >
> > > -> this is fine. But when I pass since_id like so:
> >
> > >http://api.twitter.com/1/statuses/user_timeline.json?since_id=1923315.
> ..
> >
> > > I'm getting the "Something is technically wrong." error page.
> >
> > > I'm using OAuth for authentication using Mike Knapp's oauth.py from
> > >http://github.com/mikeknapp/AppEngine-OAuth-Library
> >
> > > Any idea what I'm doing wrong?
> >
> > > Thanks!
> >
> > --
> >
> > Matt Harris
> > Developer Advocate, Twitterhttp://twitter.com/themattharris
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

Reply via email to