Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement message network framework #49

Closed
NuSkooler opened this issue Jan 23, 2016 · 2 comments
Closed

Implement message network framework #49

NuSkooler opened this issue Jan 23, 2016 · 2 comments
Assignees
Milestone

Comments

@NuSkooler
Copy link
Owner

A message network framework needs implemented. This will allow for various networks (e.g. FidoNet/FTN, QWK based, etc.) to integrate & import/export with the system. I have a design I'm working on for this. This bug is for tracking / relating existing issues.

Some general notes on what's coming:

  • The system will be "layered" allowing different import/export processors (e.g. tossers/etc.) to exist in an abstract way.
    • Conferences are being introduced. These are simply organizational groups of message areas
    • All area_name stuff in DB/code is being renamed to area_tag
    • A new configuration structure for conferences, areas, and message network mappings will be introduced (e.g. for config.hjson)
    • Initial proof of concept will be FTN processing. Next will very likely be QWK.

Current design for menu.hjson message areas & conferences is something like such:

conferences: {
    agn: {
        name: Agoranet
        desc: The Official Network of ACiD Productions

        //  simple ACS for access
        acs: THEACSSTRING

        areas: {
            agn_bbs: {
                name: BBS Discussion
                desc: General BBS discussion

                //  ACS for what users can do here
                acs: {
                    read: THEACSSTRING
                    write: THEACSSTRING
                    manage: THEACSSTRING
                }
                default: true
            }
        }
    }
}
@NuSkooler
Copy link
Owner Author

For anyone interested, this is being worked on in the msg_network branch

@NuSkooler
Copy link
Owner Author

The msg_network branch has been merged to master @ 6f8f8f7

There are likely bugs of course. Those will be separate issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant