51 upvotes, 1 direct replies (showing 1)
View submission: An Update Regarding Reddit’s API
Thank you, that does make me feel a lot better.
No. We’ve always had ratelimits in place for API usage, but we’ve not been the best about enforcement, clearing space for a premium tier (as mentioned) with higher limits, etc.
If this is just enforcing the 60 requests a second limit more strictly and adding a paid tier with higher limits I'm a big fan. Some paying clients will hopefully mean you can dedicate a bit more developer resources to updating the api (in addition to the changes being made due to devvit).
We’re introducing additional safeguards to how developers access sexually explicit content from our API across all endpoints, ensure (all the while) not to break moderation flows that may depend on these.
Safeguards or just removing the content completely? Will, for example, posts in NSFW subreddits simply not appear in /api/info calls? Or will their feeds be inaccessible through the api? Or is this just some level of whitelisting or opt in? I totally understand restricting NSFW content from the site in general, advertisers don't like it, but I don't understand the motive for removing it from the API. What behavior are you hoping to stop by doing this?
Comment by KeyserSosa at 18/04/2023 at 18:53 UTC
17 upvotes, 16 direct replies
If this is just enforcing the 60 requests a second limit more strictly and adding a paid tier with higher limits I'm a big fan.
This is where we are aiming. Part of the work here is to actually take apart where and how we do have rate limits (lot of cruft in there to wade through) and provide some consistency, but in spirit, 60 QPM (previous terms were 60 queries per *minute* btw not second like you said!) is fairly well followed and therefore keeping it would be minimally disruptive!
Safeguards or just removing the content completely? Will, for example, posts in NSFW subreddits simply not appear in /api/info calls? Or will their feeds be inaccessible through the api?
For general feeds, it would to not provide the content for sexually explicit material (which is a subset of “NSFW”). Keeping in mind, we have to be careful here in that we don’t want to impact moderation bots/scripts/whathaveyou as part of this work, so we’ll likely have to create some of carve out, and be very careful as we roll this out.
This is why we are announcing this early, 60 days before we plan to make changes. We expect the “changes” here to be gradual as there are a lot of edge and corner cases to consider. We don’t want to pull an *insert snarky name of competitor here*.