Używasz przestarzałej przeglądarki. Może ona nieprawidłowo wyświetlać tę lub inne strony. Powinieneś zaktualizować przeglądarkę lub użyć alternatywnej przeglądarki.
SockChat — A SneedChat client for the command line - A lightweight standalone SneedChat client for the terminal, written in Go
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.
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.
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:
Then sockchat_amd64.exe "xf_user=VALUE; xf_csrf=VALUE; and XF_SESSION=VALUE" then connect. Very simple!
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.
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 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.
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.