schimeltuer144/Sekura
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Sekura Secure chat
8 commits 1 branch 0 tags 52 KiB
Find a file
Exact
schimeltuer144 ab61a72572 CONTRIBUTING.md aktualisiert
2025-10-29 00:51:06 +01:00
CODE_OF_CONDUCT.md CODE_OF_CONDUCT.md hinzugefügt 2025-10-29 00:48:27 +01:00
CONTRIBUTING.md CONTRIBUTING.md aktualisiert 2025-10-29 00:51:06 +01:00
LICENSE LICENSE hinzugefügt 2025-10-29 00:40:45 +01:00
README.md README.md aktualisiert 2025-10-29 00:42:41 +01:00
specifications.md copied specifications 2025-10-29 00:31:13 +01:00

README.md

Sekura

Sekura is a secure, federated chat platform inspired by Discord. It combines a centralized identity service with federated community servers and supports end-to-end encrypted direct messaging.

Note: Sekura is currently in early development. Many features are incomplete, unstable, or still under design. This repository is primarily for discussion, prototyping, and community feedback.

Table of Contents

  1. Project Status
  2. Features (Planned / Partial)
  3. Architecture
  4. Direct Messages (DMs)
  5. Contributing
  6. License
  7. Contact

Project Status

  • Early prototype stage; many modules are placeholders
  • SAS (account service) skeleton mostly defined, minimal implementation
  • SN (federated node) partially sketched, not fully functional
  • DM relay and E2EE system currently in design, not implemented
  • API and client interfaces are conceptual
  • Active architecture and security planning ongoing

This project is not ready for production use. It is meant for exploration, discussion, and design iteration.

Features (Planned / Partial)

  • Centralized Identity Service (SAS)
  • Federated servers (SN)
  • Token-based authentication and authorization
  • End-to-end encrypted direct messages (E2EE)
  • Offline support for DMs
  • Privacy-first design with minimal personal data retention
  • TLS 1.3 with mTLS for federation communication
  • Extensible client support (web, desktop, mobile)

Architecture

Sekura consists of three main components:

  1. Sekura Account Service (SAS) – centralized identity authority and DM relay
  2. Sekura Nodes (SN) – federated community servers
  3. Clients – user applications handling authentication, communication, and encryption

The system is designed to ensure privacy, security, and federated scalability.

Direct Messages (DMs)

  • DMs are planned to be client-side encrypted (E2EE)
  • SAS will store only encrypted messages and metadata
  • Messages will support offline delivery
  • Double Ratchet protocol proposed for secure session management

Note: The DM system is not yet implemented.

Contributing

We welcome contributions! Early contributions can include:

  • Prototyping SAS/SN functionality
  • Developing client mockups
  • Security and protocol feedback
  • Documentation and design refinements

Guidelines:

  1. Fork the repository
  2. Create a branch for your work
  3. Commit and push changes
  4. Submit a Pull Request

Please review the Code of Conduct and Contribution Guidelines.

License

Sekura is licensed under GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later).

  • All modifications deployed as network services must be open-sourced
  • Users are free to run, modify, and share Sekura
  • See the LICENSE file for full terms