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

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
The issue I had was which of the 21 different items on the release page I am supposed to download to use with a 64bit windows system.
The EXE file for amd64 (sockchat_amd64.exe). amd64 is the architecture type.

Edit: There is a new release with simpler names that I will continue using from now on.
 
Last edited:
1710344417861.png

Did you self-censor or is that a feature for the app to censor "Fucker" and "FucKing" ?
 
View attachment 5811937
Did you self-censor or is that a feature for the app to censor "Fucker" and "FucKing" ?
There are no censorship or filtering features whatsoever, nor will there ever be.

Idk if the site still feeds messages from ignored users over the websocket, but I am hesitant to add anything that could stifle discussion.

Edit: No censorship on my part in the image either. Whoever wrote the message was doing a copypasta I think.
 
Last edited:
oh hell yeah never been retarded enough to cause a dev to change how they distribute a program, first time for everything :^)
lol I already had a feeling after the fact that the names would be a bit confusing. ARM64 and AMD64 look similar enough to confuse easily, and almost no one knows what i386 actually is.
 
  • Like
Reactions: Wright
Artisanal code quality. I'm nowhere near literate enough in Go to say if it's good, per se, but your semantic economy really suggests thorough grasp of the solution space.
 
  • Feels
Reactions: y a t s
I put my computer to sleep and when I came back:
1710382326229.png
It was reconnecting a lot of times though.
 
  • Feels
Reactions: Relinquish
1710344417861.png

Did you self-censor or is that a feature for the app to censor "Fucker" and "FucKing" ?
Judging by this, it looks he censored it himself.
Is this one of those things where if I have to ask how to use it I'm obviously not welcome in the first place?
No, but it's quite easy to launch. For example, my sockchat is amd64.exe, so all I would have to do is download it, cd into the folder (cd downloads), and get the cookies from the request headers (inspect element, 2nd kiwifarms.st request, scroll down, request headers:
1710382950496.png

Then sockchat_amd64.exe "xf_user=VALUE; xf_csrf=VALUE; and XF_SESSION=VALUE" then connect. Very simple! :)
 
I put my computer to sleep and when I came back:
View attachment 5813760
It was reconnecting a lot of times though.
I think I fixed that in the latest version. It was a concurrent write while trying to rejoin a room and resend a failed message.

Edit: Looks like I was accidentally re-queuing join messages that don't send. This makes them pile up with each reconnect :\. It should be fine now.
This shouldn't cause a concurrent write because it writes through the dedicated worker now, but it's closely related to that old bug.

Edit 2: If running the logger, ensure your computer's sleep mode doesn't disable the network connection. This is pretty common functionality in sleep modes for many OSes.
Once I have proper daemon services ready, I may be able to benefit from it being recognized as a background service that requires a constant connection. Idk yet.

Edit 3: I have now capped connection retries at 8 before a 15 second cooldown.
 
Last edited:
Is there a way to use a cookies.txt file instead of manually grabbing the values every time?
 
Is there a way to use a cookies.txt file instead of manually grabbing the values every time?
I'm working on full username-password authentication. I have a KiwiFlare solver made, so I just need to handle fetching the cookies. In the meantime, the values only change once every few days or something.
 
I'm working on full username-password authentication. I have a KiwiFlare solver made, so I just need to handle fetching the cookies. In the meantime, the values only change once every few days or something.
I mean I use this for ytldp and this might be easier than trying to figure that shit out
 
I mean I use this for ytldp and this might be easier than trying to figure that shit out
I know what cookies.txt is. I don't see a point in adding that in the meantime. The file doesn't stay valid for a month or anything, so the level of inconvenience seems equal. And you can use command history to recall the command with the cookies easily.
 
Last edited:
I have the same problem but I just assumed it was user error and moved on. Does it matter if I use Firefox or Chrome?
 
  • Like
Reactions: y a t s
I have the same problem but I just assumed it was user error and moved on. Does it matter if I use Firefox or Chrome?
It doesn't matter. As long as you can get the string of cookies from the header your browser uses to load the site while you're logged in, you should be able to connect.

I'm actively working on a user authentication library I can make use of here.
 
Back