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.
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?
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?
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.
805 27.12.25 ÀÄÄMaurice Kinal+! 788 26.12.25 ÀÄÄAugust Abolins
So, basically you list your messages with ls?
And I suppose you can't display msgid-relationships for navigating a
thread?
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.
One line per message.. sounds very efficient.
You'd need extra logic to produce a FULL list of threaded/ connected messages.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 51 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 11:46:09 |
| Calls: | 727 |
| Files: | 1,214 |
| Messages: | 208,407 |