[twitter-dev] Re: Automated OAuth
The server enters each username and password, so is the current way to have me go get the initial token then afterward have the server use the token programmaticly? On Sep 4, 2:18 am, Matt Harris wrote: > Hey Cradash, > > Where do the username and password come from that you use? > > If they are entered by a user you can handle the OAuth flow at that > time. Once you have an OAuth user token and secret it does not expire > and will continue to work until either the user revokes access to the > application, or the applications keys are changed. This means that > when you have the user token and secret you store that instead of the > username and password, and use those details to make requests to the > API. > > There is more information about converting Basic to OAuth on our > developer resources site: > http://dev.twitter.com/pages/basic_to_oauth > > Hope that helps, > Matt > > > > On Thu, Sep 2, 2010 at 4:57 PM, Cradash wrote: > > Yes, but I have not found a way to have the server go out with the > > consumer Key/secret then get the id # programmaticly, that's what I > > was looking for. > > > On Sep 3, 9:44 am, Taylor Singletary > > wrote: > >> Each Twitter feed in this case is a "user". > > >> On Thursday, September 2, 2010, Cradash wrote: > >> > Unfortunately that is not an option for us as we have no 'users'. We > >> > have a server that gleans information then posts it into twitter > >> > feeds, allautomated. > > > -- > > 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 > > -- > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris -- 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-dev] Re: Automated OAuth
Yes, but I have not found a way to have the server go out with the consumer Key/secret then get the id # programmaticly, that's what I was looking for. On Sep 3, 9:44 am, Taylor Singletary wrote: > Each Twitter feed in this case is a "user". > > On Thursday, September 2, 2010, Cradash wrote: > > Unfortunately that is not an option for us as we have no 'users'. We > > have a server that gleans information then posts it into twitter > > feeds, all automated. -- 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-dev] Re: Automated OAuth
Unfortunately that is not an option for us as we have no 'users'. We have a server that gleans information then posts it into twitter feeds, all automated. On Sep 2, 11:30 pm, Tom van der Woerdt wrote: > Don't worry, you'll get your answer, and if not then you'll just have to > wait until my school is over (which is now). > > Anyway, to answer your question: Yes, you may like to use xAuth to > convert all username/password combinations to OAuth credentials. For new > users you should simply do the "OAuth Dance". You can then use these > credentials to make the requests to the API. > > Tom > > On 9/2/10 12:00 PM, Cradash wrote: > > > xAuth perhaps? > > > On Sep 2, 4:28 pm, Cradash wrote: > >> A Java example is unnecessary, more to the point I basically just need > >> to figure out how it can be done. > > >> On Sep 2, 3:40 pm, Cradash wrote: > > >>> We are a bit late to the game and haven't migrated to Oauth and now > >>> are scrambling to do so, we're running some Automated tweets (we get > >>> the info and put it in a Twitter stream). I haven't found any examples > >>> of how to authorize an automated stream and was wondering in anyone > >>> had any suggestions . It's written in Scala but all I would need is a > >>> Java example. -- 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-dev] Re: Automated OAuth
xAuth perhaps? On Sep 2, 4:28 pm, Cradash wrote: > A Java example is unnecessary, more to the point I basically just need > to figure out how it can be done. > > On Sep 2, 3:40 pm, Cradash wrote: > > > We are a bit late to the game and haven't migrated to Oauth and now > > are scrambling to do so, we're running some Automated tweets (we get > > the info and put it in a Twitter stream). I haven't found any examples > > of how to authorize an automated stream and was wondering in anyone > > had any suggestions . It's written in Scala but all I would need is a > > Java example. -- 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-dev] Re: Basic Auth
Ah, thanks for the links, we were caught a bit off guard with Oauth.
On Sep 2, 12:35 am, Marc Mims wrote:
> * Cradash [100901 06:40]:
>
> > We have been getting a {"errors":[{"code":53,"message":"Basic
> > authentication is not supported"}]} error on our feeds for the last 15
> > or so hours, our feeds tweet at most 5 times an hour but have become
> > inactive because of this error. We are using Jtwitter and have not had
> > an isssue with this untill half-a day ago.
>
> I've been seeing this message for suspended users. See my most recent
> post in this
> thread:http://groups.google.com/group/twitter-development-talk/browse_thread...
>
> Here's a shortened URL:http://is.gd/eONAH
>
> An unauthenticated call to users/show for that user may tell you what
> the real problem is.
>
> -Marc
--
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-dev] Re: Automated OAuth
A Java example is unnecessary, more to the point I basically just need to figure out how it can be done. On Sep 2, 3:40 pm, Cradash wrote: > We are a bit late to the game and haven't migrated to Oauth and now > are scrambling to do so, we're running some Automated tweets (we get > the info and put it in a Twitter stream). I haven't found any examples > of how to authorize an automated stream and was wondering in anyone > had any suggestions . It's written in Scala but all I would need is a > Java example. -- 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-dev] Automated OAuth
We are a bit late to the game and haven't migrated to Oauth and now are scrambling to do so, we're running some Automated tweets (we get the info and put it in a Twitter stream). I haven't found any examples of how to authorize an automated stream and was wondering in anyone had any suggestions . It's written in Scala but all I would need is a Java example. -- 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-dev] Basic Auth
We have been getting a {"errors":[{"code":53,"message":"Basic
authentication is not supported"}]} error on our feeds for the last 15
or so hours, our feeds tweet at most 5 times an hour but have become
inactive because of this error. We are using Jtwitter and have not had
an isssue with this untill half-a day ago.
--
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
