3 ms·
I beg you DeepSeek just name it 4.1, you are not going to run out of numbers. While we're at it why don't you also append the git commit hash to the name as wel
by gulmothrowaway 2mo ago
I beg you DeepSeek just name it 4.1, you are not going to run out of numbers. While we're at it why don't you also append the git commit hash to the name as well
- npn 2mo agowell, I think it is easier for the developers, we don't have to change the model name everytime. deepseek also does not have resource to serve 2 different v4 pro versions.
- pixelesque 2mo agoI heard on the "China Talk" podcast talking about China and exports of open weight models they often do this because under Chinese law, they have to submit each new public model release to a government department for "validation", and if they keep the version the same, they don't need to re-submit it.
- DrBenCarson 2mo agoSame trick that had 737s falling out the sky (obviously different risk level involved in each )