Earlier quoted context omitted.
That's for the lawyers to sort out, they have a lot of flexibility as a US nonprofit. The case law isn't that clear cut for this.
Internet Archive was almost destroyed by a copyright lawsuit from book publishers within the last few years. I expect they aren't excited to take on any additional risk of similar lawsuits right now.
An update on Wayback Machine access
131–140 of 374 posts
Re: An update on Wayback Machine access
#132Earlier quoted context omitted.
I assume that's because the IP range of your company network overlaps with a range used by some scrapers, and if it doesn't happen on your phone even in the corporate network, then IA probably checks some extra signals like the user agent in addition to the IP
No - my phone is not connected to work's WiFi. Wonder who the bad actors in my company are...
You can try emailing the address mentioned in their post so they adjust their filters to match just the bot networks more precisely
Re: An update on Wayback Machine access
#133Earlier quoted context omitted.
I assume that's because the IP range of your company network overlaps with a range used by some scrapers, and if it doesn't happen on your phone even in the corporate network, then IA probably checks some extra signals like the user agent in addition to the IP
No - my phone is not connected to work's WiFi. Wonder who the bad actors in my company are...
Re: An update on Wayback Machine access
#134Earlier quoted context omitted.
I'd pay for it, but only if they implemented the changes the community of users have been requesting for years.
No matter what they did, you'd have a new excuse for why you won't pay.
But anyway, no, I wouldn't keep finding reasons. I donate to them every year already. Somebody asked if I would be willing to pay and my answer was "yes, but".
It would need to be improved because certain aspects of it suck right now, not only the error this post is about. They only need go as far as their forums and github repos to see the community feedback.
Re: An update on Wayback Machine access
#135Re: An update on Wayback Machine access
#136Re: An update on Wayback Machine access
#137[flagged]
Re: An update on Wayback Machine access
#138I've been getting this error a lot. Asking users to email them with details of their OS, browser, IP address is just crazy. Their support is supposedly already swamped and they are asking for more!? Changes made by IA shouldn't become my responsibility.
> Asking users to email them with details of their OS, browser, IP address is just crazy. It's surely to serve as data to help tell humans apart from bots. > Changes made by IA shouldn't become my responsibility. They're a free service. It's ultimately not their responsibility to service you either.
IA have broken it and have no real idea how to make it better so they are going to whitelist IPs or browsers or entire operating systems? Wild.
Re: An update on Wayback Machine access
#139Earlier quoted context omitted.
I suspect most people would be ok with this if they could only do it at the rate and frequency you yourself can do it. The problem is largely one of scale.
Then make agent friendly content. Take the text and make a markdown version.
Re: An update on Wayback Machine access
#140Are any AI companies using residential proxies to scrape?