I've not looked into this recently, does it support JAM yet? I'm
looking for something to switch from IREX and gecho/fastecho.
I've not looked into this recently, does it support JAM yet? I'm looking f something to switch from IREX and gecho/fastecho.
The code to support JAM is about 90% complete but needs extensive testing before I'm confident to release it.
It is an unbelievable huge royal pain to add Just Another Mess.
The code to support JAM is about 90% complete but needs extensive
testing before I'm confident to release it.
It is an unbelievable huge royal pain to add Just Another Mess.
So why do it? Probably no-one will ever use it...
So why do it? Probably no-one will ever use it...
It appears there is interest in the BBS community; otherwise the question
would not have been asked. I know that I wouldn't mind testing it as a means
of avoiding the known bugs in FastEcho that probably will never be fixed.
The code to support JAM is about 90% complete but needs extensive testing before I'm confident to release it.
The code to support JAM is about 90% complete but needs extensive testing before I'm confident to release it.
Finally I found someone that can add it into RG as well. hahahahah
It is an unbelievable huge royal pain to add Just Another Mess.
So why do it? Probably no-one will ever use it...
Finally I found someone that can add it into RG as well. hahahahah
I can almost guarantee that will never happen,
I must be very careful what I say because there are at least two Professors who may chime-in and ask me why I just don't use an API or library unit to
Finally I found someone that can add it into RG as well. hahahahah
I can almost guarantee that will never happen,
Are you sure?!? ;)
I must be very careful what I say because there are at least two Professors who may chime-in and ask me why I just don't use an API or library unit to
Just 2? ;)
Just 2? ;)
Maybe three but he hasn't farted here yet.
As sure as I am that someone will need to completely gut the RG code to red personal mail, purging/packing bases, editing/changing a message... etc.
As sure as I am that someone will need to completely gut the RG code to red personal mail, purging/packing bases, editing/changing a message... etc.
That's like 10 minutes worth of work. :)
Andrew,
So why do it? Probably no-one will ever use it...
It appears there is interest in the BBS community; otherwise the question
would not have been asked. I know that I wouldn't mind testing it as a means
of avoiding the known bugs in FastEcho that probably will never be fixed.
My view on this ... such message-bases came into existence in the days of limited disc-space to save space.
Those days are gone and while *.msg generates overhead ... who cares ... ?
I never understood why anyone want a storage system which could collapse and make'm lose the entire message base instead of just 1 or 2 messages...
Get cracking then, super hacker!
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 92 |
Nodes: | 16 (0 / 16) |
Uptime: | 02:19:13 |
Calls: | 6,588 |
Calls today: | 1 |
Files: | 8,482 |
D/L today: |
161 files (74,874K bytes) |
Messages: | 359,625 |