using with alternative discord servers

[anotherdoesnm]

Can i use rdircd with discord-compatible servers like https://spacebar.chat? Maybe rdircd can have options to specify api/gateway url?

[mk-fg]

Hi,

Yes, should probably work, though I haven't tried it.

There are no hardcoded discord.com URLs in rdircd as it is, and all used endpoints derive from a single api-url configuration setting in [discord] section. So I think you only need to change that in rdircd.ini to point to a self-hosted API endpoint, and it might work.

"Self-hosted API endpoint" as in one mentioned here - https://docs.spacebar.chat/setup/server/#connecting-from-remote-machines
All other endpoints listed there should be fetched from API, same as with official discord, e.g. gateway endpoint via <API>/gateway request, which for discord API returns json with "url" parameter in it. And CDN URLs are just in the links to posted stuff.

If that doesn't work for some reason - debug and protocol logs should probably have most info as to why, like if there are some minor API quirks and mismatches.

[mk-fg]

Btw, if you get it working, esp. with more tweaks than api-url required - maybe leave a comment as to what needs to be changed, can add it to README as a "how to use with spacebar.chat and such self-hosted instances" section or something.
Would be nice to have before discord goes IPO and adds all the ads :)

[anotherdoesnm]

Catched this error:

~ $ rdircd
/data/data/com.termux/files/usr/bin/rdircd:3741: SyntaxWarning: invalid escape sequence '\s'
  val_re = re.compile(b'^\s*([\w\d]\S+)\s*=\s*(\S+)\s*$')
/data/data/com.termux/files/usr/bin/rdircd:2715: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
  self.server_ts = dt.datetime.utcnow()
rdircd.discord ERROR :: Unhandled ws handler failure, aborting: [DiscordHTTPError] [400] Bad Request - {"code":50035,"message":"Invalid Form Body","errors":{"":{"_errors":[{"message":"must NOT have additional properties","code":"additionalPr ...[150/152]
Traceback (most recent call last):
  File "/data/data/com.termux/files/usr/bin/rdircd", line 1907, in ws_poller
    try: await self.ws_poller_loop()
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/usr/bin/rdircd", line 1937, in ws_poller_loop
    status = await aio_await_wrap(h.func(msg_data))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/usr/bin/rdircd", line 488, in aio_await_wrap
    if inspect.isawaitable(res): res = await res
                                       ^^^^^^^^^
  File "/data/data/com.termux/files/usr/bin/rdircd", line 2034, in op_hello
    await self.op_hello_auth()
  File "/data/data/com.termux/files/usr/bin/rdircd", line 2040, in op_hello_auth
    token = await self.req_auth_token()
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/usr/bin/rdircd", line 1742, in req_auth_token
    res = await self.req( 'auth/login', m='post',
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/usr/bin/rdircd", line 1776, in req
    raise DiscordHTTPError(f'[{res.status}] {res.reason} - {err}')
DiscordHTTPError: [400] Bad Request - {"code":50035,"message":"Invalid Form Body","errors":{"":{"_errors":[{"message":"must NOT have additional properties","code":"additionalPr ...[150/152]

config:

[auth]
email = nah
password = nah-too
[discord]
api-url = https://api.old.server.spacebar.chat/api/v9
gateway = wss://gateway.old.server.spacebar.chat

it's rdircd from termux repos

rdircd/stable,now 2023.02.07-1 all [installed]
  A daemon that allows using a personal Discord account through an IRC client

should i try master branch?

[mk-fg]

should i try master branch?

Uhm, yeah, that's quite an old package unfortunately :)

I think specific issue there is with sending email= field in getting auth token request, instead of login=, which discord itself also dropped relatively recently (end of '24 or maybe even in '25), and was probably never implemented in spacebar.chat in the first place.

Which should be fixed in current rdircd, no need to change rdircd.ini for it or anything, just update the script.

[anotherdoesnm]

Master branch:

~/reliable-discord-client-irc-daemon $ ./rdircd
rdircd.discord ERROR :: ws event caused handler exception [DiscordHTTPError]: {"op":10,"d":{"heartbeat_interval":30000}}
rdircd.discord ERROR :: Unhandled ws handler failure, aborting: [DiscordHTTPError] [400] Bad Request - {"captcha_key":["captcha-required"],"captcha_sitekey":"d28e3c32-2752-4408-b0c4-79a2ad98cc26","captcha_service":"hcaptcha"}
Traceback (most recent call last):
  File "/data/data/com.termux/files/home/reliable-discord-client-irc-daemon/./rdircd", line 2838, in ws_poller
    try: await self.ws_poller_loop()
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/home/reliable-discord-client-irc-daemon/./rdircd", line 2872, in ws_poller_loop
    try: status = await aio_await_wrap(h.func(msg_data))
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/home/reliable-discord-client-irc-daemon/./rdircd", line 947, in aio_await_wrap
    if inspect.isawaitable(res): res = await res
                                       ^^^^^^^^^
  File "/data/data/com.termux/files/home/reliable-discord-client-irc-daemon/./rdircd", line 2993, in op_hello
    await self.op_hello_auth()
  File "/data/data/com.termux/files/home/reliable-discord-client-irc-daemon/./rdircd", line 2999, in op_hello_auth
    token = await self.req_auth_token()
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/home/reliable-discord-client-irc-daemon/./rdircd", line 2672, in req_auth_token
    res = await self.req( 'auth/login', m='post',
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/home/reliable-discord-client-irc-daemon/./rdircd", line 2707, in req
    raise DiscordHTTPError(res.status, f'[{res.status}] {res.reason} - {msg}', err)
DiscordHTTPError: [400] Bad Request - {"captcha_key":["captcha-required"],"captcha_sitekey":"d28e3c32-2752-4408-b0c4-79a2ad98cc26","captcha_service":"hcaptcha"}

[mk-fg]

DiscordHTTPError: [400] Bad Request - {"captcha_key":["captcha-required"],"captcha_sitekey":"d28e3c32-2752-4408-b0c4-79a2ad98cc26","captcha_service":"hcaptcha"} there is probably what it says on the tin - as in CAPTCHA solving.

Don't think rdircd has any easy way to work around that, but I think when discord requests it, logging in via browser to "authorize IP address" (as iirc they say after solving the thing) can help:
https://github.com/mk-fg/reliable-discord-client-irc-daemon?tab=readme-ov-file#hdr-captcha-solving_is_required_to_login_for.ls9P

Dunno if spacebar.chat has a browser client of some kind, but if not, guess some kind of URL can be logged in rdircd for user's browser, to go there and solve the thing, which might fix the issue, but idk.

Anyhow, try browser client from same IP if alt-server you're connecting to has it, and you haven't already.
Also, if it's self-hosted and under your control, maybe disable CAPTCHA or somehow authorize your rdircd IP to not require it.
But if that doesn't work, don't think I know any other easy workaround for it currently, unfortunately.

[mk-fg]

But if that doesn't work, don't think I know any other easy workaround for it currently, unfortunately.

Oh, wait, correction - there's one listed in that link I posted, but also requires some other client that can display javascript captchas, from where you can get an auth token to use with rdircd. Should be already described in that link though.

[anotherdoesnm]

Spacebar has two clients: official (WIP) and Fermi (WIP too, but at least usable)
https://docs.spacebar.chat/setup/clients/
https://docs.spacebar.chat/setup/clients/fermi/web/

[anotherdoesnm]

filled token in config

~/reliable-discord-client-irc-daemon $ ./rdircd
rdircd.discord ERROR :: ws event caused handler exception [AttributeError]: {"op":0,"t":"READY","s":0,"d":{"v":9,"user":{"username":"doesnm","discriminato ...[90/45,628]
rdircd.discord ERROR :: Unhandled ws handler failure, aborting: [AttributeError] 'str' object has no attribute 'get'
Traceback (most recent call last):
  File "/data/data/com.termux/files/home/reliable-discord-client-irc-daemon/./rdircd", line 2838, in ws_poller
    try: await self.ws_poller_loop()
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/home/reliable-discord-client-irc-daemon/./rdircd", line 2872, in ws_poller_loop
    try: status = await aio_await_wrap(h.func(msg_data))
                                       ^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/home/reliable-discord-client-irc-daemon/./rdircd", line 3066, in op_ready
    if not (n := rs.get('last_viewed')): continue
                 ^^^^^^
AttributeError: 'str' object has no attribute 'get'

[mk-fg]

Ah yeah, that's definitely starting to get into "protocol quirks/mismatches" unfortunately, where in original discord there's an object/dict/mapping and here it's a string.

I probably should register/connect there myself and handle all these initial issues, as there's likely to be a bunch of them, so would be easier to fix/retry myself that way. Dunno when I'll get to it, but definitely nice to see more options wrt discord-like messaging, and would be great to support those as well.

Thanks for bringing it up here.

[anotherdoesnm]

i don't understand discord protocol as much better as you but making line 3066 like this at least helped to run rdircd without crashes. And i can send and receive messages

if not (n := 0): continue

[mk-fg]

Oh, nice, thanks.
Given that it was immediate protocol mismatch in the very first READY protocol message, assumed there'll be many more similar ones from there, but maybe it was indeed a one-off like that.

Should be fixed in c5795a6 I think, as I assume spacebar.chat just puts message-id into read_state directly.
EDIT: Or more like worked-around in the same way, will probably need to see what's there - a date-time, msg-id, etc - to fix this properly, but current workaround will ignore these, which should only be relevant if you use somewhat obscure channel history auto-replay functionality (via /t log watch commands), and even then it'll probably mostly work fine.

But yeah, if everything more-or-less works, you can probably bypass any other issues in a similar way, as there's a lot of miscellaneous functionality with complicated data structures that most folks probably won't even notice missing (like e.g. pretty sure most complicated code parts are parsing embedded link info, and that's kinda throwaway extra stuff).
Might be worth reporting these quirks anyhow though, to fix here for anyone else as well.

[mchamsteryt2]

Something along the lines of this issue, maybe some way to use it with a completely different discord alternative such as fluxer could be good but will need to read more into the api though

[anotherdoesnm]

is Fluxer API compatible with Discord?