Tony wrote:
IMO, web interfaces to threaded discussion is horrendous.
Some of them are decent, but I would agree that the vast majority border
on unusable, including GG.
In what way is a newsreader interface for reading better
than Google groups ?
My best explanation for this is the following snippet from my ~/.slrn-scores
file (the killfile of the newsreader slrn):
[*]
Score: =-9999
Message-ID: <.*\.googlegroups\.com>
This assigns the most negative score to anything with a Google Groups message
ID, thus making it disappear.
This gives a reason why it may be bad for posting but not why
it's bad for reading.
It gives both. How do you implement a rule like the above in Google Groups?
Apart from spam/troll filters what do you consider the main
feature that a newsreader has but the Google interface
doesn't ?
Is there any reason why you can't ask these questions in a newsgroup
about newsreaders, like news.software.readers? Or do you only care about
answers from C programmers?
I will give you a quick point form:
- Indefinite session persistence: take as long as you want to edit a response;
if the NNTP socket is closed, software can reconnect.
- Maintaining unfinished articles in a draft container, indefinitely.
- Local storage of article in the draft stage---in the event of a failure,
you can recover it (e.g. ~/.article or ~/.followup file in your home
directory). On Google if the browser dies, there goes your draft.
- Integrated use of your favorite text editor like Vim.
- The sofware will not munge your text. What you edit is what goes into the
server.
- Etiquette warnings to help safeguard against gaffes: warning that you're
crossposting without followup-to, warning against long lines, warning against
excessive quoted text, warning that your followup is being redirected to
newsgroups other than what you're reading.
- Far superior thread navigation.
- Entire thread displayed all in one view regardless of its size;
no fragmentation into ``newer'' and ``older''.
- Correct article is displayed when its condensed representation
is selected in the tree view; no need to match numbers
in thread pane and body pane.
- No bullshit bugs like articles from five years ago with the
same subject line being treaded in the same view as the
current thread!
- Scriptability. For instance my Message-ID: is generated by a custom script.
- Ability to specify arbitrary headers.
- Decoding binaries from multi-part posts.
- Using MIME (in newsgroups that allow it, of course).
- Cancelation and supersede support (may be limited by servers, but that's
no rationale for not providing it in the UI).