Live data from Hacker News

Let us serve you, but don't bring us down

blog.archive.org

171–180 of 255 posts

Re: Let us serve you, but don't bring us down

#171

I have a side project that scrapes thousands and thousands of pages of a single website. So as not to piss them off (and so they don't try to block me), my script will take about 6 hours. Between each page fetch it sleeps for a small, random amount of time. It's been working like that for years.

Have you tried getting in touch to ask if they have an API?

Re: Let us serve you, but don't bring us down

#172

Just yesterday there was a comment here on HN [1] about https://jsonip.com , which is essentially supported by a single person (all operational costs included) and gets abused in a somewhat similar manner. I am not even sure what to think: do the folks not understand what they do, or are they just bluntly ignorant of it? [1] https://news.ycombinator.com/item?id=36092417

Yeah I'm getting this shit too with Marginalia Search. I'm getting about 2-2.5M queries per day that are definitely from bots that would 100% sink my server if they somehow go through the bot mitigation. It peaks at hundreds of search queries per second. To be clear these are search queries, and search queries typically trigger disk reads of about ~10-20 Mb. I get about 20,000 queries per day that may be human.

does your server have its own isp connection or is that your home connection

Re: Let us serve you, but don't bring us down

#173
post #67

I just wonder, is archive.org getting any government grant money? If they aren't they should. And I'm not even talking about just the US. All sorts of countries (US, UK, Germany - to name the few) and international organisations like EU pour hundreds of millions into "cultural projects" of very questionable value. How about they actually fund something really worthy of preservation? Of course it is archive.org role t…

[deleted]

Re: Let us serve you, but don't bring us down

#174

Unpopular opinion: Severely rate limit retrieving the files from the website / HTTP endpoint, and loudly point towards downloading the files via torrents. The torrent protocol was meant to relieve this level of server load in mind.

Depending on the type of content you download, the chances of anyone else already seeding that might actually be zero.

Archive.org would also act as a seed, so at worst it’s similar to regular download traffic. At best there’s a few more people downloading and seeding.

Re: Let us serve you, but don't bring us down

#175
post #67

I just wonder, is archive.org getting any government grant money? If they aren't they should. And I'm not even talking about just the US. All sorts of countries (US, UK, Germany - to name the few) and international organisations like EU pour hundreds of millions into "cultural projects" of very questionable value. How about they actually fund something really worthy of preservation? Of course it is archive.org role t…

Public money would also mean regulation and I doubt the IA wants to be regulated. They already see themselves apart from things like web standards given their approach to robots.txt [1]

1: https://blog.archive.org/2017/04/17/robots-txt-meant-for-sea...

Re: Let us serve you, but don't bring us down

#176
post #156
post #107

Earlier quoted context omitted.

Proof-of-work was originally introduced by Adam Back's hashcash, to fight email spam. Bitcoin is an evolution of that idea applied to digital cash. https://en.wikipedia.org//wiki/Hashcash

Would it be possible to use bitcoin pow as a replacement for captcha? It both blocks ddos and create an income through mining (client side) for the host.

It wouldn't create any income due to the electricity costs associated with mining, unless the users start buying ASICs. Also the most straightforward way of implementing this would be by having the user spending the token they generated in a transaction to prove their work, which would nullify their income. Maybe there is some workaround by monitoring the blockchain and seeing if a certain user generated some tokens at a certain time, but would it be worth the extra energy required due to the use of bitcoin' PoW? I think no.

Re: Let us serve you, but don't bring us down

#177
post #107
post #60

Earlier quoted context omitted.

In my opinion, PoW is the only reliable way, to avoid DDoS attacks. Scraping too much, too quickly is a light form of DDoS, although not intentional. PoW was invented in 2006 exactly for that purpose. The genius of bitcoin (not BTC) is that it provides an organized and practical way, for PoW to be used by everyone on the planet. Some people find it strange, because there is an imaginary token created out of pure noth…

Proof-of-work was originally introduced by Adam Back's hashcash, to fight email spam. Bitcoin is an evolution of that idea applied to digital cash. https://en.wikipedia.org//wiki/Hashcash

no, this is incorrect. Proof of Work was invented by Moni Naor and Cynthia Dwork in 1992 as a proposal to fight email spam. https://www.wisdom.weizmann.ac.il/~naor/PAPERS/pvp.ps

Re: Let us serve you, but don't bring us down

#178
post #34

Earlier quoted context omitted.

Maybe mCaptcha [0] is worth a look. It applies a Proof-of-Work like algorithm (not blockchain-related) which makes it very expensive for scrapers to get data in bulk, but poses least amount of friction to individual users. The project is implemented in Rust and received NGI.eu/NLnet funding. I don't know its state of production-readiness, but Codeberg.org is considering using it (this choice is informed by higher res…

I got interested in mCaptcha, followed your link, but couldn’t find anywhere an example of what the end user would deal with. What kind of PoW are we talking about?

Did you click on Link to Widget? It's just above the video link.

Re: Let us serve you, but don't bring us down

#179
post #156
post #107

Earlier quoted context omitted.

Proof-of-work was originally introduced by Adam Back's hashcash, to fight email spam. Bitcoin is an evolution of that idea applied to digital cash. https://en.wikipedia.org//wiki/Hashcash

Would it be possible to use bitcoin pow as a replacement for captcha? It both blocks ddos and create an income through mining (client side) for the host.

No. In fact, using such a well-known proof of work function would defeat the purpose of using PoW. Instead of having something that's cheap for occasional users but expensive for spammers, you'd have something that's cheap for people who own mining ASICs and expensive for occasional users.

Hardware specialization breaks the economics behind a CAPTCHA. To fight that you need to use a PoW that hasn't been ASIC'd yet, and be willing to change PoW functions at the drop of a hat. PoW functions that stress memory or cache are also helpful here, though you run the risk of browsers flagging you as a cryptominer (which is technically correct, even if economically wrong).

Re: Let us serve you, but don't bring us down

#180

There's no reason for Archive.org to allow any traffic from AWS, Azure or Google Cloud. Archive.org should just block the CIDRs for all those networks. Most traffic that comes from them is scraping traffic and usually malicious.

Some users have virtual desktops in the cloud. Or use browser security sandboxes that run in the cloud.
Post reply on HN