I don’t think so. See Vaniver’s comment which describes what the site is doing. I don’t know the process, but maybe you can submit a DB request to the trike apps team for this data.
The following is what I had in mind for that section:
maybe you can submit a DB request to the trike apps team for this data.
There is an API but I think it doesn’t have the ability to do everything that we’d like it to. See this issue as an example of a missing feature.
But if you have the ability, building that feature and submitting it as a pull request is better than doing it the long way (since it also helps everyone else who wants to do that sort of thing in the future).
A feature that allows anyone on the ’net to bang on your backend database is not something to be taken lightly :-)
I think LW first needs a coherent API spec, then a framework (including thing like auth tokens, rate limiters, etc.), and only then specific abilities to e.g. ask for all comments of a particular user.
You are probably right. I would assume that I can also get the post information from this: http://lesswrong.com/r/all/recentposts/ . A graph with this much data probably wouldn’t be useful as it would be too busy. I will look into writing something else to get this data into a usable format.
Edit: Your link only has the main comments, not the discussion ones. I’m not sure what to get all the comment information from.
I don’t think so. See Vaniver’s comment which describes what the site is doing. I don’t know the process, but maybe you can submit a DB request to the trike apps team for this data.
script should be able to be run on http://lesswrong.com/comments/ without much modification...
Yeah, I recommend against scraping LW that way instead of making a DB request / building a page that makes that DB request.
Can one? In general, is there an available (and working) API to LW?
The following is what I had in mind for that section:
There is an API but I think it doesn’t have the ability to do everything that we’d like it to. See this issue as an example of a missing feature.
But if you have the ability, building that feature and submitting it as a pull request is better than doing it the long way (since it also helps everyone else who wants to do that sort of thing in the future).
A feature that allows anyone on the ’net to bang on your backend database is not something to be taken lightly :-)
I think LW first needs a coherent API spec, then a framework (including thing like auth tokens, rate limiters, etc.), and only then specific abilities to e.g. ask for all comments of a particular user.
You are probably right. I would assume that I can also get the post information from this: http://lesswrong.com/r/all/recentposts/ . A graph with this much data probably wouldn’t be useful as it would be too busy. I will look into writing something else to get this data into a usable format.
Edit: Your link only has the main comments, not the discussion ones. I’m not sure what to get all the comment information from.
maybe 3 months worth; for the past 3 years? 12 graphs in total; showing the trend...?
I figured that with the zoom it would be able to be use-able. but separate graphs work too.