-
Notifications
You must be signed in to change notification settings - Fork 14
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
Output shared tweets between profiles? #45
Comments
We were partially thinking about that in #33 - though I think in that we were thinking more as a sample rather than the complete list. It would probably be useful to have both - though I have to doublecheck whether the filesizes are still managable if we're embedding full lists of tweets into edges. |
The file sizes will probably be too big if it's incorporated in the edges. I was actually thinking about having a separate export (eg. .csv file) which could be a optional configuration after/while computing the networks. Is the full list of tweets accessible in the current code base? |
Sorry for the long delay - I've just moved jobs + will be handing the bulk of the work on this over to someone else soon (expect a bit more development activity :) To answer your question, that isn't currently available in the codebase, there was an early decision to get to aggregates as quickly as possible to keep things fast. Probably the fastest way to start to add this would be a small extension at the library layer that calculates the tweets coordinating between specific nodes on demand. @timothyjgraham - maybe this could be a good first feature once the new person is on board? |
Apologies if this has been covered in your documentation and I have missed it. Is there a function to output the specific tweets from each profile which lead them to being tied to other profiles, by the six different coordination network functions?
If not, this would be quite helpful when wanting to investigate what kind of links, tweets and text which was common for two or more profiles in the network.
The text was updated successfully, but these errors were encountered: