Comment by WiSaGaN | Hacker News Reader

Comment by WiSaGaN | Hacker News Reader

Changelog is also updated: [1]

Feb. 26, 2024

API endpoints: We renamed 3 API endpoints and added 2 model endpoints.

open-mistral-7b (aka mistral-tiny-2312): renamed from mistral-tiny. The endpoint mistral-tiny will be deprecated in three months.

open-mixtral-8x7B (aka mistral-small-2312): renamed from mistral-small. The endpoint mistral-small will be deprecated in three months.

mistral-small-latest (aka mistral-small-2402): new model.

mistral-medium-latest (aka mistral-medium-2312): old model. The previous mistral-medium has been dated and tagged as mistral-medium-2312. The endpoint mistral-medium will be deprecated in three months.

mistral-large-latest (aka mistral-large-2402): our new flagship model with leading performance.

New API capabilities:

Function calling: available for Mistral Small and Mistral Large. JSON mode: available for Mistral Small and Mistral Large

La Plateforme:

We added multiple currency support to the payment system, including the option to pay in US dollars. We introduced enterprise platform features including admin management, which allows users to manage individuals from your organization.

Le Chat:

We introduced the brand new chat interface Le Chat to easily interact with Mistral models.

You can currently interact with three models: Mistral Large, Mistral Next, and Mistral Small.

[1]: https://docs.mistral.ai/platform/changelog/

The change in endpoint name is a strong suggestion that there will be few if any open models going forwards from mistral. It’s a clear move towards the default being closed. Disappointing but I guess unsurprising.

> change in endpoint name is a strong suggestion that there will be few if any open models going forwards

From deeper in the page, unclear whether this confirms your point:

We’re simplifying our endpoint offering to provide the following:

- Open-weight endpoints with competitive pricing. This comprises open-mistral-7B and open-mixtral-8x7b.

- New optimised model endpoints, mistral-small-2402 and mistral-large-2402. We’re maintaining mistral-medium, which we are not updating today.

Maybe a requirement set by MSFT in their latest "partnership"

> The change in endpoint name is a strong suggestion

I don't think the naming really suggests that. The new naming suggests they'll have two sets, the "open" models and their commercial ones.

I do agree with your skepticism though. I kinda expected them to release something, likely an older model. Currently the closest is "miqu" which was a leak of a early quantized "medium".

I know marketing folks prefer poetic names, but I wish we had consistent naming like v1.0, 2.0 etc, instead of renaming your product line every year like Apple and Xbox does. Confusing and opaque.

Amazon's jungle convinced me there's two valid solutions to string naming.

1: Trying to design and impose an ontology, echo that in naming, and then keep it coherent in perpetuity.

2: Accept that definition cannot be solved at the naming level, expect people to read the docs to dereference names, and name it whatever the hell you want.

Honestly, as long as they don't suddenly repurpose names, I have no problem with either approach. They both have their pros and cons.

PS: And jungle does have the benefit of keeping developers from making assumptions about stringN+1 in the future...

Apple does it properly - version + moniker. Searching google/etc for specific issues related to version numbers alone is a disaster, so monikers have a use.

I used to work for them, and I agree. It seems confusing from the outside but internally they maintain a pretty consistent system. Many third party partners don't follow this system properly, in my experience.

Really? Other than the iPhone and Apple Watch which do have clear series naming, I find it basically impossible to determine if any particular Apple product name is the latest version or several years old. The iPads especially, and the MacBooks were pretty confusing until recently. The Apple TV and AirPods are also a bit of a mess. I wish they would just do for all of their products what they do for the iPhone, it would make things so much simpler. But even then, the iPhones are not clearly labeled on the products themselves. If someone hands you a random iPhone, it’s impossible to tell what model is unless you have encyclopedic knowledge of the exact differences between all the different iPhones, or you have the unlock passcode and can get into the settings>about menu.

> renaming your product line every year like Apple and Xbox does.

Apple is famous for not updating product names. This year’s MacBook Pro is just “MacBook Pro”, same as last year’s, and so on since the beginning. You have to dig to get actual names like “M3, nov 2023” or the less ambiguous Mac15,3.

That said, I agree with you. Navigating the jungle of LLMs all over the place with utterly stupid naming schemes is not easy.

What's wrong with the Google names?

It seems pretty clear, they started with Bert, to borrow from AllenAIs Elmo, then Big Bird, and made some friends with Palms along the way. So of course Bard would make sense and is a natural next name.

Then it gets even simpler really, by switching Bard to Gemini it really streamlined the naming. Gemini nano < Gemini Pro 1.0 == Gemini Advanced Then after that Gemini 1.5 Pro, but that's still worse than Gemini Ultra 1.0 which is still better than Advanced. They have made it a bit easier now though with Gemma, which is worse than all of them, but still a little bigger than what you want to run on a phone, which is a great reason to introduce Germa X. I'm mostly excited for Germa X2 version deXbox though. That's when we finally get a decent model for desktop boxes.

Reply on news.ycombinator.com