Sorry guys but none of the above tips seem to be working...

Any other thoughts?

K.

On Nov 18, 11:17 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Second 
> tip:http://blog.abrah.am/2010/04/little-known-twitter-and-twitterapi.html
>
> Abraham
> -------------
> Abraham Williams | Hacker Advocate | abrah.am
> @abraham <https://twitter.com/abraham> | github.com/abraham | blog.abrah.am
> This email is: [ ] shareable [x] ask first [ ] private.
>
> On Thu, Nov 18, 2010 at 14:15, Tom van der Woerdt <i...@tvdw.eu> wrote:
>
> > Doesn't seem to work with "#newtwitter".
>
> > Tom
>
> > On 11/18/10 11:14 PM, @Red_Eyes wrote:
> > > You can do it, but you have to be logged in first which suggests that
> > > this would be a rate limited lookup.
>
> > > eg:http://twitter.com/?id=nnnnnnnn
>
> > > Regards
>
> > > On Nov 18, 6:00 pm, Kaspa <kacper.sul...@gmail.com> wrote:
> > >> The title says it all. Been looking for some time now.
> > >> (I know I can lookup the API for user detail and then use that. That's
> > >> not what I want, I want a way of directly putting the URL together)
>
> > >> Are URLs that directly use userIDs in some way prohibited?
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk
>
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to