General text trimming#4
Conversation
|
|
||
| ### Uplink | ||
|
|
||
| Uplink is the IRC layer of an Orbit deployment - an adopted role, not software Orbit builds. Uplink is any stock IRCv3 server; [Ergo](https://ergo.chat/) is the reference implementation, run with no Orbit-specific patches. All persistent communication - messages, channel membership, message history, user identity - flows through Uplink. It is a standard IRCv3 server: no Orbit-specific plugins, no knowledge of Satellite or Depot at the protocol level. Orbit clients and plain IRC clients connect identically. There is no Uplink fork; Orbit runs the server stock and conforms to IRCv3, supporting whatever stock Ergo implements. |
There was a problem hiding this comment.
This is a fairly important line that it's dropping. I'd at least keep the fact that Orbit and normal IRC clients live alongside each other.
| ## What IRC Clients Can Do That Orbit Clients Do | ||
|
|
||
| Everything IRC does well: text chat, channel modes, SASL auth, DMs, bots, ZNC/bouncer support, scripting. An IRC client connecting to Uplink is a first-class participant in the text layer. The spec does not treat IRC clients as second-class. | ||
|
|
There was a problem hiding this comment.
Why would we drop this section? It's fairly important to state the limitations between the clients and make it clear which capabilities are still shared, making existing IRC clients lightweight Orbit clients by default.
zealsprince
left a comment
There was a problem hiding this comment.
Have a few notes for now - otherwise I'm fine with slimming down and trimming line-ending fluff. I was doing a lot of it as opinionated statements trying to drive points home but in your diff I'm realizing I'm doing it more than I remembered.
As I read the document, I change, trim or edit sections which I think should be simplified. However I think that not all edits I do might be beneficial and could be done better. Treat this PR as a suggestion then. Edits and comments are more than welcome!