FeX: Forum Explorer – Rethinking how we interact with threaded conversations
61–70 of 73 posts
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#62Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#63Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#64But I sure do like graphs.
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#65Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#66Hi hackernews! I'm the author of this site/chrome extension/app. I'm happy to answer any questions you might have/field any comments
When I started reading Usenet in the 90s, trn (threaded read news) was the state of the art in news readers. 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…
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#67Hi 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
#68* The circle should plot threads clockwise newestoldest (or reversible?)
* Node connection length should be the reply delay in the chain
* Node size should reflect comment size
* Node color/opacity should reflect comment score/vote amount (if present, which HN doesn't have.)
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#69Earlier quoted context omitted.
When I started reading Usenet in the 90s, trn (threaded read news) was the state of the art in news readers. 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…
In terms of the interface, what did trn have over other newsreaders that were capable of displaying threads?
Threads that the user didn't want to read could be "junked". This could work in the context of HN as a way of sorting posts into interesting and not interesting on a per-user basis.
Rather than just navigating a set of threads, trn gave the user tools to productively keep up with discussions they were interested in, and not have to worry about other discussions at all (after dismissing those discussions once).
Here's a basic explanation of the interface: https://www.einval.com/~steve/software/trn-faq.html
Re: FeX: Forum Explorer – Rethinking how we interact with threaded conversations
#70Earlier quoted context omitted.
Very cool. I've got to admit though, I'm a little jaded towards "Chrome only" extensions. Is there a reason you couldn't build this in Firefox? As web developers, we've really got to stop this practice lest the web become further fragmented. Anyways, I don't want to come down on you specifically - I realize this is probably just an MVP. You did a great job.
Is there a reason you can't build this in FireFox? How does "someone built a Chrome extension" justify you asking them to explain themselves for why they didn't build it the way you want?
OP seems to agree with the sentiment, so I'm not sure why you're bothered.