If there is one thing you'd like to see done before anything else feel free to let me know here. I am undecided on what I prioritize first so
On 12/03/17, g00r00 pondered and said...
If there is one thing you'd like to see done before anything else fee free to let me know here. I am undecided on what I prioritize first
A)
B)
Now that the "basics" are done for MIS, I am able to work on more things >(including things to make MIS or any of the servers better).
If there is one thing you'd like to see done before anything else feel free >to let me know here. I am undecided on what I prioritize first so I've
just been randomly doing little things here and there.
--- Mystic BBS v1.12 A36 2017/12/01 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
Now that the "basics" are done for MIS, I am able to work on more things >(including things to make MIS or any of the servers better).
If there is one thing you'd like to see done before anything else feel free >to let me know here. I am undecided on what I prioritize first so I've
just been randomly doing little things here and there.
--- Mystic BBS v1.12 A36 2017/12/01 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
If there is one thing you'd like to see done before anything else feel free to let me know here. I am undecided on what I prioritize first so I've just been randomly doing little things here and there.
Let's say Mystic could retain and display some on the fly stats about
each echo node that is set up.
1) Ability to pull a report of inactive nodes. Sysop to set threshold for days inactive to the be basis of the report. That could be generated as
a txt file and then MUTIL could post it to echo area / BBS email, etc.
I'd better stop now :)
I'd also suggest you release A36 ... there's a lot of change in there already so it would be good to get it out the door and then I can start updating videos etc. :)
Do you see a need for historical reporting?
If there is one thing you'd like to see done before anything else feel free to let me know here. I am undecided on what I prioritize first so I've just been randomly doing little things here and there.
Just think, if prealphas hadn't started, right now we'd be somewhere around A95! ;)
A)
I sort of expected these would be your requests since we've already
talked about this and how I planned to do it. At least some of them - I have a lot more that I didn't mention! It is higher up on the list
B)The thing for discussion is how we track files. Do we just track the number of files BINKP sends or receives (which is how its designed to
work now), or do we try to break that down more? I don't want to make
it too convoluted...
Now that the "basics" are done for MIS, I am able to work on more things (including things to make MIS or any of the servers better).
If there is one thing you'd like to see done before anything else feel free to let me know here. I am undecided on what I prioritize first so I've just been randomly doing little things here and there.
We still checking into the issue I posted previously about SSH and dropping the caller mid menu draw? =)
For example, when messages were written and imported (static), and on the other side of the coin the TI MCI code could be used on say the full screen message editor and actually show real time with seconds incrementing.
Let's say Mystic could retain and display some on the fly stats about each echo node that is set up.
Agreed.
This one is huge. Also, to alleviate a lot of manual intervention, a threshold setting for say if there has been no connection (in or out)
made with a node in 14 days, put everything on hold for them rather than crash (to stop the connection attempts 100s of times per day), 30 days
One more while it's still fresh in my head.. ;)
The ability to copy/paste menu options to a completely different menu would be helpful when trying to organize and move stuff around.
But I suppose if its optional it wouldn't hurt even if it did slow things down.
As far as dates in general, I plan to revamp dates across the board at some point soon (ish) to include 4 year input for date input and to (probably) change the format to be "26 Dec 2017". I can't stand the 11/11/11 formatted dates - I have to think too much about what I'm
looking at when I see it.
As far as the editor wonkiness, my brain is so tired right now that I can't really follow. If there is any way you can reproduce anything consistantly that would be the most helpful. If not though we can
figure it out.
There are some weird wrapping behaviors at times, but its not text
getting completely lost... Thats absolutely a bad thing that I haven't experienced outside of cutting and pasting bug that I recently fixed.
Anyay, I am rambling. I gotta get to sleep this is super late for me.
I have a system drawn up and even some code going for a group system
that has an ACS-like enforcement for downlinks. Hopefully it turns out nice - its something I want to work on soon.
Someone else was asking for that too. I'll put it on the list. I do remember looking into it, and I think I determined it was more difficult than expected. But I think its a good idea, and I myself have been at
the point where I was annoyed I couldn't copy between menus.
If there is one thing you'd like to see done before anything else feel free to let me know here. I am undecided on what I prioritize first so I've just been randomly doing little things here and there.
I would love to see some functionality similar to JAMNNTPD ported
into Mystic's NNTP server.
JAMNNTPD works fine and I have a few users that make good use of it, but still is a separated server that needs to be maintained, and if I could use Mystic's integrated NNTP server it would be awesome.
What exactly do you mean? What specifically do you think the NNTP server needs that JAMNNTP does?
B)When I made the echomail nodes configuration I did anticipate some echomail reporting and automated features so there is already some of
what you're asking in place. I'll probably need to make some data
changes based on your suggestions:
Files imported (should this be hatched files? bundles, unknown
files?) Files exported (just hatched files or bundles too?)
Unknown files received?
The thing for discussion is how we track files. Do we just track the number of files BINKP sends or receives (which is how its designed to
work now), or do we try to break that down more? I don't want to make
it too convoluted...
What I think it does now is tracks the BINKP files sent and receives,
and then we can add in the number of files tossed into FDN or hatched
from FDN. Tracking the number of bundles specifically might not be that useful, since we're tracking the messages exported and imported per node already. What do you think?
A potential downside with the current way it tracks this stuff is that there is no historical data. Once you reset the stats of a node at whatever interval you decide, you lose the previous data...
Maybe it'd be better to keep historical data for a month or a year on a node or something, but when I start doing stuff like this it could
effect the tossing and exporting times significantly, not sure yet.
Do you see a need for historical reporting?
Currently there is a template for the Indexed Reader (at the group/area browsing level) but when you are listing messages within an area, these
is no way (that I know of, I may have skipped something tho) to specify
a different template when calling the full-screen message reader (MR if
I remember correctly).
is no way (that I know of, I may have skipped something tho) to speci
The templates are definable per-area in the message base editor:
"ansimrd" and "ansimlst" are the defaults. Unfortunately these are the old-style templates from the 1990s not the ones that use .ini files to
go along with the ANSI...
This means you can change the look of the reader right down to each message base, but the prompts are not specific to each template like
they are in the newer template system (instead they exist in the theme prompts). In order to set the prompts specific to each message base (to match the templates) you'd have to do something with setprompt in MPY or MPL before reading that base.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 204:02:37 |
Calls: | 2,083 |
Calls today: | 1 |
Files: | 11,139 |
Messages: | 948,027 |