Comment statistics

[ciaan]

Title:
Comment statistics

Area:
entries/comments/circle

Summary:
I would like to be able to know statistics of who has commented in my journal.

Description:
There is an external app that can be used on LJ/DW to see who has commented in your journal and how many times they have commented. I would like the site to have a built-in feature similar to that. The two stats I would most like to be able to run are:

1. A list of everyone who has commented in my journal ever, and how many times each account has commented, ordered by number of comments.

2. A list of everyone I have added to my reading/access circles, and when the date was that each of them most recently commented on my journal.

Probably there are other stats other people would like to see.

Poll #2261 Comment statistics

Open to: Registered Users, detailed results viewable to: All, participants: 44

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
25 (56.8%)

Should be implemented with changes. (please comment)
2 (4.5%)

Shouldn't be implemented.
5 (11.4%)

(I have no opinion)
12 (27.3%)

(Other: please comment)
0 (0.0%)

Comments

[nacbrie]

Regarding (1), I can't see a problem with this - it's not got the same privacy issues as 'who has been viewing my journal', because you can essentially get the same data by manually counting the comments on your journal, it'd just take *ages*.

[ciaan]

Yes, that was my thought - it's all data you already have access to, just... put in one easy place for you.

[senmut]

This is one of those things that is just...bog-heavy coding for a tack on, a gee-whiz app that could later have adverse effects, or need updates as constant as security measure updates are done. So far as I know, the ability to do this on LJ was an external app someone coded, and I think that would be the smarter way here, rather than cluttering the code that is relatively clean and straight here.

[denise]

It actually wouldn't be that hard at all; the data is already available, as an automated feed even (it's how the external toys can do it for LJ). Processor power, yes, but if it's done asynchronously ("we'll run this now and message you in your inbox when the data's been crunched") it shouldn't be too much of a hit.

[senmut]

Alright. I just...real old school programmer from a long long time ago in an OS far away...and a cell phone saleperson more recently. I tend to think very minimalist due to this.

[ciaan]

Asynchronous and notification would be fine by me.

[yhlee]

Ditto this--it would be neat to play with if it can be done in a way that's not too painful to set up.

[kyrielle]

That would work nicely.

[tim]

Like someone else alluded to, I think there should be an API so this can be done elegantly as an external app (if there isn't one already), and it should be done as an external app.