A library for a decentralised peer-to-peer chat over IPv6 only.
您最多选择25个主题 主题必须以字母或数字开头,可以包含连字符 (-),并且长度不得超过35个字符
Pascal Gloor 2d68cdb118 initial 5 年前
README.md initial 5 年前

README.md

libchat6

About

libchat6 is a complete library that handles an IPv6 only, peer-to-peer, end-to-end encrypted, decentralised, chat client.

Ideas

  • transport is IPv6 only and TLS1.3
  • all clients are identical and no server is needed (some clients might run to act as bootstrap servers but all clients do that aswell.)
  • clients have a built-in bootstrap list of IPv6 addresses. This list gets updated when the client connects to the network. This allows the client to always have a recent list of bootstraping IPs.
  • There’s no central registration site, therefor users just choose a nickhandle and have a private/public key pair (generated by the client). Clients are identified by their public key hash.
  • Friends can be searched by their nickname or public key. If a client changes the nickname without changing the key pair, the friend can still be found using the public key. This process is completely handled by the library and is transparent to the user.
  • The interconnection of clients is handled over other clients. The network builds up and paths between clients are calculated similar as routing protocol for routes.
  • When a client connects to another to join the network, it will publish it’s nickname and implicitly it’s public key.
  • A client may connect to multiple clients, the network of clients will adjust the routing paths according to a metric and select the best path. The metric is the delay in miliseconds on each connection. A regular keepalive query and response is used to measure the delay and the routing information is adjusted accordingly.
  • To avoid dead paths, a relatively short keepalive timeout has to be used.
  • The network does not allow store-and-forward of messages if the friend is offline. For mobile clients, notifications might be integrated to wakup the client.
  • The network only allows users to find other users. All end-to-end communication goes directly. (should we allow relay in case the end-to-end doesn’t work?)
  • … ?