zentus / snacc Goto Github PK

Messages are not stored on server. Instead they are relayed directly to all connected clients.

Current Vision

• Open Source
• Minimal with essential features
• Secure
• Quick setup
• Runnable with zero config
• Runnable as a binary executable
• Modular
• Functional
• Test driven

Future Vision

• Scalability
• Load balancing
• Clustering
• Performance

Should be done

• Add user level server side config implementation
• Add support for multiline messages
• Test certificate via ENV. Add CLI flags for setting certificate paths
• Add a command interpreter. Interprets a message prefixed with a character (default: /) as a command. Send server commands to server in a command event. If server is not needed for command, use a separate implementation that takes care of client side commands.
• Add non-rawmode fallback client
• Write README

Is in development

• Add CLI commands for setting and getting config properties. Store client config in ${HOME}/.snacc
  • snacc config set prompt_character "$"
  • snacc config get prompt_character]
• Add client side config
• Add endpoints for registry and login. Use JWT authentication. Store user data encrypted in JSON files.

Has been done

• Validate nickname on client and server
• Show timestamp for notification event messages
• Don't use the system nickname. Add an option for sending notification event messages instead
• Fix unclean exit bug
• Use ESLint, extending Standard config