Cache the AP representation of objects/activities and rate limit the routes
- AP objects/activities (other than questions, but we can set a ttl for them) don't change after submission, so we can cache /notice, /objects and /activities routes, instead of having to get from get them from the database, render and encode to json every time.
- Rate limit the said routes to say 15 per minute per IP. I believe this thread can serve as an explanation to why this is necessary