Feedback Technical Grievances

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
I thought the site was down but it was actually Mullvad's fault: the wireguard servers won't let me access kiwifarms. I'll end up on the "page could not be loaded" site.
Weird. Works perfectely for me.
 
Tor is the most reliable option for me right now for logins. Clearnet works (good for lurking), ProtonVPN is still acting all wonky so it's not worth dicking around with right now. Onionchads stay winning
 
Does anyone know why when I use Tor (keeps happening on Android and now on Desktop) this message "Error: browser does not support WebAssembly" keeps appearing and I can't acces the forum?
 
Does anyone know why when I use Tor (keeps happening on Android and now on Desktop) this message "Error: browser does not support WebAssembly" keeps appearing and I can't acces the forum?
Tor Browser has WASM support disabled by default which is needed for DDoS protection, if you go to about:config and search for "wasm", and if "javascript.options.wasm" is set to false double click to set it to true.
 
At moment on clearnet attempting to post replys or new thread does nothing. It will show the thinking in the right upper corner, but it doesn't seem to even really try to post. It is fine on Tor. It started doing this last night when HaltDos came back.

Browser : Firefox 108.0.1
 
Site is relatively stable for me right now on clearnet. I get errors when I open a new page sometimes, but I just have to keep refreshing until I get in. Otherwise fine and a LOT better than earlier in the day. Just gotta be patient.
 
Whatever the issue was with the wireguard server from the Mullvad VPN, it's fixed now. Works smooth on pc.
 
Update from the Telegram feed:
Right now they're exploiting something in the anti-bot check itself to slow the site down tremendously. The server we have that's connected to GTT is one of the weakest, and it can't really keep up with all the attack traffic.

If you change countries on your VPN away from North America, or use Tor, you may have better luck.

Part of why they're doing this is that the anti-bot checks excludes search engine bots. Troons really want shit like "consent accident" to stay off search results for their name, so just keeping the bot check page up is a part of their ambitions.

@Null If you're up for it you can whitelist the Googlebot IPs (and I assume likewise for yandex, bing, etc.): https://developers.google.com/static/search/apis/ipranges/googlebot.json

Also, have you managed to capture a dump of the requests they're sending, that you'd be willing to share (unless you're already working on mitigating it)?

edit: bing also publishes their IPs (https://www.bing.com/toolbox/bingbot.json), but yandex seems to require reverse/forward DNS verification which I'm not sure how easy is to do in haproxy.
 
Last edited:
Tor Browser has WASM support disabled by default which is needed for DDoS protection, if you go to about:config and search for "wasm", and if "javascript.options.wasm" is set to false double click to set it to true.
Wow! Thanks! Who knew it was that easy?
 
Wow! Thanks! Who knew it was that easy?
Be aware that it makes you a bit less anonymous when browsing other sites on Tor (since sites can see that you have enabled something non-standard), so if you're very paranoid and browse the dark web you should turn it back off when done on KF.
 
  • Informative
Reactions: Kosher Salt
Back