| |
I am not sure I have the followup set right. I don't quite grasp if web
interface issues belong in .general or .nntp (neither does the filter
discussion belong in .nntp, but I digress).
I have noticed the following behaviour which seems quirky to me, it has to
do with following posts linearly and the context in which one does so.
Suppose that I have selected a group to view, say for example
lugnet.admin.nntp via a URL of the form: http://news.lugnet.com/admin/nntp/
This presents me with a list of posts. If I choose a post to view by
clicking on it (for example, following the URL:
http://news.lugnet.com/admin/nntp/?n=595) and that post is cross posted, I
am displayed that post *in the context of admin.nntp* That is as it should
be. Clicking on 596 takes me to the next post in admin.nntp. All well and good.
But if instead, I choose a post in which another group was the first group
mentioned in the list of groups to post to (for example this one:
http://news.lugnet.com/lego/direct/?n=2261 which is also theoretically 592
in admin.nntp)... when I view it I am no longer in the context of admin.nntp!
The post is displayed in the lego.direct context and the numbers I see to
move forward and back are 2260 and 2262, and I move forward and back in
lego.direct.
This strikes me as a quirk, because it means that if I want to view posts
linearly within a context, I have to choose which particular post I start
from. I can't just choose my first unread because it may put me in the wrong
context.
I could be misremembering but I seem to remember it didn't work that way
before. Did it?
I would suggest that the url that I see for 592/2261, if I am looking at it
in the list of admin.nntp posts, ought to be generated as
http://news.lugnet.com/admin/nntp/?n=592
rather than
http://news.lugnet.com/lego/direct/?n=2261
However (and I am speculating here without code base knowledge) I can also
see how that might be quite *hard to do* in the general case, especially
when it's not a list of posts I got to via a particular newsgroup, since
deriving the desired context may not always be straightforward and just
taking the first group named is simple.
Stating this quirk another way... a post "seems" more a member of l.x than
l.y if l.x was named first when it was posted, but more a member of l.y if
l.y was named first. Is that the intent or just a quirk?
I think this matters more to us if we are going to be in a situation where
we are going to see more cross posting than before, and I suspect we are
going to be in just such a situation soon.
++Lar
|
|
Message has 3 Replies:
 | | Re: Web interface "quirk"?
|
| Grumble grumble (at myself), I cut and pasted incorrecty and didn't post this originally to .nntp (just to .general twice, which fortunatly resulted in only one post) Sorry about that. (...) (23 years ago, 17-Mar-01, to lugnet.admin.nntp)
| | | Re: Web interface "quirk"?
|
| (...) It could probably go in either, but since this is news-related, I'm more comfortable with it being in the .nntp group. If you're talking about the TLC filter, that's pretty much entirely and .nntp thing. (...) Ya, it's a quirk (and I find it (...) (23 years ago, 26-Mar-01, to lugnet.admin.general, lugnet.admin.nntp)
|
6 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
