Comment by spullara

Comment by spullara 2 days ago

I hate that their model ids don't change as they change the underlying model. I'm not sure how you can build on that.

  % curl https://api.deepseek.com/models \          
    -H "Authorization: Bearer ${DEEPSEEK_API_KEY}"  
  {"object":"list","data":[{"id":"deepseek-chat","object":"model","owned_by":"deepseek"},{"id":"deepseek-reasoner","object":"model","owned_by":"deepseek"}]}

KronisLV 2 days ago

Oh hey, quality improvement without doing anything!

(unless/until a new version gets worse for your use case)

Reply View 0 replies

hnfong 2 days ago

Agree that having datestamps on model ids is a good idea, but it's open source, you can download the weights and build on those. In the long run, this is better than the alternative of calling API of a proprietary model and hoping it doesn't get deprecated.

Reply View 0 replies

deaux 2 days ago

Anthropic has done similar before (changing model behavior on the same dated endpoint).

Reply View 0 replies

cherioo a day ago

Allegedly deepseek is doing this because they don’t have enough gpu to serve two models concurrently.

Reply View 0 replies