Implement an archive database
When a user's "individual" timeline (as opposed to their "home" timeline) extends past a certain # of posts, move those posts from the "primary" db to the "archive" db
The archive db should be a database whose entire purpose is to contain (user) -> (post) data, where the (user) node just contains .... not the username since that can change, but probably the user_id (mentioned in #164)
It's not totally clear at this point how much other data would need to be moved into the archive database, ie, does it need to have
- (user) -> (user)
- (user) -[not creator]-> (post)
- etc
data? Probably. So I'm hoping that the only data transformations that need to happen between primary and archive is stripping (user) nodes of all relevant data and just leaving the user_id
Also consider making new posts -always- write to the archive database, as opposed to only writing them when they "expire" from the primary database