Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on connecting to Twitter API - /1.1/statuses/filter.json #457

Open
oriolnfe opened this issue Oct 3, 2022 · 1 comment
Open

Error on connecting to Twitter API - /1.1/statuses/filter.json #457

oriolnfe opened this issue Oct 3, 2022 · 1 comment

Comments

@oriolnfe
Copy link

oriolnfe commented Oct 3, 2022

Hello,

I have run dmi-cat both in a docker environment, and with the auto installation in an Ubuntu 18.04LTS. I have configured the Twitter API Keys as instructed by both the guide and the wiki.

When I run the project with a query bin, in both situations, I get an error from the Twitter API:

Problem accessing \'/1.1/statuses/filter.json\'. Reason:

Please use V2 filtered and sample volume stream as alternatives

I created my API keys with both a project in Twitter and as a standalone app. The former shall have access to the v1.1 and v2 APIs, and the latter to the v1.1 alone.

Could you please review this issue?

thanks.

@dale-wahl
Copy link
Member

Hello @N3if, if you created a new application after April 29th, you unfortunately will not have access to API v1 and TCAT will not work with newer keys.

We have been migrating TCAT analysis features to another tool 4CAT. You can currently use 4CAT with Twitter API v2 search (both recent and the full archive search endpoints) and have access to all but the experimental analyses in TCAT. We are also developing a scraper that will use the filtered stream and sample streams similar to TCAT (still in pre-release development).

You can read more about our plans for the future of TCAT here..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants