Zenodo performance: an update on the current situation
blog.zenodo.org
blog.zenodo.org
I found a nice workaround though. You can upload data to Github - though sometimes you need to split this across several commits b/c you can't push several GBs of data at once. You then link your Github account to Zenodo and make a release. The data is then copied over as a .zip (the Release "Asset"). Takes under a minute.
The Zenodo-Github connection is still working just fine.
Maybe this will be useful for someone!
Personally, my page fetch count is way up because I have a custom deep research agent, I've almost weaned myself off traditional search, but that agent is fetching dozens of pages, like I used to click through a bunch of search results to figure out which are relevant, adjust my query, etc...
That now happens at a higher frequency and volume through my agent.
Could well be, who knows? But, well, then, in a sense you're a part of the problem, causing a DoS for infrastructures and other, human users.
I suspect much of the infra stress is on all the "enhancements" found in the modern web application and the targeted advertising ecosystem