SockChat — A SneedChat client for the command line - A lightweight standalone SneedChat client for the terminal, written in Go

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
y a t s said:
I do have plans for a sort of API mode that external programs, such as custom UIs (perhaps a web UI or phone app), can use to access chat data and control some underlying features.
Click to expand...
So this is going to end up being a complete rewrite to a minimal client-server model. For the sake of interoperability, the best option for feeding data to clients is probably relaying raw chat JSON over unix sockets or something. That way, outer layers like clients (or an IRC translation layer) can handle chat data in a common format.



Fun stuff.
 
1771013384940.png

Shout out to @OwO What's This?
 
Flaming Dumpster said:
Story of my life
View attachment 8568827
View attachment 8568826
View attachment 8568824
Cue a million more commits trying to fix reconnect issues afterwards due to the shitty Websocket library :lossmanjack:
Click to expand...
The key detail was the tls config. The default "safe" set of ciphers (in Go's implementation, at least) isn't enough. It was a bitch to narrow down where the issue was, especially since my solver seemed to work literally everywhere else (in normal http requests).

Those 203s had me feeling like I was going crazy.
 
You must log in or register to reply here.
Back
Top Bottom