[twitter-dev] why not e-mail?
are there any plans to integrate status updates via e-mail directly into Twitter in the near future?
[twitter-dev] Re: Basic authentication
i haven't implemented OAuth at the moment but i'm at the verge doing it. although it is complete nonsense for my closed circuit use of posting status updates from website to twitter by fixed set of 2 to 3 users which never change. i wish that Twitter would offer an alternative for scenarios like this. i just wanted to clarify this... On 20 Mai, 19:16, Lil Peck lilp...@gmail.com wrote: On Tue, May 18, 2010 at 2:13 PM, Eric wetr...@gmail.com wrote: We are using the Streaming API and will only be using our own credentials. Our experience with OAuth in other services has not been positive, so like TJ says huge hassle for no gain. Although I was able to finally adapt to Oauth (thanks for Abraham and thanks to Scott), I agree that for folks who have web apps that do not require them to collect other people's logins, or to give their own to a third party, that it does seem a shame that provisions haven't been made to let those apps continue as is. Sorta looks like fixing what aint broke.
[twitter-dev] Re: Basic authentication
Twitter should offer a registration process for these cases. usually the posts aren't going to many accounts, so you could implement this registration with the Twitter user. the Twitter user could allow or disallow basic auth calls to his account. On May 21, 3:14 pm, Tammy Fennell tammykahnfenn...@gmail.com wrote: Hey, I'm pretty sure that Twitter isn't going to like that very much. The whole point is that everyone uses it not tries to get around it... I can't imagine supertweet will maintain it's own oauth for very long... On May 20, 12:02 pm, Jef Poskanzer jef.poskan...@gmail.com wrote: Thanks to @mrblog and SuperTweet I now have a backup plan in case I don't get OAuth implemented by the time Basic Auth goes away. It's a Twitter proxy - you use Basic Auth to talk to the proxy, and it uses OAuth to talk to Twitter. Easy peasy. http://www.supertweet.net/
[twitter-dev] Re: website and OAuth
i'm facing an equal scenario like the one above... i'm running a website where 2 to 3 users post status updates to that site which are posted then to twitteraccounts of the corresponding user. so basically i want to send updates to 2 or 3 twitter accounts via a php script. the users send their status updates via e-mails to the website and the script updates the website and posts to the twitter account of the user who has send in the status update. do i need to implement the whole OAuth process or can i use single tokens? thanks in advance! Claudio On May 11, 4:11 pm, glenn gillen gl...@rubypond.com wrote: Dan, I've taken a stab at answering your questions below: now from my understanding i need to change this over to start using OAuth is this correct? the system does it all back end so my bloggers dont write anything it auto does it for you, it posts to the one single twitter account. Yes you will need to switch over. now do i need to change to OAuth to get this to run when the date finally comes around, if so do i need to create an application? as it isnt really an application as such, this is the bit that confuses me a bit. You can switch over immediately, there's no need to wait until the cutoff date comes around. And yes you will need to create an application, it's just that this particular application will only. Details on some OAuth libraries (including PHP ones):http://apiwiki.twitter.com/OAuth-Examples Details on how to easily get a single token:http://dev.twitter.com/pages/oauth_single_token so i guess the question is do i need to change to oAuth and should i create an application if so would i need to create a callback URL as there wont be any callbacks as such would there as i would only be posting to my twitter feed. The single token approach can avoid the need for callbacks, so long as you don't need to tweet to other users accounts. -- Glenn Gillenhttp://glenngillen.com/
