Just for reference and logging.. I pass in application =
"SeesmicAIR / Critter" for every call I make to seesmic.. for those of
you that are developing against the api.. I would suggest something
similar just in case there ever is some problem.. it might be more
easily identified... if it is one of us 3rd parties...
> Just for reference and logging.. I pass in application =
> "SeesmicAIR / Critter" for every call I make to seesmic.. for those of
> you that are developing against the api.. I would suggest something
> similar just in case there ever is some problem.. it might be more
> easily identified... if it is one of us 3rd parties...
yea, that hasn't come up at all yet in any internal conversation but it can't hurt to have a custom string in the data stream so we know where to send the attack dogs later ;)
On Jan 24, 2008 2:01 PM, Critter <k0rnel...@gmail.com> wrote:
> Just for reference and logging.. I pass in application = > "SeesmicAIR / Critter" for every call I make to seesmic.. for those of > you that are developing against the api.. I would suggest something > similar just in case there ever is some problem.. it might be more > easily identified... if it is one of us 3rd parties...
It would be good to know what they plan. Is the Developer Key system related to OpenAuth as I have heard Johan mention OpenAuth at one point on twitter.
T
On 24/01/2008, Critter <k0rnel...@gmail.com> wrote:
> mind you... I think Johann was talking about eventually doing a > developer key system... *shrug*
> On Jan 24, 2:01 pm, Critter <k0rnel...@gmail.com> wrote: > > Just for reference and logging.. I pass in application = > > "SeesmicAIR / Critter" for every call I make to seesmic.. for those of > > you that are developing against the api.. I would suggest something > > similar just in case there ever is some problem.. it might be more > > easily identified... if it is one of us 3rd parties...
OAuth and OpenID are definetly on the table - it's just a matter of when.
Hmm, it would make complete sense if I go find out what kind of key is required and just spec that out now. Then we could be using that instead of something now that has to be changed later.
Let me go dig up some specs. :)
On Jan 24, 2008 2:11 PM, Geoff Tinnion <tinn...@gmail.com> wrote:
> It would be good to know what they plan. Is the Developer Key system related > to OpenAuth as I have heard Johan mention OpenAuth at one point on twitter.
> T
> On 24/01/2008, Critter <k0rnel...@gmail.com> wrote:
> > mind you... I think Johann was talking about eventually doing a > > developer key system... *shrug*
> > On Jan 24, 2:01 pm, Critter <k0rnel...@gmail.com> wrote: > > > Just for reference and logging.. I pass in application = > > > "SeesmicAIR / Critter" for every call I make to seesmic.. for those of > > > you that are developing against the api.. I would suggest something > > > similar just in case there ever is some problem.. it might be more > > > easily identified... if it is one of us 3rd parties...
> OAuth and OpenID are definetly on the table - it's just a matter of > when.
> Hmm, it would make complete sense if I go find out what kind of key is > required and just spec that out now. Then we could be using that > instead of something now that has to be changed later.
> Let me go dig up some specs. :)
> On Jan 24, 2008 2:11 PM, Geoff Tinnion <tinn...@gmail.com> wrote: >> Hi.
>> It would be good to know what they plan. Is the Developer Key >> system related >> to OpenAuth as I have heard Johan mention OpenAuth at one point on >> twitter.
>> T
>> On 24/01/2008, Critter <k0rnel...@gmail.com> wrote:
>>> mind you... I think Johann was talking about eventually doing a >>> developer key system... *shrug*
>>> On Jan 24, 2:01 pm, Critter <k0rnel...@gmail.com> wrote: >>>> Just for reference and logging.. I pass in application = >>>> "SeesmicAIR / Critter" for every call I make to seesmic.. for >>>> those of >>>> you that are developing against the api.. I would suggest something >>>> similar just in case there ever is some problem.. it might be more >>>> easily identified... if it is one of us 3rd parties...
Yup, I've been using a custom User Agent name for all my API calls.
Easy to do when using cUrl.
Also been using the 'source' parameter in some recent stuff.
On 24/01/2008, Critter <k0rnel...@gmail.com> wrote:
> Just for reference and logging.. I pass in application = > "SeesmicAIR / Critter" for every call I make to seesmic.. for those of > you that are developing against the api.. I would suggest something > similar just in case there ever is some problem.. it might be more > easily identified... if it is one of us 3rd parties...
> Yup,
> I've been using a custom User Agent name for all my API calls.
> Easy to do when using cUrl.
> Also been using the 'source' parameter in some recent stuff.
> On 24/01/2008, Critter <k0rnel...@gmail.com> wrote:
> > Just for reference and logging.. I pass in application =
> > "SeesmicAIR / Critter" for every call I make to seesmic.. for those of
> > you that are developing against the api.. I would suggest something
> > similar just in case there ever is some problem.. it might be more
> > easily identified... if it is one of us 3rd parties...
