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

Support for providing reply_count #356

Closed
jasco opened this issue Oct 22, 2020 · 6 comments
Closed

Support for providing reply_count #356

jasco opened this issue Oct 22, 2020 · 6 comments

Comments

@jasco
Copy link

jasco commented Oct 22, 2020

I notice that reply_count is not reported. Is there interest in adding this? Is this a limitation from the api endpoint used? (I last saw it while using the v2 endpoint directly and have not looked closely at v1.)

@edsu
Copy link
Member

edsu commented Oct 22, 2020

Yes, I think reply_count is new in v2. twarc doesn't support the v2 api yet but we are thinking about the best way to add it.

@tugrulz
Copy link

tugrulz commented Oct 22, 2020

Dear edsu, will the twarc support v2 any soon?

@edsu
Copy link
Member

edsu commented Oct 22, 2020

@SamHames & I have chatted about it, but not come up with a plan yet. The JSON output is very different, but we could look at adding some experimental support if you want to test. What API endpoint are you interested in?

@tugrulz
Copy link

tugrulz commented Feb 10, 2021

Sorry for late response. Getting the new annotations might be useful.

@edsu
Copy link
Member

edsu commented Feb 12, 2021

Work on v2 is beginning in earnest. Tune into to v2 branch to keep up with developments. Hopefully we'll have something for you to test soon.

@igorbrigadir
Copy link
Contributor

In v2 Reply counts are now included in expansions, so the tweet objects should have a public_metrics object with the counts https://github.com/DocNow/twarc/blob/main/twarc/expansions.py#L49

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

4 participants