Hello Maurice!

No one seems to be interested in building a new offline packet
system.

I've known that for decades now which is why I built my
own without ANY abandoware and/or obsolete protocols.
That is the main reason I can claim to be the best there
is, and ever was, in all of fidonet, present and past.
The future? I don't expect to live forever.

I am not sure what you've built. You are still connecting with
a host system with binkp, and fetching .PKT files, right?

And then you are doing something with those .PKT files and
storing them in JAM format or something other?
--
../|ug

--- OpenXP 5.0.64
* Origin: (2:221/1.58)

Hey August!

You are still connecting with a host system with binkp, and fetching
.PKT files, right?

Uncompressed .PKT files in order to avoid zip and other such corruption. At present, and past for that matter, this fidonet node has been using binkd for transfers to host nodes out there it requires connecting with.

And then you are doing something with those .PKT files and storing
them in JAM format or something other?

You have the basic idea. However the format is not PKT as all of that is stripped out considering it is utter crap. Same with the first 14 bytes of packed msg's which are also given ye olde heave-ho. Basically it is a stored msg format without any binary data to get in the way of progress. It is 100%, unadultered printable text with a few ascii control codes to facillitate all sorts of compatibilty you can ever dream up, including QWK if that is actually a desirable option, which of course it isn't.

Дуже груви,
Maurice

o- -o o- o- o- o- o- -o -o -o o- o-
/) (\ /) /) /) /) /) (\ (\ (\ /) /)
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... Soþ hit sylf acyþeð.
Truth will make itself known.
--- GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice!

It is 100%, unadultered printable text with a few ascii
control codes to facillitate all sorts of compatibilty you
can ever dream up, including QWK if that is actually a
desirable option, which of course it isn't.

So.. what does the UI for messaginglook like?


--
../|ug

--- OpenXP 5.0.64
* Origin: (2:221/1.58)

Hey August!

So.. what does the UI for messaginglook like?

Not much. For reading I just output to the linux terminal using regular gnu text applications such as 'cat' and 'less' and the such. For posting I am using vim. I was going to do something with ncurses not unlike msged and/or golded but as of yet haven't gotten around to it.

Дуже груви,
Maurice

-o -o -o -o o- o- o- -o o- o- o- o-
(\ (\ (\ (\ /) /) /) (\ /) /) /) /)
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... Ne beo þu no to tælende, ne to tweospræce.
Do not be too quick to disparage, nor too double-tongued.
--- GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice Kinal!

** On Saturday 27.12.25 - 00:02, Maurice Kinal wrote to August Abolins:

Hey August!

So.. what does the UI for messaginglook like?

Not much. For reading I just output to the linux terminal
using regular gnu text applications such as 'cat' and
'less' and the such. For posting I am using vim. I was
going to do something with ncurses not unlike msged and/or
golded but as of yet haven't gotten around to it.

So, basically you list your messages with ls? Are the message
files renamed with subj/from-to/date/subject so that you can
see what they are quickly?

And I suppose you can't display msgid-relationships for
navigating a thread?

References of "which is why I built my own.."
755 26.12.25 Maurice Kinal Are QWK packets still the
+ 973 26.12.25 ÀÄÄAugust Abolins
799 26.12.25 ÀÄÄMaurice Kinal
+ 699 26.12.25 ÀÄÄAugust Abolins which is why I built my own..
1365 26.12.25 ÀÄÄMaurice Kinal
+ 371 26.12.25 ÀÄÄAugust Abolins

805 27.12.25 ÀÄÄMaurice Kinal

+! 788 26.12.25 ÀÄÄAugust Abolins




--
../|ug

--- OpenXP 5.0.64
* Origin: (2:221/1.58)

Hey August!

So, basically you list your messages with ls?

As of this writing, all incoming is dumped into a single file with individual msgs occupying a line. Thus "wc -l" incoming.file will yeild the number of msgs in the file.

Each msg (line) contains five fields; $DateTime\0$To\0$From\0$Subject\0\$Body\n

And I suppose you can't display msgid-relationships for navigating a
thread?

Yes. kludges are part of $Body and are easily be 'grep'ped from that field. They stick out like a sore thumb given the leading '\1' character. However I could easily be convinced to putting kludges into their own field.

Дуже груви,
Maurice

o- -o o- -o -o -o o- o- -o o- o- -o
/) (\ /) (\ (\ (\ /) /) (\ /) /) (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... Se cræft þæs lareowdomes bið cræft ealra cræfta.
The art of teaching is the art of all arts.
--- GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice!

** On Saturday 27.12.25 - 01:04, you wrote:

So, basically you list your messages with ls?

As of this writing, all incoming is dumped into a single
file with individual msgs occupying a line. Thus "wc -l"
incoming.file will yeild the number of msgs in the file.

Each msg (line) contains five fields; $DateTime\0$To\0$From\0$Subject\0\$Body\n

One line per message.. sounds very efficient. +1

And I suppose you can't display msgid-relationships for navigating a
thread?

Yes. kludges are part of $Body and are easily be
'grep'ped from that field. They stick out like a sore
thumb given the leading '\1' character. However I could
easily be convinced to putting kludges into their own
field.

You'd need extra logic to produce a FULL list of threaded/
connected messages. But two at a time isn't too bad.

You should produce a vid illustrating how you do typical reading/searching/replying activities.

--
../|ug

--- OpenXP 5.0.64
* Origin: (2:221/1.58)

Hey August!

One line per message.. sounds very efficient.

For sure. Faster processing as well.

You'd need extra logic to produce a FULL list of threaded/ connected messages.

Like the output of unix-tree?

Дуже груви,
Maurice

-o -o -o -o o- -o o- o- -o -o o- -o
(\ (\ (\ (\ /) (\ /) /) (\ (\ /) (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... Ich habe Eichhörnchen in meiner Hose!
--- GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice!

** On Saturday 27.12.25 - 17:59, you wrote:

You'd need extra logic to produce a FULL list of threaded/
connected messages.

Like the output of unix-tree?

Sounds like your "system" is just a collection of various unix
commands at the cmd-line. How do you mark a message for a
reply later?

Take a look at OpenXP and give it a spin! It's available for
linux as well.


--
../|ug

--- OpenXP 5.0.64
* Origin: (2:221/1.58)

Hey August!

Sounds like your "system" is just a collection of various unix
commands at the cmd-line.

Change cmd-line to bash script and you have it. Also a few additional function files to facillitate the filteration issues. I'd probably do a QWK <-> MSG that way if QWK was a desirable format, which of course it isn't.

How do you mark a message for a reply later?

Use the line number of the msg and use that in a reply vector and then once editted write it to a formatted reply file that can be uploaded to the mothership, "Little Mikey's Brain" in this case. If you see this reply then you have confirmation that it works.

Take a look at OpenXP and give it a spin!

Sure. However if it cannot handle utf-8 msg posting then it won't get very far here.

Дуже груви,
Maurice

-o -o -o -o -o -o -o -o o- o- -o o-
(\ (\ (\ (\ (\ (\ (\ (\ /) /) (\ /)
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... Se forholena cræft and forhyded gold ne bið ællunga ungelice.
Concealed skill and hidden gold are not entirely unalike.
--- GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

On 28 Dec. 2025 01:19, you wrote to August:

Hey August!

Take a look at OpenXP and give it a spin!

Sure. However if it cannot handle utf-8 msg posting then it won't get very far here.

Utf-8 chars seem to "want" to work in the nntp groups, but in my case the limitation is the font set, and DOS terminal in Windows . Maybe the Linux version doesnt have that char restriction.

--- AfterShock/Android 1.7.5
* Origin: Mobile Pixel 3aXL (2:221/1.59)

Hey August!

On Sun, 28 Dec 2025 08:13:42 -0500, you wrote:

Utf-8 chars seem to "want" to work in the nntp groups, but in my case
the limitation is the font set, and DOS terminal in Windows . Maybe the Linux version doesnt have that char restriction.

If you're still referring to OpenXP here, I'm not sure if there has been any more development lately or not (or if there ever will be), but last time I checked, the Linux version still didn't support utf-8.

Winpoint did a little bit better, but still wasn't 100%, and well, it's Windows only, so that's already a huge limitation. I had mentioned a bug in how it handles time and UTC offsets upwards of 1-2 (or more, time flies these days) years ago, got a reply that it would be looked into, and nothing ever came of it.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello Nick!

** On Sunday 28.12.25 - 08:11, you wrote:

If you're still referring to OpenXP here, I'm not sure if
there has been any more development lately or not (or if
there ever will be), but last time I checked, the Linux
version still didn't support utf-8.

The latest one seems to be Feb 2025:

https://sourceforge.net/projects/openxp5/files/OpenXP%205.0/

Winpoint did a little bit better, but still wasn't 100%,
and well, it's Windows only, so that's already a huge
limitation.

It thought Win-anything was going to be my final approach to
this messaging hobby, but I actually grew quite fond of the
text-based OpenXP.

I had mentioned a bug in how it handles time and UTC
offsets upwards of 1-2 (or more, time flies these days)
years ago, got a reply that it would be looked into, and
nothing ever came of it.

I recall something re a time issue. But was there an
acknowledgement? ..or just an excuse?

What's the big deal with UTF-8 in FTN anyway? Do we need utf-8
emojiis in these messages?

As-is, my font [Lucinda console] & charset supports French,
Spanish, Norwegian, and few others.
--
../|ug

--- OpenXP 5.0.64
* Origin: (2:221/1.58)