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
For whatever reason, I suddenly can't get pass the DDoS protection on mobile. I've tried on Brave. I've tried on Samsung's default browser. I've tried enabling Brave's Desktop view. Nothing. Used to take a few seconds, but now it just hangs.
I've had a similar issue, where it does eventually get through but it's been dog shit slow. It has been taking about 90 seconds on average where it used to be nearly instant. Started a few days ago and I'm using mobile firefox.
It's not hanging, it's just really high difficulty so takes ages for phones to solve it. On my phone it takes about a minute and it's red hot by the end of it. The patience is set to 3 minutes so that's how long your phone has to solve and submit the answer.
 
I will reduce the difficulty in a bit. I am working on a lot.
Alternatively, some sort of progress indicator would be great for making it clear it's chooching along and hasn't frozen up, like a current count of the challenges solved. After a minute of the indeterminate loading indicator it's hard to tell if things are still working.
 
there is no progress. your computer has to make a guess it has a probability of a 1/2^20 shot of making. It will continue to guess until it lands. Asking for progress on this is effectively asking for progress on BossmanJack successfully winning roulette twenty times in a row.
 
there is no progress. your computer has to make a guess it has a probability of a 1/2^20 shot of making. It will continue to guess until it lands. Asking for progress on this is effectively asking for progress on BossmanJack successfully winning roulette twenty times in a row.
You could fake it by getting average solve times by device type.
 
You could fake it by getting average solve times by device type.
That would involve tracking solve times over a large enough data set. If I'm going to do that I might as well reduce difficulty to 2^16 (factor of 16 times easier) and then have them solve it 16 times. it is effectively the same thing, though it would benefit multiple cores and potentially attackers.
 
That would involve tracking solve times over a large enough data set. If I'm going to do that I might as well reduce difficulty to 2^16 (factor of 16 times easier) and then have them solve it 16 times. it is effectively the same thing, though it would benefit multiple cores and potentially attackers.
Would doing a count of the number of guesses made/submitted be easy to do? Anything that indicates it's still actively getting feedback from the server would make it clear it's still alive.
 
What does the Kiwi Flare error "Your bypass attempt was rejected." mean? Earlier KenoGPT took like 30 or 40 attempts to solve the challenge constantly getting that error until it suddenly worked.
 
What does the Kiwi Flare error "Your bypass attempt was rejected." mean? Earlier KenoGPT took like 30 or 40 attempts to solve the challenge constantly getting that error until it suddenly worked.
have you adjusted the difficulty?
 
have you adjusted the difficulty?
It gets the difficulty from the data-sssg-difficulty attribute. Does the error just mean wrong answer? Going to turn the logging up so I can see what nonce it thought was valid.
 
no, I updated something that might've rolled back a live server change.


you can report anyone from the hover-over menu.
I'm not seeing a report option in the hover-over menu

Unt3itled.jpg
 
there is no progress. your computer has to make a guess it has a probability of a 1/2^20 shot of making. It will continue to guess until it lands. Asking for progress on this is effectively asking for progress on BossmanJack successfully winning roulette twenty times in a row.
No joke, make a fake progress bar and you'll be flooded with people loving the new "faster" Kiwi Flare.
 
Back
Top Bottom