Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/no0dles/pigeon-project
An open and secure message protocol
https://github.com/no0dles/pigeon-project
Last synced: 25 days ago
JSON representation
An open and secure message protocol
- Host: GitHub
- URL: https://github.com/no0dles/pigeon-project
- Owner: no0dles
- License: other
- Created: 2015-11-25T15:12:05.000Z (about 9 years ago)
- Default Branch: master
- Last Pushed: 2015-11-25T16:49:23.000Z (about 9 years ago)
- Last Synced: 2024-04-28T04:42:30.778Z (9 months ago)
- Size: 6.84 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# Project Pigeon
## Project summary
The idea of project Pigeon is to develop an open and secure message protocol. One of the main objectives is to provide end to end encryption on any communication in a easy way to use for everyone.## Objectives
**End to end encryption**
Any communication is encrypted with your personal key which never leaves the users device.**High encryption requirements**
The protocol should force the user to use secure standards on the transport and message encryption.**Easy to use for everyone**
Any user without any understandig of encryption should be able to use it and never come in a situation where hisprivacy is compromised.**Expose as less information as possible to third parties**
The protcol uses a server client architecure and because of this there will be communication meta data which has to be revealed to third parties. These meta data should contain as less information as possible and never reaveal any information about the sender, the receiver or relate them in any way.**Prevent spam**
Any user should be able to decide what messages he wants to receive. To prevent any unwanted messages there is the possiblity to manage a whitelist on server side and a blacklist on client side.**Extendable for everbody's needs**
Any application can use the protocol and build something on top of it.**Decentralized**
The protocol should work decentralized even with the server client architecure. Every user is in control of which server handles his messages and there is never a required centralized communication.## Introduction
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua.At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.
Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet,
## Docs
**Message Server:**
Read about more the concept of the message server and how all messages are handled in pigeon [here](./docs/MessageServer.md).--
**Directory Server:**
Read more about the conecpt of the directory server and how you exchange your contact information with others [here](./docs/RegistryServer.md).--
**Chat Server:**
Read more about the conecpt of the chat server and how a chat works on top of the message server [here](./docs/ChatServer.md).## Collaborators
no0dles## License
MIT, see the [LICENSE](./LICENSE.txt) file