Hah @ "can I recommend the following book "How to win friends and
influence people".. It's a good read...
Also Keiya, Twitter is a Web App, and the majority of people jumping
on the trail are WEB DEVELOPERS. They don't want to use C++ and GTK++.
I can't even imagine having to waste the time coding a two hour OAuth
app [Dave..] in C++ and having to use GTK+ as my UI. ./make ./make
install blah -
On Oct 25, 2010, at 4:00 PM, Dave-twiends wrote:
As I fellow developer I'll say I fully support the drive to OAuth.
It's a lot more secure and although it might mean that you actually
have to write a few lines of code it will help stamp out a lot issues
with straight usernames and passwords..
OAuth took me total of about 2 hours to implement, what's the big
deal...?
Good luck Keiya, can I recommend the following book "How to win
friends and influence people".. It's a good read...
On Oct 25, 8:28 pm, Keiya Bachhuber <keiyak...@gmail.com> wrote:
Is the next version of twitter going to be written in C++ and use
GTK+
for rendering? Because that's what you're asking desktop developers
to
do by forcing OAuth. I have to include a web server in my app to work
with twitter? What the hell! It's probably simpler just to pretend to
be Chrome or Firefox. Seriously. Working through the mess that is
HTML
(any HTML, not just yours) is easier than getting the nice clean
feeds.
Good job. You made me hate you.
Keiya.
--
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
