Hacker News new | ask | show | jobs
by eksu 414 days ago
Not latencies, think data privacy / keeping queries and data from leaving sovereign borders. This way, if there is some local instance / everything is local than the datacenter and service are subject to local laws and regulations (and alternatively you're not subject to foriegn the laws and regulations (and agencies).
2 comments

That's not quite correct. The "sovereignty" pitch here is largely illusory when dealing with a US-based company like OpenAI.

The US CLOUD Act (Clarifying Lawful Overseas Use of Data Act) explicitly gives US authorities the power to compel US-based companies to provide data stored on servers, regardless of where those servers are physically located. This effectively undermines any meaningful data sovereignty claims.

Consider the actual arrangement being proposed:

    - OpenAI (US company) maintains control of the infrastructure
    - OpenAI controls the models and their development
    - OpenAI maintains the security protocols and access rights
    - The data merely sits physically within national borders
This isn't sovereignty - it's a limited hosting arrangement that remains fully under US legal jurisdiction. US intelligence agencies can still access this data through legal mechanisms that bypass the host country's laws entirely.
It would also allow OpenAI to operate in countries that have state subsidized electricity and low wages.
locality is good for resilience and latency but for privacy? how does it work?

How can one audit that the bytes going from a DC in country A to a DC in the US is not the user queries but some telemetry data for example? Presumably you don't get to look at the unencrypted packets