The GraphQL endpoint is substantially better if you're wanting information about a post which would require making multiple requests to the V2 API. If you are going to use it, tell me and I'll work on posting an example (at least for JavaScript).
If you're wanting only the data which is returned from the V2 /api/v2.0/posts/:ids endpoint, then using the V2 API is probably easier than using the GraphQL interface. You can use that endpoint to obtain data on multiple posts at the same time.
@Makyen It's also possible to get data from the GraphQL interface on multiple posts in the same request. The requests are, however, more complex to set up in your code. If the data you are requesting is not within what the V2 API provides from a single access, then the GraphQL interface is quite substantially better.
For example, to get all the data FIRE needs on 100 posts would require between a bit over 300 to a bit over 400 requests from the V2 API, whereas it can be done in 7 to 10 requests with GraphQL.
@Mast OK. In general, a request is just a request. Different languages/libraries/frameworks have a variety of ways to communicate to their requests API what you're wanting to do, but what gets transmitted is the same, so there are a lot of similarities in how that gets communicated to whatever interface the language/library/framework you're using provides.
@Makyen That makes sense, but without an example I can't completely parse that information. I know nothing of the GraphQL structure or for which cases it's better than the other API.
They both appear to return JSON, so that helps at least.
@Ollie That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@Ollie That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@EJoshuaS-ReinstateMonica If a user only has a few posts and a substantial portion of them have already been reported, please don't user allspam to re-report all of the user's posts. In this case, there was only one other (of two) which had not yet been reported.
Would it be beneficial if it were to perform that check, with -force being an option in case a particular user abused the grace period to spam (or if some other circumstantial reason emerges)?
@Ollie That pattern looks like it's already caught by Bad phone number in answer and Bad phone number in body; append -force if you really want to do that.
@Spevacus There is a substantial rewrite of the code for reporting in a PR. IIRC, that check is included. However, it's been stalled for quite some time and my memory of exactly what the code does may not be accurate.
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, no whitespace in title, numbers-only title, potentially bad keyword in body (322): 12312343212345532134234 ✏️ by Emerald Archer on ru.stackoverflow.com
