Benjamin Ooghe-Tabanou

we could benefit from the resolver calls to extract the twitter cards meta from the html optionnally

Couldn't we have only dev dependencies in a separate requirements file for instance?

I'm split :p Otherwise I have a "fantastic" idea! Let's add a github action that checks the consistency on each commit and fixes it whenever we forget! OK I'm leaving...

Actually this behaviour does not applyto the stream which returns exact results (as described in https://developer.twitter.com/en/docs/twitter-api/v1/tweets/filter-realtime/guides/basic-stream-parameters ) So for best results, using the exact words instead of unaccented characters could...

quick experiments seem to indicate no rate limit on this route (???) and between 1.5 and 2 calls of 15 urls per second, hence a resolving rate of about 25...

```bash d0=$(date +%s) count=0 while true; do count=$((count+1)) curl -X POST "https://api-ssl.bitly.com/v3/expand" -d access_token=$BITLY_API_TOKEN -d hash=2pKPIqQ -d hash=2RK2Mtc -d hash=2pKPIqQ -d hash=2RK2Mtc -d hash=2pKPIqQ -d hash=2RK2Mtc -d hash=2pKPIqQ -d hash=2RK2Mtc...

So it seems to be confirmed: it ran 2 hours (7216 seconds), calling in total the API 12437 times for 15 urls each time without returning an error once, meaning...

The error seems to indicate you formatted your configuration file wrongly. There must be a missing comma somewhere at the end of line 18.

I guess your queries might be wrong, can you copy paste the keywords part of your config file ?

There is something weird, the keywords you're giving do not correspond to the query that seems to be returned by twitter as an error, it should be the case if...