Hello All,

I've been noticing some paragraphs in QWK areas were being truncated at 256 characters. There is an update in the prealpha directory at mysticbbs.com and the current prealpha solves that.. :)

Folks who have QWK nets might want to have a look at that.

Ttyl :-),
Al

--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (21:4/106.2)

On 13 Aug 2020, Al said the following...

I've been noticing some paragraphs in QWK areas were being truncated at 256 characters. There is an update in the prealpha directory at mysticbbs.com and the current prealpha solves that.. :)

I'm running A46 Aug 11th and am still seeing some cropped QWK messages on DOVE-Net. Interestingly it seems to be only some messages, mainly from Nightfox.

I also have Synchronet running and his messages aren't cropped there. Both messages were downloaded from VERT with different QWK accounts.


Jay

... Psycho killer. Qu'est-ce que c'est?

--- Mystic BBS v1.12 A46 2020/08/06 (Windows/32)
* Origin: Northern Realms BBS | bbs.nrbbs.net | Binbrook, ON (21:3/110)

On 14 Aug 2020, Warpslide said the following...

I'm running A46 Aug 11th and am still seeing some cropped QWK messages on DOVE-Net. Interestingly it seems to be only some messages, mainly from Nightfox.

Some message editors, like golded and recently SlyEdit don't wrap message
text when they save the message to the message base, they are saved in a
long line so the text can be wrapped when it is being viewed on your terminal based on the dimensions of your terminal.

Most but not all BBS software wraps the text based on the dimensions of the terminal when the message was written. BBBS also doesn't wrap message text. That's OK as long as those reading your message are using a terminal with the same dimensions. If folks are using a different size terminal they need to unwrap that wrapping or bump and grind along with it.

Previously Mystic's QWK system and I suppose qwkpoll would truncate long lines somewhere around 256 characters so that's why some paragraphs seemed to end
mid paragraph. Something that isn't seen often in QWK because in almost every case editors would wrap the message text for an 80x25 screen size, something SlyEdit doesn't do anymore.

I like the idea of long lines since it is easy for a BBS or message viewer/editor to display those long lines for different screen sizes like phones or tablets. Most BBSs do wrap text when the message is saved based on the current screen size so it can make viewing a message on a phone or tablet or other screen dimension harder to accomplish.

Ttyl :-),
Al

--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (21:4/106.2)

On 14 Aug 2020, Al said the following...

Some message editors, like golded and recently SlyEdit don't wrap message text when they save the message to the message base.

I just realized I was running August 6th's build, not Aug 11th.

NOW I'm running Aug 11th! ;)

We'll see if that helps... *fingers crossed*

Jay

--- Mystic BBS v1.12 A46 2020/08/11 (Windows/32)
* Origin: Northern Realms BBS | bbs.nrbbs.net | Binbrook, ON (21:3/110)

Hello Warpslide & Al!

On 15 Aug 2020, Warpslide said the following...

NOW I'm running Aug 11th! ;)

Me too! :)

However Mystic (still?) appears to be cutting off long lines of (at least) QWK messages when quoting them (in the full screen editor).

They appear correct when reading them, but cut off when replying to (quoting) them.

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden

Re: Long lines in QWK packets
By: Zip to Warpslide on Sat Aug 15 2020 12:06 pm

Hey,

Something strange with your post:
┌────────────────────────····
│ Subj: Long lines in QWK packets
│ To : Warpslide
│ From: Zip (1:0/64)
│ Date: Sat Aug 15 2020 12:06 pm UTC+2:00 (4.2 hours ago) └───────────────────────────────────────────────······

And it had no address in the origin line - which might be why its 1:0/64?

...δεσ∩

... Life is a hereditary disease.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello alterego!

Thank you for your reply!

On 16 Aug 2020, alterego said the following...

Something strange with your post:
│ Subj: Long lines in QWK packets
│ To : Warpslide
│ From: Zip (1:0/64)
│ Date: Sat Aug 15 2020 12:06 pm UTC+2:00 (4.2 hours ago)
And it had no address in the origin line - which might be why its 1:0/64?

Really strange -- I managed to fetch the ZIP file (00000066.sa0) from my recycle bin and the PKT file inside it contained (output from 'strings'
command here):

15 Aug 20 12:06:39
Warpslide
Long lines in QWK packets
AREA:FSX_MYS
TID: Mystic BBS 1.12 A46
MSGID: 21:1/202 899e9c0f
TZUTC: 0200
Hello Warpslide & Al!
On 15 Aug 2020, Warpslide said the following...

NOW I'm running Aug 11th! ;)

Me too! :)
However Mystic (still?) appears to be cutting off long lines of (at least) QWK messages when quoting them (in the full screen editor).
They appear correct when reading them, but cut off when replying to (quoting) them.
Best regards
--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden
PATH: 1/202

(I added a space in front of --- in order not to mess up anything when
posting this...)

Not sure what could have gone wrong... :-O

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Re: Re: Long lines in QWK packets
By: Zip to alterego on Sun Aug 16 2020 10:39 am

Really strange -- I managed to fetch the ZIP file (00000066.sa0) from my recycle bin and the PKT file inside it contained (output from 'strings' command here):

If you did a hexdump -C (or od -a) does it show the nulls in the middle of the packet?

--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden

Yeah, no FTN address in your origin line...

Might have to put it down to one of those Mystic easter eggs :)

...δεσ∩

... The families of one's friends are always a disappointment.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello alterego!

Thank you for your reply!

On 17 Aug 2020, alterego said the following...

If you did a hexdump -C (or od -a) does it show the nulls in the middle
of the packet?

This is part of what hexdump -C shows (password masked):

00000000 ca 00 64 00 e4 07 07 00 0f 00 0c 00 06 00 2e 00 |..d.............| 00000010 00 00 02 00 01 00 01 00 fe 00 xx xx xx xx xx xx |..........xxxxxx| 00000020 xx 00 15 00 15 00 00 00 00 01 fe 00 01 00 15 00 |x...............| 00000030 15 00 00 00 00 00 00 00 00 00 02 00 ca 00 64 00 |..............d.| 00000040 01 00 01 00 00 01 00 00 31 35 20 41 75 67 20 32 |........15 Aug 2| 00000050 30 20 20 31 32 3a 30 36 3a 33 39 00 57 61 72 70 |0 12:06:39.Warp| 00000060 73 6c 69 64 65 00 5a 69 70 00 4c 6f 6e 67 20 6c |slide.Zip.Long l|

Yeah, no FTN address in your origin line...
Might have to put it down to one of those Mystic easter eggs :)

Seems like this time prealpha really meant prealpha...
I'll see if I can revert to a previous prealpha...

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Hello again alterego!

On 17 Aug 2020, Zip said the following...

Yeah, no FTN address in your origin line...

Seems like this time prealpha really meant prealpha...
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Hopefully that reply contained the FTN address, at least.

The only thing I can think of (except for the prealpha) is that I used the message postponing feature (Save as Draft) of Mystic before actually posting the message.

This reply is also sent using the message postponing feature. Please let me know (and I'll check it locally, too) if this reply has no FTN address in its Origin.

(Sorry for spamming you all, but this sounds like a rather obscure (and serious) bug when it comes to FTN...)

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Hello again Warpslide!

On 15 Aug 2020, Warpslide said the following...

NOW I'm running Aug 11th! ;)

OK, just a final "test", replying to the same message as the first time, to
see if the Origin line contains my FTN address or not. (Not using the Save as Draft feature.)

If everything looks OK this time, then I'm not sure what could have caused this.

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

On 17 Aug 2020, Zip said the following...

OK, just a final "test", replying to the same message as the first time, to see if the Origin line contains my FTN address or not. (Not using the Save as Draft feature.)

If everything looks OK this time, then I'm not sure what could have
caused this.

I seem to remember that happened to me once & I remember resuming a message from my drafts folder. I was never able to re-create it & it hasn't happened again since so I've never looked into it more.

As I recall, I think I was writing up a message in Mystic & got distracted.
I came back to my laptop & noticed I was disconnected. When I logged back
in I was prompted to resume my draft, which I did & that's when it happened.

I could be wrong about that, but I'm sure there's a bug in there just waiting to be found. That was when I was back on A45, so it does seem to be in there in A46 as well.

I'll see if I can look back & find out when that happened to me.

Jay


... Regression: When you fix one bug, you introduce several newer bugs.

--- Mystic BBS v1.12 A46 2020/08/11 (Windows/32)
* Origin: Northern Realms BBS | bbs.nrbbs.net | Binbrook, ON (21:3/110)

Hello Warpslide!

Thank you for your reply!

On 17 Aug 2020, Warpslide said the following...

I seem to remember that happened to me once & I remember resuming a message from my drafts folder. I was never able to re-create it & it hasn't happened again since so I've never looked into it more.

OK! Glad to hear I'm not alone. :)

distracted. I came back to my laptop & noticed I was disconnected. When
I logged back in I was prompted to resume my draft, which I did & that's when it happened.

I vaguely recall restarting MIS and hence getting disconnected, so this
sounds a little bit familiar... Maybe there's something with resuming drafts and what circumstances the editor has been interrupted.

Thanks again!

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Re: Long lines in QWK packets
By: Zip to alterego on Mon Aug 17 2020 03:33 pm

Howdy,

Hopefully that reply contained the FTN address, at least.

Yup, this message and that one had an FTN address in it...

...δεσ∩

... Homosexuality must be hereditory -- most gays have heterosexual parents. --- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)