Do the math, a thread with 50 comments (not rare) suddenly pulls an extra megabyte in order to retrieve several hundred bytes of info per pageview.
Anyway, it really isn't my call to make, I just figured I should warn you, in case you had not thought through the consequences of this becoming popular.
edit: unless I'm misreading your code it even does requests for users that are listed multiple times on a single page, you could easily save there by caching the results of your queries.
Or memoize the fetch function. Greasemonkey has support [1] for persistent data, it should't be hard to cache the info to only fetch the counts every n comments or x days.
Comments
Do the math, a thread with 50 comments (not rare) suddenly pulls an extra megabyte in order to retrieve several hundred bytes of info per pageview.
Anyway, it really isn't my call to make, I just figured I should warn you, in case you had not thought through the consequences of this becoming popular.
edit: unless I'm misreading your code it even does requests for users that are listed multiple times on a single page, you could easily save there by caching the results of your queries.
Maybe he can modify the script so that the score is shown only on demand.
Or memoize the fetch function. Greasemonkey has support [1] for persistent data, it should't be hard to cache the info to only fetch the counts every n comments or x days.
[1] http://diveintogreasemonkey.org/advanced/gm_getvalue.html
That sounds like a better solution. The way it is now it is very heavy.
The very best way would be to ask for stuff like this to be configurable for those that want it but HN 'feature' requests are not usually honoured.