|
Yes, there should be a more convenient
way to read through all responses.
Sibling links (both forward and
backward) would help, but one also
wants to go deeper or skip back
to higher levels. It would be
nice to have one way to
traverse all responses no matter
what level they are on. But reading
responses in that order would tend
to jump around alot getting you
confused about the context of
each response. This is why
the "star" configuration of
responses in a single chain
makes some sense. More on that
another time... I believe browsers should be made smarter about public and group annotations of documents, once a standard for them comes out. For one thing, it will soon be very important for readers to be able to see just the new annotations. What's new for one reader is not new for another, so the server cannot do a great job of threading the responses without alot of work. I'd also like to see browsers that can open a page for a link but always on another page. This would let you click on response links in the tree at the level you are interested and see the response text in another window, the same other window each time. This would avoid filling up your window history with the whole thread of all responses you have read.
|
| Inline: | Outline: |
|
to: |
|
|