Earlier quoted context omitted.
I noticed that while everyone on hn is quite clever, we are regularly not clever enough to assume that other people in similar settings are just as clever, and recognize when they probably spent a lot more time thinking about an issue we just skim the headline of.
The people on both ends of that conversation (google vs cornell) are clever but the result will probably be enshittification.
arXiv moving from Cornell servers to Google Cloud
91–100 of 178 posts
Re: arXiv moving from Cornell servers to Google Cloud
#92Earlier quoted context omitted.
I don't understand, why don't you use cloudflare? Don't they have an unlimited egress policy with R1? Its way more predictable in my opinion that you only pay per month a fixed amount to your storage, it can also help the fact that its on the edge so users would get it way faster than lets say going to bare metal (unless you are provisioning a multi server approach and I think you might be using kubernetes there and…
Could have something to do with Cloudflare’s abhorrent sales practices.
Re: arXiv moving from Cornell servers to Google Cloud
#93Re: arXiv moving from Cornell servers to Google Cloud
#94Re: arXiv moving from Cornell servers to Google Cloud
#95Cornell is currently in hiring freeze. These roles will not be filled. Source: I applied to a Cornell-related lab in March. A week after submitting my application the role was rescinded and my contact emailed me explaining the situation.
Is it related with policies from the US administration?
> Together with all of American higher education, Cornell is entering a time of significant financial uncertainty. The potential for deep cuts in federal research funding, as well as tax legislation affecting our endowment income, has now been added to existing concerns related to rapid growth and cost escalations. It is imperative that we navigate this challenging financial landscape with a shared understanding and common purpose, to continue to advance our mission, strengthen our academic community, and deepen our impact. [0]
Re: arXiv moving from Cornell servers to Google Cloud
#96Earlier quoted context omitted.
I noticed that while everyone on hn is quite clever, we are regularly not clever enough to assume that other people in similar settings are just as clever, and recognize when they probably spent a lot more time thinking about an issue we just skim the headline of.
The people on both ends of that conversation (google vs cornell) are clever but the result will probably be enshittification.
Re: arXiv moving from Cornell servers to Google Cloud
#97Earlier quoted context omitted.
CDN is one part of strategy to deal with load. But it is not the only solution unless your site is exclusively static content. Their search, APIs, submission pipelines, duplicate detectors and a lot of other things are not going to be powered by CDNs.
But, under the assumption that the problem are indeed AI crawlers, of the things you listed only the search would be under increased load.
Re: arXiv moving from Cornell servers to Google Cloud
#98Earlier quoted context omitted.
That's true. I recently had to move a VM from gcp to hetzner because gcp would silently drop all packets to some countries, Iran included. And a Stack overflow question was the easiest way to learn about it, not gcp docs.
I have looked at it recently and it seems Iran is blocking GCP, not the other way around. Not sure if Google keep a doc up to date with who blocks them.
That's not what Google says: https://support.google.com/a/answer/2891389?hl=en
Re: arXiv moving from Cornell servers to Google Cloud
#99Earlier quoted context omitted.
Perl is becoming rare, but is LaTeX also falling out of use for technical papers? Most of the scientific and CS papers I’ve seen lately still seem to use it, even those coming from Microsoft. That said, it's often generated via Org-mode or WYSIWYG tools these days.
It’s still 100% LaTeX in my fields (AI, ML, robotics, telecom).
Re: arXiv moving from Cornell servers to Google Cloud
#100Earlier quoted context omitted.
CDN is one part of strategy to deal with load. But it is not the only solution unless your site is exclusively static content. Their search, APIs, submission pipelines, duplicate detectors and a lot of other things are not going to be powered by CDNs.
pardon me but cloudflare workers seem better for this approach. If we can get for the fact that we require javascript to run it, aside from that. Cloudflare workers is literally the best single thing to happen at least to me. With a single domain, I have done so many personal projects for problems I found interesting and I built so many projects for literally free, no Credit card. No worries whatsoever. I might ditch…
However Workers supports WASM so you don’t necessarily have to switch to JavaScript to use it.
I wrote some Rust code that I run in Cloudflare Functions, which is a layer on top of Cloudflare Workers which also supports WASM. I wrote up the gory details if you’re interested:
https://127.io/2024/11/16/generating-opengraph-image-cards-f...
JavaScript is most definitely the path of least resistance but it’s not the only way.