Post History

## I'd like to make charts of user and community stats

These could involve a large amount of data as the site grows, so should probably be links to a location that generates them once a day and/or caches them so they don't use the API every time someone views them.

### A user's reputation over time
This would need similar data to the [vote summary tab of the user page](https://meta.codidact.com/users/53890/vote-summary) - a summary of votes per day, and additionally how much reputation each vote is worth.

For charts that do not start at the date a user joined a community, it would also be useful to be able to request a user's reputation at a given date, rather than request all the data back to their joining date just to calculate their reputation at the start of the chart period.

### A user's raised and fixed bugs and feature requests over time
Would this be better as:
1. A simple request for a user's posts including date of posting and tags, followed by a request for the edit history to see when a "status-completed" tag was added?
1. A request for a summary per day of a user's bugs and feature requests (the API doing some of the work for you)?

Probably best to implement to simpler, more general approach first, then add more efficient, more specific approaches if and when needed (such as if it is decided to include certain charts as part of the Codidact user interface).

### A community's/tag's questions/answers per day
For a whole community, requesting all of the questions/answers just to then count how many were posted each day seems an unreasonable demand to place on the server. Should we have the ability to request posts that meet certain criteria, much like the filters in the current user interface?
- Post ids that were posted on a specified date?
- Post ids that have a specified tag?

Would it be useful to also have a similar request that only returns the count of how many matches, rather than the list of post ids?

### A community's unanswered questions over time
Similarly here, it is technically sufficient to be able to request all posts, and the number of answers per post, but that seems an unreasonable demand to place on the server. Here we might need slightly more fine grained filters than in the current user interface:
- Filter by min/max number of answers (max zero for this specific use case).
- Apply a date to the previous filter. Unlike in the user interface where we only need to know how many answers a question has now, here we would need to know how many answers a question had at different dates over a date range.