Earlier quoted context omitted.
How many people in the world drink coffee? I don't understand your question.
The subtext was probably "Even among professional programmers, few know what it takes to safely expose a new system to the public internet."
Exposed DeepSeek database leaking sensitive information, including chat history
481–490 of 499 posts
Re: Exposed DeepSeek database leaking sensitive information, including chat history
#482Earlier quoted context omitted.
Hundreds of thousands. My employer alone probably has 1000.
No. I don’t think so. I think if you took many engineers and sat them at a computer and asked them to stand up a whole dev staging prod system they wouldn’t be able to do it. I certainly would not, or it would take me a significant amount of time to do properly. I have been a full stack dev for 10 years. Now take that one step further to someone whose only interaction with a development is numpy, pandas, julia, etc……
>An open dev database is rather normal
Not open to the internet it's not! Internal network, perhaps.
>someone whose only interaction with a development is numpy, pandas, julia, etc
This person should be aware of their limitations and give the task to someone who knows what they're doing.
Re: Exposed DeepSeek database leaking sensitive information, including chat history
#483Earlier quoted context omitted.
Well, you can't have it both ways: Some people like to complain that the stock market is very short termist, and valuations never reflect what happens in the long term. And here you complain that the stock market doesn't focus solely on short term pain, but is looking to some potential futures.
I wouldn't call Tesla's and especially Boeing's problems "short term".
If you are afraid of the potentially unlimited downside to a short, you can buy an out of the money call option as an insurance. Or instead of shorting directly and insuring that, you can also buy a put option, which gives you the right to sell the stock at a specific price.
Re: Exposed DeepSeek database leaking sensitive information, including chat history
#484Earlier quoted context omitted.
In the wild I've seen a company returning a JSON key "ankunftTime" in one of their APIs
Anyone remember T_PAAMAYIM_NEKUDOTAYIM?
Old habits die hard I guess...
Re: Exposed DeepSeek database leaking sensitive information, including chat history
#485Earlier quoted context omitted.
> not that I doubted they were using OpenAI The OpenAI API is basically the gold-standard for all kinds of LLM companies and tools, both closed and open source, regardless of whether the underlying model is trained on OpenAI or not.
Not just the gold-standard, but also a de-facto standard - most of the proprietary and OSS tools I've seen that let you configure LLMs only implement support for OpenAI-compatible endpoints.
Re: Exposed DeepSeek database leaking sensitive information, including chat history
#486Earlier quoted context omitted.
> No it’s from a book called design patterns I think you will find most Java programmers were using these patterns before they came across the book. The language naturally leads you in that direction. The book just put a name on them.
The book was published in 1994 with examples in C++ and Smalltalk. Java was released in 1995.
Re: Exposed DeepSeek database leaking sensitive information, including chat history
#487Earlier quoted context omitted.
The stock price had assumptions baked in about the number of units expected to be sold. DeepSeek cut that hardware estimate by as much as 45x. That is that absolute obvious correlation between that model being very efficient to train and NVDA dropping 18%.
Can someone explain how DeepSeek cut that estimate? Their (fast) API is always down, and the third-party providers on OpenRouter are more expensive than Claude.
Re: Exposed DeepSeek database leaking sensitive information, including chat history
#488Earlier quoted context omitted.
Well, yes, but I don't think I did. Edit: Also: these things need to be discussed. Or can't they? Did you rate limit me for this?
We didn't rate limit you. But I think you're underestimating the flamewar effect of a comment that begins "I honestly don't need to know more than: It's run from $Country".
Re: Exposed DeepSeek database leaking sensitive information, including chat history
#489Earlier quoted context omitted.
We didn't rate limit you. But I think you're underestimating the flamewar effect of a comment that begins "I honestly don't need to know more than: It's run from $Country".
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.
Re: Exposed DeepSeek database leaking sensitive information, including chat history
#490I wonder if this is the "cyberattack" DeepSeek was talking about?
A large scale DDos is being directed against deepseek.
US big tech wants to quench the competition.