Hacker Newsnew | past | comments | ask | show | jobs | submit | treesknees's commentslogin

Doubtful. You’re not going to mine a bitcoin in 30 seconds.

It’s been pretty popular lately to utilize a proof of work problem to deter AI scrapers. This is likely what you’re seeing.

Anubis is the one I’ve seen most often, but not the only one. https://github.com/techaroHQ/anubis


Thanks, but makes no sense to use 100% of the CPU power on the browser just to detect or stop AI scrapers?

Let's use all the power of a CPU during 30 seconds and save humanity from AI crap. Makes no sense at all.

Let's also make people wait 30 seconds to type something to search. People will just stop using this crap.

Thank you for your tip but this is beyong stupid. Let me just add startpage to blocked domains list.

Thanks again.


It has ramped up over time, it used to be just a few seconds was enough. You’re right that it’s unsustainable and annoying.

Without more context it’s hard to say whether 332 is reasonable, but I interpreted “reasonable” as in there will always be some amount of harmful content uncaught by automated systems.


I agree, more context would be helpful.

In my mind there are two components of this that are in direct tension though, regardless of numbers:

1. Humans having to review ad content is legitimately traumatizing and awful

2. Automated systems can miss obviously harmful content, which should never be allowed

To me this means we probably shouldn't permit these systems to scale as they do, because the company profits from harms to its own workers and/or ad viewers. I worry that we've normalized a business that shouldn't exist in its current form, but it prints so much cash that no one is willing to stop it.


I’ve been running a VPS with the same IP (v4 and v6) for ~15 years, so I’d say its stable enough. What should I use as an upstream source of time in this case that would actually be useful?


You just use a subset of the other known good nodes in the pool as your source. You’re just acting as an edge node for load distribution


You can use pretty much anything except hardcoding pool.ntp.org itself, including individual servers in the pool. You don't have to be a specific stratum or anything, and the monitors are comically generous with time accuracy (+-100ms)


I downloaded it along with everyone else. It’s decent but the voice over through CarPlay is choppy and cuts off words. You also can’t report or see hazards, speed checks, etc. and its time estimate is less accurate.

I want them to do well. But they need to add a few key features to actually compete beyond just the geographical names.


Seems to be missing some data. There was a safety recall for 2016-2017 Jeep Wranglers that doesn’t appear to be listed. https://static.nhtsa.gov/odi/rcl/2016/RCRIT-16V734-3469.pdf


Ok, I had a chance to look into it. A previous version of the website only checked for recalls for vehicles that had an email alert setup. I'm currently working on importing the backlog of all recalls. Thank you again!


Huh, I will look into it. Thanks for the pointer!


In my experience, it’s their chat harnesses/website that filters historical events. The model itself doesn’t.

For example you can point opencode at DeepSeek v4 and ask, it will accurately tell you about Tiananmen square.


This is similar to my use case as well. I’ll use a cloud model to identify security issues in a codebase and then use a report/spec output as input to the local model to build tests or verify the issue is real.


I stopped drinking alcohol for the new year. I wasn’t an alcoholic, but I’m sure I’ve driven home after consuming enough alcohol to blow above the legal limit. It’s not something I’m proud of. But one day I decided I was done taking risks like that, done feeling crappy the next day, done having to wreck myself just to socialize.

I don’t really miss it. Honestly the worst part is constantly having to defend my drink choice (mocktail or N/A beer) to the people I’m with who are ordering alcohol.


Good for you man, you made the right choice.


One where customers have their own scanners, and their unfounded panic overrides logical analysis by the engineers and admins.

We’ve had to patch plenty of stupid “security” bugs just to satisfy a paying customer.


This is the real answer to the op.

It’s incredible how overblown these sorts of things can become


If the customer can run the scanner and find the vuln, that means they can log in, right? Which means they can RCE.


Not always, it can be run at static code analysis or the container repository (not the prod one)?


Why not link to the English version? It seems intentionally misleading.

https://www.kimi.com/user/agreement/userPrivacy?version=v2


Chinese version was the one I found.


Why do that when you can do Sino bad?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: