many thanks - it happens, I guess.
On May 7, 7:38 am, Cameron Kaiser wrote:
> > You are kidding me? Is my message above reason to Ban me from this
> > group?
>
> I can only conclude this was a mistaken click on somebody's part, so I have
> temporarily removed the ban. We'll deal with it off list
> You are kidding me? Is my message above reason to Ban me from this
> group?
I can only conclude this was a mistaken click on somebody's part, so I have
temporarily removed the ban. We'll deal with it off list.
--
personal: http://www.cameronkaiser.com/ --
You are kidding me? Is my message above reason to Ban me from this
group?
On May 6, 4:41 pm, Mobasoft wrote:
> Glad that you are finally getting around to this.
> I posted it April
> 10thhttp://groups.google.com/group/twitter-development-talk/browse_thread...
>
> On May 6, 10:28 am, jmathai wr
Glad that you are finally getting around to this.
I posted it April 10th
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/960612fbcb8059de/5c2231ff33cff9e6?lnk=gst&q=revoke#5c2231ff33cff9e6
On May 6, 10:28 am, jmathai wrote:
> That would work. So would something a a
That would work. So would something a a bit simpler.
I am not sure I see the need for the username to be passed back.
Seems like that could easily be done by the site. Also unsure as to
why the special key is needed if it's always just returned as a
parameter.
Is this something that can be spe
Doug,
I think using the same "URL" would work, but it might be nice to have
an extra (or different) param added in order to determine the reason.
For example, if a user revokes access from the web and Twitter
notifies the "URL", the app may just be updating values in a DB, not
displaying anythin
I'm trying to decide if this could easily be part of [1]? Any objections for
these to be one in the same?
1. http://code.google.com/p/twitter-api/issues/detail?id=545
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On Tue, May 5, 2009 at 8:27 AM, jmathai wrote: