Feedback Technical Grievances

  • 🔧 At about Midnight EST I am going to completely fuck up the site trying to fix something.
Had a botcheck take a minute and not do anything, waited a little, went from node sneed1 to sneed2, loaded in regular time. Idk if that's relevant, haproxy seems to be working beautifully.
On mobile I let botcheck run for like 30 seconds and if nothing happens I refresh the page and it works could be just a bad connection to the node and you just need to reconnect to one that is operational. The DDoS is probably hitting the one you are connecting to initially making it lag out.
 
  • Like
Reactions: WolfeTone
2CBF355E-DAB5-46A2-96D6-1BF2AA514EFC.jpeg
 

Attachments

  • 1E47F0ED-A8D6-458E-AEDA-BBE6081BAC8D.jpeg
    1E47F0ED-A8D6-458E-AEDA-BBE6081BAC8D.jpeg
    128.4 KB · Views: 41
When is Sneed chat coming back can you give a rough ETA on it? It is not a big deal and want you to take your time with it just curious.
Sneedchat is down forever or i'm permabanned from it, or i'm just retarded?
From what I understand, Sneed chat is the reason why the site was hacked days ago so it will probably take a while until it returns.
 
  • Agree
Reactions: WebLurker
I have gained back the ability to have a post box, but the lack of pics loading remains.
 
Is there a way to submit the text box in the "No JavaScript?" section without a submit button? Sometimes I have to reload the bot page several times before the submit button loads alongside it.

Tor Browser 11.5.2
Debian Bookworm/Sid
 
Anybody gotten this error when trying to authenticate stuff?

1664928817238.png


Root got the error trying to authenticate their password
 
Bby just use kiwi browser, I have been shilling this browser up and down the farms, it is the same problem I had.
Now all of the problems (endless robot check, failed connection, secure connection, error 503/502, reply box disappearing, attachments not processing) are gone, poof.
Screenshot_20221003-193508__01.jpg


Edit: poor mfr, just read your message to the end, kiwi browser is only for android. Change the browser to something else, not duckduckgo though, it is retarded.
 
Last edited:
Bby just use kiwi browser, I have been shilling this browser up and down the farms, it is the same problem I had.
Now all of the problems (endless robot check, failed connection, secure connection, error 503/502, reply box disappearing, attachments not processing) are gone, poof.
View attachment 3715750

Edit: poor mfr, just read your message to the end, kiwi browser is only for android. Change the browser to something else, not duckduckgo though, it is retarded.

Don't use Kiwi Browser, it had pretty serious privacy issues - https://github.com/Tobi823/ffupdater/issues/35 (A)
Stick to trusted FOSS solutions(on Android) like:
- https://www.bromite.org/ - "ungoogled chromium" for Android with AdBlocker and extra hardening;
- https://f-droid.org/en/packages/org.mozilla.fennec_fdroid/ - Firefox without Mozilla and all their gay shit, sorta like Librewolf, but for Android.
 
Don't use Kiwi Browser, it had pretty serious privacy issues - https://github.com/Tobi823/ffupdater/issues/35 (A)
Stick to trusted FOSS solutions(on Android) like:
- https://www.bromite.org/ - "ungoogled chromium" for Android with AdBlocker and extra hardening;
- https://f-droid.org/en/packages/org.mozilla.fennec_fdroid/ - Firefox without Mozilla and all their gay shit, sorta like Librewolf, but for Android.
I have read up on this thing, but the developer answered this on reddit: link
Hey, Arnaud here who develops Kiwi Browser. Thanks for quoting the GitHub answer.

Yes, when you are one of the smaller browser, you don't get the direct link to [Bing.com](https://Bing.com) or [Yahoo.com](https://Yahoo.com) and the special referral code but you have to use the same setup as browser "extensions".

Extensions are forced to use intermediate redirects. This is why you see "fastsearch", "mysearch", etc, with browser extensions.

When you have a small browser (like Kiwi Browser, but Kiwi is not that small; it has about 1.2 million daily active users according to Google Play Store), you get in this shit-tier "untrusted third-party browser extensions partnership" and this lousy setup.

It's not a conspiracy, if I could put the [bing.com/?source=kiwi](https://bing.com/?source=kiwi) I would do it 100%.

You can even know that for one simple fact; most of the users (how many, I don't know because there are no analytics :D ) use Google Search, and Google is a plain old-school direct link pointing to [Google.com](https://Google.com)

What if to add an option in the Search settings page to add an additional option to go directly to Bing / Yahoo and to explicit that the other (current) settings helps to monetize/fund the browser ?

Wouldn't that make everyone happy ?

Honestly I'm not tech-savvy enough to understand anything of this but I saw an over all positive reaction to it. But I will certainly try the ones you suggested.
 

Can confirm, the issue exists.
1664934815000.png


Likely CSP related, but not sure:
1664934845300.png


Or SSL related, as no-cookie.kiwifarms.net appears to be failing on HTTPS front:
1664934925400.png


(Tested on Tor Browser connecting over .net domain, if there are some "magic session tokens" in place, then that's the issue, as Tor uses different exits to handle other domains/(?)subdomains)
 
Can confirm, the issue exists.View attachment 3715948

Likely CSP related, but not sure:
View attachment 3715950

Or SSL related, as no-cookie.kiwifarms.net appears to be failing on HTTPS front:
View attachment 3715953

(Tested on Tor Browser connecting over .net domain, if there are some "magic session tokens" in place, then that's the issue, as Tor uses different exits to handle other domains/(?)subdomains)
I'm not seeing anything obvious wrong on no-cookie with SSL/TLS from clearnet.
But I am seeing the same with TOR to the clearnet intermittently: PR_END_OF_FILE_ERROR
Seems like a bad node is being hit. I don't think any headers or URLs have been sent as it's not even getting to the TLS negotiation. Maybe an SNI problem.
 
  • Agree
Reactions: notafederalagent
<not a grievance> but the sight's working smooth as butter for me for the first time since the new router went in.
 
I noticed a minor glitch, the "thunk-provoking" reaction doesn't show properly. You need to add a slash at the start of the URL in its CSS:
Screenshot_20221005_145343 2.png

The other reactions seem fine.

Edit: Nevermind, apparently it's fixed now.
 
Last edited:
Back