The tree stopped expanding.

And it took me a while to realize I can open the console.

There I saw hundreds of such pink errors:

... only then I realized that perhaps I got rate-limited? It was a large tree.

What would be mitigation methods? Some ideas:

• show in the GUI when that error happens
  • only much later I realized that pressing "stop expanding" was the right thing to do
• auto-stop the expanding after 5 such messages came in?
• additional option to fill in some (0.01s ? 0.1s, 0.5s, 1s ?) delay between each API call, to escape from ANY rate-limiting by twitter?

Now that I know what can happen, I will find my way around, I guess. For newbs though, a solution could be fruitful.

Thanks for this amazing tool. Have used it for the second discussion now. Great!

As suggested here: https://twitter.com/thomaskowtsch/status/863138253683249152

Thank you for the Treeverse, it is very useful for us.
The issue is related to the archive mode.
If you open the archive mode from the Treeverse menu, the dragging area for the json files to be opened are not shown as in the screenshot-1.

I tried to run the archive mode from this address also: https://paulgb.github.io/Treeverse/
In that case, I could upload the json file I have but the tweet contents are not visible in the graphical interface as in the screenshot-2.

Therefore, in either case, we can't use the archive mode properly.
Thanks again for all your effort.

When viewing a tweet on the mobile website (mobile.twitter.com), the extension isn't active, e.g.:

https://mobile.twitter.com/tastapod/status/1075743440632233984

For background, the reason I'm on a mobile.twitter.com subdomain is that bookmarked tweets only seem to be accessible via the mobile version of twitter and not the desktop version. 🤷‍♂️ Thanks Twitter!

• Links are not clickable
• Images do not appear
• Long tweets are cut off (!)
• The Chrome version requires the user to click, then refresh, the first time in a session. We could probably do this automatically.
• Show a message of some sort when users not logged in to Twitter try to use it. (#37)

https://twitter.com/theGreaterMarin/status/1027195881643298816

tl;dr it's a new csrf policy check. We can get around it by re-using the tab instead of creating a new one.

The extension isn't working for me, here is what is in my console:

XMLHttpRequest cannot load https://twitter.com/Bortseb/status/897884889458106369. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'chrome-extension://aahmjdadniahaicebomlagekkcnlcila' is therefore not allowed access. The response had HTTP status code 400.

Requested on Twitter: https://twitter.com/mindianajones/status/991715776506814464?s=19

Any tweet is adjusted LTR, even if the content is is hebrew or arabic and should show as RTL.
In case of mixed content the whole tweet gets out of order (for example, this tweet is adjusted fine in Twitter, but not in treeverse version).

Here https://paulgb.github.io/Treeverse/ , I can upload twarc.json to the Treeverse, but I found no way to do this with Firefox Addon.

It would be nice to have an option to show a summary of the tweet itself in the tree - for example the first 40 characters followed by an ellipsis, or a thumbnail of an image. This would make the tree a lot more legible.

After I have explored some expanded parts of a conversation, I would like to be able to collapse that part by e.g. clicking the top-level tweet of that thread, so that my screen does not get cluttered, allowing me to focus on other threads which I have not explored yet. You could also add toggling collapse/expand with the space button.

This would need a method on TweetTree called collapseNodes, which would just hide them from the UI (but would keep the tweet content so that it does not get reloaded if I toggle it back). Its implementation could be done by adding a isVisible field on TweetNode, which would skip rendering it and all of its children if set to true.

Does the above description make sense? Great tool otherwise, thanks for building it!

Thanks very much for Treeverse!
Often I want to read a whole discussion there, but it's hard to keep track of where I've been.
Would you be interested in some UI ideas for this?

One idea involves allowing the user to mark nodes that they've already read.
Another involves keyboard navigation [I realize there's some already].
These ideas could be combined.
Details on request! 😅

suggested here: https://twitter.com/CopropraxiaETC/status/961804583659032576

probably best to add a "childrenVisible" flag to each node.

Double click handler would have this behavior:

• if the node has more children, load them
• otherwise, if the node has children, toggle childrenVisible
• otherwise, no action

The "more to load" indicator should appear if childrenVisible is false and the node has children

#52 is fixed in Chrome but breaks Firefox in master. Need to get it working again so Firefox can be deployed.

Running node v13.11.0. Some type errors on build. I would fix it myself if I knew typescript.

$ ./node_modules/.bin/webpack
(lots of stuff that's fine…)
ERROR in /Users/fei/git/treeverse2/src/viewer/tweet_visualization.ts
./viewer/tweet_visualization.ts
[tsl] ERROR in /Users/fei/git/treeverse2/src/viewer/tweet_visualization.ts(66,26)
      TS2352: Conversion of type 'Selection<SVGGElement, {}, null, undefined>' to type 'D3Selector' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Type 'SVGGElement' is missing the following properties from type 'HTMLElement': accessKey, accessKeyLabel, autocapitalize, dir, and 16 more.

ERROR in /Users/fei/git/treeverse2/src/viewer/tweet_visualization.ts
./viewer/tweet_visualization.ts
[tsl] ERROR in /Users/fei/git/treeverse2/src/viewer/tweet_visualization.ts(68,22)
      TS2352: Conversion of type 'Selection<SVGGElement, {}, null, undefined>' to type 'D3Selector' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.

ERROR in /Users/fei/git/treeverse2/src/viewer/tweet_visualization.ts
./viewer/tweet_visualization.ts
[tsl] ERROR in /Users/fei/git/treeverse2/src/viewer/tweet_visualization.ts(69,22)
      TS2352: Conversion of type 'Selection<SVGGElement, {}, null, undefined>' to type 'D3Selector' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.

ERROR in /Users/fei/git/treeverse2/src/viewer/visualization_controller.ts
./viewer/visualization_controller.ts
[tsl] ERROR in /Users/fei/git/treeverse2/src/viewer/visualization_controller.ts(83,13)
      TS2322: Type 'Timeout' is not assignable to type 'number'.

Hi,
I'm inserting here what I have read in this thread #1 (comment)

Thank you @paulgb

Ok thanks, I'll reword this so that it is crystal clear. I have no intention of misleading people about what Treeverse does. #treeversebug

— Paul Butler (@paulgb) December 20, 2019

Long posts that are too tall for the window don't seem to get a scroll bar, and seemingly can only occasionally be scrolled with the mouse wheel, either.

See, for an example, the right-side reply to this post: https://twitter.com/bikelaneuprise/status/1037351778860318725

I have unfortunately lost the source on this one, but the issue is similar — a photo attached to the tweet is so tall that it pushes up under the infobox, and with no ability to scroll, it's impossible to see all the text.

Here's another image example, from https://twitter.com/bikelaneuprise/status/1037026430440361984. This one for some reason I was able to scroll with the mouse wheel.

First off, thank you for this tool. It's pleasantly enjoyable and I think the UX of hovering over and being able to see the whole thread is really clever.

I was just browsing a conversation and I noticed some people linking to past tweets from their tweets. I was curious if you had thought about including links to other tweets as explorable? Not sure about where you would represent them, maybe as a sideways edge, if it doesn't exist in the graph so far, and if it does, an edge to that existing node?

I guess technically then this would be "graphverse" instead of "treeverse"...

Version: 3.1

The page seems to refresh when clicking the extension, but it doesn't display. No console errors. I ran it incognito so as to assure there were no other extensions that could interfere.

Hi,
It seems like Treeverse can't load tweets hidden behind the "show more replies" link.
In this case, there is an ellipsis on the tweet, and the double-click just makes it disappear, without any branch appears.
It only happens with tweets displayed with "show more replies" below in twitter display.

Thanks a lot for this app, Treeverse is amazing :)

Includes a fix for #31.

A recent Twitter change resulted in a big change in how Treeverse works. Instead of opening up a new tab, Treeverse injects itself into the current HTML page.

These things are known to be broken:

• The download button has been removed for now because the way offline export worked made some assumptions about the page that have changed.
• Loading "deeper" works, but loading "broader" does not. (fixed in 1.3)
• Warnings appear in the console from Semantic UI over font loading.
• It breaks the back button. (fixed in 2.0)
• Archive mode doesn't work (#21)

There is a way to get a JSON file from the share server, but it should be possible locally too.

Hi!
I have a question about the parser.

On line 149 of src/viewer/tweet_parser.ts

let nextChildren = [];

What is the purpose of the array nextChildren that is not returned or used inside the function? Future purpose? Idea in progress? Leftover? I might also have missed something.

Thanks for your work which I am trying to adapt for Python in order to retrieve the tree structure of conversations.

I never thought of doing this but it would be possible to do, I think. Requested on Twitter: https://twitter.com/kendmil/status/1103851198812164096

As reported here: https://twitter.com/PKolachina/status/1258813454590361600

Able to replicate on Mac with Version 81.0.4044.129 (Official Build) (64-bit)

FireFox version still appears to work, indicating this is more likely a change in a Chrome API than a Twitter API.

Sorry if maybe this isn't possible in Twitter, it would make this app really useful to me (already use it a lot!).

I saw #45 discussed downward traversal options, is there anything preventing traversing threads up to the source from which all replies were issued?

Reported on Twitter

https://twitter.com/AcidRampage/status/1021291619008446464?s=19

I'm having troubles using the extension with the new twitter UI. When I try your example, I just get an empty screen and the following errors in the js console.

Keyboard navigation would make a great addition, especially on big trees where point-and-clicking becomes hard.

Especially of "rate limit exceeded"

(via email 2020-06-12)

I tried imported a valid twarc file and got the message "'Orphaned tweet detected! See the readme for format details. Aborting."

Would it be possible to change https://github.com/paulgb/Treeverse/blob/master/src/viewer/archive.ts#L66 to raise an error, but continue trying to show what it can of the tree?

The file in question

When you click to share the tree, it gets sent to an AWS Lambda function at that endpoint. I agree that using the raw Lambda URL looks very sketchy, I will open an issue to use a https://t.co/ougObJrMXI URL as well. #treeversebug

— Paul Butler (@paulgb) December 20, 2019

Once you click on the treeverse chrome add on - it opens the new tab...with the blank window but it does not load any tweet data. Not sure if it is a Twitter issue or if somehow Treeverse has stopped working.

As reported by @infinitebuffalo in #22:

I have unfortunately lost the source on this one, but the issue is similar — a photo attached to the tweet is so tall that it pushes up under the infobox, and with no ability to scroll, it's impossible to see all the text.

Here's another image example, from https://twitter.com/bikelaneuprise/status/1037026430440361984. This one for some reason I was able to scroll with the mouse wheel.

As reported by @infinitebuffalo in #22:

See, for an example, the right-side reply to this post: https://twitter.com/bikelaneuprise/status/1037351778860318725

The actual tweet responsible is this one with a very long URL: https://twitter.com/TroyFor25/status/1037397543435550721

Twitter condenses the URL when displaying it (how? is it a CSS thing?), but Treeverse does not.

Hi!
Thanks for Treeverse.
Contrary to "twarc replies --recursive", Treeverse is able to retrieve conversations older than the search limit (which is 7 or 30 days).
I would like to add the possibility to retrieve conversations (status_id as a tree structure, or just status_id & in_reply_to_status_id pairs or in twarc json format) automatically while using Treeverse as a script or a command inside a terminal.
I am new to TypeScript (I know C++, Python and a bit of JavaScript). Do you think it can be done? Would it be easier to just use the brute-force method "list all reply to a given username, filter by in_reply_to_status_id) in a Python script (which is not so easy because tools like TweetScraper don't retrieve "in_reply_to_status_id" so I'd have to make speed limiting API calls)?
Do you have suggestions or recommendations on how to achieve this? I wouldn't want to start hacking in the wrong direction... :-)
Thanks.

Treeverse has become quite useful in my research. Is there a way to do a "save as" with the treeverse.html page so the user can pick the name it is saved under?

When a shareable link is created, any ellipses disappear and you lose the ability to expand those tweets.

Brilliant extension! Minor issue, when downloading a page, the HTML is malformed.

It is missing from the start:

<!doctype html>
<html>

And, from the end, the closing

</html>

Ref https://www.w3.org/TR/html5/syntax.html#the-doctype

I think this can be fixed in https://github.com/paulgb/Treeverse/blob/master/src/viewer/offline.ts#L28

I will attempt a PR, although I've never worked on a Chrome extension.

https://mobile.twitter.com/theGreaterMarin/status/900475201867177985

Hi,
when I use it with the latest google chrome in Win 10, I have

Reported on Twitter: https://twitter.com/ozakiiiiiiiiiii/status/1207324851989549056

It would be great if there was a way of exporting with every tweet in view. Right now I can save the page as an html file, but I only get the tweets from the branch currently suggested. Would it be possible to replace the user thumbnails in the viewer with the entire tweet text, so that when saved as a pdf/html you could zoom in anywhere, offline?

feature request: tree traversal choices?

• width first vs breadth first traversal;
  • for some discussions one is rather bad - results in either too wide or to tall pictures.
• perhaps (W,H) options for:
  • "crawl W tweets horizontally, then (in each) H tweets downwards",
  • and vice versa (for the first idea above);
  • and W and H can also be infinity.

Thanks for considering.

As far as I can see, there is no way to expand all nodes to see the whole tree. It's currently a lot of clicking the expand buttons to get the full overview.

Via Twitter: https://twitter.com/NotScottSiskind/status/1277830455665078272?s=19

Need to:

• Add a data representation for a missing tweet
• Figure out what missing tweets look like in API
• Capture past missing tweet
• Implement missing tweet in UI