Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Exposed DeepSeek database leaking sensitive information, including chat history

wiz.io

Post reply on HN
Print view View original

431–440 of 499 posts

Re: Exposed DeepSeek database leaking sensitive information, including chat history

#431

Post by stef25 »

0xDEAFBEAD wrote: post #346
heelix wrote: post #105

Earlier quoted context omitted.

Our US company sent me to France to help out with an implementation. The guy I worked with spoke very little English and my French is terrible. Both of us had done Latin, however - so the comments were hilarious as we used that as our common link. One of those projects I'd expect to show on the daily WTF at some point. I did try my hand at a translation tool, as it was all i18n up proper. Watched one guy blow coffee…

Isn't it true that schoolboys in many countries would learn Latin 100+ years ago? I suppose it would've been used sometimes in international communication?

Lol, I learned it in the 80s - 90s. If you chose to learn Latin & Greek in high school here in Belgium then you're seen as being a top student. It's still a big thing.

Re: Exposed DeepSeek database leaking sensitive information, including chat history

#432

Post by throwaway1053 »

arkh wrote: post #414
lawn wrote: post #381

Earlier quoted context omitted.

As a Swede I sometimes encounter new programmers using Swedish instead of English and it's incredibly jarring. It's a little bit better if only the comments are in Swedish but it's still annoying... Luckily it's very rare.

Until you start working on a code base made for something local only and with domain specific words. So much joy trying to remember how some word was translated for your code when a user reports a bug or ask for some new feature. Bonus point when the people who decided to use English words are also all proud of their "DDD" architecture.

I agree. It makes sense when the code needs to handle domain specific words.

Based on my experience in Norway, it is common to use English but there is also not a complete surprise to find code in Norwegian either.

I remember looking at code written by a Norwegian government agency many years ago, and asking why they used Norwegian names for functions and variables. Didn't everyone use English? The answer was that they had so much domain specific terminology that it is not only hard to find English equivalents, it was so ingrained in the business logic that they don't want to risk any confusion and legal consequences. If a function was named validateFoo, then "Foo" had a single shared understanding.

Re: Exposed DeepSeek database leaking sensitive information, including chat history

#433

Post by kgwgk »

xinayder wrote: post #392
smallerize wrote: post #295

Earlier quoted context omitted.

That's not the DeepSeek R1 model that they're offering via the API on these servers. That's a Qwen model that's been fine-tuned on output from the big R1 model.

Source?

https://arxiv.org/abs/2501.12948

Re: Exposed DeepSeek database leaking sensitive information, including chat history

#434

Post by Havoc »

sd9 wrote: post #416
Havoc wrote: post #146

Ugh. I know I’ve got at least some keys in those logs. Thankfully nothing too intense

I've been redacting my keys before sending config to chatgpt, it's a pain but I guess this shows it's worth the effort.

Yeah I avoid it too but I know I missed some during rapid copy pasting.

Re: Exposed DeepSeek database leaking sensitive information, including chat history

#435

Post by dutchbookmaker »

robomartin wrote: post #310
mlinsey wrote: post #293

Earlier quoted context omitted.

People saw how much cheaper it was to train DeepSeek v3, and assumed this reduced NVidia's TAM. I think this doesn't make much sense. a) For inference, cheaper and faster compute will increase total inference spend, because the end-user products will work better and people will use them more. b) For training, the big labs will continue to spend because we have yet to see diminishing returns to scale - in fact, we hav…

It's even more fundamental than that. Any data center project currently under way or with plans to open within the next year or two has already place orders with NVidia or will do so very soon. Due to demand and lead times, you have to order to critical parts and systems today if you want to have half a chance of receiving them a year from now. Hardware supply lines are long and complex. I like to say that you cannot…

Because all this with the stock price has nothing to do with reality.

Everyone just starts repeating the same things until people believe them as fact.

The "sell off" was basically nothing. Who cares that the NVDA went back to the price it was in October then bounced in the after market one day.

It is a complete non-story. Even at the bottom of the "sell off" it was still up 20% from the end of summer.

Listening to any news makes people less informed about the world in 2025. We are way past Gell-Mann amnesia. That was for the newspaper. "The news" in 2025 is really a strange kind of mass confusion engine. The more news a person consumes the more confused they are about the world.

Re: Exposed DeepSeek database leaking sensitive information, including chat history

#436

Post by edudobay »

david-gpu wrote: post #69
jvansc wrote: post #62

This is probably an incredibly stupid, off-topic question, but why are their database schemas and logs in English? Like, when a DeepSeek dev uses these systems as intended, would they also be seeing the columns, keys, etc. in English? Is there usually a translation step involved? Or do devs around the world just have to bite the bullet and learn enough English to be able to use the majority of tools? I'm realizing no…

> Or do devs around the world just have to bite the bullet and learn enough English to be able to use the majority of tools? That is precisely what happens. It is not unusual for code and databases to be written in English, even when the developers are from a non-English speaking country. Think about it: the toolchain, programming language and libraries are all based on English anyway.

Considering Brazil and the Spanish-speaking people whom I've worked with, it's common for English coding to be the norm for the company/project, but many people are far from being proficient in English, so we end up with funny names that are often confusing or nonsense - I've seen an "evaluation service" that is actually a "rating service" (both could translate to the same in Portuguese). They often translate to false cognates too.

There are some business concepts that are very unique to a place (country-specific or even company-specific) with no precise translation to the English-speaking world, and so I sometimes prefer to keep them in their native language.

Re: Exposed DeepSeek database leaking sensitive information, including chat history

#437

Post by iggldiggl »

TeMPOraL wrote: post #407
whilenot-dev wrote: post #369

Earlier quoted context omitted.

Correct, it's "arrival time". It isn't uncommon to find german variable names in codebases that predate web 1.0 or linux. Now that I think about it, german is especially good at creating words by concatination. So "arrival time" should just be the single word "Ankunftszeit" - "ankunftZeit" feels a bit off.

Yup. If languages were characters in a computer RPG, they'd have "special skills" listed on their character cards. Off the top of my head: - English: verbing and nouning. All languages have ways of introducing new words, but only in English I've seen it accepted as something anyone can casually do in a throwaway manner. Have a noun but want to talk about the (contextually) default action related to the noun? No big d…

> And then there's the peculiar grammar that puts the most important verb at the very end of a sentence

An American woman visiting Berlin - intent on hearing Bismarck speak - obtained two tickets for the Reichstag visitors' gallery and enlisted an interpreter to accompany her.

Soon after their arrival, Bismarck rose and began to speak. The interpreter, however, simply sat listening with intense concentration. The woman, anxious for him to begin translating, nudged and budged him, to no avail.

Finally, unable to control herself any longer, the woman burst out: "What is he saying!?" "Patience, madam," the interpreter replied. "I am waiting for the verb."

Re: Exposed DeepSeek database leaking sensitive information, including chat history

#438

Post by Kiro »

mmaunder wrote: post #225

The amount of vitriol in these comments is the really surprising data. I've seen the same on Twitter. I can only put it down to the financial pain DeepSeek inflicted on many US retail investors by wiping almost $700 billion off NVidia's stock price. I think a lot of folks didn't see it coming and it hurt them right where it matters most: In the wallet. The anger out there is very real.

I'm not seeing any vitriol or comments that are outside the norm, except people defending DeepSeek and throwing accusations left and right for seemingly no reason at all. That's the actually surprising data.

Re: Exposed DeepSeek database leaking sensitive information, including chat history

#439

Post by formerly_proven »

jvansc wrote: post #62

This is probably an incredibly stupid, off-topic question, but why are their database schemas and logs in English? Like, when a DeepSeek dev uses these systems as intended, would they also be seeing the columns, keys, etc. in English? Is there usually a translation step involved? Or do devs around the world just have to bite the bullet and learn enough English to be able to use the majority of tools? I'm realizing no…

EU - while exceptions exist, my experience generally has been that devs working in English are virtually always much better devs than their peers working in the native language of the land. Likewise, most business projects I've worked on were entirely English on the inside, even when the UI was e.g. german-only. I've also seen a few projects where the business domain is so thoroughly native-tongue (typically when the business domain is a projection of the local bureaucracy) that you couldn't name business entities in English if you tried. Those can end up with a somewhat weird hodgepodge, where the code and comments and such are still English, just the names of the entities aren't.

Re: Exposed DeepSeek database leaking sensitive information, including chat history

#440

Post by hmmm-i-wonder »

bearjaws wrote: post #77
danielodievich wrote: post #29

open exposed clickhouse is this decade's open exposed elasticsearch so common in the past

Which was originally the open exposed mongo server, then mysql/phpmyadmin, then exposed ftp, and then exposed telnet.

We move on and upwards, but never really stop making the same mistakes do we.
Post reply on HN