Hi,

It depends on how you're accessing and displaying the tweets... are you
trying to show your home timeline (the tweets you typically see on
twitter.com's home page while logged in), or are you trying to show your own
tweets, or are you trying to show someone else's tweets?

Showing your own home timeline requires authentication, as there must be a
perspective of who's home timeline is being viewed. Further, it's not
appropriate to post your own home timeline where others can see it, as you
may be following protected accounts and putting those user's privacy at
risk.

Fetching an unprotected user's timeline (their tweets, your tweets) does not
require authentication.

How are you currently integrating the streams into your site? A server-side
fetch, a client-side fetch? A widget?

Taylor


On Thu, Sep 9, 2010 at 6:53 PM, contact.edmur...@gmail.com <
contact.edmur...@gmail.com> wrote:

> Hi there-  With the outdated Basic Authentication method, I was able
> to display my freinds tweets on my web page without a problem.  Now
> with oAuth, unless already logged in, I have to click the login button
> with Twitter each time to display that content.  Multiple that for
> each person that visits my web page.  Headach City!
>
> Is there something I am missing?  Can the login be done once and
> always display said content when someone visits my site?  Thanks, any
> help is appreciated!
>
> --
> 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?hl=en
>

-- 
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?hl=en

Reply via email to