As a side effect of the change in GH-402, the API now includes over18 posts in listings even for users with a "no over18" cookie.
In some cases this is undesirable for API clients, since if the client is responsible for filtering, then there will be a variable number of posts per listing page.
As @bboe suggested in GH-402 comments, we can add an "obey_over18" parameter to re-enable server-side filtering of over18 posts when obey_over18=true. By default I suppose it would be obey_over18=false which means the client would get all unfiltered posts even if a "no over18" cookie is included in the HTTP request.
GH-407: "obey_over18" parameter to enable filtering of NSFW posts via…
GH-407: updated code not to use request.GET in model
Closed by pull request GH-452