date:20100507

Re: [twitter-dev] oAuth

2010-05-07 Thread Abraham Williams

You can get XAuth enabled for one week to convert username/passwords to
access tokens: http://dev.twitter.com/pages/xauth

Abraham

On Fri, May 7, 2010 at 15:00, garyz  wrote:

> We manage many Twitter accounts for clients.  We're switching to
> oAuth, and want to know if there is a way to automate the initial
> security key process (the first time), since many of our accounts
> don't have human intervention.
>



-- 
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.

[twitter-dev] Re: Slow response to twitter updates for a third party app

2010-05-07 Thread Tjaap


I'm seeing exactly the same: big latency and a lot of timeouts. When
posting a tweet, Twitter sometimes does not return a response within
30 seconds. After my curl times out, the app has no way of knowing if
the post made it or not. Sometimes it will appear on Twitter and
sometimes it won't. This effectively breaks our app. Replicated the
error on two different servers (in the Netherlands) and with different
accounts.

I would very much appreciate a reaction from Twitter on this. We are
in the process of switching to OAuth, but I would like to know if I
have to implement a workaround while we're on the old system.
Thanks,

@tjaap

[twitter-dev] oAuth

2010-05-07 Thread garyz

We manage many Twitter accounts for clients.  We're switching to
oAuth, and want to know if there is a way to automate the initial
security key process (the first time), since many of our accounts
don't have human intervention.

Re: [twitter-dev] Re: TCL & oAuth

2010-05-07 Thread Dossy Shiobara

It's pure Tcl.

You'll want your bot to provide the user a URL they will visit in their
browser that will start the OAuth exchange.  Then, you'll need some way
for them to provide the PIN back to the bot when they're done
authorizing your app. in their browser.


On 5/7/10 10:41 AM, Dustin Shea wrote:
> Dossy,
> 
> Your oAuth client you wrote in TCL, is it a client using TCL/TK or is
> it pure TCL? I do ask because I'm still pretty much a novice TCL
> coder and am unsure how I could go about writing something sending
> and receiving these requests, and with looking at doing
> Out-of-band/PIN implementation about causing my app (which will be
> running off of an eggdrop bot) to possibly pop up a browser window or
> at least look at finding a way for the bot to pull this information
> another way and return it to the user. Will see how to work on this
> when I finally get started converting from basic auth to oAuth.


-- 
Dossy Shiobara  | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network   | http://panoptic.com/
  "He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)

Re: [twitter-dev] Why have I recieved a HTTP 601 Response.

2010-05-07 Thread Raffi Krikorian

hi!

are you connecting through a proxy or some other intermediary?  that failure
doesn't seem like it came from the twitter stack.

On Fri, May 7, 2010 at 10:10 AM, Asura  wrote:

> I have some Twitter login problem with my Polaris 6.2 Mobile Browser
> on handset device.
> I’ve been trying to figure it out. But I haven’t found out a problem,
> I really need you guys's answer for that.
> Currently, I use the IE user agent string for compatibility.
> I’ve attached some transaction log.
> Please let me know, if you guys need more information.
> I’m looking forward to your hopeful response.
> Thank you.
>
>
>
> -
> POST http://twitter.com/oauth/authorize HTTP/1.1
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
> application/x-shockwave-flash, application/vnd.ms-excel, application/
> vnd.ms-powerpoint, application/msword, */*
> Accept-Language: ko
> Accept-Encoding: gzip, deflate
> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0);
> 800*480;POLARIS 6.100;em1.0;01057407732
> Host: twitter.com
> Connection: Keep-Alive
> Referer:
> http://twitter.com/oauth/authorize?oauth_token=QQCGC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY
> Proxy-Authorization: Basic OTcyMjQ5NjEwNTp2enc=
> Cookie: guest_id=127181804004115551;
>
> original_referer=LQtHfb3aVLhzTQteZqBtMsK1SG1k6PabMrGGFzkb8SWvN4rcMar6PByaoAj77FrM0MzwLyUG00BPri2ivfClbpZqqFy5G5VDpU5n;
> auth_token=;
>
> _twitter_sess=BAh7CzoPY3JlYXRlZF9hdGwrCKpp52FRh4oAToOcmV0dXJuX3RvIl5odHRwOi8vv50AdHdpdHRlci5jb20vb2F1dGgvYXV0aG9yaXplP29hdXRoX3Rva2VuPVFRQ0dDD50ANGpzdElqMUxONzNMWnh1aDJKaEtFYWVvaWZGN1hmTVNIalpSWToRdHJhbnNff50AcHJvbXB0MDoMY3NyZl9pZCIlYmRiMzYzNWJjZWQ0MjYyZjc4ZDZmODViZTUyy50ANjhiZGM6B2lkIiUxYjg2NmE0OTliNjI0NDljNWUwMTc5Yjg1MWU1YmU1YiIKK50AZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsAA50ABjoKQHVzZWR7AAA53DD53D--
> c2404da8c9fd8ee2a8738deeb9f7b77d49ee0c7d;
> __utmz=43838368.1271818261.2.2.utmcsr=browser.lgtelecom.com|
> utmccn=(referral)|utmcmd=referral|utmcct=/svc_twitter/fb/width/prg/
> information_1.htm;
> __utma=43838368.114323.1271818047.1271818047.1271818261.2;
> __utmc=43838368; __utmv=43838368.langgAA0en;
> __utmb=43838368.4.10.1271818261
> Content-Type: application/x-www-form-urlencoded
> Content-Length: 186
>
> authenticity_token=8e936e0758e27e3bfd5dfba85e62ee418d045f6f&oauth_token=QQCGC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY&sessionnBusername_or_emaillD=minbg717&sessionnBpassworddD=m20062445
>
>
> --
> HTTP/1.1 601 Connect Fail
> Connection: close
> Content-Length: 55
> Connecting to WEB Server Fail
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Re: [twitter-dev] Re: User tag inside users/show

2010-05-07 Thread Taylor Singletary

I wish we could provide an ETA when the operation will be complete, but
Twitter is a complicated beast. We are expiring the caches as quickly as it
is safe to do so. We're hoping it will totally clear within the next 5
hours.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Fri, May 7, 2010 at 11:14 AM, melissa  wrote:

> Thanks Taylor.  Basically, pre-exisiting users appear to fail during
> the verify credentials call.  It seems that we're still getting the
> spurious userid.  We use Tweetsharp.  We tried it with new users and
> it works, and is able to de-serialize the response.  We are getting
> the token fine - it is definitely failing in verification.  We can
> give you an example shortly, but if this sounds like the caching would
> fix it, any ETA on when cache expiration would be completed, or
> anything you can do to clear the cache? We can give you information
> telling you what users/etc if you can manually clear something.
>
> Thanks so much for replying.  BTW, check out our app sometime, it's
> pretty cool ;).
>
> Melissa, Awareness Inc.
>
> On May 7, 12:03 pm, Taylor Singletary 
> wrote:
> > Melissa,
> >
> > We had to pause the cache expiration for a little while yesterday
> afternoon,
> > but it resumed last night. It's going to continue working through the
> queue
> > today.
> >
> > Taylor Singletary
> > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > On Fri, May 7, 2010 at 7:51 AM, Taylor Singletary <
> >
> > taylorsinglet...@twitter.com> wrote:
> > > Hi Melissa,
> >
> > > Sorry to hear you are still down. Can you send along some examples of
> > > payloads still including the embedded user object and the URL used to
> access
> > > it?
> >
> > > Taylor Singletary
> > > Developer Advocate, Twitter
> > >http://twitter.com/episod
> >
> > > On Fri, May 7, 2010 at 7:41 AM, melissa 
> wrote:
> >
> > >> Sorry, missed your last reply.  Anyway, we are still down.  I assume
> > >> propagation *should* have happened - what can we do to debug this?
> >
> > >> On May 7, 10:39 am, melissa  wrote:
> > >> > Guys, we really need an update on this.  I understand if you don;t
> > >> > have a resolution, but not responding at all is not cool.  Looks
> like
> > >> > maybe Tweetsharp, the API we use, thinks the problem is resolved,
> but
> > >> > our customers are still DOWN.  Do we need to redeploy a workaround?
> > >> > What is the ETA?
> >
> > >> > On May 6, 12:19 pm, Taylor Singletary  >
> > >> > wrote:
> >
> > >> > > We're working on getting this fixed as soon as we can.
> >
> > >> > > Taylor Singletary
> > >> > > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > >> > > On Thu, May 6, 2010 at 9:12 AM, irhetoric  >
> > >> wrote:
> > >> > > > This appears to still be broken.  It affects anyone using the
> > >> > > > TweetSharp library as well. There's a workaround (http://
> > >> > > > tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but
> > >> > > > hopefully it will be fixed soon so that we don't have to
> redeploy
> > >> with
> > >> > > > the workaround.
> >
> > >> > > > On May 6, 5:23 am, Raffi Krikorian  wrote:
> > >> > > > > i'm currently looking into this now.
> >
> > >> > > > > On Thu, May 6, 2010 at 4:51 AM, Rich 
> wrote:
> > >> > > > > > Yep looks like I spoke to soon, many of my users are still
> > >> seeing this
> > >> > > > > > issue.  I've actually handled it but Apple are now taking
> about
> > >> a week
> > >> > > > > > to approve updates
> >
> > >> > > > > > On May 6, 6:50 am, Raul  wrote:
> > >> > > > > > > We still see this issue on every request athttp://
> streamd.in,
> > >> Also
> > >> > > > > > > all other apps that use twitter4j are experiencing this
> issue.
> >
> > >> > > > > > > On May 5, 6:04 pm, Taylor Singletary <
> > >> taylorsinglet...@twitter.com>
> > >> > > > > > > wrote:
> >
> > >> > > > > > > > This should now be fixed, though it may take a little
> while
> > >> for the
> > >> > > > > > cache to
> > >> > > > > > > > completely clear the labyrinth.
> >
> > >> > > > > > > > Let us know if you're still having wide spread problems.
> >
> > >> > > > > > > > Thanks!
> > >> > > > > > > > Taylor
> >
> > >> > > > > > > > On Wed, May 5, 2010 at 2:27 PM, Rich  >
> > >> wrote:
> > >> > > > > > > > > Cool, thanks Raffi, I was more concerned if it was
> > >> intentional
> > >> > > > rather
> > >> > > > > > > > > than a bug :)  Of course we all get unintentional bugs
> > >> from time
> > >> > > > to
> > >> > > > > > > > > time
> >
> > >> > > > > > > > > On May 5, 10:21 pm, Raffi Krikorian <
> ra...@twitter.com>
> > >> wrote:
> > >> > > > > > > > > > my stance on versioning is for when something has
> > >> changed that
> > >> > > > > > breaks
> > >> > > > > > > > > > backwards compatibility.  in this case, we haven't
> > >> broken
> > >> > > > backwards
> > >> > > > > > > > > > compatibility, but a regression was introduced.
> > >>  regressions
> > >> > > > can
> > >> > > > > > get
> > >> > > > > > > > > > introduced in a varie

[twitter-dev] Re: User tag inside users/show

2010-05-07 Thread melissa

Taylor, one of our users is now working, I guess we are on the last
servers.not sure if there is any timeframe we can tell our
customers hen we know this will be completed.

Thanks, Melissa
www.awarenessnetworks.com
Follow us on Twitter 


On May 7, 12:03 pm, Taylor Singletary 
wrote:
> Melissa,
>
> We had to pause the cache expiration for a little while yesterday afternoon,
> but it resumed last night. It's going to continue working through the queue
> today.
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Fri, May 7, 2010 at 7:51 AM, Taylor Singletary <
>
> taylorsinglet...@twitter.com> wrote:
> > Hi Melissa,
>
> > Sorry to hear you are still down. Can you send along some examples of
> > payloads still including the embedded user object and the URL used to access
> > it?
>
> > Taylor Singletary
> > Developer Advocate, Twitter
> >http://twitter.com/episod
>
> > On Fri, May 7, 2010 at 7:41 AM, melissa  wrote:
>
> >> Sorry, missed your last reply.  Anyway, we are still down.  I assume
> >> propagation *should* have happened - what can we do to debug this?
>
> >> On May 7, 10:39 am, melissa  wrote:
> >> > Guys, we really need an update on this.  I understand if you don;t
> >> > have a resolution, but not responding at all is not cool.  Looks like
> >> > maybe Tweetsharp, the API we use, thinks the problem is resolved, but
> >> > our customers are still DOWN.  Do we need to redeploy a workaround?
> >> > What is the ETA?
>
> >> > On May 6, 12:19 pm, Taylor Singletary 
> >> > wrote:
>
> >> > > We're working on getting this fixed as soon as we can.
>
> >> > > Taylor Singletary
> >> > > Developer Advocate, Twitterhttp://twitter.com/episod
>
> >> > > On Thu, May 6, 2010 at 9:12 AM, irhetoric 
> >> wrote:
> >> > > > This appears to still be broken.  It affects anyone using the
> >> > > > TweetSharp library as well. There's a workaround (http://
> >> > > > tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but
> >> > > > hopefully it will be fixed soon so that we don't have to redeploy
> >> with
> >> > > > the workaround.
>
> >> > > > On May 6, 5:23 am, Raffi Krikorian  wrote:
> >> > > > > i'm currently looking into this now.
>
> >> > > > > On Thu, May 6, 2010 at 4:51 AM, Rich  wrote:
> >> > > > > > Yep looks like I spoke to soon, many of my users are still
> >> seeing this
> >> > > > > > issue.  I've actually handled it but Apple are now taking about
> >> a week
> >> > > > > > to approve updates
>
> >> > > > > > On May 6, 6:50 am, Raul  wrote:
> >> > > > > > > We still see this issue on every request athttp://streamd.in,
> >> Also
> >> > > > > > > all other apps that use twitter4j are experiencing this issue.
>
> >> > > > > > > On May 5, 6:04 pm, Taylor Singletary <
> >> taylorsinglet...@twitter.com>
> >> > > > > > > wrote:
>
> >> > > > > > > > This should now be fixed, though it may take a little while
> >> for the
> >> > > > > > cache to
> >> > > > > > > > completely clear the labyrinth.
>
> >> > > > > > > > Let us know if you're still having wide spread problems.
>
> >> > > > > > > > Thanks!
> >> > > > > > > > Taylor
>
> >> > > > > > > > On Wed, May 5, 2010 at 2:27 PM, Rich 
> >> wrote:
> >> > > > > > > > > Cool, thanks Raffi, I was more concerned if it was
> >> intentional
> >> > > > rather
> >> > > > > > > > > than a bug :)  Of course we all get unintentional bugs
> >> from time
> >> > > > to
> >> > > > > > > > > time
>
> >> > > > > > > > > On May 5, 10:21 pm, Raffi Krikorian 
> >> wrote:
> >> > > > > > > > > > my stance on versioning is for when something has
> >> changed that
> >> > > > > > breaks
> >> > > > > > > > > > backwards compatibility.  in this case, we haven't
> >> broken
> >> > > > backwards
> >> > > > > > > > > > compatibility, but a regression was introduced.
> >>  regressions
> >> > > > can
> >> > > > > > get
> >> > > > > > > > > > introduced in a variety of different ways, and across a
> >> variety
> >> > > > of
> >> > > > > > > > > different
> >> > > > > > > > > > properties unfortunately.  software projects do their
> >> best to
> >> > > > avoid
> >> > > > > > them
> >> > > > > > > > > --
> >> > > > > > > > > > but its orthogonal to versioning
>
> >> > > > > > > > > > either way - we're working on a fix.
>
> >> > > > > > > > > > On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) <
> >> > > > > > or...@orianmarx.com
> >> > > > > > > > > >wrote:
>
> >> > > > > > > > > > > Well, I'm not sure if Rich was referring to the output
> >> per se
> >> > > > or
> >> > > > > > > > > > > rather that this bug was probably tied to the
> >> skip_user
> >> > > > parameter
> >> > > > > > that
> >> > > > > > > > > > > was just added to timelines... which one could argue
> >> is a
> >> > > > > > candidate
> >> > > > > > > > > > > for versioning.
>
> >> > > > > > > > > > > On May 5, 5:02 pm, Raffi Krikorian 
> >> > > > wrote:
> >> > > > > > > > > > > > versioning has absolutely nothing to do with this -
> >> this is
> >> > > > >

[twitter-dev] Re: User tag inside users/show

2010-05-07 Thread melissa

Thanks Taylor.  Basically, pre-exisiting users appear to fail during
the verify credentials call.  It seems that we're still getting the
spurious userid.  We use Tweetsharp.  We tried it with new users and
it works, and is able to de-serialize the response.  We are getting
the token fine - it is definitely failing in verification.  We can
give you an example shortly, but if this sounds like the caching would
fix it, any ETA on when cache expiration would be completed, or
anything you can do to clear the cache? We can give you information
telling you what users/etc if you can manually clear something.

Thanks so much for replying.  BTW, check out our app sometime, it's
pretty cool ;).

Melissa, Awareness Inc.

On May 7, 12:03 pm, Taylor Singletary 
wrote:
> Melissa,
>
> We had to pause the cache expiration for a little while yesterday afternoon,
> but it resumed last night. It's going to continue working through the queue
> today.
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Fri, May 7, 2010 at 7:51 AM, Taylor Singletary <
>
> taylorsinglet...@twitter.com> wrote:
> > Hi Melissa,
>
> > Sorry to hear you are still down. Can you send along some examples of
> > payloads still including the embedded user object and the URL used to access
> > it?
>
> > Taylor Singletary
> > Developer Advocate, Twitter
> >http://twitter.com/episod
>
> > On Fri, May 7, 2010 at 7:41 AM, melissa  wrote:
>
> >> Sorry, missed your last reply.  Anyway, we are still down.  I assume
> >> propagation *should* have happened - what can we do to debug this?
>
> >> On May 7, 10:39 am, melissa  wrote:
> >> > Guys, we really need an update on this.  I understand if you don;t
> >> > have a resolution, but not responding at all is not cool.  Looks like
> >> > maybe Tweetsharp, the API we use, thinks the problem is resolved, but
> >> > our customers are still DOWN.  Do we need to redeploy a workaround?
> >> > What is the ETA?
>
> >> > On May 6, 12:19 pm, Taylor Singletary 
> >> > wrote:
>
> >> > > We're working on getting this fixed as soon as we can.
>
> >> > > Taylor Singletary
> >> > > Developer Advocate, Twitterhttp://twitter.com/episod
>
> >> > > On Thu, May 6, 2010 at 9:12 AM, irhetoric 
> >> wrote:
> >> > > > This appears to still be broken.  It affects anyone using the
> >> > > > TweetSharp library as well. There's a workaround (http://
> >> > > > tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but
> >> > > > hopefully it will be fixed soon so that we don't have to redeploy
> >> with
> >> > > > the workaround.
>
> >> > > > On May 6, 5:23 am, Raffi Krikorian  wrote:
> >> > > > > i'm currently looking into this now.
>
> >> > > > > On Thu, May 6, 2010 at 4:51 AM, Rich  wrote:
> >> > > > > > Yep looks like I spoke to soon, many of my users are still
> >> seeing this
> >> > > > > > issue.  I've actually handled it but Apple are now taking about
> >> a week
> >> > > > > > to approve updates
>
> >> > > > > > On May 6, 6:50 am, Raul  wrote:
> >> > > > > > > We still see this issue on every request athttp://streamd.in,
> >> Also
> >> > > > > > > all other apps that use twitter4j are experiencing this issue.
>
> >> > > > > > > On May 5, 6:04 pm, Taylor Singletary <
> >> taylorsinglet...@twitter.com>
> >> > > > > > > wrote:
>
> >> > > > > > > > This should now be fixed, though it may take a little while
> >> for the
> >> > > > > > cache to
> >> > > > > > > > completely clear the labyrinth.
>
> >> > > > > > > > Let us know if you're still having wide spread problems.
>
> >> > > > > > > > Thanks!
> >> > > > > > > > Taylor
>
> >> > > > > > > > On Wed, May 5, 2010 at 2:27 PM, Rich 
> >> wrote:
> >> > > > > > > > > Cool, thanks Raffi, I was more concerned if it was
> >> intentional
> >> > > > rather
> >> > > > > > > > > than a bug :)  Of course we all get unintentional bugs
> >> from time
> >> > > > to
> >> > > > > > > > > time
>
> >> > > > > > > > > On May 5, 10:21 pm, Raffi Krikorian 
> >> wrote:
> >> > > > > > > > > > my stance on versioning is for when something has
> >> changed that
> >> > > > > > breaks
> >> > > > > > > > > > backwards compatibility.  in this case, we haven't
> >> broken
> >> > > > backwards
> >> > > > > > > > > > compatibility, but a regression was introduced.
> >>  regressions
> >> > > > can
> >> > > > > > get
> >> > > > > > > > > > introduced in a variety of different ways, and across a
> >> variety
> >> > > > of
> >> > > > > > > > > different
> >> > > > > > > > > > properties unfortunately.  software projects do their
> >> best to
> >> > > > avoid
> >> > > > > > them
> >> > > > > > > > > --
> >> > > > > > > > > > but its orthogonal to versioning
>
> >> > > > > > > > > > either way - we're working on a fix.
>
> >> > > > > > > > > > On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) <
> >> > > > > > or...@orianmarx.com
> >> > > > > > > > > >wrote:
>
> >> > > > > > > > > > > Well, I'm not sure if Rich was referring to the output
> >> per se
> >> > > > or
> >> > > > > > > > > > >

[twitter-dev] Why have I recieved a HTTP 601 Response.

2010-05-07 Thread Asura

I have some Twitter login problem with my Polaris 6.2 Mobile Browser
on handset device.
I’ve been trying to figure it out. But I haven’t found out a problem,
I really need you guys's answer for that.
Currently, I use the IE user agent string for compatibility.
I’ve attached some transaction log.
Please let me know, if you guys need more information.
I’m looking forward to your hopeful response.
Thank you.


-
POST http://twitter.com/oauth/authorize HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/x-shockwave-flash, application/vnd.ms-excel, application/
vnd.ms-powerpoint, application/msword, */*
Accept-Language: ko
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0);
800*480;POLARIS 6.100;em1.0;01057407732
Host: twitter.com
Connection: Keep-Alive
Referer: 
http://twitter.com/oauth/authorize?oauth_token=QQCGC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY
Proxy-Authorization: Basic OTcyMjQ5NjEwNTp2enc=
Cookie: guest_id=127181804004115551;
original_referer=LQtHfb3aVLhzTQteZqBtMsK1SG1k6PabMrGGFzkb8SWvN4rcMar6PByaoAj77FrM0MzwLyUG00BPri2ivfClbpZqqFy5G5VDpU5n;
auth_token=;
_twitter_sess=BAh7CzoPY3JlYXRlZF9hdGwrCKpp52FRh4oAToOcmV0dXJuX3RvIl5odHRwOi8vv50AdHdpdHRlci5jb20vb2F1dGgvYXV0aG9yaXplP29hdXRoX3Rva2VuPVFRQ0dDD50ANGpzdElqMUxONzNMWnh1aDJKaEtFYWVvaWZGN1hmTVNIalpSWToRdHJhbnNff50AcHJvbXB0MDoMY3NyZl9pZCIlYmRiMzYzNWJjZWQ0MjYyZjc4ZDZmODViZTUyy50ANjhiZGM6B2lkIiUxYjg2NmE0OTliNjI0NDljNWUwMTc5Yjg1MWU1YmU1YiIKK50AZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsAA50ABjoKQHVzZWR7AAA53DD53D--
c2404da8c9fd8ee2a8738deeb9f7b77d49ee0c7d;
__utmz=43838368.1271818261.2.2.utmcsr=browser.lgtelecom.com|
utmccn=(referral)|utmcmd=referral|utmcct=/svc_twitter/fb/width/prg/
information_1.htm;
__utma=43838368.114323.1271818047.1271818047.1271818261.2;
__utmc=43838368; __utmv=43838368.langgAA0en;
__utmb=43838368.4.10.1271818261
Content-Type: application/x-www-form-urlencoded
Content-Length: 186
authenticity_token=8e936e0758e27e3bfd5dfba85e62ee418d045f6f&oauth_token=QQCGC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY&sessionnBusername_or_emaillD=minbg717&sessionnBpassworddD=m20062445

--
HTTP/1.1 601 Connect Fail
Connection: close
Content-Length: 55
Connecting to WEB Server Fail

[twitter-dev] Re: xhr2 and cross domain Ajax requests

2010-05-07 Thread Remy Sharp

bump

Would be good to hear from Twitter API devs on this.

On Apr 27, 12:50 am, André Luís  wrote:
> As long as they keep this from affecting other non-API endpoints,
>
> +1
>
> Other than that, it could be disastrous.
>
> --
> André Luís
>
>
>
> On Tue, Apr 27, 2010 at 12:04 AM, rmanalan  wrote:
> > +1
>
> > On Apr 26, 5:01 am, Remy Sharp  wrote:
> >> Is there any thoughts towards setting the following header on the
> >> Twitter API server:
>
> >> Access-Control-Allow-Origin: *
>
> >> For those of us developers working with web technology in closed
> >> environments (such as PhoneGap) we can useXHRcontrolled requests to
> >> Twitter - i.e. we can read headers (like the X-RateLimit-Remaining),
> >> abort requests, handler timeouts and handle the all important fail
> >> whale coming back instead of a JSON response saying it's failed.
>
> >> Such a small change would open up using the web to access the API.
>
> >> What do you think?
>
> >> - Remy.
>
> >> --
> >> Subscription 
> >> settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en

Re: [twitter-dev] Re: User tag inside users/show

2010-05-07 Thread Taylor Singletary

Melissa,

We had to pause the cache expiration for a little while yesterday afternoon,
but it resumed last night. It's going to continue working through the queue
today.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Fri, May 7, 2010 at 7:51 AM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:

> Hi Melissa,
>
> Sorry to hear you are still down. Can you send along some examples of
> payloads still including the embedded user object and the URL used to access
> it?
>
> Taylor Singletary
> Developer Advocate, Twitter
> http://twitter.com/episod
>
>
> On Fri, May 7, 2010 at 7:41 AM, melissa  wrote:
>
>> Sorry, missed your last reply.  Anyway, we are still down.  I assume
>> propagation *should* have happened - what can we do to debug this?
>>
>> On May 7, 10:39 am, melissa  wrote:
>> > Guys, we really need an update on this.  I understand if you don;t
>> > have a resolution, but not responding at all is not cool.  Looks like
>> > maybe Tweetsharp, the API we use, thinks the problem is resolved, but
>> > our customers are still DOWN.  Do we need to redeploy a workaround?
>> > What is the ETA?
>> >
>> > On May 6, 12:19 pm, Taylor Singletary 
>> > wrote:
>> >
>> > > We're working on getting this fixed as soon as we can.
>> >
>> > > Taylor Singletary
>> > > Developer Advocate, Twitterhttp://twitter.com/episod
>> >
>> > > On Thu, May 6, 2010 at 9:12 AM, irhetoric 
>> wrote:
>> > > > This appears to still be broken.  It affects anyone using the
>> > > > TweetSharp library as well. There's a workaround (http://
>> > > > tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but
>> > > > hopefully it will be fixed soon so that we don't have to redeploy
>> with
>> > > > the workaround.
>> >
>> > > > On May 6, 5:23 am, Raffi Krikorian  wrote:
>> > > > > i'm currently looking into this now.
>> >
>> > > > > On Thu, May 6, 2010 at 4:51 AM, Rich  wrote:
>> > > > > > Yep looks like I spoke to soon, many of my users are still
>> seeing this
>> > > > > > issue.  I've actually handled it but Apple are now taking about
>> a week
>> > > > > > to approve updates
>> >
>> > > > > > On May 6, 6:50 am, Raul  wrote:
>> > > > > > > We still see this issue on every request athttp://streamd.in,
>> Also
>> > > > > > > all other apps that use twitter4j are experiencing this issue.
>> >
>> > > > > > > On May 5, 6:04 pm, Taylor Singletary <
>> taylorsinglet...@twitter.com>
>> > > > > > > wrote:
>> >
>> > > > > > > > This should now be fixed, though it may take a little while
>> for the
>> > > > > > cache to
>> > > > > > > > completely clear the labyrinth.
>> >
>> > > > > > > > Let us know if you're still having wide spread problems.
>> >
>> > > > > > > > Thanks!
>> > > > > > > > Taylor
>> >
>> > > > > > > > On Wed, May 5, 2010 at 2:27 PM, Rich 
>> wrote:
>> > > > > > > > > Cool, thanks Raffi, I was more concerned if it was
>> intentional
>> > > > rather
>> > > > > > > > > than a bug :)  Of course we all get unintentional bugs
>> from time
>> > > > to
>> > > > > > > > > time
>> >
>> > > > > > > > > On May 5, 10:21 pm, Raffi Krikorian 
>> wrote:
>> > > > > > > > > > my stance on versioning is for when something has
>> changed that
>> > > > > > breaks
>> > > > > > > > > > backwards compatibility.  in this case, we haven't
>> broken
>> > > > backwards
>> > > > > > > > > > compatibility, but a regression was introduced.
>>  regressions
>> > > > can
>> > > > > > get
>> > > > > > > > > > introduced in a variety of different ways, and across a
>> variety
>> > > > of
>> > > > > > > > > different
>> > > > > > > > > > properties unfortunately.  software projects do their
>> best to
>> > > > avoid
>> > > > > > them
>> > > > > > > > > --
>> > > > > > > > > > but its orthogonal to versioning
>> >
>> > > > > > > > > > either way - we're working on a fix.
>> >
>> > > > > > > > > > On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) <
>> > > > > > or...@orianmarx.com
>> > > > > > > > > >wrote:
>> >
>> > > > > > > > > > > Well, I'm not sure if Rich was referring to the output
>> per se
>> > > > or
>> > > > > > > > > > > rather that this bug was probably tied to the
>> skip_user
>> > > > parameter
>> > > > > > that
>> > > > > > > > > > > was just added to timelines... which one could argue
>> is a
>> > > > > > candidate
>> > > > > > > > > > > for versioning.
>> >
>> > > > > > > > > > > On May 5, 5:02 pm, Raffi Krikorian > >
>> > > > wrote:
>> > > > > > > > > > > > versioning has absolutely nothing to do with this -
>> this is
>> > > > > > clearly a
>> > > > > > > > > > > bug.
>> >
>> > > > > > > > > > > > On Wed, May 5, 2010 at 1:39 PM, Rich <
>> rhyl...@gmail.com>
>> > > > > > wrote:
>> > > > > > > > > > > > > Oh I'll add, I thought the point of a versioned
>> API was
>> > > > that
>> > > > > > this
>> > > > > > > > > sort
>> > > > > > > > > > > > > of thing didn't happen?
>> >
>> > > > > > > > > > > > > On May 5, 9:37 pm, Rich 
>> wrote:
>> > > > > > > > > > > > > > I noticed today inside the user tags an extra

[twitter-dev] Re: OAuth support and reformatted DMs live on user streams

2010-05-07 Thread lqd

I'm just displaying the events as they arrive, eg "John Kalucki
deleted a tweet". If I have the specific status I'll show it's been
deleted and link to it from the event (those 2 can be far from each
other in the timeline). Nothing important really, I was mostly asking
out of curiosity, I don't need them to be hydrated or anything :)

Great new about the OAuth fix!

Thanks for the answers John and Mark
Cheers
Rémy

On May 7, 5:11 pm, Mark McBride  wrote:
> You are correct on point 1.  That should be fixed today.
>
> Sent from mobile device
>
> On May 7, 2010, at 2:38 AM, lqd  wrote:
>
>
>
> > #1 OAuth.
> > This took a long time to debug but I think I found the problem. It
> > looks like you guys expect the OAuth Authorization header params to be
> > separated by a comma (which is OK), AND at least one space (which is
> > not OK). Am I right ? (The spaces after the comma are optional if I
> > remember the OAuth spec correctly.)
>
> > #3 The use cases for hydrated delete events would be exactly the same
> > on your part as the ones for hydrating social events :) (which I
> > believe is to make the stream more useful by itself and not *having*
> > to use the REST API to understand the stream events). I keep user
> > objects ATM, or ask the REST API for statuses or user ids I didn't
> > encounter before, there's no question that it's doable, I was just
> > wondering whether the same thinking would be applied consistently to
> > all events, the delete ones right now and any new ones created in the
> > future ?
>
> > Thanks Mark and John
> > Rémy
> > @ldq
>
> > On May 6, 6:46 pm, Mark McBride  wrote:
> >> Did you adjust the timestamp in that tool?  The hosebird
> >> implementation tolerates at most a 5 minute clock skew... in other
> >> words if it receives a timestamp that is 5 minutes older (or newer)
> >> than the current time, it rejects the request.
>
> >>    ---Mark
>
> >>http://twitter.com/mccv
>
> >> On Thu, May 6, 2010 at 6:39 AM, lqd  wrote:
> >>> Hey guys, a couple questions/remarks on the new user streams  
> >>> features:
>
> >>> 1) OAuth
> >>> I have no problem using the stream with BasicAuth, nor using the  
> >>> REST
> >>> API with OAuth. However I'm always getting 401s with OAuth on the
> >>> stream, even though Zac's fork or earlybird works flawlessly.
> >>> Just to try and locate the problem I tried signing the request with
> >>> the official noob tool athttp://hueniverse.com/2008/10/beginners-
> >>> guide-to-oauth-part-iv-signin...
> >>> and sending the header with curl (with fiddling with spaces, tabs &
> >>> newline just in case, and even the realm value - just because
> >>> earlybird's impl doesn't send it), and I still can't login. While my
> >>> own code signing matches the parameters this tool outputs (and works
> >>> on api.twitter.com) it doesn't match what the ruby gem generates,  
> >>> even
> >>> when using the same timestamp and nonce, so I was suspecting some
> >>> difference in the base string. (I don't know Ruby, or how to get the
> >>> Base String there, but there's apparently a signature_base_string
> >>> method, and it did seem to have all the oauth params in the query
> >>> string)
>
> >>> 2) +1 on the user burping at the beginning :)
>
> >>> 3) Are the deletion notices going to be hydrated too ? ATM it's a
> >>> little raw. While it's understandable for the status not to be there
> >>> since it's just been deleted, maybe the full JSON user could be  
> >>> there
> >>> instead of just its id ?
>
> >>> Thanks
> >>> Rémy
> >>> @lqd
>
> >>> On May 6, 12:41 am, Mark McBride  wrote:
>  Ok.  The query string OAuth variant should be working now.  We only
>  support HMAC-SHA1 (just like twitter.com does) for signature  
>  methods,
>  and don't have plans to support other schemes.
>
>     ---Mark
>
> http://twitter.com/mccv
>
>  On Wed, May 5, 2010 at 3:21 PM, John Kalucki   
>  wrote:
> > We should probably just burp the whole user object out at  
> > connection start.
>
> > On Wed, May 5, 2010 at 3:12 PM, Zac Bowling   
> > wrote:
> >> Hydrated message support in earlybird!
>
> >>http://github.com/zbowling/earlybird/
>
> >> OAuth in query string doesn't work  and only HMAC-SHA1  
> >> signature (unless you
> >> only allow plaintext over SSL) but its fine.
>
> >> One feature request would be an inital event with the users  
> >> credentials just
> >> like how the user's social graph comes down initially. Right  
> >> now I don't
> >> know the user's screen_name unless I also hit api.twitter.com  
> >> or he tells me
> >> on the command line. With that I could drop the dependency on  
> >> the twitter
> >> gem.
>
> >> Zac Bowling
> >> @zbowling
>
> >> On Wed, May 5, 2010 at 10:54 AM, Mark McBride  
> >>  wrote:
>
> >>> It should support both.  Can you send me a direct email with a  
> >>> URL
> >>> that you tried?
>
> >>>   ---Mark
>
> >>>http

Re: [twitter-dev] Re: OAuth support and reformatted DMs live on user streams

2010-05-07 Thread Mark McBride


You are correct on point 1.  That should be fixed today.

Sent from mobile device

On May 7, 2010, at 2:38 AM, lqd  wrote:


#1 OAuth.
This took a long time to debug but I think I found the problem. It
looks like you guys expect the OAuth Authorization header params to be
separated by a comma (which is OK), AND at least one space (which is
not OK). Am I right ? (The spaces after the comma are optional if I
remember the OAuth spec correctly.)

#3 The use cases for hydrated delete events would be exactly the same
on your part as the ones for hydrating social events :) (which I
believe is to make the stream more useful by itself and not *having*
to use the REST API to understand the stream events). I keep user
objects ATM, or ask the REST API for statuses or user ids I didn't
encounter before, there's no question that it's doable, I was just
wondering whether the same thinking would be applied consistently to
all events, the delete ones right now and any new ones created in the
future ?

Thanks Mark and John
Rémy
@ldq

On May 6, 6:46 pm, Mark McBride  wrote:

Did you adjust the timestamp in that tool?  The hosebird
implementation tolerates at most a 5 minute clock skew... in other
words if it receives a timestamp that is 5 minutes older (or newer)
than the current time, it rejects the request.

   ---Mark

http://twitter.com/mccv



On Thu, May 6, 2010 at 6:39 AM, lqd  wrote:
Hey guys, a couple questions/remarks on the new user streams  
features:



1) OAuth
I have no problem using the stream with BasicAuth, nor using the  
REST

API with OAuth. However I'm always getting 401s with OAuth on the
stream, even though Zac's fork or earlybird works flawlessly.
Just to try and locate the problem I tried signing the request with
the official noob tool athttp://hueniverse.com/2008/10/beginners- 
guide-to-oauth-part-iv-signin...

and sending the header with curl (with fiddling with spaces, tabs &
newline just in case, and even the realm value - just because
earlybird's impl doesn't send it), and I still can't login. While my
own code signing matches the parameters this tool outputs (and works
on api.twitter.com) it doesn't match what the ruby gem generates,  
even

when using the same timestamp and nonce, so I was suspecting some
difference in the base string. (I don't know Ruby, or how to get the
Base String there, but there's apparently a signature_base_string
method, and it did seem to have all the oauth params in the query
string)



2) +1 on the user burping at the beginning :)



3) Are the deletion notices going to be hydrated too ? ATM it's a
little raw. While it's understandable for the status not to be there
since it's just been deleted, maybe the full JSON user could be  
there

instead of just its id ?



Thanks
Rémy
@lqd



On May 6, 12:41 am, Mark McBride  wrote:

Ok.  The query string OAuth variant should be working now.  We only
support HMAC-SHA1 (just like twitter.com does) for signature  
methods,

and don't have plans to support other schemes.



   ---Mark



http://twitter.com/mccv


On Wed, May 5, 2010 at 3:21 PM, John Kalucki   
wrote:
We should probably just burp the whole user object out at  
connection start.


On Wed, May 5, 2010 at 3:12 PM, Zac Bowling   
wrote:

Hydrated message support in earlybird!



http://github.com/zbowling/earlybird/


OAuth in query string doesn't work  and only HMAC-SHA1  
signature (unless you

only allow plaintext over SSL) but its fine.


One feature request would be an inital event with the users  
credentials just
like how the user's social graph comes down initially. Right  
now I don't
know the user's screen_name unless I also hit api.twitter.com  
or he tells me
on the command line. With that I could drop the dependency on  
the twitter

gem.



Zac Bowling
@zbowling


On Wed, May 5, 2010 at 10:54 AM, Mark McBride  
 wrote:


It should support both.  Can you send me a direct email with a  
URL

that you tried?



  ---Mark



http://twitter.com/mccv


On Wed, May 5, 2010 at 10:38 AM, Zac Bowling  
 wrote:

My fork of earlybird works:



http://github.com/zbowling/earlybird/



Fixing it to support hydrated objects.


One thing is that it doesn't appear to support query string  
passed OAuth

params but if I pass it as authentication headers it works.



Zac Bowling


On Wed, May 5, 2010 at 10:31 AM, Mark McBride  


wrote:


OAuth support on betastream is live now.  This is different  
OAuth
implementation than we use on twitter.com, so if you find  
any rough

edges please let us know quick like.


The changes to make direct messages more distinguishable  
from tweets
has also been pushed.  This will probably require some  
changes in

parsing logic when dealing with DMs.



  ---Mark



http://twitter.com/mccv

Re: [twitter-dev] Re: User tag inside users/show

2010-05-07 Thread Taylor Singletary

Hi Melissa,

Sorry to hear you are still down. Can you send along some examples of
payloads still including the embedded user object and the URL used to access
it?

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Fri, May 7, 2010 at 7:41 AM, melissa  wrote:

> Sorry, missed your last reply.  Anyway, we are still down.  I assume
> propagation *should* have happened - what can we do to debug this?
>
> On May 7, 10:39 am, melissa  wrote:
> > Guys, we really need an update on this.  I understand if you don;t
> > have a resolution, but not responding at all is not cool.  Looks like
> > maybe Tweetsharp, the API we use, thinks the problem is resolved, but
> > our customers are still DOWN.  Do we need to redeploy a workaround?
> > What is the ETA?
> >
> > On May 6, 12:19 pm, Taylor Singletary 
> > wrote:
> >
> > > We're working on getting this fixed as soon as we can.
> >
> > > Taylor Singletary
> > > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > > On Thu, May 6, 2010 at 9:12 AM, irhetoric 
> wrote:
> > > > This appears to still be broken.  It affects anyone using the
> > > > TweetSharp library as well. There's a workaround (http://
> > > > tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but
> > > > hopefully it will be fixed soon so that we don't have to redeploy
> with
> > > > the workaround.
> >
> > > > On May 6, 5:23 am, Raffi Krikorian  wrote:
> > > > > i'm currently looking into this now.
> >
> > > > > On Thu, May 6, 2010 at 4:51 AM, Rich  wrote:
> > > > > > Yep looks like I spoke to soon, many of my users are still seeing
> this
> > > > > > issue.  I've actually handled it but Apple are now taking about a
> week
> > > > > > to approve updates
> >
> > > > > > On May 6, 6:50 am, Raul  wrote:
> > > > > > > We still see this issue on every request athttp://streamd.in,
> Also
> > > > > > > all other apps that use twitter4j are experiencing this issue.
> >
> > > > > > > On May 5, 6:04 pm, Taylor Singletary <
> taylorsinglet...@twitter.com>
> > > > > > > wrote:
> >
> > > > > > > > This should now be fixed, though it may take a little while
> for the
> > > > > > cache to
> > > > > > > > completely clear the labyrinth.
> >
> > > > > > > > Let us know if you're still having wide spread problems.
> >
> > > > > > > > Thanks!
> > > > > > > > Taylor
> >
> > > > > > > > On Wed, May 5, 2010 at 2:27 PM, Rich 
> wrote:
> > > > > > > > > Cool, thanks Raffi, I was more concerned if it was
> intentional
> > > > rather
> > > > > > > > > than a bug :)  Of course we all get unintentional bugs from
> time
> > > > to
> > > > > > > > > time
> >
> > > > > > > > > On May 5, 10:21 pm, Raffi Krikorian 
> wrote:
> > > > > > > > > > my stance on versioning is for when something has changed
> that
> > > > > > breaks
> > > > > > > > > > backwards compatibility.  in this case, we haven't broken
> > > > backwards
> > > > > > > > > > compatibility, but a regression was introduced.
>  regressions
> > > > can
> > > > > > get
> > > > > > > > > > introduced in a variety of different ways, and across a
> variety
> > > > of
> > > > > > > > > different
> > > > > > > > > > properties unfortunately.  software projects do their
> best to
> > > > avoid
> > > > > > them
> > > > > > > > > --
> > > > > > > > > > but its orthogonal to versioning
> >
> > > > > > > > > > either way - we're working on a fix.
> >
> > > > > > > > > > On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) <
> > > > > > or...@orianmarx.com
> > > > > > > > > >wrote:
> >
> > > > > > > > > > > Well, I'm not sure if Rich was referring to the output
> per se
> > > > or
> > > > > > > > > > > rather that this bug was probably tied to the skip_user
> > > > parameter
> > > > > > that
> > > > > > > > > > > was just added to timelines... which one could argue is
> a
> > > > > > candidate
> > > > > > > > > > > for versioning.
> >
> > > > > > > > > > > On May 5, 5:02 pm, Raffi Krikorian 
> > > > wrote:
> > > > > > > > > > > > versioning has absolutely nothing to do with this -
> this is
> > > > > > clearly a
> > > > > > > > > > > bug.
> >
> > > > > > > > > > > > On Wed, May 5, 2010 at 1:39 PM, Rich <
> rhyl...@gmail.com>
> > > > > > wrote:
> > > > > > > > > > > > > Oh I'll add, I thought the point of a versioned API
> was
> > > > that
> > > > > > this
> > > > > > > > > sort
> > > > > > > > > > > > > of thing didn't happen?
> >
> > > > > > > > > > > > > On May 5, 9:37 pm, Rich  wrote:
> > > > > > > > > > > > > > I noticed today inside the user tags an extra
> user tag
> > > > has
> > > > > > > > > appeared
> >
> > > > > > > > > > > > > > We now have user->status->user
> >
> > > > > > > > > > > > > > This is causing a crash on my app and number of
> engines
> > > > > > I've
> > > > > > > > > tried.
> > > > > > > > > > > > > > When did this get added and did I miss the
> > > > notification?
> >
> > > > > > > > > > > > > > Many thanks
> > > > > > > > > > > > > > Richard
> >
> > > > > > > > > > > > --
> > > > > > > > > > > > Raffi Krikorian
> >

[twitter-dev] Re: User tag inside users/show

2010-05-07 Thread melissa

Sorry, missed your last reply.  Anyway, we are still down.  I assume
propagation *should* have happened - what can we do to debug this?

On May 7, 10:39 am, melissa  wrote:
> Guys, we really need an update on this.  I understand if you don;t
> have a resolution, but not responding at all is not cool.  Looks like
> maybe Tweetsharp, the API we use, thinks the problem is resolved, but
> our customers are still DOWN.  Do we need to redeploy a workaround?
> What is the ETA?
>
> On May 6, 12:19 pm, Taylor Singletary 
> wrote:
>
> > We're working on getting this fixed as soon as we can.
>
> > Taylor Singletary
> > Developer Advocate, Twitterhttp://twitter.com/episod
>
> > On Thu, May 6, 2010 at 9:12 AM, irhetoric  wrote:
> > > This appears to still be broken.  It affects anyone using the
> > > TweetSharp library as well. There's a workaround (http://
> > > tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but
> > > hopefully it will be fixed soon so that we don't have to redeploy with
> > > the workaround.
>
> > > On May 6, 5:23 am, Raffi Krikorian  wrote:
> > > > i'm currently looking into this now.
>
> > > > On Thu, May 6, 2010 at 4:51 AM, Rich  wrote:
> > > > > Yep looks like I spoke to soon, many of my users are still seeing this
> > > > > issue.  I've actually handled it but Apple are now taking about a week
> > > > > to approve updates
>
> > > > > On May 6, 6:50 am, Raul  wrote:
> > > > > > We still see this issue on every request athttp://streamd.in, Also
> > > > > > all other apps that use twitter4j are experiencing this issue.
>
> > > > > > On May 5, 6:04 pm, Taylor Singletary 
> > > > > > wrote:
>
> > > > > > > This should now be fixed, though it may take a little while for 
> > > > > > > the
> > > > > cache to
> > > > > > > completely clear the labyrinth.
>
> > > > > > > Let us know if you're still having wide spread problems.
>
> > > > > > > Thanks!
> > > > > > > Taylor
>
> > > > > > > On Wed, May 5, 2010 at 2:27 PM, Rich  wrote:
> > > > > > > > Cool, thanks Raffi, I was more concerned if it was intentional
> > > rather
> > > > > > > > than a bug :)  Of course we all get unintentional bugs from time
> > > to
> > > > > > > > time
>
> > > > > > > > On May 5, 10:21 pm, Raffi Krikorian  wrote:
> > > > > > > > > my stance on versioning is for when something has changed that
> > > > > breaks
> > > > > > > > > backwards compatibility.  in this case, we haven't broken
> > > backwards
> > > > > > > > > compatibility, but a regression was introduced.  regressions
> > > can
> > > > > get
> > > > > > > > > introduced in a variety of different ways, and across a 
> > > > > > > > > variety
> > > of
> > > > > > > > different
> > > > > > > > > properties unfortunately.  software projects do their best to
> > > avoid
> > > > > them
> > > > > > > > --
> > > > > > > > > but its orthogonal to versioning
>
> > > > > > > > > either way - we're working on a fix.
>
> > > > > > > > > On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) <
> > > > > or...@orianmarx.com
> > > > > > > > >wrote:
>
> > > > > > > > > > Well, I'm not sure if Rich was referring to the output per 
> > > > > > > > > > se
> > > or
> > > > > > > > > > rather that this bug was probably tied to the skip_user
> > > parameter
> > > > > that
> > > > > > > > > > was just added to timelines... which one could argue is a
> > > > > candidate
> > > > > > > > > > for versioning.
>
> > > > > > > > > > On May 5, 5:02 pm, Raffi Krikorian 
> > > wrote:
> > > > > > > > > > > versioning has absolutely nothing to do with this - this 
> > > > > > > > > > > is
> > > > > clearly a
> > > > > > > > > > bug.
>
> > > > > > > > > > > On Wed, May 5, 2010 at 1:39 PM, Rich 
> > > > > wrote:
> > > > > > > > > > > > Oh I'll add, I thought the point of a versioned API was
> > > that
> > > > > this
> > > > > > > > sort
> > > > > > > > > > > > of thing didn't happen?
>
> > > > > > > > > > > > On May 5, 9:37 pm, Rich  wrote:
> > > > > > > > > > > > > I noticed today inside the user tags an extra user tag
> > > has
> > > > > > > > appeared
>
> > > > > > > > > > > > > We now have user->status->user
>
> > > > > > > > > > > > > This is causing a crash on my app and number of 
> > > > > > > > > > > > > engines
> > > > > I've
> > > > > > > > tried.
> > > > > > > > > > > > > When did this get added and did I miss the
> > > notification?
>
> > > > > > > > > > > > > Many thanks
> > > > > > > > > > > > > Richard
>
> > > > > > > > > > > --
> > > > > > > > > > > Raffi Krikorian
> > > > > > > > > > > Twitter Platform Teamhttp://twitter.com/raffi
>
> > > > > > > > > --
> > > > > > > > > Raffi Krikorian
> > > > > > > > > Twitter Platform Teamhttp://twitter.com/raffi
>
> > > > --
> > > > Raffi Krikorian
> > > > Twitter Platform Teamhttp://twitter.com/raffi

Re: [twitter-dev] Re: TCL & oAuth

2010-05-07 Thread Dustin Shea

Dossy,

Your oAuth client you wrote in TCL, is it a client using TCL/TK or is it pure 
TCL? I do ask because I'm still pretty much a novice TCL coder and am unsure 
how I could go about writing something sending and receiving these requests, 
and with looking at doing Out-of-band/PIN implementation about causing my app 
(which will be running off of an eggdrop bot) to possibly pop up a browser 
window or at least look at finding a way for the bot to pull this information 
another way and return it to the user. Will see how to work on this when I 
finally get started converting from basic auth to oAuth.

-Dustin

On 5/6/2010 9:50 PM, Dustin wrote:
> I was lookin at maybe doing Out-of-band/PIN Code Authentication.
> However, I don't see much documentation on how to go about doing this.
> 
> On May 6, 4:48 pm, Dossy Shiobara  wrote:
>> I have written an OAuth client in Tcl for Twitter Karma, but it's in no
>> condition to open source at the moment.
>>
>> However, I can tell you that the sha1 package (for sha1::hmac) works,
>> and the base64 package (for base64::encode) too.
>>
>> OAuth really isn't that hard to implement, really.  And, from the sounds
>> of it, you don't even need a full OAuth consumer implementation, just a
>> working access token for your account - perhaps there's a simple utility
>> out there that you can feed your consumer key and secret into and have
>> it output your access token that you can then use.
>>
>> On 5/6/10 5:01 PM, Dustin wrote:
>>
>>> I currently have been working on an application under TCL to post my
>>> twitter timeline, direct messages, profile information and such
>>> (almost a full TCL app) for my IRC eggdrop bot. I've been using the
>>> Basic Authentication method and I've just read come 6/30 I won't be
>>> able to use this method any longer. Has anyone come across an oAuth
>>> library for TCL that I can look into using so I can continue to work
>>> on this project of mine and not have it die when the Basic Auth method
>>> dies here soon?
>>
>>> If you are interested in what I have ATM, my code can be found here:
>>> http://github.com/demonicpagan/Stormbot-TCL-Twitter-Module/blob/maste...
>>
>>> Any help for the conversion will be greatly appreciated.
>>
>> --
>> Dossy Shiobara  | do...@panoptic.com |http://dossy.org/
>> Panoptic Computer Network   |http://panoptic.com/
>>   "He realized the fastest way to change is to laugh at your own
>> folly -- then you can let go and quickly move on." (p. 70)

[twitter-dev] Re: User tag inside users/show

2010-05-07 Thread melissa

Guys, we really need an update on this.  I understand if you don;t
have a resolution, but not responding at all is not cool.  Looks like
maybe Tweetsharp, the API we use, thinks the problem is resolved, but
our customers are still DOWN.  Do we need to redeploy a workaround?
What is the ETA?

On May 6, 12:19 pm, Taylor Singletary 
wrote:
> We're working on getting this fixed as soon as we can.
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Thu, May 6, 2010 at 9:12 AM, irhetoric  wrote:
> > This appears to still be broken.  It affects anyone using the
> > TweetSharp library as well. There's a workaround (http://
> > tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but
> > hopefully it will be fixed soon so that we don't have to redeploy with
> > the workaround.
>
> > On May 6, 5:23 am, Raffi Krikorian  wrote:
> > > i'm currently looking into this now.
>
> > > On Thu, May 6, 2010 at 4:51 AM, Rich  wrote:
> > > > Yep looks like I spoke to soon, many of my users are still seeing this
> > > > issue.  I've actually handled it but Apple are now taking about a week
> > > > to approve updates
>
> > > > On May 6, 6:50 am, Raul  wrote:
> > > > > We still see this issue on every request athttp://streamd.in, Also
> > > > > all other apps that use twitter4j are experiencing this issue.
>
> > > > > On May 5, 6:04 pm, Taylor Singletary 
> > > > > wrote:
>
> > > > > > This should now be fixed, though it may take a little while for the
> > > > cache to
> > > > > > completely clear the labyrinth.
>
> > > > > > Let us know if you're still having wide spread problems.
>
> > > > > > Thanks!
> > > > > > Taylor
>
> > > > > > On Wed, May 5, 2010 at 2:27 PM, Rich  wrote:
> > > > > > > Cool, thanks Raffi, I was more concerned if it was intentional
> > rather
> > > > > > > than a bug :)  Of course we all get unintentional bugs from time
> > to
> > > > > > > time
>
> > > > > > > On May 5, 10:21 pm, Raffi Krikorian  wrote:
> > > > > > > > my stance on versioning is for when something has changed that
> > > > breaks
> > > > > > > > backwards compatibility.  in this case, we haven't broken
> > backwards
> > > > > > > > compatibility, but a regression was introduced.  regressions
> > can
> > > > get
> > > > > > > > introduced in a variety of different ways, and across a variety
> > of
> > > > > > > different
> > > > > > > > properties unfortunately.  software projects do their best to
> > avoid
> > > > them
> > > > > > > --
> > > > > > > > but its orthogonal to versioning
>
> > > > > > > > either way - we're working on a fix.
>
> > > > > > > > On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) <
> > > > or...@orianmarx.com
> > > > > > > >wrote:
>
> > > > > > > > > Well, I'm not sure if Rich was referring to the output per se
> > or
> > > > > > > > > rather that this bug was probably tied to the skip_user
> > parameter
> > > > that
> > > > > > > > > was just added to timelines... which one could argue is a
> > > > candidate
> > > > > > > > > for versioning.
>
> > > > > > > > > On May 5, 5:02 pm, Raffi Krikorian 
> > wrote:
> > > > > > > > > > versioning has absolutely nothing to do with this - this is
> > > > clearly a
> > > > > > > > > bug.
>
> > > > > > > > > > On Wed, May 5, 2010 at 1:39 PM, Rich 
> > > > wrote:
> > > > > > > > > > > Oh I'll add, I thought the point of a versioned API was
> > that
> > > > this
> > > > > > > sort
> > > > > > > > > > > of thing didn't happen?
>
> > > > > > > > > > > On May 5, 9:37 pm, Rich  wrote:
> > > > > > > > > > > > I noticed today inside the user tags an extra user tag
> > has
> > > > > > > appeared
>
> > > > > > > > > > > > We now have user->status->user
>
> > > > > > > > > > > > This is causing a crash on my app and number of engines
> > > > I've
> > > > > > > tried.
> > > > > > > > > > > > When did this get added and did I miss the
> > notification?
>
> > > > > > > > > > > > Many thanks
> > > > > > > > > > > > Richard
>
> > > > > > > > > > --
> > > > > > > > > > Raffi Krikorian
> > > > > > > > > > Twitter Platform Teamhttp://twitter.com/raffi
>
> > > > > > > > --
> > > > > > > > Raffi Krikorian
> > > > > > > > Twitter Platform Teamhttp://twitter.com/raffi
>
> > > --
> > > Raffi Krikorian
> > > Twitter Platform Teamhttp://twitter.com/raffi

Re: [twitter-dev] Re: TCL & oAuth

2010-05-07 Thread Dustin Shea

I am partly there in that case then. I already have my application set as a 
desktop client. It's just a matter of writing the rest of the code and learning 
to use an oAuth library once I find one for TCL.

On 5/7/2010 9:06 AM, Taylor Singletary wrote:
> I'll be updating the documentation on the PIN code, out-of-band mode
> support soon.
> 
> The high-level is that it's exactly like the full OAuth flow, with the
> exception that your sever never receives a callback indicating that the
> user has authorized your application. Instead, they are presented with a
> screen that gives them a short "PIN code" that they'll then enter into a
> UI that you present in your application. 
> 
> You then perform the access token arm of the OAuth trip, just as if you
> were doing it in the normal course of OAuth, except you use the
> oauth_verifier that the user gave you (the PIN code) instead of one sent
> to you by an oauth_callback.
> 
> To turn out of band mode on, you simply mark your application as a
> "desktop application" on dev.twitter.com , and
> to be fully proper you'll also specify an oauth_callback value of "oob"
> when sending your request token request. 
> 
> Taylor Singletary
> Developer Advocate, Twitter
> http://twitter.com/episod
> 
> 
> On Thu, May 6, 2010 at 7:50 PM, Dustin  > wrote:
> 
> I was lookin at maybe doing Out-of-band/PIN Code Authentication.
> However, I don't see much documentation on how to go about doing this.
> 
> On May 6, 4:48 pm, Dossy Shiobara  > wrote:
> > I have written an OAuth client in Tcl for Twitter Karma, but it's
> in no
> > condition to open source at the moment.
> >
> > However, I can tell you that the sha1 package (for sha1::hmac) works,
> > and the base64 package (for base64::encode) too.
> >
> > OAuth really isn't that hard to implement, really.  And, from the
> sounds
> > of it, you don't even need a full OAuth consumer implementation,
> just a
> > working access token for your account - perhaps there's a simple
> utility
> > out there that you can feed your consumer key and secret into and have
> > it output your access token that you can then use.
> >
> > On 5/6/10 5:01 PM, Dustin wrote:
> >
> > > I currently have been working on an application under TCL to post my
> > > twitter timeline, direct messages, profile information and such
> > > (almost a full TCL app) for my IRC eggdrop bot. I've been using the
> > > Basic Authentication method and I've just read come 6/30 I won't be
> > > able to use this method any longer. Has anyone come across an oAuth
> > > library for TCL that I can look into using so I can continue to work
> > > on this project of mine and not have it die when the Basic Auth
> method
> > > dies here soon?
> >
> > > If you are interested in what I have ATM, my code can be found here:
> >
> >http://github.com/demonicpagan/Stormbot-TCL-Twitter-Module/blob/maste...
> >
> > > Any help for the conversion will be greatly appreciated.
> >
> > --
> > Dossy Shiobara  | do...@panoptic.com
>  |http://dossy.org/
> > Panoptic Computer Network   |http://panoptic.com/
> >   "He realized the fastest way to change is to laugh at your own
> > folly -- then you can let go and quickly move on." (p. 70)
> 
>

Re: [twitter-dev] Re: TCL & oAuth

2010-05-07 Thread Taylor Singletary

I'll be updating the documentation on the PIN code, out-of-band mode support
soon.

The high-level is that it's exactly like the full OAuth flow, with the
exception that your sever never receives a callback indicating that the user
has authorized your application. Instead, they are presented with a screen
that gives them a short "PIN code" that they'll then enter into a UI that
you present in your application.

You then perform the access token arm of the OAuth trip, just as if you were
doing it in the normal course of OAuth, except you use the oauth_verifier
that the user gave you (the PIN code) instead of one sent to you by an
oauth_callback.

To turn out of band mode on, you simply mark your application as a "desktop
application" on dev.twitter.com, and to be fully proper you'll also specify
an oauth_callback value of "oob" when sending your request token request.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod

On Thu, May 6, 2010 at 7:50 PM, Dustin  wrote:

> I was lookin at maybe doing Out-of-band/PIN Code Authentication.
> However, I don't see much documentation on how to go about doing this.
>
> On May 6, 4:48 pm, Dossy Shiobara  wrote:
> > I have written an OAuth client in Tcl for Twitter Karma, but it's in no
> > condition to open source at the moment.
> >
> > However, I can tell you that the sha1 package (for sha1::hmac) works,
> > and the base64 package (for base64::encode) too.
> >
> > OAuth really isn't that hard to implement, really.  And, from the sounds
> > of it, you don't even need a full OAuth consumer implementation, just a
> > working access token for your account - perhaps there's a simple utility
> > out there that you can feed your consumer key and secret into and have
> > it output your access token that you can then use.
> >
> > On 5/6/10 5:01 PM, Dustin wrote:
> >
> > > I currently have been working on an application under TCL to post my
> > > twitter timeline, direct messages, profile information and such
> > > (almost a full TCL app) for my IRC eggdrop bot. I've been using the
> > > Basic Authentication method and I've just read come 6/30 I won't be
> > > able to use this method any longer. Has anyone come across an oAuth
> > > library for TCL that I can look into using so I can continue to work
> > > on this project of mine and not have it die when the Basic Auth method
> > > dies here soon?
> >
> > > If you are interested in what I have ATM, my code can be found here:
> > >http://github.com/demonicpagan/Stormbot-TCL-Twitter-Module/blob/maste.
> ..
> >
> > > Any help for the conversion will be greatly appreciated.
> >
> > --
> > Dossy Shiobara  | do...@panoptic.com |http://dossy.org/
> > Panoptic Computer Network   |http://panoptic.com/
> >   "He realized the fastest way to change is to laugh at your own
> > folly -- then you can let go and quickly move on." (p. 70)
>

Re: [twitter-dev] nested user object bug in statuses/friends

2010-05-07 Thread Taylor Singletary

Hi Ken,

We've done our best to fully purge the cache from the system -- are you
still seeing the issue today?

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod

On Thu, May 6, 2010 at 7:43 PM, Ken  wrote:

> I noticed nested user tag issue at statuses/friends API.
>
> It seems to be same as following another API's report:
>
> http://groups.google.com/group/twitter-development-talk/browse_thread/thread/560a544d6703f2b9
>
> Thanks
> Ken
>

Re: [twitter-dev] Re: Malformed XML in some Atom feeds...

2010-05-07 Thread Taylor Singletary

Hi Claudia,

Could you paste a little bit of the invalid ATOM feed you are still
receiving it? This problem should be fixed now, but it's possible that some
persistent cache elements may still have the unencoded ampersand within
them.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Fri, May 7, 2010 at 3:57 AM, Claudia A. V. Callegari <
claudia.avcalleg...@gmail.com> wrote:

> Hello!
>
> Sorry for my English.
> I'm also having the same problem, has agumar forecast for this
> problem?
>
> Thanks
> Claudia Antonini  Vitiello  Callegari
> São Paulo -  Brasil
>
> On 4 maio, 12:33, Taylor Singletary 
> wrote:
> > Hi Brandon,
> >
> > Thanks for the bug report. We'll work on getting this fixed quickly.
> >
> > Thanks!
> >
> > Taylor Singletary
> > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > On Tue, May 4, 2010 at 7:54 AM, Brandon Stone  wrote:
> > > One very popular Twitter list is Scoble's Tech News Brands list:
> >
> > >http://api.twitter.com/1/Scobleizer/lists/tech-news-brands/statuses.a.
> ..
> >
> > > I've got a program that's been watching this feed for a while now.
>  Just
> > > yesterday I started getting some XML parsing errors.  I can create a
> hack to
> > > make this work again on my end, but it's definitely best for Twitter to
> make
> > > sure their XML is well-formed.
> >
> > > Here's what feed validator says:
> >
> > >http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.c.
> ..
> >
> > >> Sorry
> >
> > >> This feed does not validate.
> >
> > >> line 482<
> http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.c...>,
> > >> column 73: XML parsing error: :482:73: not well-formed
> (invalid
> > >> token) [help ]
> >
> > >> http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=16...
> >
> > > It looks like whenever a  of "Google" appears, it
> breaks
> > > the XML because of the ampersand in the URL:
> >
> > > 
> > >> http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=164577";
> > >> rel="nofollow">Google
> > >> 
> >
> > > If the ampersand is fixed, I'm guessing things will be happy again.
> >
> > > I hope I'm sending this to the right place.  Not sure where else to
> send
> > > it.
> >
> > > Thanks!
> >
> > > -Brandon
> >
> > > --
> > > Brandon Stone
> > >http://brandonstone.com
> > >http://twitter.com/LBStone
>

[twitter-dev] Re: Malformed XML in some Atom feeds...

2010-05-07 Thread Claudia A. V. Callegari

Hello!

Sorry for my English.
I'm also having the same problem, has agumar forecast for this
problem?

Thanks
Claudia Antonini  Vitiello  Callegari
São Paulo -  Brasil

On 4 maio, 12:33, Taylor Singletary 
wrote:
> Hi Brandon,
>
> Thanks for the bug report. We'll work on getting this fixed quickly.
>
> Thanks!
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Tue, May 4, 2010 at 7:54 AM, Brandon Stone  wrote:
> > One very popular Twitter list is Scoble's Tech News Brands list:
>
> >http://api.twitter.com/1/Scobleizer/lists/tech-news-brands/statuses.a...
>
> > I've got a program that's been watching this feed for a while now.  Just
> > yesterday I started getting some XML parsing errors.  I can create a hack to
> > make this work again on my end, but it's definitely best for Twitter to make
> > sure their XML is well-formed.
>
> > Here's what feed validator says:
>
> >http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.c...
>
> >> Sorry
>
> >> This feed does not validate.
>
> >> line 
> >> 482,
> >> column 73: XML parsing error: :482:73: not well-formed (invalid
> >> token) [help ]
>
> >>  >> href="http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=16...
>
> > It looks like whenever a  of "Google" appears, it breaks
> > the XML because of the ampersand in the URL:
>
> > 
> >> http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=164577";
> >> rel="nofollow">Google
> >> 
>
> > If the ampersand is fixed, I'm guessing things will be happy again.
>
> > I hope I'm sending this to the right place.  Not sure where else to send
> > it.
>
> > Thanks!
>
> > -Brandon
>
> > --
> > Brandon Stone
> >http://brandonstone.com
> >http://twitter.com/LBStone

[twitter-dev] Re: API call to turn on location-based tweets?

2010-05-07 Thread Stephen Rife

This is great.  Would be really nice if this displayed in the user's
account language setting.

- Steve
@melobubu

On 4月30日, 午前6:23, Abraham Williams <4bra...@gmail.com> wrote:
> https://twitter.com/account/geo
>
> On Thu, Apr 29, 2010 at 14:17, Ken  wrote:
>
> > > there
> > > is also a mobile optimized page with just that checkbox on twitter.comthat
> > > you could use too.
>
> > could be useful.. what's the URL?
>
> > thanks
>
> > Ken
>
> --
> Abraham Williams | Developer for hire |http://abrah.am
> @abraham |http://projects.abrah.am|http://blog.abrah.am
> This email is: [ ] shareable [x] ask first [ ] private.

[twitter-dev] Re: Tweet Box >> @Anywhere

2010-05-07 Thread Hesham

I am using the tweeter box on my blog!
I wrote two blog posts about it, plz follow it:

http://www.famousbloggers.net/tweet-box-twitter-anywhere.html
http://www.famousbloggers.net/twitter-anywhere-thesis.html

On Apr 15, 9:09 am, amrnt  wrote:
> Any body tries to post a status from Tweet Box and it posted
> successfully to his Twitter?

[twitter-dev] nested user object bug in statuses/friends

2010-05-07 Thread Ken

I noticed nested user tag issue at statuses/friends API.

It seems to be same as following another API's report:
 
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/560a544d6703f2b9

Thanks
Ken

Re: [twitter-dev] Re: OAuth support and reformatted DMs live on user streams

2010-05-07 Thread John Kalucki

Other than orthogonality, I don't understand the use case for hydrated
deletions. They're useful to delete existing data. What would you
display, and why?

Note that every byte that we send costs something in CPU, bandwidth
and increased latency.



On Fri, May 7, 2010 at 2:38 AM, lqd  wrote:
> #1 OAuth.
> This took a long time to debug but I think I found the problem. It
> looks like you guys expect the OAuth Authorization header params to be
> separated by a comma (which is OK), AND at least one space (which is
> not OK). Am I right ? (The spaces after the comma are optional if I
> remember the OAuth spec correctly.)
>
> #3 The use cases for hydrated delete events would be exactly the same
> on your part as the ones for hydrating social events :) (which I
> believe is to make the stream more useful by itself and not *having*
> to use the REST API to understand the stream events). I keep user
> objects ATM, or ask the REST API for statuses or user ids I didn't
> encounter before, there's no question that it's doable, I was just
> wondering whether the same thinking would be applied consistently to
> all events, the delete ones right now and any new ones created in the
> future ?
>
> Thanks Mark and John
> Rémy
> @ldq
>
> On May 6, 6:46 pm, Mark McBride  wrote:
>> Did you adjust the timestamp in that tool?  The hosebird
>> implementation tolerates at most a 5 minute clock skew... in other
>> words if it receives a timestamp that is 5 minutes older (or newer)
>> than the current time, it rejects the request.
>>
>>    ---Mark
>>
>> http://twitter.com/mccv
>>
>>
>>
>> On Thu, May 6, 2010 at 6:39 AM, lqd  wrote:
>> > Hey guys, a couple questions/remarks on the new user streams features:
>>
>> > 1) OAuth
>> > I have no problem using the stream with BasicAuth, nor using the REST
>> > API with OAuth. However I'm always getting 401s with OAuth on the
>> > stream, even though Zac's fork or earlybird works flawlessly.
>> > Just to try and locate the problem I tried signing the request with
>> > the official noob tool 
>> > athttp://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
>> > and sending the header with curl (with fiddling with spaces, tabs &
>> > newline just in case, and even the realm value - just because
>> > earlybird's impl doesn't send it), and I still can't login. While my
>> > own code signing matches the parameters this tool outputs (and works
>> > on api.twitter.com) it doesn't match what the ruby gem generates, even
>> > when using the same timestamp and nonce, so I was suspecting some
>> > difference in the base string. (I don't know Ruby, or how to get the
>> > Base String there, but there's apparently a signature_base_string
>> > method, and it did seem to have all the oauth params in the query
>> > string)
>>
>> > 2) +1 on the user burping at the beginning :)
>>
>> > 3) Are the deletion notices going to be hydrated too ? ATM it's a
>> > little raw. While it's understandable for the status not to be there
>> > since it's just been deleted, maybe the full JSON user could be there
>> > instead of just its id ?
>>
>> > Thanks
>> > Rémy
>> > @lqd
>>
>> > On May 6, 12:41 am, Mark McBride  wrote:
>> >> Ok.  The query string OAuth variant should be working now.  We only
>> >> support HMAC-SHA1 (just like twitter.com does) for signature methods,
>> >> and don't have plans to support other schemes.
>>
>> >>    ---Mark
>>
>> >>http://twitter.com/mccv
>>
>> >> On Wed, May 5, 2010 at 3:21 PM, John Kalucki  wrote:
>> >> > We should probably just burp the whole user object out at connection 
>> >> > start.
>>
>> >> > On Wed, May 5, 2010 at 3:12 PM, Zac Bowling  wrote:
>> >> >> Hydrated message support in earlybird!
>>
>> >> >>http://github.com/zbowling/earlybird/
>>
>> >> >> OAuth in query string doesn't work  and only HMAC-SHA1 signature 
>> >> >> (unless you
>> >> >> only allow plaintext over SSL) but its fine.
>>
>> >> >> One feature request would be an inital event with the users 
>> >> >> credentials just
>> >> >> like how the user's social graph comes down initially. Right now I 
>> >> >> don't
>> >> >> know the user's screen_name unless I also hit api.twitter.com or he 
>> >> >> tells me
>> >> >> on the command line. With that I could drop the dependency on the 
>> >> >> twitter
>> >> >> gem.
>>
>> >> >> Zac Bowling
>> >> >> @zbowling
>>
>> >> >> On Wed, May 5, 2010 at 10:54 AM, Mark McBride  
>> >> >> wrote:
>>
>> >> >>> It should support both.  Can you send me a direct email with a URL
>> >> >>> that you tried?
>>
>> >> >>>   ---Mark
>>
>> >> >>>http://twitter.com/mccv
>>
>> >> >>> On Wed, May 5, 2010 at 10:38 AM, Zac Bowling  
>> >> >>> wrote:
>> >> >>> > My fork of earlybird works:
>>
>> >> >>> >http://github.com/zbowling/earlybird/
>>
>> >> >>> > Fixing it to support hydrated objects.
>>
>> >> >>> > One thing is that it doesn't appear to support query string passed 
>> >> >>> > OAuth
>> >> >>> > params but if I pass it as authentication headers it works.
>>
>> >> >>> > Zac Bowl

[twitter-dev] Re: OAuth support and reformatted DMs live on user streams

2010-05-07 Thread lqd

#1 OAuth.
This took a long time to debug but I think I found the problem. It
looks like you guys expect the OAuth Authorization header params to be
separated by a comma (which is OK), AND at least one space (which is
not OK). Am I right ? (The spaces after the comma are optional if I
remember the OAuth spec correctly.)

#3 The use cases for hydrated delete events would be exactly the same
on your part as the ones for hydrating social events :) (which I
believe is to make the stream more useful by itself and not *having*
to use the REST API to understand the stream events). I keep user
objects ATM, or ask the REST API for statuses or user ids I didn't
encounter before, there's no question that it's doable, I was just
wondering whether the same thinking would be applied consistently to
all events, the delete ones right now and any new ones created in the
future ?

Thanks Mark and John
Rémy
@ldq

On May 6, 6:46 pm, Mark McBride  wrote:
> Did you adjust the timestamp in that tool?  The hosebird
> implementation tolerates at most a 5 minute clock skew... in other
> words if it receives a timestamp that is 5 minutes older (or newer)
> than the current time, it rejects the request.
>
>    ---Mark
>
> http://twitter.com/mccv
>
>
>
> On Thu, May 6, 2010 at 6:39 AM, lqd  wrote:
> > Hey guys, a couple questions/remarks on the new user streams features:
>
> > 1) OAuth
> > I have no problem using the stream with BasicAuth, nor using the REST
> > API with OAuth. However I'm always getting 401s with OAuth on the
> > stream, even though Zac's fork or earlybird works flawlessly.
> > Just to try and locate the problem I tried signing the request with
> > the official noob tool 
> > athttp://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
> > and sending the header with curl (with fiddling with spaces, tabs &
> > newline just in case, and even the realm value - just because
> > earlybird's impl doesn't send it), and I still can't login. While my
> > own code signing matches the parameters this tool outputs (and works
> > on api.twitter.com) it doesn't match what the ruby gem generates, even
> > when using the same timestamp and nonce, so I was suspecting some
> > difference in the base string. (I don't know Ruby, or how to get the
> > Base String there, but there's apparently a signature_base_string
> > method, and it did seem to have all the oauth params in the query
> > string)
>
> > 2) +1 on the user burping at the beginning :)
>
> > 3) Are the deletion notices going to be hydrated too ? ATM it's a
> > little raw. While it's understandable for the status not to be there
> > since it's just been deleted, maybe the full JSON user could be there
> > instead of just its id ?
>
> > Thanks
> > Rémy
> > @lqd
>
> > On May 6, 12:41 am, Mark McBride  wrote:
> >> Ok.  The query string OAuth variant should be working now.  We only
> >> support HMAC-SHA1 (just like twitter.com does) for signature methods,
> >> and don't have plans to support other schemes.
>
> >>    ---Mark
>
> >>http://twitter.com/mccv
>
> >> On Wed, May 5, 2010 at 3:21 PM, John Kalucki  wrote:
> >> > We should probably just burp the whole user object out at connection 
> >> > start.
>
> >> > On Wed, May 5, 2010 at 3:12 PM, Zac Bowling  wrote:
> >> >> Hydrated message support in earlybird!
>
> >> >>http://github.com/zbowling/earlybird/
>
> >> >> OAuth in query string doesn't work  and only HMAC-SHA1 signature 
> >> >> (unless you
> >> >> only allow plaintext over SSL) but its fine.
>
> >> >> One feature request would be an inital event with the users credentials 
> >> >> just
> >> >> like how the user's social graph comes down initially. Right now I don't
> >> >> know the user's screen_name unless I also hit api.twitter.com or he 
> >> >> tells me
> >> >> on the command line. With that I could drop the dependency on the 
> >> >> twitter
> >> >> gem.
>
> >> >> Zac Bowling
> >> >> @zbowling
>
> >> >> On Wed, May 5, 2010 at 10:54 AM, Mark McBride  
> >> >> wrote:
>
> >> >>> It should support both.  Can you send me a direct email with a URL
> >> >>> that you tried?
>
> >> >>>   ---Mark
>
> >> >>>http://twitter.com/mccv
>
> >> >>> On Wed, May 5, 2010 at 10:38 AM, Zac Bowling  
> >> >>> wrote:
> >> >>> > My fork of earlybird works:
>
> >> >>> >http://github.com/zbowling/earlybird/
>
> >> >>> > Fixing it to support hydrated objects.
>
> >> >>> > One thing is that it doesn't appear to support query string passed 
> >> >>> > OAuth
> >> >>> > params but if I pass it as authentication headers it works.
>
> >> >>> > Zac Bowling
>
> >> >>> > On Wed, May 5, 2010 at 10:31 AM, Mark McBride 
> >> >>> > wrote:
>
> >> >>> >> OAuth support on betastream is live now.  This is different OAuth
> >> >>> >> implementation than we use on twitter.com, so if you find any rough
> >> >>> >> edges please let us know quick like.
>
> >> >>> >> The changes to make direct messages more distinguishable from tweets
> >> >>> >> has also been pushed.  This will probably require some chan

Re: [twitter-dev] oAuth

[twitter-dev] Re: Slow response to twitter updates for a third party app

[twitter-dev] oAuth

Re: [twitter-dev] Re: TCL & oAuth

Re: [twitter-dev] Why have I recieved a HTTP 601 Response.

Re: [twitter-dev] Re: User tag inside users/show

[twitter-dev] Re: User tag inside users/show

[twitter-dev] Re: User tag inside users/show

[twitter-dev] Why have I recieved a HTTP 601 Response.

[twitter-dev] Re: xhr2 and cross domain Ajax requests

Re: [twitter-dev] Re: User tag inside users/show

[twitter-dev] Re: OAuth support and reformatted DMs live on user streams

Re: [twitter-dev] Re: OAuth support and reformatted DMs live on user streams

Re: [twitter-dev] Re: User tag inside users/show

[twitter-dev] Re: User tag inside users/show

Re: [twitter-dev] Re: TCL & oAuth

[twitter-dev] Re: User tag inside users/show

Re: [twitter-dev] Re: TCL & oAuth

Re: [twitter-dev] Re: TCL & oAuth

Re: [twitter-dev] nested user object bug in statuses/friends

Re: [twitter-dev] Re: Malformed XML in some Atom feeds...

[twitter-dev] Re: Malformed XML in some Atom feeds...

[twitter-dev] Re: API call to turn on location-based tweets?

[twitter-dev] Re: Tweet Box >> @Anywhere

[twitter-dev] nested user object bug in statuses/friends

Re: [twitter-dev] Re: OAuth support and reformatted DMs live on user streams

[twitter-dev] Re: OAuth support and reformatted DMs live on user streams

27 matches

Site Navigation

Mail list logo

Footer information