Harmon

There's other reports of this (e.g. https://twittercommunity.com/t/get-application-rate-limit-status-return-wrong-number-of-remaining-calls/175952), and I'm able to reproduce the issue, but this is a Twitter API bug, and it seems like it probably won't be fixed...

This is a bug with Twitter's API where using `exclude=replies` with the GET /2/users/:id/tweets endpoint doesn't exclude replies to the user's own Tweets. I was made aware of the bug...

I'm not sure what exactly you mean by running or what "API shutoff" you're referring to, but Tweepy should still be fully functional. That's not at all relevant to this...

Double check that your client ID and secret are correct. Regenerate the secret if necessary.

@boidushya Please don't ghost ping. Regardless, a reproducible example (MCVE/SSCCE) is necessary here. Although, if this is an OS-specific issue, I don't have an easy way of reproducing it on...

No, Tweepy doesn't support the subtitle endpoints yet.

Note, setting `return_type` to `dict` for `Client` or `AsyncClient` will have their methods return the raw JSON as a dictionary. I'm assuming that this is a feature request to include...

[`AsyncStreamingClient`](https://tweepy.readthedocs.io/en/v4.10.1/asyncstreamingclient.html#tweepy.asynchronous.AsyncStreamingClient)'s interface mirrors that of `StreamingClient`, for which there is [a guide with examples](https://tweepy.readthedocs.io/en/v4.10.1/streaming.html#using-streamingclient). The main difference is that many of `AsyncStreamingClient`'s methods are coroutines, which is documented. You can...

This is probably because of https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/

I don't think this is resolved, since the trove classifier is still missing in setup.cfg. I'm also not sure if the flaky tests mentioned in https://github.com/aio-libs/aiohttp/pull/7169#issuecomment-1384271888 are fixed yet.