Added communication protocol.
This commit is contained in:
parent
c730af2bcf
commit
514190e5af
2 changed files with 21 additions and 1 deletions
16
Communication Protocol.md
Normal file
16
Communication Protocol.md
Normal file
|
@ -0,0 +1,16 @@
|
|||
# Communication protocol for the better world
|
||||
|
||||
The old system is based on lies and oppression so it's important to develop a communication protocol to empower and protect all the beings.
|
||||
|
||||
## Features required
|
||||
|
||||
* Decentralization - anyone should be able to create an account and find fellow friendly beings to talk with.
|
||||
* State-of-the-art end-to-end encryption - oppressors may want to interfere with the flow of communication or get access to the chat history. It's important to make this task as difficult as possible.
|
||||
* Full Unicode support - this is the de facto standard right now.
|
||||
* Support for multi-room chats and different devices - it is common for one to have a laptop, tablet, smartphone... Synchronization of chat history is a must.
|
||||
|
||||
## Implementation plan
|
||||
|
||||
Right now there are 2 protocols that are close to this vision: [Matrix](https://matrix.org/) and [Tox](https://tox.chat/). However, Matrix suffers from the oppression of DNS, ICANN and difficult development team while Tox is way too privacy-oriented to the point of hurting usability.
|
||||
|
||||
We need a middle group. Forking the Matrix protocol seems to be the best idea. Plus, while we free ourselves from the chains of compatibility, we can develop both client and server written in efficient native language. No more baggage of JavaScript for Element and Python for Synapse. We can do better. Much better.
|
|
@ -1,6 +1,6 @@
|
|||
# Implementation plan for ActivityOS
|
||||
|
||||
## Start by forking [GNOME Shell](https://en.wikipedia.org/wiki/GNOME_Shell)
|
||||
## Native version - start by forking [GNOME Shell](https://en.wikipedia.org/wiki/GNOME_Shell)
|
||||
|
||||
It already has the Activities button so it makes a perfect candidate for a fork.
|
||||
|
||||
|
@ -8,6 +8,10 @@ GNOME Files (also known as Nautilus) needs to have an ability to add Linux VFS d
|
|||
|
||||
Once tagged libraries are implemented, it's all about adding a proper UI to create and manage activities.
|
||||
|
||||
## Web version - implement using [WebAssembly System Interface](https://wasi.dev/)
|
||||
|
||||
People already have web browsers installed on their computing devices. We can ease the migration to ActivityOS by offering it as an app on the Web.
|
||||
|
||||
### Lazy tags
|
||||
|
||||
Some automatic tags are too expensive to compute every time the file is changed. Hence, it makes sense to store a flag on file modification that tag value has to be freshly computed next time it is queried. Then there can be a command similar to [`sync`](https://linux.die.net/man/8/sync) to force recomputation of all lazy tags.
|
||||
|
|
Loading…
Reference in a new issue