Tracking number of users for an OAuth app

0 views
Skip to first unread message

SM

unread,
Mar 9, 2010, 8:14:51 PM3/9/10
to Twitter Development Talk
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.

Michael Steuer

unread,
Mar 9, 2010, 8:24:51 PM3/9/10
to twitter-deve...@googlegroups.com
Wouldn't you yourself know best how to calculate how many people are
actively using your app?

Marc Mims

unread,
Mar 10, 2010, 12:54:56 AM3/10/10
to twitter-deve...@googlegroups.com
* Michael Steuer <mst...@gmail.com> [100309 17:25]:

> Wouldn't you yourself know best how to calculate how many people are
> actively using your app?

Sure, if it's a web app. But if it's a desktop app, especially an open
source desktop app, the count twitter provides may be the only way to
know.

@semifor

SM

unread,
Mar 10, 2010, 12:53:55 AM3/10/10
to Twitter Development Talk
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?
>

Andrew Badera

unread,
Mar 10, 2010, 6:30:07 AM3/10/10
to twitter-deve...@googlegroups.com
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

Reply all
Reply to author
Forward
0 new messages