From fons.haffmans at gmail.com Sun Nov 14 18:09:37 2010 From: fons.haffmans at gmail.com (fons haffmans) Date: Sun, 14 Nov 2010 13:09:37 -0500 Subject: [cl-twitter-devel] cl-twitter update Message-ID: I'm updating cl-twitter here : http://fons at github.com/fons/cl-twitter.git. You can follow my progress here : http://cl-twitter.blogspot.com/ I've made the following updates so far : Authentication Updaterepl twitter client I've setup a twitter app called cl-twit-repl. The consumer key and consumer secret are stored in twitter.lisp. Initial setup To authenticate from the repl run (cl-twitter:repl-authenticate-user). You should see output like this : please authorize : # enter PIN : Log into your twitter account and copy the url into the browser bar. After agreeing to allow cl-twit-repl access, twitter will give you a pin. Enter the pin at the command prompt, and hit return. If everything goes well, you should be logged in. Your access tokens are stored in clear text in a file called access.ht, in the repo's directory. This is obviously not the most secure solution. The *access-file* variable controls the name and location of that file. Subsequent access Run (cl-twitter:get-authenticated-user ). This will read the access credentials from acces.ht. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sky at viridian-project.de Sun Nov 14 18:32:25 2010 From: sky at viridian-project.de (Leslie P. Polzer) Date: Sun, 14 Nov 2010 19:32:25 +0100 (CET) Subject: [cl-twitter-devel] cl-twitter update In-Reply-To: References: Message-ID: <3191bf80a7a66722b7f7e8854d8d72f5.squirrel@mail.stardawn.org> fons haffmans wrote: > I'm updating cl-twitter here : http://fons at github.com/fons/cl-twitter.git. > > You can follow my progress here : http://cl-twitter.blogspot.com/ > > I've made the following updates so far : > Authentication Updaterepl twitter client > > I've setup a twitter app called cl-twit-repl. The consumer key and consumer > secret are stored in twitter.lisp. > Initial setup > > To authenticate from the repl run (cl-twitter:repl-authenticate-user). You > should see output like this : Glad you've made it with the cl-oauth integration! Leslie From fons.haffmans at gmail.com Tue Nov 16 03:21:25 2010 From: fons.haffmans at gmail.com (fons haffmans) Date: Mon, 15 Nov 2010 22:21:25 -0500 Subject: [cl-twitter-devel] an update on cl-twitter Message-ID: <08EE0CB4-ADF5-4344-BFC3-9A4B456F5651@gmail.com> You can follow my progress here : http://cl-twitter.blogspot.com/. I'm currently upgrading cl-twitter to conform to the current twitter api. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fons.haffmans at gmail.com Tue Nov 30 04:10:54 2010 From: fons.haffmans at gmail.com (fons haffmans) Date: Mon, 29 Nov 2010 23:10:54 -0500 Subject: [cl-twitter-devel] walking the social graph with cl-twitter Message-ID: <832BB05E-96DE-42E7-BDFD-05A853E86986@gmail.com> a new blog post : http://cl-twitter.blogspot.com/2010/11/querying-social-graph-with-cl-twitter.html -------------- next part -------------- An HTML attachment was scrubbed... URL: