Because I'm a stubborn git who insists on using BlueWave, I can't view pipe color codes in messages I download via QWK properly.

Is this something I can pester my SysOp about, or could a future Mystic update allow users to choose how color codes are handled in QWK packets?

Because there's bound to be at least two of us using QWK out there.


... This tagline is made just for All
___ Blue Wave/386 v2.30

--- Mystic BBS/QWK v1.12 A43 2019/03/03 (Windows/32)
* Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)

Because I'm a stubborn git who insists on using BlueWave, I can't
view pipe color codes in messages I download via QWK properly.

Is this something I can pester my SysOp about, or could a future
Mystic update allow users to choose how color codes are handled in
QWK packets?

I think those pipe codes are there for your reader to display if it
supports that style of color codes. I don't know of a reader off hand
that does.

Not all BBSs support pipe codes either, MagickaBBS doesn't. I see lots of
|'s and digits.. :)

Pipe codes are used in Mystic, renagade and Synchronet if pipe code
support is toggled on but they are not universal.

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

I think those pipe codes are there for your reader to display if it supports that style of color codes. I don't know of a reader off hand
that does.

Not all BBSs support pipe codes either, MagickaBBS doesn't. I see lots of |'s and digits.. :)

g00r00 - feature request :) Can we have a flag to strip pipes out of messages as well? Perhaps through the qwk menu but also based on exporting to/from certain BBSes?

--- Mystic BBS v1.12 A44 2020/01/16 (Linux/64)
* Origin: monterey bbs (21:1/168)

I think those pipe codes are there for your reader to display
if it supports that style of color codes. I don't know of a
reader off hand that does.

Not all BBSs support pipe codes either, MagickaBBS doesn't. I
see lots of |'s and digits.. :)

Actually Magicka does :) but you have to enable it in your settings.
It's not very good in v0.13, but I greatly improved it yesterday int he
v0.14 branch.

Andrew

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)

I think those pipe codes are there for your reader to display
if it supports that style of color codes. I don't know of a
reader off hand that does.

Not all BBSs support pipe codes either, MagickaBBS doesn't. I
see lots of |'s and digits.. :)

Actually Magicka does :) but you have to enable it in your
settings. It's not very good in v0.13, but I greatly improved it
yesterday int he v0.14 branch.

Sorry ryan, I meant to address that to Al :)

Andrew

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)

g00r00 - feature request :) Can we have a flag to strip pipes out
of messages as well? Perhaps through the qwk menu but also based on exporting to/from certain BBSes?

Magicka displays messages with ansi just fine, and that's the case with MultiMail too. I'm not sure of the situation with offline readers
generaly.

If someone wanted to be sure the colors they use in messages shows up as expected ansi could be used.

Even then it's still not universal, but that's likely the best we can do.



Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Actually Magicka does :) but you have to enable it in your
settings. It's not very good in v0.13, but I greatly improved it
yesterday int he v0.14 branch.

Yep, I thought it did at one time. I have a v0.14 in the works so I'll
look into that.

I've always been on the fence about that since it can mess up the display
of a file that had pipe codes in it without trying to be colourful.

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

If someone wanted to be sure the colors they use in messages shows up as expected ansi could be used.

Daydream has a strippipes() function which is used on all mail during export. Daydream is very far from perfect (which is why I gave up on it hehe) but I always thought this one thing was the right call - let's not make assumptions about how mail will be consumed. We have ANSI enabled bases that expect ANSI codes, but other than that I never felt that multicolored text belonged in messages traversing FTN networks.

--- Mystic BBS v1.12 A44 2020/01/16 (Linux/64)
* Origin: monterey bbs (21:1/168)

Because I'm a stubborn git who insists on using BlueWave, I can't view pipe color codes in messages I download via QWK properly.

Is this something I can pester my SysOp about, or could a future Mystic update allow users to choose how color codes are handled in QWK packets?

Because there's bound to be at least two of us using QWK out there.

Unfortunately at the moment I don't think there is no option to strip color codes from QWK packets.

But I hear you and I think thats a good option to add. I'll put that on the TODO list and it shouldn't be too difficult to do so I can probably get that
in soon-ish (A45).

--- Mystic BBS v1.12 A44 2020/01/29 (Linux/64)
* Origin: Sector 7 (21:1/108)

g00r00 - feature request :) Can we have a flag to strip pipes out of messages as well? Perhaps through the qwk menu but also based on
exporting to/from certain BBSes?

Yep yep! On the todo list! :)

I don't want to do it in A44. Really I am just waiting to see if anything blows up with Avon running the latest Mystic updates before A44 is out
though, so it probably won't be too long.

--- Mystic BBS v1.12 A44 2020/01/29 (Linux/64)
* Origin: Sector 7 (21:1/108)

Daydream has a strippipes() function which is used on all mail
during export. Daydream is very far from perfect (which is why I
gave up on it hehe) but I always thought this one thing was the
right call - let's not make assumptions about how mail will be
consumed. We have ANSI enabled bases that expect ANSI codes, but
other than that I never felt that multicolored text belonged in
messages traversing FTN networks.

If you were developing software you were likely the recipient of comments
folks made about pipe codes in messages. At one time using pipe codes and coloring messages made you a renegade underground elitist. :)

There are good arguments for leaving color codes out of messages since
there is no universal method to decode them. They look fine in some
interfaces and in others it looks like the neighbors dog visited
overnight.

I use golded a lot to read and reply to messages also and in that case
both ansi and pipe codes (as well as <CTRL>A or heart codes) look
terrible but I know that is just in that interface.

I never get too sussed about it either way since it's just folks
expressing their creativity a bit and I think that's a good thing.

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

ryan wrote to Al <=-

If someone wanted to be sure the colors they use in messages shows up as expected ansi could be used.

Daydream has a strippipes() function which is used on all mail
during export. Daydream is very far from perfect (which is why I
gave up on it hehe) but I always thought this one thing was the
right call - let's not make assumptions about how mail will be
consumed. We have ANSI enabled bases that expect ANSI codes, but
other than that I never felt that multicolored text belonged in
messages traversing FTN networks.

I strongly agree with this post. Leave the colors/codes/pipes out
of regular FTN message areas.



... So... So you think you can tell.
=== MultiMail/Linux v0.52
--- SBBSecho 3.10-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)