FeX: Forum Explorer – Rethinking how we interact with threaded conversations
1–10 of 73 posts
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#2Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#3Another thing I was doing at the time was visualizing Twitter and Facebook friend graphs, and the first insight there was to deliberately drop the 'ego' node, as it destroys any hope of effectively showing community structure of the friends themselves (it also carries no extra information as everyone is necessarily connected to the ego).
So perhaps a similar thing would be effective for threaded conversations: if you drop the root node, disconnected discussions will become separate trees in the visualization, which will help with efficient use of space, and the tail of singleton comments that no one replied to will become isolated disks that can space-fill the background. Switching to an actual rectangular tree layout as I used in my prototype will also help in that one consistent direction (down) represents nested depth.
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#4Hi hackernews! I'm the author of this site/chrome extension/app. I'm happy to answer any questions you might have/field any comments
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#5Hi hackernews! I'm the author of this site/chrome extension/app. I'm happy to answer any questions you might have/field any comments
I then wanted to see the context for a specific comment so I clicked on it. Great that worked!
Then I wanted to go back to where I was in the list of comments by the OP. I clicked the back button ... that didn't work.
Ideally either the back button would work (each state has an equivalent URL) or the UI provides a way to return to the last state.
Thanks for the interesting tool!
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#6Is that part of what you're trying to test, or is it just an unimportant artifact of the test page?
Also, I'm not actually on board with the visualization -- it just makes everything more confusing and harder to follow. But that might be my personal idiocy.
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#7That page has a major layout issue for me: it appears to have a fixed height with no vertical scrollbar, so the bottom portion of the page is completely inaccessible to me even if I maximize the window. Is that part of what you're trying to test, or is it just an unimportant artifact of the test page? Also, I'm not actually on board with the visualization -- it just makes everything more confusing and harder to follo…
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#8Hi hackernews! I'm the author of this site/chrome extension/app. I'm happy to answer any questions you might have/field any comments
It might be worth mining the trn user interface for ideas.
The author tried to write a major new version (4) in the late 90s, but from what I could see of the development process (being on a mailing list), the codebase became unmanageable and there were lots of bugs that proved impossible to catch. Usenet was on its last legs by that stage anyway. So that's a cautionary tale: make sure the specification and basic architecture remains clear and clean. (I'm not sure how many of the bugs back then were related to managing ncurses and other fiddly issues that won't arise in the architecture of a web app.)
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#9Hi hackernews! I'm the author of this site/chrome extension/app. I'm happy to answer any questions you might have/field any comments
Thanks for sharing. I'd suggest adding a bit of descriptive prose / "about" / readme / FAQ on the linked page. Also, its layout is suboptimal on mobile safari.
I think this would be essential. I've been clicking around on it, and it's not entirely clear to me how to work it. I may be an idiot, but I'd really love some instructions.
EDIT: I just now managed to see the "wait I'm lost" link toward the bottom. It took some doing (that's part of the page that gets clipped). I'm now following the walkthrough -- perhaps that will clarify things for me.
Edit edit: OK, I think I have a basic understanding of what's up. It's overly complex for my needs, though -- I think I prefer the normal comment threads.