Feedback Technical Grievances

  • 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
Is this just me? I have been getting no image previews or avis for a week or two.
Tor site, iPhone with Orbot (onion only mode or everything mode).

If you click the image it does load (slowly).

9327B22D-1CD5-4A03-A2FE-6DECBF3E6474.jpeg
 
Is this just me? I have been getting no image previews or avis for a week or two.
Tor site, iPhone with Orbot (onion only mode or everything mode).

If you click the image it does load (slowly).

View attachment 5221032
Varies for me (tor site, brave tor thingy) - sometimes images/avis take ages or don't load, other times it's normal (and reasonably fast). Seems worse with videos for some reason.
 
View attachment 5219072

Every now and then on sneed I get a broken cryptographic challenge page. I’m pretty sure those dots animate and the logo should be there. It never progresses passed this page. It’s been happening for half a week maybe. If I go back and try again a few times it seems to go away for a while.
What I've gotten a few times in the last day or so is a normal looking page, but it just sits there forever. If I refresh, I'm allowed right in. Next time it happens I'll refresh fast to see if I'm allowed in before I could have possibly solved the challenge.
 
Occasionally I'll change pages and either get stuck on the KiwiFlare page or sometimes it will just refuse to load. Closing the window and wiping my browser fixes it temporarily.
I'm on Brave (mobile) and have my anti-fingerprinting settings turned to max
 
Occasionally I'll change pages and either get stuck on the KiwiFlare page or sometimes it will just refuse to load. Closing the window and wiping my browser fixes it temporarily.
I'm on Brave (mobile) and have my anti-fingerprinting settings turned to max
Same for me with refusing to load entirely, also Brave on Android. I wasn't even aware clearnet was fully available again until a couple of days ago. No biggie as the .onion works great apart from the picture threads but those are giving me trouble on clearnet as well and where i encounter the refusing to load thing.
 
The chat doesn’t work for me. I keep getting “429 Too Many Requests.
You have sent too many requests in a given amount of time.”
 
Has search always been autistically literal about apostrophes? I've been looking for the thread Lauren Southern's "The WHOLE Truth" and searching "Lauren Southern" in titles only doesn't bring it up. It seems to need an exact match as it does show up when searching "Lauren Southern's" instead.
 
Because the error page, for some reason, uses CSP rules that prevent arbitrary javascript from executing.
I simulated the error and the browser literally says what the issue is
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'nonce-t8L8kWrpEusj0gqt5IF3a3ghICvhgvfu' no-cookie.sneed.today www.gstatic.com www.recaptcha.net ext.nicovideo.jp". Either the 'unsafe-inline' keyword, a hash ('sha256-WTdnYyYEZzVs+CDP7J/bkAsHSkeLzTr/+WpnGg6oDug='), or a nonce ('nonce-...') is required to enable inline execution.

I wouldn't fuck with the CSP if I were you though, instead I'd remove the button from the service worker offline template.
 
I have for some time had an issue where if I open two tabs at the same time and the PoW is expired, both tabs will (sensibly) try to solve it, but while the one to be done first succeeds, the other one will fail to submit the proof and display an error. This is annoying, because then I have to manually remove the /bot-check? from the URL.
It was a bit of a bother to hold tab races to try to reproduce this, but I found out that the bot-check endpoint returns a 500 when a tab tries to submit a PoW proof while there is a valid one already. Would it be possible to make this not error out, and preferably even make the "late" tab automatically try redirecting to the bot-check-less URL? If you're fine with jank, I think it'd even work to try the redirect on failure always, in the case this is unfounded the DDoS protector will toss you back to the bot check anyway.
 
Back
Top Bottom