Skip to content

NOMERGE Testing alert blockquote support #628

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jwheare wants to merge 1 commit into from
Closed

NOMERGE Testing alert blockquote support #628

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,16 @@ The client protocol is how clients and servers talk to each other. The server-to

Plain and simple, a server's S2S protocol only needs to be understood by that same server software or services software. Even if we wanted to mandate server-to-server implementation details or architecture, servers could disregard these without clients being able to tell in any way (as the server would still expose the same protocol to the client). We don't work on the S2S protocols because they're an implementation detail. So long as those servers expose the client protocol, it's IRC.

> [!NOTE]
> Test
> ```code test
> more code
> again
> ```
> ok then
>
> bye

### Who runs IRCv3?

Originally, we were setup by the Atheme group to develop extensions to the IRC client protocol. These days, the direction of the IRCv3 WG is led by [our contributors]({{site.baseurl}}/charter.html) and the WG Chair.
Expand Down