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
I 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.
well, 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.
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
I 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.
Same trick that had 737s falling out the sky (obviously different risk level involved in each )
well, 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.
DeepSeek currently serves both V4 Flash 0424 and V4 Flash 0731 on OpenRouter. I'm not sure why they couldn't serve both V4 Pro versions.
nah, both point to the same model for deepseek. it's just openrouter weirdness.
Supposedly these benchmarks came from Deepseek WeChat group, so grain of salt perhaps:
https://www.reddit.com/r/DeepSeek/comments/1vmhser/benchmark...
Some more discussion: https://news.ycombinator.com/item?id=49274600
I wonder what the price is going to be after the "significant increase" they plan to introduce in the near future.
No vision looks like. Was hoping...