Libraries and examples. Understanding authentication isn't a prerequisite for building valuable apps. If a developer wants to understand OAuth then there is plenty of documentation out there for that. I think the biggest barrier is the complexity of beginning to understand the OAuth dance.
If there was an "interface" of examples that libraries could implement then it would go a long way. Right now every library has it's own examples and it makes it difficult for users get up and running with something as basic as authentication. I'm thinking Hello world type examples that each library can provide in a consistent manner. On Apr 7, 3:30 pm, Raffi Krikorian <ra...@twitter.com> wrote: > i would love to know how we can make oauth simpler for people. should we > provide better documentation? examples? libraries? > > > > On Wed, Apr 7, 2010 at 3:07 PM, Lil Peck <lilp...@gmail.com> wrote: > > On Wed, Apr 7, 2010 at 1:53 PM, Mike Champion <mike.champ...@gmail.com> > > wrote: > > > > I'd be curious to hear what folks think. > > > For me, the appeal of Twitter is its brevity and its simplicity for > > integration with one's website. > > > I worry that once basic authentication is discontinued, that I will > > have to stop using Twitter in my web based apps. Seems to me that > > oauth is needlessly too complicated and bloated for many Twitter uses. > > > I like it that Twitter has been a very simple service, and that > > because of the limit of its scope, there are opportunities for > > indepedent developers to create extensions for it. > > > I am not at all enchanted by Facebook and whatever I do with Facebook > > is out of sheer necessity. > > > -- > > To unsubscribe, reply using "remove me" as the subject. > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi
