|
@@ -1,6 +1,11 @@
|
1
|
1
|
# Oragono Information
|
2
|
2
|
|
3
|
|
-Here's a bunch of misc info the Oragono server!
|
|
3
|
+Here's a bunch of misc info about the Oragono server! This can include questions, plans on
|
|
4
|
+how I'm going forward, how to properly use features, or why Oragono does/doesn't do
|
|
5
|
+something.
|
|
6
|
+
|
|
7
|
+Essentially, this document acts as a braindump about Oragono while we figure out a better
|
|
8
|
+place to put all this information.
|
4
|
9
|
|
5
|
10
|
|
6
|
11
|
## Accounts and Channels
|
|
@@ -20,6 +25,23 @@ legacy interfaces to access these functions. However, it's gonna be a while befo
|
20
|
25
|
this is specified by someone like the IRCv3 WG.
|
21
|
26
|
|
22
|
27
|
|
|
28
|
+## Server-to-Server Linking (or Federation)
|
|
29
|
+
|
|
30
|
+Right now Oragono doesn't support linking multiple servers together. It's certainly planned,
|
|
31
|
+but it's a fair while away.
|
|
32
|
+
|
|
33
|
+When I do add S2S linking to Oragono, I want to use it as a testbed for a new sort of
|
|
34
|
+linking protocol. Mostly, I want a meshy protocol that minimises the effects of netsplits
|
|
35
|
+while still ensuring that messages get delivered, and preserves the AP nature of IRC
|
|
36
|
+reliability (in terms of the CAP theorem), which is something that traditional solutions
|
|
37
|
+based on the Raft protocol don't do.
|
|
38
|
+
|
|
39
|
+Basically, I'm going to continue working on my [DCMI](https://github.com/DanielOaks/dcmi)
|
|
40
|
+protocol, get that to a point where I'm happy with it and _then_ start looking at S2S
|
|
41
|
+linking properly. If anyone is interested in server protocols and wants to look at this with
|
|
42
|
+me, please feel free to reach out!
|
|
43
|
+
|
|
44
|
+
|
23
|
45
|
## Rejected Features
|
24
|
46
|
|
25
|
47
|
'Rejected' sounds harsh, but basically these are features I've decided I'm not gonna
|