I haven't done a data file format update in a long time to be able to
add in OS-specific event configurations like the archive and protocols have but that is something I might do.
This makes sense. Yeah, I can see the difficulty in maintaining software for separate architectures. At the end of the day, it's probably just "on us" to figure a lot of this stuff out, particularly the linux users. That said, I'm happy to make Mystic wiki edits or docs edits, is there a place to submit changes? How do I get a wiki account? :)
4 - When creating new message bases, configuring them to be echomail bases, assigning my local address, and then assigning a node for expo the export node doesn't save a lot of the time. I have to go back and
I just did a few tests and they all worked, but I made a note of it and will try some more. If there is something you can reproduce every time that would be helpful. This is specifically when adding the export from the message base editor?
It's odd. If you create a base from scratch in the UI and assign all the details for an echomail base on creation, to include uniquely naming everything, assigning it as an echomail base (with your node), and then also selecting your HUB, saving/closing out, and then later go back in and check
on it, you may notice the HUB portion is gone. I may be able to do a reproduction of it and take a video (more to follow).
Thanks!
--- Mystic BBS v1.12 A36 2017/12/03 (Linux/32)
* Origin: lo fidelity bbs (21:2/142)