logoalt Hacker News

plantain • today at 4:19 PM • 16 replies • view on HN

You are completely mad if you are running any kind of valuable workload on Runpod community or Vast. Hosts are absolutely peeking inside the VM's (you can see it openly discussed in their Discords).


Replies

gpm • today at 4:32 PM

There's got to be a ton of valuable workloads that don't care much about secrecy.

Who cares if someones spying on the process of fine tuning a model to help us pick strawberries? Even if they could somehow find a competitor to sell it to - the competitor wouldn't be interested because the risk of violating trade secret law is surely greater than whatever they can glean from our training run...

➕ show 6 replies
dv_dt • today at 4:43 PM

I hold the inverse risk assessment- I think acting on a peek risk is much higher with larger operations such as OpenAi or eg Amazon -as they've allegedly done the same on their product marketplace and deciding on generic products, in addition to open source-alike service offerings.

Larger entities have the resources, the inclination and the protective legal teams to act much differently than a resource tight n-tier platform operator

➕ show 1 reply
Aurornis • today at 4:37 PM

> (you can see it openly discussed in their Discords).

Can you explain? I haven’t used Runpod and don’t have time to search through a Discord to figure out what someone is talking about.

➕ show 1 reply
kirubakaran • today at 4:24 PM

Could you please share screenshots?

sixtyj • today at 5:34 PM

What is it good for if hosts spy on their customers?

➕ show 3 replies
mmnfrdmcx • today at 4:48 PM

What are places in your view to rent GPUs that are trustworthy they will not peek in your opinion?

➕ show 2 replies
ProfessorZoom • today at 6:07 PM

I only use their serverless stuff, but you can choose which security and compliance you want for their serverless stuff.

m00x • today at 4:35 PM

A lot of Vast.ai GPUs are also firmware-limited, so it's a big gamble when you run your workloads. You also can't get a cluster.

It's fine for comfyui workloads or simple LLM inference, but you lose both privacy and stability.

➕ show 2 replies
smallmancontrov • today at 4:25 PM

Sam is welcome to peek at my generative furry porn all he wants ( ͡° ͜ʖ ͡°)

➕ show 1 reply
janalsncm • today at 5:52 PM

The 1.8x difference between the cost in AWS and Azure is still relevant though.

kodoman • today at 5:37 PM

Honestly I think every one is peaking at everything, I don't want to be slanderous but I think even the more trusted cloud providers peak, though they do so more quietly and carefully.

➕ show 1 reply
bojangleslover • today at 5:27 PM

Could confidential computing help here?

Onavo • today at 5:14 PM

There's a lot of use cases that are not "commercially sensitive" that would require data center level privacy. E.g. a good percentage of academic research and experimentation, long running "boilerplate processing" for monitoring logs for e.g. a bird watching system or large scale web crawling where the individual website itself is mostly public. There are also use cases where the data itself is useless without other data to correlate. E.g. many log analytics use cases, if you are missing the main database data itself then the logs have zero value when intercepted. There are also use cases where you are doing general industrial level hotdog/not hotdog classification where unit economics is the most important and there's no real value to privacy e.g. on a factory floor (though sabotage is a bigger risk here).

stale2002 • today at 5:00 PM

You are ignoring the real usecases here. Not everything is large scale, secretly, b2b enterprise applications. Instead, many consumer applications are fully fine with being out in the open.

As an example, midjourney use to just publish ever generated image to their website.

If you are just doing inference things are public/open from the start, you dont have to worry much about the stuff you are talking about here.

➕ show 1 reply
nmm7 • today at 7:39 PM

[flagged]

EmX_3000 • today at 5:44 PM

[dead]