From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: OAuth2 implementation in Elisp Date: Sun, 25 Sep 2011 06:25:16 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87d3eo984j.fsf@lifelogs.com> References: <87sjnojl7j.fsf@keller.adm.naquadah.org> <4E7BAFA4.8090800@dogan.se> <4E7BAFE2.2090102@dogan.se> <87k490jkaw.fsf@keller.adm.naquadah.org> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1316949946 8889 80.91.229.12 (25 Sep 2011 11:25:46 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 25 Sep 2011 11:25:46 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 25 13:25:43 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1R7mq4-00017V-Vr for ged-emacs-devel@m.gmane.org; Sun, 25 Sep 2011 13:25:41 +0200 Original-Received: from localhost ([::1]:47292 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R7mq4-0004UR-Im for ged-emacs-devel@m.gmane.org; Sun, 25 Sep 2011 07:25:40 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:46535) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R7mq1-0004UB-P5 for emacs-devel@gnu.org; Sun, 25 Sep 2011 07:25:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R7mq0-0001AC-BY for emacs-devel@gnu.org; Sun, 25 Sep 2011 07:25:37 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:56514) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R7mq0-0001A3-0P for emacs-devel@gnu.org; Sun, 25 Sep 2011 07:25:36 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R7mpy-00014g-Nw for emacs-devel@gnu.org; Sun, 25 Sep 2011 13:25:34 +0200 Original-Received: from 38.98.147.133 ([38.98.147.133]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 25 Sep 2011 13:25:34 +0200 Original-Received: from tzz by 38.98.147.133 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 25 Sep 2011 13:25:34 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 26 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.133 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:16V9cYnc8BUT2c6xGJozODdMTBc= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:144266 Archived-At: On Fri, 23 Sep 2011 00:15:19 +0200 Julien Danjou wrote: JD> On Fri, Sep 23 2011, Deniz Dogan wrote: >> Uh, where is the code by the way? JD> Well, I did not published it yet, since I don't want to set up a Git JD> repository if it's OK to merge this into the trunk. And I usually don't JD> like sending code by e-mail, since there's always a chance someone will JD> grab old code from this to-be-outdated mail in the future. JD> But well, here it is. :) Could you format it to wrap the long lines? Some usage examples would be nice. I don't think you are encoding URL parameters so your URLs are not safely constructed. I think the url libraries have functions for that; you could also submit a POST (if OAuth2 supports it, I don't know the spec) so you don't have to encode things at all. Can `oauth2-request-authorization' be automated so the user doesn't have to enter a string they see on the screen? That seems painful. Thanks Ted