I found one solution that stores the reposted data within a content
field on the model, but of course that's not a good approach. If I can
use only the object's ID, I think that would slim down the amount of
data being used. The old method is below, maybe you have a better
solution with AJAX.
has_many: reposts, class_name: "Post", foreign_key: "repost_id",
respond_to do |format|