SneedChat Complaint Thread

  • 🏰 The Fediverse is up. If you know, you know.
  • 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

Null

Ooperator
kiwifarms.net
Joined
Nov 14, 2012
- Last year, XenForo banned us from renewing our license with them.
https://kiwifarms.net/threads/xenforo-has-revoked-our-license.106654/

- I am developing our own forum software in Rust.
https://kiwifarms.net/threads/sneedforo.119115/
https://git.kiwifarms.net/KiwiFarms/ruforo

- Since 2013, I think I have written 4 different chat mods from scratch for 3 different software suites. Our chat works very independently from the main forum.

- To encourage production and interest in the new forum software, I have shimmed a new websocket based chat from it.

It's very new and I may turn it off and people hate it that much, but it definitely runs very fast, which I like. Any improvement on this chat will also benefit the new codebase when/if we ever switch over, which is also nice.


Keep in mind, when you complain. the hardest and least productive (long-term) things to do and add involve XF compatibility. This means custom emote support, XF-specific bbcode, @ user tagging, etc.
 
i need the emojis to express myself, nool. it's imperative that i express my autism in pictures,
 
It's way faster than the old chat in terms of refresh rate, which is very nice. Does that make it harder on server resources?
 
It would be good to have the chats work in the background while switching so that you can check up on the history of one chat while browsing the other.
 
[img] tag embeds images directly from source, without media proxy, meaning you could log IPs of everyone who is logged in and opens the chat or main page.
 
Perhaps when you switch tabs, it should head to the bottom of the chat in the new tab.

It would be consistent with how the initially-loaded chat goes to the bottom.
 
It's way faster than the old chat in terms of refresh rate, which is very nice. Does that make it harder on server resources?
Given it's websockets, rather than a bazillion http requests every minute, I'd believe the load is much lower on the server end. It's definitely lower on the client side.
 
Colored names would be nice. Just use the colors from the old chat for reference, unless you want to change them.
 
[img] tag embeds images directly from source, without media proxy, meaning you could log IPs of everyone who is logged in and opens the chat or main page.
yeah i'm just going to disable that.

KF hidden service, Tor Browser 11.0.13 (latest)
must be logged in.

It's way faster than the old chat in terms of refresh rate, which is very nice. Does that make it harder on server resources?
no, other way. ajax based polling via php is a monster.
 
Please make the chat you're in highlight the appropriate tab when you get a chance.

I don't know where I am and that can be very scary. What if I wander into the lion's den (read: the Beauty Parlor) by mistake?!
 
Forgot to mention that part. I am logged in, this post is made in the same session I tried to post in the new chat from. JS enabled/disabled, Safer/Safest browser profiles inside TBB. All behave the same way.
You are doing something which prohibits cookies via iframe.
 
Haven't been able to figure out what breaks, so here are my headers. Hopefully they help someone.

Code:
Request

GET /test-chat#8 HTTP/1.1
Host: uquusqsaaad66cvub4473csdu4uu7ahxou3zqc35fpw5d4ificedzyqd.onion
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101 Firefox/91.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://uquusqsaaad66cvub4473csdu4uu7ahxou3zqc35fpw5d4ificedzyqd.onion/chat/autistic-shitspigots.8/
Connection: keep-alive
Cookie: xf_csrf=[EDIT]; xf_user=[EDIT]; xf_session=[EDIT]
Upgrade-Insecure-Requests: 1
Sec-Fetch-Dest: iframe
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: same-origin

Response

HTTP/1.1 200 OK
Server: nginx
Date: Tue, 07 Jun 2022 15:04:33 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
Content-Encoding: gzip
TL;DR Cookies are inside the iFrame.

Code:
Request

GET /rust-chat HTTP/1.1
Host: kiwifarms.net
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101 Firefox/91.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Sec-WebSocket-Version: 13
Origin: http://uquusqsaaad66cvub4473csdu4uu7ahxou3zqc35fpw5d4ificedzyqd.onion
Sec-WebSocket-Extensions: permessage-deflate
Sec-WebSocket-Key: [EDIT]
Connection: keep-alive, Upgrade
Sec-Fetch-Dest: websocket
Sec-Fetch-Mode: websocket
Sec-Fetch-Site: cross-site
Pragma: no-cache
Cache-Control: no-cache
Upgrade: websocket
TE: trailers

Response

HTTP/1.1 101 Switching Protocols
Date: Tue, 07 Jun 2022 15:04:37 GMT
Connection: upgrade
upgrade: websocket
sec-websocket-accept: [EDIT]
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 717a47ff58ebfd9d-PDX
alt-svc: h2="cflarenuttlfuyn7imozr4atzvfbiw3ezgbdjdldmdx7srterayaozid.onion:443"; ma=86400; persist=1
TL;DR Only Sec-Websocket-Key and no cookie on the WSS connection. Is it a websocket thing and it's normal or is this where things fuck up?
 
In their respective subforums (Beauty Parlour, DSP, and so on) the chat can't be interacted with. Neither expanding chat or writing messages from there are possible.

It works, I'm retarded. You do need to click on the upper bar, previously clicking anywhere on the chat expanded it.
 
Back
Top Bottom