indymedia
/
epicyon
mirror of https://gitlab.com/bashrc2/epicyon
7
4
Fork 1
Code Issues 14 Releases Wiki Activity

Multi user

merge-requests/30/head
Bob Mottram 2021-06-28 21:14:01 +01:00
parent aaa0be4d54
commit 31fa93c655
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README_architecture.md
View File

@ -2,6 +2,16 @@
## Design Constrains ## Design Constrains
### Open Standards Compliance
Follow the standards for HTML, CSS and ActivityPub. Especially with ActivityPub there is always some room for interpreatation, so if in doubt about a protocol implementation detail then do whatever Mastodon does to maintain maximum compatibility.
### Multi-User
It is assumed that an instance may have multiple users, although the maximum number of users is not expected to be very high. This system is for a "family and friends" or small club type of scenario.
Although it can be single user, this is not strictly a single user system.
### Anti-scale Principle ### Anti-scale Principle
In general, methods have been preferred which do not vertically scale. This includes the decision not to use a database, and the way that the inbox is processed. Lack of scalability also simplifies the design. In general, methods have been preferred which do not vertically scale. This includes the decision not to use a database, and the way that the inbox is processed. Lack of scalability also simplifies the design.