Didn't previous conversations on similar topics leads to the concept
that every client needs its own key? And if so, how do you aggregate
stats on that?

If you give out a client with a single key, and you give away that
key, who is then responsible for the behavior of the application? Who
does Twitter contact when some douchenozzle starts sending spam or
injects a worm using your key? And how do you, the developer of the
app, then fix those problems, if everyone has your key, without
re-issuing a new key and invalidating all previous installs?

You should proxy your OAuth requests through a web app. Problems solved.

∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera

On Wed, Mar 10, 2010 at 12:53 AM, SM <sanja...@gmail.com> wrote:
> It's a desktop app, not a web app. Is there an easy way to do this for
> desktop apps? I would think Twitter could provide usage stats for
> OAuth apps.
> On Mar 9, 5:24 pm, Michael Steuer <mste...@gmail.com> wrote:
>> Wouldn't you yourself know best how to calculate how many people are
>> actively using your app?
>> On 3/9/10 5:14 PM, "SM" <sanja...@gmail.com> wrote:
>> > On the application detail page there is a stat that shows how many
>> > users your app has.
>> > How is this stat calculated? Is it the number of authorized tokens or
>> > does it reflect some rolling count of accesses using an authorized
>> > token? Or some other calculation?
>> > If someone uses my app once and then forgets about it, will that
>> > person continue to be counted as a user since tokens never expire?
>> > I'm hoping it is a stat that actually tracks how many people are
>> > actively using your app.
>> > Thanks.

Reply via email to