I've experienced (twice) a newscan issue with Mystic (at least with MY Mystic.)

I was reading messages in a public message base. Let's say I was at message number 50 of 100.

I replied to message number 50, and I saved the message. Then I (J)umped to message # 101 to make a quick edit to the message I just posted (the
reply.) After editing, I (Q)uit to get out of message reading.

I came back later to continue reading new messages, but this time Mystic has
my last read pointer set at message #101 (as if I already read 50-101.)

It seems like I tricked the system when I (J)umped to message # 101.

This isn't a big deal obviously - but has anyone else experienced this?

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: CompuBBS | Ashburn VA | cfbbs.scinet-ftn.org (1:275/99)

Re: Newscan Issue
By: Aaron Thomas to All on Wed Mar 24 2021 01:04 pm

I've experienced (twice) a newscan issue with Mystic (at least with MY Mystic.)

I was reading messages in a public message base. Let's say I was at message number 50 of 100.

I replied to message number 50, and I saved the message. Then I (J)umped to message # 101 to make a quick edit to the message I just posted (the reply.) After editing, I (Q)uit to get out of message reading.

I came back later to continue reading new messages, but this time Mystic has my last read pointer set at message #101 (as if I already read 50-101.)

It seems like I tricked the system when I (J)umped to message # 101.

This isn't a big deal obviously - but has anyone else experienced this?

That's the way last read pointers work. When you jump from message 50 to 101 your last read pointer is set to 101. I get the same result here on SBBS.

Ttyl :-),
Al

... Cursor: An expert in four-letter words
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Re: Newscan Issue
By: Aaron Thomas to All on Wed Mar 24 2021 13:04:31

I replied to message number 50, and I saved the message. Then I
(J)umped to message # 101 to make a quick edit to the message I
just posted (the reply.)

ok...

After editing, I (Q)uit to get out of message reading.

i think that's where you messed up... what happens if you jump back to 50 before quitting?

JAM has two read pointers... lastread and highread... here's how they work...

1. you start at 50; lastread is 50; highread is 50.
2. you jump to 100; lastread is 100; highread is 100.
3. you jump to 50; lastread is 50; highread is 100.

if you quit at #1, you're ok.
if you quit at #2, you miss 50 messages.
if you quit at #3, you're ok.

do you see how it works, now?
that's how it is supposed to work...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

I replied to message number 50, and I saved the message. Then I (J)umped to message # 101 to make a quick edit to the message I just posted (the reply.) After editing, I (Q)uit to get out of message reading.

I came back later to continue reading new messages, but this time Mystic has my last read pointer set at message #101 (as if I already read

Yes if you jumped to 101 that would be your highest read message, so its doing what its supposed to do.

You can set your current high read message with the H key...

So you could reply at 50, jump to 100, edit, jump back to 50 and press H to set your high read message to 50 again.

I could make it so that it automatically resets your high read message when you Jump to a lower message, and I think I might even like that better - but because BBSes generally haven't worked that way I think doing so might end up confusing people more than it helped.

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

That's the way last read pointers work. When you jump from message 50 to 101 your last read pointer is set to 101. I get the same result here on SBBS.

Thank you!

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: CompuBBS | Ashburn VA | cfbbs.scinet-ftn.org (1:275/99)

do you see how it works, now?
that's how it is supposed to work...

Yes, thanks. I don't know why I thought I could jump to a higher number and still have messages in the middle remaining unscanned. Maybe that's a Renegade thing.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: CompuBBS | Ashburn VA | cfbbs.scinet-ftn.org (1:275/99)

So you could reply at 50, jump to 100, edit, jump back to 50 and press H to set your high read message to 50 again.

Thanks. I never knew about this either. I almost asked you for a feature like that!

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: CompuBBS | Ashburn VA | cfbbs.scinet-ftn.org (1:275/99)

Re: Re: Newscan Issue
By: Aaron Thomas to mark lewis on Thu Mar 25 2021 12:57:27

do you see how it works, now?
that's how it is supposed to work...

Yes, thanks. I don't know why I thought I could jump to a higher
number and still have messages in the middle remaining unscanned.

you can but you have to jump back... software using JAM bases should use the lastread pointer instead of the highread one for this to work properly... i remember plenty of confusion when JAM was introduced... some coders just
made both pointers the same every time and thus negated one of the features of the format... others used lastread or highread for everything and ignored the other one with the same result...

in normal operation, highread only changes if it is lower than lastread... lastread is used for normal movement through the messages like it would be normally in a format that has only one read pointer...

Maybe that's a Renegade thing.

i don't know... it may have a similar method coded into the BBS and instead of it part of the message base format... i've never used renegade and don't know if i've ever logged into one or not...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

you can but you have to jump back... software using JAM bases should use the lastread pointer instead of the highread one for this to work

That explains what I thought was an inconsistancy. I usually re-read my messages when I'm finished, but instead of Jumping back to where I was, I was just quitting and starting the scan over. So, I've learned my lesson.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: CompuBBS | Ashburn VA | cfbbs.scinet-ftn.org (1:275/99)