5 ms·

Visualising Twitter Conversations in 3D Space

17 points by edent 5y ago

stewx 5y ago
Side project idea: for "art", build a bot targeting specific Twitter accounts, auto-generating deepfake videos of the tweet author reading the text of their tweet, and sending it as a reply to the original tweet. Why? No real reason, I just think it would be cool.
prox 5y ago
Force directed graphs, nice but useless (at least when I used it) or perhaps I just used it wrong.
slightwinder 5y ago
Twitter conversation-view is aweful. It's like they don't want you to be able to follow it clearly and make it extra hard on purpose. Good to see that is now (meaning last year) an officual API to make threaded views simpler. Maybe some day a saner conversation-view will approach from this.
- Isthatablackgsd 5y ago
  The Twitter 'unnested-nested style' conversation continuously baffled me. It is confusing and harder to follow where the conversation go. Normally the headline or original poster should be on the top. But in retweeting, the person who is retweeting will be on the top and put the original below it which is strange and confusing.
- iamevn 5y ago
  The thing that gets me is that you (as someone writing your own client) can't reliably get all the replies to a tweet from Twitter's api. Twitter gives you a conversation_id property[1] on tweets that you can search for, but you can only search for it in recent (in the last week) tweets. Searching for older tweets in a conversation requires registering as an Academic Research Project[2]. I'm just some schmuck that wants to throw a script together to get a tree view of a thread that's big enough to be a pain to read in the web client (the main thread is long enough that replies to individual posts in the thread don't ever get loaded in). Really curious to see how this tool does it. [1] https://developer.twitter.com/en/docs/twitter-api/conversation-id https://developer.twitter.com/en/docs/twitter-api/conversati... [2] https://developer.twitter.com/en/docs/twitter-api/tweets/counts/api-reference/get-tweets-counts-all https://developer.twitter.com/en/docs/twitter-api/tweets/cou...
  - iamevn 5y ago
    > The Twitter conversation API only works on tweets sent in the last 7 days. So you can't use this on older threads. Oh it doesn't, rip.
    - edsu 5y ago
      If you work as a researcher you might be able to apply for Academic Research Product Track access, which gives you access to the full archive of tweets back to 2006.
CrazyPyroLinux 5y ago
Reminds me of https://gource.io/ https://gource.io/ Seems like there is some untapped potential in this for a 3D code visualization system. Sort of "Gource meets CodeLens." More than just "watch this flashy movie of our code evolving" but actually being able to navigate dependencies, call graphs, etc. to gain insight on the codebase.

17 points by edent 5y ago

Side project idea: for "art", build a bot targeting specific Twitter accounts, auto-generating deepfake videos of the tweet author reading the text of their tweet, and sending it as a reply to the original tweet. Why? No real reason, I just think it would be cool.

prox 5y ago

Force directed graphs, nice but useless (at least when I used it) or perhaps I just used it wrong.

slightwinder 5y ago

Twitter conversation-view is aweful. It's like they don't want you to be able to follow it clearly and make it extra hard on purpose. Good to see that is now (meaning last year) an officual API to make threaded views simpler. Maybe some day a saner conversation-view will approach from this.

Isthatablackgsd 5y ago
The Twitter 'unnested-nested style' conversation continuously baffled me. It is confusing and harder to follow where the conversation go. Normally the headline or original poster should be on the top. But in retweeting, the person who is retweeting will be on the top and put the original below it which is strange and confusing.
iamevn 5y ago
The thing that gets me is that you (as someone writing your own client) can't reliably get all the replies to a tweet from Twitter's api. Twitter gives you a conversation_id property[1] on tweets that you can search for, but you can only search for it in recent (in the last week) tweets. Searching for older tweets in a conversation requires registering as an Academic Research Project[2]. I'm just some schmuck that wants to throw a script together to get a tree view of a thread that's big enough to be a pain to read in the web client (the main thread is long enough that replies to individual posts in the thread don't ever get loaded in). Really curious to see how this tool does it. [1] https://developer.twitter.com/en/docs/twitter-api/conversation-id https://developer.twitter.com/en/docs/twitter-api/conversati... [2] https://developer.twitter.com/en/docs/twitter-api/tweets/counts/api-reference/get-tweets-counts-all https://developer.twitter.com/en/docs/twitter-api/tweets/cou...
- iamevn 5y ago
  > The Twitter conversation API only works on tweets sent in the last 7 days. So you can't use this on older threads. Oh it doesn't, rip.
  - edsu 5y ago
    If you work as a researcher you might be able to apply for Academic Research Product Track access, which gives you access to the full archive of tweets back to 2006.

CrazyPyroLinux 5y ago

Reminds me of https://gource.io/ https://gource.io/ Seems like there is some untapped potential in this for a 3D code visualization system. Sort of "Gource meets CodeLens." More than just "watch this flashy movie of our code evolving" but actually being able to navigate dependencies, call graphs, etc. to gain insight on the codebase.