KiwiFlare

I clicked the link, saw that it was that retarded tranny faggot, and assumed that I'd need to unmute it to understand what the point of it was, and I didn't want to do that so I just closed it without playing more than the first couple of seconds.

Lucky for me.
 
Every 4 or 5 actions on the site if thats responding on a thread, checking alerts, or replying to a post.
OOPS Somthing went wrong! Using Thor. Have to New Ident re-log in and it does it again after 5 or 6 actions.
Bruh!
I need more information. DM/Email me your country, provider, and if you're mobile or not.
 
Common Null W
I see it and it appears to be working for me. No errors.
 
I'm expecting that link that you can click on at the bottom to change periodically depending upon what's funny at the time.
 
  • Like
Reactions: Moosebonker
If you see any more "Client errors" prompting you to manually refresh, please notify me. This was an issue particularly with phones, because they take longer to solve the problem.
I post from 2 different phones and one of them just straight up never finishes the work or times out. Granted it's a shit android from 2016.
 
  • Thunk-Provoking
Reactions: Procrastinhater
I regret clicking on that link tremendously.
Anyone who doesn't regret it should immediately seek professional help. Or have a stiff drink. Or both.

@Null - are you at liberty to discuss what changes you made to the haproxy-protection package? Assuming it was stuff to deal with the decentralized nature of the forum these days, but certainly curious to know more.

Also for the Tor folks - I noticed this when I was testing with a Brave Tor window. I don't use Tor often so not sure if this was an issue before the KiwiFlare changes but wanted to point it out since allowing the scripts permitted me to proceed to the site. I haven't gotten a white screen yet though as other users have seen.
 

Attachments

  • tor.png
    tor.png
    72.7 KB · Views: 23
Will this be implemented on the TOR site? I’m still seeing the old bot page and I’ve never been able to get passed a WebAssembly error, even on the lowest security settings.

View attachment 4407696
Desktop here, so not sure if applicable for your browser, but try enabling a bridge for your connection. I had to do that for the previous Tor browser update before it would stop timing out on request
The site doesn't work on TOR even if I use the normal version on the tor browser
View attachment 4411308View attachment 4411380
Update your browser (you might need to reinstall) and make sure Tor isn't being blocked from online by your firewall/security programs
Every 4 or 5 actions on the site if thats responding on a thread, checking alerts, or replying to a post.
OOPS Somthing went wrong! Using Thor. Have to New Ident re-log in and it does it again after 5 or 6 actions.
Bruh!
You can also select "New Tor circuit for this site" from the toolbar dropdown to refresh your site connection without dropping cookies, Bruh
1675446600328.png
 
Also for the Tor folks - I noticed this when I was testing with a Brave Tor window. I don't use Tor often so not sure if this was an issue before the KiwiFlare changes but wanted to point it out since allowing the scripts permitted me to proceed to the site. I haven't gotten a white screen yet though as other users have seen.
This is Brave being retarded. It started happening about 2 updates ago.
 
This is Brave being retarded. It started happening about 2 updates ago.
Thanks, I didn't realize it was a recent 'feature' -- I've been dealing with other Brave retardation with not being able to claim BAT because their stupid captcha won't load. Been going on for months apparently but they keep saying the fix is "soon."
 
Thanks, I didn't realize it was a recent 'feature' -- I've been dealing with other Brave retardation with not being able to claim BAT because their stupid captcha won't load. Been going on for months apparently but they keep saying the fix is "soon."
I think it's a side effect of Brave thinking that .onion "isn't secure" because it isn't HTTPS.

1675450953703.png


edit: to expand on this a little bit, .onion is inherently secure by design... the reason that kiwifarmsaaf4t2h7gc3dfc5ojhmqruw2nit3uejrpiagrxeuxiyxcyd.onion has all that random shit in it is because it's the public key of a security certificate, and only the server with the matching private key can register itself on the Tor network and say "yeah, that's me, send me the traffic." And all traffic on the Tor network is end-to-end encrypted. So I feel that Brave is thoroughly incorrect in saying that the connection is not secure. It's not susceptible to the types of attacks that make HTTP insecure. Or even the types of attacks that could make HTTPS insecure, for that matter (much harder to do, but DNS poisoning can still allow a malicious server to impersonate an HTTPS site if they somehow obtain a valid CA security key for that domain name)!
 
Last edited:
I post from 2 different phones and one of them just straight up never finishes the work or times out. Granted it's a shit android from 2016.
Try it again. I also use a potato phone and couldn't access the site for pretty much all day yesterday. Either checks ran forever, or I got "received a client error in reply" messages. I was starting to suspect Kiwiflare's proof of work mechanism was incompatible with ancient browsers (FF 68 can't pass Cloudflare's checks either) up until one refresh suddenly succeeded.

Seems like whatever Josh tweaked today fixed the problem. The checks aren't exactly lightening fast, but none of them failed so far.
 
  • Informative
Reactions: Roland TB-303
Back