Message pointers determine what message you'll see in a new-scan based on their *import* date/time, not the date/time they were supposedly written (which is the date/time shown in the message header to users). So, not weird really. Someone just dumped some old messages into a network, it happens a lot.
Re: Message Base Question
By: Digital Man to Mortar on Sun Jan 18 2026 17:07:44
Message pointers determine what message you'll see in a new-scan based on their *import* date/time, not the date/time they were supposedly written (which is the date/time shown in the message header to users). So, not weird really. Someone just dumped some old messages into a network, it happens a lot.
Well, since the user can't see the import date (or can they?), makes more sense (IMO) to have the pointers use the date written date, which is more meaningful to the user.
Re: Message Base Question
By: Digital Man to Mortar on Sun Jan 18 2026 17:07:44
Message pointers determine what message you'll see in a new-scan basedon
their *import* date/time, not the date/time they were supposedlywritten
(which is the date/time shown in the message header to users). So, notweird
really. Someone just dumped some old messages into a network, ithappens a
lot.
Well, since the user can't see the import date (or can they?), makes more sense (IMO) to have the pointers use the date written date, which is more meaningful to the user.
Well, since the user can't see the import date (or can they?),
makes more sense (IMO) to have the pointers use the date written
date, which is more meaningful to the user.
Except that messages are imported or sorted by "written date".
Except that messages are imported or sorted by "written date".
FWIW, sbbsecho seems to do a lot better job keeping messages in such an order where, when read in the order posted, a discussion can be followed vs. some other tossers/tosser-shims I have used in the past.
I rarely notice ftn messages read in sequence seeming out of order here. Usenet groups are about the only place I might notice it, and I suspect
that is something that happens before sbbsecho gets hold of the messages.
* SLMR 2.1a * Only sheep make baaaad puns.--
FWIW, sbbsecho seems to do a lot better job keeping messages in such an order where, when read in the order posted, a discussion can be followed vs. some other tossers/tosser-shims I have used in the past.
I'm not sure why that would be. Maybe other tossers don't unpack bundes in the day-of-week order? I seem to recall that much older versions of SBBSecho didn't .
Except that messages are imported or sorted by "written date".
Message pointers determine what message you'll see in a new-scan based
on their *import* date/time, not the date/time they were supposedly
written (which is the date/time shown in the message header to users).
In any case how they're imported is irrelevent from a users'
perspective. It's how it can be manipulated once there that's
important.
Re: Good Pointers
By: Digital Man to Mortar on Sun Jan 18 2026 19:19:50
Except that messages are imported or sorted by "written date".
If that were the case, then I shouldn't be seeing msgs. from 2020. This seems to be a contradiction to...
| Sysop: | Morningstarr |
|---|---|
| Location: | Mt. Pleasant Nc |
| Users: | 3 |
| Nodes: | 250 (1 / 249) |
| Uptime: | 14:23:46 |
| Calls: | 1 |
| Calls today: | 1 |
| Files: | 498 |
| U/L today: |
498 files (5,172M bytes) |
| D/L today: |
89 files (387M bytes) |
| Messages: | 3,527 |
| Posted today: | 7 |