DrJosiah
Joined 16 years ago
Karma
604
Submissions
288
Member since
Jun 26
Recent submissions
Comment · 1 year ago
Comment · 1 year ago
I mean, Python is dynamic. Here, have this:
https://gist.github.com/josiahcarlson/39ed816e80108093d585df...
Now you don't need to write your double-underscore methods ever again, if you don't want to.
Comment · 1 year ago
I mean, it's never been a problem for me in my 26 years of Python, but if it is such a big deal for you, maybe you should consider this:
https://gist.github.com/josiahcarlson/39ed816e80108093d585df...
I wrote it in about an hour and a half. It seems to work in Python 3.6 and 3.12. Now you never need to write another double-underscore magic method again.
Comment · 3 years ago
It might have been a typo, as the current llama.cpp / alpaca.cpp included quantizers default to 4 bits.
Comment · 3 years ago
And only when Carter is in hospice.
Comment · 4 years ago
Used to work for hCaptcha.com, my thoughts:
hCaptcha.com has a "privacy pass", where if you create a user at hCaptcha.com, you can get passes to bypass the captcha itself (because you've already verified through other methods). This is not often used, because guess what? Not many people were bothered by captchas enough to create a user, because no one wants to create another user and be tracked (via privacy pass, across captcha-protected sites) through their user. This was mostly used by disabled users who couldn't pass hCaptcha's offerings.
Personally, I'm not interested in "logging in" or passing my "realness" via API from my device(s), as that's just another token to track an individual and their behaviors. Which is also why I haven't created any user for privacy pass myself, and would generally recommend that you not do so in any Apple, Google, etc., related system (not even hCaptcha, unless you're disabled and can't do the captcha itself).
I don't know what hCaptcha is doing nowadays.
But unless you're disabled, I wouldn't sign up or agree to pass this information from Apple, Google, etc.
Comment · 6 years ago
When I was writing some assembly last summer, I found:
https://software.intel.com/sites/landingpage/IntrinsicsGuide...
I don't have AMD, so didn't need to look up AMD specific stuff. Would be amazing if AMD had something like Intel's interactive Intrinsics Guide.
Comment · 6 years ago
> Are there not "ML techniques" for visual captchas too?
There are.
> how long do you think that is going to last?
I don't know. So far it hasn't been difficult to recognize the garbage traffic when we take the time to look. And attackers always make it easier by releasing github source and / or announcing their results on Twitter.
Comment · 6 years ago
I run android. Other devs run Android and recent iPhones. Someone may have an iPhone 6S to test and fix on, I'll check.
In the future, if you've got a bug that's preventing you from doing your thing, we have bug reporting instructions: https://www.hcaptcha.com/reporting-bugs
ETA: two different people have tested on Chrome and Safari on iPhone 6S locally, and can't reproduce. Please take a screenshot and provide more information to: https://www.hcaptcha.com/reporting-bugs if you want to get this fixed.
Comment · 6 years ago
Here it is: https://news.ycombinator.com/item?id=23903405
Comment · 6 years ago
Hi! I work at hCaptcha (we handle the CF captchas), and to respond specifically: audio is inaccessible for those with visual and auditory processing issues, as well as being broken by ML techniques. Not to project, but we suspect this is why Google turns it off if your browser looks at all suspicious.
Another user mentioned the Privacy Pass solution: https://news.ycombinator.com/item?id=23902870
While Privacy Pass is not perfect, we are working towards getting better. I'm not in the product flow for accessibility, but if you have ideas outside of audio that you believe would be able to distinguish between yourself and a robot, I'd be happy to discuss via email to ensure that we can get a solution for you and anyone who can reasonably interact with a computer.
eta: you can email me directly at work via: [email protected]
Comment · 6 years ago
I work at hCaptcha, we run CF's captcha. If you're having problems in the future, popping open a debugger and capturing the results can help us figure out what's going on. But also: browser, OS, site, ...?
Right now: there is an issue with Safari users on the most recent iOS and OS X, where 3rd party cookies have now been disabled by default. We're working on a solution.
If that's your issue, you can fix on your side in the short-term by not using Safari, or by enabling 3rd party cookies.
Comment · 6 years ago
If anyone doesn't think the AG is serious, read the document request / questions at the end. Someone on the tech side is giving advice :)
Comment · 6 years ago
My money is on it to disable support for sha1 in old products; maybe a bigger break than the prefix attack currently known.
Take a deep breath.