Live data from Hacker News

Exposed DeepSeek database leaking sensitive information, including chat history

wiz.io

491–499 of 499 posts

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

#491
post #489
post #488

Earlier quoted context omitted.

Well, thanks! I tend to be direct in my language usage. I'll make it more convoluted/obfuscated in the future when talking about e.g. China.

Convolution and obscurity are not the desired qualities.

I feel like this makes it impossible to sufficiently criticise countries that, eh, objectively deserve criticism. In a way, that's fair; HN is not a country review site.

However: Once in a while we get something like deepseek that is very obviously the product of some particular country.

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

#492
post #491
post #489

Earlier quoted context omitted.

Convolution and obscurity are not the desired qualities.

I feel like this makes it impossible to sufficiently criticise countries that, eh, objectively deserve criticism. In a way, that's fair; HN is not a country review site. However: Once in a while we get something like deepseek that is very obviously the product of some particular country.

I think the trick is to talk about the product rather than country.

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

#493

Earlier quoted context omitted.

Google tells me that "ankunft" means arrival in German. Is that correct?

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.

> "ankunftZeit" feels a bit off.

Not if you think of it as Hungarian notation.

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

#494
post #364
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…

From what I’ve seen, code usually comes in one of two languages: English or French. Somehow everyone but the French speaks enough English to write code!

Please come in Belgium, there are places where you can see code in Dutch, French and Englis within the same file. I suppose you even should be able to find code with some additional German in it..

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

#495
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…

This is precisely how English is the lingua franca of developers around the world, and a lot of (not all, of course) companies in e.g. Germany or Japan hire English-speaking programmers.

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

#496
post #137

Earlier quoted context omitted.

Pretty sure gamers are mentioned because those are the usual demo that has GPUs with enough memory outside of people in the ML industry.

So you’re in the demo scene as well? Yay

You were not able to use context clues to figure that "demo" in this case is short for "demographics"? Sad

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

#497
post #313

Earlier quoted context omitted.

Anyone remember T_PAAMAYIM_NEKUDOTAYIM?

No, but thanks : https://news.ycombinator.com/item?id=33829645

The original 2013 post is 404 and was not archived by IA: https://philsturgeon.com/blog/2013/09/wtf-is-t-paamayim-neku...

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

#498
post #497

Earlier quoted context omitted.

No, but thanks : https://news.ycombinator.com/item?id=33829645

The original 2013 post is 404 and was not archived by IA: https://philsturgeon.com/blog/2013/09/wtf-is-t-paamayim-neku...

Here is an archive link https://archive.ph/ACL9Q

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

#499
post #497

Earlier quoted context omitted.

The original 2013 post is 404 and was not archived by IA: https://philsturgeon.com/blog/2013/09/wtf-is-t-paamayim-neku...

Here is an archive link https://archive.ph/ACL9Q

Ok. A better, less ephemeral link is https://en.wikipedia.org/wiki/Scope_resolution_operator#PHP .

'T_PAAMAYIM_NEKUDOTAYIM' is the PHP parser's name for the '::' double-colon/scope-resolution-operator token; it means 'T_DOUBLE_COLON' in Hebrew, hence related parser error messages mean "Unexpected double-colon/scope-resolution-operator found". There was some controversy in the PHP community in 2013 about keeping the non-English naming as it was widely considered confusing to users.

Post reply on HN