Skip to content

Update servers.json #25

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

Open
Duhanins wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update servers.json #25

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
8 changes: 4 additions & 4 deletions servers.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,10 +59,10 @@
"icon": "server-icons/ptirc-irc-network.png"
},
{
"name": "mIRCClub",
"description": "We are more than just a server.",
"wss": "wss://irc.mirc.club:8000/",
"ircs": "ircs://irc.mirc.club:6697",
"name": "RusChat",
"description": "Русскоязычная IRC сеть",
"wss": "wss://irc.ruschat.net:443/",

@coderabbitai coderabbitai Bot Jul 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🩺 Stability & Availability | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Files matching servers.json:\n'
fd -a 'servers\.json$' . || true

printf '\nGit info:\n'
git rev-parse --show-toplevel 2>/dev/null || true
git status --short 2>/dev/null || true

if [ -f servers.json ]; then
  printf '\nservers.json line 64 context:\n'
  sed -n '54,70p' servers.json | nl -ba -v54
fi

printf '\nSearch for ruschat/timeout/changed-server validation:\n'
rg -n "irc\.ruschat\.net|RusChat|ruschat|TimeoutError|changed-server|connectivity|validation|changed server" . --glob '!node_modules/**' --glob '!dist/**' --glob '!build/**' || true

Repository: obbyworld/server-list

Length of output: 322

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'servers.json line 64 context:\n'
sed -n '54,70p' servers.json | awk '{print NR+53 "\t" $0}'

printf '\nSearch for ruschat/timeout/changed-server validation:\n'
rg -n "irc\.ruschat\.net|RusChat|ruschat|TimeoutError|changed-server|connectivity|validation|changed server" . --glob '!node_modules/**' --glob '!dist/**' --glob '!build/**' || true

Repository: obbyworld/server-list

Length of output: 1873

🏁 Script executed:

#!/bin/bash
set -euo pipefail

python3 - <<'PY'
import json
path='servers.json'
with open(path) as f:
    data=json.load(f)
for idx, entry in enumerate(data, start=1):
    if entry.get('name') == 'RusChat':
        for key in ['wss','ircs']:
            print(f'{key}: {entry.get(key)!r}')
PY

sed -n '400,470p' scripts/probe.py

Repository: obbyworld/server-list

Length of output: 3417

🌐 Web query:

RusChat IRC wss://irc.ruschat.net:443 WebSocket endpoint

💡 Result:

There is no public, authoritative evidence that irc.ruschat.net operates a native WebSocket (wss://) endpoint [1][2]. While modern IRC server software (such as UnrealIRCd [3] or ElixIRCd [4]) and IRC gateways (such as kiwiirc/webircgateway [5]) are capable of supporting WebSocket connections, they typically require specific server-side configuration to listen on custom ports or utilize reverse proxies to handle the WebSocket traffic on port 443 [3][5][6]. If you are attempting to connect to an IRC network via a web client: 1. Native WebSocket support is an optional extension that must be explicitly enabled by the network administrators [3][7]. 2. Many IRC networks use dedicated web-based gateways (which act as a proxy between the browser and the IRC server) to enable connection, rather than the IRC server itself listening for WebSocket connections directly [5]. 3. For networks that do not support WebSocket connections natively, you would typically need to use a middleware gateway (like KiwiIRC's webircgateway) to bridge the WebSocket connection to the network's standard TCP IRC port [5]. Without official documentation or a server capability announcement indicating that irc.ruschat.net supports the IRCv3 WebSocket extension [7], it is likely that the endpoint wss://irc.ruschat.net:443 does not exist or will not function as an IRC entry point.

Citations:

🌐 Web query:

site:irc.ruschat.net wss websocket

💡 Result:

I couldn’t find any indexed pages on irc.ruschat.net mentioning WebSocket/WSS.

wss:// is the secure WebSocket scheme, and IRC servers need explicit WebSocket support to accept WebSocket clients. So if irc.ruschat.net supports it, there’s likely a separate ws/wss endpoint rather than the raw IRC host. [1][2]

[1] WebSocket scheme (ws/wss) docs: https://en.wikipedia.org/wiki/WebSocket
[2] IRC server WebSocket support note: https://docs.inspircd.org/4/modules/websocket/

🌐 Web query:

irc.ruschat.net wss://irc.ruschat.net:443

💡 Result:

RusChat is a Russian-language IRC network, accessible via the server address irc.ruschat.net [1][2]. Regarding the specific connection details you provided: 1. irc.ruschat.net: This is the primary server address for the RusChat IRC network [3][4]. The network supports standard IRC connections, typically via port 6667 (plain) and port 6697 (SSL/TLS) [4]. 2. wss://irc.ruschat.net:443: While the RusChat network offers various connection options, standard IRC servers often use different ports for specific protocols (like SSL on 6697) [4]. The use of "wss://" (WebSocket Secure) specifically refers to a WebSocket gateway, which allows browser-based IRC clients to connect to the network [5]. While some IRC networks provide WebSocket support on ports like 443 to bypass firewalls [6], this is typically configured as a web-based gateway rather than a direct IRC server port. If you are attempting to connect via a web-based IRC client, ensure that the client supports WebSocket gateways and that the server specifically supports a WebSocket listener on the port you are attempting to use [5]. For direct IRC client connections, it is recommended to use the standard SSL/TLS port 6697 [4]. Note that RusChat is a distinct network and should not be confused with the larger, historically separate RusNet network [7][8].

Citations:

Confirm the WSS endpoint before merging.

irc.ruschat.net:443 is not documented as a WebSocket/IRCv3 WebSocket gateway, and this PR’s connectivity probes show the WSS transport is unavailable while IRCS succeeds. Remove the unsupported wss entry or replace it with the network’s valid IRCv3 WebSocket URL before this server can pass added-server validation.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@servers.json` at line 64, Update the “wss” entry in the server configuration
to use a confirmed, valid IRCv3 WebSocket endpoint for this network, or remove
the entry if no supported WSS gateway exists; do not retain the unverified
irc.ruschat.net:443 URL.

"ircs": "ircs://irc.ruschat.net:6697",
"obsidian": false,
"sasl": true,
"voice": false
Expand Down
Loading